3 Using the ORAchk Plug-in
The following sections are provided:
Accessing Compliance Results Details
The Compliance Results shows a listing of all targets including targets that are 100% compliant to a particular standard and targets that have compliance issues. ORAchk results are included in this list to show any Engineered Systems target that may be out of compliance.
You can access the Compliance Results for ORAchk/Exachk by:
Accessing ORAchk/Exachk Compliance Results through the Enterprise Menu
To view the Compliance Results for ORAchk/Exachk:
Accessing ORAchk/Exachk Compliance Results through the Target Home Page
To access Compliance Results for ORAchk/Exachk from the target home page:
Accessing ORAchk/Exachk Compliance Framework Details through the Compliance Dashboard
To access the compliance framework details through the compliance dashboard:
Compliance Content for Optional Targets
The ORAchk Healthchecks plug-in registers compliance content for all supported target types. In cases where users have not deployed optional plug-ins that ships some of the supported target types, compliance content will not be registered for such types.
For example, for target types such as TimesTen Database for Exalytics System, Oracle ZFS Storage Appliance target for Exalogic System, and so forth, if you deploy such plug-ins later, then you can download the compliance content from Self update and apply later.
Note:
Compliance contents for the same ORAchk version should be deployed as available in the Software library.
Compliance Standards for All Supported System Types
The following sections list the compliance standards for all supported system types:
Oracle Exadata Database Machine Compliance Standards
-
Exachk Cluster Best Practices For Oracle Exadata Database Machine
-
Exachk Oracle High Availability Service Best Practices For Oracle Exadata Database Machine
-
Exachk Host Best Practices For Oracle Exadata Database Machine
-
Exachk Database Instance Best Practices For Oracle Exadata Database Machine
-
Exachk Oracle Exadata Storage Server Best Practices For Oracle Exadata Database Machine
-
Exachk Oracle Infiniband Switch Best Practices For Oracle Exadata Database Machine
-
Exachk Systems Infrastructure Switch Best Practices For Oracle Exadata Database Machine
-
Exachk Cluster ASM Best Practices For Oracle Exadata Database Machine
-
Exachk Automatic Storage Management Best Practices For Oracle Exadata Database Machine
-
Exachk Cluster Database Best Practices For Oracle Exadata Database Machine
Exalogic Elastic Cloud Compliance Standards
-
Exachk Best Practices For Exalogic Elastic Cloud
-
Exachk Host Best Practices For Exalogic Elastic Cloud
-
Exachk Oracle Infiniband Switch Best Practices For Exalogic Elastic Cloud
-
Exachk Systems Infrastructure Switch Best Practices For Exalogic Elastic Cloud
-
Exachk Oracle ZFS Storage Server Best Practices For Exalogic Elastic Cloud
-
Exachk Oracle VM Guest Best Practices For Exalogic Elastic Cloud
-
Exachk Oracle VM Server Best Practices For Exalogic Elastic Cloud
-
Exachk Sun ZFS Storage 7000 Best Practices For Exalogic Elastic Cloud
Exalytics System Compliance Standards
-
Exachk Best Practices For Exalytics System
-
Exachk Host Best Practices For Exalytics System
-
Exachk Oracle BI Instance Best Practices For Exalytics System
-
Exachk TimesTen In Memory Database 11g Best Practices For Exalytics System
Cluster Compliance Standards
-
ORAchk Best Practices For Cluster
-
ORAchk Oracle High Availability Service Best Practices For Cluster
-
ORAchk Host Best Practices For Cluster
-
ORAchk Database Instance Best Practices For Cluster
-
ORAchk Automatic Storage Management Best Practices For Cluster
-
ORAchk Cluster Database Best Practices For Cluster
Recovery Appliance Compliance Standards
-
Exachk Cluster Best Practices For Recovery Appliance
-
Exachk Oracle High Availability Service Best Practices For Recovery Appliance
-
Exachk Host Best Practices For Recovery Appliance
-
Exachk Database Instance Best Practices For Recovery Appliance
-
Exachk Oracle Exadata Storage Server Best Practices For Recovery Appliance
-
Exachk Oracle Infiniband Switch Best Practices For Recovery Appliance
-
Exachk Systems Infrastructure Switch Best Practices For Recovery Appliance
-
Exachk Automatic Storage Management Best Practices For Recovery Appliance
-
Exachk Cluster Database Best Practices For Recovery Appliance
Self Updates
The regular updates for compliance standards, for each ORAchk/Exachk release, will be provided through Enterprise Manager Cloud Control's Self Update feature. For every ORAchk/Exachk release, the following self update downloads will be available:
-
ORAchk/Exachk Generic Compliance Content
-
Exachk Exalogic Compliance Content
-
Exachk Exalogic Virtualization Compliance Content
-
Exachk Exalogic Sun ZFS Compliance Content
-
Exachk Exalytics Compliance Content
-
Exachk Exalytics TimesTen Compliance Content
All updates are organized into multiple downloads to allow users to choose among these depending upon the applicability for an Enterprise Manager instance. For example, all users may not need the Exalytics update because they do not have an Exalytics target.
Troubleshooting the ORAchk Plug-in
This section describes common problems you may encounter with the ORAchk plug-in, including:
Special Purpose Compliance Rules
Two compliance rules, which are available in the ORAchk plug-in, help users to self service some of the issues that your system may encounter:
-
"Is ORAchk configured" or "Is Exachk Configured"
This rule aids in identifying if users associate the compliance standard meant for ORAchk/Exachk directly with a target. The ORAchk/Exachk standards can be associated only using deployment steps explained in Provisioning ORAchk.
-
"Is Exachk collection stale" or "Is ORAchk collection stale"
This rule violates if ORAchk/Exachk results are older than the expected date (based on configuration frequency). Incidents will be created whenever this compliance rule is violated.
Failures in Provisioning the ORAchk/Exachk Procedure Activity
Problem: Deployment procedure activities can fail due to environment issues in target system or incorrect information provided by the user.
Resolution: Depending upon the situation, correct remedial actions can be taken. Primarily these actions involve retrying the activities from failed step or recover from failed setup attempts by using stop Orachk service and start the provisioning process from beginning.
To facilitate the latter, the system allows users to stop Orachk irrespective of the state of the instance. It automatically skips the steps depending upon the failure point during provisioning activity.
Moreover, multiple stop activities can be submitted in succession. For example, if users provide a wrong password in the "stop Orachk" activity, which caused failures in third step, they can submit another activity by providing correct password.