How To Install Grid Control OMS 10.2.0.4 Using an Existing Database

Background & Overview

The following documentation provides instructions for installing Grid Control OMS residing on a Sun Solaris 10 (Version 5.10) operating system using an existing database for a repository and conforming to Oracle OFA standards.

Assumptions & Pre-Requisites

This document expects and assumes the following:

  • The instructions are carried out by a qualified DBA.
  • Access to the internet is available.
  • All necessary client software, e.g. Telnet and X-Server is available.
  • All references to SID should be replaced with correct database name as derived using a valid database naming standard.
  • There is only ONE database installed on the server and that database is at version 10.2.0.4 with ALL recommended patches applied.

Useful Information

Step-By-Step Guide

Installing Grid Control and Patching to 10.2.0.4

1. Ensure oracle account and dba group exists.

2. Ensure nobody account exists.

  • id nobody

3. Download the Oracle Grid Control OMS 10.2.0.1 binaries from Oracle into /u01/app/oracle/SOFTWARE/GRID/OMS.

Grid Control 10.2.0.4 for Solaris Operating System (SPARC) (64-bit)
Sol_Grid_Control_full_102010_disk1.zip : 470,575,730 bytes; cksum - 3364605454
Sol_Grid_Control_full_102010_disk2.zip : 616,605,844 bytes; cksum - 2061924499
Sol_Grid_Control_full_102010_disk3.zip : 591,687,858 bytes; cksum - 784133586
Sol_Grid_Control_full_102010_disk4.zip : 616,517,339 bytes; cksum - 678452560

4. Download the Oracle Grid Control OMS 10.2.0.4 upgrade binaries from Oracle into /u01/app/oracle/SOFTWARE/GRID/Upgarde.

Grid Control 10.2.0.4 for Solaris Operating System (SPARC) (64-bit)
Grid_Control_10.2.0.4.0_Solaris.zip : 1,664,610,032 bytes; cksum - 1259898047

5. Download the recommended patches for Oracle Grid Control OMS 10.2.0.4 into /u01/app/oracle/SOFTWARE/GRID/Patches. At the time of producing this guide the following patches were recommended.

Grid Control 10.2.0.4 for Solaris Operating System (SPARC) (64-bit)
p6356310_10204_GENERIC.zip : 21150 bytes; cksum - 2043055312
p6614013_10204_GENERIC.zip : 43435 bytes; cksum - 4270502455
p6646817_10204_GENERIC.zip : 18408 bytes; cksum - 3930854548
p6895374_10204_GENERIC.zip : 173889 bytes; cksum - 3688721700
p7609761_10204_GENERIC.zip : 96543 bytes; cksum - 3341925285

6. Download the post installation patches for the OMS 10.2.0.4 patchset into /u01/app/oracle/SOFTWARE/GRID/Patches. At the time of producing this guide the following patches were recommended.

Cloning Support Files Patch 5588438 for RDBMS 9.2.x Running on Solaris
p5588438_10204_GENERIC.zip : 212212788 bytes; cksum - 1627914801

One-off Patches to Fix Various Bugs
p7031906_10204_Solaris-64.zip : 24734 bytes; cksum - 3273138577
p4948589_10204_Solaris-64.zip : 21617 bytes; cksum - 4212734241
p7012242_10204_Solaris-64.zip : 36213 bytes; cksum - 4052783282

7. Download the iAS 10.1.2.3 upgrade binaries into /u01/app/oracle/SOFTWARE/GRID/IAS_Upgrade.

iAS 10.1.2.3 for Solaris Operating System (SPARC) (64-bit)
p5983622_10123_SOLARIS64.zip : 1866738796 bytes; cksum - 1511658493

8. Download the iAS recommended patches for iAS 10.1.2.3 into /u01/app/oracle/SOFTWARE/GRID/IAS_Patches. At the time of producing this guide the following patches were recommended.

iAS 10.1.2.3 for Solaris Operating System (SPARC) (64-bit)
p7608330_10123_SOLARIS64.zip : 19844724 bytes; cksum - 3034848660

9. Unzip the OMS Binaries

  • cd /u01/app/oracle/SOFTWARE/GRID/OMS
  • unzip Sol_Grid_Control_full_102010_disk1.zip
  • unzip Sol_Grid_Control_full_102010_disk2.zip
  • unzip Sol_Grid_Control_full_102010_disk3.zip
  • unzip Sol_Grid_Control_full_102010_disk4.zip

10. Unzip the OMS Upgrade Binaries

  • cd /u01/app/oracle/SOFTWARE/GRID/Upgrade
  • unzip Grid_Control_10.2.0.4.0_Solaris.zip
  • rm p4329444_10104_SOLARIS64.zip
    • NB This is a patch if using the in built 10.1.0.4 database.
  • rm p4329444_10105_SOLARIS64.zip
    • NB This is a patch if using the in built 10.1.0.5 database.
  • unzip p3731593_10204_SOLARIS64.zip
  • unzip 3731596.zip
    • NB This is required for the OMS Agent patching.
  • unzip 3822442.zip
    • NB This is required for the OMS Agent patching.

11. Unzip the OMS Patches

  • cd /u01/app/oracle/SOFTWARE/GRID/Patches
  • unzip p7609761_10204_GENERIC.zip
  • unzip p6895374_10204_GENERIC.zip
  • unzip p6646817_10204_GENERIC.zip
  • unzip p6614013_10204_GENERIC.zip
  • unzip p6356310_10204_GENERIC.zip

12. Unzip the post installation patches for the OMS 10.2.0.4 patchset.

  • cd /u01/app/oracle/SOFTWARE/GRID/Patches
  • unzip p5588438_10204_GENERIC.zip
  • unzip p7031906_10204_Solaris-64.zip
    • NB This is required for the OMS Agent patching and fixes Health Check issues.
  • unzip p4948589_10204_Solaris-64.zip
    • NB This is required for the OMS Agent patching and fixes DMS Schema issues.
  • unzip p7012242_10204_Solaris-64.zip
    • NB This is required for the OMS Agent patching and fixes Memory issues.

13. Unzip the iAS Upgrade Binaries

  • cd /u01/app/oracle/SOFTWARE/GRID/IAS_Upgrade
  • unzip p5983622_10123_SOLARIS64.zip

14. Unzip the iAS Recommended Patches

  • cd /u01/app/oracle/SOFTWARE/GRID/IAS_Patches
  • unzip p7608330_10123_SOLARIS64.zip

15. Create dbmspool procedure on the database and grant privileges.

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • sqlplus '/ as sysdba'
  • SQL> @?/rdbms/admin/dbmspool.sql
  • SQL> grant execute on utl_file to public;
  • SQL> commit;
  • SQL> quit

16. Run the OMS installer for the base OMS binaries.

  • Start and X-Server
  • cd /u01/app/oracle/SOFTWARE/GRID/OMS
  • unset ORACLE_HOME
  • unset ORACLE_SID
  • ./runInstaller

17. Follow the instructions in the Example OMS Install section below.

18. If you have patch 5191377 on your database you need to remove it before continuing. Check using the following commands.

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • opatch lsinventory |grep 5191377
  • If the above step returns any output, refer to patch 5191377 regarding its removal.

19. Stop the OMS process

  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop oms

20. Stop the iasconsole

  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop iasconsole

21. Stop all the application server components, such as Oracle HTTP Server, <nop>OracleAS Web Cache.

  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl stopall

22. Stop the Management Agent process

  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl stop agent

23. Run the OMS installer for the Upgrade OMS binaries.

  • Start and X-Server
  • cd /u01/app/oracle/SOFTWARE/GRID/Upgrade/3731593/Disk1
  • unset ORACLE_SID
  • unset ORACLE_HOME
  • ./runInstaller

24. Follow the instructions in the Example OMS Upgrade section below.

25. Run the Agent10g installer for the Upgrade Agent10g binaries.

  • Start and X-Server
  • cd /u01/app/oracle/SOFTWARE/GRID/Upgrade/3822442/Disk1
  • ./runInstaller

25. Follow the instructions in the Example Agent10g Upgrade Install section below.

26. Stop the OMS process

  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop oms

27. Stop the iasconsole

  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop iasconsole

28. Stop all the application server components, such as Oracle HTTP Server, OracleAS Web Cache.

  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl stopall

29. Stop the Management Agent process

  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl stop agent

30. Apply the post installation patches for the OMS 10.2.0.4 patchset.

  • unset ORACLE_HOME
  • export ORACLE_HOME=/u01/app/oracle/GRID/oms10g
  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/5588438
  • opatch apply
  • When you get the error, answer no continuing
  • opatch apply
    • N.B. This time the patch should apply error free.
  • ./emctl stop iasconsole

31. Start the listener and the database

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • lsnrctl start
  • sqlplus '/ as sysdba'
  • SQL> startup
  • SQL> quit

32. Identify Solaris Agents with Host 3.0 metadata in the Enterprise Manager repository.

  • cd /u01/app/oracle/GRID/oms10g/sysman/admin/emdrep/sql/core/10.2.0.2/host
  • sqlplus sysman/password
  • SQL> @list_lfm_solaris_3_0_metadata_hosts
  • SQL> @list_lfm_templates
  • SQL> @list_lfm_notif_rules
  • SQL> @list_lfm_threshold_hosts
  • SQL> quit

N.B. All of the above scripts should return an empty list or 0 rows. If not, refer to the Post Installation Tasks Specific to Solaris Agent Hosts in the readme.html file of the 10.2.0.4 OMS patchset. DO NOT continue until all of the above scripts return 0 rows or an empty list.

33. Start the Grid Control Console and agent on all OMS nodes.

  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl startall
  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl start oms
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl start agent

34. Clear and purge Log File Pattern Matched Line Count severities from Solaris 3.0 metadata based hosts

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • cd /u01/app/oracle/GRID/oms10g/sysman/admin/emdrep/sql/core/10.2.0.2/host
  • sqlplus sysman/password
  • SQL> @list_lfm_severity_solaris_hosts
  • For each host listed in the step above, perform the following steps
    • Log on to Grid Control console with credentials/privileges that help you edit the host thresholds.
    • Go to the home page for the given host and click Log File Alerts.
    • Click Clear Every Open Alert.
    • To purge the clear alerts, click Show Cleared Alerts and then Purge Every Alert.
    • SQL> @list_lfm_severity_solaris_hosts
      • N.B. This should now produce an empty list.
  • SQL> quit

35. Shutdown the Grid Control Console and agent on all OMS nodes.

  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop oms
  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl stopall
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl stop agent

36. Execute lfm_fix_host_metadata.sql to the Enterprise Manager Repository

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • cd /u01/app/oracle/GRID/oms10g/sysman/admin/emdrep/sql/core/10.2.0.2/host
  • sqlplus sysman/password
  • SQL> @lfm_fix_host_metadata

37. Start the Grid Control Console and agent on all OMS nodes.

  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl startall
  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl start oms
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl start agent

38. Verify that the patch has been applied properly.

  • Log on to Grid Control console.
  • Go to the home page of a UNIX host and click Metric and Policy Settings.
    • N.B. You will have to wait for Grid Control to poll the agent before Metric and Policy Settings becomes available
  • Click the edit icon that is next to Log File Pattern Matched Line Count
  • Verify that the following columns are displayed in the Monitored Objects table
  • Select
  • Log File Name
  • Match Pattern in Perl
  • Ignore Pattern in Perl
  • Comparison Operator
  • Warning Threshold
  • Critical Threshold
  • Corrective Action

39. Apply correct grants.

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • sqlplus '/ as sysdba'
  • SQL> grant execute on utl_file to sysman;
  • SQL> grant execute on utl_file to oracle_ocm;
  • SQL> grant execute on dbms_lob to sysman;
  • SQL> grant execute on dbms_job to sysman;
  • SQL> grant execute on dbms_job to dbsnmp;
  • SQL> alter package sys.DBMS_UTILITY compile body;
  • SQL> alter package DBSNMP.MGMT_BSLN_INTERNAL compile body;
  • SQL> alter package sys.DBMS_UTILITY compile body;
  • SQL> revoke execute on utl_file from public;
  • SQL> revoke execute on dbms_job from public;
  • SQL> revoke execute on dbms_lob from public;
  • SQL> @?/rdbms/admin/utlrp
  • SQL> @invalid
    • NB There should be no invalid objects
  • SQL> quit

Apply Recommended Patches to Grid Control 10.2.0.4

1. Shutdown the Grid Control Console and agent on all OMS nodes.

  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop oms
  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl stopall
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl stop agent

2. Apply recommended patch 6356310.

  • unset ORACLE_HOME
  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/6356310
  • export ORACLE_HOME=/u01/app/oracle/GRID/oms10g
    • opatch apply

3. Apply recommended patch 6614013.

  • unset ORACLE_HOME
  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/6614013
  • export ORACLE_HOME=/u01/app/oracle/GRID/oms10g
  • opatch apply

4. Apply recommended patch 6646817.

  • unset ORACLE_HOME
  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/6646817
  • export ORACLE_HOME=/u01/app/oracle/GRID/oms10g
  • opatch apply

5. Apply recommended patch 6895374.

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • SQL> connect sysman/password
  • SQL> SELECT what, broken FROM dba_jobs WHERE log_user = priv_user and priv_user = (SELECT owner FROM dba_procedures WHERE object_name = 'MGMT_USER' AND procedure_name = 'DROP_USER') and broken !='N' ORDER BY job;
    • N.B. Make a note of the broken jobs.
  • SQL> SELECT object_name FROM user_objects WHERE status = 'INVALID' order by object_name ;
    • N.B. Make a note of the invalid objects.
  • SQL> show parameter job_queue_processes;
    • N.B. Make a note of the job queue processes value.
  • SQL> ALTER SYSTEM SET job_queue_processes = 0;
  • SQL> SELECT /*+ RULE */ FROM DBA_JOBS_RUNNING ;
    • N.B. Make sure this returns 0 rows. Do not continue if it does not, instead stop the jobs or wait for the jobs to complete.
  • SQL> quit
  • unset ORACLE_HOME
  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/6895374
  • export ORACLE_HOME=/u01/app/oracle/GRID/oms10g
  • opatch apply
  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • sqlplus sysman/password
  • SQL> @/u01/app/oracle/GRID/oms10g/sysman/admin/emdrep/sql/core/latest/jobs/jobs_engine_pkgbody.sql
  • SQL> @/u01/app/oracle/GRID/oms10g/sysman/admin/emdrep/sql/core/latest/admin/admin_recompile_invalid SYSMAN
    • N.B. Must be in UPPERCASE
  • SQL> ALTER SYSTEM SET job_queue_processes=original value
    • N.B. Set this back to the value noted in the step above.
  • SQL> SELECT what, broken FROM dba_jobs WHERE log_user = priv_user and priv_user = (SELECT owner FROM dba_procedures WHERE object_name = 'MGMT_USER' AND procedure_name = 'DROP_USER') and broken !='N' ORDER BY job;
    • N.B. Make sure this value is the same as the value noted in the step above.
  • SQL> SELECT object_name FROM user_objects WHERE status = 'INVALID' order by object_name ;
    • N.B. Make sure this value is the same as the value noted in the step above.
  • SQL> quit

6. Now apply the January 2009 CPU patches 7609761.

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • lsnrctl stop
  • sqlplus '/ as sysdba'
  • SQL> shutdown immediate
  • SQL> quit
  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop oms
  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl stopall
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl stop agent
  • unset ORACLE_HOME
  • export ORACLE_HOME=/u01/app/oracle/GRID/oms10g
  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/7609761
  • opatch napply -skip_subset -skip_duplicate
    • N.B. The parameters on this opatch command will check your system for conflicts. If conflicts exist, click 'N' to continue and raise an SR.

7. Now apply Post Implementation Patch 7031906.

  • unset ORACLE_HOME
  • export ORACLE_HOME=/u01/app/oracle/GRID/agent10g
  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/7031906
  • opatch apply

8. Now apply Post Implementation Patch 4948589

  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/4948589
  • opatch apply

9. Now apply Post Implementation Patch 7012242.

  • cd /u01/app/oracle/SOFTWARE/GRID/Patches/7012242
  • opatch apply

10. Start up the Database and Grid Control

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • lsnrctl start
  • sqlplus '/ as sysdba'
  • SQL> startup
  • SQL> quit
  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl startall
  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl start iasconsole
  • ./emctl start oms
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl start agent

Grid Control Post Implementation Task

1. Set the *DBSNMP* password.

  • In the Grid Control console, go to the database Home Page
  • Click on the configure database link.
  • In the Configure Database Instance: Properties page, set the DBSNMP password.
  • Click the test connection button.
  • Once the connection is successful, click *next* followed by *submit*.

2. Delete the Microsoft Operations Manager target.

  • Click on the Targets tab in the Grid Control Console.
  • Click on All Targets
  • Select the radio button next to generic_mom_managed_host
  • Click remove
  • Ensure you have selected the correct target and click yes to confirm removal.

3. Fix the *maxRowCount.pl* Errors Generated in Log File *emagent_perl.trc* as per Metalink Article *359769.1*

  • cd AGENT_HOME/sysman/config/esa
  • Make a backup of the following files.
    • cp database.properties backup_location/database.properties.BACKUP
    • cp instance.properties backup_location/instance.properties.BACKUP
  • Using vi remove all blank lines from the following files
    • database.properties
    • instance.properties

4. Fix the *MGMT_CNTR_TT.CLEAN_UP_OLD_TICKET_RECS* job as per Metalink Article *416352.1*

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • sqlplus '/ as sysdba'
  • SQL> select job, schema_user, what from user_jobs where what like 'MGMT_CNTR_TT.clean_up_old_ticket_recs%';
  • SQL> exec dbms_job.remove(job id from previous step)
  • SQL> connect sysman/password
  • SQL> DECLARE jobID NUMBER; BEGIN dbms_job.submit (jobID,'MGMT_CNTR_TT.clean_up_old_ticket_recs;', SYSDATE, 'trunc (SYSDATE + 1) + 2/24'); commit; END; /
  • SQL> quit

Upgrade iAS to 10.1.2.3

1. Shutdown the Grid Control Console and agent on all OMS nodes.

  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop oms
  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl stopall
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl stop agent

2. Start the database and listener.

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • lsnrctl start
  • sqlplus '/ as sysdba'
  • SQL> startup
  • SQL> quit

3. Run the iAS installer for the base iAS upgrade binaries.

  • Start and X-Server
  • cd /u01/app/oracle/SOFTWARE/GRID/IAS_Upgrade/Disk1
  • unset ORACLE_HOME
  • unset ORACLE_SID
  • export ORACLE_HOME=/u01/app/oracle/GRID/oms10g
  • ./runInstaller

4. Follow the instructions in the [[OracleGridControlOMSInstallGuide#toc12][Example iAS Upgrade]] section below.

Apply Recommended Patches to iAS 10.1.2.3

1. Shutdown the Grid Control Console and agent on all OMS nodes.

  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl stop oms
  • ./emctl stop iasconsole
  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl stopall
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl stop agent

2. Define the OPATCH_PLATFORM

  • export OPATCH_PLATFORM_ID=23

3. Apply the Recommended Patch 7608330

  • unset ORACLE_HOME
  • unset ORACLE_SID
  • export ORACLE_HOME=/u01/app/oracle/GRID/oms10g
  • cd /u01/app/oracle/SOFTWARE/GRID/IAS_Patches/7608330
  • opatch napply
  • Answer y to the message about patch 7592360
  • sh remove_demo.sh

4. Start up the Database and Grid Control

  • . oraenv
  • ORACLE_SID = [oracle] ? SID
  • lsnrctl start
  • sqlplus '/ as sysdba'
  • SQL> startup
  • SQL> quit
  • cd /u01/app/oracle/GRID/oms10g/opmn/bin
  • ./opmnctl startall
  • cd /u01/app/oracle/GRID/oms10g/bin
  • ./emctl start iasconsole
  • ./emctl start oms
  • cd /u01/app/oracle/GRID/agent10g/bin
  • ./emctl start agent

Example OMS Install


GridControlOMSInstall_1.JPG
  • Select Enterprise Manager 10g Grid Control Using an Existing Database.
  • Click Next.

GridControlOMSInstall_2.JPG
  • Enter Oracle Home Location /u01/app/oracle/GRID
  • Click Next.

GridControlOMSInstall_3.JPG
  • This screen will move on automatically.

GridControlOMSInstall_4.JPG
  • Click Ok.

GridControlOMSInstall_5.JPG
  • Ensure all Operating System Requirements are met.
  • Click Next.

GridControlOMSInstall_6.JPG
  • Enter Database Hostname hostname.co.uk
  • Enter Port 1521
  • Enter SID SID
  • Enter SYS Password password
  • Set Management Tablespace Location to /u07/oradata/SID/data/d1/mgmt_01.dbf
  • Set Configuration Data Tablespace Loction to /u07/oradata/SID/data/d1/mgmt_ecm_depot1_01.dbf
  • Click Next.

GridControlOMSInstall_7.JPG
  • Click Next.

GridControlOMSInstall_8.JPG
  • Enter Registration Password
  • Confirm Registration Password
  • Ensure Require Secure Communications is ticked.
  • Enter SYSMAN Password
  • Confirm SYSMAN Password
  • Click Next.

GridControlOMSInstall_9.JPG
  • Review the Summary page.
  • Click Install.

GridControlOMSInstall_10.JPG
  • This page moves on automatically to the agent10g install page.

GridControlOMSInstall_11.JPG
  • This page moves on automatically.

GridControlOMSInstall_12.JPG
  • Get a Unix Administrator to run allroot.sh - _Answer 'y' to any overwrite questions_
  • Click Ok.

GridControlOMSInstall_13.JPG
  • Ensure all Configuration Assistants complete successfully
  • If the Configuration Assistants are successful, then this page will move on automatically.

GridControlOMSInstall_14.JPG
  • Click Exit.

GridControlOMSInstall_15.JPG
  • Click Yes

Example OMS Upgrade


GridControlOMSUpgardeInstall_1.JPG
  • Specify the Name of the Oracle Home you want to upgrade. E.g. oms10g
  • Enter the OMS home directory Path. E.g /u01/app/oracle/GRID/oms10g
  • Click Next.

GridControlOMSUpgradeInstall_2.JPG
  • Ensure all Operating System Checks complete ok.
  • Click Next.

GridControlOMSUpgradeInstall_3.JPG
  • Enter the SYS password.

GridControlOMSUpgradeInstall_4.JPG
  • Tick Enable Configuration Manager Registration

GridControlOMSUpgradeInstall_5.JPG
  • Click Accept Licence Agreement

GridControlOMSUpgradeInstall_6.JPG
  • Enter a valid CSI.
  • Enter a valid account in the Metalink Account Username field.
  • Select United Kingdom on the drop down box for Country Code.
  • Click Connection Settings.

GridControlOMSUpgradeInstall_7.JPG
  • Tick Enable Proxy
  • Enter a valid Proxy Server
  • Enter a valid Port
  • Enter a valid Proxy Username
  • Enter a valid Password
  • Click Test Connection

GridControlOMSUpgradeInstall_8.JPG
  • Click Ok

GridControlOMSUpgradeInstall_9.JPG
  • Click Ok

GridControlOMSUpgradeInstall_10.JPG
  • Click Ok

GridControlOMSUpgradeInstall_11.JPG
  • Click Next

GridControlOMSUpgradeInstall_12.JPG
  • Review the Summary page.
  • Click Install

GridControlOMSUpgradeInstall_13.JPG
  • This page will move on automatically.

GridControlOMSUpgradeInstall_14.JPG
  • Ensure all Configuration Assistants complete successfully
  • If the Configuration Assistants are successful, then this page will move on automatically.

GridControlOMSUpgradeInstall_15.JPG
  • Click Exit

GridControlOMSUpgradeInstall_16.JPG
  • Click Yes

Example Agent10g Upgrade Install


GridControlAgent10gUpgardeInstall_1.jpg
  • Specify the Name* of the Oracle Home you want to upgrade. *E.g. agent10g
  • Enter the agent10g home directory Path. E.g /u01/app/oracle/GRID/agent10g
  • Click Next.

GridControlAgent10gUpgardeInstall_2.jpg
  • Ensure all Operating System Checks complete ok.
  • Click Next.

GridControlAgent10gUpgardeInstall_3.JPG
  • Tick Enable Configuration Manager Registration

GridControlAgent10gUpgardeInstall_4.JPG
  • Click Accept Licence Agreement

GridControlAgent10gUpgardeInstall_5.JPG
  • Enter a valid CSI
  • Enter a valid email account in the Metalink Account Username field.
  • Select United Kingdom on the drop down box for Country Code.
  • Click Connection Settings.

GridControlAgent10gUpgardeInstall_6.JPG
  • Tick Enable Proxy
  • Enter a valid Proxy Server
  • Enter a valid Port
  • Enter a valid Proxy Username
  • Enter a valid Password
  • Click Test Connection

GridControlAgent10gUpgardeInstall_7.JPG
  • Click Ok

GridControlAgent10gUpgardeInstall_8.JPG
  • Click Ok

GridControlAgent10gUpgardeInstall_9.JPG
  • Click Ok

GridControlAgent10gUpgardeInstall_10.JPG
  • Click Next

GridControlAgent10gUpgardeInstall_11.JPG
  • Review the Summary page.
  • Click Install

GridControlAgent10gUpgardeInstall_12.JPG
  • This page will move on automatically.

GridControlAgent10gUpgardeInstall_13.JPG
  • Ensure all Configuration Assistants complete successfully
  • If the Configuration Assistants are successful, then this page will move on automatically.

GridControlAgent10gUpgardeInstall_14.JPG
  • Get a Unix Administrator to run root.sh
  • Click ok

GridControlAgent10gUpgardeInstall_15.JPG
  • Click Exit

GridControlAgent10gUpgardeInstall_16.JPG
  • Click Yes

Example iAS Upgrade


GridControliASUpgardeInstall_1.JPG
  • Click Next.

GridControliASUpgardeInstall_2.JPG
  • Set the Name to the oms10g
  • Click Next.

GridControliASUpgardeInstall_3.JPG
  • Ensure Oracle Application Server and Developer Suite 10g Rel 2 Software Update is selected.
  • Click Next.

GridControliASUpgardeInstall_4.JPG
  • Enter the ias_admin Password as specified during the Grid Control install.
  • Click Next.

GridControliASUpgardeInstall_5.JPG
  • Click OK.

GridControliASUpgardeInstall_6.JPG
  • Review the summary page.
  • Click Install.

GridControliASUpgardeInstall_7.JPG
  • This page will move on automatically if successful.

GridControliASUpgardeInstall_8.JPG
  • Get a Unix Adminitrator to run the root.sh script - _Answer 'y' to any overwrite questions_
  • Click OK.

GridControliASUpgardeInstall_9.JPG
  • Ensure all Configuration Assistants complete successfully.
  • Click Next.

GridControliASUpgardeInstall_10.JPG
  • Click Exit.

GridControliASUpgardeInstall_11.JPG
  • Click Yes.

Useful Scripts

Basic Startup Script

#!/bin/ksh
. oraenv
lsnrctl start
sqlplus '/ as sysdba' «EOF
startup
quit
EOF
cd /u01/app/oracle/GRID/oms10g/opmn/bin
./opmnctl startall
cd /u01/app/oracle/GRID/oms10g/bin
./emctl start iasconsole
./emctl start oms
cd /u01/app/oracle/GRID/agent10g/bin
./emctl start agent

Basic Shutdown Script

#!/bin/ksh
. oraenv
cd /u01/app/oracle/GRID/agent10g/bin
./emctl stop agent
cd /u01/app/oracle/GRID/oms10g/bin
./emctl stop oms
./emctl stop iasconsole
cd /u01/app/oracle/GRID/oms10g/opmn/bin
./opmnctl stopall
lsnrctl stop
sqlplus '/ as sysdba' «EOF
shutdown immediate
quit
EOF

Known Issues

Issues Applying Patch 7608330

Description

When applying patch 7608330 the following error is generated at the end.


The following warnings have occurred during OPatch execution:
1) OUI-67302:
OPatch found that the following patches are not required.
They are either subset of the patches in Oracle Home or subset of the patches in the given list :
4601861
2) OUI-67303:
Following patches will be rolled back from Oracle Home on application of the patches in the given list :
4601861


OPatch Session completed with warnings.

Cause

This is due to patch 4601861 being rolled back as it is no longer required.

Fix Step-By-Step

This error is expected and can be ignored.


Issues Applying Patch 5588438

Description

When applying patch 5588438 you may get the following error.

Return Code = 1
Command invocation returned > Error… '/u01/app/oracle/SOFTWARE/GRID/Patches/5588438/custom/scripts/pre: /u01/app/oracle/GRID/oms10g/sysman/clonerStage/db/p453/: does not exist
', Return Code = 1
Execution of PRE script failed, with return value = 1

Cause

This error is caused by an Oracle coding error where it expects a directory to exist and fails when it does not exist. In actual fact, it is unlikely that the directory will exist as it is being created by this patch.

Fix Step-By-Step

1. Answer N to the question Okay to continue?
2. Rerun the opatch apply command.


Issues Applying Patch 6895374

Description

When applying script jobs_engine_pkgbody.sql for patch 6895374 you may get the following errors.

Warning: Package Body created with compilation errors.

Errors for PACKAGE BODY MGMT_JOB_ENGINE:

LINE/COL ERROR
-- -------------
77/5 PL/SQL: SQL Statement ignored
77/12 PL/SQL: ORA-00918: column ambiguously defined
218/5 PL/SQL: Statement ignored
218/5 PLS-00313: 'MOVE_EXECUTION_TO_HISTORY' not declared in this scope
866/13 PL/SQL: Statement ignored
866/13 PLS-00313: 'UPDATE_STEP_SET_STATUS' not declared in this scope
946/5 PL/SQL: SQL Statement ignored
948/33 PL/SQL: ORA-00904: "JOB_TYPE": invalid identifier
982/5 PL/SQL: SQL Statement ignored
985/10 PL/SQL: ORA-00904: "JOB_TYPE": invalid identifier
1037/5 PL/SQL: SQL Statement ignored

LINE/COL ERROR
-- -------------
1039/12 PL/SQL: ORA-00904: "JOB_TYPE": invalid identifier
1064/17 PL/SQL: Statement ignored
1064/17 PLS-00306: wrong number or types of arguments in call to
'UPDATE_STEP_STATUS'
1077/9 PL/SQL: SQL Statement ignored
1080/16 PL/SQL: ORA-00904: "JOB_TYPE": invalid identifier
1102/17 PL/SQL: Statement ignored
1102/17 PLS-00306: wrong number or types of arguments in call to
'UPDATE_STEP_STATUS'

LINE/COL ERROR
-- -------------
1152/17 PL/SQL: SQL Statement ignored
1153/33 PL/SQL: ORA-00904: "JOB_TYPE": invalid identifier

Cause

This error is caused by using the '?' in sqlplus to substitute the ORACLE_HOME and the ORACLE_HOME is set to the database home. Ensure the full path to the script is specified. This script resides in the oms10g home directory.

Fix Step-By-Step

1. Run the script using the full path to the script. E.g.

  • @/u01/app/oracle/GRID/oms10g/sysman/admin/emdrep/sql/core/latest/jobs/jobs_engine_pkgbody.sql

Issues Running allroots.sh

Description

When running allroots.sh you may get the following error.

chmod: WARNING: /u01/app/oracle/GRID/oms10g/bin/emtgtctl2: Corresponding set-ID also disabled on file since set-ID requires execute permission

Cause

Unknown

Fix Step-By-Step

This error can be ignored.

Error Messages When Starting up Grid Control

Description

The following error messages may be reported when starting grid control.

Message Found in Log Metalink Reference Cause
ERROR app.ContextInitializer contextInitialized.436 - Exception message: Folder Name already in use emoms.trc 603862.1 Bug
[Orion Launcher] ERROR app.ContextInitializer contextInitialized.422 - Integration Class not found: oracle.sysman.pp.paf.sample.ui.intg.PAFDemoIntegration&nbsp;&nbsp; emoms.trc 603862.1 Bug
[JobWorker 875:Thread-19] ERROR jobs.pingCfmEMDDown executeCommand.311 - pingCfmEMDDown: Throwable caught null emoms.log 307734.1 If found during the start up of Grid Control, this message is due to the Agent being down.
[Thread-5] WARN ias.util getMetricResultUtil.311 - Error getting metric opmn_process_info Error getting metric opmn_process_info rows is null emagentfetchlet.trc 286624.1 Harmless message. Also appears in emagentfetchlet.log
http: snmehl_connect: connect failed to (hostname:1157): Connection refused (error = 146) emdctl.trc N/A If found during the start up of Grid Control, this message is due to the Agent being down.
tkcrrsarc: (WARN) Failed to find ARCH for message (message:0x10) LGWR trace files 375229.1 Diagnostic messages that can be ignored
Error : Breadcrumb Message: [Orion Launcher] ERROR util.Breadcrumb .72 - Duplicate breadcrumb for page ias/ias/home emoms.trc SR Raised and Resolved Bug
DEBUG, INFO and WARN messages in emagent.trc log emagent.trc SR Raised and Resolved According to Oracle Support ANY DEBUG , INFO and WARN messages can be ignored!! However, careful attention should be applied to the messages and SR's raised for issues that look dubious.
ERROR No appenders could be found for category (oracle.sysman.eml.app.ContextInitializer) em.nohup.log SR Raised and Resolved Only an issue when using iasconsole. This is generally not required for Grid Control. Close down iasconsole when not in use. No fix available.
See this log file for error messages emagent.trc emagent.trc SR Raised and Resolved Unknown. Feature/Bug. Oracle non comital. No fix available.
11347 :: Tue May 26 16:37:26 2009::AgentLifeCycle.pm:status agent returned with retCode=1

11347 :: Tue May 26 16:37:49 2009::AgentLifeCycle.pm: Exited loop with retCode=3
emctl.log SR Raised and Resolved Feature
2009-05-26 16:37:26,091 Thread-1 WARN http: snmehl_connect: connect failed to (hostname:3872): Connection refused (error = 146)

2009-05-26 16:37:26,091 Thread-1 ERROR main: nmectla_agentctl: Error connecting to https://hostname:3872/emd/main/ Returning status code 1

2009-05-26 16:37:27,363 Thread-1 WARN http: snmehl_connect: connect failed to (hostname:3872): Connection refused (error = 146)

2009-05-26 16:37:27,363 Thread-1 ERROR main: nmectla_agentctl: Error connecting to https://hostname:3872/emd/main/. Returning status code 1
emdctl.trc SR Raised and Resolved Feature!!

Cause

See above.

Fix Step-By-Step

All of these messages can be ignored.

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License