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: Invalid search key | |
|
Description |
An internal BEA TUXEDO system table was requested, and could not be read because an invalid search key was passed to the low-level access routine. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
701 |
ERROR: [Parameter error in internal routine] | |
|
Description |
One of the internal routines to modify structures in the TUXEDO System/T bulletin board received a parameter that did not match any of the allowable values. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
703 |
ERROR: Cannot get statistics on message queue number | |
|
Description |
A msgctl kernel call performing an IPC-STAT operation failed for message queue number. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
704 |
ERROR: Operating system parameter for message queues too small | |
|
Description |
The UNIX System kernel parameters related to message queues are set too low. |
Action |
Check the kernel parameters related to message queue capacities, and increase if necessary. In particular, check MSGMNB. | |
See Also |
BEA TUXEDO Installation Guide | |
705 |
ERROR: No BRIDGE available for remote send | |
|
Description |
A BEA TUXEDO system process attempted to send a message to another machine, but the BRIDGE system process could not be located. |
Action |
Shut down and reboot the BEA TUXEDO system on this machine. | |
709 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure 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. | |
710 |
ERROR: Server table index out of range | |
|
Description |
A service could not be advertised because of an invalid internal handle identifying the server process offering it. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
711 |
ERROR: Server table index out of range | |
|
Description |
A service could not be advertised because of an internal data structure inconsistency. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
712 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure 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. | |
713 |
ERROR: Queue parameter error in internal routine | |
|
Description |
One of the internal routines to manage TUXEDO System/T data structures received an invalid queue table parameter. This should not occur during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
715 |
ERROR: Cannot attach bulletin board - magic number mismatch | |
|
Description |
The process just attached to a shared memory region, expecting to find a BEA TUXEDO system bulletin board. The header's magic number indicates that it is not a valid bulletin board. |
Action |
Verify that the configuration file's IPCKEY parameter is unique, and not being used by any other software product on the machine. The UNIX ipcs utility may help diagnose the conflict. | |
716 |
ERROR: Cannot attach bulletin board - wrong release of software | |
|
Description |
The BEA TUXEDO system software has been updated on the machine, but this process has not been rebuilt with the new libraries. It therefore cannot interpret the bulletin board data structures. |
Action |
Rebuild the process with updated BEA TUXEDO system libraries. | |
See Also |
| |
717 |
ERROR: Cannot attach to or create shared memory | |
|
Description |
The calling process could not attach to the bulletin board's shared memory. It then attempted to create the bulletin board, but did not have the correct permissions to do so. |
Action |
Verify that the configuration file's IPCKEY parameter is correct, and that the application is booted. | |
721 |
ERROR: Server group creation failure | |
|
Description |
A server group entry in the bulletin board could not be created due to an internal error. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
722 |
ERROR: Cannot add subtype to bulletin board | |
|
Description |
A subtype could not be added to the bulletin board due to an internal error. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
723 |
ERROR: Cannot add subtype: no more room in subtype table | |
|
Description |
The bulletin board's subtype table is full, and a new subtype cannot be added. |
Action |
Increase the MAXBUFSTYPE parameter in the configuration file's RESOURCES section. | |
724 |
ERROR: Service information invalid | |
|
Description |
A BEA TUXEDO system internal function was used to retrieve service information from the services table, but a NULL service name was used. |
Action |
Contact your BEA TUXEDO system Technical Support for assistance. | |
725 |
ERROR: Server information invalid, does not exist | |
|
Description |
An internal error occurred while a service was being added to the bulletin board's tables. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
726 |
ERROR: Server information invalid, does not exist | |
|
Description |
An internal data structure inconsistency was detected while a service was being added to the bulletin board's tables. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
727 |
ERROR: [Server parameter error in internal routine] | |
|
Description |
The internal routine to create a server table entry received invalid parameters. This should not happen during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
728 |
ERROR: [Queue parameter error in internal routine] | |
|
Description |
One of the internal routines to manage TUXEDO System/T data structures received an invalid queue table parameter. This should not occur during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
729 |
ERROR: Server not available, doing work | |
|
Description |
An attempt to create a server table entry failed because the server was busy. |
Action |
Wait until the server is no longer busy, and then retry the failed operation. | |
730 |
ERROR: No space for another queue table entry | |
|
Description |
There are no more queue table entries left in the system. The number of queue table entries is equal to the maximum number of servers as specified in the UBBCONFIG file. |
Action |
Increase the maximum number of servers, as specified by the MAXSERVERS parameter in the RESOURCES section of the UBBCONFIG file. This can be done by editing the configuration file and reloading it with | |
See Also |
| |
732 |
ERROR: BBL unstable or dead | |
|
Description |
The BBL (Bulletin Board Liaison) process is unstable or dead. |
Action |
Look for associated messages in the userlog related to the BBL. These may give more insight about the problem. If using a multi-node configuration, make certain that the network is operating properly and has sufficient bandwidth. Verify that the TUXEDO System/T administrator or the UNIX System administrator did not kill the BBL process. Oftentimes, a network that is inoperative or slow may result in a BBL response problem. | |
733 |
ERROR: [Type information invalid] | |
|
Description |
The internal routine to create an entry in the bulletin board types table was passed invalid parameters. This should not happen during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
734 |
ERROR: Cannot add to type table due to lack of space | |
|
Description |
There are no more type table entries left in the system. An attempt to add an additional type to the bulletin board has failed due to a lack of space. The number of type table entries is equal to the number specified in the UBBCONFIG file. |
Action |
Increase the maximum number of type table entries, as specified by the MAXBUFTYPE parameter in the RESOURCES section of the UBBCONFIG file. This can be done by editing the configuration file and reloading it with | |
See Also |
| |
735 |
ERROR: [Queue parameter error in internal routine] | |
|
Description |
See message 728 for an explanation. |
Action |
See message 728 for an explanation. | |
736 |
ERROR: [Cannot delete entry from queue table due to invalid server association] | |
|
Description |
An attempt to delete an entry from the internal TUXEDO System/T queue table failed while attempting to delete one of the servers associated with the queue. This should not happen during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
737 |
ERROR: [Invalid service information passed to internal routine] | |
|
Description |
One of the internal routines to manage TUXEDO System/T data structures received an invalid service table parameter. This should not occur during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
738 |
ERROR: [Invalid server information passed to internal routine] | |
|
Description |
One of the internal routines to manage TUXEDO System/T data structures received an invalid server table parameter. This should not occur during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
739 |
ERROR: [Inconsistent service/server associations in bulletin board] | |
|
Description |
The TUXEDO System/T bulletin board data structures contain an invalid service/server association. This indicates a corruption of data structures and should not occur during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
744 |
ERROR: Not attached to a Bulletin Board | |
|
Description |
The process producing this error message is not attached to the TUXEDO System/T configuration. |
Action |
If this message occurred in a client process, make sure that the process successfully invokes | |
745 |
ERROR: Process not attached to a Bulletin Board | |
|
Description |
See message 744 for an explanation. |
Action |
See message 744 for an explanation. | |
746 |
ERROR: Cannot lock Bulletin Board | |
|
Description |
A process was unable to lock the TUXEDO System/T shared memory data structures. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
747 |
ERROR: Process not attached to Bulletin Board | |
|
Description |
See message 744 for an explanation. |
Action |
See message 744 for an explanation. | |
748 |
ERROR: Cannot unlock Bulletin Board | |
|
Description |
The process was unable to successfully unlock the TUXEDO System/T Bulletin Board. As a result of this problem, other processes will be unable to lock the Bulletin Board. The most common cause of this error is the accidental removal of some or all of the TUXEDO System/T semaphore sets. |
Action |
Ask the privileged users on your system (normally the TUXEDO System/T administrator and root) whether they may have accidentally removed some IPC resources, perhaps through inadvertent use of the UNIX System | |
749 |
ERROR: Cannot unlock Bulletin Board, not the locker | |
|
Description |
The process attempted to unlock the TUXEDO System/T Bulletin Board, but it was not the locker of the Bulletin Board. Because of this, no change was made to the status of the Bulletin Board. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
751 |
ERROR: semop system call failure for semaphore semno, errno = errno_val | |
|
Description |
A |
Action |
Refer to the UNIX System | |
752 |
ERROR: semop system call failure for semaphore semno, errno errno_val | |
|
Description |
See message 751 for an explanation. |
Action |
See message 751 for an explanation. | |
753 |
ERROR: [Invalid service information passed to internal routine] | |
|
Description |
See message 737 for an explanation. See message 737 for an explanation. |
754 |
ERROR: Service does not match existing services offered | |
|
Description |
When a new server is added to an existing group of servers on an MSSQ set, the new server must offer the same set of services as the existing servers, and these services must be performed by the same service functions. Also, the executable for the new server must be the same file as the existing server(s) on the queue, or a link to the same file. The server being started did not obey these restrictions. |
Action |
Make sure that the path name of the new server executable is the same as the path name for the existing server(s) on the queue used by the new server. Determine the services currently advertised on the server queue, and make sure that the new server offers the same set of services. The services currently offered on a queue can be determined through the | |
See Also |
| |
755 |
ERROR: Restarting server cannot delete queue | |
|
Description |
A server being restarted by the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
756 |
ERROR: Cannot get status for server files new_server_executable and existing_server_executable | |
|
Description |
When adding a server to an MSSQ set on which there are already one or more servers executing, the BEA TUXEDO system verifies that the new server either has the same file name as the existing server(s) or is a link to these server(s). This latter check requires executing the UNIX System |
Action |
Make certain that both files listed in the error message exist, that all components in the path prefixes of these files are directories, and that the user ID under which the new server is being started has search permission on every directory in the path prefix. Refer to the UNIX System | |
See Also |
| |
757 |
ERROR: Memory allocation failure | |
|
Description |
The BEA TUXEDO system received an error return when attempting to allocate memory from the operating system |
Action |
Attempt to decrease the amount of memory required by TUXEDO System/T, or add more physical memory to the machine. The amount of memory required by the BEA TUXEDO system is influenced by the parameters given in the | |
758 |
ERROR: Cannot find desired server to remove | |
|
Description |
While attempting to remove a server from the TUXEDO System/T bulletin board, the BEA TUXEDO system was unable to find the server in its internal tables. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
759 |
ERROR: Cannot find queue entry for server that is to be removed | |
|
Description |
While attempting to remove a server from the TUXEDO System/T bulletin board, the BEA TUXEDO system was unable to find the queue associated with the server in its internal tables |
Action |
Contact your BEA TUXEDO system Technical Support. | |
760 |
ERROR: [Queue parameter error in internal routine] | |
|
Description |
See message 728 for an explanation. |
Action |
See message 728 for an explanation. | |
761 |
ERROR: [Queue parameter error in internal routine] | |
|
Description |
See message 728 for an explanation. |
Action |
See message 728 for an explanation. | |
762 |
ERROR: [Parameter error in internal routine] | |
|
Description |
One of the internal routines to modify structures in the TUXEDO System/T bulletin board received a parameter that did not match any of the allowable values. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
763 |
ERROR: [Server group parameter error in internal routine] | |
|
Description |
One of the internal TUXEDO System/T routines to manipulate server group parameters within the bulletin board received an invalid input parameter. This should not happen during normal system operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
764 |
ERROR: [Server group parameter error in internal routine] | |
|
Description |
See message 763 for an explanation. |
Action |
See message 763 for an explanation. | |
765 |
ERROR: [Server group parameter error in internal routine] | |
|
Description |
See message 763 for an explanation. |
Action |
See message 763 for an explanation. | |
766 |
ERROR: [Parameter error in internal routine] | |
|
Description |
See message 762 for an explanation. |
Action |
See message 762 for an explanation. | |
767 |
ERROR: [Parameter error in internal routine] | |
|
Description |
See message 762 for an explanation. |
Action |
See message 762 for an explanation. | |
768 |
ERROR: [Invalid service information passed to internal routine] | |
|
Description |
See message 737 for an explanation. |
Action |
See message 737 for an explanation. | |
769 |
ERROR: [Invalid service information passed to internal routine] | |
|
Description |
See message 737 for an explanation. |
Action |
See message 737 for an explanation. | |
770 |
ERROR: [Invalid service information passed to internal routine] | |
|
Description |
See message 737 for an explanation. |
Action |
See message 737 for an explanation. | |
771 |
ERROR: [Invalid service information passed to internal routine] | |
|
Description |
See message 737 for an explanation. |
Action |
See message 737 for an explanation. | |
772 |
ERROR: Invalid search criteria given | |
|
Description |
See message 762 for an explanation. |
Action |
See message 762 for an explanation. | |
773 |
ERROR: Invalid server information given | |
|
Description |
This error occurs when a client or server is requesting to look up server table entries in the Bulletin Board by |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
774 |
ERROR: Invalid server information given | |
|
Description |
This error occurs when a client or server is requesting to look up server table entries in the Bulletin Board by |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
775 |
ERROR: Invalid queue information given | |
|
Description |
This error occurs when a client or server is requesting to look up server table entries in the Bulletin Board by |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
776 |
ERROR: Invalid server information given | |
|
Description |
This error occurs when a client or server is requesting to look up server table entries in the Bulletin Board by using the |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
777 |
ERROR: Invalid search criteria given | |
|
Description |
This error occurs when a client or server is requesting to look up server table entries in the Bulletin Board and supplies an incorrect or NULL scope argument. This happens if there is a bug in the calling routine. |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
778 |
ERROR: Invalid queue information given | |
|
Description |
This error occurs when a client or server is requesting to update queue table entries in the Bulletin Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine. |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
779 |
ERROR: Invalid server group information given | |
|
Description |
This error occurs when a client or server is requesting to update server group table entries in the Bulletin Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine. |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
780 |
ERROR: Invalid entry information given | |
|
Description |
This error occurs when a client or server is requesting to update the status of table entries in the Bulletin Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine. |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
781 |
ERROR: Invalid service information given | |
|
Description |
This error occurs when a client or server is requesting to update service table entries in the Bulletin Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine. |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
782 |
ERROR: Invalid server information given | |
|
Description |
This error occurs when a client or server is requesting to update server table entries in the Bulletin Board and supplies incorrect or NULL arguments. This happens if there is a bug in the calling routine. |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
788 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure 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. Increase the space on the swap device. | |
See Also |
| |
789 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure 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. Increase the space on the swap device. | |
See Also |
| |
790 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure 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. Increase the space on the swap device. | |
See Also |
| |
791 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure 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. Increase the space on the swap device. | |
See Also |
| |
792 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure 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. Increase the space on the swap device. | |
See Also |
| |
793 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
Action |
Make sure 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. Increase the space on the swap device. | |
See Also |
|