6 Troubleshooting Oracle Configuration Manager

This chapter lists some of the errors that may occur while using Oracle Configuration Manager and provides tips to troubleshoot these errors.

Insufficient Privileges While Running installCCRSQL collectconfig

When you run the installCCRSQL.sh 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 installCCRSQL.sh 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;
```
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_HOME/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.
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 installCCRSQL.sh script.
Incorrectly configured hostnames are displayed on MetaLink with only the short names.

To ensure that hostnames are displayed with their fully qualified names on MetaLink, 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:
```
10.10.10.10  myhost.mydomain  myhost
```
If the /etc/hosts file has not been correctly configured, only the short name is displayed on MetaLink.
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.