I Troubleshooting and Removing Oracle Configuration Manager Software

I.1 Troubleshooting Oracle Configuration Manager

This section lists some of the errors that may occur while using OCM and provides tips to troubleshoot these errors.

• Insufficient Privileges While Running installCCRSQL collectconfig

  When you run the installCCRSQL.exe script, it creates the ORACLE_OCM user and sets up a job to collect database configuration information. The ORACLE_OCM user requires EXECUTE privileges on UTL_FILE and DBMS_SCHEDULER for database versions 10g or later, and on the DBMS_JOB for pre-10g databases. If these privileges are granted to PUBLIC, the ORACLE_OCM user inherits these privileges, otherwise these privileges are explicitly granted when the installCCRSQL.exe script is executed. If the inherited privileges are revoked, the following errors indicating the lack of privileges will be logged in the alert_log:

  ORA-12012: error on auto execute of job 52
  ORA-04068: existing state of packages has been discarded
  ORA-04063: package body "ORACLE_OCM.package_name" has errors
  ORA-06508: PL/SQL: could not find program unit being called
  

  To resolve these errors, you must grant the missing EXECUTE privilege to the ORACLE_OCM user.

  • For database versions 10g and later, grant EXECUTE privileges on the UTL_FILE and DBMS_SCHEDULER packages to the ORACLE_OCM user by entering the following SQL*PLUS commands:

    SQL> grant execute on UTL_FILE to oracle_ocm;
    SQL> grant execute on DBMS_SCHEDULER to oracle_ocm;
    SQL> ALTER PACKAGE oracle_ocm.MGMT_DB_LL_METRICS compile;
    SQL> ALTER PACKAGE oracle_ocm.mgmt_config compile;
    

  • For versions prior to Oracle Database 10g, grant EXECUTE privileges on the DBMS_JOB package to the ORACLE_OCM user by entering the following SQL*PLUS commands:

    SQL> grant execute on UTL_FILE to oracle_ocm;
    SQL> grant execute on DBMS_JOB to oracle_ocm;
    SQL> ALTER PACKAGE oracle_ocm.MGMT_DB_LL_METRICS compile;
    SQL> ALTER PACKAGE oracle_ocm.mgmt_config compile;
    

• ORA-04021 Error

  There may be cases when the ORACLE_OCM user needs to be granted the required privileges during installation. While granting the privileges, the following error may occur in the ORACLE_BASE\ORACLE_HOME\ccr\log\collectconfigSID.log:

  ORA-04021: timeout occurred while waiting to lock object SYS.<package like UTL_FILE>
  

  This error may occur if another procedure is using the package for which the privileges are being granted. To resolve this error, retry the install when the package is not being used. This error may occur while granting privileges on UTL_FILE, DBMS_SCHEDULER, or DBMS_JOB.

• ORA-01925 Error While Running installCCRSQL

  This error may occur if the value of the MAX_ENABLED_ROLES initialization parameter has been exceeded. To resolve this error, you must increase the value of the MAX_ENABLED_ROLES parameter and restart the database as follows:

  1. Edit the initsid.ora file where sid is the database system identifier and increase the value of MAX_ENABLED_ROLES. If a server parameter (spfile) has been used, alter the MAX_ENABLED_ROLES parameter by using the following SQL*PLus command:

     SQL> alter system set MAX_ENABLED_ROLES=value scope=spfile
     

  2. Restart the database.

  Once the database has been restarted, re-run the installCCRSQL.exe script.

• Incorrectly configured hostnames are displayed on OracleMetaLink with only the short names.

  To ensure that hostnames are displayed with their fully qualified names on OracleMetaLink, the %windir%\system32\drivers\etc\hosts file must contain an entry that includes both the hostname and the domain in the following format:

  IP-Address  Full-HostName  Short-HostName
  

  For example:

  10.10.10.10  myhost.mydomain  myhost
  

  If the hosts file has not been correctly configured, only the short name is displayed on OracleMetaLink.

I.2 Removing Oracle Configuration Manager

To uninstall OCM, follow these steps:

1. If the ORACLE_BASE\ORACLE_HOME directory contains a database, remove the Oracle Configuration Manager user and the associated objects from the database by running the following script:

   SQL> ORACLE_BASE\ORACLE_HOME\ccr\admin\scripts\dropocm.sql
   

2. If the database is a repository for the Oracle E-Business Suite, log in to the database as an SYSDBA user and remove the additional objects from the database by running the following script:

   ORACLE_BASE\ORACLE_HOME\ccr\admin\scripts\ebs_dropccr.sql Oracle_Applications_User
   

3. If the database is a repository for Oracle Grid Control, log in to the database as the SYSMAN user and remove the additional objects from the database by running the following script:

   ORACLE_BASE\ORACLE_HOME\ccr\admin\scripts\dropemrep_collect.sql
   

4. To stop the Scheduler and remove the service, enter the following command:

   ORACLE_BASE\ORACLE_HOME\ccr\bin\deployPackages -d ORACLE_BASE\ORACLE_HOME\ccr\inventory\core.jar
   

5. Delete the ccr directory by entering the following command:

   SYSTEM_DRIVE:\> rmdir /S ORACLE_BASE\ORACLE_HOME\ccr
   

   OCM is successfully uninstalled.