Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	http://www.oracle.com/technology/documentation/index.html   |   Site Map   |   Search   |   PDF Files   |   Contact   |   Glossary
Tuxedo Doc Home   |   Messages   |   Catalog List   |   Previous   |   Next

LIBTUX Messages 400-499

400	ERROR: Invalid arguments for getting acknowledgement
	Description	This message is issued when an internal BEA TUXEDO system routine is passed invalid arguments.
	Action	Contact your BEA TUXEDO system Technical Support.
401	ERROR: Could not find DBBL
	Description	An attempt was made to send a message to the DBBL and its whereabouts could not be ascertained either from the BB or from a BRIDGE process.
	Action	Check for a partitioned network, corrupted shared memory, or if all administrative processes are running.
403	ERROR: Received message with an unknown internal type index val
	Description	While processing a reply, the internal buffer type is unknown. This refers to an internal system problem that could be caused, for example, by corrupted shared memory.
	Action	Contact your BEA TUXEDO system Technical Support.
404	ERROR: Received message of unknown type 'type' subtype 'subtype'
	Description	The process received a message whose type and subtype are not known. That is, the process' type switch was not built to recognize the type and/or subtype of the message received.
	Action	The process should be re-linked with the appropriate type switch including the type and subtype that are printed as part of this error message. Or, the process sending the offending type/subtype should be altered to send a buffer that the receiver understands.
	See Also	tuxtypes(5), ubbconfig(5)
405	ERROR: Received message of unknown type 'type'
	Description	The process received a message whose type is not known. That is, the process' type switch was not built to recognize the type of the message received.
	Action	The process should be re-linked with the appropriate type switch including the type that is printed as part of this error message. Or, the process sending the offending type should be altered to send a buffer that the receiver understands.
	See Also	tuxtypes(5), ubbconfig(5)
409	ERROR: Invalid table entry information given
	Description	While trying to retrieve the status field entry, the tmid passed in is invalid.
	Action	Contact your BEA TUXEDO system Technical Support.
410	ERROR: [Invalid table entry information given]
	Description	While trying to retrieve the status field entry, the tmid passed in is invalid.
	Action	Contact your BEA TUXEDO system Technical Support.
411	ERROR: [Invalid table information given]
	Description	While trying to retrieve the TMPROC information associated with the tmid specified, the entry is found to be invalid.
	Action	Contact your BEA TUXEDO system Technical Support.
412	ERROR: [Invalid table information given]
	Description	While trying to retrieve the TMPROC information associated with the tmid specified, the entry is found to be invalid.
	Action	Contact your BEA TUXEDO system Technical Support.
415	ERROR: Invalid transaction creation
	Description	While doing a warm start or load of the transaction log, an attempt to add an entry to the transaction table was invalid.
	Action	Contact your BEA TUXEDO system Technical Support.
416	WARN: Invalid state stateval for group groupname while adding transaction
	Description	While adding a transaction to the transaction table during warm start or load of the transaction log of decided transactions, the transaction table entry was found to have a group whose state indicated that the transaction was either normally or heuristically rolled back. The state will be overwritten and no further notification will be given as to the inconsistent state of the global transaction.
	Action	Since the transaction will most likely be driven through to completion, the rollback status indicates that the operation done by the rolled back transaction will be inconsistent. For instance, this could indicate inconsistent data in a data base. The action to reconcile this situation is application specific.
417	ERROR: warmstart found bad log page entry
	Description	While warm starting the transaction log, an inconsistent entry was found in the transaction table entry
	Action	Contact your BEA TUXEDO system Technical Support.
419	ERROR: Exit failure
	Description	This error occurs when the process is unable to detach from shared memory or a failure is detected while trying to release a request queue.
	Action	Contact your BEA TUXEDO system Technical Support.
421	ERROR: Memory allocation failure
	Description	A memory allocation failure occurs while the system is mapping the well known IPC key to an internal structure.
	Action	Remove processes that may be tying up physical memory, ensure that the application ipc key is correct, or verify that the UNIX sysgen process sizing parameters are correct.
422	ERROR: Cannot find own BB entry
	Description	While attempting to shut down a server, the bulletin board entry for the specified server cannot be found.
	Action	Try shutting the server down again. If this fails, you will have to use the UNIX system kill(1) command to remove the process.
423	ERROR: [Cannot update own queue]
	Description	While trying to update the server table entry, the server's queue entry cannot be accessed.
	Action	Contact your BEA TUXEDO system Technical Support.
424	ERROR: Cannot re-queue msg
	Description	During shutdown of a MSSQ set server, the shutdown message needs to be enqueued for each server instance. The message re-queuing has failed.
	Action	Contact your BEA TUXEDO system Technical Support.
425	ERROR: [Service receive: unknown meta-msg type: 0xmsg_type]
	Description	The meta message header type was of an unknown type.
	Action	Contact your BEA TUXEDO system Technical Support.
426	ERROR: [Service receive: cannot send meta-msg reply]
	Description	While advertising a new service, a reply is expected for the meta-message but fails.
	Action	Contact your BEA TUXEDO system Technical Support.
427	ERROR: [Cannot find own BB entry]
	Description	During the shutdown of a server the queue must be drained, and while the queue is being checked the getqcnt() call fails. This error may occur if the Bulletin Board is not locked or the queue information passed is in error.
	Action	Contact your BEA TUXEDO system Technical Support.
428	ERROR: Cannot re-queue msg
	Description	While trying to shut down a server, the sentinel message could not be queued.
	Action	Try to shut down the server again. If this fails, contact your BEA TUXEDO system Technical Support.
429	ERROR: Cannot perform shutdown at this time
	Description	An attempt is made to shut down a group of TMS processes in an invalid order. Specifying the TMS processes to be shut down by group, lmid, or (S) will order the shutdown sequence properly.
	Action	The TMSs should not be shut down individually (using the -i option). The -g -l -S flags should be used instead.
430	ERROR: Application rejects shutdown request
	Description	The application has denied a shutdown request. This error can occur in a variety of different scenarios. The system processes such as (D)BBL, TMS, or BRIDGE may reach a condition in which they are unable to shut down. For example, the BBL cannot process a shutdown request because a server fails to disconnect. Application servers may also reach this condition by returning a "0" value in the default shutdown function, _tmsvrstop(). If this occurs, contact your BEA TUXEDO system application administrator.
	Action	Check the userlog for other messages to determine the proper action to take. In the above example of a system process (BBL) unable to shut down, the force option (-w) may be used.
	See Also	tmshutdown(1)
431	ERROR: Service receive: cannot send meta-msg reply
	Description	While attempting to reply to a shutdown request, the meta-message send fails.
	Action	Contact your BEA TUXEDO system Technical Support.
433	ERROR: Send/receive error on remote procedure call
	Description	While trying to send a meta-message, the request cannot be sent. Possible causes may be a message type switch function failure, an invalid message length, or a low level message send failure.
	Action	Check for a partitioned network or corrupted shared memory. Check that all administrative processes are running and that the sysgen parms (IPC parameters) for messages are appropriate. Also check the userlog for additional messages that may help to isolate the problem. Contact your BEA TUXEDO system Technical Support.
439	ERROR: Migration failed: Not all the servers are shutdown
	Description	While attempting to migrate servers to another machine, the system is unable to process this request. All of the servers affected by this request must be shut down.
	Action	Shut down the desired servers with the relocate (-R) option and reissue the migrate request.
	See Also	BEA TUXEDO Administrator's Guide, tmadmin(1)
441	ERROR: Migration failed: alternate location not specified
	Description	When attempting to migrate server(s) to another site, the system is unable to complete the request because the alternate location is not specified for an affected server group(s).
	Action	The LMID entry in the GROUPS section for the affected server groups must be updated. This may be achieved by using the tmconfig() command and updating the TA_LMID field of the affected server groups to include the alternate location.
	See Also	BEA TUXEDO Administrator's Guide, tmadmin(1), tmconfig(1)
442	ERROR: Migration failed: alternate locations not the same
	Description	When attempting to migrate server(s) to another site, the system is unable to complete the request because the alternate locations specified for the affected server group(s) are not the same.
	Action	The appropriate action for this request depends on if the alternate locations are set properly or not. If the alternate locations of server groups on an lmid are different, they may be migrated independently by group. See the tmadmin() subcommand migrategroup. If the groups are to be moved to the same lmid, the LMID entry in the GROUPS section for the affected server groups must be updated. This may be achieved by using the tmconfig() command and updating the TA_LMID field of the affected server groups to specify the same alternate location. Then the request may be resubmitted.
	See Also	BEA TUXEDO Administrator's Guide, tmadmin(1), tmconfig(1)
445	INFO: BB on machine lmid has been updated for migration of group group_name.
	Description	During a migration request, this message is issued to point out that the bulletin board for the alternate location (lmid) has been updated.
	Action	No action necessary.
446	INFO: BB on machine lmid has been update for migration of groups from machine lmid.
	Description	During a migration request, this message is issued to point out that the bulletin board for the alternate location (lmid) has been updated.
	Action	No action necessary.
459	ERROR: Send to BRIDGE failed
	Description	While trying to get the status of a remote queue via tmadmin, the message to the remote BRIDGE failed.
	Action	Check the userlog for earlier messages indicating the cause of the failure.
460	ERROR: Send to BRIDGE failed
	Description	While trying to get the status of a remote queue via tmadmin, the message to the remote BRIDGE failed.
	Action	Check the userlog for earlier messages indicating the cause of the failure.
461	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to suspend the BRIDGE during a partitioned shutdown.
	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.
462	ERROR: Retrieved too many entries in tmsuspend
	Description	While trying to suspend the BRIDGE during a partitioned shutdown, the number of server entries retrieved is larger than the number of entries allocated for retrieval. This should not occur.
	Action	Re-run the tmshutdown command.
	See Also	tmshutdown(1)
463	ERROR: TMUSEBRANCH option not supported
	Description	When opening a resource manager with tpopen, the resource manager had the TMUSEBRANCH flag set from the XA Preliminary Specification. This option is not supported.
	Action	Contact your resource manager vendor.
466	ERROR: tpopen TPERMERR xa_open returned errstring
	Description	The call to xa_open from within tpopen returned the XA error value errstring.
	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.
467	ERROR: tpclose TPERMERR xa_close returned errstring
	Description	The call to xa_close from within tpclose returned the XA error value errstring.
	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.
470	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed while trying to put variables into the environment for either the machine or server ENVFILE.
	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.
474	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using malloc() failed while receiving a service request in a server.
	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.
476	WARN: Server groupid/serverid: client process processid: lost message
	Description	A server died and the specified server (with group groupid and server identifier serverid) is recovering on its behalf. A message from the client with the specified processid has been lost. Additional information will be printed in subsequent messages
	Action	No action required.
	See Also	See Messages 477 and 478 below.
477	WARN: SERVICE=servicename MSG_ID=msgid REASON=server died
	Description	A server died (see message 476) while processing service servicename. The client from which the message was sent is still active so a response message will be sent indicating the failure.
	Action	No action required.
478	WARN: SERVICE=servicename MSG_ID=msgid REASON=server and client died
	Description	A server died (see message 476) while processing service servicename. The client from which the message was sent is no longer active either so that a response message cannot be sent indicating the failure.
	Action	No action required.
480	ERROR: Cannot find own server entry
	Description	When receiving a service request in a server, the server was unable to find its own entry in the Bulletin Board.
	Action	Check the userlog for earlier messages indicating problems with the application and check with the application administrator. Contact your BEA TUXEDO system Technical Support.
481	ERROR: Service xa_start returned errno
	Description	A message request was received indicating that the message should be handled by the server in transaction mode and the corresponding xa_start failed. xa_start failed because the return code was out of range.
	Action	Perform the action appropriate for the indicated error.
482	ERROR: Service request found state state_val for group grpname
	Description	A message request was received indicating that the current transaction was to be committed, but the state of the transaction was neither active or aborted.
	Action	Check for a corrupted GTT in shared memory.
486	ERROR: Service request problem, tperrno = tperrno_val
	Description	A message request was received indicating that the message should be handled by the server in transaction mode and the corresponding tpbegin failed.
	Action	Verify that message was not received by an unsolicited message handler, the server was not part or registered with the application, the global transaction id was valid, the server had no outstanding reply messages, the resource manager was not opened, there was not enough space in the global transaction table, the resource manager xa_start failed, or a BBL lock or unlock failed.
487	ERROR: Cannot call ATMI routine without joining application
	Description	tpreturn was called and the server was no longer part of the application.
	Action	Either a tpsvrinit failed or a tpsvrdone was called before tpreturn.
488	ERROR: Invalid data pointer given to tpreturn()
	Description	tpreturn was given a pointer to a message that did not contain the appropriate magic numbers in the message header, or the address of the message did not begin on a long word boundary.
	Action	Check that the application's IPCKEY is correct, or two applications are using the same IPCKEY, or the message queue isn't corrupted, or a previously tpalloc 'ed message was invalidated (via a tpfree) before tpreturn was called.
489	ERROR: Performed tpreturn() with outstanding replies
	Description	A tpreturn was called with outstanding message replies.
	Action	Check the service code and make sure that tpreturn is not called before all the tpacall and tpgetrply 's are complete, all outstanding messages sent to other services have returned, and/or there are not two applications using the same IPCKEY.
495	ERROR: tpreturn tpcommit reported tperrno_msg
	Description	The service automatically started a transaction. tpreturn performed a tpcommit and it failed with a tperrno_val other than TPEABORT. The specific error is reported as part of this message.
	Action	Respond according to the type of error indicated in the message.
499	ERROR: Invalid table entry information given
	Description	A table id was passed to the update routine that did not correspond to the server, queue, or service (the manner in which information is arranged in the BB).
	Action	Check for corrupted shared memory or an invalid IPCKEY (wrong application).