856880 Desired_primaries for resource group %s should be 0. Current value is %d.
Description: The number of desired primaries for this resource group to be zero. In the event that a node dies or joins the cluster, the resource group might come online on some node, even if it was previously switched offline, and was intended to remain offline.
Solution: Set the Desired_primaries property for the resource group to zero.
856919 INTERNAL ERROR: process_resource: resource group <%s> is pending_methods but contains resource <%s> in STOP_FAILED state
Description: During a resource creation, deletion, or update, the rgmd has discovered a resource in STOP_FAILED state. This may indicate an internal logic error in the rgmd, since updates are not permitted on the resource group until the STOP_FAILED error condition is cleared.
Solution: Look for other syslog error messages on the same node. Save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.
857573 scvxvmlg error - rmdir(%s) failed
Description: The program responsible for maintaining the VxVM namespace was unable to access the global device namespace. If configuration changes were recently made to VxVM diskgroups or volumes, this node may be unaware of those changes. Recently created volumes may be inaccessible from this node.
Solution: Verify that the /global/.devices/node@N (N = this node's node number) is mounted globally and is accessible. If no configuration changes have been recently made to VxVM diskgroups or volumes and all volumes continue to be accessible from this node, then no further action is required. If changes have been made, the device namespace on this node can be updated to reflect those changes by executing '/usr/cluster/lib/dcs/scvxvmlg'. If the problem persists, contact your authorized Sun service provider to determine whether a workaround or patch is available.
857792 UNIX DLM initiating cluster abort.
Description: Due to an error encountered, unix dlm is intiating an abort.
Solution: This is an internal error. Save the contents of /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log and /var/cluster/ucmm/dlm*/*logs/* from all the nodes and contact your Sun service representative.
858256 Stopping %s with command %s.
Description: Sun Cluster is stopping the specified application with the specified command.
Solution: This is an informational message, no user action is needed.
859126 System property %s is empty.
Description: The system property that was named does not have a value.
Solution: Assign the property a value.
859607 Reachable nodes are %llx
Description: The cl_eventd has references to the specified nodes.
Solution: This message is informational only, and does not require user action.
861738 Error: unknown error code\n
Description: The cl_apid encountered an internal error.
Solution: Save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.
862716 sema_init: %s
Description: The rpc.pmfd server was not able to initialize a semaphore, possibly due to low memory, and the system error is shown. The server does not perform the action requested by the client, and pmfadm returns error. An error message is also output to syslog.
Solution: Investigate if the machine is running out of memory. If this is not the case, save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.
862999 Siebel server components maybe unavailable or offline. No action will be taken.
Description: Not all of the enabled Siebel server components are running.
Solution: This is an informative message. Fault Monitor will not take any action. Please manually start the Siebel component(s) that may have gone down to ensure complete service.
863007 URI (%s) must be an absolute http URI.
Description: The Universal Resource Identifier (URI) must be an absolute http URI. It must start http://
Solution: Specify an absolute http URI.
865183 Cannot open pipe to child process. pipe() failed with %m
Description: Fault monitor is not able to communicate to it's child process. Fault mointor will be restarted. If problem persists, fault monitor will be stopped.
Solution: Not available at this time.
865183 Cannot open pipe to child process. pipe() failed with %m
Description: Fault monitor is not able to communicate to it's child process. Fault mointor will be restarted. If problem persists, fault monitor will be stopped.
Solution: Not available at this time.
865292 File %s should be owned by %s.
Description: A program required the specified file to be owned by the specified user.
Solution: Use chown command to change to owner as suggested.
865635 lkcm_act: caller is not registered
Description: udlm is not currently registered with ucmm.
Solution: This is an internal error. Save the contents of /var/adm/messages, /var/cluster/ucmm/ucmm_reconf.log and /var/cluster/ucmm/dlm*/*logs/* from all the nodes and contact your Sun service representative.
866371 The listener %s is not running; retry_count <%s> exceeded. Attempting to switchover resource group.
Description: Listener is not running. Listener monitor has reached the restart limit specified in 'Retry_count' and 'Retry_interval' properties. Listener and the resource group will be moved to another node.
Solution: Check Oracle listener setup. Please make sure that Listener_name specified in the resource property is configured in listener.ora file. Check 'Host' property of listener in listener.ora file. Examine log file and syslog messages for additional information.
866624 clcomm: validate_policy: threads_low not big enough low %d pool %d
Description: The system checks the proposed flow control policy parameters at system startup and when processing a change request. The low server thread level must not be less than twice the thread increment level for resource pools whose number threads varies dynamically.
Solution: No user action required.
867059 Could not shutdown replica for device service (%s). Some file system replicas that depend on this device service may already be shutdown. Future switchovers to this device service will not succeed unless this node is rebooted.
Description: See message.
Solution: If mounts or node reboots are on at the time this message was displayed, wait for that activity to complete, and then retry the command to shutdown the device service replica. If not, then contact your authorized Sun service provider to determine whether a workaround or patch is available.
868245 Unable to process dbms log file.
Description: Error occurred when processing DBMB log file. As a result of this error, fault monitor could not scan errors from log file. This error can occur as a result of memory allocation problems.
Solution: Not available at this time.
868245 Unable to process dbms log file.
Description: Error occurred when processing DBMB log file. As a result of this error, fault monitor could not scan errors from log file. This error can occur as a result of memory allocation problems.
Solution: Not available at this time.
868467 Process %s did not die in %d seconds.
Description: HA-NFS attempted to stop the specified process id but was unable to stop the process in a timely fashion. Since HA-NFS uses the SIGKILL signal to kill processes, this indicates a serious overload or kernelproblem with the system.
Solution: HA-NFS would take appropriate action. If this error occurs in a STOP method, the node would be rebooted. Increase timeout on the appropriate method.