TMADMIN Messages 100-199

109

ERROR: Custom Error Message.

Description

An error has been produced in a tmadmin command. A message should have been previously printed explaining the nature of this error.

Action

Correct the parameters and retype the command.

See Also

tmadmin(1)

110

ERROR: Argument too long.

Description

This error is returned by the tmadmin command parser. The parser finds that an argument has more than the maximum 80 characters.

Action

Correct the argument and retype the command.

See Also

tmadmin(1)

111

ERROR: No such command.

Description

An unknown or invalid command has been entered to tmadmin.

Action

Correct and retype the command. You can type help if you are not sure of the commands available in tmadmin.

See Also

tmadmin(1)

112

ERROR: Invalid option.

Description

Unknown option or invalid argument given to a tmadmin command.

Action

Correct the parameters and reenter the command. A message should have been already delivered indicating the incorrect option. If you are not sure of the parameters, you can type help with the command name as argument. The help command will provide information about required or optional parameters used by the requested tmadmin command.

See Also

tmadmin(1)

113

ERROR: Too many arguments.

Description

A tmadmin command has been entered with more arguments than required, or the maximum number of 10 arguments has been exceeded.

Action

Correct the parameters and reenter the command. If you are not sure of the parameters, you can type help with the command name as argument. The help command will provide information about required or optional parameters used by the command.

114

ERROR: Duplicate arguments.

Description

A tmadmin command has been entered with duplicate parameters. The tmadmin command parser does not allow duplicate arguments.

Action

Correct the parameters and reenter the command. If you are not sure of the parameters, you can type help with the command name as argument. The help command will provide information about required or optional parameters used by the command.

115

ERROR: No bulletin board attached.

Description

A tmadmin command that requires information from the Bulletin Board has been entered. However, the machine on which tmadmin is executing does not have a Bulletin Board.

Action

Be sure that tmadmin is running on the Master machine, and then boot the application servers or the administrative servers (that is, use the boot command) on this machine or the other machines. Then reenter the tmadmin command.

See Also

tmadmin(1)

116

ERROR: Memory allocation failure.

Description

An attempt to dynamically to allocate memory from the operating system using malloc failed.

Action

Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also

malloc(3c) in a UNIX reference manual

117

ERROR: No queues exist.

Description

The selection criteria specified while trying to print queue information did not match any active queues.

Action

Change the queue specification (the identifier, server identifier, group, etc.) and re-run the operation.

See Also

tmadmin(1)

118

ERROR: No such queue.

Description

An invalid queue name has been entered as an argument to a tmadmin command.

Action

Correct the argument and reenter the command. You can use the tmadmin printqueue command to retrieve the names of the valid queues in your application.

See Also

tmadmin(1)

119

ERROR: Queue retrieval error.

Description

An error was produced while retrieving information about a queue or queues defined in the application. An error message should have been written to the ULOG file.

Action

Verify the parameters entered for the tmadmin command, and check the ULOG file for a record explaining the problem. Please refer to the corresponding error description to find the corrective action.

See Also

tmadmin(1)

120

ERROR: No servers exist.

Description

A tmadmin command has been entered requiring information about a server or servers defined in the application. However, no servers are currently defined in the TUXCONFIG file or no servers have been booted for the specified machine or group.

Action

Boot the application servers for the required group or machine, and then reenter the tmadmin command. Be sure that the expected servers have been defined in the TUXCONFIG file. You can use the tmconfig program or the config command of tmadmin to retrieve or change the configuration parameters.

See Also

tmadmin(1), tmconfig(1)

121

ERROR: No such server.

Description

An invalid server identifier has been entered as argument to a tmadmin command. This error may also be produced when no servers are currently booted for the particular group or machine.

Action

Use the tmadmin printserver command with no arguments to print the information about the current active servers. You can also use the printgroup command to find if a particular group or groups on a particular machine have been booted. You can boot servers on a particular machine or group with the boot command of tmadmin. After the servers have been booted, you can reenter the tmadmin command.

See Also

tmadmin(1)

122

ERROR: Server retrieval error.

Description

An error was produced while retrieving information about the defined servers in an application. An error message should have been written to the ULOG file.

Action

Verify the parameters entered for the tmadmin command, and check the ULOG file for a record explaining the problem. Please refer to the corresponding error description to find the corrective action.

See Also

tmadmin(1)

123

ERROR: No services exist.

Description

A tmadmin command has been entered requiring information about the different services currently advertised or defined by the application. However, no services are defined in the TUXCONFIG file, or the servers advertising these services have not been booted.

Action

Boot the application servers for the required group or machine, and then reenter the tmadmin command. Be sure that the expected servers and services have been defined in the TUXCONFIG file. You can use the tmconfig command or the tmadmin config command to retrieve or change the configuration parameters.

See Also

tmadmin(1)

124

ERROR: No such service.

Description

A tmadmin command requiring information about a particular service has been entered, but this service is not currently advertised in the Bulletin Board or the server advertising the service has not been booted.

Action

Use the tmadmin printservice command with no arguments to print the information about the current known services. You can also use the printgroup command to find if a particular group or the groups on a particular machine have been booted. You can boot a particular machine, group, or server with the tmadmin boot command. After the servers have been booted, you can reenter the tmadmin command.

See Also

tmadmin(1)

125

ERROR: Service retrieval error.

Description

An error was produced while retrieving information about a service or services advertised by an application. An error message explaining the problem should have been written to the ULOG file.

Action

Verify the parameters entered for the tmadmin command, and check the ULOG file for a record explaining the problem. Please refer to the corresponding error description to find the corrective action.

See Also

tmadmin(1)

126

ERROR: No BBL exists for that machine.

Description

A tmadmin command has been entered to display or change the Bulletin Board parameters defined for a particular machine. However, the particular machine has not been booted.

Action

You can use the tmadmin boot command to boot the administrative servers and (or) application servers on the required machine. Then you can reenter the tmadmin command to display or change the corresponding Bulletin Board parameters.

See Also

tmadmin(1), tmboot(1)

127

ERROR: Invalid combination of options.

Description

An invalid combination of arguments has been entered in a tmadmin command. For example, an invalid server identifier has been specified in combination with a group name.

Action

Correct the arguments and reenter the tmadmin command. You may use the help command to display information about the valid argument combinations for tmadmin commands.

See Also

tmadmin(1)

128

ERROR: Error suspending resources.

Description

An error occurred while retrieving statistical information or suspending a service or set of services. An error message explaining the problem should be found in the ULOG.

Action

Verify the parameters entered for the tmadmin command, and check the ULOG file for a record explaining the problem. Please refer to the corresponding error description to find the corrective action.

See Also

tmadmin(1)

129

ERROR: Group id is not set.

Description

A tmadmin command requiring an argument with a server group name has been entered without this argument.

Action

Reenter the tmadmin command with the corresponding group name argument. You can find the available groups with the tmadmin printgroup command.

See Also

tmadmin(1)

130

ERROR: Server id is not set.

Description

A tmadmin command requiring an argument with a server identifier has been entered without this argument.

Action

Reenter the tmadmin command with the corresponding server identifier argument. You can find the different servers with the printserver command.

See Also

tmadmin(1)

131

ERROR: Service name is not set.

Description

A tmadmin command requiring an argument with a service name has been entered without this argument.

Action

Reenter the tmadmin command with the corresponding service name argument. You can find the different services with the printservice command.

See Also

tmadmin(1)

132

ERROR: No such machine.

Description

An invalid machine name has been specified as argument to a tmadmin command.

Action

Correct the machine name and reenter the tmadmin command.

133

ERROR: Must be administrator to execute that command.

Description

A tmadmin command failed because it can only be executed by the administrator. The current instance of the tmadmin program is run by a user who is not the administrator.

Action

Terminate this instance of the tmadmin program; login as the administrator and start a new instance of the tmadmin program. Then re-execute the tmadmin subcommand that failed.

134

ERROR: Error resuming (un-suspending) resources.

Description

A tmadmin command that resumes suspended resources (that is, a queue, server, or service) has failed. An error message explaining the failure should be found in the ULOG file.

Action

Verify the parameters entered for the tmadmin command, and check the ULOG file for a record explaining the problem. Please refer to the error description of the ULOG message to find the corrective action.

135

INFO: Break out of main loop.

Description

The quit command has been entered. This instance of tmadmin will terminate.

Action

No action required.

138

ERROR: Command not allowed in private mode.

Description

The default command was used to reset the default machine, but tmadmin is running in private mode. The default machine cannot be reset (it must be the local machine).

Action

No action required.

See Also

tmadmin(1)

140

ERROR: No BBL exists on this machine.

Description

A tmadmin command has been entered to check the integrity of all processes running on a particular machine. However, this command failed because the machine is down or the BBL administrative process is not running.

Action

Use the tmadmin boot boot command to start the servers on the required machine or to boot the BBL administrative server. Then reenter the tmadmin command.

See Also

tmadmin(1)

141

ERROR: BBL dead on requested machine.

Description

A tmadmin command that requires the services of the BBL administrative server failed because the BBL is not running.

Action

The BBL administrative server is automatically restarted by the system. Please wait a couple of minutes and then reenter the tmadmin command.

See Also

tmadmin(1)

142

ERROR: Queue suspended for BBL on requested machine.

Description

A tmadmin command that requires the administrative services advertised by the BBL server running on the requested machine failed because these services are currently suspended, or the administrative services offered by the BBL on the requested machine are suspended because of a failure. For example, the connection to the requested machine was lost or that machine failed.

Action

Use the tmadmin resume command to resume the activity on the queue used by the BBL on the requested machine. The resume command will lift the suspension of administrative services advertised by the BBL server. If the error was due to a failure on the requested machine (or on the connection), use the reconnect command to reestablish the connection to the requested machine, or wait a couple of minutes until the system automatically recovers from the network failure.

See Also

tmadmin(1)

143

ERROR: No server is specified.

Description

A tmadmin command failed because it requires an argument with a specific server identifier and this argument was not specified.

Action

Reenter the tmadmin command with the corresponding server identifier argument.

See Also

tmadmin(1)

144

ERROR: Error retrieving service parms.

Description

An error was produced while retrieving information about the requested service parameters. An error message should have been written to the ULOG file.

Action

Verify the parameters entered for the tmadmin command, and check the ULOG file for a record explaining the problem. Please refer to the corresponding error description to find the corrective action.

See Also

tmadmin(1)

145

ERROR: Syntax error on command line.

Description

A syntax error was found in the tmadmin command. A previous message should have been printed specifying the nature of the error.

Action

Correct the arguments or syntax and reenter the tmadmin command.

See Also

tmadmin(1)

147

ERROR: Error accessing system semaphore.

Description

The BEA Tuxedo system uses an operating system semaphore to control access to structures in shared memory. An error occurred while accessing or retrieving information from the system level semaphore.

Action

You can run the tmadmin bbclean command to check the operating system resources, and then reenter the tmadmin command that failed.

See Also

tmadmin(1)

148

ERROR: Error accessing message queue.

Description

A tmadmin command failed while accessing or retrieving information from a message queue.

Action

You can run the tmadmin bbclean command to check the operating system IPC resources, and then reenter the tmadmin command that failed.

See Also

tmadmin(1)

149

ERROR: Error accessing shared memory.

Description

A tmadmin command failed while trying to access system information stored in shared memory.

Action

You can run the tmadmin bbclean command to check the operating system IPC resources, and then reenter the tmadmin command that failed.

See Also

tmadmin(1)

151

ERROR: Error dumping bulletin board.

Description

An error occurred while executing the tmadmin dump command. The error may have been produced while gathering information from the Bulletin Board (an error message may have been recorded in the ULOG file) or while the command was trying to write to the specified file.

Action

Check that you have permissions to write a file on the current directory or on the pathname specified as argument to the tmadmin command. Also, check the ULOG file for a record explaining the problem. Please refer to the corresponding error description to find the corrective action.

See Also

tmadmin(1)

154

ERROR: No resources are specified.

Description

A tmadmin suspend (or resume) command failed because no arguments have been specified. The command requires that either arguments are specified as default arguments (via the tmadmin default command) or that they are specified in the command line.

Action

Reenter the tmadmin command with the required arguments. You can use the tmadmin help command to find out what arguments are required.

See Also

tmadmin(1)

156

ERROR: Incorrect release code.

Description

While entering advanced administrator mode, the incorrect password was entered.

Action

Contact BEA Customer Support.

See Also

tmadmin(1)

158

ERROR: DBBL migration failure.

Description

The tmadmin master command failed while the DBBL was migrating to the backup machine. An error message may have been recorded in the ULOG file explaining the failure.

Action

Check the ULOG file for a log record explaining the failure, and contact BEA Customer Support.

See Also

tmadmin(1)

159

ERROR: Can not create a new DBBL.

Description

The tmadmin master command failed because it cannot start a new DBBL administrative server on the backup machine. An error record may have been recorded in the ULOG file.

Action

Check the ULOG file for an error record explaining the problem. You should also check if there is already a DBBL server running on the backup machine. Please contact BEA Customer Support for more information about how to correct the problem.

See Also

tmadmin(1)

160

ERROR: Backup node is not specified in the UBBCONFIG file.

Description

The tmadmin master command failed because there are no backup machines specified in the TUXCONFIG file for the Master node.

Action

You can use the tmconfig program or the tmadmin config command to define a backup machine for the Master machine. The tmadmin master command cannot be run for a Master machine that does not have a defined backup machine.

See Also

tmadmin(1), tmconfig(1)

161

ERROR: tmadmin is not running on acting backup node.

Description

The tmadmin master command failed because the tmadmin program is not executing on the machine that will become the Master machine.

Action

Terminate the current tmadmin session, and start a new instance of tmadmin on the backup machine. Then reenter the master command.

See Also

tmadmin(1)

162

ERROR: Can not clean up partitioned BB entries.

Description

The tmadmin pclean command failed to execute on the required machine. An error log record explaining the failure may have been recorded in the ULOG file.

Action

Check that the requested machine has been booted or that the BBL administrative is running on that machine. Also, check the ULOG file for a record explaining the failure.

See Also

tmadmin(1)

163

ERROR: Network reconnection failure.

Description

A failure occurred while tmadmin was processing a reconnect command. An error log record explaining the failure may be found in the ULOG file.

Action

Verify that the Bridge administrative process is running and check the ULOG file for a record explaining the problem. Please refer to the corresponding error description to find the corrective action.

164

ERROR: Invalid server group name.

Description

A tmadmin command failed because an invalid group name has been entered as an argument to the command.

Action

Check the tmadmin command arguments and reenter the command. You can use the printgroup command to print information about the current active groups running on a particular machine.

165

ERROR: Should not pclean the current machine.

Description

This error is returned by the tmadmin pclean command. This command cannot be executed when the application is running in SHM mode. The tmadmin pclean command is used when the application is running in MP mode to remove bulletin board entries for processes and services associated with a machine that has failed.

Action

If the application is running in SHM mode, then you should not execute the tmadmin pclean command. This command should be used in MP mode to remove from the Bulletin Board information about partitioned (or failed) machines.

See Also

tmadmin(1), "BEA Tuxedo Administrator's Guide"

166

ERROR: -z option is mandatory when FSCONFIG is not set.

Description

A tmadmin command failed because the shell environment variable FSCONFIG is not set and the -z option was not used on the command line. The FSCONFIG variable is an optional variable that should be set to the pathname of the device that contains the Universal Device List (UDL). If the FSCONFIG variable is not set, then the -z option must be used.

Action

Retype the tmadmin command with the -z option. This option has as argument the pathname of the device containing the Universal Device List (UDL).

See Also

tmadmin(1)


168


WARN: master command not performed

Description

This warning is returned by the master command of tmadmin(1). The master command was not performed because no explicit confirmation was provided. This command requires an explicit confirmation to be executed.

Action

Reexecute the master command with the -yes option if you want to make the backup node take over as the master node.

See Also

tmadmin(1)


181


ERROR: Invalid option: -W

Description

The -W option was specified without giving the correct associated argument. This is an undocumented option, used only for BEA Customer Support.

Action

Contact BEA Customer Support.

See Also

tmadmin(1)


182


ERROR: Invalid option: option

Description

tmadmin(1) has been invoked with an invalid option. The offending option is printed with this error message.

Action

Verify options to tmadmin and re-execute the command.

See Also

tmadmin(1)


183


ERROR: Invalid argument: argument

Description

tmadmin(1) has been invoked with an invalid argument. The offending option and argument are printed with this error message.

Action

Verify options to tmadmin and re-execute the command.

See Also

tmadmin(1)


184


ERROR: TUXCONFIG environment variable not set.

Description

The TUXCONFIG environment variable was not set. Because of this, the tmadmin command failed.

Action

Set the TUXCONFIG environment variable to the pathname of the TUXCONFIG file.

See Also

tmadmin(1)


186


INFO: Reattaching to regular bulletin board.

Description

A special administrative command to instantiate a saved Bulletin Board failed. The program will attached to the regular bulletin board.

Action

No action required.

See Also

tmadmin(1)


187


INFO: Reattaching to regular bulletin board.

Description

After running a special administrative command to attach to a special Bulletin Board, the BB has been released and tmadmin will re-attach to the normal BB.

Action

No action required.

See Also

tmadmin(1)


188


ERROR: Error while obtaining the Bulletin Board parameters

Description

An error was produced in tmadmin while retrieving the Bulletin Board parameters. A more specific error explaining the situation should already exist in the user log.

Action

Check the user log for a more specific error message. Check that the TUXCONFIG is readable, and re-execute the tmadmin command.

See Also

tmadmin(1), ubbconfig(5)


189


ERROR: Reinitialization after boot failed to set the Bulletin Board Model

Description

An error was produced in tmadmin while setting the Bulletin Board model. This error may occur while the system is reinitialized after a booting procedure.

Action

Check the Bulletin Board Model defined in the MODEL attribute of the RESOURCES section of the TUXCONFIG file. Valid Bulletin Board Model values are SHM and MP.

See Also

tmadmin(1), ubbconfig(5)


190


ERROR: Failure setting the Bulletin Board Model to MSG

Description

The tmadmin command failed to set the Bulletin Board to MSG. This failure can only be produced if the tmadmin program was not compiled with the system default libraries.

Action

Contact BEA Customer Support.

See Also

tmadmin(1), ubbconfig(5)


191


ERROR: Error setting the Bulleting Board Model to SHM

Description

The tmadmin command failed to set the Bulletin Board Model to SHM. This failure can only be produced if the tmadmin program was not compiled with the system default libraries.

Action

Contact BEA Customer Support.

See Also

tmadmin(1), ubbconfig(5)


192


ERROR: Error setting the Bulleting Board Model to MP

Description

The tmadmin command failed to set the Bulletin Board Model to MP. This failure can only be produced if the tmadmin program was not compiled with the system default libraries.

Action

Contact BEA Customer Support.

See Also

tmadmin(1), ubbconfig(5)


193


ERROR: Could not setup internal tables to enter boot mode.

Description

The tmadmin program is going to try to enter boot mode but it was not able to find the right internal tables or it could not attach to the Bulletin Board. In the latter case, another error message should have been recorded in the user log. If there are no messages in the user log, then tmadmin may have been compiled with the wrong libraries.

Action

Contact BEA Customer Support.

See Also

tmadmin(1)


194


ERROR: Invalid TUXCONFIG value

Description

The tmadmin program is trying to perform an automatic boot procedure, and it finds that the value of the TUXCONFIG environment variable does not match the value defined in the *MACHINES section of the TUXCONFIG configuration file.

Action

Check the value of the TUXCONFIG environment variable and re-run the tmadmin command.

See Also

tmadmin(1), ubbconfig(5)


195


ERROR: Failure to obtain the Master Machine identifier.

Description

The tmadmin program failed to obtain the master machine identifier from internal tables or the TUXCONFIG file. This error may be produced when tmadmin enters in automatic boot mode (that is, the system either is not up or is partitioned).

Action

Check that the TUXCONFIG configuration file is readable. Contact BEA Customer Support.

See Also

tmadmin(1)


196


ERROR: The boot mode is only available on the MASTER processor.

Description

This error is produced when tmadmin is run in boot mode on a machine that is not the MASTER machine.

Action

Reexecute tmadmin on the MASTER machine.

See Also

tmadmin(1)


199


WARN: Cannot become administrator.

Description

The tmadmin program was not able to enter the administrative mode. A limited set of commands is available (that is, the set of commands available when tmadmin is run with the -r option).

Action

No action required.

See Also

tmadmin(1)