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

5 Oracle Configuration Manager Administration

This chapter contains the following sections:

5.1 Collecting Configuration Data (Connected Mode)

Configuration data is automatically collected on a regular schedule. By default, collections are scheduled to run once a day at the time the original installation was done. Therefore, no matter how many times you view the data within that 24 hour time period, the data will remain the same until the time of the next collection.

To start a manual collection of configuration data, enter the following command:

<ocm_install_root>/ccr/bin/emCCR collect

This command collects the configuration data and uploads it to the server located at Oracle. Configuration data is collected only if the Scheduler has been started. The Scheduler is always running unless it has been manually stopped with the emCCR stop command. In this case, you will have to manually restart the Scheduler so that configuration data can be automatically collected. Check the status of the Scheduler by entering emCCR status which indicates whether the Scheduler has been started. To start the Scheduler, enter the following command:

<ocm_install_root>/ccr/bin/emCCR start

5.1.1 Using the Scheduler to Collect Configuration Data

The Scheduler acts as a coordinator of activities, and provides both a richer schedule capability and the ability to perform collections on a regular schedule. Scheduled collections are only available when Oracle Configuration Manager is running in Connected mode.

Configuration data can be collected daily, weekly, or monthly, at a particular date and time. You can set the interval for automatically collecting the configuration data with the emCCR set collection_interval command.

The emCCR stop, emCCR set collection_interval, emCCR hold, emCCR resume, emCCR getupdates, and emCCR upload commands can be used only if the Scheduler has been started.

For more information on these commands, refer to Chapter 6, "Managing the Oracle Configuration Manager Client".

5.2 Collecting Configuration Data (Disconnected Mode)

If you are using Oracle Configuration Manager in Disconnected mode, configuration data needs to be manually collected. As the Scheduler is not running in this mode, it cannot be used to automatically collect configuration data at regular intervals.

You can collect configuration data manually by using the emCCR collect command. When you run this command, the ocmconfig.jar is created in the OCM_CONFIG_HOME/state/upload/ directory. This file contains the manually collected configuration data. You can then upload this file to Oracle by way of My Oracle Support from another system that has internet access. For more details on manual collection of configuration data, refer to Section 6.3, "emCCR collect".

In this mode, the only commands supported are emCCR collect, emCCR status, emCCR enable_target, emCCR disable_target, emCCR update_components, configCCR, and emCCR help.

5.3 Updating Oracle Configuration Manager

You can update Oracle Configuration Manager either manually or automatically.


Automatic updates are not possible if Oracle Configuration Manager is installed on a shared, read-only file system. In this situation, the automatic update feature should be disabled and all updates performed manually.

5.4 Disabling Collection of IP, MAC, and Broadcast Addresses

You can disable the collection of the Host IP Address, the Network Interface MAC Address, and the Broadcast Address. To disable the collection of these items, you must add the following entries to the OCM_CONFIG_HOME/config/ file.

5.5 Disabling the Collection of Database Columns

You can disable the collection of certain database columns by using data masking. Masking data means replacing certain fields with a mask character, such as an X.

All masking operations are defined in the file located in the $ORACLE_HOME/ccr/hosts/<hostname>/config/ directory or the $ORACLE_HOME/ccr/config/ directory.

5.6 Enabling the Default Collection of NFS Disk Information

The NFS mounted file system information is no longer collected by default. Only local file system information is collected by default.

To enable the collection of NFS mounted file system information, add the following entry to the OCM_CONFIG_HOME/config/ file.

5.7 Creating a Response File

In support of mass deployment using a scripted installation, Oracle Configuration Manager installation and configuration supports the ability to create and specify a response file. The response file contains all the user required input needed when running the setupCCR and configCCR commands.

To specify the response file with the setupCCR and configCCR commands, use the -R qualifier with the <response file> argument.

configCCR [-R <response file>]
setupCCR [-R <response file>]

To create a response file, use the emocmrsp response generation utility, located in the $ORACLE_HOME/ccr/bin directory. This utility walks you through the interrogation phase of an installation and records your responses to the prompts. The information is recorded in an Oracle Configuration Manager private format response file. By default, the response file is created in the current directory with the file name ocm.rsp. To view the contents of the response file, use the -verbose option on the command line.


To create a response file that installs but does not configure Oracle Configuration Manager, click ENTER when prompted for the e-mail address and specify Yes when asked to confirm if you want to remain uninformed.

To create the response file, enter the following command:

emocmrsp [-output <response-file>] [-help] [-no_banner] [-repeater <URL>] [<CSI>
                      [<MyOracleSupportUserName>] ] 
         [-verbose <response-file>] 
         [-verify <response-file>]

The following qualifiers are allowed:

Qualifier Description
<CSI> To use Customer Support Identifier for registration, enter CSI at the end of the command line. You can either enter the MyOracleSupportUserName on the command line or be prompted for it.

Note: If CSI is not specified, you will be prompted for the My Oracle Support User Name (e-mail) and Password.

<MyOracleSupportUserName> My Oracle Support User Name holding the CSI in its My Oracle Support profile.
-help Displays this usage information.
-no_banner Indicates the banner for the response utility is not to be displayed.
-output <response_file> Creates a response file with the name specified. If you do not specify this qualifier, the response file is created in your current working directory with the file name ocm.rsp.
-repeater <URL> Indicates the URL of the Oracle Support Hub.
-verbose <response-file> Displays contents of the response file specified.
-verify <response-file> Verifies that the contents of the response file are valid.



OCM Installation Response Generator - Production
Copyright (c) 2005, 2011, Oracle.  All rights reserved.

Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your My
Oracle Support Email address/User Name.
Visit for details.
Email address/User Name:
Provide your My Oracle Support password to receive security updates via your My Oracle Support account.
Password (optional):           
The OCM configuration response file (ocm.rsp) was successfully created.


Example Using -verbose Qualifier

This example displays the contents of a response file.

$ORACLE_HOME/ccr/bin/emocmrsp -verbose <response_file>

OCM Installation Response Generator - Production
Copyright (c) 2005, 2011, Oracle and/or its affiliates.  All rights reserved.
Response file created: Jan 3, 2011 3:09:29 PM
Created by: jsmith
License agreement: accepted
Connected configuration state: connected
Proxy configuration: (none specified)
Oracle Support Hub:
Response file registration via: My Oracle Support username
My Oracle Support registration username:

Example Using -verify Qualifier

$ORACLE_HOME/ccr/bin/emocmrsp -verify <response_file>

OCM Installation Response Generator - Production
Copyright (c) 2005, 2011, Oracle and/or its affiliates.  All rights reserved.
Configuration connectivity verified successfully.

5.8 Verifying Environment Variables

For a given environment, the administrator installing Oracle Configuration Manager sets things so that all the parts of that environment are functioning properly. Part of that set up is determining the environment variables used in Oracle Configuration Manager.

To run the configuration collection, Oracle Configuration Manager needs to be in sync with the given environment. The emSnapshotEnv script (shell script on UNIX; Visual Basic script on Windows) captures the values of the environment variables required by Oracle Configuration Manager. The environment variables are listed in Table 5-1:

Table 5-1 Environment Variables Used in Oracle Configuration Manager

Environment Variable Description Used on UNIX Used on Windows


Used for WebLogic Server




Used for clustering




Used for clustering




Used for Oracle E-Business Suite




Must point to an appropriate JDK directory




Used to define the location of instance-specific data in a shared home environment.




This is the default.




Used for WebLogic Server



5.9 Evaluating System Health

The diagnostic health check evaluation (Diagnostic Checks) feature performs diagnostic health checks against your installations and generates diagnostic results that are uploaded to Oracle. The Diagnostic Checks feature is included in the regular Oracle Configuration Manager configuration collection. Oracle Support uses these results to provide efficient and timely resolution to requests for assistance.

The Diagnostic Checks feature is enabled by default, however the associated package required to collect the diagnostic data is not available until you manually download it from Oracle. To use the Diagnostics Checks feature:

  1. Download the Diagnostic Checks package from the location provided to you by your Oracle Support representative.

  2. Copy the package to a directory on your system and deploy the package into your environment using the emCCR update_components -staged_dir <location_of_package> command.

    The package might require configuration. After the installation, run the configCCR -D -v command to determine if there are properties to be configured. Running the emccr status command after the first collection identifies that there are properties that need to be configured for a target diagnostic check collection. To configure properties, use the configCCR -D command.

  3. Perform a collection using the emCCR collect command.

  4. Diagnostic Checks information is collected and uploaded to Oracle.

5.9.1 Turning Off Specific Diagnostics Checks

The collector uses diagexclude target .ini files to determine if any diagnostics checks need to be excluded from a collection. Diagnostics checks can be excluded on a per target basis.To exclude certain diagnostics checks:

  1. Copy

    OCM_CONFIG_HOME/config/diagchecks_exclude/diagexclude.template file
    OCM_CONFIG_HOME/config/diagchecks_exclude/diagexclude_<target_type>.ini file
  2. Edit the diagexclude_<target_type>.ini file.

The format of the diagexclude_<target_type>.ini file is as follows:



Fields Description
excludeAll Disables all diagnostic checks. When this field is present, all subsequent exclusions are ignored. This field is optional.
ExcludedGroups Section header for the names of the groups excluded for the target type
GroupName1 Name of the group. Group name is defined in the diagcheck metadata and script files located in the OCM_INSTALL_ROOT/diagchecks/<target_type> directory.
ExcludedChecks Section header for the names of the checks excluded for the target type
CheckName1 Name of the check. Check name is defined in the diagcheck metadata and script files located in the ccr_home/diagchecks/<target_type> directory.

Example of a group

$ cat ccr/diagchecks/host/DiagMetadata.xml check1.xml  check2.xml
<?xml version="1.0" encoding="windows-1252" ?>
<DiagMetadata TYPE="host" VERSION="1.0">
  <DiagGroup NAME="group1" FILENAME="check1.xml"> </DiagGroup>
  <DiagGroup NAME="group2" FILENAME="check2.xml"> </DiagGroup>

Example of a check

$ ls ccr/diagchecks/host/DiagMetadata.xml  check1.xml  check2.xml
$ cat ccr/diagchecks/host/check2.xml
 <DiagnosticCheck NAME="mycheck1">
 <DiagnosticCheck NAME="mycheck2">

Example of disabling a group and check