Search this Blog

Thursday, September 23, 2010

Using Oracle Configuration Manager

In this section the installation/configuration of Oracle's Configuration Manager is explained.

What is this Configuration Manager?

Oracle's Configuration Manager is a tool that enables users to link their Oracle database configuration to an account on the Oracle Support site.

The advantages are huge !!

By linking your system to the Oracle Support Site the system is analyzed, checked and monitored constantly. This means that Oracle Support is able to warn you up front of any problem, risk or abnomality in your configuration.

Next to that the Oracle Support Site offers you - the customer - the possibility to browse your own system in a graphical manner.
If you browse to the Support Site a Window is shown, called "Systems".

This window will be empty in the beginning, because you didn't link any systems to Oracle Support before as shown here:

Also other windows like 'Patch and Health Recommendations' show no information.

Setup Configuration Manager:

In order for configuration Manager to start doing his job, make sure that:

  • There is an Internet connection from the database server configured.
  • You are logged in as the owner of the Oracle database.
Browse to the directory $ORACLE_HOME/ccr.
This is the base directory for the Configuration Manager.

$ cd $ORACLE_HOME/ccr

Now start the Setup of the Configuration Manager :

$ ./bin/setupCCR

The system will ask you for a valid Oracle Support Account. This account should be able to manage systems on the MOS site.

Provide your email address to be informed of security issues, install and
initiate Oracle Configuration Manager. Easier for you if you use your MetaLink
Email address/User Name.
Visit for details.
Email address/User Name:
Provide your MetaLink password to receive security updates via your MetaLink account.
Password (optional):

The system starts configuring "Configuration Manager"

** Installing base package **
Deploying core - Version

** Registering installation with Oracle Configuration Manager server(s) **
Deploying engines - Version
Deploying metricdata - Version
Deploying scripts - Version
Deploying urda - Version

** Getting package updates from ContentServer **

Oracle Configuration Manager has been configured in connected mode. If the
target ORACLE_HOME is running a database, please refer to the
"Post-installation Database Configuration" section of the OCM Installation
and Administration Guide
( to complete the

View configuration data reports and access valuable configuration best
practices by going to MetaLink.

After the configuration is finished, the database needs to be configured too. Before running the configuration script make sure that the parameter UTL_FILE_DIR contains access to the $ORACLE_HOME/ccr/state directory. It might be needed to bounce the database since this parameter is a static parameter.

Now run the database configuration script. You might be prompted for the database instance name and/or the password. If ORACLE_SID is set and the database can be reached through OS-authentication, the script will just configure that database, without asking anything:

$ ./admin/scripts/ collectconfig
Successfully installed collectconfig in the database with SID=ORCL.

Now run the first collection to be uploaded to Oracle Support.

./bin/emCCR collect

This forces the Configuration Manager to upload the current configuration. At this time there is also a daemon running that will upload configurations once a day. The output of the above statement should look like:

$ ./bin/emCCR collect
Oracle Configuration Manager - Release: - Production
Copyright (c) 2005, 2010, Oracle and/or its affiliates. All rights reserved.
Collection and upload done.

This completes the installation.

Now login to the Oracle Support Site using the same account as used during the setup. As soon as the Dashboard appears, we are looking for a Window called "Task: Associate Collections". If this window is now shown, click on the link "Customize Page..." and drag this window to a slot on the Dashboard.

Note: This window will only stay visible if there any Collections to be Associated, so probably the window will not be shown initially, unless there is already one configuration uploaded and waiting to be associated.
This window is used to link a System to a Support Identifier. Please take care, because this action can only be done once and can not be reverted !!!

The window looks like below:

Select the correct support Identifier from the pull-down menu saying "Select a Support Identifier" and Click on the "Associate" button in the bottom corner of the Window.

As soon as all the Associations are successfull, this Task window will dissappear again.

This completes the setup of the Configuration Manager. Now you're able to browse the System and receive Patch warnings.


  1. Thankk you so much .This doc is very helpful.What about installation on linux boxes.

  2. @Chandu,

    Thanks for your comment.

    I must confess we don't have Linux boxes with Oracle, but I assume it's all the same

  3. Hi FJ,

    Did you come across any articles or blogs that reviewed the OCM pros and cons, like benefits or privacy concerns in using this tool?

  4. Hi Simon,

    Come across....No!
    But if you Google around a bit, you quickly find e.g. this site:

    It shares the most common 'Uncle Sam is watching you' worries we all have about these kind of tools. In the beginning I was ( and in fact still am ) very reserved in which systems of ours to activate this OCM on. I selectively configure and start the configuration manager on systems which we have to create S/R's for.
    And again, as with all these tools linked to a support organization, they still ask you for the usual stuff, even if a configuration manager uploaded system has been attached to the S/R.

    BUT I must also confess that I am very very positive about the possibilities offered on the MOS site. Your system is analyzed, checked and you receive automatically an overview of the health of your database system, which patches should be installed etc..etc..

    I suggest you configure one system to see what is does. If it does not meet your expectations, remove it ( remember to remove the crontab entry ) and delete the system on MOS.