11 Upgrading Enterprise Manager Grid Control

Shut Down Enterprise Manager Before Upgrade

You must ensure that the existing Enterprise Manager processes are shut down before starting the upgrade process.

To shut down Enterprise Manager, execute the following commands:

<OMS Oracle_Home>/opmn/bin/opmnctl stopall
<AGENT_HOME>/bin/emctl stop agent
<OMS Oracle_Home>/bin/emctl stop em

These commands usually successfully shut down all Enterprise Manager processes that are running. However, there may be instances where some processes might still be left running. Such instances may cause the upgrade to fail. To avoid this, you must ensure the following processes are not running before attempting to start the upgrade process:

• OPMN

• DCM

Check for Symbolic Links

The <Oracle_Home>/Apache/<component> configuration files must be examined to ensure only hard links (and no symbolic links) were referenced.

As part of the Enterprise Manager 10g Release 2 (10.2) Upgrade from 10.1, the underlying Oracle9iAS release 9.0.4 stack is also upgraded. During this phase, the upgrade utility attempts to replace the 10g Release 1 Oracle home path that is referenced in these configuration files with the new Enterprise Manager 10g Release 2 ORACLE_HOME path.

If you have customized the Oracle9iAS release 9.0.4 stack using symbolic links to the Oracle home, then the configuration files may also contain these references as symbolic links, instead of the complete path of the Oracle home.

For example, <Oracle_Home>/Apache/modplsql/conf/plsq.conf contains references to the plsql_module. If this path is a symbolic link, you must modify this path to be a hard link.

Customizations and User Permissions

If there have been any middle-tier customizations files that cannot be accessed using the upgrade user's credentials, ensure such customizations are removed or commented out before starting the upgrade. You can reapply these customizations after the upgrade is successfully completed.

Also ensure you (use performing the upgrade) have read and write permissions on /temp/em.

Recompile EMD_MAINTENANCE for Manually Upgraded Databases

If you have previously upgraded the database (from 9i to 10g) manually, you must recompile the EMD_MAINTENANCE package. To do this:

1. Shut down the Management Service that is associated with the database.

2. Execute SQLPLUS into the upgraded database as SYSMAN.

3. Execute alter package EMD_MAINTENANCE COMPILE BODY; ensure this package has been recompiled successfully.

4. Now, start the management Service.

Verify Inventory.xml for Oracle Home Path

Ensure the <Oracle_Inventory>/ContentsXML/inventory.xml file to make sure the Oracle home path is the same as the components that you are upgrading.

Select an Agent that Is Not Secure

During the upgrade process, you can choose not to specify the Agent Registration password. This leaves the upgraded agent unsecure. The installer displays an error message when the agent's REPOSITORY_URL does not match with that of the OMS, indicating the agent is not bound to the Management Service.

This can happen if multiple OMSs are grouped together through a load balancer, and the agent is using this load balancer to communicate with the Management Service.You can also choose to secure the upgraded agent manually after the agent has been upgraded.

Shut Down Database Listener (UNIX Only)

If the current Enterprise Manger installation (10g Release 1) was performed using a new database, the 10g Release 2 (10.2) upgrade process will first attempt to upgrade Oracle Database if it has not already been upgraded manually.

In an Enterprise Manager Grid Control 10g Release 1 (10.1) installation using a new database, the installer performs a release 9.0.1.5 Oracle Database installation along with the other Enterprise Manager components. When you upgrade Enterprise Manager release 10.1 to release 10.2, the database instance is upgraded to a release 10.1.0.4 before the Enterprise Manager migration configuration is performed.

To successfully migrate your existing Enterprise Manager to release 10.2, the new 10.1.0.4 database listener has to be started. To do this, you must simply stop the old (release 9.0.1.5) database listener just prior to executing the allRoot.sh script.

After you stop the old listener and execute the allRoot.sh script, the release 10.1.0.4 listener will be started automatically.

Tasks to be Performed Before Upgrading from 10.1.0.4 to 10.2.0.1 or 10.2.0.2

The following steps outline the pre-upgrade tasks for manual upgrade from Enterprise Manager 10.1.0.4 or higher to Enterprise Manager 10.2.0.1 (Linux) or 10.2.0.2 (Windows) or higher in addition to the tasks mentioned above.

1. Ensure that there is a successful database backup for 24 hours before performing upgrade.

2. Shutdown all OPMN processes and agents.

3. Perform Enterprise Manager partition cleanup. To do this, log into the database using SQLPLUS with SYSMAN credentials. At the SQL> prompt, execute the following command:

   SQL>exec emd_maintenance.partition_maintenance;
   
   

4. Apply fix for index/constraint issues. To do this, log into the database using SQLPLUS with SYSMAN credentials. At the SQL> prompt, execute the following commands:

   SQL>Alter table MGMT_JOB_TYPE_INFO disable constraint PK_JOB_TYPE_INFO cascade drop index;
   SQL>Alter table MGMT_JOB_PARAMETER disable constraint PK_MGMT_JOB_PARAM cascade drop index;
   SQL>Alter table MGMT_TARGET_PROP_DEFS  disable constraint MGMT_TARGET_PROP_DEFS_PK cascade drop index;
   SQL> Alter table mgmt_license_definitions  disable constraint mgmt_license_definitions_pk cascade drop index;
   SQL> ALTER TABLE mgmt_annotation DISABLE CONSTRAINT mgmt_annotation_pk cascade drop index;
   
   

5. Check and enable the queue MGMT_NOTIFY_Q if it is not enabled. To do this, log into the database using SQLPLUS with SYSMAN credentials. At the SQL> prompt, execute the following commands:

   SQL> select OWNER, NAME, ENQUEUE_ENABLED from dba_queues where name='MGMT_NOTIFY_Q';
   If ENQUENE_ENABLED is NOT ÒYESÓ, then
   exec dbms_aqadm.start_queue(queue_name => 'SYSMAN.MGMT_NOTIFY_Q');
   

Tasks to be Performed For Upgrading from 10.1.0.4 to 10.2.0.1 or 10.2.0.2

To upgrade from Enterprise Manager 10.1.0.4 or higher to Enterprise Manager 10.2.0.1 (Linux) or 10.2.0.2 (Windows) or higher, do the following:

1. Using the shiphome, invoke OUI with -noconfig option as follows:

   ./runInstaller -noconfig
   
   

2. When prompted for upgrade options, choose both Oracle Management Service and Agent for upgrade. Enter valid input values for the installation. OUI will perform a software only install.

3. After the software only install, replace $ORACLE_HOME/sysman/admin/emdrep/sql/core/v102020/pre_post_creation.sql with /net/stadv48/scratch/BUG566424/10.2.0.1/pre_post_creation.sql.

4. Execute the command to launch the Configuration tool to complete the upgrade. If the older Oracle Management Service was a "No seed or additional Oracle Management Service" installation, run the following command:

   $NEW_OMS_HOME/oui/bin/runConfig.sh ORACLE_HOME=<OMS HOME> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}
   
   

   If the older Oracle Management Service was a seed installation, run the following command:

   $NEW_OMS_HOME/oui/bin/runConfig.sh ORACLE_HOME=<OMS HOME> MODE=perform ACTION=configure COMPONENT_XML={encap_emseed.1_0_0_0_0.xml}
   

Tasks to be Performed Before Upgrading from 10.2.0.1 to 10.2.0.2 or 10.2.0.3.0

To upgrade from Enterprise Manager 10.2.0.1 or 10.2.0.2 to Enterprise Manager 10.2.0.2 or 10.2.0.3.0 respectively, the following manual tasks need to performed before the upgrade:

1. Using the Oracle Management Service patchset, invoke OUI with -noconfig option as follows:

   ./runInstaller -noconfig
   
   

   OUI will perform a software only install.

2. After the software only install, replace $ORACLE_HOME/sysman/admin/emdrep/sql/core/10.2.0.2/pre_data_upgrade.sql with /net/stadv48/scratch/BUG566424/10.2.0.2/pre_data_upgrade.sql.

3. Execute the command to launch the Configuration tool to complete the upgrade as follows:

   OMS_HOME/oui/bin/runConfig.sh ORACLE_HOME=<OMS_HOME> ACTION=patchsetConfigure MODE=perform RERUN=true COMPONENT_XML={oracle.sysman.top.oms.10_2_0_2_0.xml}
   

Tasks to be Performed For Upgrading from 10.2.0.1 to 10.2.0.2 or 10.2.0.3.0

For upgrading from Enterprise Manager 10.2.0.1 to 10.2.0.2 or 10.2.0.3.0 using OUI, follow the steps outlined in Chapter11, "Enterprise Manager Upgrade Using Oracle Universal Installer".

Upgrading Oracle Management Service that Is Installed Using a New Database

If the Enterprise Manager 10g Release 1 (10.1) was of this installation type, then the 10g Release 2 (10.2) installer performs an out-of-place upgrade of the release 10.1 Management Service (OMS), the repository database, and the agent Oracle homes. During the upgrade, the installer creates a new Oracle home for the management Service, Repository Database, and Management Agent. The upgrade assistants upgrade the datafiles and SYSMAN schema, and then configure the new Oracle homes.

Upgrading Management Service that Is Installed Using an Existing Database

If the earlier Enterprise Manager installation was done using an existing database, the 10g Release 2 installer automatically checks the remote database version (must be release 9.2.0.6 or later). If the minimum database version requirement is met, the installer not only performs an upgrade of the Management Service but also upgrades the SYSMAN schema in the remote database.

Upgrading the Oracle Management Service

If the previous Enterprise Manager installation was for an additional Management Service, the 10g Release 2 installer checks the remote database (must be release 9.2.0.6 or later). If this minimum database release requirement is met, the installer performs the Management upgrade.

If you are upgrading only the Management Service to 10g Release 2 (10.2) without upgrading the monitoring agent (agent associated with that Management Service), you may encounter a metric collection error. To resolve this issue, you must upgrade the monitoring agent to 10g Release 2 as well.

Oracle recommends upgrading the Management Service and the associated (monitoring) agent at the same time.

Upgrading the Management Agent

All agent Oracle homes that need to be upgraded are detected and displayed in the Select Install or Upgrade screen of the installer. You can select the agent Oracle homes that you want to upgrade and proceed with the process.

Enterprise Manager Upgrade Using Oracle Universal Installer

Follow these steps to perform an Enterprise Manager upgrade.

1. Start Oracle Universal Installer by running the runInstaller script in Linux (go to the top-level folder in the contents copied from the DVD and execute ./runInstaller or setup.exe on Microsoft Windows) from the top directory of Disk1.

2. When you invoke Oracle Universal Installer, you will be presented with two choices:

   1. Perform a New Enterprise Manager Installation

      See Chapter3, "Enterprise Manager Installation Types" for more information.

   2. Products Upgrade

      Select this option to continue with the upgrade process.

3. Click Products Upgrade. The Select Install or Upgrade screen appears.

   Figure 11-1 Select Install or Upgrade

   
   

4. The installer automatically detects the Grid Control components that require an upgrade and lists them in this screen.

5. Here, you can choose to perform the following upgrades:

   1. Management Service and the associated (monitoring) Management Agent

   2. Only the Management Service

   3. Only the Management Agent

      Caution:

      If you are upgrading both Management Service and Agent (which is part of a chain agent installation), ensure the agent you have selected is the one that is communicating with selected Management Service.

      Also, ensure you shut down the agent and the Management Service that you are going to upgrade, before starting the process.

6. Select the Oracle homes that you want to upgrade and click Next. The Specify Installation Location screen appears.

   Figure 11-2 Specify Installation Location

   
   

   Here, specify a parent directory (base directory), for example, /scratch/OracleHomes, for the new installation. because the installer is going to perform an out-of-place^Foot 2  upgrade, all the Oracle homes created during the upgrade will be placed as subdirectories under this parent directory.

7. Click Next. The Product-Specific Prerequisite Checks screen appears.

   Figure 11-3 Product-Specific Prerequisite Checks

   
   

   1. At this point, the installer runs some prerequisite checks to verify whether or not the environment meets the minimum requirements for a successful Enterprise Manager installation.

      Early detection of problems with the system setup reduces the chances of you encountering problems during installation; for instance, problems with insufficient disk space, missing patches, inappropriate hardware, and so on.

      This page displays the check name, type, and status for all prerequisite checks designed for the installation. Automatic checks are run first, followed by optional and manual checks.

      Depending on the status of the automatic checks, you must verify all warning and manual checks. At some point, if you have stopped the prerequisite check and want to rerun these checks, select the checks that you want to rerun and click Retry. As each check runs, a progress bar is shown, and test details (expected results, actual results, error messages, instructions) are displayed in the details section, at the bottom of the page.

   2. To stop all prerequisite checks, click Stop. At any point of time, click a prerequisite check to view its corresponding details, including the recommended user actions.

      Note:

      You must manually verify and confirm all checks that were flagged with a warning, skipped (stopped by user), or failed.

   3. To continue with the installation without retrying, click Next.

8. The Specify Configuration screen appears.

   Figure 11-4 Specify Configuration

   
   

   1. Here, you must specify the existing Database and Secure Management Service passwords. The Database Password (SYS) is required to access the configuration files of the existing database repository that is associated with the Management Service that you have selected for upgrade.

   2. In the Database password section, specify the SYS Password (the default super administrator account) for the existing database repository that is associated with the selected Management Service.

   3. In the Management Service Security section, specify a password that will be used to secure the communications between the Management Service and its agents.

      Note:

      Management Service Security: This section is enabled only when the existing Management Service that you are upgrading is not secure.

9. Click Next. If you are upgrading both Management Service and Agent, but only the existing Management Service is secure and locked, then the Agent Registration Password screen appears. Here, you must provide the correct password to enable communications between the secure Management Service and the agent that you are upgrading.

   Figure 11-5 Specify Agent Registration Password

   
   

   Note:

   This screen appears only if the base (existing) agent installation is not secure.

   Caution:

   If you do not know the password and choose to leave the Password field blank, you must do the following after installation, to enable secure communication between the agent and Management Service:

   1. Find out the correct password for the secure Management Service environment. If you do not know the password, obtain it from the user who configured the Management Service for SSL.

   2. In the Agent's <ORACLE_HOME>/bin directory, execute the following command:

      <AGENT_HOME>/bin/emctl secure agent -reg_passwd <password>
      
      

      The <passwd> argument must be replaced with the Agent Registration Password.

10. The Summary screen appears. This screen displays all the Oracle homes that will be created. Depending on the type of upgrade you have selected, this page will display any of the following details:

    • Global Settings

    • Product Languages

    • Space Requirements

    • New Installations

11. Verify the choices that you have made, and click Install to start the upgrade.

<New_OracleHome>/cfgtoollogs/cfgfw/oracle.sysman.top.oms_#date.log

<New_OracleHome>/cfgtoollogs/cfgfw/oracle.sysman.top.oms_#date.log

$ORACLE_HOME/sysman/log/emrepmgr.log.<pid>

Upgrading Management Agent Using the Agent Deploy Application

Agent Deploy is a J2EE application that is used for mass deployment of Management Agents.

The Upgrade Agent option in this application will help you upgrade an existing Management Agent installation to a release 10.2 Management Agent.

Accessing the Agent Deploy Application

To access the Agent Deploy application, follow these steps:

1. Log in to the Grid Control console and go to the Deployments page.

2. Click Install Agent under the Agent Installation section.

3. In the Agent Deploy Application home page that appears, select the appropriate installation option that you want to perform.

To upgrade the Management Agent using Agent Deploy, follow the instructions documented below:

1. On the Agent Deploy application home page, click Upgrade Agent to perform the Management Agent upgrade.

2. The Agent Upgrade: Installation Details page appears.

3. In the Source Agent Information section, specify the full path to an existing agent Oracle home location. This source agent installation will be used to perform the upgrade.

   Note:

   The path of the source agent should be the same on all the remote hosts.

   Figure 11-6 Source Agent Information Section of the Installation Details Screen

   
   

4. In the Version section of this page, select the appropriate version of the agent software that you want to use for upgrade.

   Note:

   The values in this list will depend on the staged software that are available on the Management Service host.

   Figure 11-7 Version Section of the Installation Details Screen

   
   

5. In the Hosts section, do the following:

   Figure 11-8 Hosts Section of the Installation Details Screen

   
   

   1. Select the appropriate platform on which you want to perform this installation.

   2. In the Provide Host List text box, specify all the hosts (host names or IP addresses) on which you want to perform the Agent installation. Alternatively, click Get Host Names From File to browse and select the file that contains a list of all the required host names.

      WARNING:

      Do not specify duplicate entries of the host list. If there are duplicate host entries in this list, the application hangs.

      Use the same host names for which the SSH has been set.

      Note:

      You can use either a comma (,), white space, or a new line as a separator when specifying multiple hosts.

      Caution:

      The Agent Deploy application picks up only the values in the first column of the Host List file that you specify or select.

      Ensure the host list format is appropriate, since the Agent Deploy application does not validate this format on the selected file.

      A sample host list format is provided in Table 11-2.

      Table 11-2 Sample Host List Format

      Fully Qualified Host name	Host name	Host IP Address
      host1.foo.com	host1	154.87.3.229
      host2.foo.com	host2	154.87.3.109
      host3.foo.com	host3	154.80.5.218

      
      

   3. Select Cluster Upgrade if you want to upgrade the Management Agent cluster.

      Note:

      The hosts that you specify must belong to the same cluster. Also, note that only the hosts that you specify here will be upgraded, irrespective of the number of hosts in that cluster. For example, if there are 10 hosts in a cluster and you specify only 5 here, Agent Deploy will upgrade only those five hosts in the cluster that you have specified.

6. In the OS Credential section, specify the appropriate operating system user credentials. Select Run root.sh (UNIX platforms only) if you want Agent Deploy to execute this script. Agent Deploy will use sudo to run this script. You must specify the invoking user's password here. You must also ensure that the targetpw variable is not set in the /etc/sudoers file.

   Figure 11-9 OS Credential Section of the Installation Details Screen (UNIX Only)

   
   

7. In the Destination section, specify the absolute path for the Installation Base Directory. This directory will be created on all the specified hosts, and the Agent Oracle home directory will be created as a subdirectory under this directory.

   Figure 11-10 Destination Section of the Installation Details Page

   
   

8. In the Additional Parameters text box, specify any additional parameters that you want to pass during installation.

   Figure 11-11 Additional Parameters Section of the Installation Details Page

   
   

9. In the Additional Scripts section, specify any preinstallation and postinstallation scripts that you want to execute.

10. Click Continue to start the installation process.

Click Help, in the Agent Deploy application for more information.

Upgrading Management Agent Using agentDownload Script

To upgrade Management Agent using the agentDownload Script, follow the instructions documented below:

1. Invoke the agendDownload script using -u option.

   The OLD_ORACLE_HOME that you want to upgrade should be specified either by passing the -o option, or setting the OLD_ORACLE_HOME environment variable.

   Invoke the agentdownload script using the following command:

   ./agentDownload.linux -u -o <OLD_ORACLE_HOME_PATH>
   
   

   For Microsoft Windows, invoke the agentDownload script using the following command:

   ./agentDownload.vbs -u -o <OLD_ORACLE_HOME_PATH>
   

   Note:

   The first two options (-u and -o) are mandatory. The -b option can be skipped if this has already been specified in the response files.

2. To construct the new Oracle home name, either pass the -b option, or specify these values for BASEDIR in the agent_download.rsp file.

   Note:

   You can specify these options in the command-line even though they are present in the response file. The command-line options will have a higher precedence over the ones in response file.

3. If the base agent that you are upgrading is not secure, the script will prompt you to specify the Agent Registration Password.

You can use the options listed in Table 11-4 to execute the agentDownload script.

General System Installation Requirements for Real Application Clusters

Each node that is going to be part of your Oracle Real Application Clusters (Oracle RAC) installation must meet the following hardware and software requirements. You will perform step-by-step tasks for hardware and software verification for the platform-specific preinstallation procedures.

emctl resetTZ agent