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.
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 4.36 [OC 12.2.2.808,SunOS11] ======================== Checking Network Connectivity ============================== Using Ops Center Proxy server:example-proxy.company.com Port:80 (you may overwrite it by setting https_proxy) Please enter the My Oracle Support (MOS) Username: example.user@company.com Password: Test 1/4: Checking CC service reachability (without using user/password yet) ============================================================================== Connecting to https://hs-ws1.oracle.com/ochi/servicecheck?type=cc OK: CC status is OK Test 2/4: Checking GUUS service (KnowledgeBase Service) reachability (without using user/password yet) ============================================================================== Connecting to https://hs-ws1.oracle.com/ochi/servicecheck?type=guus OK: GUUS status is OK Test 3/4: Downloading Knowledge Channels file from updates.oracle.com =========================================================================== Connecting to https://updates.oracle.com/channels3/channels.xml OK: Knowledge download was successful! Test 4/4: Downloading patch 108437-06 from updates.oracle.com =========================================================================== Connecting to https://updates.oracle.com/all_unsigned/108437-06.zip OK: Patch download was successful!
The OCDoctor can help you troubleshoot issues and tune systems.
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 Ops Center Doctor 4.36 [OC 12.2.2.808,SunOS11] [Read only] [31-Mar-2014 10:34AM MDT] ======================== Checking Enterprise Controller... ============================== OK: Total number of agents (without Solaris 11 ones): 20 OK: Number of agents with inventories: 20 OK: Enterprise Controller requirements are met OK: Files in /var/opt/sun/xvm/images/agent/ have the right permissions OK: Files in /var/opt/sun/xvm/osp/web/pub/pkgs/ have the right permissions OK: both pvalue and pdefault in systemproperty are equal to false (at id 114) OK: Found only 57 OCDB*.aud files in oracle/admin/OCDB/adump folder OK: Found no ocdb*.aud files in oracle/admin/OCDB/adump folder OK: No auth.cgi was found in cgi-bin OK: User 'oracleoc' home folder points to the right location OK: User 'allstart' home folder points to the right location OK: Apache logs are smaller than 2 GB OK: n1gc folder has the right permissions OK: All agent packages are installed properly OK: All Enterprise Controller packages are installed properly OK: Enterprise Controller status is online <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 4.36 [OC 12.2.2.808,SunOS11] Trying to download updates... Using Ops Center Proxy server:example-proxy.company.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: 4.36, online: 4.36). You may force downloading the online version by running: # ./OCDoctor.sh --update --force
An access point is a connection between a managed asset and the Enterprise Controller through a Proxy Controller. The number of access points for the Enterprise Controller and for each Proxy Controller provides more accurate scaling information than the number of assets.
A single managed asset can have one or more access points, depending on how many Proxy Controllers are managing it. For example, if an Oracle VM Server for SPARC control domain's operating system is managed by one Proxy Controller while a hosted logical domain's operating system is managed by another Proxy Controller, the Enterprise Controller has two access points for that asset.
The OCDoctor utility includes a script, AssetCount.sh, that you can run on the Enterprise Controller to get the current access point count for the Enterprise Controller and each Proxy Controller, including a breakdown of the type of assets on each Proxy Controller.
When the OCDoctor utility is run with the --troubleshoot option, it performs an access point count. If the results of this count indicate that the Enterprise Controller or Proxy Controllers are approaching or beyond the maximum recommended number of assets, the output will include a warning.
When you run the ./OCDoctor.sh --collectlogs command on the Enterprise Controller, the current access point count is included in the output. The current access point count can be useful when troubleshooting an issue.
The following methods can be used to view the access point count:
You can view the total number of access points managed by the Enterprise Controller, as well as a categorized count of the access points managed by each Proxy Controller. Run the following command on the Enterprise Controller:
# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh standard
For example:
# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh standard EC 72 Proxy Assets Zones Ldoms OVMGuests Servers Storages Switches ExadataCells MSeriesChassis MSeriesD ------------------------------------------------------------------------------------------------- pc4 32 5 25 0 2 0 0 0 0 0 pc1 28 0 26 0 2 0 0 0 0 0 pc0 12 2 4 0 6 0 0 0 0 0 Use option '-v' to see additional notes on the counting algorithm.
You can view a list of the access points of each type that are managed by each Proxy Controller. The output first provides the total number of access points on the Enterprise Controller, then for each Proxy Controller provides the total number of access points, the number of access points of each type, and the user-friendly name for each asset.
The output for this command can be very long in a large environment.
Run the following command on the Enterprise Controller:
# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh machine
For example:
# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh machine EC 72 Proxy 32 pc4 Zones 5 S11zone101 S11zone102 S11zone100 S11zone103 S11zone104 Ldoms 25 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ... OVMGuests 0 Servers 2 10.187.70.169 pc4 ... Proxy 28 pc1 Zones 0 Ldoms 26 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ... OVMGuests 0 Servers 2 10.187.70.171 pc1
You can view a count of the access points for each Proxy Controller in three categories: Agent Controllers, Agentless assets, and service processors.
Run the following command on the Enterprise Controller:
# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh agent
For example:
# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh agent EC 72 Proxy Agents Agentless SPs -------------------------- pc4 25 2 0 pc1 1 1 0 pc0 5 5 5 Use option '-v' to see additional notes on the counting algorithm.
You can view all access point data, including the results of the standard, machine, and agent options.
Run the following command on the Enterprise Controller:
# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh all
For example:
# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh all EC 72 Proxy Assets Zones Ldoms OVMGuests Servers Storages Switches ExadataCells MSeriesChassis MSeriesD ------------------------------------------------------------------------------------------------- pc4 32 5 25 0 2 0 0 0 0 0 pc1 28 0 26 0 2 0 0 0 0 0 pc0 12 2 4 0 6 0 0 0 0 0 Proxy Agents Agentless SPs -------------------------- pc4 25 2 0 pc1 1 1 0 pc0 5 5 5 Proxy 32 pc4 Zones 5 S11zone101 S11zone102 S11zone100 S11zone103 S11zone104 Ldoms 25 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ... OVMGuests 0 Servers 2 10.187.70.169 pc4 ... Proxy 28 pc1 Zones 0 Ldoms 26 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ... OVMGuests 0 Servers 2 10.187.70.171 pc1 Use option '-v' to see additional notes on the counting algorithm.