Skip Headers
Oracle® Configuration Manager Installation and Administration Guide
Release 10.3.8.1

Part Number E37289-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
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.

Note:

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

  • Usage: Use this command to enable and disable the automatic retrieval of new software updates. Automatic retrieval of new software updates occurs only with automatic collections. By default, automatic updates are enabled.

    <ocm_install_root>/ccr/bin/emCCR automatic_update on / off 
    
  • Execute Privileges: Can be executed by <ocm_install_root> owner

  • Prerequisites: Oracle Configuration Manager must be running in Connected mode.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR automatic_update on  
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production 
    Copyright (c) 2005, 2012, Oracle. All rights reserved. 
    ---------------------------------------------------------------- 
    AUTOMATIC_UPDATE command ended successfully. 
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

6.2 emCCR clear - diagnostic

  • Usage: Use this command to clear all diagnostic upload files. The syntax is as follows:

    emCCR clear -diagnostic[=SR=<Service request number>,FILE=<Absolute path of diagnostic package> [-completed] [-force]]
    
    • Specify the -diagnostic parameter to clear all diagnostic upload files.

    • Specify the -diagnostic parameter with the SR number to clear all uploads for a particular service request. The SR number must be in format x-y where:

      • x represents one digit

      • y represents multiple digits

    • Specify the -diagnostic parameter with SR number and FILE to clear a particular upload. FILE must include the name and the full path to the file that contains diagnostic information.

    • Specify the -completed parameter to clear only completed uploads.

    • Specify the -force parameter to clear all uploads even if there are errors.

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

  • Prerequisites: Oracle Configuration Manager must be running in Connected mode.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR clear -diagnostic=SR=3-543219500, FILE=/scratch/test/support_info.zip
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ------------------------------------------------------------------
    Command successfully completed.
    
  • Errors: Some of the error messages you may see are the following:

    • Invalid SR format: This error occurs when the SR format does not match the required format of x-y. To resolve this error, you must specify the SR number in the correct format.

    • No such diagnostic upload request exists. This error occurs if you run a -diagnostic command for a non-existent or invalid SR number or file name. To resolve this error, view the status of all submitted packages and specify the correct SR number or file name.

    • Could not access diagnostic upload data. This error occurs while reading or writing diagnostic upload data. To resolve this error, make sure that the diagnostic upload client has read and write permissions to the <ocm_install_root>/ccr/state directory.

    • Invalid upload state. Could not perform clear. Please use -force to clear. This error occurs when the diagnostic package is corrupted. To resolve this error, use emCCR clear -force to clear the upload request.

    • Invalid command. This error occurs when invalid arguments are specified on the command line. Use emCCR help, view all the command line options and enter the correct arguments.

6.3 emCCR collect

  • Usage: This command can be run in Connected and Disconnected modes. You might need to run this command to determine the properties that need to be configured as a result of deploying the Diagnostic Checks package.

    Connected Mode: Use this command to perform an immediate discovery, collection, and uploading of configuration data. When you run this command, it checks if any Oracle Configuration Manager software updates are available but does not install them.

    Disconnected Mode: Use this command to perform a manual discovery and collection of configuration data. Collected data is not automatically uploaded but is stored in the <ocm_install_root>/ccr/state/upload/ocmconfig.jar file. You can then upload this file to Oracle by way of My Oracle Support from another system that has internet access

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

  • Prerequisites:

    • Oracle Configuration Manager is registered with Oracle. (For Connected mode)

    • The Scheduler is already running. (For Connected mode)

  • Example 1

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

    Example 2:

    Sample output when the minimum JDK version is not met. Minimum version of JDK is 1.4.

    <ocm_install_root>/ccr/bin/emCCR collect
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.
    ------------------------------------------------------------------
    JDK version does not meet the minimum requirement to run diagchecks (Diagnostic
    Checks). Requires 1.4 or later, actual version is 1.2.2. Deployed diagchecks
    will not be run.
     
    Collection and upload done.
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered with Oracle: In this case, you must register Oracle Configuration Manager with Oracle.

    • Mandatory updates available. Command failed. This error occurs if you perform a manual collection before applying the mandatory updates.

    • Server not available.

    • Handshake failure. You must reregister Oracle Configuration Manager.

    • Oracle Configuration Manager is Not Running - Restart the Scheduler using the emCCR start command.

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: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    Collection and upload done.
    

6.4 emCCR enable_diagchecks | disable_diagchecks

  • Usage: Use this command to enable or disable all diagnostic checks collections in the Oracle Configuration Manager home for all targets. This command can be run in Connected or Disconnected mode.

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

  • Prerequisites: None.

  • Example 1: Sample output when the Diagnostic Checks feature is enabled.

    <ocm_install_root>/ccr/bin/emCCR enable_diagchecks
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.
    ------------------------------------------------------------------
    Diagchecks have been enabled.
    

    Example 2: Sample output when the Diagnostic Checks feature is disabled.

    <ocm_install_root>/ccr/bin/emCCR disable_diagchecks
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.
    ------------------------------------------------------------------
    Diagchecks have been disabled
    
  • Errors and Informational Messages: Some of the error and informational messages you may see are:

    • "disable_diagchecks" is not a valid command for root user. Log out as root user and login as the owner of the home in which Oracle Configuration Manager is installed.

    • Diagchecks are already enabled. No action is required because diagnostic checks are in the required state.

6.5 emCCR enable_target | disable_target

  • Usage: Use this command to enable or disable the collection of configuration information for targets discovered by the Oracle Configuration Manager. This command can be run in Connected or Disconnected mode. By default, all targets are enabled for collection. When you enter this command, the list of targets that can be enabled or disabled is displayed. Enter the number for the target that is to be enabled or disabled.

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

  • Prerequisites: You can use this option only if Oracle Configuration Manager has been registered with Oracle. This prerequisite is applicable only if you are running Oracle Configuration Manager in Connected mode.

  • Example: For example, enter the command to disable the database instance HTMLDB.

    <ocm_install_root>/ccr/bin/emCCR disable_target
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    S. No.     Category                     Target Name
    0          Host                         xyz.com
    1          Database Instance            ND10G
    2          Database Instance            HTMLDB
    3          Oracle Home                  10gR1db
    
    Press Enter to exit the command.
    Use Comma to separate multiple target numbers.
    Enter the number(s) corresponding to the target(s) you wish to disable:2
    DISABLE_TARGET command ended successfully.
    
  • Errors: Some of the error messages you may see are:

    • Access Denied - This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered With Oracle - In this case, you must register Oracle Configuration Manager with Oracle.

    • No targets to act on by this Command. - There are no targets that can be enabled or disabled.

6.6 emCCR getupdates

  • Usage: Use this command to retrieve any new software updates from the content server and deploy these updates.

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

  • Prerequisites:

    • Oracle Configuration Manager is registered with Oracle.

    • The Scheduler is already running.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR getupdates
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    Updates are downloaded from the Content Server.
    Deploying core.jar at 01-06-2012_13:57:27
    Deploying core - Version 10.3.8.0.0
    Deploying scripts.jar at 01-06-2012_13:57:35
    Deploying scripts - Version 10.3.8.0.0
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered with Oracle: In this case, you must register Oracle Configuration Manager with Oracle.

    • Server not available.

    • Oracle Configuration Manager is Not Running - Restart the Scheduler using the emCCR start command.

6.7 emCCR help

  • Usage: Use this command to list the available emCCR (Oracle Configuration Manager) options. This command can be run in Connected or Disconnected modes.

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

  • Prerequisites: None

  • Example:

    Sample Output in Connected Mode

    <ocm_install_root>/ccr/bin/emCCR help
    Oracle CCR - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ------------------------------------------------------------------
    Usage:
        emCCR start| stop| status
        emCCR set collection_interval="[FREQ=MONTHLY | WEEKLY | DAILY]
                                  [; BYMONTHDAY=1 to 31, when FREQ is MONTHLY]
                                  [; BYDAY=MON to SUN, when FREQ is WEEKLY]
                                  [; BYHOUR=0 to 23]
                                  [; BYMINUTE=0 to 59]" 
                 DAILY is the default Frequency.
        emCCR hold | resume
        emCCR [-annotation="annotation string"] collect | upload | getupdates
        emCCR [-verbose] [-register] test
        emCCR register
        emCCR automatic_update on/off
        emCCR enable_diagchecks | disable_diagchecks
        emCCR enable_target | disable_target
        emCCR upload -diagnostic=SR=Service request number,FILE=Absolute path of
     diagnostic package [-restart] [-force]
        emCCR status -diagnostic=[SR=Service request number,FILE=Absolute path of
     diagnostic package]
        emCCR clear -diagnostic[=SR=Service request number,FILE=<Absolute path of
     diagnostic package] [-completed] [-force]
        emCCR update_components [-silent] -staged_dir="Directory containing OCM
        packages" | -distribution="OCM installation kit path"
        emCCR help
        
    

    Sample Output in Disconnected Mode

    <ocm_install_root>/ccr/bin/emCCR help
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    -------------------------------------------------------
    Usage:
        emCCR [-annotation="annotation string"] collect 
        emCCR status
        emCCR enable_diagchecks | disable_diagchecks
        emCCR enable_target | disable_target
        emCCR update_components [-silent] -staged_dir="Directory containing
        OCM packages" | -distribution="OCM installation kit path" 
        emCCR help 
    

    Sample Output for Root User

    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle.  All rights reserved.
    ------------------------------------------------------------------
    Usage:
        emCCR status
        emCCR [-annotation="annotation string"] collect | upload
        emCCR upload [-diagnostic=SR=Service request number,FILE=Absolute path of diagnostic package [-restart] [-force]]
        emCCR status [-diagnostic[=SR=Service request number,FILE=Absolute path of diagnostic package]]
        emCCR clear -diagnostic[=SR=Service request number,FILE=Absolute path of diagnostic package] [-completed] [-force]
        emCCR help 
    

6.8 emCCR hold

  • Usage: Use this command to put Oracle Configuration Manager on hold. When Oracle Configuration Manager is on hold, configuration data will not be automatically collected and uploaded to the Management Repository. You can perform only a manual collection and upload using the <ocm_install_root>/ccr/bin/emCCR collect command. To resume the collection of configuration data, use the emCCR resume command.

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

  • Prerequisites:

    • Oracle Configuration Manager is registered with Oracle.

    • The Scheduler is already running and is not on hold.

    • Oracle Configuration Manager must be running in Connected mode.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR hold
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ---------------------------------------------------------------
    Oracle Configuration Manager set on Hold successfully.
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied - This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered With Oracle - In this case, you must register Oracle Configuration Manager with Oracle.

    • Oracle Configuration Manager is Not Running - In this case, you must restart the Scheduler using the emCCR start command.

    • Oracle Configuration Manager is already on hold.

6.9 emCCR register

  • Usage: After you have installed Oracle Configuration Manager, it is automatically registered. If any of the registration information has changed, use this command to reregister Oracle Configuration Manager.

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

  • Prerequisites: Oracle Configuration Manager must be running in Connected mode.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR register
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ---------------------------------------------------------------
    REGISTER command completed successfully.
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

    • Cannot connect to the server.

    • Invalid credentials specified.

6.10 emCCR resume

  • Usage: Use this command to resume the automatic collection and uploading of the configuration data.

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

  • Prerequisites:

    • Oracle Configuration Manager is registered with Oracle.

    • Oracle Configuration is on hold.

    • The Scheduler is already running.

    • Oracle Configuration Manager must be running in Connected mode.

  • Example

    <ocm_install_root>/ccr/bin/emCCR resume
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ---------------------------------------------------------------- 
    Oracle Configuration Manager Resumed.
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered with Oracle: In this case, you must register Oracle Configuration Manager with Oracle.

    • Oracle Configuration Manager is not on hold.

    • Oracle Configuration Manager is Not Running - Restart the Scheduler using the emCCR start command.

6.11 emCCR set collection_interval

  • Usage: Use this command to define the schedule to collect configuration data. Configuration data can be collected daily, weekly, or monthly.

    • If configuration data is collected daily (FREQ=DAILY), you can specify the hour (BYHOUR) and the minute (BYMINUTE) at which the collection is to be performed.

    • If the frequency is weekly, you can specify the day of the week (BYDAY=[MON|TUE|WED|THU|FRI|SAT|SUN]) and the time (BYHOUR and BYMINUTE) at which the data is to be collected.

    • If the frequency is monthly, you can specify the date [BYMONTHDAY=1 to 31] and the time (BYHOUR and BYMINUTE) at which the collection is to be performed.

      <ocm_install_root>/ccr/bin/emCCR set collection_interval= 
                          "[FREQ=MONTHLY|WEEKLY|DAILY]
                           [; BYMONTHDAY=1 to 31, when FREQ is MONTHLY]
                           [; BYDAY=MON to SUN, when FREQ is WEEKLY]
                           [; BYHOUR=0 to 23] 
                           [; BYMINUTE=0 to 59]" 
      

    Note:

    Configuration data is collected only if the Scheduler has been started. By default, configuration data is collected DAILY at the time Oracle Configuration Manager was installed.

    The BYHOUR and BYMINUTE parameters can be used with all frequencies.

    If the frequency is set to MONTHLY, and the month does not include the value of the MONTHDAY, configuration data will not be collected for that month.

    You can verify the collection interval and the collection time by using the emCCR status command.

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

  • Prerequisites:

    • Oracle Configuration Manager is registered with Oracle.

    • The Scheduler is already running.

    • Oracle Configuration Manager must be running in Connected mode.

  • Example: Enter the command to specify that configuration data is to be collected on the fourth day of the month at 11.30 pm.

    <ocm_install_root>/ccr/bin/emCCR set collection_interval="FREQ=MONTHLY;BYMONTHDAY=4;BYHOUR=23;BYMINUTE=30"
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    Collection interval set successfully.
    
  • Errors: Some of the error messages you may see are:

    • Access Denied - This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered With Oracle - In this case, you must register Oracle Configuration Manager with Oracle.

    • Usage errors such as mismatched options are also returned.

6.12 emCCR start

  • Usage: Use this command to start the Scheduler.

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

  • Prerequisites: Oracle Configuration Manager must be running in Connected mode.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR start
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    Starting Oracle Configuration Manager...
    Waiting for status from Oracle Configuration Manager....
    Start Date               06-Jan-2012 07:51:18
    Last Collection Time     07-Jan-2012 11:12:00
    Next Collection Time     08-Jan-2012 11:12:00
    Collection Frequency     Daily at 11:12
    Collection Status        idle
    Log Directory            /u01/oracle/10.1.0/database/ccr/hosts/host1/log
    Registered At            05-Jan-2012 11:13:00
    Automatic Update         On
    Collector Mode           Connected  
    
    Oracle Configuration Manager successfully started.
    
  • Errors: Some of the error messages you may see are:

    • Access Denied - This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered With Oracle - In this case, you must register Oracle Configuration Manager with Oracle.

    • Oracle Configuration Manager is Already Running - In this case, the Scheduler has already been started. No action is required.

    • Registration failure errors.

6.13 emCCR status -diagnostic

  • Usage: Use this command to view the current status of all diagnostic uploads. The syntax for this command is as follows:

    emCCR status -diagnostic[=SR=<Service request number>,[FILE=<Absolute path of diagnostic package>]]
    
    • Specify the -diagnostic parameter to see the status of all diagnostics uploads.

    • Specify the -diagnostic parameter with the SR request to view the status of all uploads for a particular service request. The SR number must be in the format x-y where x represents one digit and y represents multiple digits, for example, 3-543210001.

    • Specify the -diagnostic parameter with SR and FILE options to view the status for a particular upload. FILE must include the name and the full path to the file that contains diagnostic information.

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

  • Prerequisites: Oracle Configuration Manager must be running in Connected mode.

  • Example 1

    <ocm_install_root>/ccr/bin/emCCR status -diagnostic=SR=3-543219500,FILE=/scratch/test/support_info.zip 
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    SR Number          1234.222
    Package Name       /scratch/test/support_info.zip
    Start Time         02-Jan-2012 09:23:13 
    Submit Time        02-Jan-2012 09:23:13 
    Update Time        02-Jan-2012 09:23:20 
    Restarts           0 
    Status             COMPLETED 
    Time Elapsed       00:00:07 
    ----------------------------------------------------------------
    

    Example 2: When Diagnostic Checks Package Needs Property Definitions

    <ocm_install_root>/ccr/bin/emCCR status
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.
    ------------------------------------------------------------------
    Start Date               24-Jan-2012 15:45:33
    Last Collection Time     24-Jan-2012 15:49:59
    Next Collection Time     25-Jan-2012 15:45:00
    Collection Frequency     Daily at 15:45
    Collection Status        idle
    Log Directory            <ocm_install_root>/ccr/hosts/abc/log
    Registered At            24-Jan-2012 14:45:13
    Automatic Update         On
    Collector Mode           Connected
    Diagchecks Status        Needs configuration
     
    Diagcheck errors:
    [database, ABC]: Missing properties
    Please run "configCCR -D [-T targetType [ -N targetName [-P propertyName]]]" to configure the diagcheck properties.
    
  • Errors: Some of the error messages you may see are the following:

    • Invalid SR format: This error occurs when the SR format does not match the required format of x-y where x is a single digit and y is multiple digits. To resolve this error, you must specify the SR number in the correct format.

    • No such diagnostic upload request exists. This error occurs if you run a -diagnostic command for a non-existent or invalid SR number or file name. To resolve this error, view the status of all submitted packages and specify the correct SR number or file name.

    • Could not access diagnostic upload data. This error occurs while reading or writing diagnostic upload data. To resolve this error, ensure that the diagnostic upload client has read and write permissions to the OCM_CONFIG_HOME/state directory.

    • The diagnostic upload state is not valid. Cannot perform the requested operation. Use upload -diagnostic to start fresh upload. This error occurs when the diagnostic package is corrupted. To resolve this error, use emCCR clear -force to clear the invalid upload request.

    • Invalid command. This error occurs when invalid arguments are specified on the command line. Use emCCR help, view all the command line options and enter the correct arguments.

6.14 emCCR stop

  • Usage: Use this command to stop the Scheduler. When the Scheduler has been manually stopped, the Scheduler is not restarted automatically after a reboot or by the cron job. You must start it manually using the emCCR start command. If you run the emCCR stop command when a data collection or another command is in progress, a stop pending message is displayed. Once the command in progress is completed, the Scheduler will be stopped.

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

  • Prerequisites: You can use this command only if the Scheduler is already running.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR stop
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    Oracle Configuration Manager Stopped...
    
  • Errors: Some of the error messages you may see are:

    • Access Denied - This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered With Oracle - In this case, you must register Oracle Configuration Manager with Oracle.

    • Oracle Configuration Manager is Not Running - Restart the Scheduler using the emCCR start command.

    • Stop Pending - a collection already in progress; the Scheduler will be stopped once the collection completes.

6.15 emCCR [-register] [-verbose] test

  • Usage: Use this command to test the connection to the server at Oracle. If you specify the -register option, the client will be registered during the test. The -verbose option displays detailed information about the connection process. Both -register and -verbose arguments are optional.

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

  • Prerequisites:

    • Oracle Configuration Manager is registered with Oracle.

    • Oracle Configuration Manager must be running in Connected mode.

  • Example 1:

    <ocm_install_root>/ccr/bin/emCCR -register test
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    -------------------------------------------------------------
    Verifying Proxy settings...
    No Proxy host set.
    Oracle Configuration Manager Server is: ccr.oracle.com
    Resolving Oracle Configuration Manager Server address...
    Connecting to Oracle Configuration Manager server...
    Registering with Oracle Configuration Manager server...
    
    Command successfully completed.
    
  • Example 2:

    <ocm_install_root>/ccr/bin/emCCR -verbose test
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    -------------------------------------------------------------
    Verifying Proxy settings...
    {main} [08:28:04.761] Conn:  added module HTTPClient.RetryModule
    {main} [08:28:04.771] Conn:  added module HTTPClient.CookieModule
    {main} [08:28:04.776] Conn:  added module HTTPClient.RedirectionModule
    {main} [08:28:04.782] Conn:  added module HTTPClient.AuthorizationModule
    {main} [08:28:04.783] Conn:  added module HTTPClient.DefaultModule
    {main} [08:28:04.789] Conn:  added module HTTPClient.TransferEncodingModule
    {main} [08:28:04.794] Conn:  added module HTTPClient.ContentMD5Module
    {main} [08:28:04.796] Conn:  added module HTTPClient.ContentEncodingModule
    No Proxy host set.
    Oracle Configuration Manager Server is: ccr.oracle.com
    Resolving Oracle Configuration Manager Server address...
    Connecting to Oracle Configuration Manager server...
    {main} [08:28:05.103] Conn:  Creating Socket: ccr.oracle.com:7782
    {main} [08:28:05.140] Demux: Initializing Stream Demultiplexor (6915075)
    {main} [08:28:05.792] Conn:  Sending Request: 
    GET /em/upload HTTP/1.1
    Host: ccr.oracle.com
    Connection: Keep-Alive, TE
    TE: trailers, deflate, gzip, compress
    User-Agent: RPT-HTTPClient/0.3-3
    Accept-Encoding: gzip, x-gzip, compress, x-compress
    
    {main} [08:28:05.804] Demux: Opening stream 18929195 for demux (6915075)
    {main} [08:28:05.804] Conn:  Request sent
    {main} [08:28:05.804] Resp:  Reading Response headers 18929195
    {main} [08:28:05.805] Resp:  Parsing Response headers from Request "GET
     /em/upload":  (18929195)
    
    HTTP/1.1 200 OK
    Date: Wed, 07 Jan 2012 17:32:47 GMT
    Server: Oracle-Application-Server-10g/10.1.2.2.0 Oracle-HTTP-Server
    Content-Length: 170
    Cache-Control: private
    Keep-Alive: timeout=5, max=999
    Connection: Keep-Alive
    Content-Type: text/xml; charset=windows-1252
    
    {main} [08:28:05.808] Resp:  Response entity delimiter: Content-Length (18929195)
    {main} [08:28:05.808] Conn:  Protocol Version established: HTTP/1.1
    Command successfully completed.
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

    • Cannot connect to the server.

    • Proxy server information is incorrect.

    • Proxy server is not available.

    For other registration errors, refer to the error messages listed under the emCCR register command.

6.16 emCCR update_components

  • Usage: Use this command to manually deploy any updates to the Oracle Configuration Manager client and deploy the Diagnostic Check package. You can either use the latest Oracle Configuration Manager distribution kit for the update or stage individual Oracle Configuration Manager packages in a local directory and deploy them by using this command. This command can be run in Connected or Disconnected mode. The syntax is as follows:

    <ocm_install_root>/ccr/bin/emCCR update_components [-silent] -staged_dir
    ="Directory containing OCM packages" | -distribution="OCM installation kit
    path"
    
    • If the -silent parameter is used, no output is displayed on the screen. You will see the prompt on the screen when the command has been executed.

    • Use the -staged_dir parameter to specify the directory in which the Oracle Configuration Manager packages have been staged. For the Diagnostic Check package,

    • Use the -distribution parameter to specify the Oracle Configuration Manager kit that will be used for deployment.

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

  • Prerequisites: None

  • Example 1: Sample output when staged directory contains one new package (core.jar) and an old package (scripts.jar).

    <ocm_install_root>/ccr/bin/emCCR update_components -stage_dir=
    "/scratch/updates/ocm_pkgs"
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    Deploying core - Version 10.3.8.0.0
    scripts.jar is an old package. No update required.
    

    Example 2: Sample output when staged directory does not contain any packages.

    <ocm_install_root>/ccr/bin/emCCR update_components -staged_dir=
    "/scratch/updates/ocm_pkgs"
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    No Oracle Configuration Manager packages are candidates for updating.
    

    Example 3: Sample output with the -distribution parameter:

    <ocm_install_root>/ccr/bin/emCCR update_components -distribution=
    /scratch/distribution/ccr-Production-10.3.8.0.0-Linux-i386.zip
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ---------------------------------------------------------------
    Deploying core - Version 10.3.8.0.0
    Deploying engines - Version 10.3.8.0.0
    Deploying metricdata - Version 10.3.7.0.0
    Deploying scripts - Version 10.3.8.0.0
    

    Example 4: Sample output when deploying a Diagnostic Checks package.

    <ocm_install_root>/ccr/bin/emCCR update_components -staged_dir=/scratch/user/diagheck
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.
    ------------------------------------------------------------------
    Deploying diagchecks - Version 10.3.8.0.0
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

    • Package not supported. This error occurs when the specified package is not supported by this platform or platform architecture. To resolve this error, download the latest packages which match target system's OS and processor architecture from My Oracle Support.

    • Not a valid OCM distribution. This error occurs when the <filespec> specified with the -distribution parameter is not valid. Ensure that the distribution kit is valid and has not been corrupted.

    • Not a valid OCM package. This error occurs when the directory specified in the -staged_dir parameter contains .jar files that are not OCM packages. This is an informational message and requires no action be taken.

    • A package deployment issue was encountered. This indicates an error during the deployment of a package. The log file containing failure details is displayed. Review the log file to find out the exact reason for the error.

    • No read access. This error occurs when you do not have permissions to read the target package or directory. Ensure that you have permissions to access the specified target package or directory.

    • Qualifiers -distribution and -staged_dir are mutually exclusive This error occurs when you specify the -distribution and -staged_dir arguments together. You cannot specify both the arguments at the same time. Refer to Section 6.7, "emCCR help" for the correct syntax.

    • Invalid directory specified for the -staged_dir qualifier. This error occurs if you specify the $OCM_HOME/inventory directory with -staged_dir qualifier. To resolve this error, specify a different directory for staging the packages.

    • No Oracle Configuration Manager packages are candidates for updating. This error occurs when the specified directory does not contain any Oracle Configuration Manager packages.

6.17 emCCR upload

  • Usage: Use this command to upload the configuration data to the Management Repository especially when an upload has failed. The collection upload failure can occur in either interactive or scheduled collections. In interactive collections, you get an error indicating that there was a problem uploading the files. In the scheduled collections, the message is recorded in the <OCM_CONFIG_HOME>/log/collector.log file.

    Collections, when already in connected mode, automatically upload collections.

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

  • Prerequisites:

    • Oracle Configuration Manager is registered with Oracle.

    • Configuration data must have been collected but not uploaded.

    • The Scheduler is already running.

    • Oracle Configuration Manager must be running in Connected mode.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR upload
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    Upload Done.
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered with Oracle: In this case, you must register Oracle Configuration Manager with Oracle.

    • Mandatory update available. Command failed.

    • Cannot connect with the server.

    • Handshake failure. You must register Oracle Configuration Manager.

    • Oracle Configuration Manager is Not Running - Restart the Scheduler using the emCCR start command.

6.18 emCCR upload -diagnostic

  • Usage: Use this command to upload a file containing diagnostic information to the Management Repository. You will be prompted for My Oracle Support credentials (user name and password).

    Note:

    When specifying an e-mail address, avoid using UNIX characters that overlap with the TTY terminal settings in use. Otherwise an undefined resultant behavior may occur.

    The file is generally a .zip file that contains all the files required to troubleshoot the specified SR (service request). This command can be run only in Connected mode. The syntax for this command is as follows:

    emCCR upload -diagnostic=SR=<Service request number>,FILE=<Absolute path of diagnostic package> [-restart] [-force]
    
    • The -restart parameter is used for an upload that is incomplete or has been aborted. When you use this parameter, upload will continue from the last successful point in the previous upload.

    • The -force parameter starts the upload from the beginning and overwrites anything on the server.

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

  • Prerequisite:

    • Oracle Configuration Manager is registered with Oracle.

    • Oracle Configuration Manager must be running in Connected mode.

  • Example:

    <ocm_install_root>/ccr/bin/emCCR upload 
    -diagnostic=SR=3-543210001,FILE=/scratch/test/support_info.zip
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle. All rights reserved.
    ----------------------------------------------------------------
    My Oracle Support User Name: <e-mail address>
    My Oracle Support User Password:          Initializing upload...
    Starting upload...
    Establishing connection to Oracle...
    Uploading...
    Upload completed.
    
    Command successfully completed.
    -----------------------------------------------------------------
    
  • Errors: Some of the error messages you may see are the following:

    • Access Denied: This error is displayed if you do not have the required privileges to run this command.

    • Oracle Configuration Manager Not Registered with Oracle: In this case, you must register Oracle Configuration Manager with Oracle.

    • Cannot connect with the server.

    • Handshake failure. You must register Oracle Configuration Manager.

    • Invalid SR format: This error occurs when the SR format does not match the required format of x-y. To resolve this error, you must specify the SR number in the correct format. The SR number must be in the format x-y where x represents one digit; y represents multiple digits.

    • No such diagnostic upload request exists. This error occurs if you restart a -diagnostic command for a non-existent or invalid SR number or file name. To resolve this error, view the status of all submitted packages and specify the correct SR number or file name.

    • Could not access diagnostic upload data. This error occurs while reading or writing diagnostic upload data. To resolve this error, ensure that the diagnostic upload client has read and write permissions to the OCM_CONFIG_HOME/state directory.

    • The diagnostic upload state is not valid. Cannot perform the requested operation. Use upload -diagnostic to start fresh upload. This error occurs when the diagnostic package is corrupted. To resolve this error, use emCCR clear -force to clear the invalid upload request.

    • Invalid command. This error occurs when invalid arguments are specified on the command line. Use emCCR help, view all the command line options, and enter the correct arguments.

    • Could not open diagnostic package file (No such file or directory). This error occurs when Oracle Configuration Manager cannot locate the file specified on the command line. To resolve this error, ensure that the file is available in the specified directory and specify the absolute path to the file.

    • Could not open diagnostic package file (Permission denied). This error occurs when Oracle Configuration Manager cannot access the file specified on the command line. To resolve this error, ensure that you have Read permission on the specified directory.

    • Following error occurred (actual error). This error occurs due to an unexpected reason. See OCM_HOME/log/collector.log for the exact reason for the error.

    • Failed to create directory structure for diagnostic state. This error occurs when the diagnostic upload client failed to store upload state. This error may occur due to lack of permissions. Ensure that the upload client has write permissions to the OCM_HOME/state directory.

    • Upload request already submitted. Please use -force to overwrite previous upload. This error occurs when you submit a second upload request for the same SR number and file name. In this case, you must use emCCR clear to clear the previous upload request and resubmit the upload request or use the -force option to overwrite the previous upload.

    • Upload already in progress. This error occurs when you try to upload a package which is currently being uploaded. This upload may have been initiated from a different system and is using the same SR number and file name as the upload currently being attempted. You must either cancel the current upload or specify a different SR number.

    • Error occurred in obtaining diagnostic upload endpoint URL for Oracle Configuration Manager. This error occurs when the upload client fails to obtain diagnostic receiver URL. Ensure that the OCM_HOME/config/default/ccr.properties or OCM_HOME/config/ccr.properties file contains ccr.endpoint property.

    • This diagnostic package is already uploaded. Use upload -diagnostic to start fresh upload. This error occurs when you try to restart the upload of an already uploaded package. To upload an already uploaded package, you must submit a new upload request.

    • Diagnostic package file modified since last upload. Use upload -diagnostic to start fresh upload. This error occurs when a package is modified during the upload procedure. It may also occur if you try to restart the upload of a package that has been modified since the last upload request. To upload the modified package, you must submit a new upload request.

    • Could not recognize server response. This error occurs when the client could not interpret the server response. Check the OCM_HOME/log/collector.log file for more details.

    • Maximum session time-out limit reached. The network connection is too slow. Please restart the upload to try again. This error occurs due to slow data transfer speed. Ensure that the upload bandwidth available at customer system is at least 56 kbps.

    • An internal server error has occurred. This error occurs due to internal issues at the server. Check the OCM_HOME/log/collector.log file for more details.

    • Unexpected error occurred during diagnostic upload. This error is caused due to unexpected errors that occurred when the diagnostic package was being uploaded. Check the OCM_HOME/log/collector.log file for more details.

    • This feature is currently not supported. This error occurs when the requested operation is not supported.

6.19 configCCR

Usage:

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 ] [ -c ] [ -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.

    configCCR
    
  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.

Parameters

  • The -a parameter configures Oracle Configuration Manager to run within the instance defined by the ORACLE_CONFIG_HOME environment variable or the current host.

    • If ORACLE_CONFIG_HOME is set to a valid directory, the Oracle Configuration Manager subdirectories are created in this directory, and the crontab entry (for UNIX platforms) or the service (for Windows platforms) for this instance is also created.

    • If ORACLE_CONFIG_HOME is not set, the Oracle Configuration Manager subdirectories are added to <ocm_install_root>/ccr/hosts/<hostname> (where hostname is the current host) and the crontab entry (for UNIX platforms) or the service (for Windows platforms) for this host is added.

    You can pass the configuration information on the command line, otherwise you will be prompted for the credentials.

  • The -c parameter designates an OCM collector installation to be a central collector. This option can be given with all other options except the -d option (disconnected mode). When a collector is configured as a central collector, it will collect data from Oracle homes that you own on this host whose collectors are either not configured or configured in disconnected mode.

  • The -C URL parameter defines the Oracle Support Hub used to connect to Oracle. If a proxy server is required to access the Oracle Support Hub, the user will be prompted for the proxy information.

  • If you use the -d parameter, Oracle Configuration Manager will be switched to Disconnected mode. In this mode, configuration data is not collected automatically. This mode is useful when your computer does not have Internet access. You can manually collect the data using the emCCR collect option. For details, refer to Section 6.3, "emCCR collect". When the -d parameter is used, do not use the following qualifiers: -C, -r, and -R.

  • The -D parameter configures missing diagnostic check properties. If you use the -D parameter without any qualifiers, you will be prompted for all required properties. The qualifiers associated with the -D parameter are:

    • The -v qualifier verifies that all target properties are properly configured, and no properties are missing.

    • The -T qualifier provides the target type for the target to be configured or verified. The -T qualifier is only used with the -D parameter.

    • The -N qualifier provides the target name for the target to be configured or verified. The -N qualifier is only used with the -D parameter. The -T qualifier must be specified.

    • The -P qualifier provides the target property name for the target to be configured or verified. The -P qualifier is only used with the -D parameter. The -T and -N qualifiers must be specified.

  • The -r parameter removes Oracle Configuration Manager instance-specific data from the instance directory.

    • If ORACLE_CONFIG_HOME is set, the Oracle Configuration Manager subdirectories are removed from this directory, and the associated crontab entry (for UNIX platforms) or the service (for Windows platforms) is also removed.

    • If ORACLE_CONFIG_HOME is not set, the directory <ocm_install_root>/ccr/hosts/<hostname> (where hostname is the current host) is removed and the associated crontab entry (for UNIX platforms) or the service (for Windows platforms) is also removed.

    Note:

    Parameters -a and -r are mutually exclusive. In a multi-host, shared home environment, no prerequisite steps are required to add or remove an instance home.

    In a single host, shared file system environment, you must first set the ORACLE_CONFIG_HOME environment variable to the instance home being added or removed before running configCCR -a or configCCR -r.

  • The -R parameter indicates the reconfiguration using the contents of the response file created using the emocmrsp utility. This parameter is mutually exclusive with the specification of the following on the command line: -d (disconnected mode), -s (signature accepted), and CSI and My Oracle Support User Name.

  • The -s parameter indicates the acceptance of the Oracle Configuration Manager license agreement. This parameter is optional.

  • The CSI and My Oracle Support User Name are optional and only used if you are using Oracle Configuration Manager in Connected mode or switching to Connected mode. All parameters can be specified on the command line. You will be prompted for any parameters that are not specified. After you specify the parameters, registration will be performed. If the registration fails, the original values for these parameters will be maintained.

    If the CSI is not specified and you are using connected mode, you will be prompted for the My Oracle Support User Name and Password.

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.

Restrictions

The following restrictions apply when you install Oracle Configuration Manager:

  • When specifying an e-mail address, avoid using UNIX characters that overlap with the TTY terminal settings in use. Otherwise an undefined resultant behavior may occur.

  • For Windows 2008, the user account control must be turned off when installing and using Oracle Configuration Manager. If user account control is on, Oracle Configuration Manager experiences permission errors during installations and other Oracle Configuration Manager operations.

Prerequisites

None

Examples

  • Example 1

    This example demonstrates the use of the configCCR command without the use of parameters.

    <ocm_install_root>/ccr/bin/configCCR
    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 http://www.oracle.com/support/policies.html for details.
    Email address/User Name: joe.smith@example.com
    Provide your My Oracle Support password to receive security updates via your
    My Oracle Support account.
    Password (optional):           
    
    ** Validating configuration changes with Oracle Configuration Manager server(s) **
    

    Usage:

    joe.smith@example.com represents the My Oracle Support User Name

    The user is prompted for the My Oracle Support Password which is not echoed.

  • Example 2

    This example demonstrates the use of the configCCR command specifying CSI and My Oracle Support User Name.

    <ocm_install_root>/ccr/bin/configCCR 123456 cust@customercorp.com
    
    ** Validating configuration changes with Oracle Configuration Manager server(s) **
    

    Usage:

    123456 represents the Customer Support Identifier (CSI)

    cust@customercorp.com represents the My Oracle Support User Name

  • Example 3

    This example demonstrates the use of the configCCR command specifying the CSI. The user is prompted for My Oracle Support User Name.

    <ocm_install_root>/ccr/bin/configCCR 123456 
    Configuration requires the following pieces(s) of information.
        My Oracle Support User Name: cust@customercorp.com
    
    ** Validating configuration changes with Oracle Configuration Manager server(s) **
    

    Usage:

    123456 represents the Customer Support Identifier (CSI)

    cust@customercorp.com represents the My Oracle Support User Name

  • Example 4

    This example demonstrates the use of the configCCR command without parameters but where a proxy server is required. The proxy server being used requires authentication.

    <ocm_install_root>/ccr/bin/configCCR
    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 http://www.oracle.com/support/policies.html for details.
    Email address/User Name: joe.smith@example.com
    Provide your My Oracle Support password to receive security updates via your My 
    Oracle Support account.
    Password (optional):           
    
    Unable to establish a network connection to Oracle. Specify the URL for an
    Oracle Support Hub in this format:
        http[s]://<OracleSupportHubHost>:<OracleSupportHubPort>
    If you do not wish to configure OCM through an Oracle Support Hub, enter NONE
    Oracle Support Hub URL: http://host123.company.com:7654
     
    Unable to establish a network connection to the Oracle Support Hub. If your
    systems require a local proxy server, enter the proxy server details in this
    format:
        [<proxy-user>@]<proxy-host>[:<proxy-port>]
    
    If you want to remain uninformed of critical security issues in your
    configuration, enter NONE
    Proxy specification: ccr@ssmith-sun:8083
    Proxy Password:          
    Proxy information verified, validating specified email value(s).
    
    ** Validating configuration changes with Oracle Configuration Manager server(s) **
    

    Usage:

    ccr@ssmith-sun:8083 represents the proxy server information where: ccr is the proxy user, ssmith-sun is the proxy server, and 8083 is the proxy port.

    joe.smith@example.com represents the My Oracle Support User Name. At the prompt, you enter the My Oracle Support Password. The password is not echoed.

  • Example 5

    This example demonstrates the use of the configCCR command configuring missing Diagnostic Checks properties.

    <ocm_install_root>/ccr/bin/configCCR -D -T database -N ABC
    Please enter the values for the following missing properties (Hit enter key to skip configuring a property).
    Target [database, ABC], Property name: MachineName
    Please enter the property value: mysys.us.company.com
    Target [database, ABC], Property name: Port
    Please enter the property value: 1483
    Target [database, ABC], Property name: SID
    Please enter the property value: DBSID
    Target [database, ABC], Property name: UserName
    Please enter the property value:          
    Target [database, ABC], Property name: password
    Please enter the property value:          
     
    Note: The username and password are not echoed to the console and they must be
    confirmed, that is, you must type the username and passwowrd a second time.
    

    Usage:

    database represents the target type

    ABC represents the name of the target

Errors

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

  • Failure in registering with Oracle Configuration Manager server. Invalid credentials specified

    The My Oracle Support User Name (e-mail address) or Password or both are incorrect. If you get this message three times when you are registering using configCCR, you will register in unauthenticated mode.

  • This installation is already configured for Oracle Configuration Manager. Please remove existing configuration first.

    Received when executing configCCR -a and the host or ORACLE_CONFIG_HOME has already been configured for Oracle Configuration Manager.

  • ORACLE_CONFIG_HOME refers to a non-existent directory. Redefine $ORACLE_CONFIG_HOME to refer to the correct location or unset it if the configuration state is in the ccr directory tree.

    The ORACLE_CONFIG_HOME environment variable is defined to a nonexistent directory. The user must redefine the variable to a valid directory and rerun the configCCR command.

  • The Oracle Configuration Manager state/writable directory structure is incomplete. OCM is not configured for this host or ORACLE_CONFIG_HOME. Please configure OCM first.

    Received when executing configCCR -r and the host or ORACLE_CONFIG_HOME has already been removed.

  • The configCCR command cannot be executed as root. It can only be executed as the owner of the ORACLE_HOME.

  • The Oracle Configuration Manager install can support only one instance.

    The user is running a version of Oracle Configuration Manager that has been upgraded from a version prior to 10.2.7.0.0 and is attempting to configure a shared home. To use the shared home support, Oracle Configuration Manager must be deinstalled from the Oracle home and reinstalled.

  • Invalid My Oracle Support credentials.

    The My Oracle Support User Name (e-mail address) or Password or both are incorrect. If you get this message three times when you are registering using configCCR, you will register in unauthenticated mode.

    Invalid CSI or My Oracle Support User Name will also return this error.

6.20 deriveCCR

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

Usage:

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
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.

Parameters:

  • If no parameters are specified on the command line, configuration information is extracted from the Oracle Configuration Manager information in the source home.

    If connectivity cannot be established to Oracle using Oracle Configuration Manager information from the source home, you will be prompted for all connection information.

  • If you use the -d parameter, Oracle Configuration Manager will be configured to Disconnected mode. In this mode, configuration data is not collected automatically. This mode is useful when your computer does not have Internet access. When the -d parameter is used, do not use the following qualifiers: -C and -R.

  • The -C <OracleSupportHubUrl> parameter defines the Oracle Support Hub used to connect to Oracle. The deriveCCR command will prompt for User Name, Password and, if required, a proxy server.

  • The -R parameter indicates deriveCCR will get the configuration information from the response file created using the emocmrsp utility. This parameter is mutually exclusive with the specification of the following on the command line: -d (disconnected mode) and CSI and My Oracle Support User Name.

  • Specify the CSI and My Oracle Support User Name if you want to use a specific CSI and My Oracle Support User Name. The deriveCCR command will prompt you for any other configuration information required for connectivity to Oracle. After you specify the parameters, registration will be performed.

    If the registration fails, you will be prompted again for the information. If the validation fails three times, deriveCCR will configure Oracle Configuration Manager in unauthenticated mode.

Execute Privileges

Can only be executed by <ocm_install_root> owner.

Restrictions

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.

Prerequisites

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

Examples

  • Example 1

    This example demonstrates the use of the deriveCCR command without the use of parameters.

    <ocm_install_root>/ccr/bin/deriveCCR
    Snapshot the environmental variables.
    Ensure OCM collector is not already running by executing emCCR status.
    OCM collector is not running... continue to derive the OCM collector 
    installation.
    Gleaning OCM collector installation to create a temporary response file.
    Verifying the gleaned response file.
    Configuration connectivity verified successfully.
    Derived OCM collector will be configured using the gleaned response file.
    Invoking configCCR to re-configure using the gleaned response file.
    
    ** Installing base package **
    Deploying core - Version 10.3.8.0.0
    
    ** Registering installation with Oracle Configuration Manager server(s) **
    
    ** Getting package updates from ContentServer **
    
    ** Starting the Oracle Configuration Manager Scheduler **
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.
    ------------------------------------------------------------------
    Starting Oracle Configuration Manager...
    Waiting for status from Oracle Configuration Manager....
    Start Date               16-Jan-2012 12:04:12
    Last Collection Time     -
    Next Collection Time     17-Jan-2012 12:02:00
    Collection Frequency     Daily at 12:02
    Collection Status        scheduled collection running
    Log Directory            <ocm_install_root>/ccr/hosts/abc/log
    Registered At            16-Jan-2012 12:04:07
    Automatic Update         On
    Collector Mode           Connected
    
    Oracle Configuration Manager successfully started.
    
    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
    (http://www.oracle.com/technology/documentation/ocm.html) to complete the
    installation.
    
    View configuration data reports and access valuable configuration best
    practices by going to My Oracle Support.
    
  • Example 2

    This example demonstrates the use of the deriveCCR command using the CSI.

    <ocm_install_root>/ccr/bin/deriveCCR 12345678
    Snapshot the environmental variables.
    Ensure OCM collector is not already running by executing emCCR status.
    OCM collector is not running... continue to derive the OCM collector installation.
    Invoking configCCR to re-configure.
    Configuration requires the following pieces(s) of information.
        My Oracle Support User Name: ccrsmpdevelopment@sleepycat.com
     
    ** Installing base package **
    Deploying core - Version 10.3.8.0.0
     
    ** Registering installation with Oracle Configuration Manager server(s) **
     
    ** Getting package updates from ContentServer **
     
    ** Starting the Oracle Configuration Manager Scheduler **
    Oracle Configuration Manager - Release: 10.3.8.0.0 - Production
    Copyright (c) 2005, 2012, Oracle and/or its affiliates.  All rights reserved.
    ------------------------------------------------------------------
    Starting Oracle Configuration Manager...
    Waiting for status from Oracle Configuration Manager....
    Start Date               16-Jan-2012 12:07:18
    Last Collection Time     -
    Next Collection Time     17-Jan-2012 12:02:00
    Collection Frequency     Daily at 12:02
    Collection Status        scheduled collection running
    Log Directory            <ocm_install_root>/ccr/hosts/abc/log
    Registered At            16-Jan-2012 12:07:15
    Automatic Update         On
    Collector Mode           Connected
     
    Oracle Configuration Manager successfully started.
     
    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
    (http://www.oracle.com/technology/documentation/ocm.html) to complete the
    installation.
     
    View configuration data reports and access valuable configuration best
    practices by going to My Oracle Support.
    
  • Example 3

    This example demonstrates the use of the deriveCCR command using the disconnected (-d) parameter.

    <ocm_install_root>/ccr/bin/deriveCCR -d
    Snapshot the environmental variables.
    Ensure OCM collector is not already running by executing emCCR status.
    OCM collector is not running... continue to derive the OCM collector installation.
    Invoking configCCR to re-configure.
    Visit http://www.oracle.com/support/policies.html for Oracle Technical Support policies.
     
    ** Installing base package **
    Deploying core - Version 10.3.8.0.0
     
    Oracle Configuration Manager has been configured in disconnected 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
    (http://www.oracle.com/technology/documentation/ocm.html) to complete the
    installation.
     
    View configuration data reports and access valuable configuration best
    practices by going to My Oracle Support.
    

Errors

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