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.
601 |
ERROR: Memory allocation failure for receive buffer | |
|
Description |
An attempt to dynamically 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. | |
602 |
ERROR: Network access error | |
|
Description |
There are two possible causes:
|
Action |
| |
603 |
ERROR: Memory allocation failure | |
|
Description |
An attempt to dynamically 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. | |
604 |
ERROR: Could not decode request message | |
|
Description |
The |
Action |
Verify that the correct release of the BEA TUXEDO system is running on both machines. The master machine can be at most one release ahead of other machines in the network. Contact your BEA TUXEDO system Technical Support. | |
605 |
ERROR: Could not set uid/gid for request | |
|
Description |
The |
Action |
The | |
See Also |
| |
606 |
ERROR: Invalid version number for request | |
|
Description |
The |
Action |
Verify that the correct release of the BEA TUXEDO system is running on both machines. The master machine can be at most one release ahead of other machines in the network. | |
607 |
ERROR: Error encoding reply message | |
|
Description |
A reply message from the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
609 |
ERROR: Invalid arguments for opcode | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
610 |
ERROR: Could not creat temp file for TUXCONFIG | |
|
Description |
The |
Action |
Check the directory permissions and free disk space in the system's temporary file directory. The | |
611 |
ERROR: tmloadcf failed when creating new configuration file | |
|
Description |
The |
Action |
| |
612 |
ERROR: Could not set environment variable | |
|
Description |
The |
Action |
| |
613 |
ERROR: Could not retrieve parameters from TUXCONFIG file | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
614 |
ERROR: Unknown error, terminating | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
615 |
INFO: Terminating tlisten process | |
|
Description |
The |
Action |
No action required. | |
See Also |
| |
617 |
ERROR: Invalid tlisten option option | |
|
Description |
An invalid option, option, was passed to |
Action |
Select the appropriate option(s) from the usage line that follows the message. | |
See Also |
| |
624 |
ERROR: tlisten network address not specified | |
|
Description |
The user needs to pass the network address where the |
Action |
Invoke | |
See Also |
| |
626 |
ERROR: tlisten could not find entry for user username | |
|
Description |
The user has the option to reset the user id and group id of the |
Action |
Verify that the argument to the | |
See Also |
| |
627 |
ERROR: tlisten cannot run as root | |
|
Description |
The |
Action |
The user should use the | |
See Also |
| |
628 |
ERROR: tlisten could not set user id to user_name | |
|
Description |
The |
Action |
Verify that the user name or user id passed as an argument to the | |
See Also |
| |
629 |
ERROR: tlisten invoked by non-root, can't change user id. | |
|
Description |
The user id of the |
Action |
If the user wishes to have the | |
See Also |
| |
636 |
WARN: Error sending acknowledgment back to requester | |
|
Description |
The |
Action |
Try repeating the same operation. If this fails with the same error, contact your UNIX System administrator or your BEA TUXEDO system Technical Support. | |
See Also |
| |
642 |
ERROR: Invalid service request received, bad message header | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
644 |
ERROR: Cannot remove BRIDGE on machine machine | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
645 |
ERROR: Cannot unregister BBL on machine machine | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
646 |
ERROR: Could not restore DBBL entry after temp change for shutdown | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
647 |
ERROR: Failed to update status of restarting BRIDGE | |
|
Description |
The local |
Action |
Contact your BEA TUXEDO system Technical Support. | |
648 |
ERROR: DBBL should not receive an O_MIGGRPS opcode | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
649 |
ERROR: BBL should not receive an O_UPDGRPS opcode | |
|
Description |
A |
Action |
Contact your BEA TUXEDO system Technical Support. | |
650 |
ERROR: Could not create message queue for temporary DBBL | |
|
Description |
A temporary |
Action |
Contact your BEA TUXEDO system Technical Support. | |
651 |
ERROR: Could not update bulletin board for temporary DBBL | |
|
Description |
A temporary |
Action |
Contact your BEA TUXEDO system Technical Support. | |
652 |
ERROR: Could not create message queue for DBBL migration | |
|
Description |
The |
Action |
If after the migration the | |
See Also |
| |
653 |
ERROR: Could not update DBBL server table entry for migration | |
|
Description |
The |
Action |
If after this migration the | |
654 |
ERROR: Could not retrieve own bulletin board entry for migration | |
|
Description |
The |
Action |
After this migration it is possible that a | |
See Also |
| |
655 |
INFO: Exiting system for migration from mach1 to mach2 | |
|
Description |
The |
Action |
No action required. | |
See Also |
| |
656 |
ERROR: DBBL should not receive an O_WARMSTART opcode | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
657 |
ERROR: DBBL should not receive an O_LOADTLOG opcode | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
662 |
ERROR: Incompatible TLOG file | |
|
Description |
The data file being loaded into the TLOG assumes a different maximum number of groups involved per transaction than this BEA TUXEDO system software release allows. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
663 |
INFO: Exiting system | |
|
Description |
A temporary |
Action |
No action required. | |
664 |
ERROR: Service request from process pid failed | |
|
Description |
A serious failure occurred when processing a service request, and an error response message could not be returned to the originator. Possible causes of the error are: memory allocation failure, software version mismatch, or a shutdown is in progress. pid is the UNIX System process id number of the requester. However, it might be located on a remote machine. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
665 |
ERROR: Could not unsuspend reconnected node nodename | |
|
Description |
nodename is a remote machine that had been previously partitioned. It is now back and reconnected to the |
Action |
On the master machine, perform a | |
See Also |
| |
668 |
WARN: Stale message received from BBL on machine machinename | |
|
Description |
During collection of responses to a |
Action |
Check the status of machinename, and its network connections. | |
669 |
WARN: Stray string received from process pid | |
|
Description |
During collection of responses to a |
Action |
No action required. | |
670 |
ERROR: Cannot restore message queue, key queuekey | |
|
Description |
If the This error means the message queue recovery code itself failed. It is a serious error because the |
Action |
Use the UNIX System | |
See Also |
| |
672 |
INFO: Sending BBL on machine name new version of bulletin board | |
|
Description |
The |
Action |
No action required. | |
680 |
ERROR: Cannot find own table entry | |
|
Description |
If the This error means the message queue recovery code itself failed. It is a serious error because the |
Action |
Use the UNIX System If it does not restart successfully within a few minutes, contact your BEA TUXEDO system Technical Support. | |
681 |
ERROR: Cannot update own table entry | |
|
Description |
If the This error means the message queue recovery code itself failed. It is a serious error because the |
Action |
Use the UNIX System If it does not restart successfully within a few minutes, contact your BEA TUXEDO system Technical Support. | |
682 |
WARN: New message queue created, key =number | |
|
Description |
If the This message is output after the |
Action |
No action required. | |
683 |
ERROR: Group id for migration is missing | |
|
Description |
One or more server groups could not be migrated because an internal system message is missing necessary data. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
684 |
ERROR: Memory allocation error | |
|
Description |
An attempt to dynamically 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. | |
685 |
ERROR: Could not retrieve server entries for migration | |
|
Description |
One or more server groups could not be migrated because server table entries in the bulletin board could not be retrieved. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
686 |
ERROR: Could not update migrating server's status | |
|
Description |
A migrating server's status could not be updated in the bulletin board. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
687 |
INFO: Server process marked for migration restart, srvgrp=number srvid=number | |
|
Description |
The server process has been migrated, and is about to be restarted on the current machine. |
Action |
No action required. | |
See Also |
| |
688 |
ERROR: Running server cannot be migrated, srvgrp=number srvid=number | |
|
Description |
A request was made to migrate this server process. The migration could not proceed because it is still running. |
Action |
Shut down the process using | |
See Also |
| |
692 |
ERROR: Cannot retrieve BBL entry for pclean operation | |
|
Description |
When attempting to clean up after a dead or partitioned machine, the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
694 |
ERROR: Cannot lock bulletin board for pclean operation | |
|
Description |
A bulletin board lock could not be obtained when attempting to clean up after a dead or partitioned machine. |
Action |
Try again after a few seconds, giving the bulletin board lock recovery algorithm time to run. If this error continues, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
695 |
ERROR: Could not remove server entry for tmid number | |
|
Description |
When attempting to clean up after a dead or partitioned machine, a server table entry could not be removed from the bulletin board. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
697 |
ERROR: Could not access *RESOURCES section of TUXCONFIG file | |
|
Description |
When attempting to update the version number of the master copy |
Action |
Apparently something has happened to the master machine's | |
See Also |
| |
698 |
ERROR: Could not read *RESOURCES section of TUXCONFIG file | |
|
Description |
When attempting to update the version number of the master copy of the |
Action |
Apparently something has happened to the master machine's | |
See Also |
| |
699 |
ERROR: Could not update *GROUPS section of TUXCONFIG file | |
|
Description |
The location of a server group was being updated in the master copy of the |
Action |
Apparently something has happened to the master machine's | |
See Also |
|