Skip Navigation Links | |
Exit Print View | |
Installing Oracle Solaris 11.1 Systems Oracle Solaris 11.1 Information Library |
Part I Oracle Solaris 11.1 Installation Options
1. Overview of Installation Options
Part II Installing Using Installation Media
2. Preparing for the Installation
5. Automated Installations That Boot From Media
6. Unconfiguring or Reconfiguring an Oracle Solaris instance
Part III Installing Using an Install Server
7. Automated Installation of Multiple Clients
8. Setting Up an Install Server
10. Provisioning the Client System
11. Configuring the Client System
12. Installing and Configuring Zones
13. Running a Custom Script During First Boot
15. Troubleshooting Automated Installations
Part IV Performing Related Tasks
A. Working With Oracle Configuration Manager
Introduction to Oracle Configuration Manager
Administering Oracle Configuration Manager (Tasks)
How to Enable the Oracle Configuration Manager Service
How to Disable the Oracle Configuration Manager Service
How to Manually Register Your System With the Oracle Repository
How to Change the Time or Frequency of Data Collection for Oracle Configuration Manager
The Oracle Configuration Manager collector installed as part of the Oracle Solaris operating system is configured and designated as a central collector. To reap the benefits of an Oracle Configuration Manager collector, such as a personalized support experience, quicker resolution of support issues, and proactive problem avoidance, the configuration data for each Oracle installation must be collected and uploaded. This is normally the task of the collector installed in the Oracle home. However, sometimes the collector in Oracle homes might not have been configured or is left disconnected. The purpose of the central collector is to collect those Oracle homes and upload them under its own My Oracle Support (MOS) credentials. Here are the characteristics of a central collector:
A central collector collects:
The Oracle home in which it resides
Oracle homes on the host that do not have a configured collector
Oracle homes where the collector is in disconnect mode
Oracle homes where the collector has authenticated registration
If a collector in an Oracle home is configured using ORACLE_CONFIG_HOME designation, the central collector will not collect that home.
Using the root role, you can designate a collector installation to be a central collector by specifying the -c option in the setupCCR and configCCR commands. Subsequent configCCR commands without the -c option relinquish the central collector designation from the collector. Running the setupCCR and configCCR commands with the -c option designates the collector as a central collector. The collector installed as part of the Oracle Solaris operating system is installed using root permissions, hence it operates as the central collector for the host.
The Oracle Universal Installer central inventory is the source from which the central collector obtains the set of candidate Oracle homes to be collected. The central inventory is searched by the installer as described in the documentation. The default location for the installer central inventory pointer for the Oracle Solaris operating system is /var/opt/oracle/oraInst.loc. If you choose to place an Oracle installation inventory in a different location, then the central inventory can not find and collect it.
In this release, beyond the configuration information from the Oracle Solaris OS, only Oracle database and Oracle Fusion Middleware based products that use Oracle WebLogic are collected by the central collector.
All configuration data collected by the central collector from Oracle homes is uploaded using the My Oracle Support credentials of the central collector.