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.
1 |
ERROR: End time is before start time | |
|
Description |
The |
Action |
Re-run the command with correct start and end options. | |
See Also |
| |
10 |
ERROR: Name table full | |
|
Description |
Too many service names were supplied with the |
Action |
Re-run the command with fewer service names, or contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
15 |
ERROR: txrpt: bad -d arg | |
|
Description |
The |
Action |
Retry the command with a corrected | |
See Also |
| |
16 |
ERROR: txrpt: bad -d option value arg | |
|
Description |
The |
Action |
Retry the command with a corrected | |
See Also |
| |
17 |
WARN: BBL tpsvrinit: bad command line options were specified when booting the BBL | |
|
Description |
Bad command line options were specified when booting the BBL. |
Action |
Specify correct command line options for booting the BBL. | |
See Also |
| |
18 |
ERROR: BBL tpsvrinit: cannot find the DBBL entry in the Bulletin Board | |
|
Description |
In a networked application (MP mode), the BBL server initialization routine cannot find the DBBL entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space may be corrupted. |
Action |
Check if the DBBL is active. The DBBL should be booted before the BBL in a networked application. Try to shut down the application, remove IPC, and then reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
19 |
ERROR: BBL tpsvrinit: cannot update the DBBL entry in the Bulletin Board | |
|
Description |
In a networked application (MP mode), the BBL server initialization routine cannot find the DBBL entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space may be corrupted. |
Action |
Check if the DBBL is active. The DBBL should be booted before the BBL in a networked application. Try to shut down the application, remove IPC, and then reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
20 |
ERROR: BBL tpsvrinit: cannot find the BBL entry in the Bulletin Board | |
|
Description |
The BBL server initialization routine cannot find its own entry in the Bulletin Board. |
Action |
The Bulletin Board may be corrupted. Shut down the application, remove IPCs, and reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
21 |
ERROR: BBL tpsvrinit: cannot update the BBL entry in the Bulletin Board | |
|
Description |
The BBL server initialization routine cannot update its own entry in the Bulletin Board. |
Action |
The Bulletin Board may be corrupted. Shut down the application, remove IPC, then reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
22 |
ERROR: Exceeds the maximum number of times for the BBL to get a new Bulletin Board | |
|
Description |
After every interval of value in |
Action |
The Bulletin Board on the local machine may have been corrupted. System recovery attempts have failed. Contact your BEA TUXEDO system Technical Support. | |
23 |
ERROR: Administrative service request servicename handled by BBL failed - msg | |
|
Description |
A service request handled by the |
Action |
If the error is an operating system error, the | |
24 |
ERROR: The BBL could not bring down a paired bridge | |
|
Description |
Before the |
Action |
Contact your BEA TUXEDO system Technical Support. See LIBTUX_CAT message 683 for further explanation. | |
25 |
ERROR: The BBL could not bring down a paired bridge | |
|
Description |
Before the |
Action |
Contact your BEA TUXEDO system Technical Support. See LIBTUX_CAT messages 322, 323, 324, and 325 for further explanation. | |
26 |
INFO: The BBL is exiting system | |
|
Description |
The |
Action |
No action required. | |
See Also |
| |
27 |
ERROR: BBL bbclean: cannot re-attach to the Bulletin Board for recovery | |
|
Description |
After detecting that the Bulletin Board is corrupted, the |
Action |
The Bulletin Board on your machine has been corrupted, recovery attempts have failed. Contact your BEA TUXEDO system Technical Support. | |
28 |
ERROR: BBL bbclean: cannot find the DBBL entry in the Bulletin Board | |
|
Description |
The Bulletin Board cleanup process cannot find the |
Action |
Contact your BEA TUXEDO system Technical Support. See messages 18 and 19 above for further explanation. | |
29 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. | |
30 |
ERROR: BBL bbclean cannot find BBL entries in the Bulletin Board | |
|
Description |
The Bulletin Board cleanup process cannot find the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
31 |
ERROR: BBL bbclean cannot find DBBL entry in the Bulletin Board | |
|
Description |
The Bulletin Board cleanup process cannot find the |
Action |
Contact your BEA TUXEDO system Technical Support. See messages 18 and 19 in this chapter for further explanation. | |
32 |
ERROR: BBL bbclean cannot find queue entry for DBBL in the Bulletin Board | |
|
Description |
While attempting to clean up the Bulletin Board, the cleanup process was unable to find the queue entry associated with the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
33 |
ERROR: BBL bbclean cannot open Bulletin Board image, filename while restarting the DBBL | |
|
Description |
While attempting to restart the |
Action |
Check and clean up space in either | |
34 |
ERROR: BBL bbclean cannot write the Bulletin Board for restarting the DBBL | |
|
Description |
While attempting to restart the |
Action |
Check free space and file permissions either in | |
36 |
ERROR: BBL bbclean attempting to restart the DBBL failed | |
|
Description |
The cleanup process attempting to restart the |
Action |
Check the remote connection and the | |
37 |
WARN: BBL received stray reply from the BBL's reply queue | |
|
Description |
A stray reply message has appeared on the |
Action |
No action required. | |
38 |
ERROR: BBL requested service service failed - errmsg | |
|
Description |
The requested service handled by the |
Action |
Check the userlog for additional messages on the failure. | |
39 |
ERROR: BBL cannot find the DBBL | |
|
Description |
While the |
Action |
Check for a partitioned network or corrupted shared memory, or contact your BEA TUXEDO system Technical Support. | |
40 |
WARN: BBL found an unexpected transaction state trans_state | |
|
Description |
While the |
Action |
No action required. However, the local groups participating in the transaction are notified. If the transaction is already decided, they are sent a commit request. Otherwise, an abort, timeout, or status request is sent to the | |
41 |
WARN: BBL found unexpected flag flagval in the message | |
|
Description |
While the |
Action |
No action required. | |
42 |
WARN: BBL failed to wake up the blocking process - pid | |
|
Description |
After checking for transaction timeout, the |
Action |
No action required. | |
43 |
WARN: SIGTERM was ignored while shutting down the BBL | |
|
Description |
The |
Action |
See | |
See Also |
| |
44 |
ERROR: Must have a RESOURCES section | |
|
Description |
The |
Action |
Add the RESOURCES section with appropriate values to the | |
See Also |
| |
45 |
ERROR: Must have a MACHINES section | |
|
Description |
The |
Action |
Add the MACHINES section with appropriate values to the | |
See Also |
| |
46 |
WARN: Missing GROUPS section | |
|
Description |
The GROUPS section is missing in the |
Action |
No action required if the groups will later be added via | |
See Also |
| |
47 |
WARN: Missing SERVERS section | |
|
Description |
The SERVERS section is missing in the |
Action |
No action required if the servers will later be added via | |
See Also |
| |
48 |
WARN: Missing SERVICES section | |
|
Description |
The SERVICES section is missing in the |
Action |
No action required if the services will later be added via | |
See Also |
| |
49 |
WARN: Missing NETWORK section | |
|
Description |
The NETWORK section is missing in the |
Action |
No action required if the network configuration will later be added via | |
See Also |
| |
50 |
ERROR: Multiple machines cannot be configured for SHM mode | |
|
Description |
The option of |
Action |
Either | |
See Also |
| |
51 |
ERROR: MIGRATE option cannot be used with SHM mode | |
|
Description |
The |
Action |
Either the | |
See Also |
| |
53 |
ERROR: Can't have duplicate RESOURCES section | |
|
Description |
There are multiple RESOURCES sections defined in the |
Action |
Remove the extraneous RESOURCES section from the | |
See Also |
| |
54 |
ERROR: IPCKEY must be specified in RESOURCES section | |
|
Description |
The |
Action |
Set the | |
See Also |
| |
55 |
ERROR: MASTER must be specified in RESOURCES section | |
|
Description |
The |
Action |
Set the | |
See Also |
| |
56 |
ERROR: MODEL must be specified in RESOURCES section | |
|
Description |
The |
Action |
Set the | |
See Also |
| |
58 |
ERROR: MODEL must be MP for LAN option | |
|
Description |
The |
Action |
If the | |
See Also |
| |
59 |
ERROR: SCANUNIT (number) must be a multiple of 5, > 0 and <= 60 | |
|
Description |
The value for the |
Action |
Set the | |
60 |
ERROR: SCANUNIT (value) must be a multiple of 2 or 5, > 0 and <= 60 | |
|
Description |
|
Action |
| |
65 |
ERROR: Identifier string must be <= len characters in length | |
|
Description |
The identifier specified has a value that is greater than the specified maximum number of characters in length. |
Action |
Correct the length of the value of the identifier in the | |
See Also |
| |
67 |
ERROR: String string - must be <= len characters in length | |
|
Description |
The string specified has a length that is greater than the specified maximum number of characters. |
Action |
Correct the string in the | |
See Also |
| |
70 |
ERROR: Identifier for MASTER must be <= len characters in length | |
|
Description |
The identifier specified for |
Action |
Correct the value for | |
See Also |
| |
72 |
ERROR: Identifier for MASTER must be <= len characters in length | |
|
Description |
The identifier specified for |
Action |
Correct the value for | |
See Also |
| |
73 |
ERROR: Invalid MASTER parameter - duplicate LMID lmidname specified | |
|
Description |
A comma-separated pair of logical machine names was specified for the |
Action |
Correct the | |
See Also |
| |
76 |
ERROR: UID is not effective user ID | |
|
Description |
The value for |
Action |
Change the | |
See Also |
| |
79 |
ERROR: GID is not effective group ID | |
|
Description |
The value for |
Action |
Change the | |
See Also |
| |
81 |
ERROR: PERM parameter must be >= 1 and <= 0777 | |
|
Description |
The value for |
Action |
Correct the value for | |
See Also |
| |
83 |
ERROR: MAXACCESSERS parameter must be > 0 and < 32768 | |
|
Description |
The value for |
Action |
Correct the value for | |
See Also |
| |
85 |
ERROR: MAXSERVERS parameter must be > 0 and < 8192 | |
|
Description |
The value for |
Action |
Correct the value for | |
See Also |
| |
87 |
ERROR: MAXSERVICES parameter must be > 0 and < 32767 | |
|
Description |
The value for |
Action |
Correct the value for | |
See Also |
| |
89 |
ERROR: MAXGTT parameter must be >= 0 and < 32768 | |
|
Description |
The value for |
Action |
Correct the value for | |
See Also |
| |
91 |
ERROR: MAXBUFTYPE parameter must be > 0 and < 32768 | |
|
Description |
The value for |
Action |
Correct the value for | |
93 |
ERROR: MAXBUFSUBTYPE parameter must be > 0 and < 32768 | |
|
Description |
The value for |
Action |
Correct the value for | |
See Also |
| |
95 |
ERROR: Identifier for TAGENT must be <= len characters in length | |
|
Description |
The identifier specified for |
Action |
Correct the value for | |
See Also |
| |
96 |
ERROR: Can't have duplicate MACHINES section | |
|
Description |
There are multiple MACHINES sections defined in the |
Action |
Remove the extraneous MACHINES section from the | |
See Also |
| |
97 |
ERROR: RESOURCES section must appear before MACHINES section | |
|
Description |
The MACHINES section was put before the RESOURCES section in the |
Action |
Correct the | |
See Also |
| |
98 |
ERROR: lmidname specified in MASTER, but not defined in MACHINES section | |
|
Description |
The identified machine was specified as the primary value of |
Action |
Add the identified machine to the MACHINES section of the | |
See Also |
| |
99 |
ERROR: lmidname specified in MASTER, but not defined in MACHINES section | |
|
Description |
The identified machine was specified as the alternate value of |
Action |
Add the identified machine to the MACHINES section of the | |
See Also |
|