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

6 Managing the Oracle Configuration Manager Client

This chapter describes the various command line options that are available to manage the Oracle Configuration Manager client.

The Root user can perform diagnostic upload, diagnostic status, and diagnostic clear commands. In addition, Root user can perform configuration collection in connected and disconnected mode.


The <ocm_install_root> represents the directory in which the Oracle Configuration Manager common code is installed.

ORACLE_CONFIG_HOME is an environment variable used to define the location of instance-specific data in a shared home environment.

The following commands are described:

6.1 emCCR automatic_update on / off

6.2 emCCR clear - diagnostic

6.3 emCCR collect

6.3.1 emCCR -annotation="annotation string" collect

  • Usage: Use this command to manually collect configuration data. If you want to annotate the data collected, use the -annotation option. You can also run this command in Disconnected mode.

  • Execute Privileges: Can be executed by <ocm_install_root> owner or user ROOT

  • Prerequisites: None

  • Example:

    <ocm_install_root>/ccr/bin/emCCR -annotation="annotation string" collect
    Oracle Configuration Manager - Release: - Production
    Copyright (c) 2005, 2011, Oracle. All rights reserved.
    Collection and upload done.

6.4 emCCR enable_diagchecks | disable_diagchecks

6.5 emCCR enable_target | disable_target

6.6 emCCR getupdates

6.7 emCCR help

6.8 emCCR hold

6.9 emCCR register

6.10 emCCR resume

6.11 emCCR set collection_interval

6.12 emCCR start

6.13 emCCR status -diagnostic

6.14 emCCR stop

6.15 emCCR [-register] [-verbose] test

6.16 emCCR update_components

6.17 emCCR upload

6.18 emCCR upload -diagnostic

6.19 configCCR


Use this command to modify the configuration information using the command line interface. This command enables you to modify the registration credentials after Oracle Configuration Manager has been installed. You can also use this command to switch between Connected and Disconnected modes, and to configure Diagnostic Checks properties. The syntax is as follows:

configCCR [ -s ] [ -d | -C <OracleSupportHubUrl> ] [ -a | -r ] [<csi-number>
[<MyOracleSupportId> ]]

configCCR [ -R <response-file> ] 

configCCR -D [ -v ] [ -T <target type> [ -N <target name> [ -P <property name> ]]]
  1. If you do not specify any arguments and you can connect directly to Oracle, you are prompted for credentials.

  2. If you do not specify any arguments but you cannot connect directly to Oracle, the following occurs:

    1. You are prompted for credentials.

    2. You are prompted for an Oracle Support Hub.

    3. If you cannot access the Oracle Support Hub specified or you entered NONE, you are prompted for the proxy server.

      • Either enter a proxy server or type NONE.

      • If you entered NONE for both Oracle Support Hub and proxy server, Oracle Configuration Manager is configured in disconnected mode.

    4. If you specified a proxy server but you still cannot access Oracle, you will be prompted for Oracle Support Hub again.

      • Supply the URL for the Oracle Support Hub or type NONE.

    You will be prompted for Oracle Support Hub and possibly proxy server until there is connectivity to Oracle or you type NONE for both the Oracle Support Hub and proxy server.


Execute Privileges

Can be executed by <ocm_install_root> owner. Only the same user as the owner of the <ocm_install_root> directory can configure additional Oracle Configuration Manager instances.


The following restrictions apply when you install Oracle Configuration Manager:





Some of the error messages you may see are the following:

6.20 deriveCCR

Note: Before using the deriveCCR command, refer to Section 3.7, "Setting Up Oracle Configuration Manager in a Cloned Home".


Use this command to configure Oracle Configuration Manager in an Oracle Home that has been cloned. Execute this command from the ccr directory in the cloned home.

The syntax is as follows:

deriveCCR [ -d | -C <OracleSupportHubUrl> ] [ <csi-number> <MyOracleSupportID> ]
deriveCCR [ -R <response-file> ] 

Before executing deriveCCR, ensure that the environment variables needed to configure Oracle Configuration Manager in the cloned Oracle home are set. Of special importance is the ORACLE_CONFIG_HOME environment variable. If ORACLE_CONFIG_HOME was used in the original home environment, then you must set this variable to the cloned home environment before executing deriveCCR.

The JAVA_HOME used for Oracle Configuration Manager is determined in the following order:

  1. If the JAVA_HOME variable is set for the environment, that is the variable used.

  2. If the JAVA_HOME variable is not set, but there is a JDK or JRE in the cloned home, that is the path used.

  3. Otherwise, the JAVA_HOME variable is determined from the Oracle Configuration Manager properties in the source home.


Execute Privileges

Can only be executed by <ocm_install_root> owner.


On UNIX, if the source home was in disconnected mode, you are prompted for credentials so Oracle Configuration Manager will be configured in connected mode.


Oracle Configuration Manager had to have been configured in the original source home.



If deriveCCR cannot configure the Oracle Configuration Manager in the cloned home, it returns an appropriate error.