My Oracle Support Banner

Automated Oracle Solaris Cluster(OSC) Configuration Check Requirements and Expectations. (Doc ID 1580031.1)

Last updated on AUGUST 05, 2021

Applies to:

Solaris Cluster Geographic Edition - Version 3.0x to 4.4 [Release 3.0 to 4.4]
Solaris Cluster - Version 3.0 to 4.4 [Release 3.0 to 4.4]
Information in this document applies to any platform.


 This document introduces the automated Oracle Solaris Cluster(OSC) configuration check.  This configuration check is invoked automatically upon creating a MOS Service Request for the Solaris Cluster product, with the 'Problem Type' set to 'Automated Configuration Check for Solaris Cluster'.  

The document explains the requirements and expectations regarding the configuration check's use, explains the output that will be provided, as well as discusses the handling of a Service Request created for the automated OSC configuration check tool.


The Automated Oracle Solaris Cluster(OSC) configuration check Service Request type is an automated service that performs a series of checks against various OSC-related components, and provides a current snapshot of the OSC configuration.  Upon successful completion of this tool, output will be provided based on the Explorers you have provided at Service Request(SR) creation time.  The output is only as current as the data provided. This output is explained in the 'Details' portion of this document.  Once the output is successfully provided, the Service Request will be placed in an 'Auto-Close' queue, and will not be routed to the support team. There is nothing further that is required from you, and the SR will be closed.

This tool is meant to provide current 'snapshots' and general verifications of the OSC environment, and is not meant to replace the in-depth cluster configuration audits that Oracle Advanced Customer Support (ACS) Services performs for a fee-based service.  For in-depth verification and optimization of your cluster environment, we encourage you to reach out to Oracle ACS Services. 

Further information, please see:

The output provided will require some level of OSC understanding, but the aim of this document is to explain that output.  This is a growing tool, and we welcome feedback on how we can improve this document or the output of the configuration check.

In larger configurations, you may see the following message: 'This message has been truncated by Poirot.  Maximum message length is 31500 characters'.  This usually occurs in the DID Compare section of the output.  We are bound to this limit, and are working to determine how best to provide the entire output.  The output that is usually cut out is the Solaris OS patch and package comparisons.  If you desire this output, you may update the SR with this request for the entire 'Customer_Cluster_Report'.  The SR will then be transferred to the TSC for assistance. 



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
 Device IDs and DID Pseudo Driver

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.