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.
401 |
ERROR: service request service_name handled by DBBL failed, msg | |
|
Description |
An administrative service request handled by the |
Action |
The service requests failed with | |
See Also |
| |
402 |
INFO: The temporary DBBL is exiting system | |
|
Description |
A temporary |
Action |
No action required. | |
See Also |
| |
403 |
INFO: The DBBL is exiting system | |
|
Description |
The |
Action |
No action required. | |
See Also |
| |
404 |
WARN: 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. | |
406 |
WARN: SIGTERM was ignored while shutting down the DBBL | |
|
Description |
|
Action |
See | |
See Also |
| |
407 |
ERROR: Unable to add group group_name to TMGCTL table - no space | |
|
Description |
BEA TUXEDO system attempted to add the specified group in the transaction management data table, but the space allocated for the number of groups was exceeded. |
Action |
Please modify your configuration and increase the number of server groups that are to be used. Then reload the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
408 |
ERROR: Unable to add group group_name to TMGTT table - no space | |
|
Description |
BEA TUXEDO system was in the process of recovering transactions while performing a |
Action |
Contact your BEA TUXEDO system Technical Support. | |
409 |
ERROR: xa_recover() returned count for group groupname | |
|
Description |
BEA TUXEDO system was in the process of recovering transactions while performing a |
Action |
Check the error mechanism for the associated resource manager to find the nature of the error. | |
410 |
WARN: tpsvrinit() changing state of group groupname from TMGHCOMMIT to TMGABORTED | |
|
Description |
BEA TUXEDO system was in the process of recovering transactions while performing a |
Action |
Please repeat the transaction. | |
411 |
ERROR: tpsvrinit() found transaction state state_val | |
|
Description |
BEA TUXEDO system was in the process of recovering transactions while performing a |
Action |
Contact your BEA TUXEDO system Technical Support. | |
412 |
ERROR: tpsvrinit() unable to locate entry for TMS in the Bulletin Board | |
|
Description |
BEA TUXEDO system was in the process of recovering transactions while performing a |
Action |
Contact your BEA TUXEDO system Technical Support. | |
413 |
ERROR: tpsvrinit() unable to update entry for TMS in the Bulletin Board | |
|
Description |
BEA TUXEDO system was in the process of recovering transactions while performing a |
Action |
Contact your BEA TUXEDO system Technical Support. | |
414 |
ERROR: TMS() got request for invalid Global Transaction ID | |
|
Description |
BEA TUXEDO system server |
Action |
Contact your BEA TUXEDO system Technical Support. | |
415 |
ERROR: Invalid service identifier requested while processing transactions | |
|
Description |
An invalid service identifier identifier was specified for processing, and therefore could not complete the necessary operation. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
416 |
ERROR: service svcname sent to non-coordinator | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
417 |
ERROR: TMS_MANAGE found transaction state stateval | |
|
Description |
While processing transactions, an invalid state was reached. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
418 |
ERROR: Unable to add message groups to transaction | |
|
Description |
While processing transactions, the BEA TUXEDO system attempted to add message groups to the transaction. The operation was unsuccessful. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
419 |
WARN: Commit found no participants | |
|
Description |
While processing a commit request, the |
Action |
No action required. | |
420 |
WARN: Commit coordinator gone | |
|
Description |
BEA TUXEDO system was processing transactions. In a transaction, the first Resource Manager group is the transaction coordinator, so it must be the first at its site. However, it is possible that the site went down and came back up before the arrival of a TMS_MANAGE message. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
421 |
ERROR: Invalid transaction state state | |
|
Description |
BEA TUXEDO system was committing a transaction. During a one-phase commit step, the transaction state was invalid. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
422 |
ERROR: XA_RETRY not supported for one-phase commit | |
|
Description |
BEA TUXEDO system was committing a transaction. During a one-phase commit, the |
Action |
Check the error reporting mechanism for the associated resource manager. | |
423 |
WARN: One-phase commit - xa_commit returned error_val | |
|
Description |
BEA TUXEDO system was committing a transaction. During a one-phase commit, the |
Action |
Check the error reporting mechanism for the associated resource manager. | |
424 |
ERROR: Commit found invalid state - group group state state | |
|
Description |
BEA TUXEDO system was committing a transaction. During a one-phase commit, the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
425 |
ERROR: Precommit found an invalid transaction state state | |
|
Description |
BEA TUXEDO system was precommitting a transaction. The transaction state was not one of the states expected. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
426 |
ERROR: Precommit found invalid state group group state state | |
|
Description |
BEA TUXEDO system was precommitting a transaction. The transaction state for the indicated group was not as expected. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
427 |
ERROR: Precommit transaction state state after xa_precom failure | |
|
Description |
BEA TUXEDO system was precommitting a transaction. The transaction state after xa_precom failure was not as expected. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
428 |
ERROR: Precommit transaction state state after xa_precom | |
|
Description |
BEA TUXEDO system was precommitting a transaction. The transaction state after xa_precom was not as expected. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
429 |
ERROR: Rollback found invalid transaction state state | |
|
Description |
BEA TUXEDO system was rolling back a transaction. The transaction state was not as expected. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
430 |
ERROR: Completion found invalid transaction state state | |
|
Description |
BEA TUXEDO system was completing a transaction. The transaction state was not as expected. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
431 |
ERROR: Received a rollback request for a decided transaction | |
|
Description |
BEA TUXEDO system received a rollback request for a decided transaction. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
432 |
ERROR: Group group at coordinator site received rollback request in ready state | |
|
Description |
BEA TUXEDO system received a request to rollback a transaction that is already in "ready" state. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
433 |
ERROR: Rollback - xa_abort returned error for group group | |
|
Description |
BEA TUXEDO system was rolling back a transaction. The resource manager returned an error when |
Action |
Check the error reporting mechanism for the associated resource manager. | |
434 |
WARN: Rollback changing group group from heuristic commit to rolled back | |
|
Description |
BEA TUXEDO system was rolling back a transaction. The transaction state of the group was changed from heuristic commit to rolled back. |
Action |
No action required. | |
435 |
ERROR: Rollback found invalid state - group group in state state | |
|
Description |
BEA TUXEDO system was rolling back a transaction. The transaction state of the group was not one of the expected states. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
436 |
WARN: Heuristic rollback of transaction | |
|
Description |
BEA TUXEDO system received a request to heuristically rollback a global transaction. This request was generated via |
Action |
No action required. | |
437 |
WARN: Heuristic rollback of transaction | |
|
Description |
BEA TUXEDO system received a request to heuristically rollback a transaction for this group only. This request was generated via |
Action |
No action required. | |
438 |
WARN: Heuristic rollback not allowed for decided transaction | |
|
Description |
A request was received to heuristically rollback a transaction that is already in decided state. This request was generated via |
Action |
No action required. | |
439 |
WARN: Heuristic rollback not allowed for ready transaction at coordinator site | |
|
Description |
BEA TUXEDO system received a request to heuristically rollback a transaction that is in ready state. The request was generated by the |
Action |
The request will be ignored. No action required. | |
440 |
WARN: Transaction heuristically rolled back for group groupname | |
|
Description |
BEA TUXEDO system heuristically rolled back a transaction based on a request from the |
Action |
No action required. | |
441 |
ERROR: Rollback xa_abort returned error | |
|
Description |
BEA TUXEDO system was rolling back a transaction. The |
Action |
Check the error reporting mechanism for the associated resource manager. | |
442 |
ERROR: Timeout found invalid state state | |
|
Description |
BEA TUXEDO system was processing a timeout request for a transaction and found an unexpected state, state. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
443 |
ERROR: tms_timeout group group xa_abort returned error | |
|
Description |
BEA TUXEDO system was processing a timeout request for a transaction. The resource manager returned an error from |
Action |
Check the error reporting mechanism for the associated resource manager. | |
444 |
WARN: Heuristic commit for group group | |
|
Description |
This informative message indicates that the transaction has been heuristically committed as a result of a |
Action |
No action required. | |
445 |
ERROR: Heuristic commit xa_commit for group group returned error | |
|
Description |
While heuristically committing a transaction, the resource manager returned an error condition from |
Action |
Check the error reporting mechanism for the associated resource manager. | |
446 |
ERROR: Commit found transaction state state | |
|
Description |
While committing a transaction, an unexpected transaction state was found. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
447 |
ERROR: xa_commit returned error for group group | |
|
Description |
While committing a transaction, the resource manager returned an error from |
Action |
Check the error reporting mechanism for the associated resource manager. | |
448 |
ERROR: Commit found invalid state for group group state state | |
|
Description |
While committing a transaction, an invalid state was found for the specified group. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
449 |
ERROR: Ready indication for missing group group | |
|
Description |
While committing a transaction, a ready indication was received for a group that is not part of the transaction. The indication will be ignored. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
450 |
ERROR: Ready found invalid state for group group state state | |
|
Description |
While committing a transaction, a ready indication was received for a group that is in an invalid state. The indication will be ignored. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
451 |
ERROR: Reday indication found transaction state state | |
|
Description |
While committing a transaction, a ready indication was received for a transaction that is in an unexpected state. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
452 |
ERROR: Status request transaction state state group group state state | |
|
Description |
While processing a status request for a transaction, unexpected states were found for the transaction and the specified group. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
453 |
ERROR: Transaction log commit failed | |
|
Description |
While committing a transaction, updating the transaction log failed. |
Action |
Check the userlog for earlier messages indicating the nature of the failure. | |
454 |
ERROR: Status request found transaction state state | |
|
Description |
While processing a status request, an invalid transaction state was found. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
455 |
ERROR: tpsvrdone can't find group group | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
456 |
ERROR: tpsvrdone can't get queue entry | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
457 |
INFO: TMS tpsvrdone complete | |
|
Description |
The |
Action |
No action required. | |
458 |
ERROR: Memory allocation failure | |
|
Description |
The distinguished |
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. | |
459 |
ERROR: Invalid sendlist error | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
460 |
ERROR: TMS send - failed to set priority for TMS request | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
461 |
ERROR: tms_send tpacall service code | |
|
Description |
The |
Action |
A possible cause for this error may be that the | |
462 |
WARN: Can't send reply to committer | |
|
Description |
The |
Action |
Please examine the userlog for additional messages included prior to this one. If further assistance is needed, contact your BEA TUXEDO system Technical Support. | |
463 |
ERROR: could not contact BBL to abort old transactions | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
464 |
ERROR: could not contact DBBL to abort old transactions | |
|
Description |
The |
Action |
Please ensure that the | |
465 |
ERROR: Failed to abort old transactions | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
468 |
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. | |
469 |
ERROR: Can't send shutdown message to the BSBRIDGE | |
|
Description |
Please refer to the description for Message 468 above. The send of the shutdown message to the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
470 |
WARN: 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. | |
471 |
WARN: Error sending message OB_IDENT process | |
|
Description |
The |
Action |
It is likely that further errors will occur over this connection. Try to reestablish the link using | |
473 |
ERROR: Could not find DBBL | |
|
Description |
|
Action |
Check the master machine's network addresses in the NETWORK section of the configuration file. Check for and resolve any networking problems. | |
476 |
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. | |
480 |
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. | |
See Also |
| |
481 |
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. | |
See Also |
| |
482 |
ERROR: Received message with unknown release number rel_val | |
|
Description |
The message received by the |
Action |
Verify that the releases of the BEA TUXEDO system software installed are valid. Contact your BEA TUXEDO system Technical Support. | |
483 |
ERROR: Shutting down bridge, serious message receive error | |
|
Description |
The bridge is shutting down due to a system error. |
Action |
Re-try the desired operation and if the problem persists, contact your BEA TUXEDO system Technical Support. | |
484 |
ERROR: BRIDGE process detected corrupted message | |
|
Description |
The bridge or bootstrap bridge process detected a message with a corrupted header. This could be caused by problems in the networking software or in BEA TUXEDO system itself. |
Action |
Contact your BEA TUXEDO system Technical Support for assistance. | |
485 |
ERROR: Memory allocation failure | |
|
Description |
BEA TUXEDO system received an error return while attempting to allocate memory from the operating system. The amount of memory required by BEA TUXEDO system is influenced by the parameters in the |
Action |
Attempt to decrease the amount of memory required by BEA TUXEDO system, or add more physical memory to the machine. | |
See Also |
BEA TUXEDO Administrator's Guide | |
486 |
ERROR: Message encoding error | |
|
Description |
BEA TUXEDO system encountered an error while attempting to encode a negative acknowledgment message being sent from the bridge or bootstrap bridge process. |
Action |
Contact your BEA TUXEDO system Technical Support for assistance. | |
490 |
ERROR: tprealloc() failed | |
|
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. | |
491 |
ERROR: tprealloc() failed | |
|
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. | |
492 |
ERROR: tprealloc() failed | |
|
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. | |
493 |
INFO: Waiting for orderly release to exit | |
|
Description |
BEA TUXEDO system was processing a server shutdown. This message is an indication of that action. |
Action |
No action required. | |
494 |
INFO: BRIDGE exiting system | |
|
Description |
BEA TUXEDO system was processing a server shutdown. This message is an indication of that action. |
Action |
No action required. | |
495 |
INFO: Alarm forcing shutdown after 30 second wait | |
|
Description |
BEA TUXEDO system was processing a BRIDGE shutdown. This message indicates that a forced shutdown of the BRIDGE was initiated, most likely because a previous network connection disconnect failed. |
Action |
Please examine the userlog for further information. If necessary, contact your BEA TUXEDO system Technical Support. | |
496 |
INFO: Rejecting EXIT Message not sent from local BBL or BRIDGE | |
|
Description |
BEA TUXEDO system was processing a BRIDGE shutdown. The BSBRIDGE process received an EXIT message from a process other than the local BRIDGE or BBL process, not from a process on a remote machine. |
Action |
This message is informative in nature. BEA TUXEDO system processing will continue. However, the userlog may yield additional information that would help explain why this message was written to the userlog. | |
497 |
INFO: Rejecting EXIT Message not sent from local BBL | |
|
Description |
BEA TUXEDO system was processing a BRIDGE shutdown. The BRIDGE process received an EXIT message from a process other than the local BBL process, not from a process on a remote machine. |
Action |
This message is informative in nature. BEA TUXEDO system processing will continue. However, the userlog may yield additional information that would help explain why this message was written to the userlog. | |
498 |
ERROR: Shutting down bridge, serious message receive error | |
|
Description |
The bridge is shutting down due to a system error. |
Action |
Re-try the desired operation and if the problem persists, contact your BEA TUXEDO system Technical Support. | |
499 |
ERROR: Shutting down bridge, serious message receive error | |
|
Description |
The bridge is shutting down due to a system error. |
Action |
Re-try the desired operation and if the problem persists, contact your BEA TUXEDO system Technical Support. |