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 500-599

512	ERROR: Cannot create device devname, start val, size val on val
	Description	Creation of a new device using crdl failed. The parameters to the creation are printed.
	Action	Check to ensure that you have write permission on the device, that tlid values are specified, and that the slice does not overlap with an existing device (use the lidl command to check existing devices).
	See Also	tmadmin(1)
515	WARN: Not destroyed
	Description	While executing dsdl to destroy a device list entry, a yes answer was not provided to the prompt to ensure that the operation should be done.
	Action	No action required.
	See Also	tmadmin(1)
516	ERROR: Cannot list device devindex on config-file
	Description	While destroying a device using dsdl, the specified index on the configuration file could not be listed.
	Action	Use the lidl command to see what devices are available and specified a valid device index.
	See Also	tmadmin(1)
517	ERROR: Cannot destroy device index on device
	Description	While destroying a device using dsdl, the specified index on the configuration file could not be destroyed. This could occur for many reasons including the file is being updated by another process, entry 0 is being destroyed and other files or device entries exist, or an I/O error occurred.
	Action	For device entry 0, use litc and livtoc to ensure that other entries do not exist. Re-try the operation.
	See Also	tmadmin(1)
520	WARN: Not re-initialized
	Description	While executing indir to re-initialize a configuration, a yes answer was not provided to the prompt to ensure that the operation should be done. This operation wipes out all files and device entries for the file - use it with care!
	Action	No action required.
	See Also	tmadmin(1)
521	ERROR: Can't open file
	Description	While executing indir to re-initialize a configuration file, the specified file could not be opened. This operation wipes out all files and device entries for the file - use it with care!
	Action	Make sure that the proper value was specified for the -z option and that the file has read and write permission.
	See Also	tmadmin(1)
523	ERROR: Can't write file
	Description	While executing indir to re-initialize a configuration file, the specified file could not be updated. This operation wipes out all files and device entries for the file - use it with care!
	Action	Make sure that the proper value was specified for the -z option and that the file has read and write permission.
	See Also	tmadmin(1)
526	WARN: Not initialized
	Description	While executing indl to re-initialize a decide list entry, a yes answer was not provided to the prompt to ensure that the operation should be done.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	tmadmin(1)
527	ERROR: Cannot list device index on file
	Description	While executing indl to initialize a device list entry, an error occurred while reading information about the entry.
	Action	Check to see that the file is a valid BEA TUXEDO configuration file, that you have read permission, and that the index is valid (use lidl).
	See Also	tmadmin(1)
528	ERROR: Cannot re-initialize device index on file
	Description	While executing indl to initialize a device list entry, an error occurred while reading information about the entry. This operation frees up all space on that entry - do not do this operation if BEA TUXEDO tables are using space on the entry. Freeing up entry 0 clears all other device entries - do this with care!
	Action	Check to see that the file is a valid BEA TUXEDO configuration file, that you have write permission, and that the index is valid (use lidl). Another program may have the file locked for update.
	See Also	tmadmin(1)
530	ERROR: Device list not initialized
	Description	The lidl was executed for a configuration device that was not initialized.
	Action	Make sure the device specified with the -z option is correct. If it has not already been initialized, use the crdl command to initialize it and create a device entry.
	See Also	tmadmin(1)
539	ERROR: Can't get vtoc on device
	Description	The livtoc was executed for a configuration device that was not initialized or for which the user does not have access permissions.
	Action	Make sure the device specified with the -z option is correct, and that you have read permissions. If it has not already been initialized, you must also have update permissions, and you should use the crdl command to initialize the device and create a device entry.
	See Also	tmadmin(1)
544	WARN: No entries found
	Description	A printgroup or pg was executed but no groups were found to match the specified group (-g) or machine (-m) options, or no groups exist.
	Action	No action required.
	See Also	tmadmin(1)
552	ERROR: Migration not allowed
	Description	The migg or migrategroup command was executed but the application is not configured with the MIGRATE option set.
	Action	Change the configuration to have the MIGRATE option, and configure backup machines.
	See Also	tmadmin(1), ubbconfig(5)
553	ERROR: Invalid group name
	Description	The migg or migrategroup command was executed but an invalid group name was specified.
	Action	Use the pg command to print a list of valid group names.
	See Also	tmadmin(1)
554	ERROR: Error occurred (errval): Check ULOG file
	Description	A migg or migrategroup command was executed but the operation failed.
	Action	Check the event log for messages indicating the nature of the failure.
	See Also	tmadmin(1)
555	ERROR: Migration time out: Check ULOG file
	Description	A migg or migrategroup command was executed but the operation did not complete within the configured timeout value.
	Action	Check the event log for messages indicating the state of the migration. It may still complete after the time-out occurs.
	See Also	tmadmin(1)
557	ERROR: Migration not allowed
	Description	The migm or migratemach command was executed but the application is not configured with the MIGRATE option set.
	Action	Change the configuration to have the MIGRATE option, and configure backup machines.
	See Also	tmadmin(1), ubbconfig(5)
558	ERROR: Invalid machine name
	Description	The migm or migratemach command was executed but an invalid machine name was specified.
	Action	Use the pg command to print a list of valid group names and their associated machine names.
	See Also	tmadmin(1)
559	ERROR: Error occurred (errval): Check ULOG file
	Description	A migm or migratemach command was executed but the operation failed.
	Action	Check the event log for messages indicating the nature of the failure.
	See Also	tmadmin(1)
560	ERROR: Migration time out: Check ULOG file
	Description	A migm or migratemach command was executed but the operation did not complete within the configured timeout value.
	Action	Check the event log for messages indicating the state of the migration. It may still complete after the time-out occurs.
	See Also	tmadmin(1)
562	ERROR: Not running on Master
	Description	The crlog or crlg command was run but not from the configured master machine.
	Action	Execute the command from the configured master machine.
	See Also	tmadmin(1)
563	ERROR: Can't get log information
	Description	The crlog or crlg command was executed but the log information for the specified or default machine could not be found.
	Action	Make sure that the TUXCONFIG file is loaded and that the machine name specified is valid.
	See Also	tmadmin(1), ubbconfig(5)
564	ERROR: TLOGDEVICE must be specified
	Description	The crlog or crlg command was executed but the configuration for the specified machine does not have a TLOGDEVICE specified.
	Action	Change the configuration for the machine to define a TLOGDEVICE file.
	See Also	tmadmin(1), tmconfig(1)
565	ERROR: remote log creation failed
	Description	The crlog or crlg command was executed for a remote machine but the operation failed. This is most often because tlisten(1) is not running on the remote machine.
	Action	Make sure tlisten is running on the remote machine. Check the event log on the local and remote machine for related messages.
	See Also	tlisten(1), tmadmin(1)
566	ERROR: local log creation failed
	Description	The crlog or crlg command was executed for the local machine but the operation failed.
	Action	Check the event log on the local for related messages.
	See Also	tmadmin(1)
568	ERROR: can't open dump file - errno = errval
	Description	The dumptlog or dl command was executed but the output file could not be created and opened. The errno value is printed.
	Action	Check the errno value to determine the reason for the fopen() failure. It may be that you do not have permissions on the directory or the file, or a lack of resources (files or space).
	See Also	tmadmin(1)
569	ERROR: command failed, check ULOG file for message
	Description	The dumptlog or dl command was executed but getting information about the associated log file failed.
	Action	Check the event log for the prior failure message (_gp_litbl).
	See Also	tmadmin(1)
570	ERROR: command failed, check ULOG file for message
	Description	The dumptlog or dl command was executed but opening the transaction log file failed.
	Action	Check the event log for the prior failure message.
	See Also	tmadmin(1)
571	ERROR: command failed, check ULOG file for message
	Description	The dumptlog or dl command was executed but reading the transaction log file failed.
	Action	Check the event log for the prior failure message (_gp_tblread).
	See Also	tmadmin(1)
572	ERROR: command failed, check ULOG file for message
	Description	The dumptlog or dl command was executed but updating the transaction log file failed.
	Action	Check the event log for the prior failure message (_gp_tblwrite).
	See Also	tmadmin(1)
573	ERROR: Tmdumptlog: Page num skipped, chksum unmatch
	Description	While processing a dl or dumptlog command, a page was found in the transaction log that was invalid. The page is skipped and processing continues.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	tmadmin(1)
575	ERROR: command failed, check ULOG file for message
	Description	The dumptlog or dl command was executed but reading a page from the transaction log file failed.
	Action	Check the event log for the prior failure message (_gp_tblread).
	See Also	tmadmin(1)
576	ERROR: command failed, check ULOG file for message
	Description	The dumptlog or dl command was executed but reading a page from the transaction log file failed.
	Action	Check the event log for the prior failure message (_gp_tblread).
	See Also	tmadmin(1)
579	ERROR: Not running on Master
	Description	The dslog or dslg command was run but not from the configured master machine.
	Action	Execute the command from the configured master machine.
	See Also	tmadmin(1)
580	ERROR: Not enough log information
	Description	The dslog or dslg command was executed but the log information for the specified or default machine could not be found, or a TLOGDEVICE was not configured.
	Action	Make sure that the TUXCONFIG file is loaded and that the machine name specified is valid. Change the configuration for the machine to define a TLOGDEVICE file.
	See Also	tmadmin(1), ubbconfig(5)
581	ERROR: Application is still active
	Description	The dslog or dslg command was executed but one or more servers are still active.
	Action	Shut down the application and re-run the command.
	See Also	tmadmin(1)
583	ERROR: Not destroyed
	Description	While executing dslog or dslg to destroy a transaction log, a yes answer was not provided to the prompt to ensure that the operation should be done.
	Action	No action required.
	See Also	tmadmin(1)
584	ERROR: remote log destroy failed
	Description	The dslog or dslg command was executed for a remote machine but the operation failed. This is most often because tlisten(1) is not running on the remote machine.
	Action	Make sure tlisten is running on the remote machine. Check the event log on the local and remote machine for related messages.
	See Also	tlisten(1), tmadmin(1)
585	ERROR: tlog_destroy failed
	Description	The dslog or dslg command was executed for the local machine but the operation failed.
	Action	Check the event log on the local for related messages.
	See Also	tmadmin(1)
587	ERROR: Not running on Master
	Description	The inlog or inlg command was run but not from the configured master machine.
	Action	Execute the command from the configured master machine.
	See Also	tmadmin(1)
588	ERROR: Not enough log information
	Description	The inlog or inlg command was executed but the log information for the specified or default machine could not be found, or a TLOGDEVICE was not configured.
	Action	Make sure that the TUXCONFIG file is loaded and that the machine name specified is valid. Change the configuration for the machine to define a TLOGDEVICE file.
	See Also	tmadmin(1), ubbconfig(5)
589	ERROR: Application is still active
	Description	The inlog or inlg command was executed but the one or more servers are still active.
	Action	Shut down the application and re-run the command.
	See Also	tmadmin(1)
591	ERROR: remote log init failed
	Description	The inlog or inlg command was executed for a remote machine but the operation failed. This is most often because tlisten(1) is not running on the remote machine.
	Action	Make sure tlisten is running on the remote machine. Check the event log on the local and remote machine for related messages.
	See Also	tlisten(1), tmadmin(1)
592	ERROR: tlog_reinit failed
	Description	The inlog or inlg command was executed for the local machine but the operation failed.
	Action	Check the event log on the local for related messages.
	See Also	tmadmin(1)
594	ERROR: The system is not active
	Description	The loadtlog command was executed but the application is not currently active or there is an error in finding the master machine.
	Action	Check the event log for messages related to the failure.
	See Also	tmadmin(1)
595	ERROR: loadtlog failed, can't open tlog file
	Description	The loadtlog command was executed but the transaction log file could not be opened for reading/writing.
	Action	Check that the file specified is valid (e.g., that the directory and file specified exists and has read and write permission). Check for limited resources (out of files or disk space).
	See Also	tmadmin(1)
596	ERROR: can't write tlog dump file - errno = val
	Description	The loadtlog command was executed but the status of the transaction log file could not be determined.
	Action	Contact your BEA TUXEDO system Technical Support.
	See Also	tmadmin(1)
597	ERROR: loadtlog failed, can't get msgbuf. tperrno = sub
	Description	An attempt dynamically to allocate memory from the operating system failed while trying to load a transaction log.
	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.
598	ERROR: loadtlog failed, can't read logfile. errno = val
	Description	The loadtlog command was executed but a read of the transaction log file failed.
	Action	Make sure that the file specified is a valid transaction log. The file is character-based and can be read using any text editor.
	See Also	tmadmin(1)
599	ERROR: can't close tlog dump file - errno = errno.
	Description	The loadtlog command was executed. After reading the transaction log, the close of the file failed.
	Action	This error is ignored and processing continues. No action required.
	See Also	tmadmin(1)