One of my friend told me that they used to have Oracle Enterprise Manager Grid Control 10g and deployed its agents to some database servers but now they removed Grid Control and want to use Oracle Enterprise Manager Database Console. After we uninstall the agent, we’re ready to reconfigure Enterprise Manager Database Control. The steps and commands in listed in document are they executed on the Target server or on the OMS server? Please could you identified for me which of the proceedure on the document are executed on the Target server and which one are executed on the OMS serevr.
I rerun the process again after deleting and recreating the agent12c directory per your instruction. In my previous post, I demonstrated how to use emcli to download new agent software and import them to Enterprise Manager Cloud Control.
In my opinion, Enterprise Manager Cloud Control server should be able to connect My Oracle Support.
I attended Oracle EMEA Exadata & Manageability Partner Communities Event on March 14-15.
The event started with welcome speech of Javier Puerta, Core Technology Partner Programs Director of Oracle EMEA. Today, one of my blog reader asked how we can add new agent software to Oracle Cloud Control. For whom are not familiar with PostgreSQL, it is an open source object-relational database system.
My friend Franck Pachot noticed that EM12c doesn’t show the blocking sessions across all RAC nodes.
Last month I was confronted to a very interesting and strange problem while deploying a Cloud Control 12c infrastructure. First of all, as usual, My Oracle Support is a good starting point to find out the possible causes. One possible reason presented in the My Oracle Support note 1418873.1 was that the plugins were not installed correctly on the  agent side. If you want to take additional preparatory steps for a successful upgrade, then see My Oracle Support note 1682332.1.
If you want to see a list of known issues before starting the upgrade process, then see My Oracle Support note 2022505.1.
Oracle Management Agent (Management Agent) that was installed with the Oracle Management Service (OMS) is not upgraded by default. Do not install Enterprise Manager Cloud Control 12c on servers of SPARC series: T1000, T2000, T5xx0, and T3-*. While upgrading, you might see an error message stating that some Management Agents are still in Activation Pending state, or that the Deferred Data Migration Process (DDMP) or Accrued Data Migration Process (ADMP) is not complete.
Here, the Management Repository details are details of the existing or old Management Repository. If you are upgrading a multi-OMS environment, always start the upgrade process with the first OMS, where the Admin Server is running, and not with any of the additional OMS instances.
To identify the OMS where the Admin Server is running, run the following command on the OMS home and verify if the output displays the Admin Server details. Oracle strongly recommends that you back up the Management Repository, the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. Invoke the Enterprise Manager Cloud Control Installation Wizard on the host where your existing OMS is running. While upgrading on IBM AIX, if you see an error message stating that your JDK version in the middleware home is not of a supported version, then make sure you install the supported version mentioned in the message, and then invoke the installer passing the -skipJDKValidation argument. If the host from where you are running the installation wizard does not have a connection to the Internet, then enter only the e-mail address and leave the other fields blank. On the Software Updates screen, apply the latest software updates, including the latest PSU patches. You can download the software updates in offline mode (if you do not have Internet connectivity) or online mode (if you have Internet connectivity).
On the Prerequisite Checks screen, check the status of the prerequisite checks run by the installation wizard, and verify whether your environment meets all the minimum requirements for a successful upgrade. The installation wizard runs the prerequisite checks automatically when you come to this screen. If some checks result in Warning or Failed status, then investigate and correct the problems before you proceed with the upgrade. If a prerequisite check fails reporting a missing package, then make sure you install the required package, and click Rerun. On the Installation Types screen, select Upgrade an Existing Enterprise Manager System, then select One System Upgrade. Ensure that the Middleware home you enter or validate here is used only for Enterprise Manager Cloud Control. Enter the passwords for the SYS and SYSMAN user accounts of the database that houses the Management Repository for the selected OMS. Confirm that you have backed up the Management Repository (although the installer checks only if you have backed up the Management Repository, Oracle strongly recommends that you back up the OMS, the inventory, the Software Library, and other components that are critical to the functioning of Enterprise Manager. If you encounter a Provisioning Archive Framework (PAF) prerequisite check error, then exit the installer, stop all the running and scheduled deployment procedures in your existing Enterprise Manager system, invoke the installer all over again, and retry the upgrade process. To identify all running and scheduled deployment procedures, run the following query, and note down the GUID of the deployment procedures. For information about the various prerequisite checks that are run on the database at this point, see Oracle Enterprise Manager Cloud Control Basic Installation Guide. Deployed when the plug-ins being upgraded have new dependencies, or when there are any new default plug-ins introduced with a release. Here, newer versions refer to the newer versions of plug-ins available in the Enterprise Manager software (DVD, or downloaded software) that you are using to install. If the newer versions do not exist in the Enterprise Manager software that you are using, but exist on Oracle Technology Network (OTN), then you can choose to manually download them from OTN and upgrade your existing plug-ins, instead of having them automatically migrated by default.
From the Download Plug-ins section, manually download the plug-ins and store them in an accessible location. Once the newer versions of the plug-ins are made available, this screen lists those plug-ins as plug-ins that will automatically be upgraded. If you see a message stating that you have unsupported plug-ins on the OMS or on some of the Management Agents, then follow the instructions outlined in the message to upgrade the plug-ins, and then retry upgrading the OMS. On the Select Plug-ins screen, select the optional plug-ins you want to deploy in addition to the plug-ins that will automatically be upgraded while upgrading the OMS. If you are upgrading an additional OMS, then enter the host name and port of the AdminServer configured for the first OMS that you have already upgraded, and then, enter the credentials for the existing WebLogic Server user account. Enter the absolute path to the new OMS instance base directory (gc_inst), which will be created for storing the configuration information related to the upgraded OMS. Make sure the path you enter leads up to the instance base directory, and is maintained outside the middleware home. If you are installing on an NFS-mounted drive and creating the OMS instance base directory (gc_inst) on that NFS-mounted drive, then after you install, move the lock files from the NFS-mounted drive to a local file system location. If you want to change the Oracle WebLogic Server password or the Node Manager password, see My Oracle Support note 1450798.1. If you want to change the details, click Back repeatedly until you reach the screen where you want to make the changes. On the Install Progress screen, view the overall progress (in percentage) of the upgrade operation and the status of each of the Configuration Assistants.
If a Configuration Assistant fails, the installer stops and none of the subsequent Configuration Assistants are run until the issue related to the failed Configuration Assistant is resolved. If the Management Repository upgrade fails with the following error in the schemamanager logs, then restart the database, and then try the upgrade again. Once the software binaries are copied and configured, you are prompted to run the allroot.sh script. If you are installing on Microsoft Windows operating system, then you will NOT be prompted to run this script. On the Finish screen, you should see information pertaining to the upgrade of Enterprise Manager. After upgrading all the OMS instances, upgrade the Management Agents, including the one that was installed with the first, old OMS (that is, central agent). After upgrading the central agent, if you find the agent base directory of the upgraded central agent in the old Oracle Middleware home, and if you want to move it outside that old Oracle Middleware home, then follow the instructions outlined in the My Oracle Support note 1520010.1. If you have any JVM targets associated with the old OMS, then even after you refresh the WebLogic domain, on the WebLogic domain home page, you will continue to see the JVM target that was associated with the old OMS. By default, a Provisioning Advisor Framework (PAF) staging directory is created for copying the Software Library entities related to the deployment procedures. If you want to override this location with a custom location, then invoke the installer with the EM_STAGE_DIR option, and enter a unique custom location. Manually download the plug-ins from the following URL, and store them in an accessible location. This displays a list of plug-ins available in the software kit (DVD, downloaded software) as well as the plug-ins available in this custom location. After the upgrade operation ends successfully, the OMS and the Management Agent start automatically. When you use START_OMS and b_startAgent as advanced options to control the way the OMS and the Management Agent start up automatically, sometimes the Management Agent and the host on which it was installed do not appear as targets in the Cloud Control console. If, for some reason, you are unable to delete the unwanted Management Agents, then turn off the sanity check that checks for Managements Agents with Activation Pending state.
Edit the response file and enter appropriate values for the variables described in Appendix A.
If a prerequisite check fails reporting a missing package, then make sure you install the required package, and retry the installation.
After the installation ends successfully, the OMS and the Management Agent start automatically. This section describes how you can install only the software binaries of Enterprise Manager 12c Cloud Control in graphical mode at one point, and upgrade them at a later point. This upgrade approach is best suited for multi-OMS environments, as it minimizes the downtime of the OMS instances. While installing on IBM AIX, if you see an error message stating that your JDK version in the middleware home is not of a supported version, then make sure you install the supported version mentioned in the message, and then invoke the installer passing the -skipJDKValidation argument. Enter the absolute path to the agent base directory, a location outside the Oracle Middleware home where the Management Agent can be installed. This is a mandatory field although the Management Agent installed with the OMS is not required, and must be deinstalled as described in Step (15).
After you verify the details, if you are satisfied, click Install to begin the installation process. On the Install Progress screen, view the overall progress (in percentage) of the installation. On the Finish screen, you should see information pertaining to the installation of Enterprise Manager.
Deinstall the Management Agent and delete the agent base directory you created in Step 10 (b).
The Management Agent you installed and the agent base directory you created in Step 10 (b) is essentially for a fresh installation, and is not used while upgrading Management Agents using the Agent Upgrade Console.
If you have additional OMS instances, then run this script on those additional OMS hosts as well. If you do not have the permission to run this script at this point, you can always run it after configuring the software binaries, but make sure you run it before you start upgrading the Management Agents.
Make a note of the plug-in version and plug-in update as shown in the missing plug-ins error message.
From the Download Plug-ins section, manually download the same plug-in version and the same or higher plug-in update as shown in the missing plug-ins error message. If the newer versions do not exist in the Enterprise Manager software that you are using, but exist on OTN, then you can choose to manually download them from OTN and upgrade your existing plug-ins, instead of having them automatically migrated by default. After you verify the details, if you are satisfied, click Configure to begin the installation process. After upgrading all the OMS instances, upgrade the Management Agents, including the one that was installed with the first, old OMS (that is, central agent).For more information, refer to Chapter 6.
If you have any JVM targets associated with the old OMS, then even after you refresh the WebLogic domain, on the WebLogic domain home page, you will continue see the JVM target that was associated with the old OMS. After the configuration ends successfully, the OMS and the Management Agent start automatically.
This section explains how you can install only the software binaries of Enterprise Manager 12c Cloud Control in silent mode at one point, and upgrade them at a later point. To do so, on the Management Services and Repository page, click the information icon adjacent to the page title. If the host names match and if they reflect the host on which you have installed the new 12c OMS, then it is a confirmation that you have installed on a fresh host.
If one of them reflects a different host name, then it is a confirmation that you have installed on a host that already has a Management Agent.
Add the host as a target to the new Management Agent, which was installed with the new 12c OMS as part of the 2-system upgrade. Relocate the Management Services and Repository target, which is monitored by the Management Agent installed with the old OMS host, to the new Management Agent, which was installed with the new 12c OMS as part of the 2-system upgrade.
Set the connect descriptor and credentials of the new, upgraded Management Repository as the monitoring configuration settings of the Management Services and Repository target. To do so, on the Management Services and Repository Home page, from the OMS and Repository menu, select Target Setup, then select Monitoring Configuration. As a prerequisite for upgrading your Enterprise Manager system using the 2-System upgrade approach, you are required to clone (or back up) your existing database first, and then upgrade the Oracle Management Repository (Management Repository) that is configured in it.
However, after you upgrade the Management Repository in the backed up database, link it to your earlier release of the Management Repository so that the two repositories are linked with each other, and any operations on the upgraded repository can be directly done from the old repository. If the GLOBAL_NAMES parameter is set to FALSE on both the databases, then ensure that you do not change this value until the upgrade is complete, and all the Management Agents are switched over. On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
Enterprise Manager Grid Control refreshes the page and displays a table with a list of tasks you need to perform for the upgrade approach you selected.
In the OMS Upgrade Steps section, from the table, click Create Link to Upgraded Repository.
Enter the connect string to connect to the upgraded Management Repository that will be used by Enterprise Manager Cloud Control.
You will find the connect string set as a value to the EM_REPOS_CONNECTDESCRIPTOR parameter of the emgc.properties file. If you connect using service name instead of SID, then replace SID in the syntax with SERVICE_NAME. Enter the SYSMAN password of the upgraded Management Repository that will be used by Enterprise Manager Cloud Control. If you had already provided these details and linked the two repositories, and if you are updating the connect descriptor or the SYSMAN password, then click Re-create DB Link.
After completing the 2-System upgrade, manually discover the database where you upgraded the Management Repository so that the database can be monitored in the Enterprise Manager Cloud Control Console.


In a one-system upgrade, where the upgraded Enterprise Manager 12c comes up on the same host, reconfiguration is not required as the upgraded Software Library becomes functional when the system starts.
For a one system upgrade, where the upgraded Enterprise Manager 12c comes up on a different host, all the location(s) configured in the earlier, existing Enterprise Manager system for Software Library should be accessible from the new host.
In a two-system upgrade, and sometimes in a one-system upgrade on a different host, if the location configured in the earlier, existing Enterprise Manager system is a local file system path, then follow the instructions outlined in Section 9.1 for more information. In Cloud Control, from Setup menu, select Provisioning and Patching and then, click Software Library.
On the Software Library Reconfigure Locations page, enter the new file system location that is to be configured, corresponding to the location configured in the earlier, existing Enterprise Manager system. The archive of the location which was configured for the old Enterprise Manager system must be unzipped in the corresponding location on the new file system. Since the new locations are only reconfiguring the OMS Shared File System storage locations, you must ensure that these new locations are either NFS-mounted shared locations or OCFS2 shared locations.
Click Validate to submit a validation job that performs exhaustive validation checks on the entities being migrated.
Not Supported, to identify the Management Agents that are not supported in the upgraded Enterprise Manager system because Oracle Management Agent 12c is not released for a particular platform.
To filter the list according to your needs and view only the upgrade operations that interest you, use the search functionality. For example, to view only the deployment operations that have failed, select Deployment from the Operation Type list, and select Failed from the Operation Status list, and click Search. An Operation Type refers to a job submitted for a particular agent upgrade step such as Deployment, Configuration, Health Check, Upgrade, or Switch Over. To deploy the agent software, select one or more Management Agent from the table, and click Deploy and Configure Agent.
You cannot deploy and configure Oracle Management Agent 12c for problematic Management Agents.
Also, you can deploy and configure Oracle Management Agent 12c only on existing Management Agents that are either completely upgradable or upgradable with missing plug-ins. To check the health and readiness of the deployed Management Agent, select one or more Management Agents, and click Check Agent Readiness. To view the readiness check details, select one or more Management Agents, and click View and Verify Health Check Reports. To switch over the agents, select one or more Management Agents, which have successfully been deployed, configured, and health-checked, and click Switch Agent.
This section describes the postupgrade steps you must follow after upgrading to Enterprise Manager Cloud Control.
Follow the postupgrade steps outlined in the chapter that describes how to install a new Enterprise Manager system, in the Oracle Enterprise Manager Cloud Control Basic Installation Guide. As a sanity check, ensure that all the database parameters are reset to their original values that existed before you started the upgrade operation, particularly for the job_queue_processes parameter. While upgrading the Enterprise Manager system, in the installer if you had provided a middleware home location that already contained an Oracle WebLogic Server of the supported version, which you had installed yourself before invoking the installer, then make sure you apply the patches 14482558, 13349651, and 16080294 on that Oracle WebLogic Server. These patches are required only if you are using an Oracle WebLogic Server that you installed yourself. If one or more such Management Agents are not upgraded yet to any of these supported releases, then the job fails and does not upgrade the Oracle Exalogic System targets. To resolve this issue, first check if the Management Agent on the additional OMS host is up, then refresh the Weblogic domain in the Enterprise Manager Cloud Control Console, and then restart the Management Agent on the additional OMS host. If you have the OCM scheduler installed on Oracle Management Agent, then repeat these steps on the Management Agent home as well. Targets that were created to monitor the earlier release of Enterprise Manager are not deleted automatically.
After you upgrade your Enterprise Manager using the 1-System upgrade approach, these targets might appear as if they are up and running. As part of 2-system upgrade, the central agent and the targets monitored by it are automatically deleted, and therefore, you need not manually delete the old central agent.
If you want to continue to monitor some of the targets that were automatically deleted, then install Oracle Management Agent 12c on that host. From the Enterprise Manager Cloud Control Console (or from EM CLI), when you delete a target that is associated with a user-defined compliance standard, the target is deleted from the Enterprise Manager system but its user-defined compliance standard is not removed completely. To verify if you have any stale, compliance-related data for the deleted targets, run the following SQL query manually as SYSMAN user on the Management Repository. During upgrade, all Notification Rules created in the earlier release of Enterprise Manager are automatically migrated to corresponding Incident Rulesets that act on the targets originally defined in the Notification Rule. However, for situations where the target type modeling has changed in Enterprise Manager Cloud Control, you must manually adjust the rules.
In the earlier releases of Enterprise Manager, OMS and Repository was a common target type defined for all the OMS instances in your environment. However, in Enterprise Manager Cloud Control, in addition to the target type OMS and Repository, a new target type Oracle Management Service has been introduced to represent each of the OMS instances in your environment. While the target type OMS and Repository captures metrics that are common to all the OMS instances in your environment, the target type Oracle Management Service captures metrics specific to an OMS.
Table 13-1 lists the metrics and describes the changes done to them due to the introduction of a new target type Oracle Management Service, and the actions you must take for each change. Some metrics have been moved to the individual target type—Oracle Management Service. Set up new incident rules to respond to the metrics that have been moved to different target types. Some metrics have been decommissioned due to lack of support in Enterprise Manager Cloud Control. On the Incident Rules page, from the table, select an incident rule created for Oracle Management Service (OMS), click Edit. On the Edit Rule Set page, in the Rules tab, select the event rule that operates on the moved metrics, and click Edit.
Enterprise Manager displays the Edit Rule Wizard where you can edit the incident rule for the selected incident rule set. On the Select Events page, select the metrics listed in the second row of Table 13-1, and click Remove.
On the Add Actions page and the Specify Name and Description page, click Next without making any change.
Enterprise Manger displays the Create New Rule Wizard where you can create a new incident rule set. For the metric Management Service Status, select Target Availability from the Event Type list. In the Search region, from the Target Type list, select Oracle Management Service, and then, click Search. In the Severity and Corrective Action Status region, from the Severity list, select an appropriate severity level.
On the Edit Rule Set page, in the Rules tab, select the event rule that operates on the renamed metrics, and click Edit.
On the Select Events page, select the metrics listed in the third row of Table 13-1, and click Remove.
In the Search region, from the Target Type list, select OMS and Repository, and then, click Search. On the Edit Rule Set page, in the Rules tab, select the rule Metric Alerts Event Rule, and click Edit.
On the Select Events page, select the metrics listed in the last row of Table 13-1, and click Remove.
If you upgraded using the 2-System upgrade approach, then disable the default incident rule sets.
On the Incident Rules - All Enterprise Rules page, scroll down the table, and expand Incident management Ruleset for all targets. Once all the rule sets are disabled, ensure that the Enabled column of the table shows No with a warning icon next to it. If you were monitoring a SOA target in your earlier release of Enterprise Manager, then in the health report you generated as described in Section 11.2, you might have seen metric collection errors for the metrics Top SOA SQL Queries and Dehydration Store Tables. To resolve that issue, access the Monitoring Configuration page of the SOA target, and provide the database credentials. After the upgrade, you must stop all active Linux patching jobs that were submitted prior to the upgrade, reset their credentials, and then resubmit the jobs on the same targets. In the Advanced Search options, select Job Type as DownloadLatestPkgs, Target Type as Host, Status as Active, Scheduled Start as All, and then click Go. In the Setup RPM Repository page, select the Host target and set Normal Host Credentials and Privileged Host Credentials for this host target.
In the Advanced Search options, select Job Type as UpdateHostPackages, Target Type as All Target Types against which jobs were submitted, Status as Active, Scheduled Start as All, and then click Go.
In the Setup Groups page, select the group on which you stopped an active UpdateHostPackages job and click Edit.
In the Edit Group: Credentials page, either use Host Preferred Credentials or Override Preferred Credentials and specify Normal Host Credentials and Privileged Host Credentials. Before editing this step, ensure that the host Preferred credentials are set already or the appropriate Named Credentials have been created already. After upgrade, you must reset the credentials of all active Linux patching jobs that were submitted prior to the upgrade, and then resubmit the jobs.
In the Advanced Search region, in the Name field, enter the job name PACKAGES UPDATE%, and from the Job Type list, select UpdateHostPackages.
Repeat Step (3) to Step (7) for the job name DOWNLOADLATESTPKGS% of the job type DownloadLatestPkgs.
If you have a multi-OMS environment with a Server Load Balancer (SLB) configured for the upgraded OMS instances, then make sure you update the console URL on the Management Services and Repository page. On the Management Services and Repository page, in the Overview section, click Edit against the Console URL label, and modify the URL to the SLB URL. Verify if the updated console URL appears correctly in the e-mails sent by Enterprise Manager. This section is applicable only for Oracle WebLogic Server custom certificates, and not applicable for Enterprise Manager Console certificates. If it still shows the older version and not the upgraded version, then restart the Management Agent on the additional OMS host. On the Target Settings for Compliance Standard page, in the left tree view, select the rule node, and in the right panel, from the Compliance Standard Rule Evaluation Status list, select Disabled. Access the emgc.properties file in the OMS base instance home directory (gc_inst), and check the value of the argument you reset. If you had selectively skipped or postponed the upgrade of certain job types as described in Step 2 (j) of Table 4-1, then after upgrading the Enterprise Manager system, make sure you clear the values you inserted into the MGMT_PARAMETERS table.
Deferred Data Migration is a post-upgrade activity to migrate the format of the data stored in an earlier release of Enterprise Manager to the format compatible with the upgraded Enterprise Manager system.
The format of the data stored in Enterprise Manager Cloud Control is different from the format in which the data was stored in any earlier release of Enterprise Manager. When you upgrade from an earlier release of Enterprise Manager to Enterprise Manager Cloud Control, the data format gets automatically converted or migrated to the format that is compatible with Enterprise Manager Cloud Control. However, the time taken to migrate the data format depends on the volume of data available in your earlier release of Enterprise Manager. Considering this, Oracle has fine-tuned its upgrade process to migrate the data format in two distinct phases. In the first phase, when the Enterprise Manager system is shut down and upgraded, the most critical data relevant to the functioning of Enterprise Manager Cloud Control is migrated within a short time so that the new system can start functioning without much downtime. In the second phase, after the upgraded Enterprise Manager system starts functioning, the remaining data is migrated. The data whose format is migrated in the second phase, after Enterprise Manager Cloud Control starts functioning, is called the Deferred Data, and this process of migrating from old to new format is called the Deferred Data Migration. Do not shut down or restart the OMS or the Management Repository while DDMP jobs are running. In Cloud Control, from the Setup menu, select Manage Cloud Control and then, click Post Upgrade Tasks. The tab provides a list of data migration jobs with their status, start date and time, and end date and time. Accrued Data Migration is a post-upgrade activity to migrate the accrued data stored in an earlier release of Oracle Management Repository (Management Repository) to the upgraded Management Repository.
The Accrued Data Migration process does not migrate any of the following changes if they were done after the Management Repository was backed up. Check the Diff Report as described in Section 13.9 to know what all changes are not migrated via the ADMP process and what needs to be migrated manually. The migration activity is essentially a job in Enterprise Manager that runs in the background immediately after the earlier releases of Oracle Management Agents (Management Agents) are switched over to Oracle Management Agent 12c, particularly in the case of 2-System upgrade approach. As part of the upgrade process, when you switch over the earlier releases of Oracle Management Agents to Oracle Management Agent 12c, the new Management Agents start communicating with Enterprise Manager Cloud Control, and start uploading data to the upgraded Oracle Management Repository (Management Repository). In the 1-System upgrade approach, the entire Enterprise Manager system is upgraded, and therefore, all the Management Agents are switched over at a given time.
However, in the 2-System upgrade approach, you can choose to switch over your Management Agents in phases.
When you swtich over the next set of Management Agents in the next phase, although they start uploading data to the upgraded Management Repository, the data uploaded to the old Management Repository before being switched over continues to exist in the old Management Repository.
If the ECM history data is associated with a target that is no longer part of the Enterprise Manager system, then the ECM history data for that target is not migrated to Enterprise Manager Cloud Control. As part of the data migration process, summary counts are now calculated and displayed in the ECM Summary region. If you do not see key values that you saw in the past, or if you see new values as key values, then note that this is an expected behavior. If you want to prevent the ADMP jobs from running immediately by default, then see Section 10.2 (Step 6). ADMP uses DBMS_SCHEDULER, so make sure all scheduler-related settings are turned on (on the server) to submit any jobs using DBMS_SCHEDULER.
The Accrued Data Migration page displays information about the accrued data migration jobs related to all the targets available in your Enterprise Manager system. All, to view all the accrued data migration jobs for all the targets in your Enterprise Manager system. Active, to view the accrued data migration jobs that either failed or are currently running. To stop a running job, select the target for which you want to stop the job and click Stop. However, before I could get the SEs to run the root.sh scripts as root for me on the server, the system timed out on me. If you can’t deinstall your agent with runInstaller (because your deployment is broken), you may delete the directory of the agent and re-deploy the agent to another directory.
In other word you want me to delete “agent12c” directory I created before the deployment of the agent on the target server? You shouldn’t ignore the prerequisites, you should try to fix them before you deploy the agent.
According to the bug, you get this error if you do not use a fully qualified domain name (FQDN) of the OMS server for emcli setup (or while installing Enterprise Manager Cloud Control).


Enterprise Manager Cloud Control will not switch to offline mode when it can connect to My Oracle Support. Then Ron Tolido (VP, Capgemini) made a great keynote presentation about Innovation and Cloud infrastructure. He says he installed Cloud Control on a Linux server and now he wants to deploy cloud control agents to Solaris Servers. It has more than 15 years of active development and a proven architecture that has earned it a strong reputation for reliability, data integrity, and correctness. YUM (Yellowdog Updater, Modified) is an open-source command-line package-management utility for Linux operating systems using the RPM Package Manager.
My presentation will be about creating a mobile interface (a simple application) using Application Express to access Oracle Enterprise Manager repository views (and some procedures) to manage incidents and problems. Select the one that best suits your requirement, and follow the instructions outlined in the respective section.
Wait until the upgrade completes fully because there might be some standalone Management Agents in status pending state while the upgrade is in progress. You will be prompted for the administration server password and the repository password if you do not explicitly specify them in the command line. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support. This means that you must provide network access to this URL, or grant proxy access to it from any client that will access My Oracle Support.
For instructions, see Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.
The installation wizard validates the package name as well as the version, so make sure you install the packages of the minimum versions mentioned in Oracle Enterprise Manager Cloud Control Basic Installation Guide. However, make sure this is a new middleware home meant for the Enterprise Manager system you are installing now, and not the middleware home you were using earlier for the previous release of Enterprise Manager system. In this case, the installer detects them and displays the Middleware home where they are installed. Ensure that no other Oracle Fusion Middleware products or components are installed in the same Middleware home.
By default, the host name is the name of the host where the existing, earlier release of Enterprise Manager was installed. This is required to create a new WebLogic domain (GCDomain) on the same port and host name as the AdminServer used by the earlier release of the OMS you are upgrading. Modify the lock file location in the httpd.conf file to map to a location on a local file system. In this case, diagnose the issue, resolve it, and then, click Retry on the Install Progress screen to rerun the Configuration Assistants starting from the Configuration Assistant that failed.
If you want to override this with a custom name, then invoke the installer with the WLS_DOMAIN_NAME option, and enter a unique custom name.
If you do not want them to start automatically, then invoke the installer with START_OMS and b_startAgent options, and set them to true or false depending on what you want to control. EM CLI Client is available by default with every OMS installation, so you need not install the client separately.
This enables you to proceed with the upgrade process without encountering any such warning.
In both these sections, for the LockFile parameter, specify the absolute path to a location on the local file system where Oracle HTTP Server can automatically create the http_lock file. If it does not exit, create it in the following way, and then specify this path in the httpd.conf file. The installer validates the package name as well as the version, so make sure you install the packages of the minimum versions mentioned in Oracle Enterprise Manager Cloud Control Basic Installation Guide. This approach consists of three parts, mainly copying the software binaries, running the root.sh script, and configuring the software binaries. The Agent Upgrade Console performs an out-of-place upgrade, and creates a new agent home in the existing agent base directory for every Management Agent that is upgraded. As a prerequisite, you must back up the Management Repository before starting the upgrade process.
Store the plug-ins in an accessible location, and ensure that the location is meant only for these missing plug-ins.
If you do not want them to start automatically, then invoke the script with START_OMS and b_startAgent options, and set them to true or false depending on what you want to control. In the Target Information region that appears, as shown in Figure 13-1, validate the host name and make sure it reflects the host on which you have installed the new 12c OMS. Clean up or remove information related to this Management Agent and the targets monitored by it, from the Management Repository. To do so, on the Management Agent home page, in the Monitoring section, in the Monitored Targets tab, verify that the host is listed. On the Monitoring Configuration page, enter the connect descriptor and the credentials of the new, upgraded Management Repository. This is to ensure that the upgraded Management Repository coexists with the earlier release of the Management Repository.
A job starting with SwlibUpgradeLocations is submitted, which must be tracked to successful completion, following which you should initiate any patching or provisioning tasks. Enterprise Manager Grid Control displays the Agent Upgrade Status page that provides information. An operation name refers to the operation name you specified while submitting any of these jobs.
If you want to confirm that you have verified the report, then select the Management Agent and click Verify and Sign Off Report. Before starting the 2-system upgrade, you would have shut it down to prevent it from connecting to the Management Repository for metric collections. They are not required if you provided an empty middleware home location and let the installer install the Oracle WebLogic Server while performing the upgrade.
Under such circumstances, to resolve the issue, first upgrade those Management Agents, and then try submitting this job to upgrade the Oracle Exalogic System targets. In this case, set the environment variable ORACLE_HOME to the Management Agent home as described in Step (1), and perform Step (2) from its home.
In this case, skip Step (1), set the environment variable ORACLE_HOME to the Management Agent home as described in Step (2), and perform Step (3) from its home. This is because you might have created notification rules, metric threshold settings, compliance standard settings, jobs, and so on for these targets, and you might want to copy them to the new Oracle WebLogic Server targets of Enterprise Manager Cloud Control. You can delete these by deleting the top-level Oracle Application Server target of each old OMS. And the metrics collected for the different OMS instances were shown within this common target type. Therefore, if you have five OMS instances in your environment, you will see one target type OMS and Repository and five instances of the target type Oracle Management Service - one for each OMS. If you do not disable them, the incidents are automatically created for all critical metric alerts. If not, from the Setup menu, select Security and then Named Credentials to create Named Credentials or Preferred Credentials to set the Preferred Credentials for the host targets contained in the Linux Patching group. The console URL you enter here is used to compose links pointing back to the Enterprise Manager Cloud Control Console in the e-mails sent by Enterprise Manager. For information on the command and the options you can pass, see the Oracle Enterprise Manager Cloud Control Security Guide. To do so, from the Setup menu, select Manage Cloud Control, then select Management Services.
Therefore, as a postupgrade step, you must manually reset the heap size to the custom value of 8 GB. The migration activity is essentially a job in Enterprise Manager that is submitted when the Oracle Management Repository gets upgraded and is scheduled to run in the background when the upgraded Enterprise Manager system starts functioning.
Therefore, if you have a large amount of data, then it takes longer to migrate, and as a result, the upgrade process takes more time to complete. At this point, only some historical data is unavailable, but you can start monitoring the targets in the upgraded Enterprise Manager system, and see new alerts generated by the upgraded Oracle Management Agent.
The accrued data relates to functional areas such as blackouts, alerts, events, metrics, and so on.
If you want these changes in the upgraded Enterprise Manager system, you must manually redo these changes after upgrade. In this approach, earlier releases of Management Agents cannot coexist with the upgraded ones, and once they are switched over, the upgraded Management Agents upload data only to one Management Repository at any given point, which is the upgraded repository. When one set of Management Agents are switched over, they start uploading data about their hosts and targets to the upgraded Management Repository, whereas the ones that are not switched over yet, continue to upload data about their hosts and targets to the old Management Repository.
This data is called the Accrued Data, and the process of migrating this accrued data from the old Management Repository to the new one is called the Accrued Data Migration Process. By default, for every target, the accrued data migration job migrates the ECM history details as well as the metric details. First I thought he does not run the commands in time so emcli session expires but I get the same error in one of my test servers. Sometimes, security policies do not allow your Cloud Control server connect internet in any way.
Oracle Database is running on Sparc Server (Solaris 10), so I downloaded the free ODBC packages from unixODBC project. Like all other enterprise companies, we use different databases beside Oracle to lower the costs. It handles library dependencies, so it’s the easiest and maybe the best way to install any RPMs. Anyway, if our Linux server is ready, we can download and install Repository RPM for our server. I have connected to first node of our RAC database, created a sample table, inserted a row, committed, and then deleted the row. The x86_64 cloud control 12c agent has been deployed on this server with the standard Cloud Control 12c agent deployment procedure (not the scope of this post).
After you correct the problems, return to this screen and click Rerun to check the prerequisites again. To understand the logic the installation wizard uses to verify these packages, see Oracle Enterprise Manager Cloud Control Basic Installation Guide.
If you enter the old gc_inst directory, then the installer will display a warning that the directory is not empty.
The location is used only for provisioning activities—entities are copied for a deployment procedure, and then, deleted once the deployment procedure ends.
If the location you specify does not already exist, then create it first, and then specify the path here.
To understand the logic the installer uses to verify these packages, see Oracle Enterprise Manager Cloud Control Basic Installation Guide. You can copy the software binaries on all the OMS hosts in parallel without shutting down the OMS instances.
If you have not already taken a backup, then do so immediately, and then return to the installer to continue with the upgrade. Also verify that the same host name appears on the top-right corner of the page, right below the Search Target Name text box, as shown in Figure 13-1. When you enter this value as the connect string, remove all backslashes (\) and white spaces if any. And each of these operations can have a status such as Not Started, In Progress, Success, Not Supported, Failed, or Pending Report Verification. If you want to view more details about the readiness check, then select the Management Agent and click View Detailed Report. To circumvent this issue, after upgrading the Enterprise Manager system, manually delete all stale compliance-related data for the deleted targets. Therefore, after upgrading, make sure you reconfigure the Oracle WebLogic Servers with custom certificates. Unfortunately, until the upgrade process completes, your existing Enterprise Manager system might be unavailable, particularly when you use a 1-System upgrade approach (either on the local host or on a different, remote host). Therefore, the earlier releases of Management Agents coexist with the upgraded ones when only some of them are switched over, and under such circumstances, the data is uploaded to the old Management Repository as well as the new one at a given point. If metadata keys were removed from the metadata, those values will no longer be displayed in the Enterprise Manager Cloud Control as key columns, though the data is still present in the migrated database. In this case, you can use it in offline mode, and still can use self-update and patch management features. I followed the manageability track because it mostly focused on Enterprise Manager Cloud Control.
In this blog post, I’ll install PostgreSQL on Oracle Linux because I use Oracle Linux when I need a Linux OS, and its support costs are lower than Redhat Enterprise Linux. While the session is open, I opened another terminal, connected to second node and tried to delete the rows in same table so my second session started to wait for the transaction of my first session completed. For instructions to use the Agent Upgrade Console to upgrade Management Agents, see Chapter 6. If you do not have access to it, then set the TEMP variable to a location where the install user has access, and then relaunch the installation wizard. The installer detects and displays only those Middleware homes where Enterprise Manager is not already configured. This not only saves time but also enables the earlier release of the OMS instances to remain up and running at this point.
Manually delete the targets as they are no longer needed in the Enterprise Manager Cloud Control.
However, note that only one Management Agent represents a host at any given time, so the coexistence does not indicate two Management Agents on the same host. If existing columns are now flagged as key columns, those columns will start appearing as key columns for newly collected data only. In next weeks, I’m also gonna blog about backup and replication for PostgreSQL, and maybe (not promising) blog about some key concepts of PostgreSQL such as MVCC, vacuum and vacuum freeze. So I will not go deep on technical details but I think it will be still enough to show what can be done with a small effort. Once the software binaries are copied, you can shut down all the OMS instances, and configure the software binaries to upgrade the OMS instances, one after the other. Since the agent base directory you provided in Step 10 (b) is no longer required, you can deinstall the Management Agent and manually delete the agent base directory. It only indicates an earlier release of Management Agent monitoring a host that coexists with an upgraded Management Agent monitoring another host. For new columns that are added either as key columns or non key columns, data will start appearing for newly collected data only.
Therefore, the downtime begins only when you start configuring the OMS instances, and not while copying the software binaries to the host.



Affiliate program paypal payout time
Owncloud first login password zon


Comments

  1. 14.02.2016 at 18:31:42


    This is probably one of the best approach is to determine the most appropriate option on each.

    Author: LoVeS_THE_LiFe
  2. 14.02.2016 at 13:14:28


    Computing stack, because they the documents are kept.

    Author: 10_Uj_040
  3. 14.02.2016 at 11:26:47


    Services in the ballpark of $5-$10 per month can do: pay.

    Author: Gunewlinec_CeKa
  4. 14.02.2016 at 23:47:25


    Data in real-time, online backup is closer to a ?�save' button that you hit cloud-scale computing resources while.

    Author: Hulya