Install EM GC 10.2.0.5 Using Existin DB with Software Only on Linux x86_763347.1
Case Study - Installation of Enterprise Manager Grid Control 10.2.0.5.0 Using an Existing Database with the Software Only Method on Linux x86 (Doc ID 763347.1)
In this Document
Applies to:Enterprise Manager Base Platform - Version: 10.2.0.5 and later [Release: 10.2 and later ]Linux x86 x86 32 bit (for Enterprise Linux only) GoalThis procedure is for Oracle Enterprise Linux 5.3 x86, but the principle is applicable to all platforms with a base product version available. Nevertheless, other platforms may show slight differences in the configuration required to complete a successful installation. Likewise, different stage sources may result in a different filepath to required locations in the staged software, so adjust accordingly.
The software-only method of installation, first offered in version 10.2.0.4.0, allows;
Note:
This method is specifically for full installation of version 10.2.0.5.0 Grid Control. Do NOT use this method to install any other version of Grid Control. Do NOT use this method to patch or upgrade any existing Grid Control installation
. For this exercise, the following configuration is used in the example:
10.2.0.1.0 base product install stage: /u02/gc10201/ Values used in response files and command executions must be altered if a different configuration is used. These values are for demonstration use only and should be changed to be applicable to the system receiving the installation. Solution
Database Prerequisites:
Special attention must be paid to the repository database in certain versions. See Note 853691.1 "ALERT: Important Upgrade Steps Required for Enterprise Manager Grid Control 10gR5 (10.2.0.5) Upgrades" for pre-patch installation maintenance requirements for the affected database versions.
/u02/gc10201/response/em_using_existing_db.rsp.
Generic filepath form:
UNIX_GROUP_NAME="dba"
Notes:
generic filepath form:
>
6. Rename the copy in place to oms_patchset.rsp.
ORACLE_HOME="/u01/app/gc/oms10g"
b_softwareonly=true s_sysPassword="dbauser32" sl_pwdInfo={ "dbauser32" } oracle.iappserver.st_midtier:szl_InstanceInformation={ "dbauser32" }
u02/gc10205/3731593/Disk1/response/patchset.rsp
generic filepath form:
>
8. Rename the copy in place to agent_patchset.rsp.
ORACLE_HOME="u01/app/gc/agent10g"
> /u02/gc10201/runInstaller -noconfig -silent
-responseFile /u02/gc10201/response/em_using_existing_db.rsp -force generic command form:
>
-responseFile Note:
Use the -force option if installing into a parent directory that is not empty.. .../oraInventory/logs/ location (i.e., /u01/app/oraInventory/logs/ )
In addition, the installActions
.../oms10g/cfgtoollogs/oui/
.../agent10g/cfgtoollogs/oui/
These two installActions
.../oraInventory/oraInstRoot.sh
Run the allroot.sh script from the Oracle home directory of the database:
.../oms10g/allroot.sh
3. Certain opmn processes will be running merely as a result of installation, in spite of the fact that no configuration of the OMS Oracle Home has been performed. Stop these OPMN processes by running the following command from the Oracle Home directory of the OMS:
.../oms10g/opmn/bin/opmnctl stopall
4. Apply the 10.2.0.5.0 patchset to OMS: > /u02/gc10205/3731593/Disk1/runInstaller -noconfig -silent -responseFile /u02/gc10205/3731593/Disk1/response/oms_patchset.rsp -force generic command form:
>
Logging for the oms patchset application will be in the installActions
.../oraInventory/logs/
.../oms10g/cfgtoollogs/oui/
.../oms10g/root.sh
No feedback will be given on successful execution in this case.
/u02/gc10205/3731593/Disk1/runInstaller -noconfig -silent -responseFile /u02/gc10205/3731593/Disk1/response/agent_patchset.rsp -force
generic command orm:
>
Logging for the agent patchset application will be in the installActions
.../oraInventory/logs/
.../agent10g/cfgtoollogs/oui/
The installActions
.../agent10g/root.sh.
> setenv PERL5LIB_BACKUP $PERL5LIB
Set PERL5LIB:
> export PERL5LIB=.../oms10g/perl/lib/5.6.1
> .../oms10g/perl/bin/perl .../oms10g/sysman/install/ConfigureGC.pl /u01/app/gc
generic command form:
>
Logging for this action will start in the:
.../oms10g/cfgtoollogs/oui/configActions
As the configuration assistants are run through the progress of the script, ORACLE_HOME/cfgtoollogs/cf**/ files will begin to populate with the results of these configuration actions for each Oracle Home in its respective directory (i.e., .../oms10g/ or .../agent10g/). As operational actions (i.e., process start) are taken in the configuration steps, operational logs will be populated in these locations:
.../oms10g/sysman/log/
.../agent10g/sysman/log/ .../oms10g/opmn/logs/ .../oms10g/j2ee/OC4J_EM/log/ .../oms10g/Apache/Apache/logs/
amongst others.
.../oms10g/cfgtoollogs/oui/configActions
.../oms10g/cfgtoollogs/cf**/CfmLogger .../oms10g/sysman/log/emrepmgr* (for the progress of the repository upgrade)
5. At the point where the OMS Configuration Assistant runs and accesses the repository database to perform a repository drop in preparattion for the new repository creation, database access may fail with ORA-01017 as logged in the .../oms10g/sysman/log/emca_repos_drop
Could not connect to
This problem is discussed in Note.602750.1 ConfigureGC.pl Reports - Invalid Username/Password.
> ALTER user SYS identified by "default";
Run the configuration command again, as before:
> .../oms10g/perl/bin/perl .../oms10g/sysman/install/ConfigureGC.pl /u01/app/gc
In this case, the repository creation will be successful but the configuration action will fail later, in one of the last actions, a patch upgrade to the repository, again with the ORA-01017 (seen in the latest .../oms10g/cfgtoollogs/cf**/CfmLogger Log on to the database as SYSTEM, and issue this upate:
> ALTER user SYS identified by linux32;
Generic command form:
> ALTER user SYS identified by
Run the confiugration command yet again as before:
> .../oms10g/perl/bin/perl .../oms10g/sysman/install/ConfigureGC.pl /u01/app/gc
This last configuration command should run to successful completion after the repository upgrade action is complete. 6. Successful finish of the last configuration script will be denoted by this messaging in the command session (ignore date):
perform - mode finished for action: patchsetConfigure
You can see the log file: /u01/app/gc/oms10g/cfgtoollogs/oui/configActions2009-01-25_08-37-20-AM.log 10.2.0.5 OMS patch configuration done 7. Verify the 10.2.0.5.0 component version for the OMS in any of these ways:
a) "About Oracle Enterprise Manager" in the console view.
a) Application Server main target page
b) Home/Deployments Summary view for Application Server Installations in Grid Control c) Deplyments/Deployments Summary view for Application Server Installations in Grid Control d) .../oms10g/OPatch/opatch lsinventory e) OUI "Installed Products" view f) Main page of OMS/AS Application Server Control web site g) Application Server Control home page for the OMS installation.
a) Grid Control agent page view.
b) emctl status agent c) .../agent10g/OPatch/opatch lsinventory d) OUI "Installed Products" view e) Setup/Agents view in Grid Control
10. Review the post patch requirements of Note 853691.1 "ALERT: Important Upgrade Steps Required for Enterprise Manager Grid Control 10gR5 (10.2.0.5) Upgrades" for OMS and agent patching requirements of the 10.2.0.5.0 version. This is also a good time to apply the pre-patch database maintenance actions from this note, if appropriate, if this was not done before 10.2.0.5.0 patchset application to the OMS.
D. Potential Pitfalls:
E. Published Documentation References:
Oracle Enterprise Manager Grid Control Installation Guide ReferencesNOTE:763351.1 - Document References for Grid Control 10.2.0.5.0 Installation and UpgradeNOTE:853691.1 - Upgrade Grid Control 10.2.0.x to 10.2.0.5 - Important Steps Required |

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/17252115/viewspace-1246130/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 1. install software
- upgrade 10.2.0.5 to 11.2.0.4 on linuxLinux
- 【DB寶49】Oracle如何設定DB、監聽和EM開機啟動Oracle
- 02. 【Node.js Module】Install Pakages Using NPMNode.jsNPM
- You are using the runtime-only build of Vue where the template compiler is not available.UIVueCompileAI
- Android Studio Run專案出現Failure [INSTALL_FAILED_TEST_ONLY]AndroidAI
- Mysql 5.7.21 install for LinuxMySqlLinux
- linux之--install超時Linux
- 02. Install redis on LinuxRedisLinux
- Oracle 10.2.0.5升級至11.2.0.4Oracle
- EM
- Converting Oracle Database from Linux to Windows using RMANOracleDatabaseLinuxWindows
- Install linux mint apt to Ubuntu 18.04 LTSLinuxAPTUbuntu
- Linux下python pip install失敗LinuxPython
- install java javac on kali linux, raspberry piJavaLinux
- Android Studio ERROR: Installed Build Tools revision 34.0.0 is corrupted. Remove and install again using the SDK Manager.AndroidErrorUIREMAI
- SQLServer2017_Install_for_CentOS Linux release 7.5SQLServerCentOSLinux
- Oracle Linux 7.1 silent install 19cOracleLinux
- Example of SQL Linux Windows Authentication configuration using Managed Service AccountsSQLLinuxWindows
- DB2 Linux環境安裝DB2Linux
- Oracle Linux 7.1 silent install 19C RACOracleLinux
- em 和 remREM
- Cisco Firepower 9300 Series FTD Software 7.6.0 & ASA Software 9.22.1
- Cisco Firepower 4100 Series FTD Software 7.6.0 & ASA Software 9.22.1
- Cisco Firepower 1000 Series FTD Software 7.6.0 & ASA Software 9.22.1
- oracle 10 rac 升級 10.2.0.1升級到10.2.0.5Oracle
- 從10.2.0.1升級到10.2.0.5操作實驗(下)
- Connect SQL Server from Linux Client using Windows Authentication and troubleshoot stepsSQLServerLinuxclientWindows
- Manifesto of Software CraftsmanshipRaft
- Cisco Secure Firewall 3100 Series FTD Software 7.6.0 & ASA Software 9.22.1
- Full GC (Metadata GC Threshold)GC
- rem與em的區別||結合使用rem與emREM
- Failed to run 'create login' or 'sp_addsrvrolemeber' in sql Linux using windows authentcationAIVRSQLLinuxWindows
- oracle EM 優化Oracle優化
- MySQL 索引優化 Using where, Using filesortMySql索引優化
- 從CLR GC到CoreCLR GCGC
- linux下使用npm install報EACCES的解決方法LinuxNPM
- Linux安裝Redis 6.0.5 ./install_server.sh報錯LinuxRedisServer
- MySQL explain結果Extra中"Using Index"與"Using where; Using index"區別MySqlAIIndex