This chapter describes how you can use silent mode to upgrade Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher to Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0), and how you can upgrade Oracle Management Service 10g Release 4 (10.2.0.4.0) to Oracle Management Service 11g Release 1 (11.1.0.1.0).
In particular, this chapter covers the following:
Note:
If Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher has add-ons installed, then do NOT follow the instructions outlined in this chapter. Instead, follow the instructions outlined for upgrading Enterprise Manager Grid Control with add-ons installed in Part V, "Upgrading Enterprise Manager System".And if you want to upgrade standalone Management Agents, then see the upgrade chapters described in Part VI, "Upgrading Oracle Management Agent".
Note:
If you have Enterprise Manager 10g Grid Control Release 1 (10.1) or Enterprise Manager 10g Grid Control Release 3 (10.2.0.3) or lower, then you must first upgrade or patch them to Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, before upgrading them directly to Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0). For information about upgrading or patching them to Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, see My Oracle Support note 1076420.1.After upgrading or patching them to Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, follow the instructions outlined in this chapter to upgrade them to Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0).
You can upgrade an existing Enterprise Manager Grid Control or Oracle Management Service (OMS) in silent mode using the response file upgrade.rsp
. Using the response file is only an alternative to using the GUI-rich screens offered by the installer to upgrade a previous release of Enterprise Manager Grid Control. The response file captures all the required information that the installer captures, and performs exactly the same function as the installer. This is an out-of-place upgrade where the Oracle homes of the previous release are left intact and new Oracle homes for 11g Release 1 are created.
The following are the functions performed by the response file:
Upgrades Oracle Management Service 10g Release 4 (10.2.0.4.0) or higher
Upgrades Oracle Management Agent 10g Release 4 (10.2.0.4.0) or higher that was installed by default with Oracle Management Service 10g Release 4 (10.2.0.4.0)
Installs Oracle Web Tier 11g Release 1
Note:
If you have multiple OMSes connecting to one Management Repository, stop all the OMSes and upgrade the first OMS using the installer. When you upgrade the first OMS, the installer also upgrades the Management Repository, and since the other OMSes connect to the same Management Repository, they must also be stopped.Stopping the Management Agents is not mandatory, and as a result, there may be an increase in the number of Agent-related log files. However, this is harmless and can be ignored.
Once that OMS is upgraded, invoke the installer again, and select and upgrade all other OMSes, which connect to the same Management Repository, so that they are upgraded simultaneously. Ensure that Oracle WebLogic Server 10.3.2 (Oracle Fusion Middleware 11g Release 1 Patch Set 1) is installed on every host where the OMS is being upgraded. For information on installing Oracle WebLogic Server, see My Oracle Support note 1063762.1.
This upgrade process does NOT do the following:
Does NOT upgrade Oracle Management Agent 10g Release 4 (10.2.0.4.0) or higher that was NOT installed by default with Oracle Management Service 10g Release 4 (10.2.0.4.0).
To upgrade such Management Agents, use the Agent Upgrade Wizard available in the Grid Control console.
Does NOT upgrade your existing Oracle Database where the Management Repository is configured.
To upgrade such databases, use the database upgrade tool. For more information, on the upgrade tool, see the Oracle Database Upgrade Guide available at:
http://www.oracle.com/technology/documentation/database.html
If you are upgrading the installation type Enterprise Manager Grid Control Using a New Database or Enterprise Manager Grid Control Using an Existing Database of 10g Release 4 (10.2.0.4) or higher, then before you begin, keep in mind the points described in Before You Begin.
If you are upgrading the installation type Additional Oracle Management Service of 10g Release 4 (10.2.0.4) or higher, then meet the prerequisites described in Before You Begin.
Before upgrading to Enterprise Manager 11g in silent mode, ensure that you meet the following prerequisites.
If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.
Table 21-1 Prerequisites for Upgrading to Enterprise Manager 11g in Silent Mode
Requirement | Description | Yes/No |
---|---|---|
Basic Prerequisites |
The basic prerequisites for upgrading Enterprise Manager Grid Control depend on the installation type that is being upgraded.
|
|
Existing Management Repository |
Ensure that the existing, certified Oracle Database already has a Management Repository configured, and that the Management Repository is compatible with Oracle Management Service 11g Release 1 (11.1). For more information, refer to My Oracle Support note 412431.1. |
|
Ensure that you back up the existing, certified Oracle Database (which houses the Management Repository), the Oracle home of the OMS, the Oracle home of the Management Agent (which was installed along with the OMS), and the Oracle Inventory directory. This helps you maintain a copy of the database, the Oracle home, and the inventory details that were existing before the environment was upgraded, and it naturally offers the scope to revert to it whenever you want. |
||
Ensure that the existing Oracle Database, which houses the Management Repository, has the Partitioning Option enabled (therefore, ensure that you install it into Oracle Database Enterprise Edition.) To verify this, connect to the database as SYSDBA and run the following query:
The result of this query should be |
||
If the Enterprise Manager system that you are about to upgrade was shut down for a long period of time, then you will not have partitions created in the existing, certified Oracle Database, which houses the Management Repository, to load new data. Therefore, under such circumstances, do the following:
|
||
Database and Listener Status Requirements |
Ensure that the existing, certified Oracle Database and its listener are running. |
|
Valid Objects Requirements |
Ensure that you do have only valid SYSMAN and SYS objects in the existing, certified Oracle Database.
|
|
DBMS Jobs and DBMS Scheduler Status Requirements |
Ensure that your stop the DBMS Jobs and the DBMS scheduler in the existing, certified Oracle Database. To do so, log in to the database as SYS:
|
|
Gather Statistics Job Status Requirements |
Ensure that you stop the Gather Statistics job that is running in the existing, certified Oracle Database. To do so, log in to the database as SYS and run the following commands: For Oracle Database 10g (10.2.0.4) or higher
For Oracle Database 11g (11.1.0.7) or higher
|
|
User Privilege Requirements |
Ensure that SYSMAN and DBSNMP users have SQL> CONNECT AS SYS; SQL> SELECT grantee, grantor, owner, table_name FROM DBA_TAB_PRIVS WHERE table_name = 'DBMS_RANDOM' AND privilege = 'EXECUTE' AND grantee IN ( SELECT DISTINCT granted_role FROM DBA_ROLE_PRIVS START WITH grantee = '<user_account_name>' CONNECT BY PRIOR granted_role=grantee UNION ALL SELECT '<user_account_name>' FROM dual WHERE ROWNUM = 1 UNION ALL SELECT 'PUBLIC' FROM dual WHERE ROWNUM = 1 ) If these users do not have
|
|
Environment Variable Setting Requirements |
Ensure that the environment variable ORACLE_HOME is set to the Oracle home of the OMS. For example, in Cshell, set it in the following way:
For example, in bash shell, set it in the following way:
|
|
OMS and Grid Control Process Status Requirements |
Ensure that you shut down all the running processes (OPMN, DCM, and so on) and also all the OMSes, which are connecting to the same Management Repository. To do so, follow these steps:
|
|
Customization File Requirements |
If there are any middle-tier customizations files that cannot be accessed using the credentials of the user account that is used for the upgrade process, then ensure that such customizations are removed or commented out. You can reapply these customizations after the upgrade is successfully completed. |
|
Oracle Home Path Requirements |
In the following file, ensure that the Oracle home path is the same as the component you are upgrading. The path must be a hardlink.
|
|
SUDO Configuration Requirements |
Ensure that you configure SUDO in your environment. If you are unable to do so or if you have already upgraded any of the core components (OMS or Management Agent) without configuring SUDO, then follow the workaround described in My Oracle Support note 789363.1. |
|
User-Defined Metric Script Definition Requirement |
If you have any user-defined metric scripts in the Oracle home of a Management Agent that you are upgrading, then ensure that you manually copy all those scripts to another directory outside any Oracle home, and then update the user-defined metric definitions to reflect the new script location. This is because, after the Management Agent is upgraded, the user-defined metric scripts are not automatically copied to the new Oracle home. |
Note:
Besides the prerequisites mentioned in Table 21-1, refer to My Oracle Support note 1073166.1 for information on other upgrade-related known issues, prerequisites, and additional requirements.To upgrade to Enterprise Manager 11g in silent mode, follow these steps:
Copy the following response file to an accessible location on your local host:
<Software_Location>/response/upgrade.rsp
In this command, <Software_Location>
is either <DVD>
or <Software_Downloaded_Location>
.
For example,
/u01/app/response/upgrade.rsp
Edit the response file:
If you are upgrading Enterprise Manager Grid Control, then specify values for the mandatory parameters listed in Table 21-2.
If you are upgrading an additional OMS, then specify values for the mandatory parameters listed in Table 21-3.
Invoke the installer:
./runInstaller -silent -responseFile <absolute_path_location>/upgrade.rsp
Note:
For Microsoft Windows, invoke setup.exe
instead of runInstaller
.
In Microsoft Windows, if the path to the software download location contains a subdirectory name with two or more words and a space between each of the words, then ensure that the parent directory of such a subdirectory does not contain a file whose name matches with the first word of that subdirectory.
For example, if the software is downloaded to C:\Documents and Settings
, then before you invoke setup.exe
, ensure that there are no files titled Documents (for example, shortcut files such as C:\Documents
) in the C:\ drive
.
After the installation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer using the START_OMS=false
and b_startAgent=false arguments
.
However, if you pass the START_OMS=false
argument, the installation does not configure the EMCLI tool, and as a result, none of the EMCLI commands will work. Therefore, after the installation ends, you must manually configure the EMCLI tool in the $<ORACLE_HOME>/bin
directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface available at:
By default, GCDomain
is the default name used for creating the WebLogic Domain.
To override this, invoke the installer using the following command:
./runInstaller WLS_DOMAIN_NAME=<Custom_Domain_Name>
Run the allroot.sh
script from the Oracle home of the OMS (oms11g
):
$<ORACLE_HOME>/allroot.sh
For example, if you are using SUDO to change to a root user, then you will run the following command:
/usr/local/bin/sudo /scratch/OracleHomes/oms11g/allroot.sh
Table 21-2 Response File Parameters for Upgrading Enterprise Manager Grid Control
Parameter | Description |
---|---|
OLD_BASE_DIR |
Specify the full path to the installation base directory where the existing OMS, which has to be upgraded, is installed. |
SECURITY_UPDATES_VIA_MYORACLESUPPORT |
|
DECLINE_SECURITY_UPDATES |
|
ORACLE_MIDDLEWARE_HOME_LOCATION |
Specify the location that was specified while installing Oracle WebLogic Server. For example, For example, if you accept the default location For more information about this location, see What Is Oracle Middleware Home? Note: Ensure that the Middleware Home you specify here is used only for Enterprise Manager Grid Control. Ensure that no other Oracle Fusion Middleware products or components are installed in the same Middleware Home that is designated for Enterprise Manager Grid Control. |
ORACLE_INSTANCE_HOME_LOCATION |
By default, Whether you accept the default directory or specify a custom one, by default, the directory is created under the parent directory of the Oracle Middleware Home. For example, if the Oracle Middleware Home is For more information about this location, see What Is Oracle Management Service Instance Base Location?. |
WLS_ADMIN_SERVER_USERNAME |
Specify the default user name that will be used as the administrative user for the WebLogic Domain. By default, the user name is |
WLS_ADMIN_SERVER_PASSWORD |
Specify the password for the WebLogic user account. |
WLS_ADMIN_SERVER_CONFIRM_PASSWORD |
Confirm the password for the WebLogic user account. |
NODE_MANAGER_PASSWORD |
Specify the node manager password. |
NODE_MANAGER_CONFIRM_PASSWORD |
Confirm the node manager password. |
SYS_PASSWORD |
Specify the password for SYS user account. |
Table 21-3 Response File Parameters for Upgrading Additional Oracle Management Service
Parameter | Description |
---|---|
OLD_BASE_DIR |
Specify the full path to the installation base directory where the existing OMS, which has to be upgraded, is installed. |
SECURITY_UPDATES_VIA_MYORACLESUPPORT |
|
DECLINE_SECURITY_UPDATES |
|
ORACLE_MIDDLEWARE_HOME_LOCATION |
Specify the location that was specified while installing Oracle WebLogic Server. For example, For example, if you accept the default location For more information about this location, see What Is Oracle Middleware Home?. |
ORACLE_INSTANCE_HOME_LOCATION |
Specify the directory where the configuration files of OMS can be created. Ensure that the directory you specify has write permission. By default, this location is under the parent directory of the Oracle Middleware Home. For example, if the Oracle Middleware Home is For more information about this location, see What Is Oracle Management Service Instance Base Location?. |
ADMIN_SERVER_HOSTNAME |
Specify the name of the host where the Admin Server is running. Admin Server is the server that was created when you installed the first Oracle Management Service 11g Release 1. |
ADMIN_SERVER_PORT |
Specify the port on which the Admin Server is running. |
WLS_ADMIN_SERVER_USERNAME |
Specify the user name that will be used as the administrative user for the WebLogic Server Domain. By default, the user name is |
WLS_ADMIN_SERVER_PASSWORD |
Specify the password for the WebLogic user account that was provided during the first Oracle Management Service installation. |
SYS_PASSWORD |
Specify the password for SYS user account. |
After you upgrade, follow these steps:
Start the DBMS Jobs and the DBMS Scheduler. To do so, log in to the database as SYS and perform the following:
Start the DBMS Jobs by setting the job_queue_processes
to the value you recorded while stopping the DBMS Jobs as a prerequisite.
alter system set job_queue_processes=<original_value> scope=both;
Start DBMS Scheduler by running the following command:
execute dbms_scheduler.set_scheduler_attribute ('SCHEDULER_DISABLED','FALSE');
Submit the DBMS jobs by running the following command:
execute emd_maintenance.submit_em_dbms_jobs;
Start the Gather Statistics job in the existing database by running the following as SYS:
For Oracle Database 10g (10.2.0.4) or higher
execute dbms_scheduler.enable('GATHER_STATS_JOB');
For Oracle Database 11g (11.1.0.7) or higher
execute dbms_auto_task_admin.enable('auto optimizer stats collection',null,null);
If you upgraded an additional OMS, then refresh the Oracle WebLogic Server Domain, which hosts the Enterprise Manager application, so that the configuration changes made to the domain as a result of adding an additional OMS are reflected in the Grid Control console. To refresh the Oracle WebLogic Server Domain, follow these steps:
In Enterprise Manager Grid Control, navigate to the Home page for the Oracle WebLogic Server Domain that hosts the Enterprise Manager application. In most cases, the following is the direct URL to the Home page. If your domain name is not GCDomain
, then replace that string with your domain name:
[protocol]://[host]:[port]/em/faces/as/as/domainHome?target=/secFarm_GCDomain/GCDomain&type=weblogic_domain
From the WebLogic Domain menu, click Refresh WebLogic Domain.
On the Refresh WebLogic Domain page, click Continue.
Note:
This submits a WebLogic Domain Refresh job, which captures the domain configuration changes and reflects them in the Enterprise Manager Grid Control console. The job repeats itself once a day, and therefore, if you add any more additional OMSes or remove OMSes from your Enterprise Manager system in the future, this job automatically captures the configuration changes to the Oracle WebLogic Server Domain. You do NOT have to repeat this procedure every time you add an additional OMS.Remove Oracle Application Server-related targets such as Oracle Application Server, Oracle HTTP Server, OC4J, and Oracle Web Cache from the Management Repository.
In particular, remove <OLD_OMS_NAME>
, <OLD_OMS_NAME>_home
, <OLD_OMS_NAME>_OC4J_EM
, <OLD_OMS_NAME>_OC4J_EMPROV
, <OLD_OMS_NAME>_HTTP Server
, and <OLD_OMS_NAME>Web Cache
.
Table 21-4 shows how these targets might appear in Enterprise Manager Grid Control.
Table 21-4 Removing Oracle Application Server Targets
Target Name | Target Type |
---|---|
EnterpriseManager0.hostname.com |
Oracle Application Server |
EnterpriseManager0.hostname.com_home |
OC4J |
EnterpriseManager0.hostname.com_HTTP Server |
Oracle HTTP Server |
EnterpriseManager0.hostname.com_OC4J_EM |
OC4J |
EnterpriseManager0.hostname.com_OC4J_EMPROV |
OC4J |
EnterpriseManager0.hostname.com_Web Cache |
Web Cache |
To remove these targets, log in to Enterprise Manager Grid Control, click All Targets, select for the target, and click Remove.
Discover all new targets such as Scan Listener and so on either using the Enterprise Manager Grid Control console or by running the following command from the Oracle home of the Management Agent where the new targets are running:
$<ORACLE_HOME>/bin/agentca -d
In Enterprise Manager 11g Grid Control, the emoms.properties
file is no longer supported. To view details related to the Management Repository, run the following command:
(Optional) If you want to connect to another Management Repository, then shut down the OMS, run the following command, and then restart the OMS.
emctl config oms -store_repos_details (-repos_host <host> -repos_port <port> -repos_sid <sid> | -repos_conndesc <connect descriptor>) -repos_user <username> [-repos_pwd <pwd>] [-no_check_db]
Note:
On Linux, you need to double escape the connect descriptor using single and double quotes. However, on Microsoft Windows, you need not.For example, on Linux:
emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc '"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb)))"' -repos_user sysman
For example, on Microsoft Windows:
emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb))) -repos_user sysman
(Optional) If you want to discover the newly installed targets, if you want to convert the standalone Management Agent to a cluster-based Management Agent, if you want to discover the targets on the new nodes of the cluster, or if you want to reconfigure the cluster-based Management Agent, you must run the agentca
script to reconfigure and discover all new targets.
For information about the agentca
script, see What Is Agent Configuration Assistant Used For?.
For information about reconfiguring the Management Agent and discovering all new targets, see Appendix I, "Reconfiguring Oracle Management Agent and Discovering New Targets".
(Optional) If you want to enable the Request Monitoring feature for tracing transaction requests in WLS, you need JVM Diagnostics as well as Application Dependency and Performance (ADP) managers and agents configured against the target to be monitored.
For information about installing JVM Diagnostics and enabling the Request Monitoring feature, refer to the Oracle Enterprise Manager Administration Guide.
For information about enabling the ADP feature in Enterprise Manager Grid Control, refer to the Oracle Enterprise Manager Getting Started with Management Pack Plus for SOA.
Both these guides are available at:
Delete the old Oracle homes of OMS (oms10g) and Management Agent (agent10g). Also remove their entries, oms10g and agent10g, from the /etc/oratab
file. However, do NOT delete the Oracle home of the database because it contains the upgrade schemas.