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.
1110 |
ERROR: TUXDIR environment variable not set | |
|
Description |
The |
Action |
Set the | |
See Also |
| |
1111 |
ERROR: Could not allocate internal TPINIT typed buffer | |
|
Description |
During shutdown, memory could not be allocated for an internal data structure. |
Action |
Remove processes that may be tying up physical memory, ensure that the application ipc key is correct, or verify that the UNIX | |
1112 |
ERROR: Could not find entry for user | |
|
Description |
Retrieving user information from the |
Action |
Validate your login and contact your System Administrator. | |
1113 |
ERROR: Must be the administrator to execute this command | |
|
Description |
A user other than root or the system administrator for the application is making a boot or shutdown request. |
Action |
The user must be the system administrator (or root) to issue these commands. | |
See Also |
| |
1126 |
WARN: Can't shutdown servers, Memory allocation failure | |
|
Description |
Space cannot be allocated to hold server group information used in the shutdown procedure. |
Action |
Kill extraneous processes and resubmit | |
See Also |
| |
1130 |
ERROR: Argument arg_value to option -e is not numeric | |
|
Description |
The |
Action |
Correct the arguments to the | |
See Also |
| |
1133 |
ERROR: Cannot determine authentication level | |
|
Description |
The |
Action |
Attempt to determine why the | |
See Also |
| |
1134 |
ERROR: Unable to get user id | |
|
Description |
The |
Action |
Have the UNIX System administrator correct any problems related to the entry of the user invoking | |
See Also |
| |
1135 |
ERROR: Unable to obtain application password | |
|
Description |
The |
Action |
If the | |
See Also |
| |
1138 |
ERROR: Can't process a message with an unknown release, relnum | |
|
Description |
The BEA TUXEDO system provides a means for converting a message from one release to another. It will convert messages from a previous release to the current one and vice versa. For example, BEA TUXEDO system Release 4.1.x will interoperate with Release 4.2.x and vice versa. The message received was not one from the current release or the previous one but from release relnum. |
Action |
Verify that the releases of the BEA TUXEDO system software installed are valid. | |
See Also |
BEA TUXEDO Administrator's Guide | |
1139 |
ERROR: Memory allocation failure, errno = errno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to allocate additional memory while attempting to create an internal table. This table was to be used for storing client information when forwarding unsolicited messages. |
Action |
Check errno_val against the error numbers in the UNIX System header file | |
1140 |
WARN: WSH (pid) should not be ignoring unsolicited messages | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process has found a Workstation handler (WSH) that will not accept unsolicited messages on behalf of its /WS clients. The process id of the WSH is pid. /WS clients connected to this WSH will not be able to receive unsolicited messages regardless of the notification method they will have selected. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1141 |
ERROR: Memory allocation failure, errno = errno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to allocate additional memory while attempting to create an internal table. This table was to be used for storing Workstation handler (WSH) information when forwarding unsolicited messages. |
Action |
Check errno_val against the error numbers in the UNIX System header file | |
1142 |
ERROR: Memory reallocation failure, errno = errno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to reallocate additional memory while attempting to increase the size of an internal table. This table was to be used for storing client information when forwarding broadcast messages. |
Action |
Check errno_val against the error numbers in the UNIX System header file | |
1143 |
ERROR: Unable to find WSH (pid) | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to locate the Workstation handler (WSH) that was going to be used to forward a broadcast messages to one or more Workstation clients. |
Action |
The | |
1144 |
ERROR: Memory reallocation failure, errno = errno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to reallocate additional memory while attempting to increase of size of an internal table. This table was to be used for storing client information when forwarding broadcast messages. |
Action |
Check errno_val against the error numbers in the UNIX System header file | |
1145 |
ERROR: Unable to send broadcast due to lack of system resources | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to forward the unsolicited message to a Workstation handler due to a blocking condition. The BBL will write this error message to the userlog and return an error. The BBL will only log this error message if several blocking conditions have occurred. Otherwise a warning message is posted in the userlog. |
Action |
The application administrator will need to determine whether there are sufficient inter-process communication (IPC) resources available on the UNIX system. The UNIX command | |
1146 |
WARN: Unable to send broadcast to WSH (pid), tperrno = tperrno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to forward the unsolicited message to a Workstation handler with a process id of pid. The BBL will write this message to the user log and attempt to send the unsolicited message to the next targeted Workstation handler, or native client. |
Action |
Check tperrno_val against the error numbers in the BEA TUXEDO system header file | |
1149 |
ERROR: Unable to send broadcast due to lack of system resources, tperrno = errno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to send the unsolicited message to a client process due to a blocking condition. The BBL will write this error message to the user log and return an error. The BBL will only return an error if several blocking conditions have occurred. Otherwise a warning message is posted in the user log. |
Action |
The application administrator will need to determine whether or not there are sufficient inter-process communication (IPC) resources available on the machine. The UNIX command | |
1150 |
WARN: Unable to send broadcast to client (pid) tperrno = errno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to send the unsolicited message to a client with a process id of pid. The BBL will write this message to the user log and attempt to send the unsolicited message to the next targeted client. |
Action |
Check tperrno_val against the error numbers in the BEA TUXEDO system header file | |
1158 |
ERROR: Unable to send unsolicited message to client (pid) | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to send the unsolicited message to a client with a process id of pid. The BBL failed due to a BEA TUXEDO system error. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1159 |
ERROR: Invalid USIGNAL parameter in Bulletin Board | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process may only send one of two signals to a Workstation handler or native client: |
Action |
The administrator of the BEA TUXEDO system application should verify that the | |
1160 |
ERROR: Unable to send signal to client, pid = pid | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to send a signal to process pid. Clients that have selected |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1161 |
ERROR: Memory allocation failure, errno = errno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to allocate additional memory while attempting to create an internal table. This table was to be used for storing Workstation handler (WSH) information when forwarding unsolicited messages. |
Action |
Check tperrno_val against the error numbers in the UNIX header file | |
1162 |
ERROR: Memory reallocation failure, errno = errno_val | |
|
Description |
The BEA TUXEDO system administrative Bulletin Board Liaison (BBL) process failed to reallocate additional memory while attempting to increase the size of an internal table. This table was to be used for storing Workstation handler information when forwarding broadcast messages. |
Action |
Check errno_val against the error numbers in the UNIX header file | |
1163 |
ERROR: invalid option - argument to -u not n, u, or j | |
|
Description |
The command option |
Action |
Re-execute the command using a valid -u argument. | |
See Also |
| |
1165 |
ERROR: Machine name must be a valid identifier. | |
|
Description |
An invalid identifier was used as a symbolic name for a machine. |
Action |
Use a valid identifier as a symbolic name for that machine. This name cannot contain a period or comma, and must be 30 characters or less. | |
See Also |
| |
1166 |
ERROR: MAXWSCLIENTS value (val) exceeds system limit (lim) for this site | |
|
Description |
|
Action |
Reset | |
See Also |
| |
1168 |
ERROR: UID is not effective user ID | |
|
Description |
The |
Action |
Verify that the effective user id of the user invoking | |
1171 |
ERROR: Memory allocation failure | |
|
Description |
The BEA TUXEDO system administrative |
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 |
| |
1175 |
WARN: *RESOURCES SYSTEM_ACCESS setting cannot be overridden in *SERVERS section | |
|
Description |
An attempt was made to override the setting of the RESOURCES section |
Action |
Check the | |
See Also |
| |
1176 |
WARN: *RESOURCES SYSTEM_ACCESS setting cannot be overridden in *SERVERS section | |
|
Description |
An attempt was made to override the setting of the RESOURCES section |
Action |
Check the | |
See Also |
| |
1178 |
ERROR: Mismatch on uid/gid from connecting bridge | |
|
Description |
A BEA TUXEDO system pre-4.2 |
Action |
Check the | |
See Also |
| |
1183 |
ERROR: Group name grpname must not contain *, comma, or colon | |
|
Description |
A group name specified starting in the first column of a line in the |
Action |
Verify that the configuration file has the proper syntax. If necessary, choose a new name for the group which meets the syntax restrictions. | |
See Also |
| |
1186 |
ERROR: Invalid setting of SYSTEM_ACCESS | |
|
Description |
An invalid value was specified for the |
Action |
Edit the configuration file to conform to the syntax guidelines and reexecute | |
See Also |
| |
1188 |
ERROR: Invalid setting of SYSTEM_ACCESS | |
|
Description |
An invalid value was specified for the |
Action |
Edit the configuration file to conform to the syntax guidelines and reexecute | |
See Also |
| |
1190 |
ERROR: Invalid setting of SYSTEM_ACCESS | |
|
Description |
An invalid value was specified for the |
Action |
Edit the configuration file to conform to the syntax guidelines and reexecute | |
See Also |
| |
1191 |
ERROR: *ROUTING entry routing_name has more than one default range | |
|
Description |
The ROUTING table entry routing_name was specified with more than one default range specification. This is not allowed. A default range specification is one which has the meta-character "*" (wild-card) in the position of a range. |
Action |
Recode the | |
See Also |
| |
1193 |
ERROR: *ROUTING entry entry_name has both numeric and character values in the RANGES statement | |
|
Description |
The ROUTING entry entry_name has both numeric and character values in the |
Action |
The values specified in the | |
See Also |
| |
1196 |
ERROR: *ROUTING entry entry_name lacks a single quote at the end of a character string or lacks a backslash to escape a double quote | |
|
Description |
The routing entry entry_name lacks a single quote at the end of a character string, or lacks a backslash to escape a double quote within a character string. |
Action |
Examine the routing field flagged as being in error. Make sure that the | |
See Also |
| |
1197 |
ERROR: or a backslash to escape a double quote. | |
|
Description |
The routing entry entry_name lacks a single quote at the end of a character string, or lacks a backslash to escape a double quote within a character string. |
Action |
Examine the routing field flagged as being in error. Make sure that the | |
1198 |
ERROR: *ROUTING entry entry_name has both numeric and character values in the RANGES statement | |
|
Description |
The ROUTING entry entry_name has both numeric and character values in the |
Action |
The values specified in the | |
See Also |
| |
1199 |
ERROR: *ROUTING entry entry_name has both numeric and character values in the RANGES statement | |
|
Description |
The ROUTING entry entry_name has both numeric and character values in the |
Action |
The values specified in the | |
See Also |
|