This chapter contains the following sections:
Configuration data is automatically collected on a regular schedule. By default, collections are scheduled to run daily at the time the original installation was done. To start a manual collection of configuration data, enter the following command:
$ORACLE_HOME/ccr/bin/emCCR collect
This command collects the configuration data and uploads it to the repository. Configuration data is collected only if the Scheduler has been started. The Scheduler is always running unless it has been manually stopped with the emCCR stop command. In this case, you will have to manually restart the Scheduler so that configuration data can be automatically collected. Check the status of the Scheduler by entering emCCR status which indicates whether the Scheduler has been started. To start the Scheduler, enter the following command:
$ORACLE_HOME/ccr/bin/emCCR start
The Scheduler acts as a coordinator of activities, and provides both a richer schedule capability and the ability to perform collections on a regular schedule. Scheduled collections are only available when Oracle Configuration Manager is running in Connected mode.
Configuration data can be collected daily, weekly, or monthly, at a particular date and time. You can set the interval for automatically collecting the configuration data with the emCCR set collection_interval command.
The emCCR stop, emCCR set collection_interval, emCCR hold, emCCR resume, emCCR getupdates, emCCR upload, and emCCR config commands can be used only if the Scheduler has been started.
For more information on these commands, refer to Chapter 5, "Managing the Oracle Configuration Manager Client".
If you are using Oracle Configuration Manager in Disconnected mode, configuration data needs to be manually collected. As the Scheduler is not running in this mode, it cannot be used to automatically collect configuration data at regular intervals.
You can collect configuration data manually by using the emCCR collect command. When you run this command, the ocmconfig.jar is created in the $ORACLE_HOME/ccr/state/upload/ directory. This file contains the manually collected configuration data. You can then upload this file to the Oracle server. For more details on manual collection of configuration data, refer to Chapter5, "emCCR collect".
In this mode, the only commands supported are emCCR collect, emCCR status, emCCR enable_target, emCCR disable_target, emCCR update_components, configCCR, and emCCR help.
You can update Oracle Configuration Manager either manually or automatically.
Updating Oracle Configuration Manager Automatically: After the Oracle Configuration Manager client has been installed in Connected mode, it automatically schedules a collection. If any updates to the Oracle Configuration Manager client are available, they are downloaded and applied when the configuration data is collected.
To disable the automatic updates, enter the following command:
$ORACLE_HOME/ccr/bin/emCCR automatic_update off
Note:
The automatic update feature is enabled by default. When you disable automatic updates, the configuration data will be collected and uploaded until a new mandatory Oracle Configuration Manager software update is available. When a mandatory update is available, configuration data will not be collected or uploaded until the mandatory update is installed.If you have disabled the automatic updates, the updates can be manually downloaded and applied. To manually download and deploy the updates, enter the following command:
$ORACLE_HOME/ccr/bin/emCCR getupdates
Updating Oracle Configuration Manager Manually: You can manually apply updates by using the emCCR update_components command. 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 the emCCR update_components command. This command can be used in both Connected and Disconnected modes. For more information on this command, refer to Chapter5, "emCCR update_components".