4 Common Errors

This chapter describes the common errors you may encounter when running the Oracle Configuration Manager.

4.1 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.

4.2 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: 
"ORACLE_OCM.MGMT_DB_LL_METRICS" 
ORA-06512: at line 1

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

GRANT EXECUTE ON SYS.UTL_FILE TO ORACLE_OCM;

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.