|
|
1000 |
ERROR: System clock has been reset to prior time. Reset again to time after time. | |
|
Description |
The system clock as been reset such that the current time precedes the timestamps in the transaction log. |
Action |
Reset the system clock to the correct time. Retry the operation again, and if the problem persists, contact your BEA TUXEDO system Technical Support. | |
1001 |
ERROR: Cannot receive reply because MSSQ is specified but REPLYQ is N | |
|
Description |
An error has occurred in receiving a reply from either a tpcall(3c) or |
Action |
If the server is expected to receive | |
See Also |
| |
1002 |
ERROR: tpforward called in conversational server; service error returned to originator | |
|
Description |
|
Action |
The service routine should be changed to use | |
See Also |
| |
1003 |
ERROR: xa_end flags returned error status | |
|
Description |
This message is issued if the process receiving a reply encounters an error upon calling the database resource manager with xa_end(). The transaction fails to commit. The message prints the error code that the function returned. |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. | |
1004 |
ERROR: xa_abort returned error | |
|
Description |
This message is issued when BEA TUXEDO tries unsuccessfully to rollback a transaction via xa_rollback() after receiving a reply. The message prints the error code that the function returned. |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. See the userlog for more information on the outcome of the transaction. Also, use tmadmin's printtrans command to find out more information about the transaction. | |
1005 |
INFO: Switched to dip-in based notification | |
|
Description |
When the client is joining the application, the specified or default notification is set to signal based. But to use signal based notification, the userid must be the administrator's. This message alerts the switch in the notification mechanism. |
Action |
No action necessary. | |
1006 |
INFO: Using dip-in based notification instead of application default setting | |
|
Description |
When the client is joining the application, the notification mechanism is set to signal based (the application default). But to use signal based notification, the user must be the administrator. This message alerts the switch in the notification mechanism. |
Action |
No action necessary. | |
1007 |
INFO: Notification mechanism unknown. Switching to dip-in based notification | |
|
Description |
The notification mechanism is not specified, so the default (dip-in based) is used. |
Action |
No action necessary. | |
1013 |
ERROR: Migration failed: invalid type | |
|
Description |
The migration type code passed to the migration function is not valid. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1014 |
ERROR: Migration failed: Memory allocation failure | |
|
Description |
An attempt to dynamically 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. | |
1015 |
ERROR: Migration failed: Memory allocation failure | |
|
Description |
An attempt to dynamically 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. | |
1016 |
ERROR: Migration failed: Memory allocation failure | |
|
Description |
An attempt to dynamically 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. | |
1017 |
ERROR: Migration failed: no group name | |
|
Description |
The group name passed to the migration function was empty. |
Action |
Verify that the group name for the migration request is valid. If so, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
1018 |
ERROR: Migration failed: bad group name, tperrno = tperrno_val | |
|
Description |
The group name passed to the migration function was invalid. |
Action |
Verify that the group name for the migration request is valid. If so, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
1019 |
ERROR: Migration failed: no machine name | |
|
Description |
The machine name passed to the migration function was empty. |
Action |
Verify that the machine name for the migration request is valid. If so, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
1020 |
ERROR: Migration failed: bad machine name, tperrno = tperrno_val | |
|
Description |
The machine name passed to the migrate function was invalid. |
Action |
Verify that the machine name for the migration request is valid. If so, contact your BEA TUXEDO system Technical Support. | |
1021 |
ERROR: Migration failed: invalid current location | |
|
Description |
The entry in the server group table for the current lmid (the location that the servers are to be migrated from) is invalid. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1023 |
ERROR: Migration failed: cannot update server group information | |
|
Description |
An attempt failed trying to update the entry or entries in the server group table. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1024 |
ERROR: Migration failed: cannot update server information | |
|
Description |
While updating the local bulletin board, an error occurred. This error could be caused by the following:
|
Action |
Check the userlog for more information. | |
1026 |
ERROR: Migration failed: cannot migrate group on machine | |
|
Description |
A request to migrate the server group(s) to the BBL on the alternate location has failed. This error could be caused by the following:
|
Action |
Check the userlog for more information. | |
1027 |
ERROR: Migration failed: cannot retrieve new server information | |
|
Description |
The verification of the alternate location has failed. The bulletin board has been checked for consistency, and one of the following errors has happened:
|
Action |
Check the userlog for additional information to properly diagnose this error. | |
1029 |
ERROR: Migration failed: cannot find BBL information for lmid | |
|
Description |
An attempt to retrieve the server table entry for the servers to be migrated failed. The requested entry was not found. This error is probably the result of an internal corruption of the bulletin board and not the result of anything the user has done. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1030 |
ERROR: Migration failed: cannot retrieve BBL information for lmid, tperrno = tperrno_val | |
|
Description |
An attempt to retrieve the server table entry for the servers to be migrated failed. This error is probably the result of an internal corruption of the bulletin board and not the result of anything the user has done. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1031 |
ERROR: Migration failed: cannot make request message | |
|
Description |
Creating an internal system message for the migrating servers fails. This error is due to the inability to allocate enough memory for the message. |
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 physical memory usage on the machine or increase the amount of physical memory on the machine. | |
1032 |
ERROR: Migration failed: cannot send service request to BBL on lmid | |
|
Description |
The service request to start the migrating servers on the new site has failed. |
Action |
Check the userlog for additional information to determine the proper action to be taken. | |
1033 |
ERROR: Migration failed: invalid response from BBL on lmid | |
|
Description |
The response for the request to start the migrated servers on lmid returns an error. The bulletin board on the machine lmid was unstable at the time of the migration request and therefore was aborted. |
Action |
Check the status of the bulletin board on lmid by using the | |
See Also |
| |
1034 |
ERROR: Migration failed: invalid response from BBL on lmid, tperrno = tperrno_val | |
|
Description |
The response for the request to start the migrated servers on lmid returns an unknown status code. The bulletin board on the machine lmid was unstable at the time of the migration request and therefore was aborted. |
Action |
Check the status of the bulletin board on lmid by using the | |
See Also |
| |
1035 |
ERROR: Migration failed: cannot lock BB, tperrno = tperrno_val | |
|
Description |
While confirming that all relevant servers are shut down for migration, the lock for the bulletin board has not been granted. |
Action |
This may be the result of a transitive failure of a process attached to the bulletin board. Try the command again; if this fails, contact your BEA TUXEDO system Technical Support. | |
1036 |
ERROR: Migration failed: cannot retrieve server information, tperrno = tperrno_val | |
|
Description |
While confirming that all relevant servers are shut down for migration, the server information in the bulletin board cannot be retrieved. |
Action |
This may be the result of a transitive failure of a process attached to the bulletin board. Try the command again; if this fails, contact your BEA TUXEDO system Technical Support. | |
1037 |
ERROR: Migration failed: server not shutdown | |
|
Description |
While attempting to migrate server(s) to another machine, the system is unable to process this request because a server remains running. All of the servers affected by this request must be shut down before a migration command is issued. |
Action |
Shut down the desired servers with the relocate (-R) option and retry the request. | |
1038 |
ERROR: Migration failed: cannot unlock BB, tperrno = tperrno_val | |
|
Description |
While attempting to update internal information of server(s) to be migrated, the local bulletin board is unable to be unlocked. |
Action |
This may be the result of a transitive failure of a process attached to the bulletin board. Try the command again; if this fails, contact your BEA TUXEDO system Technical Support. | |
1039 |
ERROR: Migration failed: cannot lock BB, tperrno = tperrno_val | |
|
Description |
While attempting to update internal information of server(s) to be migrated, the local bulletin board is unable to be locked. |
Action |
This may be the result of a transitive failure of a process attached to the bulletin board. Try the command again; if this fails, contact your BEA TUXEDO system Technical Support. | |
1040 |
ERROR: Migration failed: cannot retrieve queue information, tperrno = tperrno_val | |
|
Description |
While attempting to update the queue table entry of the servers to be migrated, the queue table entry cannot be retrieved. This error is probably the result of an internal corruption of the bulletin board and not the result of anything the user has done. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1041 |
ERROR: Migration failed: cannot update server information, tperrno = tperrno_val | |
|
Description |
While attempting to update the server table entry for the servers to be migrated, the required entry cannot be retrieved. This error is probably the result of an internal corruption of the bulletin board and not the result of anything the user has done. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1042 |
ERROR: Migration failed: cannot unlock BB, tperrno = tperrno_val | |
|
Description |
While attempting to update internal information of server(s) to be migrated, the local bulletin board is unable to be unlocked. |
Action |
This may be the result of a transitive failure of a process attached to the bulletin board. Try the command again; if this fails, contact your BEA TUXEDO system Technical Support. | |
1043 |
ERROR: Migration failed: time out occurred | |
|
Description |
During the verification of the alternate location after the servers have been migrated, a failure has occurred. The verification request has timed out. |
Action |
Check the status of the bulletin board on the alternate location. This may be accomplished by using the | |
See Also |
| |
1044 |
ERROR: Migration failed: cannot lock BB, tperrno = tperrno_val | |
|
Description |
During the migration verification of the alternate location after the servers have been migrated, a failure has occurred. The bulletin board was not able to be locked. |
Action |
This may be the result of a transitive failure of a process attached to the bulletin board. Try the command again; if this fails, contact your BEA TUXEDO system Technical Support. | |
1045 |
ERROR: Migration failed: server(server_id/group_id) failed to migrate, tperrno = tperrno_val | |
|
Description |
The bulletin board of an alternate location reported that the server information requested was not found. This error is probably the result of an internal corruption of the bulletin board and not the result of anything the user has done. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1046 |
ERROR: Migration failed: cannot retrieve server (server_id/group_id) information, tperrno = tperrno_val | |
|
Description |
The bulletin board of an alternate location reported that the server information requested was not found. This error is probably the result of an internal corruption of the bulletin board and not the result of anything the user has done. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1047 |
ERROR: Migration failed: cannot unlock BB, tperrno = tperrno_val | |
|
Description |
During the migration verification of the alternate location after the servers have been migrated, a failure has occurred. The bulletin board was not able to be unlocked (or released). |
Action |
This may be the result of a transitive failure of a process attached to the bulletin board. Try the command again; if this fails, contact your BEA TUXEDO system Technical Support. | |
1048 |
ERROR: Migration failed: server (server_id/group_id) still cleaning | |
|
Description |
The verification of the alternate location has failed because the server server_id is still cleaning up its entries in the bulletin board. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1052 |
ERROR: Request/response request received in conversational server | |
|
Description |
A message request was received by a conversational server from a request/response server. |
Action |
Verify that the service name used in a tpcall, tpacall, or tpforward belongs to a request/response server and not a conversational server. | |
1053 |
ERROR: Conversational request received in request/response server | |
|
Description |
A message request was received by a request/response server from a conversational server. |
Action |
Verify that the service name in tpconnect belongs to a conversational server and not a request/response server. | |
1055 |
ERROR: Memory allocation failure | |
|
Description |
While attempting to restart a server, the BEA TUXEDO system needed to allocate a memory buffer. This memory allocation failed. |
Action |
Contact your UNIX Administrator. | |
1056 |
ERROR: Char range with MAX as lower value has values out of order | |
|
Description |
If MAX is specified for the char lower routing range, then its corresponding upper routing range must also be specified as MAX. That is: MAX - MAX: server_group |
Action |
Check the char routing range in the ROUTING section of the UBBCONFIG file. If MAX is specified for the lower routing range, then its corresponding upper routing range must be MAX. | |
See Also |
| |
1057 |
ERROR: Char range with MIN as upper value has values out of order | |
|
Description |
If MIN is specified for the char upper routing range, then its corresponding lower routing range must also be specified as MIN. That is: MIN - MIN: server_group |
Action |
Check the char routing range in the ROUTING section of the UBBCONFIG file. If MIN is specified for the upper routing range, then its corresponding lower routing range must be MIN. | |
See Also |
| |
1058 |
ERROR: Range values out of order for the packed decimal routing data | |
|
Description |
The range values for the packed decimal routing data are out order, that is, the upper range value is less than the lower range value. |
Action |
Check routing range values for the packed decimal routing data in your UBBCONFIG file. The lower range value must be less than or equal to the upper range value. | |
See Also |
| |
1059 |
ERROR: Invalid format for decimal | |
|
Description |
The data for a decimal routing range is specified incorrectly. |
Action |
Check routing range decimal data in the ROUTING section of the UBBCONFIG file. The data must be in the correct format. | |
See Also |
| |
1060 |
ERROR: Cannot have a '-' in front of MAX or MIN | |
|
Description |
The routing range cannot have a '-' sign in front of the MAX or MIN value. |
Action |
Check the routing range data in the ROUTING section of the UBBCONFIG file. Remove any '-' sign in front of the MAX or MIN value. | |
See Also |
| |
1061 |
ERROR: Cannot have a '-' and a '+' sign in front of a number | |
|
Description |
The routing range cannot have both a '-' and a '+' sign in front of a number. |
Action |
Check the routing range data in the ROUTING section of the UBBCONFIG file. If a '-' and a '+' sign are both in front of a number, remove the '+' sign. | |
See Also |
| |
1065 |
ERROR: xa_end TMSUSPEND returned errstring | |
|
Description |
The process called |
Action |
Contact your BEA TUXEDO system Technical Support or database system vendor. | |
1066 |
ERROR: xa_start TMRESUME returned errstring | |
|
Description |
The process called |
Action |
Contact your BEA TUXEDO system Technical Support or database system vendor. | |
1067 |
ERROR: Request/response service name matches conversational service name | |
|
Description |
An error occurred while a service was being added to the bulletin board's tables. The same service name cannot be used for both conversational and request/response types of services. |
Action |
Rename the services being offered so that the each service name is used consistently throughout the system as either conversational or request/response. | |
See Also |
| |
1074 |
ERROR: Connection information invalid | |
|
Description |
This error occurs when a client or server is requesting to create a connection table entry 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. | |
1076 |
ERROR: Tried to set up a duplicate connection | |
|
Description |
This error occurs when a client or server is requesting to create a connection table entry in the Bulletin Board and tries to set up a duplicate entry. This happens if there is a bug in the calling routine. |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
1077 |
ERROR: Bad event: status | |
|
Description |
This error occurs when |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
1078 |
ERROR: errno TPEEVENT but event flag not set | |
|
Description |
This error occurs when tprecv(3c) gets a message from the other end of a conversation and the tperrno information in the message header is set to TPEEVENT and the event is set to zero. |
Action |
Report this failure to your BEA TUXEDO system Technical Support. | |
1079 |
ERROR: Failed to create connection | |
|
Description |
This error occurs when |
Action |
Increase the number of connection table entries in the Bulletin Board by increasing the MAXCONV parameter in the UBBCONFIG file. | |
See Also |
| |
1080 |
WARN: Failed to disconnect process pid | |
|
Description |
This error occurs when a conversational disconnect event is sent by a server to a client on the same machine via a message, and the server is unable to send the message to the client. The client could have died before the disconnect event is sent or if there is an error queueing the message. |
Action |
Check the UNIX message queue kernel parameters and increase them if necessary. | |
1081 |
ERROR: Failed to allocate space for disconnect msg | |
|
Description |
This error occurs when a conversational disconnect message is sent to the BBL and there is not enough memory in the system to allocate the message. |
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 |
| |
1082 |
ERROR: Disconnect failed, couldn't find BBL | |
|
Description |
This error occurs when a conversational disconnect message has to be sent to the BBL and the server table entry for the BBL is missing from the Bulletin Board. This is a severe error and the system is unstable. |
Action |
Contact the BEA TUXEDO system administrator and restart the BEA TUXEDO system. | |
1083 |
ERROR: Disconnect failed, message send/receive error | |
|
Description |
This error occurs when a conversational disconnect event is sent by a process to the remote BBL via a message, and the server is unable to send the message to the BBL. This can happen if the limit on the number of bytes on the message queue is reached. |
Action |
Check the UNIX system message queue kernel parameters and increase them if necessary. | |
1084 |
ERROR: Failed to get acknowledgement message for connection | |
|
Description |
This error occurs when a conversational client or server issues a |
Action |
Check the UNIX message queue kernel parameters and increase them if necessary. Check the userlog for error messages regarding the remote server. | |
1085 |
ERROR: Invalid mid value during spawn | |
|
Description |
While getting ready to spawn a conversational server, the calling process failed to retrieve its machine table entry. The machine identifier that is used to retrieve the entry is invalid. The conversational server will therefore not be spawned. |
Action |
Look through the userlog to see if there are other messages related to this failure. If so, refer to the appropriate system messages. Otherwise, contact your BEA TUXEDO system Technical Support. | |
1086 |
ERROR: Argument vector formation error during spawn | |
|
Description |
While getting ready to spawn a conversational server, the calling process failed to build the command line arguments for that server. An attempt to dynamically 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. | |
1087 |
ERROR: aout=aout: too many arguments | |
|
Description |
While getting ready to spawn a conversational server, the calling process failed to set the argument vector for that server. The calling process attempted to pass more than 256 arguments to the conversational server. The conversational server will therefore not be spawned. |
Action |
Make sure the number of arguments passed to the conversational server is not greater than 256. Note that the system may be adding up to eight arguments to the command line obtained from the configuration file. | |
See Also |
| |
1088 |
ERROR: spawn error: cannot fork | |
|
Description |
The calling process failed to spawn a conversational server. The call to |
Action |
The system-imposed limit on the total number of processes under execution by a single user may be exceeded. In this case you may either reduce the number of processes the BEA TUXEDO system application administrator is running on the system or increase the total number of processes allowed per user by reconfiguring the UNIX kernel. | |
See Also |
| |
1089 |
ERROR: Cannot exec, executable file not found | |
|
Description |
The calling process failed to spawn a conversational server. The call to |
Action |
Make sure the conversational server is in the application directory. | |
See Also |
| |
1090 |
ERROR: Cannot exec, network send error | |
|
Description |
The calling process failed to spawn a conversational server due to a networking problem. |
Action |
Make sure the network has not been partitioned and that the remote site is booted. If the remote site is not booted, call | |
See Also |
| |
1091 |
WARN: process id=pid ... Assume started (network). | |
|
Description |
The calling process attempted to spawn a conversational server. The conversational server with a process ID of pid is believed to have been started. However the calling process did not receive an acknowledgment. |
Action |
Make sure a conversational server with process ID pid is running. If not, look for a core dump in the application directory. | |
1092 |
WARN: process id=pid ... Assume started (pipe). | |
|
Description |
The calling process attempted to spawn a conversational server. The conversational server with a process ID of pid is believed to have been started. However the calling process did not receive an acknowledgment. |
Action |
Make sure a conversational server with process ID pid is running. If not, look for a core dump in the application directory. | |
1094 |
ERROR: No BBL available, cannot boot | |
|
Description |
The calling process failed to spawn a conversational server. The BBL is not active. |
Action |
Make sure the BBL is booted on the site the conversational server is being spawned. Use | |
See Also |
| |
1095 |
ERROR: No DBBL available, cannot boot | |
|
Description |
The calling process failed to spawn a conversational server. The DBBL is not active on the master site. |
Action |
Make sure the DBBL is booted on the master site. Use | |
See Also |
| |
1096 |
ERROR: Spawning process failed. | |
|
Description |
The calling process failed to spawn a conversational server. |
Action |
Look through the userlog to see if there are other messages related to this failure. If so, refer to the appropriate system messages. Otherwise, contact your BEA TUXEDO system Technical Support. | |
See Also |
See Messages No. 1097 and 1098 below | |
1097 |
ERROR: Process process at site failed with /T error (errmsg) | |
|
Description |
The calling process failed to spawn a conversational server, process. The spawned server failed on site site. |
Action |
Take corrective measures based on errmsg. | |
1098 |
ERROR: Process process at site failed with code code | |
|
Description |
The calling process failed to spawn a conversational server, process. The spawned server failed on site site. |
Action |
Take corrective measures based on error code code. | |
1099 |
ERROR: Cannot process a message with an unknown release, release | |
|
Description |
An invalid release number, release, was found in a message while being converted. Interoperability allows a single application to have multiple (two) releases of the BEA TUXEDO system exist on different nodes and interoperate with one another. The conversion is done by either the sender, if it has the latest software, or the receiver. |
Action |
Check the release of the BEA TUXEDO system software and make sure that the master and backup nodes are running the later release. Also make sure the TUXDIR parameter is set correctly in the configuration file. | |
See Also |
BEA TUXEDO Administrator's Guide |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|