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.
1301 |
WARN: Cannot update server group location as listed in bulletin board | |
|
Description |
While booting, a server process noticed that it was being booted on the processor listed as the backup processor for that server's group. (This situation occurs when |
Action |
The administrator may choose to allow the servers in the group reporting this error to continue running, or may elect to shut down and restart the server group so that the group location is stored consistently in the bulletin board. | |
See Also |
| |
1302 |
ERROR: Commit error due to outstanding handles | |
|
Description |
An attempt to commit a transaction with outstanding handles failed. |
Action |
This is an application error. Make sure there are no outstanding handles before calling | |
1308 |
ERROR: TUXCONFIG environment variable must be an absolute pathname. | |
|
Description |
The application specified a value for the TUXCONFIG environment variable that is a simple or relative pathname, not beginning with slash (/). |
Action |
Change the TUXCONFIG environment variable to be an absolute pathname and re-execute the program. | |
1309 |
ERROR: tpcommit failed to send message to TMS server | |
|
Description |
The application called |
Action |
Check the userlog for other messages indicating why the request failed. Check that the transaction manager servers are available for all resource managers involved in the application service. | |
See Also |
| |
1351 |
ERROR: Performed tpforward() with outstanding conversations | |
|
Description |
The application called |
Action |
Correct the application such that | |
See Also |
| |
1354 |
ERROR: Another application is using IPC key ipckey | |
|
Description |
The IPC key, ipckey, specified in the RESOURCES section of the UBBCONFIG file is being used by another BEA TUXEDO system application. |
Action |
Change the IPCKEY value, reload the configuration file, and boot the application. | |
See Also |
| |
1355 |
ERROR: Cannot find *MACHINES entry for MASTER master | |
|
Description |
When joining the application, a client or server cannot find the configuration entry for the MASTER machine, master. |
Action |
This should not occur since it is checked when the configuration is loaded or updated. Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
1367 |
ERROR: Expired TUXEDO System Binary License | |
|
Description |
The TUXEDO System/T master binary is not properly licensed, or the expiration date on an evaluation copy has been reached. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1372 |
ERROR: tpsuspend xa_end returned errstring | |
|
Description |
The call to |
Action |
Check the error reporting mechanism for the associated resource manager to determine the cause of the problem. Contact your BEA TUXEDO system Technical Support or resource manager vendor. | |
1373 |
ERROR: Wrong transaction state statestring | |
|
Description |
tpsuspend was called while the transaction was not in an active state (for example, |
Action |
Correct the application such that it does not call | |
See Also |
| |
1374 |
ERROR: tpresume xa_start flags flagval returned errstring | |
|
Description |
The call to |
Action |
Check the error reporting mechanism for the associated resource manager to determine the cause of the problem. Contact your BEA TUXEDO system Technical Support or resource manager vendor. | |
1376 |
WARN: variable value "string" in environment does not match configuration "string" | |
|
Description |
While putting variables into the environment for either the machine or server |
Action |
No action required. | |
See Also |
| |
1378 |
ERROR: Transaction counter <= 0 | |
|
Description |
As part of starting a new transaction, the system makes a unique transaction identifier that is based, in part, on a system counter. If for some reason the counter was corrupted, this message is printed. |
Action |
Contact your BEA TUXEDO system Technical Support. The bulletin board shared memory has probably been corrupted by a stray pointer or some other problem. Consider running | |
See Also |
| |
1380 |
ERROR: Still in transaction | |
|
Description |
A service routine explicitly started a transaction but did not commit or abort it before calling |
Action |
Modify the service routine to resolve the transaction before calling | |
See Also |
| |
1381 |
ERROR: Cannot lock bulletin board | |
|
Description |
As part of |
Action |
Check for corrupted shared memory, an invalid application IPCKEY, or if two applications are using the same IPCKEY. | |
1382 |
ERROR: Cannot unlock bulletin board | |
|
Description |
As part of |
Action |
Check for corrupted shared memory, an invalid application IPCKEY, or if two applications are using the same IPCKEY. | |
1383 |
ERROR: Cannot get counter value for new transaction | |
|
Description |
As part of starting a new transaction, the system makes a unique transaction identifier that is based, in part, on a system counter. If for some reason the counter was corrupted, this message is printed. |
Action |
Contact your BEA TUXEDO system Technical Support. The bulletin board shared memory has probably been corrupted by a stray pointer or some other problem. Consider running | |
See Also |
| |
1384 |
ERROR: xa_start flags flags returned errcode | |
|
Description |
This message is issued if a process attempting to start a new transaction encounters an error when calling the database resource manager's |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database system documentation or error logs may contain more information about why | |
1385 |
ERROR: xa_end returned errcode | |
|
Description |
This message is issued if a process attempting to commit a transaction encounters an error when calling the database resource manager's |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database system documentation or error logs may contain more information about why | |
1386 |
ERROR: xa_abort returned errcode | |
|
Description |
This message is issued if a process attempting to commit a transaction could not lock the bulletin board. It then attempted to roll back the transaction, and encountered an error when calling the database resource manager's |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database system documentation or error logs may contain more information about why | |
1387 |
ERROR: xa_commit returned errcode | |
|
Description |
This message is issued if a process attempting to commit a transaction encountered an error when calling the database resource manager's |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database system documentation or error logs may contain more information about why | |
1388 |
ERROR: Wrong transaction state state | |
|
Description |
This message is issued when a transaction cannot be committed because the process is in an invalid transaction state (that is, a protocol violation). The process may have already called |
Action |
See the userlog for more information about this transaction's completion. Also, use | |
1389 |
ERROR: xa_end returned errcode | |
|
Description |
This message is issued if a process attempting to abort a transaction encounters an error when calling the database resource manager's |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. The database system documentation or error logs may contain more information about why | |
1390 |
ERROR: Too many groups in transaction, cannot add groupname | |
|
Description |
An error has occurred while attempting to add a group to a transaction because the maximum number of groups allowed in a transaction (16 groups) has been reached. The transaction will be aborted. |
Action |
If possible, reduce the number of groups required for the particular operation, or call some of them with the TPNOTRAN flag. Using | |
1391 |
WARN: tpreturn called outside service routine | |
|
Description |
|
Action |
Modify the application code calling | |
See Also |
| |
1392 |
WARN: tpreturn called with invalid flags 0xflags | |
|
Description |
|
Action |
Modify the application code calling | |
See Also |
| |
1393 |
WARN: tpreturn called with TPEXIT | |
|
Description |
|
Action |
Contact the application developer to learn why the server process failed and requested a restart. | |
See Also |
| |
1394 |
WARN: tpreturn called with invalid rval number | |
|
Description |
|
Action |
Modify the application code calling | |
See Also |
| |
1395 |
WARN: tpreturn failed because connection not SENDONLY | |
|
Description |
|
Action |
Modify the application logic so that the service routine has SENDONLY control of the conversation before calling | |
See Also |
| |
1396 |
WARN: tpreturn failed because subordinate conversations open | |
|
Description |
|
Action |
Modify the application logic so that the service routine ends all conversations it started before calling | |
See Also |
| |
1397 |
WARN: tpreturn transaction processing failure | |
|
Description |
|
Action |
See the userlog for more information about this transaction's completion. Also, use | |
See Also |
| |
1398 |
WARN: tpforward called outside service routine | |
|
Description |
|
Action |
Modify the application code calling | |
See Also |
| |
1399 |
WARN: tpforward called with invalid flags 0xflags | |
|
Description |
|
Action |
Modify the application code calling | |
See Also |
|