806128 Ignoring PATH set in environment file %s
HA-Oracle reads the file specified in USER_ENV property and exports the variables declared in the file. If PATH variable is attempted to be set in the USER_ENV file, it gets ignored.
Solution:Please check the environment file and remove any PATH variable setting from it.
815147 Validate - Faultmonitor-resource <%s> does not exist
The Samba resource could not validate that the fault monitor resource exists.
Solution:Check that the Samba instance's smb.conf file has the fault monitor resource scmondir defined. Please refer to the data service documentation to determine how to do this.
821789 Validate - User %s is not a member of group mqbrkrs
The WebSphere MQ Broker userid is not a member of the group mqbrkrs.
Solution:Ensure that the WebSphere MQ Broker userid is a member of the group mqbrkrs.
826556 Validate - Group mqbrkrs does not exist
The WebSphere MQ Broker resource failed to validate that the group mqbrkrs exists.
Solution:Ensure that the group mqbrkrs exists.
834841 Validate - myisamchk %s non-existent or non-executable
The mysqladmin command doesn't exist or is not executable.
Solution:Make sure that MySQL is installed correctly or right base directory is defined.
835739 validate: Host is not set but it is required
The parameter Host is not set in the parameter file
Solution:Set the variable Host in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.
836825 validate: TestCmd is not set but it is required
The parameter TestCmd is not set in the parameter file
Solution:Set the variable TestCmd in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.
838688 validate: Startwait is not set but it is required
The parameter Startwait is not set in the parameter file
Solution:Set the variable Startwait in the parameter file mentioned in option -N to a of the start, stop and probe command to valid contents.
844160 ERROR: stop_mysql Option -H not set
The -H option is missing for stop_mysql command.
Solution:Add the -H option for stop_mysql command.
845276 WebSphere MQ Broker Queue Manager has been restarted
The WebSphere MQ Broker fault monitor has detected that the WebSphere MQ Broker Queue Manager has been restarted.
Solution:None. The WebSphere MQ Broker will be restarted.
845586 ERROR: start_mysql Option -L not set
The -L option is missing for start_mysql command.
Solution:Add the -L option for start_mysql command.
857002 Validate - Secure mode invalid in %s
The secure mode value for MODE is invalid.
Solution:Ensure that the secure mode value for MODE equals Y or N when registering the resource.
865963 stop_mysql - Pid is not running, let GDS stop MySQL for %s
The saved Pid didn't exist in process list.
Solution:MySQL was already down.
871438 Validate - User ID %s is not a member of group mqbrkrs
The WebSphere MQ UserNameServer userid is not a member of the group mqbrkrs.
Solution:Ensure that the WebSphere MQ UserNameServer userid is a member of the group mqbrkrs.
884759 All WebSphere MQ Broker processes stopped
The WebSphere MQ Broker has been successfully stopped.
Solution:None.
895418 stop_mysql - Failed to stop MySQL through mysqladmin for %s, send TERM signal to process
mysqladmin command failed to stop MySQL instance.
Solution:Either was MySQL already down or the fault monitor user doesn't have the right permission to stop MySQL. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges.
897653 Validate - Samba sbin directory %s does not exist
The Samba resource could not validate that Samba sbin directory exists.
Solution:Check that the correct pathname for the Samba sbin directory was entered when registering the Samba resource and that the sbin directory really exists.
898957 Validate - De-activating %s, by removing it
The DHCP resource validates that /etc/rc3.d/S34dhcp is not active and achieves this by deleting/etc/rc3.d/S34dhcp.
Solution:None, /etc/rc3.d/S34dhcp will be deleted.
899940 check_mysql - Couldn't drop table %s from database %s (%s)
The fault monitor can't drop specified table from the test database.
Solution:Either was MySQL already down or the fault monitor user doesn't have the right permission. The defined fault monitor should have Process-,Select-, Reload- and Shutdown-privileges and for MySQL 4.0.x also Super-privileges. Check also the MySQL logfiles for any other errors.