Oracle® Enterprise Manager Grid Control Installation and Configuration Guide 10g Release 5 (10.2.0.5.0) Part Number E10953-15 |
|
|
PDF · Mobi · ePub |
You can install Enterprise Manager Grid Control (Grid Control) in silent mode, that is, without using the GUI-based screens. In silent mode, a response file provides the necessary installation information, typically answered by you, using stored values.
This chapter describes how you can install Grid Control in silent mode. In particular, this chapter covers the following:
Using Silent Mode to Install Enterprise Manager Grid Control Using a New Database
Using Silent Mode to Install Enterprise Manager Grid Control Using an Existing Database
Note:
You do not need to set the DISPLAY environment variable for silent installations using Oracle Universal Installer.The following lists the response files available for each installation type. You will find these response files in the <DVD>/response
directory of the DVD-ROM.
Table 9-1 Available Response Files for Silent Installation
Installation Option | Response File |
---|---|
Enterprise Manager 10g Grid Control Using a New Database |
em_with_new_db.rsp |
Enterprise Manager 10g Grid Control Using an Existing Database |
em_using_existing_db.rsp |
Additional Management Service |
additional_mgmt_service.rsp |
Run the response files in the following way:
For UNIX Platforms
./runInstaller -silent -responseFile=<absolute path of the response file> -waitforcompletion
For Microsoft Windows Platforms
./setup.exe -silent -responseFile <absolute path of the response file>
The silent installation on a UNIX environment can bee seen as a three-step process:
noconfig
: In the first step, you must run the -noconfig
option. This will copy all the bits into the corresponding Oracle homes.
allroot.sh/orainstRoot.sh
: After the bits are copied, the installer will prompt you to run the allroot.sh
script (and orainstRoot.sh
) or root.sh
script (depending on. installation type).
Run the orainstRoot.sh
script if this is the first Oracle product installation on your host.
Run the allroot.sh
script from the first Oracle home that was created during installation.
runconfig.sh
: You must pass this command to run the configuration assistants.
For a Grid Control installation using a new database, run:
<DB_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<database home path> ACTION=configure MODE=perform COMPONENT_XML={encap_emseed.1_0_0_0_0.xml}
For a Grid Control installation using an existing database, run:
<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<OMS Home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}
For an additional OMS installation, run:
<OMS_HOME>/oui/bin/runConfig.sh ORACLE_HOME=<OMS Home> MODE=perform ACTION=configure COMPONENT_XML={encap_oms.1_0_0_0_0.xml}
Note:
If you want to use the-noconfig
option during the silent installation, you must run the runconfig.sh
command at the end of the installation in order to run the configuration assistants.Caution:
When you are using the-noconfig
option in your installation, ensure you also pass -silent
to invoke the installer. The -noconfig
option must be executed only during silent installations.Before you begin the silent installation of Grid Control using a new database, you must meet the prerequisites described in Installing Enterprise Manager Grid Control Using a New Database.
After you meet the prerequisites, follow these steps:
Copy the <DVD>/response/em_with_new_db.rsp
file to a location on the local host.
Modify the following entries in the response file.
Table 9-2 Parameters to Modify in em_with_new_db.rsp File
Parameter | Description |
---|---|
FROM_LOCATION |
Specify the complete path to the products.xml file. For example, FROM_LOCATION = "../stage/products.xml". |
BASEDIR |
Specify the directory where the ORACLE_HOME directories must be created. For example, on Microsoft Windows, BASEDIR = "C:\OHOME1", and on Linux, BASEDIR = "/scratch/OracleHomes". |
INSTALLATION_NAME |
Specify the name to be used for creating the Oracle home directories. For example, INSTALLATION_NAME = "OHOME1". |
s_gdbName |
Specify the global name of the database that houses the repository. For example, s_gdbName="emrep.us.oracle.com". |
s_mountPoint |
Specify the Oradata location where the datafiles are available. For example, s_mountPoint="/scratch/OracleHomes/oradata". |
s_operGroup |
Specify the UNIX group for database operators. For example, s_operGroup="g900", Group names can be obtained by executing groups command at the prompt in UNIX. |
s_adminGroup |
Specify the UNIX group for database administrators. For example, s_adminGroup="g900", Group names can be obtained by executing groups command at the prompt in UNIX. |
s_securePassword |
Specify the registration password for securing the communication between OMS and its Agents. Note: Enterprise Manager implements a password policy requiring passwords to be at least 5 characters long, with at least one number. Passwords must start with a letter. |
s_securePasswordConfirm |
Specify the password again for confirmation. |
b_lockedSelected |
Specify whether the Management Agent communication must be locked. For example, b_lockedSelected=true/false. |
b_passwordsDifferent |
Specify whether different or same password will be used for database administration accounts. |
sl_adminPwds |
Specify different passwords for the database administration accounts - SYS, SYSTEM, SYSMAN, DBSNMP. This is required only when b_passwordsDifferent is set to "true". For example, sl_adminPwds={ "one", "two", "three", "four" }. |
sl_adminPwdsConfirm |
Specify the passwords again for confirmation. |
s_reposPwd |
Specify the password for SYSMAN user account. This is required only when b_passwordsSame is set to "true". This password will be taken for all the accounts. |
s_reposPwdConfirm |
Specify the passwords again for confirmation. |
UNIX_GROUP_NAME |
Specify the UNIX group to be set for the inventory directory. This is valid only for UNIX platforms. For example, UNIX_GROUP_NAME = "install". |
Invoke the runInstaller (setup.exe
on Microsoft Windows) by executing:
<DVD>/<runInstaller or setup.exe> -silent -responseFile <location>/em_with_new_db.rsp
The following message on the root.sh
scripts is displayed (for UNIX only):
WARNING:A new inventory has been created in this session. However, it has not yet been registered as the central inventory of this system.To register the new inventory please run the script '<User's Home Dir>/oraInventory/orainstRoot.sh' with root privileges. If you do not register the inventory, you may not be able to update or patch the products you installed.The following configuration scripts need to be executed as the root user.#!/bin/sh#Root script to run<User's Home Dir>/oraInventory/orainstRoot.sh<Install Location>/db10g/allroot.shTo execute the configuration scripts: 1. Open a terminal window 2. Log in as root 3. Run the scripts 4. Return to this window and click OK to continue
Caution:
If this is the first time an Oracle product is being installed on the machine, the database listener targets will not be discovered, as theroot.sh
scripts have not been executed.After the installation is complete, you must execute orainstRoot.sh
and allroot.sh
scripts as root (UNIX only).
To discover the Grid Control targets, you can execute <Install Location>/agent10g/bin/agentca
, or discover the targets from the Grid Control console. See Invoking the Agent Configuration Assistant in Standalone Mode for more information on executing the Agent Configuration Assistant in standalone mode.
Note:
If the Management Agent does not start up automatically when you restart the host, then do the following:Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.
Before you begin the silent installation of Grid Control using an existing database, you must:
Set the initialization parameters correctly for your qualified existing Enterprise Edition database to be able to run a Management Repository. You should also set all fixed parameters for your Management Repository database. For more information about managing initialization parameters, see Check Database Initialization Parameters. Also see the chapter "Managing Initialization Parameters Using a Server Parameter File" of the Oracle Database Administrator's Guide.
Meet the prerequisites mentioned in Installing Enterprise Manager Grid Control Using an Existing Database.
After you set the initialization parameters and meet the prerequisites, follow these steps:
Copy the <DVD>/response/em_using_existing_db.rsp
file to a location on your local host.
Modify the following entries in the response file.
Table 9-3 Parameters to Modify in em_using_existing_db.rsp File
Parameter | Description |
---|---|
FROM_LOCATION |
Specify the complete path to the products.xml file. For example, FROM_LOCATION = "../oms/Disk1/stage/products.xml". |
BASEDIR |
Specify the directory where the ORACLE_HOME directories must be created. For example, on Microsoft Windows, BASEDIR = "C:\OHOME1", and on Linux, BASEDIR = "/scratch/OracleHomes". |
INSTALLATION_NAME |
Specify the name to be used for creating the Oracle home directories. For example, INSTALLATION_NAME = "OHOME1". |
s_reposHost |
Specify the name of the host where the database, which houses the Management Repository, is running. For example, s_reposHost="repo.xyz.com". |
s_reposPort |
Specify the port on which the database, which houses the Management Repository, is running. For example, s_reposPort="1521". |
s_reposSID |
Specify the SID or Service name of the database, which houses the Management Repository. For example, s_reposSID="emrep". |
s_reposDBAPwd |
Specify the DBA user account password (SYS user) that must be used for creating the repository schema. |
s_mgmtTbsName |
Specify the full path to the location where the data file for management tablespace (mgmt.dbf) can be stored. For example, s_mgmtTbsName=<Database Oracle home>/oradata/<SID>/mgmt.dbf. |
s_ecmTbsName |
Specify the full path to the location where the data file for configuration data tablespace (mgmt_ecm_depot1_.dbf) can be stored. For example, <Database Oracle home>/oradata/<SID>/mgmt_ecm_depot1.dbf. |
s_securePassword |
Specify the registration password for securing the communication between OMS and its Agents. Note: Enterprise Manager implements a password policy requiring passwords to be at least 5 characters long, with at least one number. Passwords must start with a letter |
s_securePasswordConfirm |
Specify the password again for confirmation. |
b_lockedSelected |
Specify whether the Management Agent communication must be locked. For example, b_lockedSelected=true/false. |
s_reposPwd |
Specify password for repository schema owner. |
s_reposPwdConfirm |
Specify the passwords again for confirmation. |
Invoke the runInstaller (setup.exe
on Microsoft Windows) by executing:
<DVD>/<runInstaller or setup.exe> -silent -responseFile <location>/em_using_existing_db.rsp
The following message on the root.sh scripts
appears (for UNIX only):
WARNING:A new inventory has been created in this session. However, it has not yet been registered as the central inventory of this system.To register the new inventory please run the script '<User's Home Dir>/oraInventory/orainstRoot.sh' with root privileges. If you do not register the inventory, you may not be able to update or patch the products you installed.The following configuration scripts need to be executed as the root user.#!/bin/sh#Root script to run<User's Home Dir>/oraInventory/orainstRoot.sh<Install Location>/oms10g/allroot.shTo execute the configuration scripts: 1. Open a terminal window 2. Log in as root 3. Run the scripts 4. Return to this window and click OK to continue
Note:
If the Management Agent does not start up automatically when you restart the host, then do the following:Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.
Before you begin the silent installation of an additional OMS, you must meet the prerequisites described in Installing an Additional Management Service.
After you meet the prerequisites, follow these steps:
Copy the <DVD>/response/additional_mgmt_service.rsp
file to a location on your local host.
Modify the following entries in the response file.
Table 9-4 Parameters to Modify in additional_mgmt_service.rsp File
Parameter | Description |
---|---|
FROM_LOCATION |
Specify the complete path to the products.xml file. For example, FROM_LOCATION = "../oms/Disk1/stage/products.xml". |
BASEDIR |
Specify the directory where the ORACLE_HOME directories must be created. For example, on Microsoft Windows, BASEDIR = "C:\OHOME1", and on Linux, BASEDIR = "/scratch/OracleHomes". |
INSTALLATION_NAME |
Specify the name to be used for creating the Oracle home directories. For example, INSTALLATION_NAME = "OHOME1". |
s_reposHost |
Specify the name of the host where the database, which houses the Management Repository, is running. For example, s_reposHost="repo.xyz.com". |
s_reposPort |
Specify the port on which the database, which houses the Management Repository, is running. For example, s_reposPort="1521". |
s_reposSID |
Specify the SID or Service name of the database, which houses the Management Repository. For example, s_reposSID="emrep". |
s_reposPwd |
Specify password for repository schema owner. |
b_lockedSelected |
Specify whether the Management Agent communication must be locked. For example, b_lockedSelected=true/false. |
s_securePassword |
Specify the registration password for securing the communication between OMS and its Agents. Note: Enterprise Manager implements a password policy requiring passwords to be at least 5 characters long, with at least one number. Passwords must start with a letter |
s_securePasswordConfirm |
Specify the password again for confirmation. |
Invoke the runInstaller
(setup.exe
on Microsoft Windows) by executing:
<DVD>/<runInstaller or setup.exe> -silent -responseFile <location>/additional_mgmt_service.rsp
The following message on the root.sh scripts
is displayed (for UNIX only):
WARNING:A new inventory has been created in this session. However, it has not yet been registered as the central inventory of this system.To register the new inventory please run the script '<User's Home Dir>/oraInventory/orainstRoot.sh' with root privileges. If you do not register the inventory, you may not be able to update or patch the products you installed.The following configuration scripts need to be executed as the root user.#!/bin/sh#Root script to run<User's Home Dir>/oraInventory/orainstRoot.sh<Install Location>/oms10g/allroot.shTo execute the configuration scripts: 1. Open a terminal window 2. Log in as root 3. Run the scripts 4. Return to this window and click OK to continue
Note:
If the Management Agent does not start up automatically when you restart the host, then do the following:Open the agentstup file from the Oracle home of the Management Agent:
$ORACLE_HOME/install/unix/scripts/agentstup
Edit the file to replace executingUser=$USER with executingUser=`id -un`. Then, save and exit the file.
Run the root.sh script from the Oracle home of the Management Agent:
$<ORACLE_HOME>/root.sh
Restart the Management Agent by running the following command from the Oracle home of the Management Agent:
$<ORACLE_HOME>/bin/emctl start agent
This is a one-time action to be taken. Step (1) to Step (3) will ensure that the Management Agent starts up automatically every time you restart the host in the future.