Oracle Tuxedo 10g Release 3 (10.3) System Message CMDTUX Catalog

Messages

Oracle Tuxedo System Messages provide the following information:

Description: The meaning and context of the message.

Action: What steps you can take to correct any problems identified.

See Also: A pointer to related information (not specified for all messages).

The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.

Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.

905	ERROR: Memory allocation failure
	Description	While executing `tmloadcf`, an attempt dynamically to allocate memory from the operating system using `malloc()` failed while parsing the `UBBCONFIG` file.
	Action	Ensure 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.
	See Also	`tmloadcf`(1)
906	ERROR: Memory allocation failure
	Description	While executing `tmloadcf`, an attempt dynamically to allocate memory from the operating system using `malloc()` failed while parsing the `UBBCONFIG` file.
	Action	Ensure 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.
	See Also	`tmloadcf`(1)
908	*ERROR: Can't read MACHINES section**
	Description	During the `tmshutdown` process, the MACHINES section of the configuration file could not be read.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, or that `TUXCONFIG` is not corrupted (try a `tmunloadcf`), or `TUXCONFIG` was propagated to all machines in the configuration.
	See Also	`tmshutdown`(1)
909	ERROR: Memory allocation failure
	Description	During the `tmshutdown` process, memory could not be allocated for a structure that holds information pertaining to the `DBBL` process.
	Action	Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX `sysgen` process sizing parameters are correct.
	See Also	`tmshutdown`(1)
910	ERROR: No DBBL exists
	Description	During the `tmshutdown` process, information pertaining to the `DBBL` in shared memory could not be located.
	Action	Ensure that the application IPC key is correct, or that no other application is using the same IPC key, or that the parameter `TUXDIR` is set correctly.
	See Also	`tmshutdown`(1)
911	ERROR: Memory allocation failure
	Description	During the `tmshutdown` process, memory could not be allocated for a structure that holds information pertaining to a `BBL` process.
	Action	Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX `sysgen` process sizing parameters are correct.
	See Also	`tmshutdown`(1)
912	ERROR: Memory allocation failure
	Description	During the `tmshutdown` process, memory could not be allocated for a structure that holds status information pertaining to the local `BRIDGE`.
	Action	Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX sysgen process sizing parameters are correct.
	See Also	`tmshutdown`(1)
913	*ERROR: Can't shutdown BBL on PE machine* causes partitioning**
	Description	During the `tmshutdown` process, a determination is made if the `BRIDGE` local to the `MASTER` can be shut down. This determination fails if remote `BBL`s are active.
	Action	Determine why remote `BBL`s are still active and use `pclean` if necessary.
	See Also	`tmshutdown`(1)
918	ERROR: Can't shutdown servers, Memory allocation failure
	Description	During the `tmshutdown` process, memory could not be allocated for a list of servers to be shut down.
	Action	Kill any processes that may be tying up physical memory, verify that the UNIX `sysgen` specification for process sizing is correct, or ensure that the application IPC key is correct.
	See Also	`tmshutdown`(1)
919	*ERROR: Can't shutdown TMS servers, error reading GROUPS section**
	Description	During the `tmshutdown` process, the GROUPS section of the configuration file could not be read.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, or that `TUXCONFIG` is not corrupted (try a `tmunloadcf`), or `TUXCONFIG` was propagated to all machines in the configuration.
	See Also	`tmshutdown`(1)
920	*ERROR: Can't shutdown servers, error reading SERVERS section**
	Description	During the `tmshutdown` process, the SERVERS section of the configuration file could not be read.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, or that `TUXCONFIG` is not corrupted (try a `tmunloadcf`), or `TUXCONFIG` was propagated to all machines in the configuration.
	See Also	`tmshutdown`(1)
922	ERROR: Memory allocation failure
	Description	During the `tmshutdown` process, memory could not be allocated for a new link in an ordered list of processes to be shut down.
	Action	Try a partial shutdown if the configuration is too big, or ensure that the UNIX `sysgen` process sizing is correct.
	See Also	`tmshutdown`(1)
924	WARN: Can't find Server Group = svrgroup Id = srvid
	Description	During the `tmshutdown` process, a search of the `BBL` for a list of server ids failed.
	Action	Check for an erroneous IPC key or corrupted shared memory (two or more applications sharing the same IPC key).
	See Also	`tmshutdown`(1)
925	*WARN: Bad Machine ID, machine_id* in bulletin board**
	Description	During the `tmshutdown` process, if an acknowledgment to an orderly shutdown message is not received from a remote process in a given time interval, the bridge on the remote machine is then asked, via a message, to send that process a software termination signal, `SIGTERM`. An invalid machine id associated with the remote process or `BRIDGE` is indicated by this message.
	Action	Check for an erroneous IPC key or corrupted shared memory (two or more applications sharing the same IPC key).
	See Also	`tmshutdown`(1)
932	INFO: System Shutdown Canceled
	Description	During the `tmshutdown` process, an interrupt was received from the user's terminal terminating the shutdown.
	Action	No action required.
	See Also	`tmshutdown`(1)
933	*INFO: Server svrgrp/srvid* not running**
	Description	During `tmshutdown -d`, an entry in the `BBL` for the indicated process could not be found. Either the process was not booted or was previously shut down.
	Action	No action required.
	See Also	`tmshutdown`(1)
934	WARN: Can't update status of Server Group grpname Id srvid
	Description	During the `tmshutdown` process, the status of the process being terminated could not be updated. Either a `BBL` lock could not be obtained, the machine id was incorrect, or the server id did not match an entry in the `BBL`.
	Action	Check for an invalid IPC key or a corrupted `BBL`.
	See Also	`tmshutdown`(1)
937	INFO: Still running
	Description	During `tmshutdown -n`, indicates that the process, administrative or server, is still active.
	Action	No action required.
	See Also	`tmshutdown`(1)
938	*WARN: Can't report BB resource usage on svrgrp/srvid* Memory allocation failure**
	Description	During `tmshutdown -n`, space for the list of system IPC resources held by each `BBL` could not be allocated.
	Action	Remove processes that are tying up physical memory, and verify that the UNIX sysgen parms for processes are sized adequately.
	See Also	`tmshutdown`(1)
939	ERROR: Failed
	Description	During the `tmshutdown` process, space for the reply to the message directing an administrative process or server to shut down could not be allocated, and the debugging option was specified, or the `-q` option was not specified. This directs the failed message to standard error.
	Action	Remove processes that are tying up physical memory, and verify that the UNIX sysgen parms for processes are sized adequately.
	See Also	`tmshutdown`(1)
940	ERROR: Memory allocation failure
	Description	During the `tmshutdown` process, space for the reply to the message directing an administrative process or server to shut down could not be allocated.
	Action	Remove processes that are tying up physical memory, and verify that the UNIX sysgen parms for processes are sized adequately.
	See Also	`tmshutdown`(1)
941	WARN: No active alternate LMID for migration
	Description	During `tmshutdown -R`, the system discovered that none of the alternative machine locations specified for migration were active (did not have a running BBL).
	Action	Check for a partitioned network, make sure that the migration machine or the group migration values specified in the configuration file are correct, and the corresponding `BBL`(s) are active and functioning.

942	WARN: Can't shutdown server
	Description	During `tmshutdown -q`, the shutdown message send to a server failed. Either the receiving process is dead, no acknowledgment to the send was received, or the send itself failed.
	Action	Check for a partitioned network or a dead server on the remote `PE`.
	See Also	`tmshutdown`(1)
943	*INFO: Server (svrgrp/srvid) was shutdown for migration*
	Description	During the `tmshutdown` process, the shutdown message send to a server failed because it had migrated or was in the process of migrating.
	Action	No action required.
	See Also	`tmshutdown`(1)
944	*WARN: Can't shutdown server (svrgrp/srvid)*
	Description	During `tmshutdown -q`, the shutdown message send to a server failed. Either the receiving process is dead, no acknowledgment to the send was received, or the send itself failed.
	Action	Check for a partitioned network or a dead server on the remote `PE`.
	See Also	`tmshutdown`(1)
945	WARN: Server was shutdown for migration
	Description	During the `tmshutdown` process, the reply to the shutdown message sent to a server on a remote machine was not received in a specified time interval, nor was it in the process of migrating.
	Action	Check for a partitioned network or a dead server on the remote `PE`.
	See Also	`tmshutdown`(1)
946	*INFO: Server (svrgrp/srvid) was shutdown for migration*
	Description	During the `tmshutdown` process, the reply to the shutdown message sent to a server on a remote machine was not received in a specified time interval. The server was shut down during a prior migration, or is in the process of shutting down from a recent migration request.
	Action	No action required.
	See Also	`tmshutdown`(1)
947	*WARN: Can't shutdown server (svrgrp/srvid)*
	Description	During `tmshutdown -q`, the reply to the shutdown message sent to a process on a remote machine was not received in a specified time interval. Another possibility is that the server died; shutdown of an inactive server causes a warning message.
	Action	Check for network partition and resubmit `tmshutdown`, or do `kill -9` on the remote machine and clean up IPC resources.
	See Also	`tmshutdown`(1)
949	WARN: Shutdown failed
	Description	During the `tmshutdown` process, the message sent to a process on a remote machine, telling the process to stop in an orderly fashion, returned with a failure indication.
	Action	Resubmit `tmshutdown`, or do `kill -9` on the remote machine and clean up IPC resources.
	See Also	`tmshutdown`(1)
950	*INFO: BB resources on grpname* not removed**
	Description	During `tmshutdown -n`, the system resource information associated with a Bulletin Board is displayed but not removed. Examples of system resource information are shared memory and semaphores.
	Action	No action required.
	See Also	`tmshutdown`(1)
951	*INFO: BB resources on grpname* not removed**
	Description	During `tmshutdown -n`, the system resource information associated with a Bulletin Board is displayed but not removed. Examples of system resource information are shared memory and semaphores.
	Action	No action required.
	See Also	`tmshutdown`(1)
952	ERROR: Memory allocation failure
	Description	During the `tmshutdown`, process space could not be allocated for all of the server table entry structures associated with each `BBL` in the configuration.
	Action	Check for wrong shared memory IPC key or corrupted shared memory, or kill extraneous processes that may be tying up physical memory.
	See Also	`tmshutdown`(1)
953	ERROR: Can't find BBL's
	Description	During the `tmshutdown` process, no `BBL` server table entries were located in the Bulletin Board, or a lock could not be obtained to search the Bulletin Board.
	Action	Check for wrong shared memory IPC key or corrupted shared memory, or kill the process holding the Bulletin Board lock.
	See Also	`tmshutdown`(1)
962	ERROR: BB resources not removed
	Description	The `-n` option was specified with `tmshutdown` and the system resource information (for example, shared memory or semaphores) associated with a Bulletin Board could not be found. Either the message request for this information failed, or the message request to the `PE` returned with an indication of no such information.
	Action	Check for a partitioned network, network failure, or no application running on the remote `PE`(s).
	See Also	`tmshutdown`(1)
963	WARN: Status of BB resources unknown
	Description	The system resource information associated with a Bulletin Board could not be found during `tmshutdown`. Examples of system resource information are shared memory and semaphores. Either the message request for this information failed, or the message request to the `PE` returned with an indication of no such information.
	Action	Check for a partitioned network, network failure, or no application running on the remote `PE`(s).
	See Also	`tmshutdown`(1)
971	ERROR: Invalid option option_val
	Description	The option specified is not a valid option to the `tmunloadcf` command.
	Action	Correct the options to the `tmunloadcf` command as per the usage message.
	See Also	`tmunloadcf`(1)
973	ERROR: Invalid argument - argval
	Description	The argument specified is not a valid argument to the `tmunloadcf` command. There are no options or arguments to `tmunloadcf`.
	Action	Correct the argument to the `tmunloadcf` command as per the usage message - there are no arguments to the command.
	See Also	`tmunloadcf`(1)
976	ERROR: TUXCONFIG environment variable not set
	Description	The `TUXCONFIG` environment variable is not set. `TUXCONFIG` must be set to the path to the `UBBCONFIG` file.
	Action	Set the `TUXCONFIG` environment variable to the full path of the `UBBCONFIG` file.
	See Also	`tmunloadcf`(1)
977	ERROR: Error in reading TUXCONFIG file
	Description	An error occurred when trying to read the `TUXCONFIG` file pointed to by the `TUXCONFIG` environment variable. Surrounding messages may give more information as to the cause.
	Action	Make sure the `TUXCONFIG` file is set appropriately and the file has correct permissions. See possible surrounding messages for more information. It is possible that the `TUXCONFIG` file is corrupted.
	See Also	`tmunloadcf`(1)
978	ERROR: malloc failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc()` failed while allocating space for the entries in the `TUXCONFIG` file.
	Action	Ensure 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.
	See Also	`tmunloadcf`(1), `malloc`(3) in UNIX reference manuals
979	*ERROR: Option -d argument arg_value* not numeric**
	Description	The `-d` option to the `ud` command specifies the maximum delay time in seconds before timeout. The `-d` option requires an argument, which must be numeric. The option argument supplied was not numeric.
	Action	Correct the argument to the `ud` command so that the `-d` option has a numeric argument, and reexecute the command.
	See Also	`ud`(1)
980	ERROR: Cannot use the -d and -r options together
	Description	The `-d` and `-r` options to `ud` are mutually exclusive. The `-d` option specifies the maximum delay in receiving a reply before timeout. The `-r` option states that no reply is expected.
	Action	Change the arguments to the `ud` command so that the `-d` and `-r` options are not both specified and reexecute the command.
	See Also	`ud`(1)
981	ERROR: Cannot use the -d and -r options together
	Description	See message 980 for an explanation.
	Action	See message 980 for an explanation.
	See Also	`ud`(1)
982	*ERROR: Argument arg_value* to -s not numeric**
	Description	The `-s` option to `ud` specifies a sleep time between requests. This option requires an option argument, which must be numeric. The option argument specified by the user was not numeric.
	Action	Correct the arguments to the `ud` command so that the `-s` option has a numeric subargument, and reexecute the command.
	See Also	`ud`(1)
983	*ERROR: Argument arg_value* to -t not numeric**
	Description	The `-t` option to `ud` specifies a transaction timeout value in seconds. This option requires an option argument, which must be numeric. The option argument specified by the user was not numeric.
	Action	Correct the arguments to the `ud` command so that the `-t` option has a numeric subargument, and reexecute the command.
	See Also	`ud`(1)
984	ERROR: Can't have transaction and no reply
	Description	The user specified options to `ud` that combined the transaction mode option, `-t`, with the no reply option, `-r`. This is not allowed.
	Action	Change the arguments to the `ud` command so that the `-r` and `-t` options are not both specified and reexecute the command.
	See Also	`ud`(1)
985	ERROR: Cannot combine transaction (-t) and message delay (-d)
	Description	The user specified options to `ud` that combined the transaction mode option, `-t`, with the message delay option, `-d`. This is not allowed.
	Action	Change the arguments to the `ud` command so that the `-d` and `-t` options are not both specified and reexecute the command.
	See Also	`ud`(1)
988	ERROR: ud detected syntax error in fielded buffer #buf
	Description	One of the fielded buffers passed as input to the `ud` program has invalid syntax.
	Action	Inspect the input data to `ud` and correct any errors in the input format.
	See Also	`ud`(1)
989	ERROR: No service in FBFR
	Description	One of the input buffers to `ud` did not contain a service name.
	Action	Be sure to include a line with fieldname `SRVCNM`, a tab character, and the name of a service in every fielded buffer input to `ud`.
	See Also	`ud`(1)
991	ERROR: Can't send buffer buf
	Description	`ud` was unable to send a buffer to the requested service. It is also possible that the transaction or service timed out. A description of the particular error encountered is included in the latter half of the message.
	Action	To deal with the most common causes of error, verify that the service specified in the `ud` input buffer exists, is not a conversational service, and is available, that the service accepts FML input buffers, and that the server supports transactions if the `-t` option of ud was specified. The `tpcall`(3) manual page contains information on these and other conditions that could cause an error return from `tpacall`.
	See Also	`ud`(1), `tpcall`(3)
993	ERROR: Return packet time out
	Description	A service call request made by `ud` has timed out. This can occur either due to a transaction timeout or a blocking timeout.
	Action	Determine whether it is necessary to allocate a longer time for this transaction or service call to complete. If so, increase the time specified with the `-t` option if using transaction mode, or use the `-d` option if not running in transaction mode. Reexecute the failed request.
	See Also	`ud`(1), `tpcall`(3)
994	ERROR: Reply failure - tperrno_message
	Description	The `tpgetrply()` function was called from within `ud` to receive the response from a service request, and returned an error. A description of the particular error encountered is included in the latter part of the message.
	Action	Refer to the `tpcall`(3) manual page for information on the particular errors returned.
	See Also	`ud`(1), `tpcall`(3)
998	ERROR: Too many errors encountered, exiting
	Description	The `ud` command has encountered too many errors, and is exiting. The maximum number of allowable errors defaults to 25, and may be specified explicitly using the `-e` option.
	Action	Investigate the earlier errors reported by `ud`, and try to eliminate as many as possible. If it is an expected condition for a large number of service calls to return errors, invoke with the `-e` option to specify an explicit error limit.
	See Also	`ud`(1)