Oracle Enterprise Manager Ops Center includes the OCDoctor utility, a tool that can check systems for installation prerequisites, troubleshoot issues, and tune systems for Oracle Enterprise Manager Ops Center. This chapter discusses the use of the OCDoctor.
The following features and topics are covered in this chapter:
The OCDoctor is a tool that can provide a variety of information about Oracle Enterprise Manager Ops Center and current or potential Enterprise Controller, Proxy Controller, and Agent Controller systems.
The OCDoctor is located in the /var/opt/sun/xvm/OCDoctor directory on the Enterprise Controller system. You can copy the OCDoctor to other systems or download it from Oracle. Once you have copied it onto a system, you can perform preinstallation checks, troubleshoot issues, and check for OCDoctor updates.
If you are operating in disconnected mode, or if you want to install the latest version of the OCDoctor on a new system, you can download the latest version from Oracle.
On an Internet-facing system, navigate to http://java.net/projects/oc-doctor/downloads and click the OCDoctor-LATEST.zip download.
Move the downloaded file to the target system.
Unzip the file.
If the target system is an existing Enterprise Controller, replace the contents of the /var/opt/sun/xvm/ocdoctor directory with the contents of the zip file.
You can use the OCDoctor to verify that systems meet the prerequisites for an Oracle Enterprise Manager Ops Center installation, get a benchmark score, or check the system's connectivity.
To Perform Preinstallation Checks
Change to the /var/opt/sun/xvm/OCDoctor directory.
Run the OCDoctor.sh script with one of the following options:
--ec-prereq: Verifies that the system meets the prerequisites for an Enterprise Controller installation.
--proxy-prereq: Verifies that the system meets the prerequisites for a Proxy Controller installation.
--agent-prereq: Verifies that the system meets the prerequisites for an Agent Controller installation.
--performance: Checks the speed of the system and provides a Benchmark Time (BT) score. You can use a BT score to estimate how many assets a system can effectively manage. You should use this option when the system is idle.
--check-connectivity: Verifies that the system has network connectivity by connecting to My Oracle Support and downloading two test files.
For example:
# ./OCDoctor.sh --check-connectivity Ops Center Doctor version 3.06 (Jan 21 2012 [Build 450]), OC Version 12.1 (SunOS) ======================== Checking Network Connectivity ============================== Using Ops Center Proxy server:www-proxy.us.oracle.com Port:80 (you may overwrite it by setting https_proxy) Please enter the My Oracle Support (MOS) Username: owen.allen@oracle.com Password: Test 1/2: Downloading Knowledge Channels file from updates.oracle.com =========================================================================== OK: Knowledge download was successful! Test 2/2: Downloading patch 108437-06 from updates.oracle.com =========================================================================== OK: Patch download was successful!
The OCDoctor can help you troubleshoot issues and tune systems.
To Perform Troubleshooting and Tuning
Change to the /var/opt/sun/xvm/OCDoctor directory.
Run the OCDoctor.sh script with one of the following options:
--troubleshoot: Troubleshoots common problems and suggests solutions. You can also use the --fix option to automatically fix certain issues.
--collectlogs <parameters>: Collects all logs from the current system. You can add optional parameters to pass the logs to collection scripts.
--needhelp: Provides information on gathering additional system information and filing a support case.
--tuning: Scans the current system and suggests changes to improve system performance. You can also use the --fix option to automatically apply some tuning improvements.
--whatisblobid <id>: Provides details about the specified blob id.
--getblobid <patch id>: Provides the blob id for a specified patch.
For example:
# ./OCDoctor.sh --troubleshoot
======================== Checking Enterprise Controller... ==============================
OK: Total number of agents: 12
OK: Number of agents with inventories: 12
OK: Enterprise Controller requirements are met
OK: SUNWj6rt version matches SUNWj6rtx version (1.6.0_21)
OK: Apache logs are smaller than 2 GB
OK: n1gc folder has the right permissions
OK: All Enterprise Controller packages are installed properly
OK: All agent packages are installed properly
OK: All agent patches are installed properly
WARNING: Enterprise Controller status is not online - try starting it using the command:
/opt/SUNWxvmoc/bin/ecadm start -w
<output omitted>
The OCDoctor can locate and download updates if it is on an Internet-facing system. The Enterprise Controller performs this update automatically. You can also perform this update manually.
Change to the /var/opt/sun/xvm/OCDoctor directory.
Run the OCDoctor.sh script with the --update option. If you want to force a download of the latest online version, use the --force option.
For example:
# ./OCDoctor.sh --update Ops Center Doctor version 3.06 (Jan 21 2012 [Build 450]), OC Version 12.1 (SunOS) Trying to download updates... Using Ops Center Proxy server:www-proxy.us.oracle.com Port:80 Downloading version file using mirror: updates.oracle.com OK: Version file was downloaded successfully OK: Connected successfully - but no updates were found (current: 3.06, online: 3.06). You may force downloading the online version by running: # ./OCDoctor.sh --update --force