My Oracle Support Banner

Solaris Cluster 3.x Generic Data Service, GDS Method Failed, Restarted or Timed Out Troubleshooting Resolution Path (Doc ID 1021039.1)

Last updated on OCTOBER 10, 2022

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)


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:

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.

Please note that not all applications are properly suited for cluster control, even when written by Oracle. Sendmail is one such application. Refer to Solaris Cluster Why Some Applications or Services Do Not Or Cannot Have Oracle Solaris Cluster Agents? (Doc ID 1538827.1)


Troubleshooting Steps

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
Troubleshooting Steps
 1. Verify that you are running Solaris Cluster.
 2. First confirm that the error or problem is related to a Generic Data Service resource type.
 3. Confirm that your application can run outside of cluster control.
 a) Make sure that the GDS resource you are troubleshooting is not online on any cluster nodes:
 b) Configure all components needed for your application to start 
 c) Run the script or command
 d) Example
 4. Verify resource dependencies and affinities.
 5. Verify if  the error is a method  timeout.
 6. Verify GDS Validation method failure
 7. Verify GDS resource in STOP_FAILED state
 8. Verify GDS resource was restarted
 9. Verify GDS resource fails because of connection timeout
 10. Appendix
 a) Enable debugging for GDS.
 b) More GDS Documentation.
 11. What to do if you are still  having the problem. 

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