Message IDs 900000–999999

900198 validate: Port is not set but it is required

Description:

The parameter Port is not set in the parameter file

Solution:

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

914529 ERROR: probe_mysql Option -L not set

Description:

The -L option is missing for probe_mysql command.

Solution:

Add the -L option for probe_mysql command.

916067 validate: Directory $Directoryname does not exist but it is required

Description:

The directory with the name $Directoryname does not exist

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.

924002 check_samba - Samba server <%s> not working, failed to connect to samba-resource <%s>

Description:

The Samba resource's fault monitor checks that the Samba server is working by using the smbclient program. However this test failed to connect to the Samba server.

Solution:

None, the Samba server will be restarted. However, 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.

924059 Validate - MySQL database directory %s does not exist

Description:

The defined database directory (-D option) doesn't exist.

Solution:

Make sure that defined database directory exists.

930535 Ignoring string with misplaced quotes in the entry for %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 VALUE may be a single-quoted or double-quoted string. The string itself may not contain any quotes.

Solution:

Please check the environment file and correct the syntax errors.

932026 WebSphere MQ Broker RDBMS has been restarted

Description:

The WebSphere MQ Broker fault monitor has detected that the WebSphere MQ Broker RDBMS has been restarted.

Solution:

None. The resource group will be restarted.

935470 validate: EnvScript not set but it is required

Description:

The parameter EnvScript is not set in the parameter file

Solution:

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

939576 WebSphere MQ bipservice UserNameServer failed

Description:

The WebSphere MQ UserNameServer fault monitor has detected that the WebSphere MQ UserNameServer bipservice process has failed.

Solution:

None, the WebSphere MQ UserNameServer will be restarted.

942855 check_mysql - Couldn't do show tables for defined database %s (%s)

Description:

The fault monitor can't issue show tables for the specified 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.

944096 Validate - This version of MySQL <%s> is not supported with this dataservice

Description:

An unsupported MySQL version is being used.

Solution:

Make sure that supported MySQL version is being used.

947882 WebSphere MQ Queue Manager not available - will try later

Description:

Some WebSphere MQ processes are start dependent on the WebSphere MQ Queue Manger, however the WebSphere MQ Queue Manager is not available.

Solution:

None. The resource will try again and gets restarted.

957505 Validate - WebSphere MQ Broker /var/mqsi/locks is not a symbolic link

Description:

The WebSphere MQ Broker failed to validate that /var/mqsi/locks is a symbolic link.

Solution:

Ensure that /var/mqsi/locks is a symbolic link. Please refer to the data service documentation to determine how to do this.

978736 ERROR: stop_mysql Option -B not set

Description:

The -B option is missing for stop_mysql command.

Solution:

Add the -B option for stop_mysql command.

980162 ERROR: start_mysql Option -F not set

Description:

The -F option is missing for start_mysql command.

Solution:

Add the -F option for start_mysql command.

983530 can not find alliance_init in ~ALL_ADM for instance $INST_NAME

Description:

Configuration error in configuration file.

Solution:

Verify and correct SAA configuration file.

986150 check_mysql - Sql-command %s returned error (%s)

Description:

The fault monitor can't execute the specified SQL command.

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.

992415 Validate - Couldn't retrieve MySQL-user <%s> from the nameservice

Description:

Couldn't retrieve the defined user from name service.

Solution:

Make sure that the right user is defined or the user exists. Use getent passwd 'username' to verify that defined user exist.

995331 start_broker - Waiting for WebSphere MQ Broker Queue Manager

Description:

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

Solution:

None.

996303 Validate - winbindd %s non-existent executable

Description:

The Winbind resource failed to validate that the winbindd program exists and is executable.

Solution:

Check that the correct bin directory for the winbindd program was entered when registering the winbind resource. Please refer to the data service documentation to determine how to do this.