|Oracle® Enterprise Manager Advanced Configuration
10g Release 2 (10.2)
Migrating from an older architecture Enterprise Manager (pre-Oracle Enterprise Manager 10g) to Enterprise Manager version 10.2 is performed in two phases:
This chapter covers phase one, the migration procedure used to move from a previous version of Oracle Enterprise Manager to an Oracle Enterprise Manager 10.1 environment. This chapter covers the following topics:
Migrating your existing Enterprise Manager framework to the Enterprise Manager version 10.1 environment involves two steps:
Making targets within your managed environment monitorable using the 10.1 framework by installing 10.1 Management Agents on hosts that are running your managed targets.
Migrating information about users, privileges, groups, and preferred credentials from the old management repository to the Oracle Enterprise Manager 10.1 Management Repository.
Once you have completed migrating to the 10.1 framework, you may wish to change the default metric thresholds for groups of managed targets within your enterprise. For more information, see Configuring Metric Thresholds.
Before beginning the migration process, ensure that the following list of requirements is satisfied:
The previous version of complete Enterprise Manager Framework (Release 2.2, 9.0.1, or 9.2) must be up and running, including the Enterprise Manager Console, Oracle Management Server, Repository, and Intelligent Agents. The migration procedure uses the Job system in the previous version of Enterprise Manager to deploy the Enterprise Manager 10.1 Management Agents.
The Oracle Enterprise Manager (version 10.1) must be installed and running one network host. Specifically, the 10.1 Management Service must be up and running and available to the 10.1 Management Agents that you will install on your managed hosts.
You must have the credentials for the Enterprise Manager Administrator Account for both the previous version of Enterprise Manager, as well as Enterprise Manager 10.1. Account read/write privileges are required for any machine currently running the Release 2.2, 9.0.1 or 9.2 Intelligent Agent.
You must have the Database User and Password for both the previous version of the Enterprise Manager repository database, as well as the Enterprise Manager 10.1 repository database.
You must have 375 Megabytes of free disk space on each host where a 10.1 Management Agent is to be installed.
You must have installed the latest system and software patches for the Enterprise Manager environment. Note that the system and software patch requirements for the Enterprise Manager 10g are significantly different from previous versions of Enterprise Manager.
Deploying 10.1 Management Agents on machines running targets managed by an older version of Enterprise Manager makes these targets monitorable via Enterprise Manger . To simplify and automate Management Agent deployment, a Tcl script is provided that is submitted as a job from an Enterprise Manager Release 2.2, Release 9.0.1, or Release 9.2 Job system. The deployment script (
agentIntallJob.tcl) can be found in the Enterprise Manager 10.1 home directory at the following location:
Deployment of the 10.1 Management Agent is carried out in two phases:
gentInstallJob.tcl script must be run as a Tcl job from an Enterprise Manager Release 2.2, Release 9.0.1, or Release 9.2 Console. As shown in Figure 11-1, you define the job by choosing a "Node" target type and then selecting the machines on which the 10.1 Management Agents are to be installed.
Figure 11-1 Selecting Machines for Management Agent Deployment
Once you have selected where the Management Agents are to be deployed, you need to define an installation task using
agentInstallJob.tcl. As shown in Figure 11-2, select the "Run TCL Script" task.
Figure 11-2 Choosing the Run TCL Script Task
The next step involves defining the functional core of the job. As shown in Figure 11-3, you need to copy the content of the
agentInstallJob.tcl script into the text entry area using either the Import function or manually copying and pasting the entire script into the TCL Script text entry area.
Figure 11-3 Copying agentInstallJob.tcl and Specifying Job Parameters
In addition to importing the script content, you must specify operational parameters required by the script to install the 10.1 Management Agent. As shown in Figure 11-3, you enter these parameters in the Run TCL Script Parameters field. The parameters are:
The Oracle Management Service host
HTTP Port Number
Directory Type (-o or -f)
-o Identical installation directory structure on all machines.
-f Different installation directory structure on various machines (specified in text file)
Example 11-1 Same Installation Directory Structure on All Machines
mgmthost1.acme.com 7778 -o /u09/Agent/Agent_41
Example 11-2 Different Installation Directory Structure on Different Machines
mgmthost1.acme.com 7778 -f hostname_lookup.txt
The Directory Type parameter offers two options either "-o" or "-f" plus the Directory Argument which consists of either a default directory (-o option) or host lookup file (-f option). As mentioned in the previous section, the "-o" option specifies that the same Management Agent home directory structure be created on all machines where the Management Agent is to be installed. For example, if the
agentInstallJob.tcl job is submitted against MACHINE1, MACHINE2, and MACHINE3 using the following job parameters,
mgmthost1.acme.com 7778 -o /u09/agent/agent_41
agentInstallJob.tcl script will create the
/u09/agent/agent_41 directory on each of the three machines. Once created, this directory is used by the Oracle Universal Installer (OUI) as an installation staging area. This directory eventually becomes the Oracle Enterprise Manager 10g Management Agent Home.
Note:The agentInstallJob.tcl job runs OUI in silent mode to perform the actual Management Agent installation operations.
The "-f" option specifies that different installation/Agent Home directory structures be created for specific machines. Before creating a TCL job with this option you must first create a flat text file listing each machine name and corresponding directory for that host. The flat file MUST reside in the Oracle Enterprise Manager 10g Management Service Home in the following directory:
In the following example, the lookup file parsed by the TCL job is named hostname_lookup.txt.
When a TCL job is submitted using the "-f" option, the job first obtains the name of the target machine by executing the "hostname" command. The result is then compared against entries in the hostname lookup file. If the hostname is found in the file, the associated directory structure is used. If the hostname is not found, then the directory structure specified for the "wildcard" character is used. The wildcard can be used as a default entry in case the TCL job cannot locate a particular hostname within the file. A wildcard entry is designated by a "*" and must be the last entry as the file is parsed from top to bottom.
Example 11-3 shows the format for a sample hostname lookup file. In the example, you have 20 machines in your enterprise where you want 10.1 Management Agents installed. You want the same Agent Home directory structure created on all machines except HOST1, HOST2, and HOST3.
Example 11-3 Sample Hostname Lookup File
HOST1 /oracle_home1/agent/agent_install HOST2 /ora_host2/agent_install HOST3 /orahome_host3/agent/install * /ora_agent/agent/install
The TCL job (submitted to HOST2) runs the hostname command and receives HOST2 as the output. This output is then cross-referenced with all entries within the hostname_lookup.txt file. Since HOST2 is an entry in the hostname_lookup.txt file, the TCL job knows to create the 10.1 Management Agent Home in
/ora_host2/agent_install. HOST1, HOST2, and HOST3 will have unique directories. The Management Agent home directory for the remaining 17 machines will be
Because the TCL job, or more specifically OUI, creates files and directories on the target machines, full read/write privileges for the Enterprise Manager administrator account running the job are required. When the installation is complete, the new 10.1 Management Agent is started automatically and begins retrieving host, database, and listener information. This information is then uploaded via HTTP or HTTPS to the new Enterprise Manager 10.1 management repository where it becomes available to the Enterprise Manager Grid Control console for viewing.
Once the 10.1 Management Agents are operational, you need to configure each Management Agent for use with the Oracle Enterprise Manager 10.1 Job system. This step consists of running the
root.sh script on each machine where the Management Agent is installed. This script is located in the Management Agent Home of the host machine. Specifically, the root.sh script grants root privileges to the Oracle Enterprise Manager 10g Management Agent. Therefore, the root user and password for that machine are required in order to run root.sh.
As with the agentInstallJob.tcl script you can automate this task by running the
root.sh script using the Enterprise Manager Release 2.2, Release 9.0.1, or Release 9.2 Job system. To do this, you create an "OS command" job that executes "root.sh" on all machines requiring Management Agent configuration. As shown in the Figure 11-4, preferred credentials should be overridden by the root user and password of the target host.
Figure 11-4 Overriding Preferred Credentials
On the job Parameters page (Figure 11-5), specify "root.sh" in the Command field as shown in the following figure and submit the job for execution. You must specify the full path to the root.sh script. For example:
Figure 11-5 Command Parameters
The 10.1 Management Agent can be up and running when
root.sh is executed and does not need to be restarted after the configuration process has been completed.
Note:In previous releases of Enterprise Manager, job system configuration was part of the Intelligent Agent install. With the Enterprise Manager 10g release, this configuration is now a separate step due to architectural differences between the old and new frameworks.
Once the 10.1 Management Agents have been deployed and configured, the next step is to migrate information about users, privileges, groups, and preferred credentials from the oldManagement Repository to the Enterprise Manager 10.1 Management Repository.
Note:Privileges, group membership, and preferred credentials are migrated for databases, listeners, and hosts only.
Both Enterprise Manager 9i and Oracle Enterprise Manager 10g save and encrypt all administrator accounts and preferred credentials in the repository. In order to migrate all of these accounts over to Enterprise Manager 10.1, you must run the Migration Utility from the Enterprise Manager 10.1 home. This command line utility can be found in the following directory:
The Migration Utility requires the repository user and password for both the original Management Repository database and for the new Enterprise Manager 10.1 Management Repository database. You execute the utility and specify operational parameters using the following syntax:
repo_mig -preview|-migrate source_user/source_pwd@source_service dest_user/dest_pwd@dest_service
-preview: Generates a preliminary migration report without carrying out the migration.
-migrate: Performs migration of groups, administrators, target privileges, and preferred credentials of hosts, databases, and listeners.
source_user: Source OEM repository user name
source_pwd: Source OEM repository password
source_service: Source OEM repository service. For example, Host:Port:SID
dest_user: Destination OEM repository user name
dest_pwd: Destination OEM repository password
dest_service: Destination OEM repository service. (Host:Port:SID)
Once the migration is complete, the account information is then saved and encrypted. The passwords on all of the accounts will remain the same.
As mentioned previously, migration only involves transferring users, privileges, groups, and preferred credentials to the Enterprise Manager 10g framework; any older event test thresholds that existed in pre-10g versions of Enterprise Manager will not be transferred.
Enterprise Manger 10g provides out-of-the-box monitoring that simplifies a critical but potentially time-consuming task of setting up monitoring for managed targets. As you add targets to Enterprise Manager, options are automatically provided to monitor the target at a recommended or at a minimum level. Each level of monitoring consists of a set of metrics and predefined thresholds that are based on Oracle recommendations for those levels. You may choose to use these Oracle recommendations, or you can change these thresholds to suit your particular needs.
Your Enterprise Manager Grid Control installation may be monitoring a very large number of targets, making it inconvenient to manually change metric threshold values for each monitored target. Enterprise Manager Grid Control 10.2 provides an easy way to propagate metric thresholds to any number of targets via monitoring templates.
Monitoring templates allow you to define metric settings once and apply these settings to any number of targets of the same type. For more information about monitoring templates, see Enterprise Manager Grid Control online help.