Install Oracle Enterprise Manager Grid Control 10.2.0.4 on Linux AS4.5

一、 概述
     Grid Control网格控制是为整个Oracle IT架构提供中心化监视、管理、生命周期管理功能的系统管理软件。包含Oracle系统和非Oracle系统。在你的企业架构中也许有很多数据库，中间件，应用程序，当然你可以为每个产品安装一个控制监视台，但对于大的复杂环境来说显然这样的工作量很大和效果不好。

二、Grid Control 架构
　网格控制包含三个组件：
　1). Oracle Management Service (OMS)
    2). Oracle Management Agent (Management Agent)
    3). Oracle Management Repository (Management Repository)

    OMS就好比是Grid Control架构里的大脑，负责和OMA和中央的存储信息的OMR通信。OMA就好比手和脚，负责从被监视的目标里收集信息并传输给OMS。OMR被配置为中央存储系统，专门用于存储收集来的信息。

三、安装前的准备工作
　　在安装前必须做一些准备工作：
　　1). 检查目标系统是不是支持的平台。比如：10.2.0.1是release版本，支持AIX 5L(不支持AIX6)，但是现在要安装10.2.0.4到认证了的平台AIX6，并且需要先安装１０.２.０.１然后打补丁到10.2.0.4。这样先安装10.2.0.1时就会报不支持的平台错误。这在metalink上有解决方法。
　　2). 安装包，32-bit的只能在32-bit的平台上安装，64-bit的必须在64-bit平台上安装。
　　3). 安装存储库时，提供两种选项：一个安装到存在的数据库，一个新安装一个数据库作为存储库。
　　　如果是选项一：那么需要考虑存在数据库的版本是否符合要求，参数是否满足要求，是否已经配置了ｃｏｎｔｒｏｌ控制台，如果是必须先卸载，某些包是否存在等。
　　　如果是选项二：那么默认安装的数据库版本是10.1.0.4，如果升级Grid Control到10.2.0.4那不会自动升级该数据库，必须手工升级到10.2.0.4以上版本。
　　　对于不同的安装方法下文将会介绍。
　　4).接下来还需要检查系统包、内核安全参数、空间、内存等，具体见附件
　　5).Grid Control有密码策略：密码必须５到３０个字符长、不能和用户名一样、必须包含要么全小写要么全大写的字母、至少要一个字母一个数字和一个特殊字符(如下划线)、密码不能为Oracle的保留字。
　　　如果想改默认的密码： ORACLE_HOME/bin/emctl set password <old_default_password> <new_password>
　　6). Grid ControlSchema用户需要在UTL_FILE包上有执行权限
　　　　SQL> grant execute on utl_file to sysman;
        7). 尽量使用静态的IP和主机名
　　8). 其它的所需要的用户和组基本和创建数据库一样：Group----oinstall, dba, oper, user----oracle, nobody

四、安装Grid Control version10.2.0.4
        安装10.2.0.4之前必须先安装10.2.0.1，因此需要两个安装包。
　　选项一：安装到存在的数据库
　　这里我选择安装到存在的数据库11.1.0.6上。
　　

Note:Before proceeding with the silent install change the port of ONS from database home $ORACLE_DB_HOME/opmn/conf/ons.config to 6004 or 6003 (or other unused non-default port for the OMS, 6001), and restart the database.

Note:

Example filepaths are used below. Actual filepaths should be substituted for the actual procedure.

$ORACLE_HOME:   repository databse Oracle Home filepath.

<gc_install_stage>:   grid control extracted installation stage filepath, may taake a variety of forms, depending on the source being used.

<oms_home>:   OMS Oracle Home filepath, i.e., /u01/app/oracle/oms10g.

<patchset_stage>:   10.2.0.4 Grid Control patchset extracted installation stage filepath, i.e., /u02/gcpatch/3731593/Disk1.

<parent_directory>:   filepath of the parent directory to be used for the OMS and agent.

Step 1: 

Upgrade the 10.1.0.4.0 database to 10.1.0.5.0 by applying thePatch 4505133, if it is desired to upgrade or patch the repository database later on. Note that only these versions are supported for this procedure at this time.

Step 2:

Edit the following parameters (example shown) ofem_using_existing_db.rsp
Located under the <gc_install_stage>/response/  

Parameter =              “ Value”
===========               ======
s_operGroup             ="dba"
UNIX_GROUP_NAME         ="dba"
FROM_LOCATION           ="/u02/grid_control/Disk1/oms/Disk1/stage/products.xml"
BASEDIR                 ="/u01/app/oracle"
INSTALLATION_NAME       ="Silent Install"
s_reposHost             ="<my_computer>"
s_reposPort             ="1521"
s_reposSID              ="emrep"
s_reposDBAPwd           ="oracle1"
s_mgmtTbsName           ="/u01/app/oracle/oradata/emrep/mgmt.dbf"
s_ecmTbsName            ="/u01/app/oracle/oradata/emrep/mgmt_ecm_depot1.dbf"
s_securePassword        ="oracle1"
s_securePasswordConfirm ="oracle1"
s_reposPwd              ="oracle1"
s_reposPwdConfirm       ="oracle1"


 

Note:If the database is already configured with Database Control, then it must be deconfigured before continuing the installation of Grid Control.

 

cd $ORACLE_HOME/bin
emca -deconfig dbcontrol db -repos drop

For the RAC cluster database, use this command.

cd $ORACLE_HOME/bin
emca -deconfig dbcontrol db -repos drop -cluster

Step 3:

Now Install the Grid Control Base version 10.2.0.1 for 32-bit Linux using silent install option with using “em_using_existing_db.rsp” response file.

Step 4:

cd <gc_install_stage>
runInstaller -noconfig -silent -ignoreSysPrereqs　-responseFile <gc_install_stage>/response/em_using_existing_db.rsp -force

After successful installation of the base version run the scripts recommended by installer as a userroot.

<oms_home>/allroot.sh

Step 5:

The OMS should not be started at this point.

Stop the opmn processes which may be running as follows:

cd <oms_home>/opmn/bin
./opmnctl stopall

Edit the parameters in the10.2.0.4 patchset.rsp located under the directory
<patchset_stage>//Disk1/response/patchset.rsp:

Parameter =        “ Value” 
===========        ====== 
UNIX_GROUP_NAME    ="dba" 
ORACLE_HOME        =”<oms_home>” 
b_softwareonly     =true 
FROM_LOCATION      =”<patchset_stage>/Disk1/stage/products.xml” 
s_sysPassword      =”oracle1” 
s1_pwdInfo         =”oracle1”

By using the following command, the installer will start the installation of the 10.2.0.4 patchset to the OMS home:

runInstaller -noconfig -silent -responseFile <patchset_stage>/Disk1/response/patchset.rsp -force

Step 6:

Now after patching OMS home, use the same response file to patch the Agent home. Change the ORACLE_HOME parameter to the filepath for the Agent Home in the patchset.rsp file. Leave all other parameters in place:

ORACLE_HOME=”<parent directory>/agent10g”

After making changes to patchset.rsp re run the command for patching Agent Home.

./runInstaller -noconfig -silent -responseFile <patchset_stage>/Disk1/response/patchset.rsp -force  

Set the environmental variablePERL5LIB

export PERL5LIB=<oms_home>/perl/lib/5.6.1

Next, run the ConfigureGC.pl script. in either of these ways:

<oms_home>/perl/bin/perl <oms_home>/sysman/install/ConfigureGC.pl <parent_directory>

or

cd <oms_home>/perl/bin/
./perl <oms_home>/sysman/install/ConfigureGC.pl <parent_directory>

 
Monitor these files in for errors and progress of the ConfigureGC.pl script.:

<oms_home>/cfgtoollogs/oui/configActions<date_time>.log

<oms_home>/cfgtoollogs/cfgfw/CfmLogger_<date_time>.log

<oms_home>/sysman/log/emca_repos_create<time>.log

<oms_home>/sysman/log/emca_repos_drop<time>.log


The end of configuration is denoted by this message in the command session from which the ConfigureGC.pl script. was run:

10.2.0.4 OMS patch configuration done

　　选项二：安装到新的数据库里
　　

A) For the base 10.2.0.1.0 Grid Control product install:

Before invoking the runInstaller utility for the 10.2.0.1.0 base Grid Control product installation in step 1, the following  modifications may be made to the <product_install_stage>/response/em_with_new_db.rsp response file (other values may remain at default):

UNIX_GROUP_NAME=<Value Unspecified> to dba
FROM_LOCATION="../rdbms/Disk1/stage/products.xml" to actual full filepath
BASEDIR=<Value Unspecified> to full parent directory filepath
INSTALLATION_NAME=<Value Unspecified> to "<ACTUAL NAME>"
s_gdbName=<Value Unspecified> to <ACTUAL REPO DB NAME>
s_mountPoint=<Value Unspecified> to <intended oradata directory filepath>
s_operGroup=<Value Unspecified> to dba
s_adminGroup=<Value Unspecified> to dba
b_lockedSelected=<Value Unspecified> to false (to be locked later)
b_passwordsDifferent=<Value Unspecified> to false (for common password option)
sl_adminPwds=<Value Unspecified> to <actual desired sys password value>
sl_adminPwdsConfirm=<Value Unspecified> to <actual desired sys password value>
b_passwordsSame=<Value Unspecified> to true (for common password option)
s_reposPwd=<Value Unspecified> to <actual dedsired sysman password value>
s_reposPwdConfirm=<Value Unspecified> to <actual desired sysman password value>

Notes:

In the configuration above, using common passwords for sys, system, dbsnmp and sysman, this password is established in the s_reposPwd and s_reposPwdConfirm values.

If the values for b_passwordsDifferent and b_passwordsSame are not correct, i.e, they are both false, then the subsequent configuration action will fail on repository access by SYS or SYSMAN, showing ORA-01017 in the associated logging.. Be sure these entries are correct before running the silent installation.

B) For the 10.2.0.4.0 Grid Control patchset application to the OMS (agent is similar):

Before invoking the runInstaller utility for the 10.2.0.4.0 Grid Control patchset installation in step 3, the following modifications may be made to the <patchset_install_stage>/3731593/Disk1/response/patchset.rsp response file (other values may remain at default):

UNIX_GROUP_NAME=<Value Unspecified> to dba
FROM_LOCATION="../stage/products.xml" to "<ACTUAL LOCATION OF PATCHSET STAGE>/stage/products.xml"
ORACLE_HOME=<Value Required> to the BASEDIR parameter from the base install appended with "/oms10g".
b_softwareonly=false to true
s_sysPassword=<Value Unspecified> to <ACTUAL VALUE>
sl_pwdInfo=<Value Unspecified> to <ACTUAL VALUE>
ORACLE_HOME_NAME should be "oms10g" in the response file and this will need to be added.
DEINSTALL_LIST should be active with the default value during patchset installation.

all of these set to false:
SHOW_SPLASH_SCREEN
SHOW_WELCOME_PAGE
SHOW_SUMMARY_PAGE
SHOW_INSTALL_PROGRESS_PAGE
SHOW_REQUIRED_CONFIG_TOOL_PAGE
SHOW_CONFIG_TOOL_PAGE
SHOW_XML_PREREQ_PAGE
SHOW_END_OF_INSTALL_MSGS
SHOW_ROOTSH_CONFIRMATION
SHOW_END_SESSION_PAGE
SHOW_EXIT_CONFIRMATION

Additionally, the 10.1.0.5.0 database patchset and 4329444 database patch should be applied to the repository database Oracle Home prior to 10.2.0.4.0 Control Grid patching as required by the 10.2.0.4.0  patchset installation procedure described in its readme.html (see alsoNote 457442.1).

Further, OPMN may have been started during the base product installation, but all of the OPMN-managed processes will be stopped. OPMN itself will also need to be stopped before application of the 10.2.0.4.0 Control Grid patchset can proceed. Issue the command "opmnctl stopall" to terminate the interfering processes and then apply the patchset. Stoppage can be verified with this command: ps -ef|grep opmn

Note that patching of the agent in the .../agent10g/ location is not performed in this step. A similar patching action should be performed on the agent at this time, so the action of the ConfigureGC.pl can proceed successfully through 10.2.0.4.0 agent configuration.

C) Execution of ConfigureGC.pl

In step 7c, during the OMS configuration step in the ConfigureGC.pl execution, it is likely that dbms jobs are running which will need to time out before the OMS CA can complete successfully. This problem and the solution are logged in the .../oms10g/cfgtoollogs/cfgfw/CfmLogger<date-time>.log for the session. Not enough time is allowed for the job queue to flush out, so, on failure of the OMS CA, execute the following on the repository database as SYSMAN:

exec emd_maintenance.remove_em_dbms_jobs;

This action prevents start of new jobs, but existing ones will need to complete. Run this query until no rows are returned:

Select count(*) FROM dba_jobs_running run_job,gv$session sess WHERE sess.sid = run_job.sid AND sess.schemaname = 'SYSMAN';

Then run the exact same ConfigureGC.pl script. execution command again. Note that this possibility is described in the software-only install procedure, but the sql indicated above is not provided there.

Normally the CA process will run to completion, through the agent CA, with all components starting up. If this is not the observed state of components, bring the Grid Control framework down completely and restart it from the listener as described in:

Oracle® Enterprise Manager Advanced Configuration
10g Release 4 (10.2.0.4.0)
Part Number E10954-01
Chapter 2 Starting and Stopping Enterprise Manager Components
Section titled: 2.6 Starting and Stopping Oracle Enterprise Manager 10g Grid Control

Execute this procedure when the ConfigureGC.pl script. is complete and the Grid Control framework is working:

exec emd_maintenance.submit_em_dbms_jobs;

 

Enterprise Manager Grid Control Architecture

Enterprise Manager Grid Control Components

初始化参数

内存要求

包检查