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

CMDTUX Messages 600-699

601	ERROR: Memory allocation failure for receive buffer
	Description	An attempt to dynamically allocate memory from the operating system using malloc() failed while allocating a buffer to receive network messages.
	Action	Ensure that 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.
602	ERROR: Network access error
	Description	There are two possible causes: A networking error was encountered when sending back a reply message. The requesting process was running a version of the BEA TUXEDO system more than one release old. Interoperability is supported with only one previous release.
	Action	Check for and resolve any networking problems. Upgrade the BEA TUXEDO system version on the remote machine.
603	ERROR: Memory allocation failure
	Description	An attempt to dynamically allocate memory from the operating system using malloc() failed while the tagent was processing a request.
	Action	Ensure that 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.
604	ERROR: Could not decode request message
	Description	The tagent process received an invalid request message that it could not decode.
	Action	Verify that the correct release of the BEA TUXEDO system is running on both machines. The master machine can be at most one release ahead of other machines in the network. Contact your BEA TUXEDO system Technical Support.
605	ERROR: Could not set uid/gid for request
	Description	The tagent process received a failure from the setgid() or setuid() kernel calls. This indicates that it is not running with the correct login user id or group id.
	Action	The tlisten process must be started with a UNIX user id and group id that matches the configuration file. Refer to the UID and GID parameters of the RESOURCES and MACHINES sections.
	See Also	ubbconfig(5)
606	ERROR: Invalid version number for request
	Description	The tagent process received a request from an incompatible version of the BEA TUXEDO system.
	Action	Verify that the correct release of the BEA TUXEDO system is running on both machines. The master machine can be at most one release ahead of other machines in the network.
607	ERROR: Error encoding reply message
	Description	A reply message from the tagent process could not be encoded.
	Action	Contact your BEA TUXEDO system Technical Support.
609	ERROR: Invalid arguments for opcode
	Description	The tagent process received a request message containing invalid argument values.
	Action	Contact your BEA TUXEDO system Technical Support.
610	ERROR: Could not creat temp file for TUXCONFIG
	Description	The tagent process could not create or write a temporary file for propagation of the configuration file.
	Action	Check the directory permissions and free disk space in the system's temporary file directory. The tagent uses UNIX's tmpnam() library function to obtain temporary file names.
611	ERROR: tmloadcf failed when creating new configuration file
	Description	The tagent process was attempting to load a new configuration file, and tmloadcf failed.
	Action	Examine tmboot output for any userlog or error messages. Verify that $TUXDIR/bin/tmloadcf exists and is executable. Verify that the TUXCONFIG file name, directory permissions, and file permissions are set correctly. If the TUXCONFIG file already exists, try removing it and then running tmboot again. If these steps fail, contact your BEA TUXEDO system Technical Support.
612	ERROR: Could not set environment variable
	Description	The tagent process encountered an error when attempting to set an environment variable using UNIX's putenv() call.
	Action	Remove any unnecessary UNIX System environment variables that may have been set when tlisten was started. Expand the UNIX kernel per-process limit for environment variables.
613	ERROR: Could not retrieve parameters from TUXCONFIG file
	Description	The tagent process encountered an error when attempting to read an existing TUXCONFIG file.
	Action	Contact your BEA TUXEDO system Technical Support.
614	ERROR: Unknown error, terminating
	Description	The tagent process encountered an unknown error.
	Action	Contact your BEA TUXEDO system Technical Support.
615	INFO: Terminating tlisten process
	Description	The tlisten process will print this message in the tlisten log file when terminating. The only valid exit for the tlisten process is when it receives a SIGTERM termination signal.
	Action	No action required.
	See Also	tlisten(1)
617	ERROR: Invalid tlisten option option
	Description	An invalid option, option, was passed to tlisten.
	Action	Select the appropriate option(s) from the usage line that follows the message.
	See Also	tlisten(1)
624	ERROR: tlisten network address not specified
	Description	The user needs to pass the network address where the tlisten process is to listen for connection requests. The address should be passed as an argument to the -l option.
	Action	Invoke tlisten with the -l nlsaddr option. The value passed as nlsaddr should be the same as that specified for the NLSADDR parameter in the NETWORK section of the configuration file.
	See Also	tlisten(1), ubbconfig(5)
626	ERROR: tlisten could not find entry for user username
	Description	The user has the option to reset the user id and group id of the tlisten process through the -u option. If the user id or user name passed as an argument is invalid, the tlisten process will print this message and terminate.
	Action	Verify that the argument to the tlisten -u option is a valid user id or user name.
	See Also	tlisten(1)
627	ERROR: tlisten cannot run as root
	Description	The tlisten process was most likely invoked by root. For security purposes, this is not allowed.
	Action	The user should use the -u option to specify an alternate user id or user name instead of root, or invoke the tlisten process from another login.
	See Also	tlisten(1)
628	ERROR: tlisten could not set user id to user_name
	Description	The tlisten process failed to reset its user id.
	Action	Verify that the user name or user id passed as an argument to the -u option has a valid entry in the /etc/passwd file.
	See Also	tlisten(1)
629	ERROR: tlisten invoked by non-root, can't change user id.
	Description	The user id of the tlisten process may only be changed if the tlisten process was originally invoked by root. When invoked by someone other than root, the user id of the tlisten process may not be reset.
	Action	If the user wishes to have the tlisten process run with a specific user id, tlisten should either be invoked by that user, or by root. When invoked by root, the -u option should be used to reset the user id.
	See Also	tlisten(1)
636	WARN: Error sending acknowledgment back to requester
	Description	The tlisten process was unable to send an acknowledgment back to the requester. The problem associated with this error is not likely to be caused by something that the invoker of the tlisten process will have done. Nor is it likely to be a BEA TUXEDO system error.
	Action	Try repeating the same operation. If this fails with the same error, contact your UNIX System administrator or your BEA TUXEDO system Technical Support.
	See Also	tlisten(1)
642	ERROR: Invalid service request received, bad message header
	Description	The DBBL or BBL process received an invalid service request message. It will be ignored.
	Action	Contact your BEA TUXEDO system Technical Support.
644	ERROR: Cannot remove BRIDGE on machine machine
	Description	The DBBL process could not remove the bulletin board entry for machine's BRIDGE process.
	Action	Contact your BEA TUXEDO system Technical Support.
645	ERROR: Cannot unregister BBL on machine machine
	Description	The DBBL process could not remove the bulletin board entry for machine's BBL process.
	Action	Contact your BEA TUXEDO system Technical Support.
646	ERROR: Could not restore DBBL entry after temp change for shutdown
	Description	The DBBL 's server table entry in the bulletin board had been temporarily modified to allow a partitioned shutdown. The original entry could not be restored.
	Action	Contact your BEA TUXEDO system Technical Support.
647	ERROR: Failed to update status of restarting BRIDGE
	Description	The local BRIDGE process was marked in the bulletin board as restarting when a new bulletin board upload arrived. This status could not be restored after the upload request was processed.
	Action	Contact your BEA TUXEDO system Technical Support.
648	ERROR: DBBL should not receive an O_MIGGRPS opcode
	Description	The DBBL process received an internal migration operation code intended for BBLs only. The request will be ignored.
	Action	Contact your BEA TUXEDO system Technical Support.
649	ERROR: BBL should not receive an O_UPDGRPS opcode
	Description	A BBL process received an internal operation code intended for DBBLs only. The request will be ignored.
	Action	Contact your BEA TUXEDO system Technical Support.
650	ERROR: Could not create message queue for temporary DBBL
	Description	A temporary DBBL was being created for partitioned shutdown. There was an error when creating its message queue.
	Action	Contact your BEA TUXEDO system Technical Support.
651	ERROR: Could not update bulletin board for temporary DBBL
	Description	A temporary DBBL was being created for partitioned shutdown. There was an error when updating its server table entry in the bulletin board.
	Action	Contact your BEA TUXEDO system Technical Support.
652	ERROR: Could not create message queue for DBBL migration
	Description	The DBBL process is migrating to this machine. However, a message queue could not be created for it.
	Action	If after the migration the DBBL process is not running on either the master or backup machine, try a partitioned shutdown and reboot of the master. If this does not solve the problem, contact your BEA TUXEDO system Technical Support.
	See Also	tmboot(1), tmshutdown(1)
653	ERROR: Could not update DBBL server table entry for migration
	Description	The DBBL process is migrating to this machine. However, its new server table entry in the bulletin board could not be updated.
	Action	If after this migration the DBBL process is not running on either the master or backup machine, try a partitioned shutdown and reboot of the master. If the error persists, contact your BEA TUXEDO system Technical Support.
654	ERROR: Could not retrieve own bulletin board entry for migration
	Description	The DBBL process is migrating to another machine. However, it could not find its own server table entry in the bulletin board. This prevents the old DBBL from broadcasting where the new DBBL is located.
	Action	After this migration it is possible that a DBBL process is running on both the master or backup machines. If so, shut down the machine with the newest one (that is, the destination of the last migrate command). Then boot that machine up and try to migrate again. If the error persists, contact your BEA TUXEDO system Technical Support.
	See Also	tmboot(1), tmshutdown(1)
655	INFO: Exiting system for migration from mach1 to mach2
	Description	The DBBL process has migrated to another machine. The old DBBL outputs this message just before exiting.
	Action	No action required.
	See Also	tmadmin(1) migrate command
656	ERROR: DBBL should not receive an O_WARMSTART opcode
	Description	The DBBL process received an internal operation code intended for BBLs only. The request will be ignored.
	Action	Contact your BEA TUXEDO system Technical Support.
657	ERROR: DBBL should not receive an O_LOADTLOG opcode
	Description	The DBBL process received an internal operation code intended for BBLs only. The request will be ignored.
	Action	Contact your BEA TUXEDO system Technical Support.
662	ERROR: Incompatible TLOG file
	Description	The data file being loaded into the TLOG assumes a different maximum number of groups involved per transaction than this BEA TUXEDO system software release allows.
	Action	Contact your BEA TUXEDO system Technical Support.
663	INFO: Exiting system
	Description	A temporary DBBL that was running to facilitate partitioned shutdown is now exiting.
	Action	No action required.
664	ERROR: Service request from process pid failed
	Description	A serious failure occurred when processing a service request, and an error response message could not be returned to the originator. Possible causes of the error are: memory allocation failure, software version mismatch, or a shutdown is in progress. pid is the UNIX System process id number of the requester. However, it might be located on a remote machine.
	Action	Contact your BEA TUXEDO system Technical Support.
665	ERROR: Could not unsuspend reconnected node nodename
	Description	nodename is a remote machine that had been previously partitioned. It is now back and reconnected to the DBBL. There was a problem unsuspending nodename's services while accepting it back into the network. It will remain partitioned.
	Action	On the master machine, perform a tmadmin pclean command for the partitioned node. On the partitioned machine, do a partitioned shutdown and then reboot.
	See Also	tmadmin(1), pclean command, tmshutdown(1), tmboot(1)
668	WARN: Stale message received from BBL on machine machinename
	Description	During collection of responses to a DBBL broadcast, a stale message (from a previous broadcast) was received from machinename's BBL. The stale message will be ignored.
	Action	Check the status of machinename, and its network connections.
669	WARN: Stray string received from process pid
	Description	During collection of responses to a DBBL broadcast, an ACK or NACK message was received from an unrecognized process. The ACK/NACK message will be ignored.
	Action	No action required.
670	ERROR: Cannot restore message queue, key queuekey
	Description	If the DBBL 's UNIX System message queue is ever removed, the DBBL will attempt to recreate it. This should never happen, but the DBBL has recovery code for extra reliability. This error means the message queue recovery code itself failed. It is a serious error because the DBBL cannot function without a message queue.
	Action	Use the UNIX System kill command to force a DBBL restart. If it does not restart successfully within a few minutes, contact your BEA TUXEDO system Technical Support.
	See Also	kill(1) in UNIX System reference manuals
672	INFO: Sending BBL on machine name new version of bulletin board
	Description	The BBL on machine name is being sent a new copy of the bulletin board by the DBBL. This would occur if a previous bulletin board update request failed, or if machine name had been partitioned and now is reconnected.
	Action	No action required.
680	ERROR: Cannot find own table entry
	Description	If the DBBL 's UNIX System message queue is ever removed, the DBBL will attempt to recreate it. This should never happen, but the DBBL has recovery code for extra reliability. This error means the message queue recovery code itself failed. It is a serious error because the DBBL cannot function without a message queue.
	Action	Use the UNIX System kill command to force a DBBL restart. If it does not restart successfully within a few minutes, contact your BEA TUXEDO system Technical Support.
681	ERROR: Cannot update own table entry
	Description	If the DBBL 's UNIX System message queue is ever removed, the DBBL will attempt to recreate it. This should never happen, but the DBBL has recovery code for extra reliability. This error means the message queue recovery code itself failed. It is a serious error because the DBBL cannot function without a message queue.
	Action	Use the UNIX System kill command to force a DBBL restart. If it does not restart successfully within a few minutes, contact your BEA TUXEDO system Technical Support.
682	WARN: New message queue created, key =number
	Description	If the DBBL 's UNIX System message queue is ever removed, the DBBL will attempt to recreate it. This should never happen, but the DBBL has recovery code for extra reliability. This message is output after the DBBL successfully recreates its queue.
	Action	No action required.
683	ERROR: Group id for migration is missing
	Description	One or more server groups could not be migrated because an internal system message is missing necessary data.
	Action	Contact your BEA TUXEDO system Technical Support.
684	ERROR: Memory allocation error
	Description	An attempt to dynamically allocate memory from the operating system using malloc() failed while migrating one or more groups.
	Action	Ensure that 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.
685	ERROR: Could not retrieve server entries for migration
	Description	One or more server groups could not be migrated because server table entries in the bulletin board could not be retrieved.
	Action	Contact your BEA TUXEDO system Technical Support.
686	ERROR: Could not update migrating server's status
	Description	A migrating server's status could not be updated in the bulletin board.
	Action	Contact your BEA TUXEDO system Technical Support.
687	INFO: Server process marked for migration restart, srvgrp=number srvid=number
	Description	The server process has been migrated, and is about to be restarted on the current machine.
	Action	No action required.
	See Also	tmadmin(1), migrategroup and migratemach commands
688	ERROR: Running server cannot be migrated, srvgrp=number srvid=number
	Description	A request was made to migrate this server process. The migration could not proceed because it is still running.
	Action	Shut down the process using tmshutdown 's -R option before migrating it.
	See Also	tmadmin(1), migrategroup and migratemach commands
692	ERROR: Cannot retrieve BBL entry for pclean operation
	Description	When attempting to clean up after a dead or partitioned machine, the DBBL could not find any record of that machine's BBL process.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	tmadmin(1), pclean command
694	ERROR: Cannot lock bulletin board for pclean operation
	Description	A bulletin board lock could not be obtained when attempting to clean up after a dead or partitioned machine.
	Action	Try again after a few seconds, giving the bulletin board lock recovery algorithm time to run. If this error continues, contact your BEA TUXEDO system Technical Support.
	See Also	tmadmin(1), pclean command
695	ERROR: Could not remove server entry for tmid number
	Description	When attempting to clean up after a dead or partitioned machine, a server table entry could not be removed from the bulletin board.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	tmadmin(1), pclean command
697	ERROR: Could not access *RESOURCES section of TUXCONFIG file
	Description	When attempting to update the version number of the master copy TUXCONFIG file, the RESOURCES section could not be read.
	Action	Apparently something has happened to the master machine's TUXCONFIG file. It can be restored by shutting down the entire application, and then running tmloadcf on a backup ASCII copy. Running tmunloadcf on a different machine's TUXCONFIG file should provide a recent backup version.
	See Also	tmloadcf(1), tmunloadcf(1)
698	ERROR: Could not read *RESOURCES section of TUXCONFIG file
	Description	When attempting to update the version number of the master copy of the TUXCONFIG file, the RESOURCES section could not be read.
	Action	Apparently something has happened to the master machine's TUXCONFIG file. It can be restored by shutting down the entire application, and then running tmloadcf on a backup ASCII version. Running tmunloadcf on a different machine's TUXCONFIG file should provide a recent backup version.
	See Also	tmloadcf(1), tmunloadcf(1)
699	ERROR: Could not update *GROUPS section of TUXCONFIG file
	Description	The location of a server group was being updated in the master copy of the TUXCONFIG file, to reflect a new location after migration. An error prevented the GROUPS section from being read (or updated).
	Action	Apparently something has happened to the master machine's TUXCONFIG file. It can be restored by shutting down the entire application, and then running tmloadcf on a backup ASCII version. Running tmunloadcf on a different machine's TUXCONFIG file should provide a recent backup version.
	See Also	tmloadcf(1), tmunloadcf(1)