This chapter describes the preupgrade requirements you must meet. In particular, this part covers the following:
Identifying a Host and Port for the New Enterprise Manager System
Managing and Validating the Location of the Management Agent Software and Its Associated Plug-ins
Cloning (or Backing Up) Your Existing Database Before Upgrading an Enterprise Manager System
Analyzing Your Environment Before Upgrading an Enterprise Manager System
Providing Repository Backup Details for Upgrading an Enterprise Manager System
For instructions to apply the Preupgrade Console patch, see Section 2.2.3.1.
Note:
Follow these instructions only if you are upgrading using the 2-System upgrade approach or the 1-System upgrade approach on a different host. Perform these steps in the Enterprise Manager Grid Control console of the earlier release.To identify and provide information about the host where you plan to install Enterprise Manager Cloud Control, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Select Upgrade Type section, select one of the following.
To upgrade your Enterprise Manager system with "near zero" downtime (even if you manually install Management Agents), select 2-System.
To upgrade your Enterprise Manager system with downtime on a different host, select 1-System on a Different Host.
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 Preupgrade Steps section, from the table, click Identify Host and Port for New Enterprise Manager System.
On the Identify Host and Port for New Enterprise Manager System page, enter the following:
The fully qualified name of the host where you plan to install Enterprise Manager Cloud Control. For example, example.com.
The secure port and the unsecure upload port you plan to assign for that Enterprise Manager Cloud Control console. For example, 1768.
In case of a multi-OMS environment, if the host on which you plan to install Oracle Management Service 12c is managed by a Server Load Balancer (SLB), then select Click if you wish to have Server Load Balancer (SLB) configured for your Oracle Management Service 12c Release 5 (12.1.0.5.0). Then, enter the fully qualified name, and then the secure and unsecure upload ports of the host where the SLB is running.
Note:
For 2-System upgrade approach and 1-System upgrade approach on a different host, understandably, the host referred to here is any host other than the one where your existing OMS is running. In a Multi-OMS environment this means that a new virtual host name must be used and a new SLB configuration created for this virtual host name.
Ensure that you install Oracle Management Service 12c on the host entered here, and ensure that you use the same HTTPS and HTTP upload ports entered here. In the installation wizard, on the Port Configuration Details screen, enter the HTTPS upload port for the component Enterprise Manager Upload Http SSL Port, and the HTTP upload port for the component Enterprise Manager Upload Http Port.
If you have already installed Oracle Management Service 12c, then retrieve the values from the emgc.properties file, which is available in the OMS home. For HTTPS upload port, look for the value assigned to the parameter EM_UPLOAD_HTTPS_PORT, and for HTTP upload port, look for the value assigned to the parameter EM_UPLOAD_HTTP_PORT.
Once you enter the secure and unsecure upload ports here, avoid changing them once the deployment starts.
In the Configure Postupgrade Tasks section, select one of the following options:
Disable automatic DDMP jobs, if you want to prevent the DDMP jobs from running automatically. This option is applicable for 1-System upgrade approach as well as 1-System upgrade approach on a different host.
If you want to run the DDMP jobs explicitly after upgrading to Enterprise Manager Cloud Control, perform Step (3) as described in Section 13.7.2—select each component and click Start.
Note:
If you disable the DDMP jobs, the ADMP jobs are also disabled by default.Disable automatic ADMP jobs, if you want to prevent the ADMP jobs from running automatically. This option is applicable only for 1-System upgrade approach.
If you want to run the DDMP jobs explicitly after upgrading to Enterprise Manager Cloud Control, perform Step (3) as described in Section 13.8.2.
Click Save.
Enterprise Manager Grid Control saves the information you provided and returns to the Upgrade Console page that shows a list of tasks to perform for the upgrade approach you selected.
Note:
Follow these instructions only if you are upgrading using the 1-System upgrade approach. Perform these steps in the Enterprise Manager Grid Control console of the earlier release.By default, soon after the upgrade, Enterprise Manager Cloud Control automatically runs the deferred data migration process (DDMP) jobs. These jobs migrate historical data such as metrics, configuration, and so on from the format stored in the earlier release of Enterprise Manager to the format compatible with Enterprise Manager Cloud Control. For more information DDMP jobs, see Section 13.7.1.
Depending on the size of your Enterprise Manager system, these jobs consume a high amount of Management Repository resources and take longer time to complete. In particular, when you upgrade using the 1-System upgrade approach, you might face resource contention as all the Management Agents will be up and running soon after the upgrade.
For better control on these jobs, you may choose to disable the auto-run of these DDMP jobs. If you do so, you must run these jobs later explicitly from the Post Upgrade Tasks page within the Enterprise Manager Cloud Control console.
To disable the auto-run of DDMP jobs, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Select Upgrade Type section, select 1-System.
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 Preupgrade Steps section, from the table, click Configure Postupgrade Tasks.
On the Configure Postupgrade Tasks page, select Disable automatic DDMP jobs.
Click Save.
Enterprise Manager Grid Control saves the information you provided and returns to the Upgrade Console page that shows a list of tasks to perform for the upgrade approach you selected.
Note:
If you want to run the DDMP jobs explicitly after upgrading to Enterprise Manager Cloud Control, perform Step (3) as described in Section 13.7.2—select each component and click Start.Note:
Perform these steps in the Enterprise Manager Grid Control console of the earlier release.To manage information about the location of the core Management Agent software and its associated plug-ins, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Select Upgrade Type section, select one of the following. For information about these upgrade approaches, see Chapter 2.
To upgrade your Enterprise Manager system with downtime (even if you manually install Management Agents), select 1-System.
To upgrade your Enterprise Manager system with "near zero" downtime (even if you manually install Management Agents), select 2-System.
To upgrade your Enterprise Manager system with downtime on a different host, select 1-System on a Different Host.
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 Preupgrade Steps section, from the table, click Manage Software.
On the Manage Software page, in the Agent Upgradability and Target Upgradability pie charts, click the hyperlinks in the respective legends and identify the Management Agents and targets that can be upgraded, and that cannot be upgraded due to unavailability of the Management Agent software or the plug-in software.
In the Provide Software Location section, enter the absolute path to the directory where the core Management Agent software and the plug-in software are present for the required platforms.
For example, /john/software/oracle/em/.
And then, click Validate to register that location with the Enterprise Manager system.
Note:
The absolute path you enter must be to a staging location that contains both the Management Agent software and the plug-in software.
To download the Management Agent software and the plug-ins, follow these steps
(a) Access the following URL:
http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-upgrade-console-502238.html
(b) Download the Management Agent software to an accessible location. Do NOT extract the contents of the software ZIP file. The Management Agent software is platform-specific, so ensure that you copy the software for the platform on which you want to install.
(c) Download all the required plug-ins to the same location. Plug-ins are generic, so they are common for all platforms.
Ensure that you download all the plug-ins listed as required plug-ins on the Manage Software page, whether or not you want to monitor a target with them. You may feel that a few plug-ins are not required because you do not have targets to be monitored by them, but those plug-ins may be required for upgrading your system. Therefore, download all the plug-ins listed on the Manage Software page. Ensure that you download these plug-ins before backing up the database that contains the Management Repository.
Ensure that the core Management Agent software and the plug-in software you provide have read permission, and ensure that the location in which they are present is accessible and has read and write permission.
If you plan to install multiple Oracle Management Services (OMS instances), then ensure that the location you enter is writable and accessible to all the OMS instances.
If you have a plug-in version deployed to the earlier release of Enterprise Manager that is not supported in Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5), then do NOT provide the software of the higher version of that plug-in even if its available for download. This ensures that the unsupported version is removed while upgrading to 12c Release 5 (12.1.0.5). After you upgrade, you can deploy the higher version directly from the Plug-In Manager.
After registering the locations of the Management Agent software and the plug-in software, if you download some more plug-ins at a later stage in the same or a different location, then register the location of those recently downloaded plug-ins as well.
The validation and registration process might take some time to complete, so after you click Validate, wait for some time for the process to end. Once the process ends, you should see a message confirming that the location has been successfully registered.
Note:
If you are deploying Oracle Management Agent 12c on platforms such as Red Hat Enterprise Linux 4.x, Oracle Linux 4.x, or SUSE Linux Enterprise 10, then ensure that you deploy only the 32-bit version of the Management Agent software. Do not deploy the 64-bit version because it is not supported on these platforms.However, despite using the 32-bit version, while validating the software on the Manage Software page, if you see an error stating that the 32-bit version is not supported, then follow these steps to resolve the issue:
Run the following SQL query in the old Management Repository as a sysman user. Ensure that the Management Repository is not already upgraded at this point.
update PRE_UPGC_AGT_STAT_MGMT set PLATFORM_ID='46', PLATFORM_NAME='Linux x86-64' where OS_VERSION like '%Enterprise Linux%elease%4%' and PLATFORM_ID='226';
update PRE_UPGC_AGT_STAT_MGMT set PLATFORM_ID='46', PLATFORM_NAME='Linux x86-64' where OS_VERSION like '%SUSE%10%' and PLATFORM_ID='226';
commit;
On the Manage Software page, enter the absolute path to the location where the 32-bit version of the Management Agent software is available, and click Validate.
In the Agent Upgradability pie chart, verify if the Management Agent appears as an upgradable target.
If you are performing a 2-system upgrade, then make sure you clone (or back up) your existing database that houses the Management Repository. For instructions, refer to Step 3 (f) of Table 9-2 of Section 9.2.
Note:
If you want to recover the cloned or backed up Oracle Database 11g Release 1 (11.1.0.7) or 10g Release 2 (10.2.0.5) from Microsoft Windows 32-bit to Microsoft Windows 64-bit, then see Appendix J.This chapter describes how you can analyze your existing Oracle Management Agents (Management Agent) and prepare yourself to upgrade them. In particular, this chapter covers the following:
Checking the Upgradability Status of Oracle Management Agents
Identifying Oracle Management Agents That Need to Be Reconfigured
Identifying Oracle Management Agents That are Not Supported in Enterprise Manager 12c
Identifying Oracle Management Agents That are Installed after Repository Backup
Note:
Perform these steps in the Enterprise Manager Grid Control console of the earlier release.Every Oracle software product, including Oracle Management Agent (Management Agent) installed on a host is registered with the central inventory (oraInventory). Every Oracle software product has an entry in the inventory.xml file, which is present in the oraInventory directory. If a Management Agent is registered with the central inventory, then it is a Management Agent with valid inventory.
To identify Management Agents with valid inventory, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Agent Upgrade Status section, view the count displayed against Agents with Valid Inventory.
To drill down and view more information about each of the Management Agents, click the count value.
Enterprise Manager Grid Control displays the Upgrade Status page that provides information such as the platform on which the Management Agents are running; their versions; their old and new Oracle home locations; and their deployment, configuration, health check, and switch over status.
Note:
The count displayed here does not include the Management Agents with invalid inventory and the Management Agents that were installed after the count was determined.
To consider the Management Agents that have an invalid inventory, first resolve the issue with such Management Agents. Ensure that there are no such faulty Management Agents. For information on how to identify such Management Agents and resolve them, see Section 10.6.2. Once you have resolved the issue, click Refresh Agents and Targets List.
To consider the Management Agents that were installed after the count was determined, refresh the list by clicking Refresh Agents and Targets List.
Every Oracle software product, including Management Agent installed on a host is registered with the central inventory (oraInventory). Every Oracle software product has an entry in the inventory.xml file, which is present in the oraInventory directory.
However, there may be circumstances when an entry for a Management Agent might be missing, incomplete, or corrupt, or the entry might be existing with an incorrect syntax. In addition, there is also a possibility that the host configuration was not refreshed and the latest configuration was not collected. If a Management Agent is not registered with the central inventory for such reasons, then it is a Management Agent with invalid inventory.
Management Agents with invalid inventory do not appear in the Preupgrade Console, and as a result, you will not be able to upgrade them until the issues are fixed.
To identify Management Agents with invalid inventory, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Agent Upgrade Status section, view the count displayed against Agents with Invalid Inventory.
To drill down and view more information about each of the Management Agents, click the count value.
Note:
To resolve this issue, follow these steps:Check the entry for these Management Agents in the inventory.xml file.
The inventory.xml file is present in the oraInventory directory (central inventory). The location of the oraInventory directory is mentioned in the oraInst.loc file that you pass while invoking the installer in silent mode. Ensure that the entry is present with the correct syntax.
Refresh the host configuration in one of the following ways:
(a) Go to the home page of the host. Click the Configuration tab. On the Configuration page, click Refresh.
(b) Go to the Deployments page. In the Configuration section, click Refresh Host Configuration.
If Step 2 (a) or Step 2 (b) fail, then run the following command from the Management Agent home:
$<AGENT_HOME>/bin/emctl control agent runCollection
Refresh the agent list in the Preupgrade Console.
Go to the Preupgrade Console. In the Agent Upgrade Status section, click Refresh Agents and Targets List.
To check the upgradability status of the Management Agents, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Preupgrade Steps section, from the table, click Manage Software.
On the Manage Software page, view the Agent Upgradability pie chart. The pie chart graphically shows the following information:
Completely Upgradable - Number of Management Agents that can be fully upgraded because the Management Agent software and all the associated, target-specific management plug-in software are available.
Missing Plug-Ins Software - Number of Management Agents that can be partially upgraded because the Management Agent software and only a few of the associated, target-specific management plug-in software are available. Some management plug-in software are either missing or unsupported in the upgraded Enterprise Manager system.
Missing Agent Software - Number of Management Agents that cannot be upgraded because the Management Agent software is not available. The associated, target-specific management plug-in software might be available, but the core Management Agent software is not available.
Not Supported - Number of Management Agents that are not supported in the upgraded Enterprise Manager system because Oracle Management Agent 12c has not been released for a particular platform. The targets monitored by those Management Agents can no longer be monitored in the upgraded Enterprise Manager system.
To check the upgradability status of the targets, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, do one of the following:
In the Other Links section, click Targets Upgradability Status.
On the Targets Upgradability Status page, use the search functionality to search and identify the targets that can either be monitored or not monitored in the upgraded Enterprise Manager system.
For example, to list the targets that cannot be monitored in the upgraded Enterprise Manager system, from the Upgrade Status list, select Not Upgradable. Similarly, to list the target that can be monitored, select Upgradable.
In the Preupgrade Steps section, from the table, click Manage Software.
On the Manage Software page, view the Target Upgradability pie chart. The pie chart graphically shows the following information:
Upgradable - Number of targets that can be monitored in the upgraded Enterprise Manager system because the Management Agent software and the associated, target-specific management plug-in software are available.
Missing Agent/Plug-In Software - Number of targets that cannot be monitored in the upgraded Enterprise Manager system because either the Management Agent software is missing or the associated management plug-in software is missing.
Not Supported - Number of targets that cannot be monitored in the upgraded Enterprise Manager system because either Oracle Management Agent 12c has not been released for the platforms on which the targets are running, or the management plug-ins for those targets are not supported in the upgraded Enterprise Manager system.
Plug-In Software Not Certified - Number of targets that cannot be monitored in the upgraded Enterprise Manager system because the management plug-ins for those targets are not certified.
There may be Management Agents that cannot be upgraded due to technical issues such as missing host target, association with multiple host targets, unreachable state, invalid inventory, and so on.
To identify such problematic Management Agents, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Other Links section, click Problematic Agents.
On the Problematic Agents page, view the Management Agents that cannot be upgraded.
To search for a particular Management Agent, enter the Management Agent name in the Agent field, and click Search.
To filter the Management Agents based on a particular technical reason, select one of the following reasons from the Reason list, and click Search:
Missing Repository Inventory - Lists the Management Agents that are not registered with the central inventory (oraInventory).
Multiple Host Target - Lists the Management Agents that are either associated with or monitoring more than one host.
Agent Unreachable - Lists the Management Agents that are down.
Host Target Missing - Lists the Management Agents whose hosts are not discovered and monitored in the Enterprise Manager Grid Control console. The Management Agents themselves may be monitored but their hosts may not be monitored for some reason.
Central agent - Lists the central agents (Management Agents installed with the first OMS) that cannot be upgraded for 2-system upgrade.
All - Lists all the Management Agents that have one or more issues listed in the Reason list.
You might have to reconfigure the Management Agents for one of the following reasons:
If the OMS host and port with which you deployed a Management Agent do not match with the OMS host and port with which you deployed the other Management Agents.
You have either deleted one or more targets monitored by this Management Agent, or added new targets to be monitored by this Management Agent. To resolve this issue, reconfigure this Management Agent so that the new configuration can take effect.
The versions of the plug-ins you deployed with this Management Agent are different from the versions of the plug-ins you deployed with the other Management Agents. To resolve this issue, deploy this Management Agent again with the correct plug-in versions.
To identify the Management Agents that need to be reconfigured, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Other Links section, click Agents Needing Reconfiguration.
On the Agents Needing Reconfiguration page, view the Management Agents that need to be reconfigured. The table not only lists the Management Agents but also provides the following reasons for you to reconfigure them.
OMS Host and Port Mismatch
Indicates that the OMS host and port with which you deployed the Management Agent do not match with the OMS host and port with which you deployed the other Management Agents. To resolve this issue, access the Identify Host and Port for New Enterprise Manager System page, correct the OMS host and port, and deploy this Management Agent again.
Targets Deleted or Added
Indicates that you have either deleted one or more targets monitored by this Management Agent, or added new targets to be monitored by this Management Agent. To resolve this issue, reconfigure this Management Agent so that the new configuration can take effect.
Plug-In Version Mismatch
Indicates that the versions of the plug-ins you deployed with this Management Agent are different from the versions of the plug-ins you deployed with the other Management Agents. To resolve this issue, deploy this Management Agent again with the correct plug-in versions.
If the core agent software has not been released for the platforms on which the Management Agents run, then these Management Agents will not be supported in Enterprise Manager 12c. Technically, the target or target monitored by those agents can no longer be monitored in the upgraded Enterprise Manager system.
To identify the Management Agents that are not supported in Enterprise Manager 12c, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Other Links section, click Agents Not Supported in Enterprise Manager 12c.
On the Agents Not Supported in Enterprise Manager 12c page, view the Management Agents that are not supported in Enterprise Manager 12c.
When upgrading Management Agents to Enterprise Manager 12c using the 2-system approach, if agents are installed after Repository Back-Up, then these agents will not be able to migrate to Enterprise Manager 12c system. You will have to push these 12c Management Agents from the 12c system and rediscover these targets.
To identify the Management Agents that are not supported in Enterprise Manager 12c, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Other Links section, click Agents Installed after Repository Back-Up.
On the Agents Installed after Repository Back-Up page, view the Management Agents that are installed after Repository-Back-Up.
A broken target indicates that the deployed Management Agent from the Enterprise Manager 12c system is not in a position to monitor the target that was monitored earlier by the old Management Agent.
To identify the broken targets, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Other Links section, click Broken Targets.
On the Broken Targets page, view the list of broken targets. The table not only lists the broken targets but also provides the reason for the broken target, the type of target, the name of the Agent, the name of the Plug-In, and the Platform.
Note:
Follow these instructions only if you are upgrading using the 2-System upgrade approach. Perform these steps in the Enterprise Manager Grid Control console of the earlier release.To provide information on when you backed up your Oracle Management Repository, follow these steps:
In Grid Control, click Deployments.
On the Deployments page, in the Upgrade section, click Enterprise Manager 12c Upgrade Console.
On the Upgrade Console page, in the Select Upgrade Type section, select 2-System. For information about these upgrade approaches, see Chapter 2.
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 and Repository Upgrade Steps section, from the table, click Provide Repository Backup Details.
On the Provide Repository Backup Details page, provide the date and time when you backed up your Oracle Management Repository.
Note:
Ensure that the backup time you enter is based on the time zone to which your existing Management Repository belongs.If you are noting down the backup time stamp from your clock in a time zone that is different from the time zone of the region where the Management Repository resides, then make sure you change the time stamp to the time zone to which the Management Repository belongs.
For example, to convert the time stamp "1999-12-01 11:00:00" in the America/Newyork time zone to America/LosAngeles time zone, run the following query. The result of this query displays the time in 'America/LosAngeles' time zone.
SELECT FROM_TZ(CAST(TO_DATE('1999-12-01 11:00:00', 'YYYY-MM-DD HH:MI:SS') AS TIMESTAMP), 'America/New_York') AT TIME ZONE 'America/Los_Angeles' "West Coast Time" FROM DUAL;
Click Save.