Message IDs 800000–899999

This section contains message IDs 800000–899999.

802539 No permission for owner to read %s.

Description: The owner of the file does not have read permission on it.

Solution: Set the permissions on the file so the owner can read it.

802796 UPDATE failed with error %d

Description: An UPDATE operation failed with error indicated.

Solution: Contact your Oracle support representative for further assistance.

803179 CRS is detected to be down, oracle instance %s is DOWN.

Description: The shutdown of the Oracle instance is considered a success since CRS is detected to be down.

Solution: Typically, none required, since if CRS is down, the RAC instance is down as well. However, if this is not the true scenario, contact your Sun support representative for further assistance.

804002 Function: stop_sczbt - Manual intervention needed for non-global zone %s - unable to get into state installed.

Description: The non-global zones shutdown command did not complete in time or zoneadm halt was not able to bring the non-global zone into state "installed". In order to prevent failed starts of the non-global zone on this node, manual cleanup is necessary.

Solution: Follow the Solaris System Administrator Guide for Zones to bring the non-global zone into state "installed" before trying to restart the resource on this node.

804597 Validation failed. DB_UNIQUE_NAME=%s is not correct

Description: Extension property DB_UNIQUE_NAME is not correct.

Solution: Verify that the Grid Infrastructure for Clusters installation completed successfully on all cluster nodes and that a Grid Infrastructure for Clusters database resource exists. Finally, verify that the extension property DB_UNIQUE_NAME correctly reflects the database unique name, for the database that you want to manage with this Oracle Solaris Cluster resource. If the problem persists, contact your Oracle support representative for further assistance.

805049 validate_acfsproxy - Deploying Oracle ASM 11gR2 or later

Description: Oracle 11.2.0.2.0 or later is not running.

Solution: Deploy Oracle 11.2.0.2.0 or later.

807015 Validation of URI %s failed

Description: The validation of the uri entered in the monitor_uri_list failed.

Solution: Make sure a proper uri is entered. Check the syslog and /var/adm/messages for the exact error. Fix it and set the monitor_uri_list extension property again.

807778 validate_asm_unique_instance - An Oracle ASM instance (%s) already exists on zone (%s)

Description: SCMSGS An Oracle ASM instance already exists.

Solution: Only one Oracle ASM instance can exist within the same zonelist as the resource group that is currently being used to create a new Oracle ASM instance resource. You must ensure that only one Oracle ASM instance is defined per zonelist.

808356 mountd did not respond to a NULL_RPC call. The NFS daemons will not be restarted as Failover_mode is set to LOG_ONLY.

Description: HA-NFS probe has determined that one of the daemon is dead. However, since the Failover_mode property is set to LOG_ONLY, the daemon will NOT be restarted.

Solution: This is an informational message, no action is needed.

808978 Domain %s has been deleted on this node.

Description: The domain was deleted.

Solution: None required. The domain has been deleted as it will be defined on another node. Deleting the domain on this node ensures that it can't be started on more than one cluster node at a time.

809026 sge_schedd already running; start_sge_schedd aborted.

Description: An attempt was made to start sge_schedd by bringing the sge_schedd-rs resource online, with a sge_schedd process already running.

Solution: Terminate the running sge_schedd process and retry bringing the resource online.

809554 Unable to access directory %s:%s.

Description: A HA-NFS method attempted to access the specified directory but was unable to do so. The reason for the failure is also logged.

Solution: If the directory is on a mounted filesystem, make sure the filesystem is currently mounted. If the pathname of the directory is not what you expected, check to see if the Pathprefix property of the resource group is set correctly. If this error occurs in any method other then VALIDATE, HA-NFS would attempt to recover the situation by either failing over to another node or (in case of Stop and Postnet_stop) by rebooting the node.

809742 HTTP GET response from %s:%d has no status line

Description: The response to the GET request did not start or had a malformed status line.

Solution: Check that the URI being probed is correct and functioning correctly.

813149 validate_zcboot_resource - Oracle Grid Infrastructure resource %s has ACL=%s which is incorrect, owner must equal root.

Description: The Oracle Grid Infrastructure resource sun.<resource> ACL attribute value is incorrect.

Solution: You must set the owner of the Oracle Grid Infrastructure resource, sun.<resource>, equal to root. Note that <resource> represents the Oracle Solaris Cluster SUNW.wait_zc_boot resource name. Refer to the Oracle Solaris Cluster documentation for information on how to do this.

814807 validate_zcboot_resource - Oracle Grid Infrastructure resource %s has ACTION_SCRIPT=%s which is incorrect.

Description: The Oracle Grid Infrastructure resource sun.<resource> ACTION_SCRIPT attribute value is incorrect.

Solution: You must set the ACTION_SCRIPT attribute for the Oracle Grid Infrastructure resource, sun.<resource>, equal to <basedir>/SUNWscor/dsconfig/bin/scproxy_crs_action. Note that <resource> represents the Oracle Solaris Cluster SUNW.wait_zc_boot resource name and <basedir> is typically /opt. Refer to the Oracle Solaris Cluster documentation for information on how to do this.

815148 Monitor check for sckrb5 successful.

Description: The node to be failed over to for HA-KDC is ready.

Solution: This is for informational purposes, no action is required.

816300 Validate - can't resolve local hostname

Description: ${SGE_ROOT}/utilbin/<arch>/gethostname when executed does not return a name for the local host.

Solution: Make certain the /etc/hosts and/or /etc/nsswitch.conf file(s) is/are properly configured.

816405 set_acfs_variables - This resource has not set resource_dependencies_offline_restart to any SUNW.scalable_asm_diskgroup_proxy resource

Description: The resource is missing a resource_dependencies_offline_restart entry against an Oracle ASM disk group proxy resource.

Solution: Ensure that resource_dependencies_offline_restart is set.

819721 Failed to start %s.

Description: Oracle Solaris Cluster could not start the application. It would attempt to start the service on another node if possible.

Solution: 1) Check prior syslog messages for specific problems and correct them. 2) This problem may occur when the cluster is under load and Oracle Solaris Cluster cannot start the application within the timeout period specified. Consider increasing the Start_timeout property. 3) If the resource was unable to start on any node, resource would be in the START_FAILED state. In this case, use clresourcegroup to bring the resource ONLINE on this node. 4) If the service was successfully started on another node, attempt to restart the service on this node by using clresourcegroup. 5) If the above steps do not help, disable the resource by using clresource. Check to see that the application can run outside of the Oracle Solaris Cluster framework. If it cannot, fix any problems specific to the application, until the application can run outside of the Oracle Solaris Cluster framework. Enable the resource by using clresource. If the application runs outside of the Oracle Solaris Cluster framework but not in response to starting the data service, contact your authorized Oracle service provider for assistance in diagnosing the problem.

820394 Cannot check online status. Server processes are not running.

Description: HA-Oracle could not check online status of Oracle server. Oracle server processes are not running.

Solution: Examine 'Connect_string' property of the resource. Make sure that user id and password specified in connect string are correct and permissions are granted to user for connecting to the server. Check whether Oracle server can be started manually. Examine the log files and setup.

820567 Failed to unbind domain %s on this node.

Description: The /opt/SUNWldm/bin/ldm unbind-domain command failed.

Solution: Determine why it was not possible to unbind the domain.

821354 scf_handle_decode_fmri failed: %s

Description: An API call failed.

Solution: Examine log files and syslog messages to determine the cause of the failure. Take corrective action based on any related messages. If the problem persists, report it to your Oracle support representative for further assistance.

822385 Failed to retrieve process monitor facility tag.

Description: Failed to create the tag that is used to register with the process monitor facility.

Solution: Check the syslog messages that occurred just before this message. In case of internal error, save the /var/adm/messages file and contact authorized Oracle service provider.

823331 asm_proxy_daemon - restarting to include the new Proxy_probe_interval (%s)

Description: Restarting as the Proxy_probe_interval has changed.

Solution: None required. The ASM proxy daemon will be restarted to ensure the new Proxy_probe_interval value is used.

823553 Function: validate - Zonebrand for zone %s is configured as %s on a non-sparc system. It is only supported on sparc systems.

Description: The solaris8 and solaris9 brand for zones is only supported on the sparc platform.

Solution: Review the components configuration file and make sure the variable Zonebrand defines "solaris8" or "solaris9" only on a sparc system.

824975 scf_entry_create failed: %s

Description: An API call failed.

826800 Error in processing file %s

Description: Unexpected error found while processing the specified file.

Solution: Examine other syslog messages occurring around the same time on the same node, to see if the source of the problem can be identified.

828140 Starting %s.

Description: Oracle Solaris Cluster is starting the specified application.

Solution: This is an informational message, no user action is needed.

828171 stat of file %s failed.

Description: Status of the named file could not be obtained.

Solution: Check the permissions of the file and all components in the path prefix.

829132 scha_control GIVEOVER failed. error %s

Description: Fault monitor had detected problems in RDBMS server. Attempt to switchover resource to another node failed. Error returned by API call scha_control is indicated in the message.

Solution: None.

833126 Monitor server successfully started.

Description: The Sybase Monitor server has been successfully started by Oracle Solaris Cluster HA for Sybase.

Solution: This is an information message, no user action is needed.

834749 Validate - sge_qmaster file does not exist or is not executable at %s/sge_qmaster

Description: The file sge_qmaster cannot be found, or is not executable.

Solution: Confirm the file ${SGE_ROOT}/bin/<arch>/sge_qmaster both exists at that location, and is executable.

837169 Starting listener %s.

Description: Informational message. HA-Oracle will be starting Oracle listener.

Solution: None

837211 Resource is already online.

Description: While attempting to restart the resource, error has occurred. The resource is already online.

Solution: This is an internal error. Save the /var/adm/messages file from all the nodes. Contact your authorized Oracle service provider.

837223 NFS daemon %s died. Will restart in 100 milliseconds.

Description: While attempting to start the specified NFS daemon, the daemon started up, however it exited before it could complete its network configuration.

Solution: This is an informational message. No action is needed. HA-NFS would attempt to correct the problem by restarting the daemon again. HA-NFS imposes a delay of milliseconds between restart attempts.

837568 Addition of General parent group for FMRI %s Failed %s

Description: An attempt to add a "general framework" parent group has failed.

Solution: Because the service is in a disabled state now, you must manually bring the service to the online state using the "svccfg -s fmri_instance delcust" command. Replace "fmri_instance" with the fmri instance name.

837595 Error: unknown error code

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 Oracle service provider for assistance in diagnosing and correcting the problem.

837752 Failed to retrieve the resource group handle for %s while querying for property %s: %s.

Description: Access to the object named failed. The reason for the failure is given in the message.

Solution: Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

837760 monitored processes forked failed (errno=%d)

Description: The rpc.pmfd server was not able to start (fork) the application. This problem can occur if the machine has low memory. The system error number is shown, and an error message is output to syslog.

Solution: Determine if the machine is running out of memory. If this is not the case, save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

838032 %s: Couldn't run method tag. Error in %s: %s.

Description: The rpc.fed server was not able to run the method with the tag specified. The cause of the error is specified by the exact error message.

Solution: Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

838270 HA: exception %s (major=%d) from process_to().

Description: An unexpected return value was encountered when performing an internal operation.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

838422 The directory '%s' of a file system managed by the resource '%s' of global cluster is planned to share as lofs to zone cluster '%s' on the mount point '%s'. The resource group '%s' containing the resource '%s' has node list containing native zones which is not supported.

Description: The resource has not met configuration requirements to share the directory with the zone cluster.

Solution: Modify the specified global cluster resource group node list to contain only global zones and retry the operation.

838570 Failed to unmount %s: (%d) %s.

Description: HAStoragePlus was not able to unmount the specified file system. The return code and output of the umount command is also embedded in the message.

Solution: Check the system configuration. If the problem persists, contact your authorized Oracle service provider.

838695 Unable to process client registration

Description: The cl_apid experienced an internal error (probably a memory error) that prevented it from processing a client registration request.

Solution: Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Oracle service provider for assistance in diagnosing and correcting the problem.

838960 Switch-over of RG %s failed: %s

Description: The resource group that contains the metadata server resource could not be switched over to any other node in the resource group's node list. One possible cause of this error is that all nodes in the node list are being reconfigured.

Solution: When possible, manually switch over the resource group to a node in the node list of the resource group. After switching over the resource group, manually unmount the file system.

839031 Method <%s> on resource <%s> node <%s>: Execution failed: no such method tag.

Description: An internal error has occurred in the rpc.fed daemon which prevents method execution. This is considered a method failure. Depending on which method was being invoked and the Failover_mode setting on the resource, this might cause the resource group to fail over or move to an error state, or it might cause an attempted edit of a resource group or its resources to fail.

839060 Couldn't remove file:'%s' from the deleted directory, error: (%d)

Description: The file system is unable to create temporary copies of deleted files.

Solution: Mount the affected file system as a local file system, and ensure that there is no file system entry with name "._" at the root level of that file system. Alternatively, run fsck on the device to ensure that the file system is not corrupt.

839743 Ignoring the line %d of file %s as it exceeds %d characters.

Description: The number of characters in specified file file has exceeded and hence ignoring the line.

Solution: Rectify the line if it contains tunable variable.

839881 Media error encountered, but Auto_end_bkp failed.

Description: The HA-Oracle start method identified that one or more datafiles is in need of recovery. This was caused by the file(s) being left in hot backup mode. The Auto_end_bkp extension property is enabled, but failed to recover the database.

Solution: Examine the log files for the cause of the failure to recover the database.

839936 Some ip addresses may not be plumbed.

Description: Some of the ip addresses managed by the LogicalHostname resource were not successfully brought online on this node.

Solution: Use ifconfig command to make sure that the ip addresses are indeed absent. Check for any error message before this error message for a more precise reason for this error. Use clresourcegroup to move the resource group to some other node.

840233 INTERNAL ERROR: Failed to get nodename of cluster %s : %s.

Description: Failed to get the node name.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

840542 OFF_PENDING_BOOT: bad resource state <%s> (%d) for resource <%s>

Description: The rgmd state machine has discovered a resource in an unexpected state on the local node. This should not occur and may indicate an internal logic error in the rgmd.

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 Oracle service provider.

840619 Invalid value was returned for resource group property %s for %s.

Description: The value returned for the named property was not valid.

Solution: Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

840682 validate_acfs_dg_dependency - The ACFS proxy resource (%s) requires that an ASM diskgroup proxy resource is created first

Description: The ACFS proxy resource requires an ASM diskgroup proxy resource be created first.

Solution: Ensure that a resource using type SUNW.scalable_asm_diskgroup_proxy is created before creating an ACFS proxy resource.

840696 DNS database directory %s is not readable: %s

Description: The DNS database directory is not readable. This may be due to the directory not existing or the permissions not being set properly.

Solution: Make sure the directory exists and has read permission set appropriately. Look at the prior syslog messages for any specific problems and correct them.

840725 %s: sig2str(3C) failed for signal %d

Description: The pmmd daemon was unable to get the signal name for a signal number because the sig2str(3C) function failed. The pmmd daemon will not do the requested action.

Solution: Save a copy of the /var/adm/messages files on this node, and report the problem to your authorized Oracle service provider.

841104 Could not set gid to '%d': %s

Description: The program failed to change the group ID to the specified value. The reason for the failure is also specified in the above message.

Solution: Please verify that the specified group ID is valid. For Oracle, the specified group ID is obtained from the owner of the file $ORACLE_HOME/bin/oracle.

841394 Unable to get cluster name for caller (zone %s, cluster id %d) : %s

Description: The proxy event listener daemon could not get the cluster name for a client event listener subsystem, and so could not validate the request from the client subsystem.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

841616 CMM: This node has been preempted from quorum device %s.

Description: This node's reservation key was on the specified quorum device, but is no longer present, implying that this node has been preempted by another cluster partition. If a cluster gets divided into two or more disjoint subclusters, exactly one of these must survive as the operational cluster. The surviving cluster forces the other subclusters to abort by grabbing enough votes to grant it majority quorum. This is referred to as preemption of the losing subclusters.

Solution: There might be other related messages that might indicate why quorum was lost. Determine why quorum was lost on this node, resolve the problem and reboot this node.

841858 popen failed on sharectl: %s.Will attempt to read config from %s file.

Description: popen failed while getting NFS parameters using "sharectl".

Solution: This is a warning message. An attempt will be made to read the properties directly from the file. Examine syslog messages to determine the cause of failure. Take corrective action based on any related messages. If the problem persists, report it to your Oracle support representative for further assistance.

842059 Cannot create monitor child process. fork failed with %m

Description: Fault monitor is not able to create child process. Fault monitor will be restarted. If problem persists, fault monitor will be stopped.

Solution: Examine other syslog messages occurring around the same time on the same node, to see if the source of the problem can be identified.

842084 thr_sigsetmask returned %d. Exiting.

Description: The rtreg server program has encountered a failed thr_sigsetmask(3C) system call. The error message indicates the error number for the failure.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

842313 clexecd: Sending fd on common channel returned %d. Exiting.

Description: clexecd program has encountered a failed fcntl(2) system call. The error message indicates the error number for the failure.

Solution: The node will halt or reboot itself to prevent data corruption. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

842382 fcntl: %s

Description: A server (rpc.pmfd or rpc.fed) was not able to execute the action shown, and the process associated with the tag is not started. The error message is shown.

Solution: Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

842514 Failed to obtain the status of global service %s associated with path %s: %s.

Description: The DCS was not able to obtain the status of the specified global service.

Solution: Check the cluster configuration. If the problem persists, contact your authorized Oracle service provider.

842712 clcomm: solaris xdoor door_create failed

Description: A door_create operation failed. Refer to the "door_create" man page for more information.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

842823 %s exception occured during execution of %s on node %d

Description: An exception occured while a remote command is being executed.

Solution: Check the message to determine what might be wrong. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

842993 scf_pg_create failed: %s

Description: An API call failed.

843127 Extension properties %s and %s and %s are empty.

Description: HAStoragePlus detected that no devices, file systems or zpools are to be managed.

Solution: This is an informational message, no user action is needed.

843876 Media error encountered, and Auto_end_bkp was successful.

Description: The HA-Oracle start method identified that one or more datafiles was in need of recovery. This was caused by the file(s) being left in hot backup mode. The Auto_end_bkp extension property is enabled, and successfuly recovered and opened the database.

Solution: None. This is an informational message. Oracle server is online.

843983 CMM: Node %s: attempting to join cluster.

Description: The specified node is attempting to become a member of the cluster.

Solution: This is an informational message, no user action is needed.

844812 check_for_ccrdata failed strdup for (%s)

Description: Call to strdup failed. The "strdup" man page describes possible reasons.

Solution: Install more memory, increase swap space or reduce peak memory consumption.

844900 The hostname in %s is not a network address resource in this resource group.

Description: The resource group does not contain a network address resource with the hostname contained in the indicated URI.

Solution: Check that the resource group contains a network resource with a hostname that corresponds with the hostname in the URI.

845305 DNS not already running

Description: The DNS service is not running.

Solution: No action needed.

845358 Failed to add resource group '%s' to the MDS resource group list.

Description: The zone boot handler failed to generate the list resource groups containing SUNW.qfs resources.

Solution: Investigate the zone boot log messages and try to rectify the problem. If problem persists after rebooting the zone, contact your authorized Oracle service provider with copy of /var/adm/messages files on all nodes.

845431 Aborting fault monitor child process %d. Check for the core file in the / directory. If not present, enable setid core dumps with coreadm.

Description: This message indicates that fault monitor timed out and would be aborted. If core dumps are enabled, a core file is dumped in the / directory for diagnostics. The process ID of the aborted process is listed in the message.

Solution: Determine whether the timeout of the fault monitor occurred due to some abnormal event. If the timeout occurred due to normal and expected system load, consider increasing the Probe_timeout and the Start_timeout for the resource.

845504 door_call: %s

Description: The door_call failed with the specified reason. The libsczones was unable to register with the sc_zonesd for zone state change callbacks.

Solution: Search for messages from sc_zonesd to determine the source of the error. Save a copy of the /var/adm/messages files on all nodes. If the problem persists, contact your authorized Oracle service provider for assistance in diagnosing the problem.

845866 Failover attempt failed: %s.

Description: The failover attempt of the resource is rejected or encountered an error.

Solution: For more detailed error message, check the syslog messages. Check whether the Pingpong_interval has appropriate value. If not, adjust it by using clresourcegroup. Otherwise, use clresourcegroup switch to switch the resource group to a healthy node.

846376 fatal: Got error <%d> trying to read CCR when making resource group <%s> unmanaged; aborting node

Description: Rgmd failed to read updated resource from the CCR on this node.

Solution: Save a copy of the /var/adm/messages files on all nodes, and of the rgmd core file. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

846420 CMM: Nodes %ld and %ld are disconnected from each other; node %ld will abort using %s rule.

Description: Due to a connection failure between the two specified non-local nodes, one of the nodes must be halted to avoid a "split brain" configuration. The CMM used the specified rule to decide which node to fail. Rules are: rebootee: If one node is rebooting and the other was a member of the cluster, the node that is rebooting must abort. quorum: The node with greater control of quorum device votes survives and the other node aborts. node number: The node with higher node number aborts.

Solution: The cause of the failure should be resolved and the node should be rebooted if node failure is unexpected.

846813 Switchover (%s) error (%d) converting to primary

Description: The file system specified in the message could not be hosted on the node the message came from.

Solution: Check /var/adm/messages to make sure there were no device errors. If not, contact your authorized Oracle service provider to determine whether a workaround or patch is available.

847065 Failed to start listener %s.

Description: Failed to start Oracle listener.

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.

847496 CMM: Reading reservation keys from quorum device %s failed with error %d.

Description: An error was encountered while trying to read reservation keys on the specified quorum device.

Solution: There might be other related messages on this and other nodes that are connected to this quorum device that might indicate the cause of this problem. Refer to the quorum disk repair section of the administration guide for resolving this problem.

847656 Command %s is not executable.

Description: The specified pathname, which was passed to a libdsdev routine such as scds_timerun or scds_pmf_start, does not refer to an executable file. This could be the result of 1) mis-configuring the name of a START or MONITOR_START method or other property, 2) a programming error made by the resource type developer, or 3) a problem with the specified pathname in the file system itself.

Solution: Ensure that the pathname refers to a regular, executable file.

847978 reservation fatal error(UNKNOWN) - cluster_get_quorum_status() error, returned %d

Description: The fencing subsystem was unable to obtain information about the quorum devices.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available. Copies of /var/adm/messages from all nodes should be provided for diagnosis. It may be possible to retry the failed operation, depending on the nature of the error. If the message specifies the 'node_join' transition, then this node might be unable to access shared devices. If the failure occurred during the 'release_shared_scsi2' transition, then a node that was joining the cluster might be unable to access shared devices. In either case, it might be possible to reacquire access to shared devices by executing '/usr/cluster/lib/sc/run_reserve -c node_join' on all cluster nodes. If the failure occurred during the 'make_primary' transition, then a device group has failed to start on this node. If another node was available to host the device group, then it should have been started on that node. It might be possible to switch the device group to this node by using the cldevicegroup command. If another node is not available, then the device group will not be started. You can use the cldevicegroup command to retry the attempt to start the device group. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group has failed. You can retry the desired action.

847994 Plumb failed. Tried to unplumb %s%d, unplumb failed with rc %d

Description: Topology Manager failed to plumb an adapter for private network. A possible reason for plumb to fail is that it is already plumbed. Solaris Clustering tries to unplumb the adapter and plumb it for private use but it could not unplumb the adapter.

Solution: Check if the adapter by that name exists.

848024 XDR Error while encoding arguments.

Description: An internal error has occurred in the inter-process communication between Oracle Solaris Cluster processes. Related error messages might be found near this one in the syslog output. This zone will not be able to host applications.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

848033 SharedAddress online.

Description: The status of the sharedaddress resource is online.

Solution: This is informational message. No user action required.

848057 Validation succeeded.

Description: Validation of this ScalMountPoint resource succeeded. This message is an informational message.

Solution: No user action is required.

848288 The command '%s' to find MDS of '%s' file system failed : %s.

Description: The zone boot handler failed to determine the MDS node of a file system.

Solution: Try running the command manually and see the execution status. If the command execution succeeds contact your Oracle service provider to determine whether a workaround or patch is available. In case the execution fails investigate the failure and reboot the zone after rectifying the problem.

848580 Restarting on signal %d.

Description: The cl_eventlogd daemon has recieved a SIGHUP signal, which indicates that it must reconfigure.

Solution: This message is informational only, and does not require user action.

848652 CMM aborting.

Description: The node is going down due to a decision by the cluster membership monitor.

Solution: This message is preceded by other messages indicating the specific cause of the abort, and the documentation for these preceding messages will explain what action should be taken. The node should be rebooted if node failure is unexpected.

848854 Failed to retrieve WLS extension properties.

Description: The WLS Extension properties could not be retrieved.

Solution: Check for other messages in syslog and /var/adm/messages for details of failure.

848943 clconf: No valid gdevname field for quorum device %d

Description: Found the gdevname field for the quorum device being incorrect while converting the quorum configuration information into quorum table.

Solution: Check the quorum configuration information.

848988 libsecurity: NULL RPC to program %s (%lu) failed; will retry %s

Description: A client of the specified server was not able to initiate an rpc connection, because it could not execute a test rpc call, and the program will retry to establish the connection. The message shows the specific rpc error. The program number is shown. To find out what program corresponds to this number, use the rpcinfo command. An error message is output to syslog.

Solution: Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

849138 Validate method for resource %s completed successfully.

Description: HA-KDC's validate method has successfully completed.

Solution: This is for informational purposes only, no action is required.

850108 Validation failed. PARAMETER_FILE: %s does not exist

Description: Oracle parameter file (typically init<sid>.ora) specified in property 'Parameter_file' does not exist or is not readable.

Solution: Please make sure that 'Parameter_file' property is set to the existing Oracle parameter file. Reissue command to create/update

853956 INTERNAL ERROR: WLS extension properties structure is NULL.

Description: This is an internal Error.

Solution: Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

854038 validate_acfs_in_clzc - Zone cluster %s is not configured

Description: The zone cluser is not configured.

Solution: You must configure the zone cluster first. Refer to the Oracle Solaris Cluster documentation for information on how to do this.

854894 No LogicalHostname resource in resource group.

Description: The probe method for this data service could not find a LogicalHostname resource in the same resource group as the data service.

Solution: Use scrgadm to configure the resource group to hold both the data service and the LogicalHostname.

856627 Failed to update the SERVERPOOL %s with the current server name %s, [%s]

Description: Failed to update the SERVERPOOL with the current server name.

Solution: Determine why the SERVERPOOL updated failed. If the problem persists, contact your Oracle support representative for further assistance.

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 Oracle service provider.

857088 Failed to open file %s: %s.

Description: Unable to open sharetab file.

Solution: No user action required.

857509 validate_diskgroup - Deploying Oracle ASM 11gR1 or earlier requires resource type SUNW.asm_diskgroup

Description: Oracle 11.2.0.1.0 or later requires Oracle Grid Infrastructure for Cluster and resource type SUNW.scalable_asm_diskgroup_proxy. However, Oracle 11.2.0.1.0 or later is not running.

Solution: As Oracle 11.2.0.1.0 or later is not running, you must use resource type SUNW.asm_diskgroup.

857620 Resource "%s" could not be disabled: %s, will retry.

Description: The scha_control() call to disable this ScalMountPoint resource failed, will retry disabling.

Solution: No user action is required.

859377 at or near: %s

Description: Indicates the location where (or near which) the error was detected.

Solution: Please ensure that the entry at the specified location is valid and follows the correct syntax. After the file is corrected, validate it again to verify the syntax.

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.

859614 Failed to register configuration callbacks

Description: The scprivipd daemon was unable to register for configuration callbacks.

Solution: These callbacks are used only for enabling or disabling the private IP communication for local zones. So, this feature will be unavailable. To recover, it may be necessary to reboot this node or the entire cluster. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

859686 Error: rpc.pmfd is not running.

Description: The initfed init script found that the rpc.pmfd is not running. The rpc.fed will not be started, which will prevent the rgmd from starting, and which will prevent this node from participating as a full member of the cluster.

Solution: Examine other syslog messages occurring at about the same time to determine why the rpc.pmfd is not running. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Oracle service provider for assistance in diagnosing and correcting the problem.

860514 sc_zonesd couldn't service the request.

Description: The sc_zonesd in the global zone was unable to service the request. This zone will not be able to host applications.

Solution: Verify that the system is not running on low memory. Save a copy of the /var/adm/messages file on the node. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

860640 Function: validate - Zonepath %s needs to be a directory

Description: The zone path extracted from the zones configuration is not present or not a directory.

Solution: Make sure that the filesystem for the zone path is mounted. Consider using a SUNW.HAStoragePlus resource. If already used, check if the resource dependency to it is in place.

860721 WARNING, Dependency between resource %s and the underlying MDS resource %s has not been defined.

Description: The specifed ScalMountPoint resource requires an explicit dependency on the metadata server resource that represents the mount point. Validation of the ScalMountPoint resource succeeded, but the dependency must be defined before any attempt to start the ScalMountPoint resource.

Solution: Before you attempt to start the ScalMountPoint resource, define the required dependency between the ScalMountPoint resource and the metadata server resource.

861044 Failed to retrieve the resource handle of %s: %s.

Description: An error occurred while the handle for the resource was being retrieved.

Solution: Investigate possible RGM errors or DSDL errors. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

861134 Initialization failed. Invalid command line %s %s

Description: Unable to process parameters passed to the callback method. This is an internal error.

Solution: Contact your Oracle service representative to report this problem.

861260 statvfs failed on the mount point %s : %s

Description: The file system specified on the mount point is not available.

Solution: Check the statvfs(2) man page for errors and try to resolve the problem. Otherwise contact your authorized Oracle service provider.

861642 Function: clear_zone - Killing processes with fuser -ck on the file system %s

Description: The non-global zones shutdown command did not complete in time or zoneadm halt was not able to bring the non-global zone into state "installed". A fuser -ck is submitted against each of the zones file systems. The reported processes will be send a SIGKILL.

Solution: None.

861818 in libsecurity for program %s ; unable to register service

Description: The specified daemon was not able to start because it could not initialize a door for communication with its clients. This causes the node to be rebooted or halted.

Solution: Examine other syslog messages occurring at about the same time to see if the problem can be identified. Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

862414 About to mount on %s for zone cluster '%s'.

Description: HAStoragePlus will mount the file system for zone cluster on specified path name onto a specified mount point.

Solution: This is an informational message, no user action is needed.

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.

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.

863983 Failed to save locale.

Description: Failed to save locale.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

864151 Failed to enumerate instances for IPMP group %s

Description: There was a failure while trying to determine the instances (v4, v6 or both) that the IPMP group can host.

Solution: Contact your authorized Oracle service provider.

864161 QUORUM_GENERIC: quorum_reserve error: this node's registration key was not found on the quorum device %s.

Description: When reserving the quorum device, the node's registration key was not found on the device. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.

Solution: Contact your authorized Oracle service provider to determine if a workaround or patch is available.

864516 SCSLM getprojidbyname <%s> error <%s>

Description: Should never occur.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

865130 Probe - Fatal: %s/qconf not found or not executable

Description: The binary file qconf can not be found, or is not executable.

Solution: Confirm the binary file ${SGE_ROOT}/bin/<arch>/qconf both exists in that location, and is executable.

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: Examine other syslog messages occurring around the same time on the same node, to see if the source of the problem can be identified.

865958 Domain %s has been gracefully shutdown.

Description: The domain was shutdown gracefully.

Solution: None required. The domain has shutdown gracefully.

866316 cl_orb: not booted in cluster mode.

Description: Attempted to load the cl_comm module when the node was not booted as part of a cluster.

Solution: Users should not explicitly load this module.

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.

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 Oracle service provider to determine whether a workaround or patch is available.

868064 Resource %s does not have the property DB_PORT defined

Description: The property DB_PORT is a mandatory property of the data service. Should never occur.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

868245 Unable to process dbms log file.

Description: Error occurred when processing DBMS 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: This is an internal error possibly caused by shortage of memory resources. Ensure that your system has sufficient memory and if the problem persists even when sufficient free memory is available, contact your Sun support representative for help.

868277 CMM: Erstwhile online quorum device %s (qid %d) is inaccessible now.

Description: A formerly online quorum device has become inaccessible now. This node will mark the quorum device as inaccessible. The quorum device is considered offline now.

Solution: Check whether something has gone wrong with the quorum device. The quorum device could have failed or the path to the device could have broken down. Refer to the quorum disk repair section of the administration guide for resolving this problem.

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 appropiate action. If this error occurs in a STOP method, the node would be rebooted. Increase timeout on the appropiate method.

869196 Failed to get IPMP status for group %s (request failed with %d).

Description: A query to get the state of a IPMP group failed. This may cause a method failure to occur.

Solution: Make sure the network monitoring daemon (cl_pnmd) is running. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

869406 Failed to communicate with server %s port %d: %s.

Description: The data service fault monitor probe was trying to read from or write to the service specified and failed. Oracle Solaris Cluster will attempt to correct the situation by either doing a restart or a failover of the data service. The problem may be due to an overloaded system or other problems, causing a timeout to occur before communications could be completed.

Solution: If this problem is due to an overloaded system, you may consider increasing the Probe_timeout property.

870181 Failed to retrieve the resource handle for %s while querying for property %s: %s.

Description: Access to the object named failed. The reason for the failure is given in the message.

Solution: Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

870317 INTERNAL ERROR: START method is not registered for resource <%s>

Description: A non-fatal internal error has occurred in the rgmd state machine.

Solution: Since this problem might indicate an internal logic error in the rgmd, save a copy of the /var/adm/messages files on all nodes, and the output of clresourcetype show -v, clresourcegroup show -v +, and clresourcegroup status +. Report the problem to your authorized Oracle service provider.

870414 Can't import Manifest File%s

Description: An attempt to import the SMF service has failed.

Solution: You need to manually bring the service online.

870566 clutil: Scheduling class %s not configured

Description: An attempt to change the thread scheduling class failed, because the scheduling class was not configured.

Solution: Configure the system to support the desired thread scheduling class.

870578 Waiting for all configured nodes to join the cluster ...

Description: All configured nodes are joining the cluster

Solution: Please wait for all the nodes to join the cluster. This is an informational message.

870650 %s: Cannot create closedown thread

Description: This program could not create the closedown thread.

Solution: Save the contents of /var/adm/messages from all nodes and contact your Oracle service representative for assistance in diagnosing and correcting the problem.

870753 Failed to get parent directory of %s

Description: A call to dirname() failed.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

871529 Validate - can't determine Qmaster Spool dir

Description: The qmaster spool directory could not be determined, using the 'QmasterSpoolDir' function.

Solution: Use the command 'qconf -sconf' to determine the value of '${qmaster_spool_dir}'. Update/correct the value if necessary using the command 'qconf -mconf'.

871642 Validation failed. Invalid command line %s %s

Description: Unable to process parameters passed to the call back method. This is an internal error.

Solution: Please report this problem.

872411 Setting the restarter property for FMRI %s Failed %s

Description: An attempt to change the restarter property has failed.

872503 The number of supplementary groups for user id %d exceeds the limit of %d. Only the first %d groups can be set. Please correct the file %s.

Description: There is a limit to the number of supplementary groups a single user ID can belong to, and this limit has been exceeded for the specified user ID.

Solution: Correct the /etc/group file so that the Oracle user ID's supplementary group list does not exceed the limit.

872744 fstat: %s

Description: rpc.fed is unable to open a door file descriptor with fstat.

Solution: Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

873300 fatal: unable to check for fencing completion.

Description: The RGM was unable to detect whether or not a node that left the cluster was properly fenced. This is an unrecoverable error so the RGM will abort the node.

873473 Unable to determine whether the node can safely join the cluster. Giving up after %s retries. The ucmmd daemon will not be started on this node.

Description: After retrying the operation, the RAC framework cannot determine whether the node can safely join the cluster. The node is not allowed to join the cluster now.

Solution: Wait for all reconfiguration activity to stop on existing cluster members. Then repeat the attempt to enable the node to join the cluster. If the node is still unable to join, contact your Oracle service representative for assistance in diagnosing and correcting the problem.

873991 clexecd: too big cmd size %d cmd <%s>

Description: clexecd program has encountered a problem with a client requesting a too big command.

Solution: clexecd program will exit and node will be halted or rebooted to prevent data corruption. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

874133 Issuing a failover request because the application exited.

Description: This message indicates that the fault monitor is about to make a failover request because the application exited. If the request fails, refer to the syslog messages that appear after this message.

Solution: This is an informational message.

874550 Error killing <%d>: %s

Description: An error occured while rpc.pmfd attempted to send SIGKILL to the specified process. The reason for the failure is also given.

Solution: Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

874578 zc_rgm_halt for zone %s: Could not shut down all resource groups: %s

Description: zc_rgm_halt failed to evacuate all resource groups from this zone which belongs to a zone cluster. Support for this zone cluster might not work properly.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

874879 clcomm: Path %s being deleted

Description: A communication link is being removed with another node. The interconnect might have failed or the remote node might be down.

Solution: Any interconnect failure should be resolved, and/or the failed node rebooted.

875171 clcomm: Pathend %p: %d is not a pathend state

Description: The system maintains state information about a path. The state information is invalid.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

875345 None of the shared paths in file %s are valid.

Description: All the paths specified in the dfstab.<resource_name> file are invalid.

Solution: Check that those paths are valid. This might be a result of the underlying disk failure in an unavailable file system. The monitor_check method would thus fail and the HA-NFS resource would not be brought online on this node. However, it is advisable that the file system be brought online soon.

875401 Hosting member %s of instance %s does not match with hostname %s.

Description: The node specified to the SUNW.scalable_rac_server_proxy resource as hosting the RAC instance does not match with the node configured as the hosting member for that RAC instance, with CRS.

Solution: This error occurs during resource creation. Specify the same node the particular ORACLE_SID, that is configured for it with CRS. This node value can be found by inspecting the HOSTING_MEMBERS CRS attribute for this RAC instance.

875595 CMM: Shutdown timer expired. Halting.

Description: The node could not complete its shutdown sequence within the halt timeout, and is aborting to enable another node to safely take over its services.

Solution: This is an informational message, no user action is needed.

875796 CMM: Reconfiguration callback timed out; node aborting.

Description: One or more CMM client callbacks timed out and the node will be aborted.

Solution: There may be other related messages on this node which may help diagnose the problem. Resolve the problem and reboot the node if node failure is unexpected. If unable to resolve the problem, contact your authorized Oracle service provider to determine whether a workaround or patch is available.

875939 ERROR: Failed to initialize callbacks for Global_resources_used, error code <%d>

Description: The rgmd encountered an error while trying to initialize the Global_resources_used mechanism on this node. This is not considered a fatal error, but probably means that method timeouts will not be suspended while a device service is failing over. This could cause unneeded failovers of resource groups when device groups are switched over.

Solution: Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem. This error might be cleared by rebooting the node.

876090 fatal: must be superuser to start %s

Description: The rgmd can only be started by the super-user.

Solution: This probably occured because a non-root user attempted to start rgmd manually. Normally the rgmd is started automatically when the node is booted.

876120 init_signal_handlers pthread_create: %s

Description: Internal error.

Solution: Save the syslog messages file. Contact your authorized Oracle service provider for assistance in diagnosing and correcting the problem.

876324 CCR: CCR transaction manager failed to register with the cluster HA framework.

Description: The CCR transaction manager failed to register with the cluster HA framework.

Solution: This is an unrecoverable error, and the cluster needs to be rebooted. Also contact your authorized Oracle service provider to determine whether a workaround or patch is available.

876386 Failed to stop DNS with SIGTERM; retry with SIGKILL

Description: The data service failed to stop the application by sending it a SIGTERM in the allotted time. Will retry with SIGKILL.

Solution: This problem may occur when the cluster is under load and Oracle Solaris Cluster cannot stop the application within the timeout period specified. You may consider increasing the Stop_timeout property.

876834 Could not start server

Description: HA-Oracle failed to start Oracle server. Syslog messages and log file will provide additional information on possible reasons of failure.

Solution: Check whether Oracle server can be started manually. Examine the log files and setup.

876906 %s/kadmind not started, exiting

Description: kadmind is no longer running just after Oracle Solaris Cluster tried to start it.

Solution: This problem could be caused by a number of issues. Check the krb5.conf(4), kdc.conf(4), and kadm5.acl(4) files for correctness. Ensure that the master key exists: /etc/krb5/.k5.<realm name>. Check that the binary is executable and that the /var/krb5/principal database file exists.

877653 ct_pr_event_get_exitstatus: %s

Description: The rpc.pmfd was unable to determine the exit status of a process under its control that exited. It will assume failure.

Solution: Search 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 Oracle service provider.

878089 fatal: realloc: %s (UNIX error %d)

Description: The rgmd failed to allocate memory, most likely because the system has run out of swap space. The rgmd will produce a core file and will force the node to halt or reboot to avoid the possibility of data corruption.

Solution: The problem was probably cured by rebooting. If the problem recurs, you might need to increase swap space by configuring additional swap devices. See swap(1M) for more information.

878101 Switch over the MDS for '%s' file system from '%s' node to node '%s'.

Description: This is a notification from the handler that it is trying to switch over the MDS for the specified file system.

Solution: This is an informational message; no user action is needed.

878486 %s: fsync_core_files: %s open <%s> failed, error %s

Description: The pmmd was unable to open the core file dumped by a monitored process. The pmmd will continue to monitor the process, but the pmmd has missed information of interest.

Solution: Search 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 Oracle service provider.

878692 repl_check fatal error - Device group not specified

Description: An error was encountered while checking for replicated device groups.

Solution: Replicated device groups may not have properly started on this node. If so, you may manually configure this node as the replication master and attempt to restart the device group on this node. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

879190 door_callback: invalid argument

Description: The zone state change callback from the sc_zonesd was improperly formatted. The callback will be ignored.

Solution: Save a copy of the /var/adm/messages files on all nodes. If the problem persists, contact your authorized Oracle service provider for assistance in diagnosing the problem.

879380 pmf_monitor_children: Error stopping <%s>: %s

Description: An error occured while rpc.pmfd attempted to send a KILL signal to one of the processes of the given tag. The reason for the failure is also given. rpc.pmfd attempted to kill the process because a previous error occured while creating a monitor process for the process to be monitored.

Solution: Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

880080 No MDS resource found for mount-point %s.

Description: No metadata server resource has been created to represent the specified file system.

Solution: Ensure that a metadata server resource for the file system is created. For information about how to configure the shared QFS file system with Oracle Solaris Cluster, see your Oracle Solaris Cluster documentation and your Sun QFS documentation.

880087 Failed to un-mount mountpoint %s : %s

Description: The lofs file system could not be unmounted from its mount point during a postnet-stop operation.

Solution: Manually unmount the file system.

880651 No hostnames specified.

Description: An attempt was made to create a Network resource without specifying a hostname.

Solution: At least one hostname must be specified by using the -h option to clreslogicalhostname or clressharedaddress.

880789 Failed to retrieve the resource '%s' information. Skipping this resource ...

Description: The zone boot handler failed to retrieve the specified resource information.

Solution: Investigate the zone boot log messages and rectify the problem. If problem persists after rebooting the zone, contact your authorized Oracle service provider with copy of /var/adm/messages files on all nodes.

880835 pmf_search_children: Error stopping <%s>: %s

Solution: Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

880921 %s is confirmed as mounted.

Description: HAStoragePlus certifies that the specified file system is in /etc/mnttab.

Solution: This is an informational message, no user action is needed.

881132 Error in trying to access the configured network resources : %s

Description: Failed to get the available network address resources for this resource.

Solution: This is an internal error. Save the /var/adm/messages file and contact an authorized Oracle service provider.

881737 Cluster delegated restarter unable to get state of Fmri::%s

Description: The Oracle Solaris Cluster delegated restarter was not able to get the state of the proxied SMF service.

Solution: Check the status of the Fmri using svcs -xv

881808 shared QFS file system associated with mount point %s cannot be specified with failover resources.

Description: The specified HAStoragePlus resource is a failover resource, hence shared QFS file systems cannot be specified in the FilesystemMountPoints extension property.

Solution: Correct either the resource group type or remove the shared QFS file system from the FilesystemMountPoints extension property.

881846 run_srvctl - Oracle srvctl command %s failed

Description: The Oracle srvctl command failed.

Solution: Investigate the error.

882451 Shared address resource %s is DISABLED. Its strong/restart dependents will be brought OFFLINE

Description: The resource being disabled is a SHARED ADDRESS resource. The strong and the restart dependents of this resource will be brought offline. The dependents will automatically be brought ONLINE once this resource is re-enabled.

Solution: None. This is just an informational message.

882651 INTERNAL ERROR: PENDING_OFF_STOP_FAILED or ERROR_STOP_FAILED in sort_candidate_nodes

Description: An internal error has occurred in the rgmd. This may prevent the rgmd from bringing affected resource groups online.

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 Oracle service provider.

882793 Function: validate - Zonebrand for zone %s is configured as %s on a non-i386 system. It is only supported on i386 systems.

Description: The lx brand for zones is only supported on the i386 platform.

Solution: Review the components configuration file and make sure the variable Zonebrand defines "lx" only on a i386 system.

883414 Error: unable to bring Resource Group <%s> ONLINE, because the Resource Groups <%s> for which it has a strong negative affinity are online.

Description: The rgmd is enforcing the strong negative affinities of the resource groups. This behavior is normal and expected.

Solution: No action required. If desired, use clresourcegroup to change the resource group affinities.

883453 exception %s raised while attempting to get the status of cluster shutdown flag in CMM.

Description: An exception occurred when retrieving the status of the cluster shutdown flag in CMM.

Solution: Contact your authorized Oracle service provider to determine if a workaround or patch is available.

883465 Successfully delivered event %lld to remote node %d.

Description: The cl_eventd was able to deliver the specified event to the specified node.

Solution: This message is informational only, and does not require user action.

883690 Failed to start Monitor server.

Description: Oracle Solaris Cluster HA for Sybase failed to start the monitor server. Other syslog messages and the log file will provide additional information on possible reasons for the failure.

Solution: Please whether the server can be started manually. Examine the HA-Sybase log files, monitor server log files and setup.

884114 clcomm: Adapter %s constructed

Description: A network adapter has been initialized.

Solution: No action required.

884156 reservation warning(%s) - MHIOCGRP_RESERVE error(%d) will retry in %d seconds

Description: The device fencing program has encountered errors while trying to access a device. The failed operation will be retried

Solution: This is an informational message, no user action is needed.

884482 clconf: Quorum device ID %ld is invalid. The largest supported ID is %ld

Description: Found the quorum device ID being invalid while converting the quorum configuration information into quorum table.

Solution: Check the quorum configuration information.

884495 Could not get service parameters for device service %s, error = %d

Description: No service by this name was found when executing scdidadm -C. This service might have been removed by another instance of this command that was issed from another node.

Solution: No user action required.

884821 Unparsable registration

Description: A CRNP client submitted a registration message that could not be parsed.

Solution: No action required. This message represents a CRNP client error.

885546 Function: check_sczbt - Zone scheduler for %s not running

Description: The zsched prcess of the referenced zone is not running. The zone is not operable.

Solution: None. The resource will be restarted or the resource group will be failed over.

885590 Domain %s has been forcefully terminated.

Description: The domain was immediately terminated.

Solution: None required. The domain had previously failed to shutdown gracefully but has now been immediately terminated.

885688 Mounting the file systems is completed successfully.

Description: Self explanatory.

Solution: This is an informational message, no user action is needed.

885719 Telemetry data service monitor successfully stopped (resource: %s)

Description: The monitor program of the telemetry data service stopped successfully.

Solution: This message is informational; no user action needed.

885997 ucmmd got invalid upgrade callback from version manager: new version %d.%d is not the expected new version %d.%d from callback step 1.

Description: Version manager delivered upgrade callback to ucmmd about a new version that is not the expected new version after callback step 1 for ucmmd.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

886033 fatal: unable to determine if resource type %s exists.

Description: The rgmd failed to detect the existence of the specified resource type, so was unable to complete the administrative request. The node will be aborted.

Solution: Examine other syslog messages occurring at about the same time to see if the problem can be identified which is preventing the CCR access. Save a copy of the /var/adm/messages files on all nodes and contact your authorized Oracle service provider for assistance in diagnosing and correcting the problem.

886247 Function: check_sczbt - Zones %s ip address %s is not running

Description: The referenced zones ip address is unplumbed.

Solution: None. The resource will be restarted or the resource group will be failed over.

886919 CMM: Callback interface versions do not match.

Description: Interface version of an instance of userland CMM does not match the kernel version.

Solution: Ensure that complete software disribution for a given release has been installed using recommended install procedures. Retry installing same packages if previous install had been aborted. If the problem persists, contact your authorized Oracle service provider to determine whether a workaround or patch is available.

887138 Extension property <Child_mon_level> has a value of <%d>

Description: Resource property Child_mon_level is set to the given value.

Solution: This is an informational message, no user action is needed.

887282 Mode for file %s needs to be %03o

Description: The file needs to have the indicated mode.

Solution: Set the mode of the file correctly.

887656 Process: tag="%s", cmd="%s", Failed to stay up.

Description: The tag shown, being run by the rpc.pmfd server, has exited. Either the user has decided to stop monitoring this process, or the process exceeded the number of retries. An error message is output to syslog.

Solution: This message is informational; no user action is needed.

887666 clcomm: sxdoor: op %d fcntl failed: %s

Description: A user level process is unmarshalling a door descriptor and creating a new door. The specified operation on the fcntl operation fails. The "fcntl" man page describes possible error codes.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

887669 clcomm: coalesce_region request(%d) > MTUsize(%d)

Description: While supporting an invocation, the system wanted to create one buffer that could hold the data from two buffers. The system cannot create a big enough buffer. After generating another system error message, the system will panic. This message only appears on debug systems.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

888259 clcomm: Path %s being deleted and cleaned

Description: A communication link is being removed with another node. The interconnect might have failed or the remote node might be down.

Solution: Any interconnect failure should be resolved, and/or the failed node rebooted.

888476 SCSLM <%s> pool_destroy error <%s>

Description: Should never occur.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

888499 scal_dg_monitor_start.c: Failed to start fault monitor.

Description: An error prevented a resource's fault monitor from starting.

Solution: Contact your authorized Oracle service provider for assistance in diagnosing the problem.

889303 Failed to read from kstat:%s

Description: See 176151

Solution: See 176151

889414 Unexpected early exit while performing: '%s' result %d revents %x

Description: clexecd program got an error while executing the program indicated in the error message.

Solution: Please check the error message. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

889899 scha_control RESTART failed. error %s

Description: Fault monitor had detected problems in RDBMS server. Attempt to restart RDBMS server on the same node failed. Error returned by API call scha_control is indicated in the message.

Solution: None.

890413 %s: state transition from %s to %s.

Description: A state transition has happened for the IPMP group. Transition to DOWN happens when all adapters in an IPMP group are determined to be faulty.

Solution: If an IPMP group transitions to DOWN state, check for error messages about adapters being faulty and take suggested user actions accordingly. No user user action is needed for other state transitions.

890927 HA: repl_mgr_impl: thr_create failed

Description: The system could not create the needed thread, because there is inadequate memory.

Solution: There are two possible solutions. Install more memory. Alternatively, reduce memory usage.

891063 Received non-interrupt heartbeat on %s.

Description: On Oracle Solaris 11, network packets can be delivered either in interrupt context or in regular system priority depending on mac polling. It is therefore expected that some heartbeats may be delivered in system priority, while still getting protection against interrupt overloading and packet storm on the public network interfaces due to mac polling. The message is safe to ignore.

Solution: No need to do anything.

891131 The "%s" command returned error %s, unable to start the VUCMMD under the PMMD.

Description: The command used to launch the VUCMMD has failed.

Solution: Review logs and messages in /var/adm/messages and /var/cluster/vucmm/vucmm_reconf.log. Refer to the Oracle Solaris Cluster documentation. If the problem persists, contact your Oracle service representative.

891362 scha_resource_open error (%d)

Description: Error occurred in API call scha_resource_open.

Solution: Check syslog messages for errors logged from other system modules. Stop and start fault monitor. If error persists then disable fault monitor and report the problem.

891424 Starting %s with command %s.

Description: Oracle Solaris Cluster is starting the specified application with the specified command.

Solution: This is an informational message, no user action is needed.

891462 in libsecurity caller is %d, not the desired uid %d

Description: A server (rpc.pmfd, rpc.fed or rgmd) refused an rpc connection from a client because it has the wrong uid. The actual and desired uids are shown. An error message is output to syslog.

Solution: Save the /var/adm/messages file. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

891542 Diskgroup (%s) is in degraded state

Description: The disk group is degraded. Although the disk group is usable it requires maintenance.

Solution: To prevent further degradation, perform the required maintenance on the disk group as soon as possible.

891745 Unable to register for upgrade callbacks with version manager: %s

Description: An exception was raised when PNM proxy tried to register for upgrade callbacks with the Version Manager.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

891915 stop_dgproxy - PMF managed asmdg proxy daemon failed to stop (%s)

Description: Failed to stop the PMF managed Oracle ASM DG proxy resource.

Solution: Check the syslog for further messages. The Solaris Cluster resource will now enter a stop_failed state. You must determine why the Oracle ASM DG proxy resource failed to stop. Once resolved you can reenable the Solaris Cluster resource again.

892076 Waiting for the PNM in zone %s to stop

Description: The PNM service is being stopped.

Solution: Please wait. No action is required. This is an informational message.

892197 Sending to node %d.

Description: The cl_eventd is forwarding an event to the specified node.

Solution: This message is informational only, and does not require user action.

892269 Failed to configure sci%d adapter

Description: The Oracle Solaris Cluster Topology Manager (TM) has failed to add or remove a path using the SCI adapter.

Solution: Make sure that the SCI adapter is installed correctly on the system. Also ensure that the cables have been setup correctly. If required contact your authorized Oracle service provider for assistance.

892307 mdcomm SMF service is not online and multi-owner sets are present

Description: The mdcomm SMF service is disabled on this node even though multi-owner disksets are present. Hence the SUNW.rac_framework or SUNW.vucmm_framework resource will not be started.

Solution: Ensure the mdcomm service is enabled and restart the resource. If the problem persists, contact your authorized Oracle service provider to determine whether a workaround or patch is available.

892316 Error: The RAC Framework resource does not exist.

Description: The RAC framework resource does not exist. The Oracle CRS framework resource depends on the RAC framework resource.

Solution: Ensure that the RAC framework resource has been created and repeat the attempt to create the CRS framework resource.

892362 The special device %s of the file system mount point %s in the vfstab of zone cluster %s is not configured for the zone cluster.

Description: The specified device is not authorized for use in the specified zone cluster, because it is not configured for the zone cluster.

Solution: Retry the operation after the specified device is configured for the zone cluster. If the problem persists, contact your authorized Oracle service provider with the /var/adm/messages from the cluster nodes.

893086 Failed to check whether the weights are set with error: %s

Description: The query for checking, whether the weights are set or not, has failed.

Solution: Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

893268 RAC framework did not start on this node. The ucmmd daemon is not running.

Description: RAC framework is not running on this node. Oracle parallel server/ Real Application Clusters database instances will not be able to start on this node. One possible cause is that installation of Oracle Solaris Cluster support for Oracle Parallel Server/Real Application clusters is incorrect. When RAC framework fails during previous reconfiguration, the ucmmd daemon and RAC framework is not started on the node to allow investigation of the problem.

Solution: Review logs and messages in /var/adm/messages and /var/cluster/ucmm/ucmm_reconf.log. Refer to the documentation of Oracle Solaris Cluster support for Oracle Parallel Server/ Real Application Clusters. If problem persists, contact your Oracle service representative.

893639 Invalid zone state: %s

Description: The sc_zonesd received an invalid zone state notification from Solaris.

Solution: This message can be ignored and the user need not take any action

893702 Unable to get door credentials : %s

Description: door_ucred(3DOOR) failed for the specified reason. The proxy event listener daemon could not validate a request from a client event listener subsystem.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

893971 in libsecurity, authorization failed

Description: A cluster daemon refused a door connection from a client because of improper credentials. This might happen if a caller program is required to run as superuser or as a specific user ID, and fails to do so.

Solution: Examine other syslog messages occurring at about the same time to see if the problem can be identified. Check that the clustering software is properly installed, and that no unauthorized user processes are running on the cluster. If these checks cannot explain the error, contact your authorized Oracle service provider to determine whether a workaround or patch is available.

894418 reservation warning(%s) - Found invalid key, preempting

Description: The device fencing program has discovered an invalid scsi-3 key on the specified device and is removing it.

Solution: This is an informational message, no user action is needed.

894711 Could not resolve '%s' in the name server. Exiting.

Description: clexecd program was unable to start due to an error in registering itself with the low-level clustering software.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

894831 Error reading caapi_reg CCR table

Description: The cl_apid was unable to read the specified CCR table. This error will prevent the cl_apid from starting.

894921 UNRECOVERABLE ERROR: Oracle Solaris Cluster boot: /usr/cluster/lib/sc/failfastd not found

Description: Internal error.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

895159 clcomm: solaris xdoor dup failed: %s

Description: A dup operation failed. The "dup" man page describes possible error codes.

Solution: Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

895266 DID reconfiguration discovered an invalid disk path. You must remove this path before you can add a new path. Run 'scdidadm -C' then rerun 'scdidadm -r'.

Description: Invalid disk path found during DID reconfiguration.

Solution: Remove the invalid disk path and run 'scdidadm -C' and rerun 'scdidadm -r'.

895493 metaset command failed with error %d.

Description: An error occurred when the command 'metaset' was run.

Solution: Contact your authorized Oracle service provider for assistance in diagnosing the problem.

896252 clcomm: failed to create thread for autom_thread

Description: The system could not create the needed thread, because there is inadequate memory.

Solution: There are two possible solutions. Install more memory. Alternatively, reduce memory usage. Since this happens during system startup, application memory usage is normally not a factor.

896275 CCR: Ignoring override field for table %s on joining node %s.

Description: The override flag for a table indicates that the CCR should use this copy as the final version when the cluster is coming up. If the cluster already has a valid copy while the indicated node is joining the cluster, then the override flag on the joining node is ignored.

Solution: This is an informational message, no user action is needed.

896441 Unknown scalable service method code: %d.

Description: The method code given is not a method code that was expected.

Solution: Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

896532 Invalid variable name in Environment_file. Ignoring %s

Description: HA-Sybase reads the Environment_file and exports the variables declared in the Environment file. Syntax for declaring the variables is : VARIABLE=VALUE Lines starting with " with "export" are ignored. VARIABLE is expected to be a valid Korn shell variable that starts with alphabet or "_" and contains alphanumerics and "_".

Solution: Please check the syntax and correct the Environment_file

896853 Membership: Unable to create automaton callback thread for membership subsystem.

Description: A thread that is part of the membership subsystem could not be created. This might be due to lack of memory. Membership subsystem will not work properly.

Solution: Lack of memory might lead to other problems on the node. You must free up memory on the node.

897830 This node is not in the replica node list of global service %s associated with path %s. Although AffinityOn is set to TRUE, device switchovers cannot be performed to this node.

Description: Self explanatory.

Solution: Remove the specified node from the resource group.

898001 launch_fed_prog: getlocalhostname() failed for program <%s>

Description: The ucmmd was unable to obtain the name of the local host. Launching of a method failed.

898028 Service failed and the fault monitor is not running on this node. Not restarting service because failover_enabled is set to false.

Description: The probe has quit previously because failover_enabled is set to false. The action script for the process is trying to contact the probe, and is unable to do so. Therefore, the action script is not restarting the application.

Solution: This is an informational message, no user action is needed.

898227 Creation of the SUNW.rac_svm resource is not allowed if a SUNW.vucmm_svm resource is running.

Description: The creation of the SUNW.rac_svm resource is not permitted when a SUNW.vucmm_svm resource is currently running.

Solution: Refer to the documentation of Oracle Solaris Cluster for information about using the SUNW.vucmm_svm resource type.

898507 reservation notice(%s) - MHIOCGRP_REGISTER success during retry attempt: %d

Description: Informational message from reserve on ioctl success during retry.

Solution: No user action required.

898512 Validation failed. The Oracle Clusterware start dependencies for database %s were unable to be identified.

Description: The Oracle Clusterware start dependencies for the database were unable to be identified.

Solution: Check that the oratab entry for the database exists and is correct. If the problem persists, contact your Oracle support representative for further assistance.

898738 Aborting node because pm_tick delay of %lld ms exceeds %lld ms

Description: The system is unable to send heartbeats for a long time. (This is half of the minimum of timeout values of all the paths. If the timeout values for all the paths is 10 secs then this value is 5 secs.) There is probably heavy interrupt activity causing the clock thread to get delayed, which in turn causes irregular heartbeats. The node is aborted because it is considered to be in 'sick' condition and it is better to abort this node instead of causing other nodes (or the cluster) to go down.

Solution: Check to see what is causing high interrupt activity and configure the system accordingly.

898802 ping_interval out of bound. The interval must be between %d and %d seconds: using the default value

Description: scdpmd config file (/etc/cluster/scdpm/scdpmd.conf) has a bad ping_interval value. The default ping_interval value is used.

Solution: Fix the value of ping_interval in the config file.

898960 Failed to generate callback for path down event

Description: Cluster cannot generate a callback for the RDS module. Operation of RDS sockets might be affected.

Solution: If Reliable Datagram Sockets (RDS) is used by applications running on this cluster, contact your Oracle service representative to determine if a workaround or patch is available.

899278 Retry_count exceeded in Retry_interval

Description: Fault monitor has detected problems in RDBMS server. Number of restarts through fault monitor exceed the count specified in 'Retry_count' parameter in 'Retry_interval'. Database server is unable to survive on this node. Switching over the resourge group to other node.

Solution: Please check the RDBMS setup and server configuration.

899305 clexecd: Daemon exiting because child died.

Description: Child process in the clexecd program is dead.

Solution: If this message is seen when the node is shutting down, ignore the message. If thats not the case, the node will halt or reboot itself to prevent data corruption. Contact your authorized Oracle service provider to determine whether a workaround or patch is available.

899648 Failed to process the resource information.

Description: An Oracle Solaris Cluster data service is unable to retrieve the resource property information. Low memory or API call failure might be the reasons.

Solution: In case of low memory, the problem will probably cured by rebooting. If the problem recurs, you might need to increase swap space by configuring additional swap devices. Otherwise, if it is API call failure, check the syslog messages from other components.

899877 time in throttle wait: %s

Description: The time(2) function failed with the specified error. The program will exit and the node might halt or reboot.

Solution: Search 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 Oracle service provider.

Skip Navigation Links
Exit Print View
	Oracle Solaris Cluster Error Messages Guide Oracle Solaris Cluster 4.0