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.

Friday, September 17, 2010

Install Oracle Enterprise Manager Grid Control 11g on IBM AIX 5.3

In this thread the installation of Oracle Enterprise Manager Grid Control 11g is explained. The installation takes place on an IBM Pseries server running AIX 5.3 TL-10.

Server requirements:

For setting up a Grid Control server using Oracle Enterprise Manager 11gR1 on AIX 5.3 a server is needed with approx. the following specs:

Operating system: AIX 5.3 TL10
Available RAM: 6Gb ( depending on the number of databases monitored, here less than 50 databases)
Available diskspace: Approx 50Gb in total.

Software requirements

Following the official installation guide, two software prerequisites are to be present and installed:

The first is the bos.perf.proctools package
The second is a Java 6 SDK. This SDK is needed for installing the Weblogic server
The minimum Service Release is 6. On the server this would show up like:

# /usr/java6_64/jre/bin/java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build pap6460sr8-20100409_01(SR8))
IBM J9 VM (build 2.4, JRE 1.6.0 IBM J9 2.4 AIX ppc64-64 jvmap6460sr8-20100401_55940 (JIT enabled, AOT enabled)
J9VM - 20100401_055940
JIT - r9_20100401_15339
GC - 20100308_AA)
JCL - 20100408_01

Please note that the above installation has a SR8 update installed.

Oracle recommends to install the Java SDK into a separate directory within the directory that will become "Middelware Home". This is to prevent accidental upgrades from the Java version, which is not supported.
Because the software packages on IBM AIX are installed with the 'smit' tool, they end up in /usr.
To follow the Oracle recommendation, the Java installation is copied into the middleware home directory ( in our case /opt/oemprd/ora/middleware).
$ cp –r /usr/java6_64 /opt/oemprd/ora/middleware/

User requirements

Create an Oracle user who will be the owner of all installations.
Add the following entries to the .profile of this user.
export JAVA_HOME=/opt/oemprd/ora/middleware/java6_64
export PATH=$PATH:$JAVA_HOME/bin
export MW_HOME=/opt/oemprd/ora/middleware/
Note that the Weblogic server will be installed in $MW_HOME/wlserver_10.3
For all below installations, this user needs to have its DISPLAY set and a valid X-Display emulator should be running on your PC
Use e.g. the following command to set the DISPLAY to the correct value:

export DISPLAY=$(who -m | cut -d\( -f2 | tr -d " \)"):0

Weblogic Server
The installation manual for Oracle Enterprise Manager 11g dictates a minimum version of Weblogic server 10.3.2. This is THE ONLY SUPPORTED version !!!!
It is important to install the Weblogic server on a server which has no Oracle software installed yet.

Download the Weblogic server from:

Unzip the downloaded file into the homedirectory of the "oracle" user.
Start the installer using:
$ java -d64 -jar wls1032_generic.jar

After extraction the welcome screen appears

Click on Next.

Enter the base directory used as "Middleware Home".

Click on Next

Because the Oracle Enterprise Manager 11g is tightly linked to Oracle Support site, we select to enter credentials here.

Click in Next

Confirm the selected Java installation to use for weblogic.
It should state the installation directory copied above in section 2.1.

Click on Next

The installer now shows the installation homes of the two weblogic parts:
Weblogic server and Oracle Coherence.
Leave the given directories as is and click on Next.
After confirming the installation summary, the installation progress screen is displayed.

After the intallation completes, unselect "Quick Start" and press Done.

Patching WebLogic Server

Before the patching of the Weblogic server can be started, make sure you have:

- Access to the Internet from the server you are installing
- Added the following hosts to /etc/hosts

Start the patch installer, using:

oemprd@vsv1h151:/opt/oemprd/ora/middleware/utils/bsu (OEMPRD)
$ -log=/tmp/bsu.log

The file /tmp/bsu.log can be optionally used for detailed logging of the actions the program takes.
It is possible that the installer first is going to update itself. You will be prompted for that.

In the below table the update walkthrough is displayed:

Afterwards it downloads the available Weblogic updates will be downloaded.
First you need to enter the credentials to access Oracle Support like shown in the figure.
After supplying the login credentials and having verified them the update installer appears.
Again the login credentials for Oracle Support are asked, as shown here.
We choose here to not enter the credentials, as:

• We don't need any Emails about updates
• There seems to be some kind of problem with the connection. It keeps returning asking for the credentials.

In the "Get Patches" Tab the Weblogic patch "WDJ7" is shown.
Select that patch and click download.
After a couple of seconds the download finishes and the patch dissappears from the screen.

Select the tab "Manage Patches".
In the lower part of the screen the downloaded patch "WDJ7" is shown.
Select the patch and click the "Apply" button.

The installer checks for any conflicts. If correct, no conflicts should be found.
Click OK to start the update

After the patch is installed it will appear in the upper part of the screen. This concludes the patch installations.
Select File, Exit to leave the patch installer.

Installation of Grid database

Install an Oracle release database and patch it with the latest patches.
At the time of writing this was

For ORACLE_HOME during this installation /opt/oemprd/ora/db/11.1.0 is used
Create a database called OEMPRD which will be used as Catalog for the Enterprise Manager server.
Ensure that all parameters have been set correctly according to the Installation Manual. These parameters are:


Because the installation and configuration of a database should be easy for DBA's working on a Grid Control installation, the procedure is not explained here.

Before continuing, make sure the database and the listener are up and running.

Installing Oracle Enterprise Manager Grid Control

Download and extract the Grid Control installation files.
Enter the directory where the files have been extracted.

Now Download the available updates for the Grid Control installation.

The commands to do so are:
oemprd@vsv1h151:/opt/oemprd/ora/home/staging (OEMPRD)
$ cd install
$ mkdir updates
$ ./utility/downloadSWUpdates -u -p -s ./updates/

Warning: It might be that the downloadSWUpdates program fails. This is because the program "thinks" you're on a 'linux' system. It tries to search for a library file in a non-existing directory called linux.
Solve this by:
$ cd /opt/oemprd/ora/home/staging/install/updates/java/oui/lib
$ ln –s aix linux
$ cd /opt/oemprd/ora/home/staging/install/updates/java/oui/bin/platform/
$ ln –s aix linux

Start the installer using the following syntax:

oemprd@vsv1h151:/opt/oemprd/ora/home/staging (OEMPRD)
$ ./runInstaller -noconfig WLS_DOMAIN_NAME=GridControl

Below the walkthrough of the Grid Control Installation:

In the first screen you're able to enter you 'My Oracle Support' Credentials. It is recommended to do so, enabling the installer to check and download available updates.

Possible screen if Check for "Download and install updates" is selected

Select Installation Type:

Select "Install a new Enterprise Manager System" as the server in this installation does not have an OEM installed.

Click 'Next'

Check Prerequisites

The installer will list all failed prerequisite checks. If needed solve the given problem and confirm if the check runs OK afterwards

Click 'Next'

Enter the installation directory of the Oracle Enterprise manager installation and the 'Middleware Home' location ( the location where Weblogic is installed)

The installer determines the given entries and they are correct most of the time.

Click 'Next'

Weblogic Server Domain.

Since Oracle Enterprise Manager 11g runs on a Weblogic environment, a weblogic domain will be created.

Specify passwords for the given Weblogic user and Node manager.

Click 'Next'

Database credentials.

Enter the database servername, Listener Port, SID and SYS password for access to the database created for this purpose.

Setup the Management repository.

Enter a password for the to be created SYSMAN user.

Confirm the file locations of the to be created tablespaces.

Click 'Next'

Enter passwords for the Management Agent registration.

Keep this password somewhere safe, as it is needed later when installing/configuring the clients

Click 'Next'

The port numbers to be used.

It is smart to keep a print of the screen, or write down the port numbers.

Click 'Next'

Installation Summary.

Click 'Next'

Although the manual states that 400Mb of temp space in /tmp is needed, the installer actually needs 936Mb (or more), as stated on the screen from which the installer started:

Space Requirements

/tmp/ Required 936MB (only as temporary space) : Available 781MB

Increase space in /tmp and afterwards continue the installation by clicking 'Yes'.

Execution of script

After running a root-script for which a dialog box appears, the configuration of the product starts.

If the configuration of OMS fails ( step 5) and the logfile shows:

FINE: Cleaning the OMS from the repository

Sep 22, 2010 11:17:34 AM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterCleanup

FINE: Got the Host URL as: null

Sep 22, 2010 11:17:34 AM oracle.sysman.omsca.framework.OMSGenericAdapter postDeployAndReposSetup

SEVERE: OMSCA-ERR:Securing of OMS failed. Check the trace file:/opt/oemprd/ora/middleware/weblogic/oms11g/cfgtoollogs/omsca/omsca_20


Sep 22, 2010 11:17:34 AM oracle.sysman.omsca.framework.OMSCAFreshInstall execute

SEVERE: Securing of OMS failed.

Sep 22, 2010 11:17:34 AM oracle.sysman.omsca.framework.OMSConfigAssistantDriver main

FINE: Got resultfalse

then the an unsupported version of WebLogic is installed .

Only version 10.3.2 is supported for Oracle Enterprise Manager 11g ( see Note: 1096766.1)

If the configuration fails at Add-on OMS side configuration, a manual fix needs to be applied to, as described here:

This page says:

While installing Oracle 11g on AIX you could hit this failure

Do not CANCEL or EXIT the installation from the GUI mode.

A check of the logfile reveals this error -

11g Grid Control installation fails at ‘ Add-on OMS Side Configuration ‘ with following error message in


at java.lang.Terminator.setup(

at java.lang.System.completeInitialization(

at java.lang.Thread.(

Caused by: java.lang.RuntimeException: Can’t recognise platform – Unix

The following file needs to be backed up and edited as follows

Go to the newly installed Oracle Management server HOME/bin folder -


Edit the file -


Look for Unix under osname and change it to AIX -



$osname = “Unix” ;





$osname = “AIX” ;


Click on RETRY and the installation completes.

This completes the installation of Grid Control 11g on AIX 5.3

Instructions on how to install the Oracle 11g Management Agent can be found here: