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.
700 |
ERROR: Group's current location inconsistent with TUXCONFIG file | |
|
Description |
The location of a server group was being updated in the master copy of the |
Action |
The master machine's | |
See Also |
| |
730 |
ERROR: Memory allocation failure | |
|
Description |
This error occurred while attempting to shut down a partitioned lmid and its associated servers. |
Action |
Remove processes that may be tying up physical memory, ensure that the application | |
See Also |
| |
731 |
ERROR: for debug level | |
|
Description |
A non-numeric argument was specified with the debugging option of |
Action |
Specify a numeric value for the debugging level command line option. | |
732 |
ERROR: for srvid | |
|
Description |
The argument for the |
Action |
Specify a numeric value between 1 and 30,000. | |
See Also |
| |
733 |
ERROR: for sequence number | |
|
Description |
The argument for the |
Action |
Specify a numeric value between 1 and 9,999. | |
See Also |
| |
734 |
ERROR: for delay | |
|
Description |
The argument for the |
Action |
Specify a numeric value greater than 0. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
735 |
ERROR: Memory allocation failure | |
|
Description |
This error occurred while booting the |
Action |
Remove processes that may be tying up physical memory, ensure that the application | |
See Also |
| |
737 |
ERROR: tmboot too many arguments | |
|
Description |
An argument is present that does not match the options selected for |
Action |
Resubmit after verifying the command line options. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
738 |
ERROR: -R option requires either the -g or -l option | |
|
Description |
A shutdown request with the |
Action |
Resubmit the command and specify either the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
739 |
ERROR: -A option not allowed with -R | |
|
Description |
A shutdown request with the migration option, |
Action |
Resubmit | |
See Also |
BEA TUXEDO Administrator's Guide, | |
740 |
ERROR: -S option not allowed with -R | |
|
Description |
A shutdown request with the |
Action |
Resubmit | |
See Also |
BEA TUXEDO Administrator's Guide, | |
741 |
ERROR: -B option not allowed with -R | |
|
Description |
A shutdown request with the migration, |
Action |
Resubmit | |
See Also |
BEA TUXEDO Administrator's Guide, | |
742 |
ERROR: -T option not allowed with -R | |
|
Description |
A shutdown request with the migration, |
Action |
Resubmit | |
See Also |
BEA TUXEDO Administrator's Guide, | |
743 |
ERROR: -H option not allowed with -R | |
|
Description |
A shutdown request with the migration, |
Action |
Resubmit | |
See Also |
BEA TUXEDO Administrator's Guide, | |
744 |
ERROR: -i option not allowed with -R | |
|
Description |
A shutdown request with the migration, |
Action |
Resubmit | |
See Also |
BEA TUXEDO Administrator's Guide, | |
745 |
ERROR: -o option not allowed with -R | |
|
Description |
A shutdown request with the migration, |
Action |
Resubmit | |
See Also |
BEA TUXEDO Administrator's Guide, | |
746 |
ERROR: -s option not allowed with -R | |
|
Description |
A shutdown request with the migration, |
Action |
Resubmit | |
See Also |
BEA TUXEDO Administrator's Guide, | |
754 |
ERROR: error processing configuration file | |
|
Description |
When booting or shutting down an application, |
Action |
The value of the | |
See Also |
| |
755 |
ERROR: -R option not allowed if MIGRATE not specified | |
|
Description |
A shutdown request with the |
Action |
To enable migration for an application in this situation, the application must be shut down, and the configuration must be updated to include the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
756 |
ERROR: -P option not allowed on non-partitioned node | |
|
Description |
A shutdown request with the |
Action |
To shut down servers on this lmid, the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
757 |
ERROR: Could not reset model to MP for partitioned shutdown | |
|
Description |
A BEA TUXEDO system internal value was not set correctly. Check the userlog for additional error messages to clarify this error condition. The circumstances associated with this error are not likely to be caused by something that the invoker of the |
Action |
Try repeating the same operation. If this fails with the same error, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
758 |
ERROR: Could not attach to local BB for partitioned shutdown | |
|
Description |
While trying to connect to the local bulletin board to complete the partitioned shutdown request, an error occurred in the initialization phase. There are several scenarios that may eventually cause this error, including a corrupted |
Action |
Check the userlog for error messages to clarify the problem. If the cause cannot be discerned, contact your BEA TUXEDO system Technical Support. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
759 |
ERROR: Could not bring up temp DBBL for partitioned shutdown | |
|
Description |
While trying to process a partitioned shutdown request, a temporary DBBL process must be booted. An error occurs such as running the command on a machine that is not partitioned. Or while starting the pseudo-DBBL, the original DBBL is still reachable through another bridge from the "partitioned" site. |
Action |
Determine if the machine is partitioned (by using the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
760 |
ERROR: Failed to attach to temp DBBL for partitioned shutdown | |
|
Description |
The |
Action |
Try repeating the command again. If it fails in the same manner, contact your BEA TUXEDO system Technical Support. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
761 |
ERROR: Illegal TUXCONFIG value | |
|
Description |
The value of the |
Action |
Reset the | |
See Also |
| |
762 |
ERROR: LAN mode not specified for multiple node application | |
|
Description |
The |
Action |
Change the application configuration to ensure that the | |
See Also |
| |
763 |
ERROR: cannot create internal BB tables | |
|
Description |
While booting, an application error in attaching to the shared memory has occurred. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
764 |
ERROR: can't attach to BB | |
|
Description |
While shutting down an application, an error in attaching to the configuration bulletin board has occurred. |
Action |
Check the userlog for additional diagnostic messages. Normally this error implies that the | |
See Also |
| |
765 |
ERROR: must run on master node | |
|
Description |
|
Action |
Reissue the boot or shutdown command on the proper processing element. | |
See Also |
| |
766 |
ERROR: must run on master node | |
|
Description |
A boot request is issued from the backup master node specified in the configuration. Or, the system cannot find a DBBL process in the system during a shutdown request. |
Action |
Reissue the boot request from the master specified in the configuration. If this error results from a shutdown request, make sure that there is a DBBL process running before reissuing the request. | |
See Also |
| |
767 |
ERROR: must run on master node | |
|
Description |
A shutdown request is issued from the master node specified in the configuration. However, this is no longer the active master, since the original master has been migrated. |
Action |
Reissue the shutdown request from the active master. | |
See Also |
| |
768 |
ERROR: Bad LMID (lmid) in command line option(s) | |
|
Description |
The argument lmid specified for the command line option is invalid. |
Action |
Check the configuration for the correct lmid value and reissue the command. | |
See Also |
| |
769 |
ERROR: Server group name (grpname) too long | |
|
Description |
The group name specified for the command line option is too long. The server group name must be less than or equal to 30 characters. |
Action |
Check the configuration for the correct group name and reissue the command. | |
See Also |
| |
770 |
ERROR: Invalid server group name (grpname) | |
|
Description |
The group name specified for this command is not in the configuration. |
Action |
Check the configuration for the correct group name and reissue the command. | |
See Also |
| |
771 |
ERROR: Bad command line options! Check the LOG file | |
|
Description |
An invalid command line option was specified that resulted in a fatal error. |
Action |
Check the userlog file to determine the exact cause of the error. | |
See Also |
| |
772 |
ERROR: can't get (D)BBL's table entry | |
|
Description |
While shutting down the system, a server table entry is in an inconsistent state. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
777 |
INFO: See ULOG for complete process status | |
|
Description |
This message reminds the user that there is more information available in the userlog. |
Action |
No action required. | |
786 |
ERROR: Memory allocation failure | |
|
Description |
During shutdown, memory could not be allocated for an internal structure that holds process information. |
Action |
Remove processes that may be tying up physical memory, ensure that the application | |
787 |
ERROR: Memory allocation failure | |
|
Description |
During shutdown, memory could not be allocated for an internal structure that holds process information. |
Action |
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX | |
788 |
ERROR: Memory allocation failure | |
|
Description |
During shutdown, memory could not be allocated for an internal structure that holds process information. |
Action |
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX | |
790 |
INFO: *Interrupt* Want to Continue? (y/n): | |
|
Description |
The system was being shut down when an alarm was turned on. |
Action |
You may proceed with the shutdown request by entering ' | |
794 |
ERROR: Memory allocation failure | |
|
Description |
During |
Action |
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX | |
795 |
ERROR: Memory allocation failure | |
|
Description |
During |
Action |
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX | |
796 |
ERROR: Cannot continue booting without DBBL | |
|
Description |
During the booting sequence for a multiprocessing configuration, the DBBL process is required to be booted before the BBLs may be booted. However, the DBBL has not been booted. |
Action |
Make sure that the DBBL is running on the master node. If the DBBL is in fact running, contact your BEA TUXEDO system Technical Support. Otherwise, the DBBL must be booted (unless all of the admin processes are started at the same time with | |
See Also |
| |
797 |
ERROR: No BBL available for boot of BRIDGE on lmid | |
|
Description |
The |
Action |
The BBL may be booted explicitly using | |
See Also |
| |
798 |
ERROR: Cannot boot remote BBL(lmid1), no BRIDGE available on DBBLs node(lmid2) | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
799 |
ERROR: Cannot boot remote BBL(lmid), machine inaccessible | |
|
Description |
The node lmid is inaccessible and the BBL may not be booted as requested. |
Action |
Verify that the node lmid is running. If so, contact your BEA TUXEDO system Technical Support. |