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，因此需要两个安装包。 选项一：安装到存在的数据库 这里我选择安装到存在的数据库18.104.22.168上。
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
Example filepaths are used below. Actual filepaths should be substituted
for the actual procedure.
$ORACLE_HOME: repository databse Oracle Home filepath.
grid control extracted installation stage filepath, may taake a variety
of forms, depending on the source being used. : OMS Oracle Home filepath, i.e., /u01/app/oracle/oms10g. :
10.2.0.4 Grid Control patchset extracted installation stage filepath,
i.e., /u02/gcpatch/3731593/Disk1. : 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 the Patch 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) of em_using_existing_db.rsp Located under the /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 =" " 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"
If the database is already configured with Database Control, then it
must be deconfigured before continuing the installation of Grid Control.
emca -deconfig dbcontrol db -repos drop
For the RAC cluster database, use this command.
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:
runInstaller -noconfig -silent -ignoreSysPrereqs -responseFile /response/em_using_existing_db.rsp -force
After successful installation of the base version run the scripts recommended by installer as a user root.
Step 5: The OMS should not be started at this point.
Stop the opmn processes which may be running as follows:
/opmn/bin ./opmnctl stopall
Edit the parameters in the10.2.0.4 patchset.rsp located under the directory //Disk1/response/patchset.rsp:
Parameter = “ Value” =========== ====== UNIX_GROUP_NAME ="dba" ORACLE_HOME =” ” b_softwareonly =true FROM_LOCATION =” /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
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:
After making changes to patchset.rsp re run the command for patching Agent Home.
./runInstaller -noconfig -silent -responseFile
Set the environmental variable
Next, run the ConfigureGC.pl script. in either of these ways:
cd /perl/bin/ ./perl /sysman/install/ConfigureGC.pl
Monitor these files in for errors and progress of the ConfigureGC.pl script.:
/sysman/log/emca_repos_create .log /sysman/log/emca_repos_drop .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:
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
file (other values may remain at default): UNIX_GROUP_NAME= to dba FROM_LOCATION="../rdbms/Disk1/stage/products.xml" to actual full filepath BASEDIR= to full parent directory filepath INSTALLATION_NAME= to " " s_gdbName= to s_mountPoint= to s_operGroup= to dba s_adminGroup= to dba b_lockedSelected= to false (to be locked later) b_passwordsDifferent= to false (for common password option) sl_adminPwds= to sl_adminPwdsConfirm= to b_passwordsSame= to true (for common password option) s_reposPwd= to s_reposPwdConfirm= to
the configuration above, using common passwords for sys, system, dbsnmp
and sysman, this password is established in the s_reposPwd and
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
B) For the 10.2.0.4.0 Grid Control patchset application to the OMS (agent is similar):
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
response file (other values may remain at default): UNIX_GROUP_NAME= to dba FROM_LOCATION="../stage/products.xml" to " /stage/products.xml" ORACLE_HOME= to the BASEDIR parameter from the base install appended with "/oms10g". b_softwareonly=false to true s_sysPassword= to sl_pwdInfo= to 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 also Note 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
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
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
.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;
topology_new.gif Snap1.jpg init_par.jpg memory_conf.jpg
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/9466564/viewspace-609515/，如需转载，请注明出处，否则将追究法律责任。