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.
1600 |
ERROR: Unable to register - another DBBL already exists on machine | |
|
Description |
The BEA TUXEDO system application was unable to unregister the DBBL process because another DBBL was found to have been booted already. |
Action |
No action required. | |
1601 |
ERROR: TUXCONFIG,TUXOFFSET device1 offset1 doesn't match first device entry on configuration device2 offset2 | |
|
Description |
While loading a |
Action |
Remove the configuration file before loading it with | |
See Also |
| |
1603 |
ERROR: TLOGDEVICE must be an absolute pathname | |
|
Description |
The value for the |
Action |
Correct the value for | |
See Also |
| |
1604 |
ERROR: section_name entry entry_name - duplicate type(type_name)/subtype(subtype_name) | |
|
Description |
The |
Action |
Modify the | |
See Also |
| |
1605 |
ERROR: SERVICES entry entry_name - must have the same BUFTYPE for all SERVICE entries. | |
|
Description |
If multiple entries exist in the SERVICES section with the same service name but with different |
Action |
Specify the same | |
See Also |
| |
1614 |
WARN: Network device does not exist | |
|
Description |
The device specified for the |
Action |
If TLI is being used, specify the correct network device pathname. | |
See Also |
| |
1615 |
ERROR: Identifier or number must be followed by white space or punctuation | |
|
Description |
While parsing a |
Action |
Correct the syntax and re-load the configuration file. | |
See Also |
| |
1624 |
ERROR: Invalid or unspecified administrative password | |
|
Description |
An administrative request generated by |
Action |
If no administrative password was specified locally, then determine an appropriate administrative password and set the local environment to pass it to remote sites as indicated in If an administrative password was specified locally, then either the local setting will have to change to match that expected by the remote site, or the administrative password used by this application will have to be added to the password file used by | |
See Also |
| |
1626 |
ERROR: Machine "pmid" cannot be of the form "name.number" | |
|
Description |
While parsing a UBBCONFIG file, an invalid machine name was specified. The name has a value of the form name.number (this is restricted only in the development copy, compiled to allow what is called fake mp). |
Action |
Correct the syntax error and re-load the configuration file. | |
See Also |
| |
1627 |
ERROR: LMID "value" must not contain comma | |
|
Description |
While parsing a UBBCONFIG file, an invalid LMID value was found. The LMID value contains a comma. |
Action |
Correct the syntax and re-load the configuration file. | |
See Also |
| |
1628 |
ERROR: LMID "value" must not contain comma | |
|
Description |
While parsing a UBBCONFIG file, an invalid LMID value was found. The LMID value contains a comma. |
Action |
Correct the syntax and re-load the configuration file. | |
See Also |
| |
1629 |
ERROR: Cannot allow only release 4.2.x BBLs to join system with a configuration of number machines or more | |
|
Description |
An attempt was made to boot a 4.2.x site into an application with more than number configured machines. |
Action |
Either reduce the number of configured machines and reboot the site, or upgrade the site to release 5.0.x or later. | |
See Also |
BEA TUXEDO Administrator's Guide | |
1631 |
ERROR: MAXMACHINES parameter must be >= number and < 8191 | |
|
Description |
The |
Action |
Correct the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1633 |
ERROR: MAXQUEUES parameter must be > 0 and < 8192 | |
|
Description |
The |
Action |
Correct the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1634 |
ERROR: MAXQUEUES(number) and MAXSERVERS(number) must be equal to interoperate with release number | |
|
Description |
An attempt was made to boot a 4.2.x site with the |
Action |
Either reconfigure the application to have equivalent values for these parameters and reboot the site, or upgrade the 4.2.x site to release 5.0.x or later. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1636 |
ERROR: MAXGROUPS parameter must be >= number and < 32767 | |
|
Description |
The |
Action |
Correct the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1638 |
ERROR: Invalid CMPLIMIT value string | |
|
Description |
The |
Action |
Correct the value for this parameter to the acceptable format and rerun | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1640 |
ERROR: NETLOAD parameter must be >= 0 | |
|
Description |
The |
Action |
Correct the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1642 |
ERROR: SPINCOUNT parameter must be >= 0 | |
|
Description |
The |
Action |
Correct the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1643 |
ERROR: More than MAXGROUPS(number) groups in configuration file | |
|
Description |
The application was configured to handle up to number configured server groups (see the |
Action |
Either reset the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1644 |
ERROR: More than MAXMACHINES(number) machines in configuration file | |
|
Description |
The application was configured to handle up to number configured machines (see the |
Action |
Either reset the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1645 |
ERROR: Illegal opcode (number) sent to tagent | |
|
Description |
An invalid opcode number was sent to the |
Action |
The most likely cause of this problem is a non-BEA TUXEDO system process incorrectly connecting to the BEA TUXEDO system listener ( | |
1646 |
ERROR: MAXGROUPS(num1) must be num2 to interoperate with release num3 | |
|
Description |
The configured value num1 for the maximum number of configured groups in the application (see the |
Action |
Either modify the value of this parameter in the configuration file and rerun | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1647 |
ERROR: Cannot migrate master from release num1 to release num2 | |
|
Description |
Master migration from a release num1 site to a num2 site was attempted. |
Action |
Change the backup site to be one of the same release as the master site. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1649 |
ERROR: Backup master is running invalid release number | |
|
Description |
The backup master site attempted to boot with an invalid release number. |
Action |
Either change the backup master site to one of the same release as the master site, or upgrade the backup master site release. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1651 |
ERROR: Cannot join system with DBBL running older release number | |
|
Description |
A BBL attempted to boot into an application with a master site running an older release than its own, number. |
Action |
Either run the older release on the site in question, or upgrade the master site to be one running the latest BEA TUXEDO system release desired. | |
1655 |
ERROR: SVCTIMEOUT parameter must not be < 0 | |
|
Description |
The |
Action |
Change the parameter value in the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1666 |
WARN: Could not terminate server(pid) processing after SVCTIMEOUT | |
|
Description |
The BBL could not abortively deactivate the server with process id pid after the server exceeded the configured |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1667 |
WARN: Server(pid) processing terminated after SVCTIMEOUT | |
|
Description |
The BBL has terminated the local server with process id pid using the |
Action |
Either increase the configured service timeout value, or modify the server to complete the service within the allotted time interval. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1668 |
WARN: Cannot shutdown BBL on machine. Clients and/or servers may be running | |
|
Description |
A shutdown request has been received, but the BBL cannot be shut down because processes are still attached. |
Action |
Check on what processes are running to see if they can be individually killed. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1669 |
ERROR: If SECURITY is not set, then AUTHSVC must not be specified. | |
|
Description |
While parsing a |
Action |
Correct the syntax and re-load the configuration file. | |
See Also |
| |
1670 |
ERROR: IPCKEY parameter must be > number and < 262143 | |
|
Description |
The |
Action |
Correct the value for this parameter in the configuration file and rerun | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1671 |
ERROR: Could not initialize /Admin service | |
|
Description |
The DBBL could not initialize the administrative services necessary for application administration. |
Action |
Consult the local userlog file and contact your BEA TUXEDO system Technical Support. | |
1672 |
ERROR: Could not initialize /Admin service | |
|
Description |
The BBL could not initialize the administrative services necessary for application administration. |
Action |
Consult the local userlog file and contact your BEA TUXEDO system Technical Support. | |
1673 |
ERROR: Invalid logical machine | |
|
Description |
While trying to handle a TMIB request for the T_NETWORK class, an invalid logical machine name (TA_LMID) was specified. |
Action |
Ensure that a valid logical machine name is specified (one that is already configured) and re-run the operation. | |
See Also |
| |
1674 |
ERROR: Failed to establish connection | |
|
Description |
While trying to satisfy a MIB request for the T_NETWORK class to change the state of a connection to ACTIVE, the connection failed. |
Action |
Ensure that the machine to which the connection is being made and the network are available and re-try the operation. | |
See Also |
| |
1675 |
ERROR: Unable to allocate buffer for master migration reply | |
|
Description |
An attempt dynamically to allocate memory from the operating system failed while trying migrate the master to the backup machine. No response will be returned to the requester of the operation. |
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. | |
1676 |
ERROR: System tables corrupted | |
|
Description |
An internal error occurred while trying to migrate the master. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1677 |
ERROR: Master migration attempted in non-LAN application | |
|
Description |
A master migration to the backup was requested but the configuration does not have the LAN option configured (and thus doesn't have a backup). |
Action |
No action required. | |
See Also |
| |
1678 |
ERROR: Invalid parameters for master migration | |
|
Description |
A master migration to the backup was requested, but the master and backup are on the same machine or the DBBL has already been migrated. This should not occur. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
1679 |
ERROR: Master migration failed, no available backup site | |
|
Description |
A master migration was requested but the BBL is not running on the backup site (or the site is already partitioned). |
Action |
The migration cannot occur in this situation. Make sure that the backup machine and the network are available, and that the application is booted on the machine. Then re-try the operation. | |
See Also |
| |
1680 |
ERROR: Master migration failed, could not modify queue parameters | |
|
Description |
A master migration was requested but the operation failed because the queue for the DBBL could not be re-set to take no more messages. This could occur if the queue were manually deleted or an error occurred with the IPC sub-system. |
Action |
Re-try the operation. For subsequent failures, shutdown and re-boot the application. | |
See Also |
| |
1681 |
ERROR: Master migration failed, could not requeue message | |
|
Description |
A master migration was requested but the operation failed because an error failed in putting a message on the queue for the DBBL. This could occur if the queue were manually deleted or an error occurred with the IPC sub-system (e.g., the message queues were full). |
Action |
Re-try the operation. | |
See Also |
| |
1682 |
ERROR: Could not retrieve own BB entry for migration | |
|
Description |
The |
Action |
After this shaky migration it is possible that a | |
See Also |
| |
1683 |
ERROR: Connection received from inactive machine lmid | |
|
Description |
The machine indicated by the logical machine identifier lmid attempted to connect to the local site but is not active in the application. |
Action |
This is caused when a partitioned live node is cleaned up in the non-partitioned part of the application (see the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1684 |
ERROR: Application initialization failure | |
|
Description |
Server failed to restart due to application initialization failure. |
Action |
This is an application specific failure and must be resolved with application knowledge of server initialization. | |
See Also |
BEA TUXEDO Programmer's Guide | |
1685 |
ERROR: Application initialization failure | |
|
Description |
Server failed to boot due to application initialization failure from |
Action |
Identify application initialization problem and resolve prior to booting the server again. | |
See Also |
BEA TUXEDO Programmer's Guide, | |
1686 |
ERROR: Older release sites cannot join an application with deleted machines in the *MACHINES section | |
|
Description |
An activation request was received for a a computer running a version prior to release 5.0. However, one or more machines were dynamically deleted from the configuration. A pre-5.0 machine cannot join the application in this situation. |
Action |
Shutdown the entire application and then re-boot (including the older release machines). | |
See Also |
| |
1687 |
ERROR: No active servers found in class instance | |
|
Description |
A deactivation (shutdown) request was received. However, based on the values of TA_SRVGRP, TA_SRVID, TA_GRPNO, TA_SERVERNAME, TA_LMID and TA_SEQUENCE for the T_SERVER class, no servers match the desired criteria and no servers will be deactivated. |
Action |
No action required. Check the activated servers and re-try the operation with valid selection criteria. | |
See Also |
| |
1688 |
ERROR: Could not retrieve information on servers | |
|
Description |
A deactivation (shutdown) request was received. However, based on the values of TA_SRVGRP, TA_SRVID, TA_GRPNO, TA_SERVERNAME, TA_LMID and TA_SEQUENCE for the T_SERVER class, no servers match the desired criteria and no servers will be deactivated. |
Action |
No action required. Check the activated servers and re-try the operation with valid selection criteria. | |
See Also |
| |
1689 |
ERROR: Could not shutdown any servers | |
|
Description |
A request was received to deactivate one or more servers. Although some servers matched the requested criteria, no servers were shutdown. This could be because the servers could not be contacted, they might be looping, or administrative servers might not shutdown because other clients or servers are still running. |
Action |
Re-try the operation. It may be necessary to request a forced shutdown, setting the state to DEAd, in which servers will be killed and administrative servers are shutdown even if clients exist. | |
See Also |
| |
1690 |
ERROR: System error (error_string) while shutting down server | |
|
Description |
A MIB request was received to shutdown a server but the request to the server failed, due to a system error. More information regarding the failure is printed as part of the message. For example, it could be that the message queues are full. |
Action |
Re-try the operation. | |
See Also |
| |
1691 |
ERROR: System server cannot shutdown with clients and/or servers attached | |
|
Description |
A TMIB request to shutdown an administrative server failed because one or more clients and/or servers is still active. |
Action |
Stop active clients and shutdown application servers before shutting down the administrative servers, or use a forced shutdown that ignores clients and kills application servers. | |
See Also |
| |
1692 |
ERROR: Application server will not shutdown | |
|
Description |
A TMIB request to shutdown an application server failed because server refused to shutdown. |
Action |
Use a forced shutdown, setting the state to DEAd, which kills application servers. | |
See Also |
| |
1693 |
WARN: Timeout period expired on /Admin blocking request | |
|
Description |
A MIB request was received to shutdown a server but the request to the server failed, due to timeout. This indicates that the server took too long to shutdown. This could indicate that the server is busy (or looping). |
Action |
Re-try the operation. To force a shutdown, set the state to DEAd. | |
See Also |
| |
1694 |
WARN: Alternate site for group is not currently active | |
|
Description |
A TMIB request was received to deactivate a server for migration to the backup site. The server was shutdown but the backup site is not available so the server cannot be re-activated on the backup. |
Action |
Issue another operation to activate the server on the backup site. | |
See Also |
| |
1695 |
WARN: Server not restartable, will not be migrated | |
|
Description |
A TMIB request was received to deactivate a server for migration to the backup site. The server was shutdown but the server is not configured to be restartable so the server cannot be re-activated on the backup. |
Action |
Issue another operation to activate the server on the backup site. | |
See Also |
| |
1696 |
ERROR: No active machines available for activation of server group | |
|
Description |
A TMIB request was received to activate a server, but the primary and backup machines for the group with which the server is associated are not active. |
Action |
Activate one of the associated machines before activating the application server. | |
See Also |
| |
1697 |
ERROR: Could not format command line options | |
|
Description |
A TMIB request to activate a server failed during processing to start the server. An attempt dynamically to allocate memory from the operating system failed. |
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. | |
1698 |
ERROR: Could not format command line arguments | |
|
Description |
A TMIB request to activate a server failed during processing to start the server. An attempt dynamically to allocate memory from the operating system failed. |
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. | |
1699 |
ERROR: Could not fork | |
|
Description |
While activating a server, the new program could not be started (forked or spawned). This usually indicates that system resources did not exist to allow for the execution (e.g., a shortage of process table entries or swap space). |
Action |
Check for administrative events that might keep a program from being started (either on the console, in administrative logs, or in the OS event monitor). Re-try the operation. | |
See Also |
|