Skip Headers
Oracle® Configuration Manager Installation and Administration Guide
Release 10.3.5

Part Number E22050-01
Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Index
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

7 Troubleshooting Oracle Configuration Manager

This chapter explains how to enable debug logging, lists some of the errors that may occur while using Oracle Configuration Manager, and provides tips on how to troubleshoot these errors.

This chapter includes the following sections:

7.1 Enabling Debug Logging

To enable debug logging by the collector, add the following property to the file.

log4j.rootCategory=DEBUG, Rolling

If the $ORACLE_CONFIG_HOME variable was defined for the deployment of the collector, the location of the file is the $ORACLE_CONFIG_HOME/ccr/config directory.

Otherwise, add the property to the <INSTALLED_PRODUCT_ROOT>/ccr/hosts/<hostname>/config/ file.

Note that debug logging of the collector consumes space. Once you have completed the debugging task, remove the added entry from the file to resume the previous behavior.

To have Perl scripts generate debugging output when the collection is run, set EMAGENT_PERL_TRACE_LEVEL=1 and run emSnapshotEnv.

To see all the steps performed throughout the execution of the setupCCR, configCCR, and deriveCCR commands, set the CCR_DEBUG environment variable to 1. We suggest that the output be redirected to a file. This enables you to send the file to Oracle Support if needed.

7.2 Errors You May Encounter

This section describes some of the errors you may encounter while you work with Oracle Configuration Manager and provides possible solutions to these errors.

7.2.1 Insufficient Privileges While Running installCCRSQL collectconfig

When you run the 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 higher, 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 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 higher, 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 pre-10g databases, 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;

7.2.2 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 <ocm_install_root>/ccr/log/collectconfig<SID>.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.

7.2.3 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 init<sid>.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 script.

7.2.4 Incorrectly Configured Hostnames Are Displayed on My Oracle Support with Only the Short Names

To ensure that hostnames are displayed with their fully qualified names on My Oracle Support, the /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:  myhost.mydomain  myhost

If the /etc/hosts file has not been correctly configured, only the short name is displayed on My Oracle Support.

7.2.5 Oracle Configuration Manager Synchronization Messages

Oracle Configuration Manager does not allow you to run multiple commands simultaneously. If you attempt to do so, the following messages may be displayed:

  • Message: Another operation is in progress. Please wait...

    Description: There are several Oracle Configuration Manager commands that cannot run concurrently. If you try to run one of these commands while another command is in progress, the second command will not be executed until the first command is completed. A message indicating that another command is in progress is displayed. The second command will automatically be run when the first command is completed.

    Commands: emCCR collect, emCCR getupdates, emCCR update_components, and emCCR upload

    Action: Initially, take no action, the second command will be executed when the first command is completed. But if the command execution takes too long, a timeout will occur. If a timeout occurs, ensure there is no Oracle Configuration Manager activity by executing emCCR stop command. Delete the ccr/state/collector.lock file and restart the Scheduler by running the emCCR start command. If you are running the command in Disconnected mode, ensure that no collection or update is taking place and then delete the ccr/state/collector.lock file.

  • Message: Operation blocked, waiting...

    Description: You cannot run the emCCR update_components command if any other emCCR command is running. If you try to run the command, it will be blocked. You also cannot run any emCCR command while emCCR update_components is running as all other commands will be blocked.

    Commands: configCCR and most of the emCCR commands

    Action: Initially, take no action, the command will get executed when the current command is completed. If a timeout occurs, ensure that there is no Oracle Configuration Manager activity by executing emCCR stop. Delete the ccr/state/semaphore.op* and ccr/state/semaphore.update* files, and restart Oracle Configuration Manager by running emCCR start. If running the command in Disconnected mode, ensure no collection or update is taking place and delete the ccr/state/semaphore.op* and the ccr/state/semaphore.update* files.

  • Message: The Scheduler is down for upgrade.

    Description: While upgrading Oracle Configuration Manager, you cannot run any of the emCCR commands.

    Commands: All emCCR commands

    Action: Retry the commands later.

7.2.6 Errors in Oracle Database Trace File

The following errors in the Oracle Database Trace file denote that the ORACLE_OCM user account does not have Execute Privilege on the UTL_FILE located in the SYS.UTL_FILE package.

ORA-12012: error on auto execute of job xxxxx 
ORA-04063: package body "ORACLE_OCM.MGMT_DB_LL_METRICS" has errors 
ORA-06508: PL/SQL: could not find program unit being called: 
ORA-06512: at line 1

To give Execute Privilege to the UTL_FILE, run the following SQL statement:


At the time of instrumentation of the database, Oracle Configuration Manager executes the ccr/admin/execocm.sql script. This script tests to see if PUBLIC access is granted to all the routines Oracle Configuration Manager needs access to. If PUBLIC access is not available, Oracle Configuration Manager grants specific access rights.If you specifically revoke PUBLIC access after installation, you will need to rerun at least the execocm.sql script. Rerunning the collecconfig.sql script accomplishes the same result.

7.2.7 Upgrade Failure on Windows

When there is an Oracle Configuration Manager upgrade failure on the Windows environment, the log file is named update2.log.

7.2.8 Database Previously Collected But Now Dropped

Customers are seeing messages similar to the following message when a database that's been previously collected but is now dropped.

WARN: Oracle Configuration Manager database objects are not in sync with the
installed configuration collection scripts. Refer to the Installation and
Configuration documentation on reloading the SQL collection packages.

Use emCCR disable_target command. The emCCR status does not look at the list of disabled targets to determine whether it conforms to the list of targets for which it should check metadata.

7.2.9 Siebel Host Name Returned Twice

Customers are seeing the host names containing Siebel services twice: once with the long name and the second with the short name.

The Siebel topology is discovered from the host that runs the Siebel Gateway Server. A host definition is created and uploaded to Oracle services with the intent that the host configuration definition will rendezvous at Oracle when an Oracle Collection Manager collector is installed on the physical host where the Siebel service runs. Due to host network configuration, the name of the host is returned as different strings; one from the gateway server and another from the physical host. It is required that all hosts within the Siebel topology be configured to return full canonic names for hosts. This is true for the Siebel Gateway server, as well as from all hosts containing Siebel services.

Reconfigure your host network to return the full canonic name for the local host. On the Gateway Server, the network configuration must return the full canonic name for all hosts that are known to participate in a Siebel system defined by the Gateway Server.

7.2.10 CCR Configuration Failure During Installation of Oracle Database Release 11.2 on Linux x86-64

Installation of the Oracle Configuration Manager fails, with the following error in $ORACLE_HOME/ccr/hosts/<hostname>/log/install-core-*.log, indicating a relink issue. The log file contains records such as:

skipping incompatible /usr/lib64/gcc/x86_64-suse-linux/4.3/libgcc.a when
searching for -lgcc
cannot find -lgcc
collect2: ld returned 1 exit status

The problem occurs on a 64-bit Linux system where the 32-bit libraries are not installed. Install the 32-bit gcc RPM and reconfigure the Oracle Configuration Manager using the command line interface: