Oracle Configuration Manager For Ex A Data

An Oracle White Paper
February, 2012
Oracle Configuration Manager

for Oracle Exadata Database Machine
Introduction ....................................................................................... 2
Terminology....................................................................................... 2
Benefits of Deploying OCM for Exadata ............................................ 2
Before you start ................................................................................. 2
Pre-requisites .................................................................................... 3
Compute node SerialNumbers file permissions ............................. 3
Options available for configuring Oracle Configuration Manager collections for an
Oracle Exadata Database Machine ................................................... 4
Configure OCM collections for Exadata using the Enterprise Manager Cloud
Control 12c Harvester........................................................................ 6
Step 1 - Configure OCM in each OMS Oracle Home ..................... 6
Step 2 - Assign CSIs to the Exadata targets. ................................. 7
Configure OCM collections for Exadata using the Mass Deployment utility to
deploy standalone OCM collectors to each Oracle Home on each compute node
........................................................................................................ 10
Step 1 - Download and Install the Mass Deployment utility .......... 10
Step 2 - Mass Deployment Input File Creation............................. 11
Step 3 - Determine the current state of OCM in each compute node Oracle
home ........................................................................................... 14
Step 4 - Deploying/Configuring OCM ........................................... 15
Step 5 - Determine the state of OCM in each compute node Oracle home after
deployment .................................................................................. 18
Manually install OCM version 10.3.6 or above into each Oracle Home on each
compute node.................................................................................. 20
Configuring OCM in disconnected mode ..................................... 20
Problems you may experience ........................................................ 21
Appendices ..................................................................................... 22
Appendix A Exadata Configuration Worksheets........................ 22
Appendix B - Configuration Table Entries for OCM ...................... 24
Appendix C - Secure Password Entry .......................................... 26
Appendix D - Testing the link to Oracle........................................ 27
Introduction
This document is intended to assist in deploying and configuring Oracle Configuration
Manager (OCM) collections for an Oracle Exadata Database Machine (updates to this
document will be made available via the Oracle Support Portal).
Terminology
Throughout this document the terms Compute node and Database Server are used
interchangeably to refer to the Oracle Exadata Database Machine Database Servers. The
terms are synonymous.
Benefits of Deploying OCM for Exadata

When you install Oracle Configuration Manager (OCM) and upload your Oracle Exadata
Database Machine configurations, you start realizing the following benefits:
Simplification of the SR creation process and faster problem resolution from

integrating your configuration information into the service request flow providing Oracle
Support the information they need, real-time, to resolve your problem quickly and
efficiently
Simplified configuration management, benefiting from a single, comprehensive and

personalized dashboard of Oracle Exadata Database Machine configurations, projects and
inventory. See the Oracle Configuration Manager Collection Overview, Chapter 18,
Oracle Exadata Storage Server Software Collections for details of the configuration
information collected by OCM.
Enable Oracle's Proactive Health Check capabilities. Health Check rules are run
against your Oracle Exadata Database Machine collections and any known issues found
are shown to you in the Health Recommendations area within My Oracle Support. Note
868955.1 My Oracle Support Health Check Catalog lists the current set of Health Checks
for Oracle Exadata Database Machines. Health Checks are being added continually to
improve the benefits of this service.
Before you start

Before proceeding with this document, ensure that you have the information listed below.
Note: This information is likely to be available in the Exadata Database Machine

configuration worksheets that were used to setup the Oracle Exadata Database Machine.
Please see Appendix A for examples. Appendix B provides a data collection worksheet
that can be used to collect all of the required information.
1. Host-Name, Host-User, Host-Password for each compute node (database server)
2
2. Oracle Home, Oracle SID, sysdba username, sysdba password for each database
running on each compute node.
3. A valid My Oracle Support user name (email address) with the valid Hardware
Customer Support Identifier (CSI) for the Oracle Exadata Database Machine
registered and approved.
4. URL, username and password for Enterprise Manager Cloud Control 12c that
monitors the Oracle Exadata Database Machine targets - if Enterprise Manager
Cloud Control 12c is in use.
5. Proxy details - hostname, port, (username and password if required) - if a proxy is

required for the compute nodes to connect to My Oracle Support.
6. Oracle Support Hub URL if the compute nodes have no way of connecting to
My Oracle Support and need to upload to an Oracle Support Hub.
Pre-requisites
Compute node SerialNumbers file permissions
Many services available in My Oracle Support (MOS) are dependent upon the validation
of the host server serial number being covered under an active support contract. If you
are running Exadata software prior to version 11.2.2.4.0, please run the following
commands on each compute server node. These commands only have to be executed
once. This ensures the capture of serial number data by the OCM collectors.
As the root user enter:

# chmod +r /var/log/cellos/SerialNumbers
# grep SerialNumbers /opt/oracle.cellos/vldrun
If the grep command returns no rows, run the following command:

#sed -i '/find.*-perm.*-exec chmod/aif \[ -e \/var\/log\/cellos\/SerialNumbers \]\;
then chmod go+r \/var\/log\/cellos\/SerialNumbers\; fi\n' /opt/oracle.cellos/vldrun
Note: The sed command adds the line:

if \[ -e \/var\/log\/cellos\/SerialNumbers \]\; then chmod go+r
\/var\/log\/cellos\/SerialNumbers\; fi
to the file /opt/oracle.cellos/vldrun. This allows vldrun to ensure the privileges are correct on the
SerialNumbers file. If the command is run repeatedly, duplicate lines will be repeatedly added to the
vldrun file. This does not cause any problem but should be avoided. Duplicate lines can be manually
removed from the file.
3
Options available for configuring Oracle Configuration Manager

collections for an Oracle Exadata Database Machine
With the release of Enterprise Manager Cloud Control 12c, the Oracle Harvester has been
improved over previous versions so that it now supports the same collections as a
standalone OCM installation.
There is now no difference in data uploaded to My Oracle Support when using standalone
OCM or the Enterprise Manager Cloud Control 12c Oracle Harvester. Additionally,
Enterprise Manager Cloud Control 12c has been extended to provide a means of
specifying, and changing, the CSI for each Oracle Home on a host, and therefore it is now
possible to associate each Oracle Exadata Database Machine with its own CSI when the
Oracle Harvester is used.
This functionality was not available in previous releases of Enterprise Manager and
therefore it is not possible to use the Oracle Harvester for Oracle Exadata Database
Machine OCM collections prior to Enterprise Manager Cloud Control 12c.
These new capabilities of the Enterprise Manager Cloud Control 12c Oracle Harvester
make it the obvious choice for customers who have an Enterprise Manager Cloud Control
12c deployment that can upload to My Oracle Support as this option removes the
requirement to deploy and maintain OCM on each of the compute nodes.
Without Enterprise Manager Cloud Control 12c, it is necessary to deploy OCM in each
Oracle Home on each of the compute nodes, including both the Database Oracle Homes
and the Grid Infrastructure Oracle Homes. Since, even for the smaller variants of the
Oracle Exadata Database Machine, this results in the need to deploy a large number of
OCMs, it is useful to use the Mass Deployment utility, rather than manually deploying
each OCM, especially if it is likely that the exercise is to be repeated on several Oracle
Exadata Database Machines. The investment in time taken to become familiar with the
Mass Deployment utility will pay off the more it is used.
If the Oracle Exadata Database Machine compute nodes do not have direct connectivity
to My Oracle Support then the OCMs deployed in each of the compute node Oracle
Homes can be configured to upload via a proxy, via an Oracle Support Hub or via a
combination of both.
When the Oracle Exadata Database Machine compute nodes are on a network that has no
means of accessing My Oracle Support, with no option to use a proxy or an Oracle
Support Hub then it is possible to configure OCM in each Oracle Home in disconnected
mode. In this case, the Mass Deployment Utility cannot be used since the Mass
Deployment Utility itself requires connectivity to My Oracle Support as part of the
deployment process. OCM must therefore be installed manually in each Oracle Home on
each compute node.
4
The following flowchart can be used to advise on the most appropriate option for your
environment:
Deploy OCM for

Exadata
Is the Oracle Exadata Database

Machine monitored by Enterprise
Manager Cloud Control 12c?
Yes No
Is Enterprise Manager Cloud No

Control 12c able to upload to My
Oracle Support either directly or via
a proxy?
Yes Are the compute nodes able to

upload to My Oracle Support either
directly or using a proxy? (see
No Testing the Link to Oracle)?
Yes
Follow the instructions to

Follow the instructions to Configure OCM for Exadata using the Mass Deployment utility
Configure OCM for Exadata using the Enterprise Manager or
Cloud Control 12c Harvester Manually install OCM version 10.3.6 or above into each Oracle
Home on each compute node.
Yes Is there a host that the compute No

nodes can connect to that can
upload to My Oracle Support (see
Testing the Link to Oracle)?
Follow the instructions to Configure OCM for Exadata using

the Mass Deployment utility using the option to upload via
an Oracle Support Hub Follow the instructions to Manually install OCM version
or 10.3.6 or above into each Oracle Home on each compute
Manually install OCM version 10.3.6 or above into each node in disconnected mode
Oracle Home on each compute node using the option to
upload via an Oracle Support Hub.
Note: Please ensure that the network configuration applicable to your specific
environment is implemented and functioning before OCM is deployed and/or configured
using either of the methods outlined in this document.
5
Configure OCM collections for Exadata using the Enterprise

Manager Cloud Control 12c Harvester
The Oracle Harvester and all necessary sub-components are automatically installed when
you install Enterprise Manager Cloud Control 12c. The only steps that need to be
performed are to configure OCM in each of the OMS Oracle Homes and to assign the
relevant CSIs to your Exadata targets.
Step 1 - Configure OCM in each OMS Oracle Home

The Oracle Harvester requires OCM to be configured and running in connected mode in
each OMS home before it can run.
To achieve this, perform the following steps on each OMS host.
1. Locate the OMS config home.
In the $ORACLE_HOME/sysman/config/emInstanceMapping.properties file

(where ORACLE_HOME is the Oracle Home of the OMS), there is an entry
referencing a file called emgc.properties.
The directory in which the emgc.properties file is located is the "config home" of
the OMS. In the following example
/u01/app/oracle/product/gc_inst/em/EMGC_OMS1 is the config home of the
OMS:
EMGC_OMS1=/u01/app/oracle/product/gc_inst/em/EMGC_OMS1/emgc.properties
2. Set the environment variable ORACLE_CONFIG_HOME to the config home of

the OMS. For Example:
$export ORACLE_CONFIG_HOME=/u01/app/oracle/product/gc_inst/em/EMGC_OMS1
3. Change to the directory $ORACLE_HOME/ccr/bin and list its contents.
If the file setupCCR exists, OCM has never been configured for this
ORACLE_HOME, use setupCCR [CSI_number] to configure OCM.
For example (using 12345678 as the CSI):

$ cd $ORACLE_HOME/ccr/bin
$ ./setupCCR 12345678
Otherwise, use configCCR r then configCCR a to first remove the previous

OCM configuration and then add a new one (to ensure that it is configured
correctly).
6
For example (using 12345678 as the CSI):
$ cd $ORACLE_HOME/ccr/bin
$ ./configCCR -r
$ ./configCCR a 12345678
Notes:
i. The CSI number should be the one that Enterprise Manager Cloud
Control 12c Oracle Home itself will be associated with. If this is
not known, do not specify a CSI Number and OCM will use the
default CSI of the provided My Oracle Support account, which you
will be prompted for. You will be prompted for the password for
that account only if you have not provided a CSI number.
ii. The My Oracle Support account you provide is used to upload the
configuration data to My Oracle Support. This account needs to
have privileges on the CSI for the OMS and the HW CSI for the
Exadata targets in order to be able to allocate the HW CSI to the
Exadata targets uploaded by the Oracle Harvester.
iii. You must provide either the CSI that you would like to use for the
OMS or the password for the My Oracle Support user specified. If
neither a CSI nor a password is provided, OCM will be configured
in 'anonymous' mode and you will not see any of the data uploaded
to My Oracle Support.
4. Verify that OCM has been configured successfully in the OMS Oracle Home by
examining the output of the emCCR status command.
Example:
$ ./emCCR status
Oracle Configuration Manager - Release: 10.3.6.0.2 Production
Copyright (c) 2005, 2011, Oracle and/or its affiliates. All rights
reserved.
------------------------------------------------------------------
Start Date 02-Dec-2011 04:40:29
Last Collection Time 12-Jan-2012 04:39:00
Next Collection Time 13-Jan-2012 04:39:00
Collection Frequency Daily at 04:39
Collection Status idle
Log Directory /u01/app/oracle/MW/oms/ccr/hosts/myOMShost/log
Registered At 02-Dec-2011 04:39:49
Automatic Update On
Collector Mode Connected
Look out for the version, which should be 10.3.6.0.1 or above, and the
timestamps, which should be current.
Step 2 - Assign CSIs to the Exadata targets.

By default, all targets are uploaded using the CSI used to register Oracle Configuration
Manager in the OMS Home. The 12c Oracle Harvester supports uploading configuration
7
data using different CSIs for each Oracle Home. This is important when monitoring
Oracle Exadata Database Machine targets since each Oracle Exadata Database Machine
target needs to be assigned its own CSI.
CSIs are assigned to Oracle Home targets using the Cloud Control console by navigating
to the Setup > My Oracle Support > Support Identified Assignment page:
Note: Before you can use this page to Assign CSIs you need to:
i. Ensure My Oracle Support credentials are set for your user in Cloud Control using Setup > My
Oracle Support > Set Credentials.
ii. Ensure the Connection setting is set to Online on the Setup > Proxy Settings > Online and
Offline Settings (Patching Setup) page.
iii. Ensure Proxy Settings are configured and tested (if required) using Setup > Proxy Settings >
My Oracle Support and Proxy Connection
iv. Wait for the Oracle Harvester to have run for the first time. As stated previously, the
Harvester requires OCM to be configured in each of the OMS Oracle Homes before it will run.
The Harvester will run automatically at 02:00 (OMS local time) following OCM configuration. No
Oracle Homes will be listed on the Assign CSI page until the Harvester has run successfully. The
scheduled run time for the Harvester can be modified following the steps in Note 1325594.1 How
To Change The Enterprise Manager Harvester Job RunTime Schedule.
8
On the Support Identifier Assignment page, use the Search dialogue to filter the list of
Oracle Homes that can have CSIs assigned based on specified Oracle Home, Host Name
and Support Identifier search strings. The wildcard % can be used within the search
strings.
The list of Oracle Homes can further be filtered based on whether or not the Oracle
Homes have CSIs assigned already by selecting Assigned or Unassigned from the Show
Oracle Homes drop-down list and clicking Go.
Users with Super Administrator privileges are able to assign CSIs for any oracle home.
Administrators without Super Administrator privileges can assign CSIs only to oracle
homes for which they have at least operator privilege on all the targets.
After finding the Oracle Home(s) that you want to Assign CSIs to, select them using the
checkboxes in the Select column then click Assign. A pop-up window will appear that
shows the list of selected Oracle Homes and a drop-down list that can be used to select
the CSI that you want to assign to those Oracle Homes. Administrators will be able to
select from the list of CSIs available to the My Oracle Support user whose credentials they
provided in Setup > My Oracle Support > Set Credentials. Select the CSI from the
drop-down list then click OK.
9
Configure OCM collections for Exadata using the Mass Deployment

utility to deploy standalone OCM collectors to each Oracle Home
on each compute node
When not using the Oracle Harvester, to collect the configuration data for all the targets
in your Oracle Exadata Database Machine, the OCM collector must be installed and
configured in all of the Oracle homes on all the compute nodes (database servers) of the
Oracle Exadata Database Machine.
Because the Oracle Exadata Database Machine consists of multiple compute-nodes and
multiple Oracle homes, you can use the Oracle Configuration Manager Mass Deployment
Utility (Mass Deployment) for configuring OCM in multiple Oracle homes in one go.
The process of using the Mass Deployment utility for deploying OCM collectors in the
Oracle Homes on each compute node consists of five steps:
1. First the Mass Deployment utility software needs to be downloaded and installed
on any host from which all nodes in an Oracle Exadata Database Machine can be
accessed using ssh.
2. Next, an input csv file is created that will be used as input for the Mass
Deployment utility.
3. The Mass Deployment utility is then run for the first time with the action
get_info for each Oracle Home. This does not result in any OCM collector
being deployed but simply returns the current status of OCM for each of the
Oracle Homes listed in the input csv file
4. Based on the output of the get_info run, a new input csv file is created to actually
deploy the OCM collectors and the Mass Deployment utility is run to perform the
deployment.
5. Lastly, the Mass Deployment utility output file is checked to verify that the OCM
Collectors have been deployed successfully.
Step 1 - Download and Install the Mass Deployment utility

The Mass Deployment utility can be downloaded from My Oracle Support via Patch
13015545.
Note: It is important to ensure that you download the correct version of the Mass Deployment
utility. The minimum version required for deploying OCM on Oracle Exadata Database Machines
is version 10.0.1.1.0. Prior to version 10.0.1.1.0, it is not possible to specify the HW CSI that the
OCM that will deployed into an Oracle Home will use and therefore it is difficult to configure
OCM to upload configuration data using the correct CSI for the Oracle Exadata Database
Machine. Patch 13014454 provides the correct version of the Mass Deployment utility.
Download and install the Mass Deployment utility on any one host from which all the
nodes in an Oracle Exadata Database Machine can be accessed using ssh. A compute
10
node can be used for this purpose. Instructions to install the Mass Deployment utility can
be referenced in the Oracle Configuration Manager Companion Distribution Guide.
Step 2 - Mass Deployment Input File Creation

Mass Deployment takes as input a manually created comma-separated values (csv) text file
which lists all compute nodes and Oracle Homes and the parameters necessary to install,
configure or check the status of OCM for each. The process being described is best
performed by creating two input files, one to be used to check whether OCM collectors
are deployed in each Oracle Home and their status, e.g. get_info_input.csv, and one to be
used to perform the actual install or configuration steps, e.g. deploy_input.csv. Before we
can create the deploy_input.csv file we need the output from running the Mass
Deployment utility with the get_info_input.csv.
Use your favorite spreadsheet editor to create the get_info_input.csv file. To facilitate the
use of the input file, the Mass Deployment utility contains a template for you to use,
sample_input.csv, in the folder ocm_companion/distributions/ocm/md. See Section 2.4.5
Input File in the Mass Deployment documentation for further details on the input file
format.
Much of the information required as input into Mass Deployment can be retrieved from
the Exadata Database Machine configuration worksheets. Please see Appendix A for
examples.
1. Copy/rename the sample_input.csv file
cp sample_input.csv get_info_input.csv
2. Create a line for each Compute Node/Database Oracle Home combination. For
example, if the Oracle Exadata Database Machine houses two compute nodes,
which each have one Grid Infrastructure Oracle Home and one Database Oracle
Home, create four lines. Add the following information on each line (if a column
value is not specified, leave it blank for now):
Action: Set this column to get_info to retrieve information about the state of
the OCM collector in the compute node Oracle home specified on this line
Host-Name: Host name of the compute node.
Host-User: OS user that owns the Oracle home.
Note: For Grid Infrastructure Oracle Homes, when using the Mass Deployment
utility, specify the root user as the Host-User since it is the root user that owns
the Oracle home. This results in the OCM deployment being owned by the root
user. Alternatively, OCM can be deployed manually in Grid Infrastructure homes
using the non-root Oracle software owner.
Host-Password: Password for the OS user - set to __PROMPT__ (two
underscores before and after) and you will be prompted for the password at the
time you run the Mass Deployment utility, interactively. This is a secure option
for providing the password as it results in the password not being written to a file
at any phase of the process. See Section 2.4.4 Credentials in the Mass
11
Deployment Documentation or Appendix B of this document for more

information on alternative secure ways of providing the password
Oracle Home: Oracle Home location.
ML-User: Enter the MOS Account username (email address) that has access to
the Exadata Hardware Customer Support Identifier (CSI) for the Oracle Exadata
Database Machine.
ML-CSI: This field holds the Exadata Hardware Customer Support Identifier
(CSI) and is used in conjunction with the ML-User field to authenticate OCM
uploads. If the CSI is not known, this field can be left blank and the My Oracle
Support password for the username specified for ML-User can be instead
provided. However, this will result in the Oracle Exadata Database Machine
target being assigned the default CSI for the provided My Oracle Support account
and this is unlikely to be the correct one. The OCM collector will need to be
configured with the correct CSI once again when it is known.
ML-Pwd: Leave blank unless the CSI is not known. If used, specify
__PROMPT__ to be prompted for this value at the time that the Mass
Deployment utility is run or see Appendix B for details of how to provide this
value securely
Depending on how OCM will connect to My Oracle Support, Proxy- values need
to be provided:
o Direct Connectivity to the Internet
No need to supply values for Proxy- fields
o No Direct Connectivity to the Internet Using a Proxy Server
Provide the following proxy information in the csv file:
Proxy-Host: Host of the proxy.
Proxy-Port: Port for the proxy.
Proxy-User: In case of authenticated proxy, provide proxy user name.
Proxy-Pwd: In case of authenticated proxy, provide proxy user password.
Specify __PROMPT__ to be prompted when the Mass Deployment utility
is run or follow the same process used for the host-password to provide
an encypted password.
o No Direct Connectivity to the Internet- Using Oracle Support Hub
Edit the file:
<path_to_mass_deployment_utility>/ocm/md/config/md.properties
and add the property md.repeater.uri with the value of the Oracle Support
Hub Url
Example
md.repeater.uri=http://shhost.example.com:7003
12
(See Configuring Mass Deployment in the documentation for more

details)
Notes:
The Oracle Support Hub needs to have been deployed on a server that can
connect to My Oracle Support. A pre-requisite of deploying the Oracle
Support Hub is to have a Weblogic or Oracle Application Server to be
available and configured ready for deployment of the Oracle Support Hub
application. The Oracle Support Hub is supported to run on the following
versions of Weblogic and Oracle Application Server:
WebLogic Server (WLS) 10.3.0 on both the Windows and Linux

platforms.
Oracle Application Server 10.1.2 and 10.1.4 on both the Windows
and Linux platforms.
For details of how to install and configure an Oracle Support Hub, refer to
the Oracle Support Hub Documentation.
Example get_info_input.csv:
The following is an example of the lines in a csv file with sample entries for compute
nodes edbm01db01 and edbm01db02, which have one Database Oracle Home and one
Grid Infrastructure Oracle Home each. Notice, the first line starts with a pound sign (#)
signifying that the first line is a comment showing the column labels. You may copy these
lines to a text file and open that file in your favorite spreadsheet editor for better viewing.
"#Action","HostName","Host-user","Host-Password","Product Home Path","Oracle Config
Home Path","OCM Version","OCM Status","OCM Mode (connected/disconnected)","Db SID","DB
Type (EM/Ebiz/db)","ML-user (Metalink user ID)","ML-CSI (Metalink CSI)","ML-
Pwd","Proxy-Host","Proxy-Port","Proxy-user","Proxy-Pwd","DB-user (SYSDBA user)","DB-
Pwd","DB-App-user (Ebiz user if db type is Ebiz)","DB-App-Pwd (Ebiz user password if db
type is Ebiz or SYSMAN password if db type is EM)","Cmd Status (Status of the remote
operation)"
"get_info","edbmdb01","oracle","
ENCR_8EBB07D9D486C17A4BA0F6FD4B93BF52","/u01/app/oracle/product/11.2.0/dbhome_1",,,,,,,
"jdoe@example.com",12345678,,,,,,,,,,
"get_info","edbmdb01","root","__PROMPT__","/u01/app/grid/11.2.0",,,,,,
,"jdoe@example.com",12345678,,,,,,,,,,
"get_info","edbmdb02","oracle","__PROMPT__","/u01/app/oracle/product/11.2.0/dbhome_1",,
,,,, ,"jdoe@example.com",12345678,,,,,,,,,,
"get_info","edbmdb02","root","__PROMPT__","/u01/app/grid/11.2.0",,,,,,
,"jdoe@example.com",12345678,,,,,,,,,,
The following graphic illustrates the sample get_info_input.csv when viewed from
spreadsheet editor software (the full width of the spreadsheet is shown in three sections).
13
Step 3 - Determine the current state of OCM in each compute node Oracle home
Before performing any deployment operations, the Mass Deployment Utility should first
be run with the Action get_info for each database Oracle home on each compute node.
Based on the output of get_info, a new input csv file will be created in the next step with
relevant Action values depending on the current status of OCM in each database Oracle
home.
The Mass Deployment utility is run using the remote_op command and performs the
action specified in the Action column for the Oracle home of the compute node of each
row of the input csv file that gets passed as the parameter input_file.
Execute the remote_op Mass Deployment command using the get_info_input.csv file
as input to gather information about the status of OCM in each DB Oracle Home on
each compute node.
For example:
$ bin/remote_op -input_file get_info_input.csv
Notes:
1. When you run either of the remote_op or secure_password utilities for the first time, you will
be prompted for a password. This password will be required subsequently each time either
the remote_op or secure_password utility is used. The password must be at least 8 characters
long. If you forget the password you will need to remove the current Mass Deployment
Utility and install it once again. Any input files that have encrypted values from a previously
deployed Mass Deployment utility will no longer be able to be used.
2. The remote_op command requires the environment variable JAVA_HOME to be set to point
to a JDK version greater than 1.5
Respond to the prompts as needed. You will be prompted for the Mass Deployment
utility password and each password field in the input.csv file that contained a
__PROMPT__
For example:
$ export JAVA_HOME=/
$ bin/remote_op -input_file get_info_input.csv
OCM Mass Deployment Utility - Release: 10.0.1.1.0
Copyright (c) 2009, Oracle. All rights reserved.
Please enter the password for Mass Deployment Utility.
Password:
Password for user oracle (host:edbmdb01):
Confirm Password:
14
Password for user root (host:edbmdb01):

Confirm Password:
Password for user oracle (host:edbmdb02):
Confirm Password:
Password for user root (host: edbmdb02):
Confirm Password:
Encrypting input file
/scratch/username/MD/ocm_companion/distributions/ocm/md/getinfo_exadata_csi_input.csv
Please be patient, process may take some time.
Log File: /scratch/username/MD/ocm_companion/distributions/ocm/md/out/output-2011-09-
12_03-50-03-PM-getinfo_exadata_csi_input.csv.log
Please see the output file
/scratch/username/MD/ocm_companion/distributions/ocm/md/out/output-2011-09-12_03-50-03-
PM-getinfo_exadata_csi_input.csv
A Mass Deployment output csv file is generated showing the results of the remote_op
commands. The output file name will default to the input file name prepended by the
string output- and the timestamp, for example, output-2012-01-11_10-39-36-AM-
get_info_input.csv and will be located in the ocm/md/out directory. See Mass
Deployment Output File for details on the output file format and log file information
that can be used for troubleshooting.
Step 4 - Deploying/Configuring OCM
Create a new input csv, deploy_input.csv, to perform the required deployment actions
After the initial execution of the remote_op command using the get_info_input.csv file,
create a new input file. deploy_input.csv by copying the get_info_input.csv file. You will
notice that the __PROMPT__ values have been replaced by encrypted passwords and
therefore the passwords do not need to be entered when the remote_op command uses
this file.
Edit the Action value for each row of the input file based on the status returned for the
same row in the output.csv file from step 3:
1. Set to install if the OCM Mode field is empty or shows OCM Not Configured
2. Set to config if the OCM Mode field is Disconnected or Connected
unauthenticated
3. Set to upgrade if the OCM Mode field is Connected or Connected (via Oracle
Support Hub) but the OCM Version is less than 10.3.6
Note: If a row shows the OCM Mode Connected or Connected (via Oracle Support Hub)
and the OCM Version is 10.3.6 or above, OCM is already configured in the Oracle Home,
keep the value get_info for the Action for such rows. If OCM is already configured in all
Oracle Homes then there is no need to perform any more steps.
Add rows to the deploy_input.csv file for each database to be instrumented
To ensure OCM collects the most complete set of configuration data for the databases
running on the Oracle Exadata Database Machine, it is good practice to ensure that the
most up to date version of the ORACLE_OCM schema objects are installed in the
ORACLE_OCM schema of each database. The Mass Deployment Utility instrument
action installs or updates the ORACLE_OCM schema for a specified database.
15
For each database, select one compute node and Oracle Home that the database runs out
of and duplicate that row in the deploy_input.csv file. Give the new row the Action
value Instrument and provide the DB SID, DB Type, DB-User and DB-Pwd field
values:
DB-SID:Database system identifier. Used for install and instrument actions.
DB-Type: The database type. Provide the value db for all databases other than
EBiz repositories (provide the value ebiz) and Enterprise Manager repositories
(provide the value EM)
DB-user (SYSDBA user): SYSDBA user - This field is not required if OS
Authentication is enabled on the database
DB-Pwd: Password for the SYSDBA user. This field is not required if OS
Authentication is enabled on the database
The resultant deploy_input.csv file should have one row for each compute node Oracle
Home with the Action install, config, upgrade or get_info and one row for each
database with the Action instrument.
Example deploy_input.csv file
Below is an example of the lines in a deploy_input.csv file with sample entries for
compute nodes edbm01db01 and edbm01db02, which each have one Grid Infrastructure
Oracle Home and one Database Oracle Home that runs the proddb RAC database with
instances proddb1 running on emdbmdb01 and proddb2 running on emdbmdb02.
"#Action","HostName","Host-user","Host-Password","Product Home Path","Oracle Config
Home Path","OCM Version","OCM Status","OCM Mode (connected/disconnected)","Db SID","DB
Type (EM/Ebiz/db)","ML-user (Metalink user ID)","ML-CSI (Metalink CSI)","ML-
Pwd","Proxy-Host","Proxy-Port","Proxy-user","Proxy-Pwd","DB-user (SYSDBA user)","DB-
Pwd","DB-App-user (Ebiz user if db type is Ebiz)","DB-App-Pwd (Ebiz user password if db
type is Ebiz or SYSMAN password if db type is EM)","Cmd Status (Status of the remote
operation)"
"install","edbmdb01","oracle","ENCR_8EBB07D9D486C17A4BA0F6FD4B93BF52","/u01/app/oracle/
product/11.2.0/dbhome_1",,,,,,,"jdoe@example.com",12345678,,,,,,,,,,
"install","edbmdb01","root","ENCR_8EBB07D9D486C17A4BA0F6FD4B93BF52","/u01/app/grid/11.2
.0",,,,,,,"jdoe@example.com",12345678,,,,,,,,,,
"install","edbmdb02","oracle","ENCR_8EBB07D9D486C17A4BA0F6FD4B93BF52","/u01/app/oracle/
product/11.2.0/dbhome_1",,,,,,,"jdoe@example.com",12345678,,,,,,,,,,
"install","edbmdb02","root","ENCR_8EBB07D9D486C17A4BA0F6FD4B93BF52","/u01/app/grid/11.2
.0",,,,,,,"jdoe@example.com",12345678,,,,,,,,,,
"instrument","edbmdb01","oracle","__PROMPT__","/u01/app/oracle/product/11.2.0/dbhome_1"
,,,,,"proddb1","db","jdoe@example.com",12345678,,,,,, "sys","__PROMPT__",,,
The following graphic illustrates the sample deploy_input.csv when viewed from
spreadsheet editor software (the full width of the spreadsheet is shown in three sections).
16
Run the Mass Deployment utility using the deploy_input.csv file as input
Once the deploy_input.csv file has been created and populated, run the Mass Deployment
utility, passing the deploy_input.csv file as input. The Mass Deployment will attempt to
perform each of the Actions and if they are all successful OCM will be configured in each
of the compute node Database Oracle homes and each of the databases running on the
Oracle Exadata Database Machine will be instrumented with the most up to date version
of the ORACLE_OCM schema objects.
17
For example:
$ bin/remote_op -input_file deploy_input.csv
OCM Mass Deployment Utility - Release: 10.0.1.1.0
Copyright (c) 2009, Oracle. All rights reserved.
Please enter the password for Mass Deployment Utility.
Password:
Password for user SYS (database:proddb1):
Confirm Password:
Encrypting input file
/scratch/username/MD/ocm_companion/distributions/ocm/md/deploy_input.csv
Please be patient, process may take some time.
Log File: /scratch/username/MD/ocm_companion/distributions/ocm/md/out/output-2011-09-
12_03-50-03-PM-install_exadata_csi_input.csv.log
Please see the output file
/scratch/username/MD/ocm_companion/distributions/ocm/md/out/output-2011-09-12_03-50-03-
PM-install_exadata_csi_input.csv
Step 5 - Determine the state of OCM in each compute node Oracle home after
deployment
After running the Mass Deployment utility remote_op command with the
deploy_input.csv file as input, an output csv file is generated showing the results of the
remote_op commands. The output file name will default to the input file name
prepended by the string output- and the timestamp, for example, output-2012-01-11_10-
39-36-AM-deploy_input.csv and will be located in the ocm/md/out directory.
Confirm the success of each action by checking the Cmd Status field of the output csv
file. The example, below, shows the successful installation of OCM on both nodes along
with the successful instrumentation of the database.
"#Action",HostName,Host-user,Host-Password,Product Home Path,Oracle Config Home
Path,OCM Version,OCM Status,OCM Mode (connected/disconnected),Db SID,DB Type
(EM/Ebiz/db),ML-user (Metalink user ID),ML-CSI (Metalink CSI),ML-Pwd,Proxy-Host,Proxy-
Port,Proxy-user,Proxy-Pwd,DB-user (SYSDBA user),DB-Pwd,DB-App-user (Ebiz user if db
type is Ebiz),DB-App-Pwd (Ebiz user password if db type is Ebiz or SYSMAN password if
db type is EM),
"",edbmdb01,oracle,ENCR_8EBB07D9D486C17A4BA0F6FD4B93BF52,/u01/app/oracle/product/11.2.0
/dbhome_1,,10.3.6.0.2,idle,Connected,,,jdoe@example.com,12345678,,,,,,,,,,Success:
config operation
"",edbmdb01,root,ENCR_8EBB07D9D486C17A4BA0F6FD4B93BF52,/u01/app/grid/11.2.0,,10.3.6.0.2
,idle,Connected,,,jdoe@example.com,12345678,,,,,,,,,,Success: config operation
/dbhome_1,,10.3.6.0.2,idle,Connected,,,jdoe@example.com,12345678,,,,,,,,,,Success:
config operation
"",edbmdb02,root,ENCR_8EBB07D9D486C17A4BA0F6FD4B93BF52,/u01/app/grid/11.2.0,,10.3.6.0.2
,idle,Connected,,,jdoe@example.com,12345678,,,,,,,,,,Success: config operation
/dbhome_1,,10.3.6.0.2,idle,Connected,proddb1,db,jdoe@example.com,12345678,,,,,,SYS,ENCR
_8EBB07D9D486C17A4BA0F6FD4B93BF52,,,Success: instrument operation
See Section 2.4.6 Mass Deployment Output File for details on the output file format
and log file information that can be used for troubleshooting.
You can also validate the success of the deployment and/or configuration of OCM via
Mass Deployment by executing the emCCR status command on each node. If
successful, the command should return the status of the collector.
18
For example:
[oracle@db01 ccr]$ bin/emCCR status
Oracle Configuration Manager - Release: 10.3.6.0.1 Production
Copyright (c) 2005, 2011, Oracle and/or its affiliates. All rights reserved.
------------------------------------------------------------------
Start Date 12-Jan-2012 14:13:17
Last Collection Time 12-Jan-2012 14:13:17
Next Collection Time 13-Jan-2012 14:12:00
Collection Frequency Daily at 14:12
Collection Status idle
Log Directory
/u01/app/oracle/product/11.2.0/dbhome_1/ccr/hosts/edbmdb01.us.oracle.com/log
Registered At 12-Jan-2012 14:12:59
Automatic Update On
Collector Mode Connected
Look out for the version, which should be 10.3.6.0.1 or above, and the timestamps, which
should be current.
19
Manually install OCM version 10.3.6 or above into each Oracle

Home on each compute node
The steps to manually deploy OCM in Oracle Homes are documented in the Oracle
Configuration Manager Installation and Administration Guide.
Special care should be taken to ensure that setupCCR is run with the Hardware CSI of the
Oracle Exadata Database Machine passed as a parameter, e.g:
$ setupCCR 12345678
Note: When installing OCM into a Grid Infrastructure home, since version 10.3.5 of
OCM, it is no longer necessary to install as the root user or change ownership of the
Oracle Home to the non-root user.
Since the Grid Infrastructure Oracle Home is owned by the root user, OCM must be
unzipped as the root user and then chown can be used to change the ownership of the
ccr directory and its contents to the non-root user before that user runs setupCCR.
Configuring OCM in disconnected mode

When there is no means of connecting to My Oracle Support at all, with no access to a
proxy, or an Oracle Support Hub that can connect to My Oracle Support, the only option
available is to configure OCM in disconnected mode.
It is not currently possible to use the Mass Deployment utility to deploy OCM in
disconnected mode so manually deploying OCM in each Oracle Home is the only option
available.
Once OCM is configured in each Oracle Home, a manual collection needs to be

performed for each of those Oracle Homes.
Note 763142.1 How to upload the collection file ocmconfig.jar to My Oracle Support for
Oracle Configuration Manager (OCM) running in Disconnected Mode provides
instructions on how to upload the Oracle Exadata Database Machine configuration data
to My Oracle Support.
20
Problems you may experience

1. After deploying OCM, either manually or using the Mass Deployment utility,
no Exadata targets are visible in My Oracle Support. Only the host, cluster and
Grid Infrastructure targets are discovered.
Check the file <CCR_HOME>/hosts/<compute_node_name>/config/default/
targets.xml on each compute node. If the Exadata targets are not discovered by ccr
they will not exist in targets.xml. The Exadata targets are discovered only after the
first successful execution of the DBMS Scheduler job that is scheduled to run on the
databases that are instrumented for OCM. If the databases have not been
instrumented with the most recent version of the OCM database objects, that job
might not be running. Ensure all DBs running on the Oracle Exadata Database
Machine are instrumented by either running the Mass Deployment utility with an
input file that contains a line for each database with the action instrument or by
manually running installCCRSQL.sh for each database, following the steps described
in the Post-Installation Database Configuration of the OCM documentation.
2. When deploying OCM on an Oracle Exadata Database Machine, either

manually or using the Mass Deployment utility, for an Oracle Home owned by
a non-root user you are likely to see a message stating that the user cannot use
cron:
This account does not have permission to use cron. The Oracle Configuration Manager
will not be automatically started on system reboot. Add the command:
/u01/app/oracle/product/11.2.0/dbhome_1/ccr/bin/emCCR start -silent
to your system startup procedures.
It is common for non-root users on an Exadata server to not have access to cron.
The message is displayed because the deployment of OCM tries to configure crontab
to run a script every 15 minutes to start OCM when it is not running, e.g:
0,15,30,45 * * * * /u01/app/oracle/product/11.2.0/dbhome_1/ccr/bin/emCCR -cron -

silent start
If cron cannot be enabled, an alternative approach is to configure an init.d script to

start OCM on startup.
21
Appendices
Appendix A Exadata Configuration Worksheets
Exadata Database Machine Configuration Worksheets contain customer provided data
used to generate the Exadata Installation Template. These worksheets, along with the
installation template are a good source of Exadata compute node data used by the OCM
Mass Deployment Utility.
See below for examples:
The value of the Net0 Name column of rows with a Component of Database
server in the Server Components listing from the Exadata Installation Template
can be used as compute node host names in the Mass Deployment input.csv file.
Host
Names
The Exadata Database machine name entered into the General Configuration
Worksheet is the basis of the generated host names (e.g., dm01 will result in a
database server host name of dm01db01). This can then be used to infer the host
names to be entered into the input.csv file.
22
Oracle Environment Default Settings can also be used to deduce compute node host
user names and passwords.
Host username
Host password
23
Appendix B - Configuration Table Entries for OCM

The following table lists the information that will be required for deploying OCM on an
Oracle Exadata Database Machine
Name Value Description

My Oracle Support Email address for My Oracle Support Account that
Email has access to the CSI for the Oracle Exadata Database
Machine
My Oracle Support For security purposes, Password for the My Oracle Support Account that has
Password do not write this down, access to the CSI for the Oracle Exadata Database
just make sure you Machine
know the password
Support Hub Host If required. Please check
Name and port http://download.oracle.com/docs/cd/E18041_01/do
c.103/e14501/stdalone_rptr.htm for installation
Support Hub OS For security purposes, details.
Username and do not write down any
Password passwords, just make
sure you know the
password
Applicable Proxy Provide Proxy server if required for connecting to
servers for Oracle.
connecting to
Oracle This includes any applicable Proxy between
1
1. Compute Nodes and Oracle
2
2. Compute Nodes and Support Hub
3
3. Support Hub and Oracle
Enter the Proxy server details in this format:
[<Proxy-user>@]<Proxy-host>[:<Proxy-port>]
for all the applicable cases above.
Proxy-user and Proxy-port are optional.
If passwords are needed, provide at installation time.
1 Applicable if you dont have a Oracle Support Hub.

2 Applicable only if you have a Oracle Support Hub.
3 Applicable only if you have a Oracle Support Hub.
24
The following table can be used to list each Oracle Home for each Compute Node along
with the details of the databases that run from that Oracle Home.
Compute Node Oracle Home Oracle Listener SYSDBA SYSDBA

(Database Server) SID Port Username Password
edbm01db01 /u01/app/oracle/product/11.2.0/ proddb1 1521 sys Do not write
dbhome_1 this down.
edbm01db02 /u01/app/oracle/product/11.2.0/ proddb2 1521 sys Do not write

dbhome_1 this down.
edbm01db03 /u01/app/oracle/product/11.2.0/ salesdb 1521 sys Do not write

dbhome_1 this down.
edbm01db03 /u01/app/oracle/product/11.2.0/ repdb 1522 sys Do not write

dbhome_1 this down.
25
Appendix C - Secure Password Entry

To allow configuration data to be sent to Oracle, the OCM collector needs to be
configured with the customer's My Oracle Support (MOS) credentials. MOS credentials
can consist of a MOS user name (e-mail address) and either an Exadata Hardware
Customer Support Identifier (CSI) or a MOS password. Utilizing the CSI is preferable as
it does not require encryption. If the CSI is not known, then OCM can be configured
with a valid MOS User ID and Password using the following options. These options can
also be applied to the compute node host passwords and or proxy host passwords placed
in the Host-Password field of the input.csv file.
a). Allow the utility to prompt for the password: If you want to be prompted
for the password as the remote_op utility processes the input file, enter
__PROMPT__ (that is, two underscore characters, followed by the string PROMPT in
uppercase, followed by another two underscore characters) in the password fields in the
password.csv. For more details on this, refer to Section 2.4.4 of the Oracle
Configuration Manager Companion Distribution Guide.
Note: The remote_op utility encrypts the values of the input.csv file, changing the values
in the actual input file and saves those changes.
b). If the same credentials are being used for multiple hosts, another option is to
use a password group name in the password.csv file as described in Section 2.4.1
of the Oracle Configuration Manager Companion Distribution Guide.
26
Appendix D - Testing the link to Oracle

The OCM documentation provides instructions for Testing the Link to Oracle. Those
instructions require telnet to be available on the compute node, which generally is not
the case in an Exadata environment.
An alternative way of testing connectivity to Oracle would be to use ssh as in the example
below:
ssh -v ccr.oracle.com -p 443 true

OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to ccr.oracle.com [141.146.8.206] port 443.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: loaded 3 keys
The ssh connection will hang and you will need to use CTRL-C to exit but the highlighted
output will confirm whether or not the node you are on can connect to Oracle.
27
Oracle Configuration Manager for Oracle Copyright 2011, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only and the
Exadata Database Machine contents hereof are subject to change without notice. This document is not warranted to be error-free, nor subject to any other
January, 2012 warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or
Author: David Parker-Bastable fitness for a particular purpose. We specifically disclaim any liability with respect to this document and no contractual obligations are
Contributing Authors: Casey Costley, Tina formed either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any
Boisvert means, electronic or mechanical, for any purpose, without our prior written permission.
Oracle Corporation
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
World Headquarters
500 Oracle Parkway
AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices.
Redwood Shores, CA 94065
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license
U.S.A.
and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open
Worldwide Inquiries: Company, Ltd. 1010
Phone: +1.650.506.7000
Fax: +1.650.506.7200
oracle.com

Oracle Configuration Manager For Ex A Data

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Oracle Configuration Manager For Ex A Data

Uploaded by

Copyright:

Available Formats

An Oracle White Paper

Oracle Configuration Manager

Benefits of Deploying OCM for Exadata

Simplification of the SR creation process and faster problem resolution from

Simplified configuration management, benefiting from a single, comprehensive and

Before you start

Note: This information is likely to be available in the Exadata Database Machine

1. Host-Name, Host-User, Host-Password for each compute node (database server)

5. Proxy details - hostname, port, (username and password if required) - if a proxy is

As the root user enter:

If the grep command returns no rows, run the following command:

Note: The sed command adds the line:

Options available for configuring Oracle Configuration Manager

Deploy OCM for

Is the Oracle Exadata Database

Is Enterprise Manager Cloud No

Yes Are the compute nodes able to

Follow the instructions to

Yes Is there a host that the compute No

Follow the instructions to Configure OCM for Exadata using

Configure OCM collections for Exadata using the Enterprise

Step 1 - Configure OCM in each OMS Oracle Home

To achieve this, perform the following steps on each OMS host.

1. Locate the OMS config home.

In the $ORACLE_HOME/sysman/config/emInstanceMapping.properties file

2. Set the environment variable ORACLE_CONFIG_HOME to the config home of

3. Change to the directory $ORACLE_HOME/ccr/bin and list its contents.

For example (using 12345678 as the CSI):

Otherwise, use configCCR r then configCCR a to first remove the previous

For example (using 12345678 as the CSI):

Step 2 - Assign CSIs to the Exadata targets.

Configure OCM collections for Exadata using the Mass Deployment

Step 1 - Download and Install the Mass Deployment utility

Step 2 - Mass Deployment Input File Creation

Deployment Documentation or Appendix B of this document for more

(See Configuring Mass Deployment in the documentation for more

WebLogic Server (WLS) 10.3.0 on both the Windows and Linux

Password for user root (host:edbmdb01):

Step 4 - Deploying/Configuring OCM

Add rows to the deploy_input.csv file for each database to be instrumented

Manually install OCM version 10.3.6 or above into each Oracle

Configuring OCM in disconnected mode

Once OCM is configured in each Oracle Home, a manual collection needs to be

Problems you may experience

2. When deploying OCM on an Oracle Exadata Database Machine, either

/u01/app/oracle/product/11.2.0/dbhome_1/ccr/bin/emCCR start -silent

to your system startup procedures.

0,15,30,45 * * * * /u01/app/oracle/product/11.2.0/dbhome_1/ccr/bin/emCCR -cron -

If cron cannot be enabled, an alternative approach is to configure an init.d script to

Appendix B - Configuration Table Entries for OCM

Name Value Description

Enter the Proxy server details in this format:

for all the applicable cases above.

Proxy-user and Proxy-port are optional.

If passwords are needed, provide at installation time.

1 Applicable if you dont have a Oracle Support Hub.

Compute Node Oracle Home Oracle Listener SYSDBA SYSDBA

edbm01db02 /u01/app/oracle/product/11.2.0/ proddb2 1521 sys Do not write

edbm01db03 /u01/app/oracle/product/11.2.0/ salesdb 1521 sys Do not write

edbm01db03 /u01/app/oracle/product/11.2.0/ repdb 1522 sys Do not write

Appendix C - Secure Password Entry

Appendix D - Testing the link to Oracle

ssh -v ccr.oracle.com -p 443 true