Solaris Cluster 3.x Generic Data Service, GDS Method Failed, Restarted or Timed Out Troubleshooting Resolution Path
(Doc ID 1021039.1)
Last updated on AUGUST 11, 2020
Applies to:
Solaris Cluster Geographic Edition - Version 3.0x to 3.3 U2 [Release 3.0 to 3.3] Solaris Cluster - Version 3.0 to 3.3 U2 [Release 3.0 to 3.3] Oracle Solaris on SPARC (32-bit) Oracle Solaris on SPARC (64-bit) Oracle Solaris on x86 (32-bit) Oracle Solaris on x86-64 (64-bit)
Purpose
This document helps determine the issue of a Generic Data Service method failed, restarted or timed out. Non exhaustive list of Solaris Cluster Data Service based on GDS:
Apache Tomcat
Domain Name Service
PostgreSQL
iPlanet Mail Server
MySQL
Oracle Application Server
Oracle EBusiness Suite
Samba
SAP DB
SWIFT Alliance Gateway
IBM WebSphere Message Queue Server
This document is provided as an aid to help you identify why a GDS resource failed. It is not meant to troubleshoot 3rd party applications which has been placed under the control of a GDS resource.
Oracle Global Support Services (GSS) is not responsible for 3rd party applications which fail to start, stay running, or suffer probe failures as a result of 3rd party application software defects, mis-configurations, failed upgrades, etc... Customers should engage the application vendor for such support.
