Solaris Cluster 4.x SUNW.derby Resource Fails to Start and Timeout if more than One Name Server is Configured
(Doc ID 1478965.1)
Last updated on AUGUST 18, 2020
Applies to:Solaris Cluster - Version 4.0 and later
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
The Solaris Cluster SUNW.derby resource created during telemetry configuration never completely starts up, therefore the resource group will not start or appears to partially startup.
Using the following documentation as reference:
<Document 1002657.1> Solaris Cluster How to Configure Telemetry/Workload Resource Monitoring
The following messages are observed:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!