Sun Cluster Error Messages Guide for Solaris OS

Message IDs 200000–299999

201348 Resource <%s> must be in the same resource group as <%s>.

Description:

There is atleast one HAStoragePlus resource, on which this resource depends, that is not in this resource's RG.

Solution:

Move the resources identified by the message into the same RG and retry the operation that caused this error.

201876 dl_info ack bad len %d

Description:

Sanity check. The message length in the acknowledgment to the info request is different from what was expected. We are trying to open a fast path to the private transport adapters.

Solution:

Reboot of the node might fix the problem.

201878 clconf: Key length is more than max supported length in clconf_file_io

Description:

In reading configuration data through CCR FILE interface, found the data length is more than max supported length.

Solution:

Check the CCR configuraton information.

202528 No permission for group to read %s.

Description:

The group of the file does not have read permission on it.

Solution:

Set the permissions on the file so the group can read it.

203202 Peer node %d attempted to contact us with an invalid version message, source IP %s. Peer node may be running pre 3.1 Sun Cluster software.

Description:

Sun Cluster software at the local node received an initial handshake message from the remote node that is not running a compatible version of the Sun Cluster software.

Solution:

Make sure all nodes in the cluster are running compatible versions of Sun Cluster software.

203680 fatal: Unable to bind to nameserver

Description:

The low-level cluster machinery has encountered a fatal error. The rgmd will produce a core file and will cause the node to halt or reboot to avoid the possibility of data corruption.

Solution:

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

203739 Resource %s uses network resource %s in resource group %s, but the property %s for resource group %s does not include resource group %s. This dependency must be set.

Description:

For all network resources used by a scalable resource, a dependency on the resource group containing the network resource should be created for the resource group of the scalable resource.

Solution:

Use the scrgadm(1M) command to update the RG_dependencies property of the scalable resource's resource group to include the resource groups of all network resources that the scalable resource uses.

204163 clcomm: error in copyin for state_balancer

Description:

The system failed a copy operation supporting statistics reporting.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

204342 Apache service with startup script <%s> does not configure %s.

Description:

The specified Apache startup script does not configure the specified variable.

Solution:

Edit the startup script and set the specified variable to the correct value.

204584 clexecd: Going down on signal %d.

Description:

clexecd program got a signal indicated in the error message.

Solution:

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

205259 Error reading properties; exiting.

Description:

The cl_apid was unable to read the SUNW.Event resource properties that it needs to run.

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.

205445 check_and_start(): Out of memory

Description:

System runs out of memory in function check_and_start()

Solution:

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

205754 All specified device services validated successfully.

Description:

All device services specified directly or indirectly via the GlobalDevicePath and FilesystemMountPoint extension properties respectively are found to be correct. Other Sun Cluster components like DCS, DSDL, RGM are found to be in order. Specified file system mount point entries are found to be correct.

Solution:

None.

205822 clcomm:Cannot vfork() after ORB server initialization.

Description:

A user level process attempted to vfork after ORB server initialization. This is not allowed.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

205873 Permissions incorrect for %s. s bit not set.

Description:

Permissions of $ORACLE_HOME/bin/oracle are expected to be '-rwsr-s--x' (set-group-ID and set-user-ID set). These permissions are set at the time or Oracle installation. FAult monitor will not function correctly without these permissions.

Solution:

Check file permissions. Check Oracle installaion. Relink Oracle, if necessary.

205873 Permissions incorrect for %s. s bit not set.

Description:

Solution:

Check file permissions. Check Oracle installaion. Relink Oracle, if necessary.

206501 CMM: Monitoring re-enabled.

Description:

Transport path monitoring has been enabled back in the cluster, after being disabled.

Solution:

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

206947 ON_PENDING_MON_DISABLED: 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 Sun service provider.

207481 getlocalhostname() failed for resource <%s>, resource group <%s>, method <%s>

Description:

The rgmd was unable to obtain the name of the local host, causing a method invocation to fail. Depending on which method is 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.

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

207615 Property Confdir_list is not set.

Description:

The Confdir_list property is not set. The resource creation is not possible without this property.

Solution:

Set the Confdir_list extension property to the complete path to the WLS home directory. Refer to the COnfiguration guide for more details.

207873 Validate - User ID root is not a member of group mqbrkrs

Description:

The WebSphere Broker resource requires that root mqbrkrs is a member of group mqbrkrs.

Solution:

Ensure that root is a member of group mqbrkrs.

208216 ERROR: resource group <%s> has RG_dependency on non-existent resource group <%s>

Description:

A non-existent resource group is listed in the RG_dependencies of the indicated resource group. 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 Sun service provider.

208441 Stopping %s with command %s failed.

Description:

An attempt to stop the application by the command that is listed failed. Informational message.

Solution:

Other syslog messages that occur shortly before this message might indicate the reason for the failure. Check the application installation and make sure the command listed in the message can be executed successfully outside Sun Cluster. A more severe command will be used to stop the application after this. No user action is needed.

208596 clcomm: Path %s being initiated

Description:

A communication link is being established with another node.

Solution:

No action required.

208701 %s error status ignored in step %s

Description:

Ignoring the error status from step execution since this does not affect outcome of the step.

Solution:

None.

209090 scha_control RESOURCE_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.

209274 path_check_start(): Out of memory

Description:

Run out of memory in function path_check_start().

Solution:

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

209314 No permission for group to write %s.

Description:

The group of the file does not have write permission on it.

Solution:

Set the permissions on the file so the group can write it.

210725 Warning: While trying to lookup host %s, the length of the returned address (%d) was longer than expected (%d). The address will be truncated.

Description:

The value of the resolved address for the named host was longer than expected.

Solution:

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

210975 Stop monitoring saposcol under PMF times out.

Description:

Stopping monitoring the SAP OS collector process under the control of Process Monitor facility times out. This might happen under heavy system load.

Solution:

You might consider increase the monitor stop time out value.

211018 Failed to remove events from client

Description:

The cl_apid experienced an internal error that prevented proper updates to a CRNP client.

Solution:

211198 Completed successfully.

Description:

Data service method completed successfully.

Solution:

No action required.

211869 validate: Basepath is not set but it is required

Description:

The parameter Basepath is not set in the parameter file

Solution:

Set the variable Basepath in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.

211873 pmf_search_children: pmf_remove_triggers: %s

Description:

The rpc.pmfd server was not able to monitor a process, and the system error is shown. An error message is output to syslog.

Solution:

Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

212337 (%s) scan of seqnum failed on "%s", ret = %d

Description:

Could not get the sequence number from the udlm message received.

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.

212697 CMM: Open failed with error '(%s)' and errno = %d for quorum device %ld with gdevname '%s'.

Description:

The open operation on the specified quorum device failed, and this node will ignore the quorum device.

Solution:

The quorum device has failed or the path to this device may be broken. Refer to the quorum disk repair section of the administration guide for resolving this problem.

213112 latch_intention(): IDL exception when communicating to node %d

Description:

An inter-node communication failed, probably because a node died.

Solution:

No action is required; the rgmd should recover automatically.

213546 Unable to contact fault monitor. 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.

213583 Failed to stop Backup server.

Description:

Sun Cluster HA for Sybase failed to stop backup server using KILL signal.

Solution:

Please examine whether any Sybase server processes are running on the server. Please manually shutdown the server.

213599 Failed to stop backup server.

Description:

Sun Cluster HA for Sybase failed to stop backup server using KILL signal.

Solution:

Please examine whether any Sybase server processes are running on the server. Please manually shutdown the server.

213973 Resource depends on a SUNW.HAStoragePlus type resource that is not online anywhere.

Description:

The resource depends on a SUNW.HAStoragePlus resource that is not online on any cluster node.

Solution:

Bring all SUNW.HAStoragePlus resources, that this HA-NFS resource depends on, online before performing the operation that caused this error.

213991 No Network resource in resource group.

Description:

This message indicates that there is no network resource configured for a "network-aware" service. A network aware service can not function without a network address.

Solution:

Configure a network resource and retry the command.

215525 Failed to stop orbixd.

Description:

The orbix daemon could not be stopped by the stop method.Thiscould be an internal error also.

Solution:

Kill orbixd manually and also clear all the BV processes running onthe node where the resource failed.If all the resources on thenode ,where the stop failed,are turned off delete the/var/run/cluster/bv/bv_orbixd_lock_file file .

215538 Not all hostnames brought online.

Description:

Failed to bring all the hostnames online. Only some of the ip addresses are online.

Solution:

Use ifconfig command to make sure that the ip addresses are available. Check for any error message before this error message for a more precise reason for this error. Use scswitch command to move the resource group to a different node. If problem persists, reboot.

216087 rebalance: resource group <%s> is being switched updated or failed back, cannot assign new primaries

Description:

The indicated resource group has lost a master due to a node death. However, the RGM is unable to switch the resource group to a new master because the resource group is currently in the process of being modified by an operator action, or is currently in the process of "failing back" onto a node that recently joined the cluster.

Solution:

Use scstat(1M) -g to determine the current mastery of the resource group. If necessary, use scswitch(1M) -z to switch the resource group online on desired nodes.

216244 CCR: Table %s has invalid checksum field. Reported: %s, actual: %s.

Description:

The indicated table has an invalid checksum that does not match the table contents. This causes the consistency check on the indicated table to fail.

Solution:

Boot the offending node in -x mode to restore the indicated table from backup or other nodes in the cluster. The CCR tables are located at /etc/cluster/ccr/.

216379 Stopping fault monitor using pmfadm tag %s

Description:

Informational message. Fault monitor will be stopped using Process Monitoring Facility (PMF), with the tag indicated in message.

Solution:

None

216774 WARNING: update_state:udlm_send_reply failed

Description:

A warning for udlm state update and results in udlm 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.

217093 Call failed: %s

Description:

A client was not able to make an rpc connection to a server (rpc.pmfd, rpc.fed or rgmd) to execute the action shown. The rpc error message is shown. An error message is output to syslog.

Solution:

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

218227 Error accessing policy string

Description:

This message appears when the customer is initializing or changing a scalable services load balancer, by starting or updating a service. The Load_Balancing_String is missing.

Solution:

Add a Load_Balancing_String parameter when creating the resource group.

218575 low memory: unable to capture output

Description:

The rpc.fed server was not able to allocate memory necessary to capture the output from methods it runs.

Solution:

Investigate if the host is running out of memory. If not save the /var/adm/messages file. whether a workaround or patch is available.

218780 Stopping the monitor server.

Description:

The Monitor server is about to be brought down by Sun ClusterHA for Sybase.

Solution:

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

219058 Failed to stop the backup server using %s.

Description:

Sun Cluster HA for Sybase failed to stop the backup server using the file specified in the STOP_FILE property. Other syslog messages and the log file will provide additional information on possible reasons for the failure.

Solution:

Please check the permissions of file specified in the STOP_FILE extension property. File should be executable by the Sybase owner and root user.

219205 libsecurity: create of rpc handle to program %s (%lu) failed, will keep trying

Description:

A client of the specified server was not able to initiate an rpc connection. The maximum time allowed for connecting (1 hr) has not been reached yet, and the pmfadm or scha command will retry to connect. An accompanying error message shows the rpc error data. 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 Sun service provider to determine whether a workaround or patch is available.

219930 Cannot determine if the server is secure: assuming secure.

Description:

While attempting to determine if the Netscape server is running under secure or non-secure mode an error occurred. This error results in the Data Service assuming a secure Netscape server, and will probe the server as such.

Solution:

This message is issued after an internal error has occurred. Refer to syslog for that message.

220753 %s: Arg error, invalid tag <%s> restarting service.

Description:

The PMF tag supplied as argument to the PMF action script is not a tag generated by the DSDL; the PMF action script has restarted the application.

Solution:

This is an internal error. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

220824 stop SAA failed rc<>

Description:

Failed to stop SAA.

Solution:

Verify if SAA has not been stopped manually outside the cluster.

220849 CCR: Create table %s failed.

Description:

The CCR failed to create the indicated table.

Solution:

The failure can happen due to many reasons, for some of which no user action is required because the CCR client in that case will handle the failure. The cases for which user action is required depends on other messages from CCR on the node, and include: If it failed because the cluster lost quorum, reboot the cluster. If the root file system is full on the node, then free up some space by removing unnecessary files. If the root disk on the afflicted node has failed, then it needs to be replaced. If the cluster repository is corrupted as indicated by other CCR messages, then boot the offending node(s) in -x mode to restore the cluster repository backup. The cluster repository is located at /etc/cluster/ccr/.

221314 INTERNAL ERROR: usage: $0 <gateway_or_server_root>

Description:

An internal error has occurred.

Solution:

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

221527 Created thread %d for node %d.

Description:

The cl_eventd successfully created a necessary thread.

Solution:

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

221746 Failed to retrieve property %s: %s.

Description:

The PMF action script supplied by the DSDL could not retrieve the given property of the resource.

Solution:

Check the syslog messages around the time of the error for messages indicating the cause of the failure. If this error persists, contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

222512 fatal: could not create death_ff

Description:

The daemon indicated in the message tag (rgmd or ucmmd) was unable to create a failfast device. The failfast device kills the node if the daemon process dies either due to hitting a fatal bug or due to being killed inadvertently by an operator. This is a requirement to avoid the possibility of data corruption. The daemon will produce a core file and will cause the node to halt or reboot.

Solution:

Save a copy of the /var/adm/messages files on all nodes, and of the core file generated by the daemon. Contact your authorized Sun service provider for assistance in diagnosing the problem.

222869 Database is already running.

Description:

The database is running and does not need to be started.

Solution:

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

223145 gethostbyname failed for (%s)

Description:

Failed to get information about a host. The "gethostbyname" man page describes possible reasons.

Solution:

Make sure entries in /etc/hosts, /etc/nsswitch.conf and /etc/netconfig are correct to get information about this host.

223458 INTERNAL ERROR CMM: quorum_algorithm_init called already.

Description:

This is an internal error during node initialization, and the system can not continue.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

223641 Validation failed. User %s does not belong to the project %s.

Description:

Resource_project_name or RG_project_name property has been set to a project whose members do not include the specified user.

Solution:

Please set the Resource_project_name or the RG_project_name property to a valid project for the specified user. The project membership of a user is displayed by the command 'projects <user>'.

223641 reservation error() - Unable to release fencing lock %s.

Description:

The device fencing program was unable to release the lock which is used to indicate that device fencing is in progress. This node will be to act as the primary node for device groups.

Solution:

A reboot of the node may clear up the problem. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

223809 CL_EVENTLOG Error: Can't start ${LOGGER}.

Description:

An attempt to start the cl_eventlogd server failed.

Solution:

224682 Failed to initialize the probe history.

Description:

A process has failed to allocate memory for the probe history structure, most likely because the system has run out of swap space.

Solution:

To solve this problem, increase swap space by configuring additional swap devices. See swap(1M) for more information.

224718 Failed to create scalable service in group %s for IP %s Port %d%c%s: %s.

Description:

A call to the underlying scalable networking code failed. This call may fail because the IP, Port, and Protocol combination listed in the message conflicts with the configuration of an existing scalable resource. A conflict can occur if the same combination exists in a scalable resource that is already configured on the cluster. A combination may also conflict if there is a resource that uses Load_balancing_policy LB_STICKY_WILD with the same IP address as a different resource that also uses LB_STICKY_WILD.

Solution:

Try using a different IP, Port, and Protocol combination. Otherwise, save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

224783 clcomm: Path %s has been deleted

Description:

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

Solution:

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

225296 "pmfadm -s": Can not stop <%s>: Monitoring is not resumed on pid %d

Description:

The command 'pmfadm -s' can not be executed on the given tag because the monitoring is suspended on the indicated pid.

Solution:

Resume the monitoring on the indicated pid with the 'pmfctl -R' command.

225882 Internal: Unknown command type (%d)

Description:

An internal error has occurred in the rgmd while trying to connect to the rpc.fed server.

Solution:

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

226280 PNM daemon exiting

Description:

The PNM daemon (pnmd) is shutting down.

Solution:

This message is informational; no user action is needed.

226907 Failed to run the DB probe script %s

Description:

This is an internal error.

Solution:

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

226914 scswitch: internal error: bad nodename %s in nodelist of resource group %s

Description:

The indicated resource group's Nodelist property, as stored in the CCR, contains an invalid nodename. This might indicate corruption of CCR data or rgmd in-memory state. The scswitch command will fail.

Solution:

Use scstat(1M) -g and scrgadm(1M) -pvv to examine resource group properties. If the values appear corrupted, the CCR might have to be rebuilt. If values appear correct, this may indicate an internal error in the rgmd. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

227214 Error: duplicate method <%s> launched on resource <%s> in resource group <%s>

Description:

Due to an internal error, the rgmd state machine has attempted to launch two different methods on the same resource on the same node, simultaneously. The rgmd will reject the second attempt and treat it as a method failure.

Solution:

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

227820 Attempting to stop the data service running under process monitor facility.

Description:

The function is going to request the PMF to stop the data service. If the request fails, refer to the syslog messages that appear after this message.

Solution:

This is an informational message, no user action is required.

228021 Failed to retrieve the extension property <%s> for NetBackup, error : %s.

Description:

The extension <%s> is missing in the RTR File.

Solution:

Serious error. The RTR file may be corrupted. Reload the package for HA-NetBackup SUNWscnb. If problem persists, contact the Sun Cluster HA developer.

228212 reservation fatal error(%s) - unable to get local node id

Description:

The device fencing program has suffered an internal error.

Solution:

Contact your authorized Sun 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 may be unable to access shared devices. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access shared devices. In either case, it may 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. If desired, it may be possible to switch the device group to this node with the scswitch command. If no other node was available, then the device group will not have been started. The scswitch command may be used 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. The desired action may be retried.

228399 Unable to stop processes running under PMF tag %s.

Description:

Sun Cluster HA for Sybase failed to stop processes using Process Monitoring Facility. Please examine if the PMF tag indicated in the message exists on the node. (command: pmfadm -l <tag>). Other syslog messages and the log file will provide additional information on possible reasons for the failure.

Solution:

Please examine Sybase logs and syslog messages. If this message is seen under heavy system load, it will be necessary to increase Stop_timeout property of the resource.

228461 CMM: Issuing a SCSI2 Release failed on quorum device %s with error %d.

Description:

This node encountered the specified error while issuing a SCSI2 Release operation on the specified quorum device. The quorum code will either retry this operation or will ignore this quorum device.

Solution:

There may be other related messages that may provide more information regarding the cause of this problem. SCSI2 operations fail with an error code of EACCES if SCSI3 keys are present on the device. Scrub the SCSI3 keys off of the quorum device.

230326 start_uns - Waiting for WebSphere MQ UserNameServer Queue Manager

Description:

The WebSphere UserNameServer is dependent on the WebSphere MQ UserNameServer Queue manager, which is not available. So the WebSphere UserNameServer will wait until it is available before it is started, or until Start_timeout for the resource occurs.

Solution:

None.

231556 %s can't plumb %s: out of instance numbers on %s

Description:

This means that we have reached the maximum number of Logical IPs allowed on an adapter.

Solution:

This can be increased by increasing the ndd variable ip_addrs_per_if. However the maximum limit is 8192. The default is 256.

231770 ns: Could not initialize ORB: %d

Description:

could not initialize ORB.

Solution:

Please make sure the nodes are booted in cluster mode.

231991 WARNING: lkcm_dreg: udlm_send_reply failed

Description:

Could not deregister udlm with ucmm.

Solution:

None.

232201 Invalid port number returned.

Description:

Invalid port number was retrieved for the Port_list property of the resource.

Solution:

Any of the following situations may occur. Different user action is required for these different scenarios. 1) If a new resource has created or updated, check whether it has valid port number. If port number is not valid, provide valid port number using scrgadm(1M) command. 2) Check the syslog messages that have occurred just before this message. If it is "Out of memory" problem, then correct it. 3) For all other cases, treat it as an Internal error. Contact your authorized Sun service provider.

232501 Validation failed. ORACLE_HOME/bin/svrmgrl not found ORACLE_HOME=%s

Description:

Oracle binaries (svrmgrl) not found in ORACLE_HOME/bin directory. ORACLE_HOME specified for the resource is indicated in the message. HA-Oracle will not be able to manage resource if ORACLE_HOME is incorrect.

Solution:

Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.

232565 Scalable services enabled.

Description:

This means that the scalable services framework is set up in the cluster. Specifically, is is printed out for the node that has joined the cluster and for which services have been downloaded. Once the services have been downloaded, those services are ready to participate as scalable services.

Solution:

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

232920 -d must be followed by a hex bitmask

Description:

Incorrect arguments used while setting up sun specific startup parameters to the Oracle unix dlm.

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.

233017 Successfully stopped %s.

Description:

The resource was successfully stopped by Sun Cluster.

Solution:

No user action is required.

233053 SharedAddress offline.

Description:

The status of the sharedaddress resource is offline.

Solution:

This is informational message. No user action required.

233327 Switchover (%s) error: failed to mount FS (%d)

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

233956 Error in reading message in child process: %m

Description:

Error occurred when reading message in fault monitor child process. Child process will be stopped and restarted.

Solution:

If error persists, then disable the fault monitor and report the problem.

233961 scvxvmlg error - symlink(%s, %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 unaccessible 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.

234330 Failed to start NFS daemon %s.

Description:

HA-NFS implementation failed to start the specified NFS daemon.

Solution:

HA-NFS would attempt to remedy this situation by attempting to restart the daemon again, or by failing over if necessary. If the system is under heavy load, increase Start_timeout for the HA-NFS resource.

234438 INTERNAL ERROR: Invalid resource property type <%d> on resource <%s>; aborting node

Description:

An attempted creation or update of a resource has failed because of invalid resource type data. This may indicate CCR data corruption or an internal logic error in the rgmd. The rgmd will produce a core file and will force the node to halt or reboot.

Solution:

Use scrgadm(1M) -pvv to examine resource properties. If the resource or resource type properties appear to be corrupted, the CCR might have to be rebuilt. If values appear correct, this may indicate an internal error in the rgmd. Re-try the creation or update operation. If the problem recurs, save a copy of the /var/adm/messages files on all nodes and contact your authorized Sun service provider for assistance.

234463 INTERNAL ERROR: process_resource: resource group <%s> is pending_mon_disable but contains resource <%s> in STOP_FAILED state

Description:

During a resource monitor disable (scswitch -M -n), 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.

235455 inet_ntop: %s

Description:

The cl_apid received the specified error from inet_ntop(3SOCKET). The attempted connection was ignored.

Solution:

No action required. If the problem persists, 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.

235707 pmf_monitor_suspend: pmf_remove_triggers: %s

Description:

The rpc.pmfd server was not able to suspend the monitoring of a process and the monitoring of the process has been aborted. The message contains the system error.

Solution:

Save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

236733 lookup of oracle dba gid failed.

Description:

Could not find group id for dba. udlm will not startup.

Solution:

Make sure /etc/nswitch.conf and /etc/group files are valid and have correct information to get the group id of dba.

236737 libsecurity: NULL RPC to program %s (%lu) failed; will not 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. The program will not retry because the time limit of 1 hr was exceeded. 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 Sun service provider to determine whether a workaround or patch is available.

237149 clcomm: Path %s being constructed

Description:

A communication link is being established with another node.

Solution:

No action required.

237547 Adaptive server stopped (nowait).

Description:

The Sybase adaptive server been been stopped by Sun Cluster HA for Sybase using the nowait option.

Solution:

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

237724 Failed to retrieve hostname: %s.

Description:

The call back method has failed to determine the hostname. Now the callback methods will be executed in /var/core directory.

Solution:

No user action is needed. For detailed error message, look at the syslog message.

237744 SAP was brought up outside of HA-SAP, HA-SAP will not shut it down.

Description:

SAP was started up outside of the control of Sun cluster. It will not be shutdown automatically.

Solution:

Need to shut down SAP, before trying to start up SAP under the control of Sun Cluster.

238019 Invalid configuration. Both SUNWcvmr and SUNWschwr packages are installed on this node. Only one of these package must be installed.

Description:

Sun Cluster support for Oracle Parallel Server/ Real Application Clusters will not function correctly when both SUNWschwr and SUNWcvmr packages are installed on the node.

Solution:

Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.

239109 Validation failed. Resource property RESOURCE_DEPENDENCIES should contain at least the rac_framework resource

Description:

The resource being created or modified must be dependent upon at least the rac_framework resource

Solution:

Amend the RESOURCE_DEPENDENCIES property to inlude the rac_framework resource

239109 Validation failed. Resource property RESOURCE_DEPENDENCIES should contain at least the rac_framework resource

Description:

The resource being created or modified should be dependent upon the rac_framework resource in the RAC framework resource group.

Solution:

If not already created, create the RAC framework resource group and it's associated resources. Then specify the rac_framework resource for this resource's RESOURCE_DEPENDENCIES property.

239415 Failed to retrieve the cluster handle: %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 Sun service provider for assistance in diagnosing the problem.

239415 Failed to retrieve the cluster handle: %s.

Description:

An API operation has failed while retrieving the cluster information.

Solution:

This may be solved by rebooting the node. For more details about API failure, check the messages from other components.

239631 The status of device: %s is set to UNMONITORED

Description:

A device is not monitored.

Solution:

No action required.

239735 Couldn't parse policy string %s

Description:

This message appears when the customer is initializing or changing a scalable services load balancer, by starting or updating a service. The Load_Balancing_String is invalid.

Solution:

Check the Load_Balancing_String value specified when creating the resource group and make sure that a valid value is used.

240376 No protocol was given as part of property %s for element %s. The property must be specified as %s=PortNumber%cProtocol,PortNumber%cProtocol,...

Description:

The property named does not have a legal value.

Solution:

Assign the property a legal value.

Description:

The IPMP group named is in a transition state. The status will be checked again.

Solution:

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

240388 Prog <%s> step <%s>: timed out.

Description:

A step has exceeded its configured timeout and was killed by ucmmd. This in turn will cause a reconfiguration of OPS.

Solution:

Other syslog messages occurring just before this one might indicate the reason for the failure. After correcting the problem that caused the step to fail, the operator may retry reconfiguration of OPS.

240529 Listener status probe failed with exit code %s.

Description:

An attempt to query the status of the Oracle listener using command 'lsnrctl status <listener_name>' failed with the error code indicated. HA-Oracle will attempt to kill the listener and then restart it.

Solution:

None, HA-Oracle will attempt to restart the listener. However, the cause of the failure should be investigated further. Examine the log file and syslog messages for additional information.

241147 Invalid value %s for property %s.

Description:

An invalid value was supplied for the property.

Solution:

Supply "conf" or "boot" as the value for DNS_mode property.

241441 clexecd: ioctl(I_RECVFD) returned %d. Returning %d to clexecd.

Description:

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

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

241630 File %s should be readable only by the owner %s.

Description:

The specified file is expected to be readable only by the specified user, who is the owner of the file.

Solution:

Make sure that the specified file has correct permissions permissions by running "chmod 600 <file>" for non-executable files, or "chmod 700 <file>" for executable files.

241948 Failed to retrieve resource <%s> extension property <%s>: %s.

Description:

An internal error occurred in the rgmd while checking a resource property.

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.

242214 clexecd: fork1 returned %d. Returning %d to clexecd.

Description:

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

Solution:

If the error number is 12 (ENOMEM), install more memory, increase swap space, or reduce peak memory consumption. If error number is something else, contact your authorized Sun service provider to determine whether a workaround or patch is available.

242385 Failed to stop liveCache with command %s. Return code from SAP command is %d.

Description:

Failed to shutdown liveCache immediately with listed command. The return code from the SAP command is listed.

Solution:

Check the return code for dbmcli command for reasons of failure. Also, check the SAP log files for more details.

243322 Unable to launch dispatch thread on remote node %d

Description:

An attempt to deliver an event to the specified node failed.

Solution:

Examine other syslog messages occurring at about the same time on both this node and the remote node to see if the problem can be identified. 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.

243444 CMM: Issuing a SCSI2 Tkown failed for quorum device with error %d.

Description:

This node encountered the specified error while issuing a SCSI2 Tkown operation on a quorum device. This will cause the node to conclude that it has been unsuccessful in preempting keys from the quorum device, and therefore the partition to which it belongs has been preempted. 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 will be other related messages that will identify the quorum device for which this error has occurred. If the error encountered is EACCES, then the SCSI2 command could have failed due to the presence of SCSI3 keys on the quorum device. Scrub the SCSI3 keys off of it, and reboot the preempted nodes.

243639 Scalable service instance [%s,%s,%d] deregistered on node %s.

Description:

The specified scalable service had been deregistered on the specified node. Now, the gif node cannot redirect packets for the specified service to this node.

Solution:

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

243648 %s: Could not create %s table

Description:

libscdpm could not create the cluster-wide consistent table that the Disk Path Monitoring Daemon uses to maintain persistent information about disks and their monitoring status.

Solution:

This is a fatal error for the Disk Path Monitoring daemon and will mean that the daemon cannot run on this node. Check to see if there is enough space available on the root file system. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

243781 cl_event_open_channel(): %s

Description:

The cl_eventd was unable to create the channel by which it receives sysevent messages. It will exit.

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.

243965 udlm_ack_msg: udp is null!

Description:

Can not acknowledge a message received from udlmctl because the address to acknowledge to is null.

Solution:

None.

243996 Failed to retrieve resource <%s> extension property <%s>

Description:

Can not get extension property.

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.

244116 clcomm: socreate on routing socket failed with error = %d

Description:

The system prepares IP communications across the private interconnect. A socket create operation on the routing socket failed.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

245068 RG_dependency check failed.

Description:

RG_dependencies resource group property is set but the value is not correct.

Solution:

Ensure that the SAP xserver resource group is listed in RG_dependencies. Also, ensure that the nodelist of the SAP xserver resource group is a superset of the nodelist of the resource group that is set by the RG_dependencies property.

245128 Extension property %s must be set.

Description:

The indicated property must be set by the user.

Solution:

Use scrgadm to set the property.

245186 reservation warning(%s) - MHIOCGRP_PREEMPTANDABORT error 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.

246769 kill -TERM: %s

Description:

The rpc.fed server is not able to kill a tag that timed out, and the error message is shown. An error message is output to syslog.

Solution:

Save the /var/adm/messages file. Examine other syslog messages occurring around the same time on the same node, to see if the cause of the problem can be identified.

247405 Failed to take the resource out of PMF control. Will shutdown WLS using sigkill

Description:

The resource could not be taken out of pmf control. The WLS will however be shutdown by killing the process using sigkill.

Solution:

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

247682 recv_message: cm_reconfigure: %s

Description:

udlm received a message to reconfigure.

Solution:

None. OPS is going to reconfigure.

247752 Failed to start the service %s.

Description:

Specified data service failed to start.

Solution:

Look in /var/adm/messages for the cause of failure. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

248031 scvxvmlg warning - %s does not exist, creating it

Description:

The program responsible for maintaining the VxVM device namespace has discovered inconsistencies between the VxVM device namespace on this node and the VxVM configuration information stored in the cluster device configuration system. If configuration changes were made recently, then this message should reflect one of the configuration changes. If no changes were made recently or if this message does not correctly reflect a change that has been made, the VxVM device namespace on this node may be in an inconsistent state. VxVM volumes may be inaccessible from this node.

Solution:

If this message correctly reflects a configuration change to VxVM diskgroups then no action is required. If the change this message reflects is not correct, then the information stored in the device configuration system for each VxVM diskgroup should be examined for correctness. If the information in the device configuration system is accurate, then executing '/usr/cluster/lib/dcs/scvxvmlg' on this node should restore the device namespace. If the information stored in the device configuration system is not accurate, it must be updated by executing '/usr/cluster/bin/scconf -c -D name=diskgroup_name' for each VxVM diskgroup with inconsistent information.

248838 SAPDB parent kernel process file does not exist.

Description:

The SAPDB parent kernel process file cannot be found on the system.

Solution:

During normal operation, this error should not occurred, unless the file was deleted manually. No action required.

249804 INTERNAL ERROR CMM: Failure creating sender thread.

Description:

An instance of the userland CMM encountered an internal initialization error. This is caused by inadequate memory on the system.

Solution:

Add more memory to the system. If that does not resolve the problem, contact your authorized Sun service provider to determine whether a workaround or patch is available.

249934 Method <%s> failed to execute on resource <%s> in resource group <%s>, error: <%d>

Description:

A resource method failed to execute, due to a system error number identified in the message. The indicated error number appears not to match any of the known errno values described in intro(2). This is considered a method failure. Depending on which method is 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.

Solution:

Other syslog messages occurring at about the same time might provide evidence of the source of the problem. If not, save a copy of the /var/adm/messages files on all nodes, and (if the rgmd did crash) a copy of the rgmd core file, and contact your authorized Sun service provider for assistance.

250047 Failed to start Broadvision servers on %s.

Description:

The Broadvision servers could not be started on the specified host.This could happen if the orbixd didnot get started properly or if there are any configurationerrors.

Solution:

See if there are any internal errors.Look at the Broadvisionconfiguration and check if everything is OK.Try to startBV on the specified host manually and check if it can bestarted properly.If orbixd could be started manually butcouldnt be started under HA contact sun support with/var/adm/messages and other BV logs.

250133 Failed to open the device %s: %s.

Description:

This is an internal error. System failed to perform the specified operation.

Solution:

For specific error information check the syslog message. Provide the following information to your authorized Sun service provider to diagnose the problem. 1) Saved copy of /var/adm/messages file 2) Output of "ls -l /dev/sad" command 3) Output of "modinfo | grep sad" command.

250151 write: %s

Description:

The cl_apid experienced the specified error when attempting to write to a file descripter. If this error occurs during termination of the daemon, it may cause the cl_apid to fail to shutdown properly (or at all). If it occurs at any other time, it is probably a CRNP client error.

Solution:

250387 Stop fault monitor using pmfadm failed. tag %s error=%s.

Description:

The Process Monitoring Facility could not stop the Sun ClusterHA for Sybase fault monitor. The fault monitor tag is providedin the message. The error returned by the PMF is indicatedin the message.

Solution:

Stop the fault monitor processes. Contact your authorized Sun Serviceprovider to report this problem.

251472 Validation failed. SYBASE directory %s does not exist.

Description:

The indicated directory does not exist. The SYBASE environmentvariable may be incorrectly set or the installation may be incorrect.

Solution:

Check the SYBASE environment variable value and verify the Sybaseinstallation.

251552 Failed to validate configuration.

Description:

The data service is not properly configured.

Solution:

Look at the prior syslog messages for specific problems and take corrective action.

251620 Validate - RUN_MODE has to be server

Description:

The DHCP resource requires that that the /etc/inet/dhcpsvc.conf file has RUN_MODE=SERVER.

Solution:

Ensure that /etc/inet/dhcpsvc.conf has RUN_MODE=SERVER by configuring DHCP appropriately, i.e. as defined within the Sun Cluster 3.0 Data Service for DHCP.

251702 Error initializing an internal component of the version manager (error %d).

Description:

This message can occur when the system is booting if incompatible versions of cluster software are installed.

Solution:

Verify that any recent software installations completed without errors and that the installed packages or patches are compatible with the rest of the installed software. Also contact your authorized Sun service provider to determine whether a workaround or patch is available.

252457 The %s command does not have execute permissions: <%s>

Description:

This command input to the agent builder does not have the expected default execute permissions.

Solution:

Reset the permissions to allow execute permissions using the chmod command.

252585 ERROR: stop_mysql Option -U not set

Description:

The -U option is missing for stop_mysql command.

Solution:

Add the -U option for stop_mysql command.

254053 Initialization error. Fault Monitor password is NULL

Description:

Internal error. Environment variable SYBASE_MONITOR_PASSWORD not set before invoking fault monitor.

Solution:

Report this problem to your authorized Sun service provider.

254131 resource group %s removed.

Description:

This is a notification from the rgmd that the operator has deleted a resource group. This may be used by system monitoring tools.

Solution:

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

254388 Failed to retrieve Message server pid.

Description:

Failed to retrieve the process ID for the message server indicating the message server process is not running.

Solution:

No action needed. The fault monitor will detect this and take appropriate action.

254692 scswitch: internal error: bad state <%s> (<%d>) for resource group <%s>

Description:

While attempting to execute an operator-requested switch of the primaries of a resource group, the rgmd has discovered the indicated resource group to be in an invalid state. The switch action will fail.

Solution:

This may indicate an internal error or bug in the rgmd. Contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

255071 Low memory: unable to process client registration

Description:

The cl_apid experienced a memory error that prevented it from processing a client registration request.

Solution:

Increase swap space, install more memory, or reduce peak memory consumption.

255115 Retrying to retrieve the resource type information.

Description:

An update to cluster configuration occurred while resource type properties were being retrieved

Solution:

Ignore the message.

255929 in libsecurity authsys_create_default failed

Description:

A client was not able to make an rpc connection to a server (rpc.pmfd, rpc.fed or rgmd) because it failed the authentication process. An error message is output to syslog.

Solution:

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

256023 pmf_monitor_suspend: Error opening procfs status file <%s> for tag <%s>: %s

Description:

The rpc.pmfd server was not able to open a procfs status file, and the system error is shown. procfs status files are required in order to monitor user processes. This error occurred for a process whose monitoring had been suspended. The monitoring of this process has been aborted and can not be resumed.

Solution:

Investigate if the machine is running out of memory. If this is not the case, save the syslog messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

256245 ORB initialization failure

Description:

An attempt to start the scdpmd failed.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

257965 File %s should be readable by %s.

Description:

A program required the specified file to be readable by the specified user.

Solution:

Set correct permissions for the specified file to allow the specified user to read it.

258357 Method <%s> failed to execute on resource <%s> in resource group <%s>, error: <%s>

Description:

A resource method failed to execute, due to a system error described in the message. For an explanation of the error message, consult intro(2). 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.

Solution:

If the error message is not self-explanatory, other syslog messages occurring at about the same time might provide evidence of the source of the problem. If not, save a copy of the /var/adm/messages files on all nodes, and (if the rgmd did crash) a copy of the rgmd core file, and contact your authorized Sun service provider for assistance.

258909 clexecd: sigfillset returned %d. Exiting.

Description:

clexecd program has encountered a failed sigfillset(3C) system call. The error message indicates the error number for the failure.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

259455 in fe_set_env_vars malloc failed

Description:

The rgmd server was not able to allocate memory for the environment name, while trying to connect to the rpc.fed server, possibly due to low memory. An error message is output to syslog.

Solution:

Investigate if the host is running out of memory. If not save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

259810 reservation error(%s) - do_scsi3_reserve() error for disk %s

Description:

The device fencing program has encountered errors while trying to access a device. All retry attempts have failed.

Solution:

This may be indicative of a hardware problem, which should be resolved as soon as possible. Once the problem has been resolved, the following actions may be necessary: If the message specifies the 'node_join' transition, then this node may be unable to access the specified device. If the failure occurred during the 'release_shared_scsi2' transition, then a node which was joining the cluster may be unable to access the device. In either case, access can be reacquired 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 may have failed to start on this node. If the device group was started on another node, it may be moved to this node with the scswitch command. If the device group was not started, it may be started with the scswitch command. If the failure occurred during the 'primary_to_secondary' transition, then the shutdown or switchover of a device group may have failed. If so, the desired action may be retried.

261123 resource group %s state change to managed.

Description:

This is a notification from the rgmd that a resource group's state has changed. This may be used by system monitoring tools.

Solution:

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

261236 Validate - my.cnf %s does not exist

Description:

The my.cnf configuration doesn't exist in the defined database directory.

Solution:

Make sure that my.cnf is placed in the defined database directory.

262281 Validate - User %s does not exist

Description:

The WebSphere Broker userid does not exist.

Solution:

Ensure the correct WebSphere Broker userid has been setup and was correctly entered when registering the WebSphere Broker resource.

262295 Failback bailing out because resource group <%s>is being updated or switched

Description:

The rgmd was unable to failback the specified resource group to a more preferred node because the resource group was already in the process of being updated or switched.

Solution:

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

262898 Name service not available.

Description:

The monitor_check method detected that name service is not responsive.

Solution:

Check if name servcie is configured correctly. Try some commands to query name serves, such as ping and nslookup, and correct the problem. If the error still persists, then reboot the node.

263110 Error deleting PidLog <%s> (%s) for iPlanet service with config file <%s>

Description:

The data service was not able to delete the specified PidLog file.

Solution:

Delete the PidLog file manually and start the the resource group.

263258 CCR: More than one copy of table %s has the same version but different checksums. Using the table from node %s.

Description:

The CCR detects that two valid copies of the indicated table have the same version but different contents. The copy on the indicated node will be used by the CCR.

Solution:

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

263606 unpack_rg_seq: rname_to_r error <%s>

Description:

Due to an internal error, the rgmd was unable to find the specified resource data in memory.

Solution:

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

264326 Error (%s) when reading extension property <%s>.

Description:

Error occurred in API call scha_resource_get.

Solution:

Check syslog messages for errors logged from other system modules. If error persists, please report the problem.

264326 Error (%s) when reading extension property <%s>.

Description:

This is an internal error. Program failed to read an extension property of the resource.

Solution:

If the problem persists, save the contents of /var/adm/messages and contact your Sun service representative.

265109 Successfully stopped the database.

Description:

The resource was able to successfully shutdown the the HADB database.

Solution:

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

265925 CMM: Cluster lost operational quorum; aborting.

Description:

Not enough nodes are operational to maintain a majority quorum, causing the cluster to fail to avoid a potential split brain.

Solution:

The nodes should rebooted.

266059 security_svc_reg failed.

Description:

The rpc.pmfd server was not able to initialize authentication and rpc initialization. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.

Solution:

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

266274 %s: No memory, restarting service.

Description:

The PMF action script supplied by the DSDL could not complete its function because it could not allocate the required amount of memory; the PMF action script has restarted the application.

Solution:

If this error persists, contact your authorized Sun service provider for assistance in diagnosing and correcting the problem.

266602 ERROR: stop_mysql Option -G not set

Description:

The -G option is missing for stop_mysql command.

Solution:

Add the -G option for stop_mysql command.

266834 CMM: Our partition has been preempted.

Description:

The cluster partition to which this node belongs has been preempted by another partition during a reconfiguration. The preempted partition will abort. 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 may be other related messages that may indicate why quorum was lost. Determine why quorum was lost on this node partition, resolve the problem and reboot the nodes in this partition.

267361 check_cmg - Database connect to %s failed

Description:

While probing the Oracle E-Business Suite concurrent manager, a test to connect to the database failed.

Solution:

None, if two successive failures occur the concurrent manager resource will be restarted.

267558 Error when reading property %s.

Description:

Unable to read property value using API. Property name is indicated in message. Syslog messages may give more information on errors in other modules.

Solution:

Check syslog messages. Please report this problem.

267589 launch_fed_prog: call to rpc.fed failed for program <%s>, step <%s>

Description:

Launching of fed program failed due to a failure of ucmmd to communicate with the rpc.fed daemon. If the rpc.fed process died, this might lead to a subsequent reboot of the node.

Solution:

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

267673 Validation failed. ORACLE binaries not found ORACLE_HOME=%s

Description:

Oracle binaries not found under ORACLE_HOME. ORACLE_HOME specified for the resource is indicated in the message. HA-Oracle will not be able to manage Oracle if ORACLE_HOME is incorrect.

Solution:

Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.

267673 Validation failed. ORACLE binaries not found ORACLE_HOME=%s

Description:

Oracle binaries not found under ORACLE_HOME. ORACLE_HOME specified for the resource is indicated in the message. HA-Oracle will not be able to manage Oracle if ORACLE_HOME is incorrect.

Solution:

Specify correct ORACLE_HOME when creating resource. If resource is already created, please update resource property 'ORACLE_HOME'.

267724 stat of file system %s failed.

Description:

HA-NFS fault monitor reports a probe failure on a specified file system.

Solution:

Make sure the specified path exists.

268593 Failed to take the resource out of PMF control. Sending SIGKILL now.

Description:

An error was encounterd while taking the resource out of PMF's control while stopping the resource. The resource will be stopped by sending it SIGKILL.

Solution:

This message is informational; no user action is needed.

268593 Failed to take the resource out of PMF control. Sending SIGKILL now.

Description:

Process monitor facility failed to stop monitoring the applicatin. The stop method will send SIGKILL to stop the application.

Solution:

No action required.

269027 sigfillset: %s

Description:

The cl_apid was unable to configure its signal handling functionality, so it is unable to run.

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.

269240 clconf: Write_ccr routine shouldn't be called from kernel

Description:

Routine write_ccr that writes a clconf tree out to CCR should not be called from kernel.

Solution:

No action required. This is informational message.

269251 Failing over all NFS resources from this node

Description:

HA-NFS is failing over all NFS resources.

Solution:

This is an informational message, no action is needed. Look for previous error messages from HA-NFS for the reason for failing over.

270043 reservation warning(%s) - MHIOCENFAILFAST error 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.

270645 Resource Group %s will be restarted

Description:

The WebSphere Broker resource has determined that the WebSphere MQ Broker RDBMS has either failed or has been restarted.

Solution:

None, as the Resource Group will be restarted.

272139 Message Server Process is not running. pid was %d.

Description:

Message server process is not present on the process list indicating message server process is not running on this node.

Solution:

No action needed. Fault monitor will detect that message server process is not running, and take appropriate action.

272238 reservation warning(%s) - MHIOCGRP_RESERVE error 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.

272434 Validation failed. SYBASE text server startup file RUN_%s not found SYBASE=%s.

Description:

Text server was specified in the extension property Text_Server_Name. However, text server startup file was not found. Text server startup file is expected to be: $SYBASE/$SYBASE_ASE/install/RUN_<Text_Server_Name>

Solution:

Check the text server name specified in the Text_Server_Name property. Verify that SYBASE and SYBASE_ASE environment variables are set property in the Environment_file. Verify that RUN_<Text_Server_Name> file exists.

272732 scvxvmlg warning - chmod(%s) failed

Description:

Solution:

273018 INTERNAL ERROR CMM: Failure starting CMM.

Description:

An instance of the userland CMM encountered an internal initialization error.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

273354 CMM: Node %s (nodeid = %d) is dead.

Description:

The specified node has died. It is guaranteed to be no longer running and it is safe to take over services from the dead node.

Solution:

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

273638 The entry %s and entry %s in property %s have the same port number: %d.

Description:

The two entries in the list property duplicate port number.

Solution:

Remove one of the entries or change its port number.

274229 validate_options: $COMMANDNAME Option -N not set

Description:

The option -N of the Apache Tomcat agent command $COMMANDNAME is not set, $COMMANDNAME is either start_sctomcat, stop_sctomcat or probe_sctomcat.

Solution:

Look at previous error messages in the syslog.

274386 reservation error(%s) - Could not determine controller number for device %s

Description:

The device fencing program has suffered an internal error.

Solution:

274421 Port %d%c%s is listed twice in property %s, at entries %d and %d.

Description:

The port number in the message was listed twice in the named property, at the list entry locations given in the message. A port number should only appear once in the property.

Solution:

Specify the property with only one occurrence of the port number.

274506 Wrong data format from kstat: Expecting %d, Got %d.

Description:

See 176151

Solution:

See 176151

274603 No interfaces found

Description:

The allow_hosts or deny_hosts for the CRNP service specifies LOCAL and the cl_apid is unable to find any network interfaces on the local host. This error may prevent the cl_apid from starting up.

Solution:

274605 Server is online.

Description:

Informational message. Oracle server is online.

Solution:

None

274887 clcomm: solaris xdoor: rejected invo: door_return returned, errno = %d

Description:

An unusual but harmless event occurred. System operations continue unaffected.

Solution:

No user action is required.

274901 Invalid protocol %s given as part of property %s.

Description:

The property named does not have a legal value.

Solution:

Assign the property a legal value.

275415 Broker_user extension property must be set

Description:

A Sun Java System Message Queue resource with the Smooth_Shutdown property set to true must also set the Broker_User extension property.

Solution:

Set the Broker_User extension property on the resource.

276380 "pmfadm -k": Error signaling <%s>: %s

Description:

An error occurred while rpc.pmfd attempted to send a signal to one of the processes of the given tag. The reason for the failure is also given. The signal was sent as a result of a 'pmfadm -k' command.

Solution:

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

276672 reservation error(%s) - did_get_did_path() error

Description:

The device fencing program has suffered an internal error.

Solution:

277995 (%s) msg of wrong version %d, expected %d

Description:

Expected to receiver a message of a different version. udlmctl will fail.

Solution:

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.

278240 Stopping fault monitor using pmf tag %s.

Description:

The fault monitor will be stopped usingthe Process Monitoring Facility (PMF), with the tagindicated in the message.

Solution:

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

278526 in libsecurity for program %s (%lu); creat of file %s failed: %s

Description:

The specified server was not able to create a cache file for rpcbind information. The affected component should continue to function by calling rpcbind directly.

Solution:

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

278654 Unable to determine password for broker %s.

Description:

Cannot retrieve the password for the broker.

Solution:

Check that the scs1mqconfig file is accessible and correctly specifies the password.

279035 Unparsed sysevent received

Description:

The cl_apid was unable to process an incoming sysevent. The message will be dropped.

Solution:

279084 CMM: node reconfiguration

Description:

The cluster membership monitor has processed a change in node or quorum status.

Solution:

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

279152 listener %s probe successful.

Description:

Informational message. Listener monitor successfully completed first probe.

Solution:

None

279309 Failfast: Invalid failfast mode %s specified. Returning default mode PANIC.

Description:

An invalid value was supplied for the failfast mode. The software will use the default PANIC mode instead.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

280108 clcomm: unable to rebind %s to name server

Description:

The name server would not rebind this entity.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

280505 Validate - Application user <%s> does not exist

Description:

The Oracle E-Business Suite applications userid was not found in /etc/passwd.

Solution:

Ensure that a local applications userid is defined on all nodes within the cluster.

281386 dl_attach: DL_OK_ACK rtnd prim %u

Description:

Wrong primitive returned to the DL_ATTACH_REQ.

Solution:

Reboot the node. If the problem persists, check the documentation for the private interconnect.

281428 Failed to retrieve the resource group handle: %s.

Description:

An API operation on the resource group has failed.

Solution:

For the resource group name, check the syslog tag. For more details, check the syslog messages from other components. If the error persists, reboot the node.

281428 Failed to retrieve the resource group handle: %s.

Description:

An API operation on the resource group has failed.

Solution:

For the resource group name, check the syslog tag. For more details, check the syslog messages from other components. If the error persists, reboot the node.

281680 fatal: couldn't initialize ORB, possibly because machine is booted in non-cluster mode

Description:

The rgmd was unable to initialize its interface to the low-level cluster machinery. This might occur because the operator has attempted to start the rgmd on a node that is booted in non-cluster mode. The rgmd will produce a core file, and in some cases it might cause the node to halt or reboot to avoid data corruption.

Solution:

If the node is in non-cluster mode, boot it into cluster mode before attempting to start the rgmd. If the node is already in cluster mode, save a copy of the /var/adm/messages files on all nodes, and of the rgmd core file. Contact your authorized Sun service provider for assistance in diagnosing the problem.

281819 %s exited with error %s in step %s

Description:

A ucmm step execution failed in the indicated step.

Solution:

None. See /var/adm/messages for previous errors and report this problem if it occurs again during the next reconfiguration.

281954 Incorrect resource group properties for RAC framework resource group %s. Value of Maximum_primaries(%s) is not equal to number of nodes in nodelist(%s).

Description:

The RAC framework resource group is a scalable resorce group. The value of the Maximum_primaries and Desired_primaries properties should be set to the number of nodes specified in the Nodelist property. RAC framework will not function correctly without these values.

Solution:

Specify correct values of the properties and reissue command. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.

282196 Invalid configuration. Either SUNWcvmr or SUNWschwr package must be installed on this node.

Description:

Sun Cluster support for Oracle Parallel Server/ Real Application Clusters will not function correctly if SUNWschwr or SUNWcvmr package is not installed on the node.

Solution:

Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.

282406 fork1 returned %d. Exiting.

Description:

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

Solution:

282508 INTERNAL ERROR: r_state_at_least: state <%s> (%d)

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, please save a copy of the /var/adm/messages files on all nodes, the output of an scstat -g command, and the output of a scrgadm -pvv command. Report the problem to your authorized Sun service provider.

282828 reservation warning(%s) - MHIOCRELEASE error 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.

282980 liveCache %s was brought down outside of Sun Cluster. Sun Cluster will suspend monitoring for it until it is started up successfully again by the user.

Description:

LiveCache fault monitor detects that liveCache was brought down by user intendedly outside of Sun Cluster. Suu Cluster will not take any action upon it until liveCache is started up successfully again by the user.

Solution:

No action is needed if the shutdown is intended. If not, start up liveCache again using LC10 or lcinit, so it can be under the monitoring of Sun Cluster.

283262 HA: rm_state_machine::service_suicide() not yet implemented

Description:

Unimplemented feature was activated.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

283767 network is very slow

Description:

This means that the PNM daemon was not able to read data from the network - either the network is very slow or the resources on the node are dangerously low.

Solution:

It is best to restart the PNM daemon. Send KILL (9) signal to pnmd. PMF will restart pnmd automatically. If the problem persists, restart the node with scswitch -S and shutdown(1M).

284150 Nodelist must contain two or more nodes.

Description:

The nodelist resource group property must contain two or more Sun Cluster nodes.

Solution:

Recreate the resource group with a nodelist that contains two or more Sun Cluster nodes.

284560 Failed to offload resource group %s: %s

Description:

An attempt to offload the specified resource group failed. The reason for the failure is logged.

Solution:

Look for the message indicating the reason for this failure. This should help in the diagnosis of the problem. Otherwise, save a copy of the /var/adm/messages files on all nodes. Contact your authorized Sun service provider for assistance in diagnosing the problem.

284635 BV Update Completed successfully.

Description:

Just an informational message that the update method method completedsuccessfully

Solution:

No action needed.

284644 Warning: node %d has a weight assigned to it for property %s, but node %d is not in the %s for resource %s.

Description:

A node has a weight assigned but the resource can never be active on that node, therefore it doesn't make sense to assign that node a weight.

Solution:

This is an informational message, no user action is needed. Optionally, the weight that is assigned to the node can be omitted.

284702 Error parsing URI: %s (%s)

Description:

There was an error parsing the URI for the reason given.

Solution:

Fix the syntax of the URI.

285040 The application process tree has died and the action to be taken as determined by scds_fm_history is to failover. However the application is not being failed over because the failover_enabled extension property is set to false. The application is left as-is. Probe quitting ...

Description:

The application is not being restarted because failover_enabled is set to false and the number of restarts has exceeded the retry_count. The probe is quitting because it does not have any application to monitor.

Solution:

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

286259 Incorrect resource group properties for RAC framework resource group %s. Value of Maximum_primaries(%s) is not equal to Desired_primaries(%s).

Description:

The RAC framework resource group is a scalable resorce group. It must be created with identical values for the Maximum_primaries and Desired_primaries properties. RAC framework will not function correctly without these values.

Solution:

Specify correct values of the properties and reissue command. Refer to the documentation of Sun Cluster support for Oracle Parallel Server/ Real Application Clusters for installation procedure.

286722 scvxvmlg error - remove(%s) failed

Description:

Solution:

286807 clnt_tp_create_timed of program %s failed %s.

Description:

HA-NFS fault monitor was not able to make an rpc connection to an nfs server.

Solution:

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

286807 clnt_tp_create_timed of program %s failed %s.

Description:

HA-NFS fault monitor was not able to make an rpc connection to an nfs server.

Solution:

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

287834 Stopping fault monitor: %s:<%s>:%s

Description:

Fault monitor has detected an error. Fault monitor will be stopped. Error detected by fault monitor and action taken by fault monitor is indicated in message.

Solution:

None

288900 internal error: invalid reply code

Description:

The cl_apid encountered an invliad reply code in an sc_reply message.

Solution:

This particular error should not cause problems with the CRNP service, but it might be indicative of other errors. 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 Sun service provider for assistance in diagnosing and correcting the problem.

289194 Can't perform failover: Failover mode set to NONE.

Description:

Cannot perform failover of the data service. Failover mode is set to NONE.

Solution:

This is informational message. If failover is desired, then set the Failover_mode value to SOFT or HARD using scrgadm(1M).

289503 Unable to re-compute NFS resource list.

Description:

The list of HA-NFS resources online on the node has gotten corrupted.

Solution:

Make sure there is space available in /tmp. If the error is showing up despite that, reboot the node.

289503 Unable to re-compute NFS resource list.

Description:

The list of HA-NFS resources online on the node has gotten corrupted.

Solution:

Make sure there is space available in /tmp. If the error is showing up despite that, reboot the node.

290644 Started sap processes under PMF successfully.

Description:

Informational message. SAP is being started under the control of Process Monitoring Facility (PMF).

Solution:

No action needed.

290735 Conversion of hostnames failed.

Description:

Data service is unable to convert the specified hostname into an IP address.

Solution:

Check the syslog messages that occurred just before, to check whether there is any internal error. If there is, then contact your authorized Sun service provider. Otherwise, if the logical host and shared address entries are specified in the /etc/inet/hosts file, check these entries are correct. If this is not the reason then check the health of the name server.

290926 Successful validation.

Description:

The validation of the configuration for the data service was successful.

Solution:

None. This is only an informational message.

291077 Invalid variable name in the Environment file %s. Ignoring %s

Description:

HA-Oracle reads the file specified in USER_ENV property and exports the variables declared in the file. Syntax for declaring the variables is : VARIABLE=VALUE Lines starting with " VARIABLE is expected to be a valid Korn shell variable that starts with alphabet or "_" and contains alphanumerics and "_".

Solution:

Please check the environment file and correct the syntax errors. Do not use export statement in environment file.

291245 Invalid type %d passed.

Description:

An invalid value was passed for the program_type argument in the pmf routines.

Solution:

This is a programming error. Verify the value specified for program_type argument and correct it. The valid types are: SCDS_PMF_TYPE_SVC: data service application SCDS_PMF_TYPE_MON: fault monitor SCDS_PMF_TYPE_OTHER: other

291362 Validate - nmbd %s non-existent executable

Description:

The Samba executable nmbd either doesn't exist or is not executable.

Solution:

Check the correct pathname for the Samba (s)bin directory was entered when registering the resource and that the program exists and is executable.

291378 No Database probe script specified. Will Assume the Database is Running

Description:

This is a informational messages. probing of the URL's set in the Server_url or the Monitor_uri_list failed. Before taking any action the WLS probe would make sure the DB is up (if a db_probe_script extension property is set). But, the Database probe script is not specified. The probe will assume that the DB is UP and will go ahead and take action on the WLS.

Solution:

Make sure the DB is UP.

291522 Validate - smbd %s non-existent executable

Description:

The Samba executable smbd either doesn't exist or is not executable.

Solution:

Check the correct pathname for the Samba (s)bin directory was entered when registering the resource and that the program exists and is executable.

291716 Error while executing siebenv.sh.

Description:

There was an error while attempting to execute (source) the specified file. This may be due to improper permissions, or improper settings in this file.

Solution:

Please verify that the file has correct permissions. If permissions are correct, verify all the settings in this file. Try to manually source this file in korn shell (". siebenv.sh"), and correct any errors.

291986 dl_bind ack bad len %d

Description:

Sanity check. The message length in the acknowledgment to the bind request is different from what was expected. We are trying to open a fast path to the private transport adapters.

Solution:

Reboot of the node might fix the problem.

292013 clcomm: UioBuf: uio was too fragmented - %d

Description:

The system attempted to use a uio that had more than DEF_IOV_MAX fragments.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

292193 NFS daemon %s did not start. Will retry in 100 milliseconds.

Description:

While attempting to start the specified NFS daemon, the daemon did not start.

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 100 milliseconds between restart attempts.

293095 Validation failed. Oracle_config_file %s not found

Description:

Unable to locate the file specified in Oracle_config_file property. This message is given by the validate method, when creating the resource for UNIX Distributed Lock Manager or modifying the property value. This file created when ORCLudlm package is installed on the node.

Solution:

Verify the file name specified in Oracle_config_file property. Verify installation of ORCLudlm package on this node.

295075 Configuration file %s synchronization not required

Description:

This is informational message. Configuration file specified in the message is synchronized with resource properties.

Solution:

None

295366 Unable to mark the interface %s%d down, rc %d

Description:

Topology Manager is done with using the adapter and failed when tried to mark the interface down

Solution:

Not available.

295666 clcomm: setrlimit(RLIMIT_NOFILE): %s

Description:

During cluster initialization within this user process, the setrlimit call failed with the specified error.

Solution:

Read the man page for setrlimit for a more detailed description of the error.

295838 Listener %s started.

Description:

Informational message. HA-Oracle successfully started Oracle listener.

Solution:

None

295838 Listener %s started.

Description:

Informational message. HA-Oracle successfully started Oracle listener.

Solution:

None

296046 INTERNAL ERROR: resource group <%s> is PENDING_BOOT or ERROR_STOP_FAILED or ON_PENDING_R_RESTART, but contains no resources

Description:

The operator is attempting to delete the indicated resource group. Although the group is empty of resources, it was found to be in an unexpected state. This will cause the resource group deletion to fail.

Solution:

Use scswitch(1M) -z to switch the resource group offline on all nodes, then retry the deletion operation. Since this problem might indicate an internal logic error in the rgmd, please save a copy of the /var/adm/messages files on all nodes, and report the problem to your authorized Sun service provider.

297061 clcomm: can't get new reference

Description:

An attempt was made to obtain a new reference on a revoked handler.

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

297139 CCR: More than one data server has override flag set for the table %s. Using the table from 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. In this case, the CCR detected multiple nodes having the override flag set for the indicated table. It chose the copy on the indicated node as the final version.

Solution:

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

297178 Error opening procfs control file <%s> for tag <%s>: %s

Description:

The rpc.pmfd server was not able to open a procfs control file, and the system error is shown. procfs control files are required in order to monitor user processes.

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.

297325 The node portion of %s at position %d in property %s is not a valid node identifier or node name.

Description:

An invalid node was specified for the named property. The position index, which starts at 0 for the first element in the list, indicates which element in the property list was invalid.

Solution:

Specify a valid node instead.

297493 Validate - Applications directory %s does not exist

Description:

The Oracle E-Business Suite applications directory does not exist.

Solution:

Check that the correct pathname was entered for the applications directory when registering the resource and that the directory exists.

297536 Could not host device service %s because this node is being shut down

Description:

An attempt was made to start a device group on this node while the node was being shutdown.

Solution:

If the node was not being shutdown during this time, or if the problem persists, please contact your authorized Sun service provider to determine whether a workaround or patch is available.

297867 (%s) t_bind: tli error: %s

Description:

Call to t_bind() failed. The "t_bind" man page describes possible error codes. udlmctl will exit.

Solution:

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.

298060 Invalid project name: %s

Description:

Either the given project name doesn't exist, or root is not a valid user of the given project.

Solution:

Check if the project name is valid and root is a valid user of that project.

298320 Command %s is too long.

Description:

The command string passed to the function is too long.

Solution:

Use a shorter command name or shorter path to the command.

298360 HA: exception %s (major=%d) from initialize_seq().

Description:

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

Solution:

Contact your authorized Sun service provider to determine whether a workaround or patch is available.

298532 Script lccluster does not exist.

Description:

Script 'lccluster' is not found under /sapdb/<livecache_Name>/db/sap/.

Solution:

Follow the HA-liveCache installation guide to create 'lccluster'.

298625 check_winbind - User <%s> can't be retrieved by the nameservice

Description:

The Windows NT userid used by winbind could not be retrieved through the name service.

Solution:

Check that the correct userid was entered when registering the Winbind resource and that the userid exists within the Windows NT domain.

298719 getrlimit: %s

Description:

The rpc.pmfd or rpc.fed server was not able to get the limit of files open. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.

Solution:

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

298744 validate: $Variable is not set in the parameterfile $Filename but it is required

Description:

The variable $Variable is not set in the parameter file $Filename.

Solution:

Set the variable in the file $Filename to a valid contents.

298911 setrlimit: %s

Description:

The rpc.pmfd server was not able to set the limit of files open. The message contains the system error. This happens while the server is starting up, at boot time. The server does not come up, and an error message is output to syslog.

Solution:

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

299417 in libsecurity strong Unix authorization failed

Description:

A server (rgmd) refused an rpc connection from a client because it failed the Unix authentication. This happens if a caller program using scha public api, either in its C form or its CLI form, is not running as root or is not making the rpc call over the loopback interface. An error message is output to syslog.

Solution:

Check that the calling program using the scha public api is running as root and is calling over the loopback interface. If both are correct, save the /var/adm/messages file. Contact your authorized Sun service provider to determine whether a workaround or patch is available.

299639 Failed to retrieve the property %s: %s. Will shutdown the WLS using sigkill

Description:

This is an internal error. The property could not be retrieved. The WLS stop method however will go ahead and kill the WLS process.

Solution:

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