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

TMADMIN Messages 1300-1399

1300	ERROR: can't become a client - tpinit() failed - string
	Description	Execution of tmadmin failed because the user could not join the application. The printed string indicates the reason for the failure. This message can be printed either because no more clients can join the application or because the user failed security permissions.
	Action	If the reason is that no more clients can join the application, re-try the operation a later time. The system should be configured to allow for more clients. If a security problem occurs, the command must be run by the BEA Tuxedo administrator.
	See Also	tmadmin(1)
1301	ERROR: Foreign host already booted, hosterrno=sub
	Description	A command to boot a foreign host with foreign services was executed when the host was already booted.
	Action	This operation cannot be done from tmadmin, thus it cannot occur.
	See Also	tmadmin(1)
1302	ERROR: Foreign host already shutdown, hosterrno=sub
	Description	A command to shut down a foreign host with foreign services was executed when the host was already shut down.
	Action	This operation cannot be done from tmadmin, thus it cannot occur.
	See Also	tmadmin(1)
1303	ERROR: Unlicensed TUXEDO System Binary
	Description	An attempt was made to execute tmadmin in an unlicensed BEA Tuxedo binary.
	Action	Contact BEA Customer Support.
	See Also	tmadmin(1)
1304	ERROR: Expired TUXEDO System Binary
	Description	An attempt was made to execute tmadmin in an expired BEA Tuxedo binary.
	Action	Contact your BEA Customer Support.
	See Also	tmadmin(1)
1315	ERROR: Memory allocation failure, tperrno = error_info
	Description	An attempt dynamically to allocate memory from the operating system failed while executing changetrance or chtr. Additional information about the problem is printed as part of 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.
1316	ERROR: Can't change trace configuration on machine lmid
	Description	A failure occurred while trying to change the tracing configuration on the specified machine.
	Action	Check the event log for related messages.
	See Also	tmadmin(1)
1318	ERROR: Can't change trace configuration of server name in group groupname
	Description	A failure occurred while trying to change the tracing configuration on the specified server and group.
	Action	Check the event log for related messages.
	See Also	tmadmin(1)
1320	ERROR: Update of trace configuration to R4.2 machine not supported
	Description	The chtr or changetrace command was executed for a machine that is running a release earlier than 5.0. This feature was not supported on those releases.
	Action	No action required.
	See Also	tmadmin(1)
1321	ERROR: Invalid trace specification
	Description	The trace specified for the chtr or changetrace command was not valid syntax.
	Action	Correct the syntax and re-run the command.
	See Also	tmadmin(1)
1322	ERROR: Trace specification too long
	Description	The trace specified for the chtr or changetrace command was greater than 78 characters in length.
	Action	Change the trace specification and re-run the command.
	See Also	tmadmin(1)
1323	ERROR: Update of trace configuration for server name in group groupname on R4.2 machine not supported
	Description	The chtr or changetrace command was executed for a server on a machine that is running a release earlier than 5.0. This feature was not supported on those releases.
	Action	No action required.
	See Also	tmadmin(1)
1324	ERROR: Can't change trace configuration of server name in group groupname
	Description	A failure occurred while trying to change the tracing configuration on the specified server and group.
	Action	Check the event log for related messages.
	See Also	tmadmin(1)
1326	ERROR: You must print the transaction table (printtrans) before aborting it
	Description	The aborttrans or at command was executed before executing printtrans. The information from printtrans is needed to specify an index of the entry to be aborted.
	Action	Execute the printtrans command and then the aborttrans command.
	See Also	tmadmin(1)
1327	ERROR: You must print the transaction table (printtrans) before committing it
	Description	The committrans or ct command was executed before executing printtrans. The information from printtrans is needed to specify an index of the entry to be committed.
	Action	Execute the printtrans command and then the committrans command.
	See Also	tmadmin(1)
1330	INFO: Command: string
	Description	All commands that are not read-only or boot (or quit) are written to the event log as a trace of administrative actions that are done.
	Action	No action required.
	See Also	tmadmin(1)
1331	ERROR: Could not send message to tlisten
	Description	While trying to execute crlog to create a transaction log on a remote machine, tmadmin was unable to contact the tlisten on the remote machine.
	Action	Check that tlisten is running on the remote machine. Check the event log for related messages.
	See Also	tlisten(1), tmadmin(1)
1332	ERROR: Could not send message to tlisten
	Description	While trying to execute dslg to destroy the transaction log on a remote machine, tmadmin was unable to contact the tlisten on the remote machine.
	Action	Check that tlisten is running on the remote machine. Check the event log for related messages.
	See Also	tlisten(1), tmadmin(1)
1333	ERROR: Could not send message to tlisten
	Description	While trying to execute inlog to re-initialize the transaction log on a remote machine, tmadmin was unable to contact the tlisten on the remote machine.
	Action	Check that tlisten is running on the remote machine. Check the event log for related messages.
	See Also	tlisten(1), tmadmin(1)
1341	ERROR: Size of Shared Memory file is too large for the existing SHMID
	Description	An attempt to load a file into shared memory via loadmem failed because the size of the file was too large for the existing shared memory ID.
	Action	Re-create (if possible) the file that is being loaded with the correct size.
1344	ERROR: Invalid IPCKEY. IPCKEY must be between 32768 and 262143.
	Description	The IPCKEY that was used was not in the valid range of keys. Valid keys are between 32768 and 262143.
	Action	Enter a new IPCKEY within the valid range.
1345	ERROR: Invalid filename for load memory function.
	Description	The filename that was used was not valid.
	Action	Check that the file specified is valid (e.g., that the directory and file specified exists and has read permission). Check for limited resources (out of files or disk space).
	See Also	tmadmin(1)
1348	ERROR: Could not send message to tlisten
	Description	While trying to execute stoptlisten to stop tlisten on a remote machine, tmadmin was unable to contact the tlisten on the remote machine.
	Action	Check that tlisten is running on the remote machine. Check the event log for related messages.
	See Also	tlisten(1), tmadmin(1)
1349	ERROR: Failed to stop tlisten
	Description	While trying to execute stoptlisten to stop tlisten on a remote machine, a failure occurred.
	Action	Check the event log for related messages.
	See Also	tlisten(1), tmadmin(1)