Message IDs 500000–599999

This section contains message IDs 500000–599999.

500095 The "%s" command returned error %s, unable to start the UCMMD under the PMMD.

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

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

500540 QUORUM_GENERIC: quorum_register error: writing registration key on quorum device %s failed with error code %d.

Description: An error was encountered when placing the node's registration key on a specified quorum device. This error occurs because of unexpected behavior from the device driver, the multipathing driver, or the device's firmware.

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

501184 Conflict: Attempt to change binding (%s, %d) to node %d

Description: An attempt was made to change the node affinity for a specific client address. This can happen if an attempt was made to establish an outgoing connection from a node that is different from the node that is handling the specific client. It can also happen when a client sends a packet for the first time and there was an outgoing connection being attempted simultaneously.

Solution: The cluster service will see connection timeouts and should be handled correctly by the service. This is an informational message. No user action is required.

501495 Validation failed. The RAC framework resource %s that is specified in the RESOURCE_DEPENDENCIES property is not in any of the resource groups specified by the resource group property RG_AFFINITIES.

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 scalable resource group containing RAC framework resource and its associated resources. Specify this resource's dependency on the RAC framework by updating the RESOURCE_DEPENDENCIES property, and ensure that the RAC framework resource group is a part of the strong positive affinity (++) list specified in the RG_AFFINITIES property value for the resource group containing the proxy resource.

501628 Function: check_sczbt - runlevel did not run successfully (return code %s) in the non-global zone %s, try again in 5 seconds

Description: The runlevel command did not run successfully in the configured non-global zone. The state is checked again in 5 seconds.

Solution: None.

501632 Incorrect syntax in the environment file %s. Ignoring %s

Description: HA-Oracle reads the fle 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.

501723 Insufficient memory. Exiting.

Description: process_cmd_log was unable to allocate memory.

Solution: Ensure that the cluster node has sufficient memory.

501981 Valid connection attempted from %s: %s

Description: The cl_apid received a valid client connection attempt from the specified IP address.

Solution: No action required. If you do not wish to allow access to the client with this IP address, modify the allow_hosts or deny_hosts as required.

502022 fatal: joiners_read_ccr: exiting early because of unexpected exception

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.

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

502258 fatal: Resource group <%s> create failed with error <%s>; aborting node

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

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

504794 %s/bin/crsctl is either not found or not executable.

Description: ${ORA_CRS_HOME}/bin/crsctl is either not found or not executable.

Solution: Verify that the Grid Infrastructure for Clusters installation completed successfully on all cluster nodes. If the problem persists contact your Oracle support representative for further assistance.

506226 Deletion of FMRI %s failed %s

Description: An attempt to delete the SMF service instance has failed.

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

506381 Custom action file %s contains errors.

Description: The custom action file that is specified contains errors which need to be corrected before it can be processed completely.

Solution: Please ensure that all entries in the custom monitor action file are valid and follow the correct syntax. After the file is corrected, validate it again to verify the syntax.

507933 Target host %s not matched with the resource group nodelist, normal failover will be performed.

Description: The target host found in the command log file is not a valid entry within the resource groups nodelist.

Solution: None required. The domain will not be migrated or live migrated instead a normal failover will be performed.

508160 Password file cannot be (null).

Description: Password file cannot be null.

Solution: Ensure that a password file name is specified.

508719 set_acfs_variables - The Oracle ASM disk group proxy resource (%s) has not set resource_dependencies_offline_restart to any SUNW.scalable_asm_instance_proxy resource

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

Solution: Ensure that resource_dependencies_offline_restart is set.

509136 Probe failed.

Description: Fault monitor was unable to perform complete health check of the service.

Solution: 1) Fault monitor would take appropiate action (by restarting or failing over the service.). 2) Data service could be under load, try increasing the values for Probe_timeout and Thororugh_probe_interval properties. 3) If this problem continues to occur, look at other messages in syslog to determine the root cause of the problem. If all else fails reboot node.

512980 Internal Error: ORACLE_OWNER not set even after successful validation. Shutdown may not be successful in cleaning up all resources.

Description: An internal error occurred while attempting to save the name of the owner of the Oracle installation in a local file for use during shutdown of Oracle.

Solution: After next shutdown of the resource, check to verify if the shutdown completed successfully by cleaning up all the resources. If the problem persists, report it to your Oracle support representative.

514078 Validate - The keyword INTERFACES have to be set in %s when -T is being used

Description: If USE_CGTP=TRUE was set within /opt/SUNWscdhc/util/dhcp_config then the INTERFACES within /etc/inet/dhcpsvc.conf needs to be set.

Solution: If USE_CGTP=TRUE is required, then ensure that the INTERFACES variable is set within /etc/inet/dhcpsvc.conf. If USE_CGTP=TRUE is required, then ensure that the INTERFACES variable is set within /etc/inet/dhcpsvc.conf. Refer to dhcpsvc.conf(4) man page for further information on INTERFACES.

514731 Failed to kill listener process for %s

Description: Failed to kill listener processes.

Solution: None

515849 acfsutil info fs %s -o isavailable,iscorrupt returns %s

Description: "acfsutil info fs <filesystem> -o isavailable,iscorrupt" failed

Solution: Contact your Oracle support representative for further assistance.

516089 Oracle commands inaccessible. Forcing shutdown of Oracle by killing Oracle processes and removing any shared memory.

Description: The resource shutdown will attempt to clean up any Oracle processes or shared memory segments. A graceful shutdown could not be attempted as Oracle commands are inaccessible, possibly due to the commands residing on a failover, global, or NAS file system on which the database resource's dependency has not been set.

Solution: This message is informational. You must ensure that the resource comes online correctly on an alternate cluster node or on the same node after the Oracle commands become accessible again. If possible and supported, set the dependency of the database resource on the file system resource.

517720 Invalid password file specified %s.

Description: Incorrect Password file specified.

Solution: Ensure that a valid password file is specified.

519262 Validation failed. SYBASE monitor server startup file RUN_%s not found SYBASE=%s.

Description: Monitor server was specified in the extension property Monitor_Server_Name. However, monitor server startup file was not found. Monitor server startup file is expected to be: $SYBASE/$SYBASE_ASE/install/RUN_<Monitor_Server_Name>

Solution: Check the monitor server name specified in the Monitor_Server_Name property. Verify that SYBASE and SYBASE_ASE environment variables are set property in the Environment_file. Verify that RUN_<Monitor_Server_Name> file exists.

519641 sckrb5 not running.

Description: HA-KDC's stop method was called but the service was not running.

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

521393 Backup server stopped.

Description: The backup server was stopped by Oracle Solaris Cluster HA for Sybase.

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

521671 uri <%s> probe failed

Description: The probing of the url set in the monitor_uri_list extension property failed. The agent probe will take action.

Solution: None. The agent probe will take action. However, the cause of the failure should be investigated further. Examine the log file and syslog messages for additional information.

521918 Validation failed. Connect string is NULL.

Description: The 'Connect_String' extension property used for fault monitoring is null. This has the format "username/password".

Solution: Check for syslog messages from other system modules. Check the resource configuration and the value of the 'Connect_string' property.

523531 Listener probe timed out two times consecutively.

Description: Listener monitor has timed out in two successive attempts to probe the listener.

Solution: None

523643 INTERNAL ERROR: %s

Description: An internal error has occurred.

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

524368 Kerberos database %s is missing, exiting.

Description: The /var/krb5/principal database is missing or of zero length.

Solution: Verify that the principal database has been properly configured and that the /etc/krb5/krb5.conf and /etc/krb5/kdc.conf files have been specified correctly.

527073 Could not set uid to '%d': %s

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

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

529096 Function: validate - %s is not executable

Description: The Zone SMF Probe Script is not executable.

Solution: Review the /opt/SUNWsczone/sczsmf/util/sczsmf_config configuration file and make sure you have specified the correct SERVICE_PROBE.

530828 Failed to disconnect from host %s and port %d.

Description: The data service fault monitor probe was trying to disconnect from the specified host/port and failed. The problem may be due to an overloaded system or other problems. If such failure is repeated, Oracle Solaris Cluster will attempt to correct the situation by either doing a restart or a failover of the data service.

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

530938 Starting NFS daemon %s.

Description: The specified NFS daemon is being started by the HA-NFS implementation.

Solution: This is an informational message. No action is needed.

532118 All the SUNW.HAStoragePlus resources that this resource depends on are not online on the local node. Skipping the checks for the existence and permissions of the start/stop/probe commands.

Description: The HAStoragePlus resources that this resource depends on are online on another node. Validation checks will be done on that other node.

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

532454 file specified in USER_ENV parameter %s does not exist

Description: 'User_env' property was set when configuring the resource. File specified in 'User_env' property does not exist or is not readable. File should be specified with fully qualified path.

Solution: Specify existing file with fully qualified file name when creating resource. If resource is already created, please update resource property 'User_env'.

532774 Function: validate - %s state is %s

Description: The referenced zone is not in the state installed, ready or running.

Solution: Make sure that the referenced zone name is configured properly. Check if you have done a zlogin -C. Make sure that the name in the appropriate config file is correct.

532776 %s has requested an immediate failover.

Description: The domain has requested an immediate failover.

Solution: None. The domain will be immediately failed over.

533824 Function: validate - %s invalid boot option [%s]

Description: The specified boot option is not allowed.

Solution: Consult the manpage of zoneadm which boot options are allowed and specify one of them.

534755 Shutdown - can't access pidfile %s of process %s

Description: The file ${pidfile} was not found. ${pidfile} is the second argument to the 'Shutdown' function. 'Shutdown' is called within the stop scripts of sge_qmaster-rs and sge_schedd-rs resources.

Solution: Confirm the file schedd.pid or qmaster.pid exists. Said file should be found in the respective spool directory of the daemon in question.

536550 check_dhcp - Dhcpclient didn't retrieve any IP-number

Description: The dhcpclient could not retrieve any IP number.

Solution: None required. Informational message, an immediate failover is being requested.

539760 Error parsing URL: %s. Will shutdown the WLS using sigkill

Description: There is an error in parsing the URL needed to do a smooth shutdown. 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 Oracle service provider for assistance in diagnosing the problem.

540705 The DB probe script %s Timed out while executing

Description: 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. The Database probe script set in the extension property db_probe_script timed out while executing. The probe will not take any action till the DB is UP and the DB probe succeeds.

Solution: Make sure the DB probe (set in db_probe_script) succeeds. Once the DB is started the WLS probe will take action on the failed WLS instance.

541666 asmdg_proxy_daemon - the named pipe (%s) elapsed time (%s) is greater than 2 x proxy_probe_interval (%s)

Description: The named pipe has not been accessed for a while.

Solution: None required. The named pipe elapsed time is greater than 2 x Proxy_probe_interval. As we expect the named pipe to be accessed within the Proxy_probe_interval the named pipe will be recreated.

542099 File %s or %s is not readable: %s.

Description: The DNS binary is not accessible and executable. This may be due to the file not existing or the permissions not being set properly.

Solution: Make sure the DNS binary exists and has read and execute permission set appropriately.

544600 Reading from server timed out: server %s port %d

Description: While reading the response from a request sent to the server the probe timeout ran out.

Solution: Check that the server is functioning correctly and if the resources probe timeout is set too low.

547145 Initialization error. Fault Monitor username is NULL

Description: Internal error. Environment variable SYBASE_MONITOR_USER not set before invoking fault monitor.

Solution: Report this problem to your authorized Oracle service provider.

547444 Oracle Grid Infrastructure type sun.storage_proxy.type is not a cluster_resource.

Description: The Oracle Grid Infrastructure type sun.storage_proxy.type is not a cluster_resource.

Solution: You must create the Oracle Grid Infrastructure type sun.storage_proxy.type as a cluster_resource. Refer to the Oracle Solaris Cluster documentation for information on how to do this.

547574 The LDom Manager is running in configuration mode.

Description: Self explanatory.

Solution: Ensure that the resource is configured in control domain.

547918 Invalid failure policy "%s" for %s domain.

Description: Incorrect failure-policy setting for the domain.

Solution: Ensure that the failure-policy for the domain is set to "reset" on the control domain.

548103 dismount_unconnected_asm_diskgroup - Oracle ASM instance (%s) failed to dismount (%s)

Description: The Oracle ASM diskgroup failed to dismount.

Solution: None required. Informational message.

548162 Error (%s) when reading standard property <%s>.

Description: This is an internal error. Program failed to read a standard property of the resource.

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

548237 Validation failed. Connect string contains 'sa' password.

Description: The 'Connect_String' extension property used for fault monitoring uses 'sa' as the account password combination. This is a security risk, because the extension properties are accessible by everyone.

Solution: Check the resource configuration and the value of the 'Connect_string'. property. Ensure that a dedicated account (with minimal privileges) is created for fault monitoring purposes.

548445 Failed to refresh %s after property update.

Description: The Solaris service management facility failed to refresh the service instance that the fault management resource identifier (FMRI) in the /var/adm/messages specifies.

Solution: Run the command 'svcadm refresh <fmri>' to refresh the service instance. Then run the command 'svcs -x <service>' to verify that the service is online. If the problem persists, contact your Oracle Support representative for further assistance.

548673 Validation failed. CHECK_INTERVAL=0 is not allowed when Oracle Solaris Cluster is managing database %s

Description: Attribute CHECK_INTERVAL has been set to 0.

Solution: Setting CHECK_INTERVAL=0 for the database resource is now allowed when Oracle Solaris Cluster is also managing the database. Modify the database resource so that at least CHECK_INTERVAL=1 is set.

548838 Deletion of Admin customization for FMRI %s Failed %s

Description: An attempt to delete the Admin customization for the service has failed.

548977 Function: clear_zone - Killing processes with fuser -cs 15 on the file system %s

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

Solution: None.

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

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

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

549190 Text server successfully started.

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

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

550126 Validate - The tftp testfile (%s) don't exist in directory (%s) or has filesize of zero bytes

Description: The file specified in TFTPTESTFILE= within /opt/SUNWscdhc/util/dhcp_config doesn't exist or has a zero length witihin /etc/inet/inetd.conf.

Solution: If TFTPTESTFILE= is required, then ensure file specified is correct.

550803 validate_asm - Deployment of resource type %s not allowed when CRS is not deployed

Description: CRS is not deployed or running and contradicts the deployment of resource type SUNW.scalable_asm_instance_proxy.

Solution: Determine if CRS should be deployed and running. If CRS is required then SUNW.scalable_asm_instance_proxy should be deployed. If CRS is not required then SUNW.scalable_asm_instance should be deployed.

551285 %s not mounted, exiting

Description: The /usr/lib/krb5 path is not accessible.

Solution: Check this path and determine if /usr needs to be mounted.

551569 asmdg_proxy_daemon_write_pipe - the named pipe (%s) does not exist

Description: The named pipe does not exist.

Solution: None required. The named pipe will be recreated.

551893 Function: val_parfile - File %s does not exist

Description: The parameter file does not exist in the parameter file directory.

Solution: Restore the parameter file or re-register the resource.

552067 Waiting for Kerberos daemons to startup.

Description: Waiting for both the krb5kdc and kadmind daemons to start successfully under PMF.

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

553590 User id %d not found in file %s.

Description: The program failed to locate a valid entry in /etc/passwd for the specified user ID.

Solution: Please verify that the specified user ID is valid. For Oracle, the specified user ID is obtained from the owner of the file $ORACLE_HOME/bin/oracle. Also ensure that both the Oracle user and dba group are declared locally in the /etc/passwd and /etc/group files.

554202 %s/bin/srvctl is either not found or not executable.

Description: ${ORACLE_HOME}/bin/srvctl is either not found or not executable.

556039 Validation failed. ORACLE_HOME/bin/srvctl not found ORACLE_HOME=%s

Description: The SUNW.scalable_rac_server_proxy agent could not find the srvctl binary in the indicated ORACLE_HOME/bin directory.

Solution: Check whether the $ORACLE_HOME/bin directory is accessible, and if so, whether the srvctl binary exists. If the problem persists, contact your Oracle support representative for further assistance.

556800 Validation failed. Resource Group %s containing the Proxy Resource %s should have a strong positive affinity on the Resource Group %s containing an offline restart dependee resource %s.

Description: One or more resources that you are specifying as an offline restart dependee of the proxy resource does not belong to a resource group on which the resource group containing the proxy resource has a strong positive affinity.

Solution: Modify the resource group containing the proxy resource to have a strong positive affinity on the dependee resource's resource group.

556945 No permission for owner to execute %s.

Description: The specified path does not have the correct permissions as expected by a program.

Solution: Set the permissions for the file so that it is readable and executable by the owner.

557249 Invalid Migration_type=%s.

Description: Invalid Migration_type specified.

Solution: Delete and reregister the resource with a valid Migration_type entry.

558350 Validation failed. Connect string is incomplete.

Description: The 'Connect_String' extension property used for fault monitoring has been incorrectly specified. This has the format "username/password".

Solution: Check the resource configuration and the value of the 'Connect_String' property. Ensure that there are no spaces in the 'Connect_String' specification.

558527 run_sqlplus - Oracle ASM instance (%s) SQL*Plus command timeout - (%s)

Description: The SQL*Plus command has timed-out

Solution: Increase the Start_timeout or Stop_timeout.

558763 Failed to start the WebLogic server configuredin resource %s

Description: The WebLogic Server configured in the resource could not be started by the agent.

Solution: Try to start the Weblogic Server manually and check if it can be started manually. Make sure the logical host is UP before starting the WLS manually. If it fails to start manually then check your configuration and make sure it can be started manually before it can be started by the agent. Make sure the extension properties are correct. Make sure the port is not already in use.

559233 add_zcboot_dependency - Failed to retrieve START_DEPENDENCIES for the Oracle Grid Infrastructure ora.%s.%s.acfs resource

Description: Failed to retrieve the Oracle Grid Infrastructure ora.${dg}.${vol}.acfs resource START_DEPENDENCIES.

Solution: Determine why retrieving the ora.${dg}.${vol}.acfs resource failed. If the problem persists, contact your Oracle support representative for further assistance.

564643 Fault monitor detected error %s: %ld %s Action=%s : %s

Description: Fault monitor has detected an error. Error detected by fault monitor and action taken by fault monitor is indicated in message. This message also indicates whether the action taken is default or user-defined (custom).

Solution: None

564810 Function: validate - Zone %s has brand type %s. No SMF available, sczsmf does not work for the configured Zone.

Description: The sczsmf component does not work with zones of brand type other than "native", "solaris10" or "solaris", since they have no SMF feature implemented.

Solution: Don't configure the sczsmf component for a zone of brand type other than "native", "solaris10" or "solaris". Use the sczsh component instead.

564883 The Data base probe %s also failed. Will restart or failover the WLS only if the DB is UP

Description: 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 DB probe also failed. The probe will not take any action till the DB is UP and the DB probe succeeds.

Solution: Start the Data Base and make sure the DB probe (the script set in the db_probe_script) returns 0 for success. Once the DB is started the WLS probe will take action on the failed WLS instance.

566781 ORACLE_HOME %s does not exist

Description: Directory specified as ORACLE_HOME does not exist. ORACLE_HOME property is specified when creating Oracle_server and Oracle_listener resources.

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

567374 Failed to stop %s.

Description: Oracle Solaris Cluster failed to stop the application.

Solution: Use process monitor facility (pmfadm (1M)) with -L option to retrieve all the tags that are running on the server. Identify the tag name for the application in this resource. This can be easily identified as the tag ends in the string ".svc" and contains the resource group name and the resource name. Then use pmfadm (1M) with -s option to stop the application. This problem may occur when the cluster is under load and Oracle Solaris Cluster cannot stop the application within the timeout period specified. Consider increasing the Stop_timeout property. If the error still persists, then reboot the node.

567783 %s - %s

Description: The first %s refers to the calling program, whereas the second %s represents the output produced by that program. Typically, these messages are produced by programs such as strmqm, endmqm rumqtrm etc.

Solution: No user action is required if the command was successful. Otherwise, examine the other syslog messages occurring at the same time on the same node to see if the cause of the problem can be identified.

568392 check_dhcp - Dhcpclient test timed out exeeded %s seconds

Description: The dhcpclient has exceeded it's timeout allowance.

Solution: None required. Informational message, an immediate failover is being requested.

569559 Start of %s completed successfully.

Description: The resource successfully started the application.

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

569889 Function: validate - Zonebrand for zone %s is configured as native, but the zone is configured as brand type %s.

Description: Zonebrand is set to "native". But the zone is configured as a different brand type, for example lx, according to zonecfg information.

Solution: Review the components configuration file and make sure the variable Zonebrand defines the actual zone brand type for the Zone.

570525 Stopping startup script initiated by agent.

Description: The agent is attempting to stop a previous instance startup instruction that was issued to it.

Solution: None required. Informational message.

571734 Validation failed. ORACLE_SID is not set

Description: ORACLE_SID property for the resource is not set. HA-Oracle will not be able to manage Oracle server if ORACLE_SID is incorrect.

Solution: Specify correct ORACLE_SID when creating resource. If resource is already created, please update resource property 'ORACLE_SID'.

571825 Stopping listener %s.

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

Solution: None

572885 Pathprefix %s for resource group %s is not readable: %s.

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

Solution: This could happen if the filesystem on which the Pathprefix directory resides is not available. Use the HAStorage resource in the resource group to make sure that HA-NFS methods have access to the file system at the time when they are launched. Check to see if the pathname is correct and correct it if not so. HA-NFS would attempt to recover from this situation by failing over to some other node.

575279 add_zcboot_dependency - SUNW.wait_zc_boot resource is not configured for zone cluster %s in the global zone

Description: SUNW.wait_zc_boot resource is not configured for zone cluster

Solution: Configure a SUNW.wait_zc_boot resource with ZCName set to the zone cluster assistance.

577088 Waiting for WLS to startup

Description: This is just a informational message that the WLS is still starting up.

Solution: None

577130 Failed to retrieve network configuration: %s.

Description: Attempt to get network configuration failed. The precise error strings is included with the message.

Solution: Check to make sure that the /etc/netconfig file on the system is not corrupted and it has entries for tcp and udp. Additionally, make sure that the system has enough resources (particularly memory). HA-NFS would attempt to recover from this failure by failing over to another node, by crashing the current node, if this error occurs during STOP or POSTNET_STOP method execution.

577405 mountd daemon is dead. It will not be restarted as Failover_mode is set to LOG_ONLY.

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

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

577828 Failed to delete domain %s on this node.

Description: The /usr/sbin/xm delete command failed.

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

578842 validate_asm - Deployment of resource type %s not allowed when CRS is deployed

Description: CRS is deployed and running and contradicts the deployment of resource type SUNW.scalable_asm_instance.

579193 validate: User is set as root in %s. But Tomcat is not installed as root.

Description: The Tomcat software must be installed as root user only

Solution: Make sure the Tomcat software is installed as root and root writable only.

581413 Daemon %s is not running.

Description: HA-NFS fault monitor checks the health of statd, lockd, mountd and nfsd daemons on the node. It detected that one these are not currently running.

Solution: No action. The monitor would restart these.

581898 Application failed to stay up. Start method Failure.

Description: The Application failed to stay start up.

Solution: Look in /var/adm/messages for the cause of failure. Try to start the Weblogic Server manually and check if it can be started manually. Make sure the logical host is UP before starting the DAS manually. If it fails to start manually then check your configuration and make sure it can be started manually before it can be started by the agent. Make sure the extension properties are correct. Make sure the port is not already in use. Save a copy of the /var/adm/messages files on all nodes. Contact your authorized Oracle service provider for assistance in diagnosing the problem.

582067 stop_asmproxy - PMF managed asmproxy daemon for Oracle ASM instance (%s) failed to stop - %s

Description: Failed to kill The Oracle ASM instance.

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

582353 Adaptive server shutdown with wait failed. STOP_FILE %s.

Description: The Sybase adaptive server failed to shutdown with the wait option using the file specified in the STOP_FILE property.

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

582418 Validation failed. SYBASE ASE startserver file not found SYBASE=%s.

Description: The Sybase Adaptive server is started by execution of the "startserver" file. This file is missing. The SYBASE directory is specified as a part of this error message.

Solution: Verify the Sybase installation including the existence and proper permissions of the "startserver" file in the $SYBASE/$SYBASE_ASE/install directory.

582789 Function: check_sczbt - %s runlevel [%s] not online, runlevel is %s, try again in 5 seconds

Description: The runlevel is not equal to the configured LXrunlevel. The state is checked again in 5 seconds.

Solution: None.

583147 scf_service_create failed: %s

Description: An API call failed.

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

583224 Rebooting this node because daemon %s is not running.

Description: The rpcbind daemon on this node is not running.

Solution: No action. Fault monitor would reboot the node. Also see message id 804791.

584207 Stopping %s.

Description: Oracle Solaris Cluster is stopping the specified application.

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

584425 Validation failed. CRS_HOME/bin/crs_start not found CRS_HOME=%s

Description: The SUNW.scalable_rac_server_proxy agent could not find the crs_start binary in the indicated $CRS_HOME/bin/ directory.

Solution: Check whether the $CRS_HOME/bin/ directory is accessible, and if so, whether the crs_start binary exists. If the problem persists, contact your Oracle support representative for further assistance.

585295 Validate - getservbyname file does not exist or is not executable at %s/getservbyname

Description: The file 'getservbyname' can not be found, or is not executable.

Solution: Confirm the file '${SGE_ROOT}/utilbin/<arch>/getservbyname' both exists in that location, and is executable.

586101 validate_asm - Oracle ASM ORACLE_SID (%s) does not match the Oracle ASM configuration ORACLE_SID (%s) within CRS

Description: The Oracle ASM ORACLE_SID is incorrect.

Solution: The Oracle ASM ORACLE_SID that was used when registering or updating the resource of type SUNW.scalable_asm_instance_proxy does not match the Oracle ASM configuration within CRS. Specify the correct value for ORACLE_SID when registering or updating the resource.

586552 validate_asm_crs_dependency - The clustered Oracle ASM instance resource (%s) requires that a CRS resource is created first

Description: The clustered Oracle ASM instance resource requires an offline restart dependency against a CRS resource, however no such resource exists.

Solution: Ensure that a resource using type SUNW.crs_framework is created before creating a clustered Oracle ASM instance resource.

587554 Function: validate - Syntax errors in %s

Description: The parameter file is not a valid shell script.

Solution: Correct the parameter file. It must pass ksh -n <file name>.

588716 validate_asm - CRS_HOME %s either does not exist or is not a directory

Description: ${CRS_HOME} either does not exist or is not a directory.

Solution: Ensure that ${CRS_HOME} represents the directory where the Oracle Clusterware files are installed.

589373 scha_control RESOURCE_RESTART failed with error code: %s

Description: Fault monitor had detected problems in Oracle listener. Attempt to switchover resource to another node failed. Error returned by API call scha_control is indicated in the message. If problem persists, fault monitor will make another attempt to restart the listener.

Solution: Check Oracle listener setup. Please make sure that Listener_name specified in the resource property is configured in listener.ora file. Check 'Host' property of listener in listener.ora file. Examine log file and syslog messages for additional information.

589805 Fault monitor probe response times are back below 50%% of probe timeout. The timeout will be reduced to it's configured value

Description: The resource's probe timeout had been previously increased by 10% because of slow response, but the time taken for the last fault monitor probe to complete, and the avarege probe time, are both now less than 50% of the timeout. The probe timeout will therefore be reduced to it's configured value.

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

590700 ALERT_LOG_FILE %s doesn't exist

Description: File specified in resource property 'Alert_log_file' does no exist. HA-Oracle requires correct Alert Log file for fault monitoring.

Solution: Check 'Alert_log_file' property of the resource. Specify correct Oracle Alert Log file when creating resource. If resource is already created, please update resource property Alert_log_file'.

593712 ORACLE_SID extension property must match the ORACLE_SID environment variable setting for Oracle.

Description: The value of the ORACLE_SID extension property should be a valid value, that is identical to the value of the ORACLE_SID environment variable set before starting up the Oracle database.

Solution: In order to bring the resource online, set the value of the ORACLE_SID extension property of the Oracle Solaris Cluster resource to the value for that Oracle instance using appropriate Oracle Solaris Cluster commands and retry bringing the resource online.

593855 Custom monitor actions found in %s. These will override the default actions.

Description: This message indicates that a custom monitor action file has been configured. The entries in this file will determine the actual action that is taken for the specified errors. In case any error is specified in both, the custom and the default action files, the action specified in the custom action file will be chosen.

Solution: None.

595077 Error in hasp_check. Validation failed.

Description: Internal error occured in hasp_check.

Solution: Check the errors logged in the syslog messages by hasp_check. Please verify existance of /usr/cluster/bin/hasp_check binary. Please report this problem.

595926 Stopping Adaptive server with nowait option.

Description: The Oracle Solaris Cluster HA for Sybase will retry the shutdown using the nowait option.

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

596001 The fault monitor will not be restarted

Description: Fault Monitor will not be restarted when resource is configured to indicate Database role transition.

Solution: None required. Informational message.

598115 Ignoring invalid expression <%s> in custom action file.

Description: This is an informational message indicating that an entry with an invalid expression was found in the custom action file and will be ignored.

Solution: Remove the invalid entry from the custom action file or correct it to be a valid regular expression.

598587 get_property - failed to retrieve extension property %s

Description: Failed to retrieve extension property.

Solution: Check the syslog for further messages.

598973 set_scproxy_resource - Multiple Oracle ASM disk groups [%s] cannot be dependent on the same SUNW.ScalDeviceGroup resource %s

Description: Only one Oracle ASM disk group can be specified when a SUNW.ScalDeviceGroup resource is specified within resource_dependency_offline_restart.

Solution: Specify only one Oracle ASM disk group when a SUNW.ScalDeviceGroup resource is specified within resource_dependency_offline_restart. Create another Oracle Solaris Cluster resource of type SUNW.scalable_asm_diskgroup_proxy if additional Oracle ASM disk groups are required.

599371 Failed to stop the WebLogic server smoothly.Will try killing the process using sigkill

Description: The Smooth shutdown of the WLS failed. The WLS stop method however will go ahead and kill the WLS process.

Solution: Check the WLS logs for more details. Check the /var/adm/messages and the syslogs for more details to fix the problem.

599430 Failed to retrieve the resource property %s: %s.

Description: An API operation has failed while retrieving the resource property. Low memory or API call failure might be the reasons.

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

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