Messages
Oracle Tuxedo System Messages provide the following information:
Description: The meaning and context of the message.
Action: What steps you can take to correct any problems identified.
See Also: A pointer to related information (not specified for all messages).
The Oracle Tuxedo System Messages are numbered and organized in catalogs, based on parts of the Oracle Tuxedo 10g Release 3 (10.3) system from which they are generated. For information about a specific message, click on the name of the appropriate catalog.
Note: Some messages for deprecated features may still display. Be aware that deprecated features are not supported.
512 |
ERROR: Cannot create device devname, start val, size val on val | |
|
Description |
Creation of a new device using |
Action |
Check to ensure that you have write permission on the device, that | |
See Also |
| |
515 |
WARN: Not destroyed | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
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 | |
See Also |
| |
517 |
ERROR: Cannot destroy device index on device | |
|
Description |
While destroying a device using |
Action |
For device entry 0, use | |
See Also |
| |
520 |
WARN: Not re-initialized | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
521 |
ERROR: Can't open file | |
|
Description |
While executing |
Action |
Make sure that the proper value was specified for the | |
See Also |
| |
523 |
ERROR: Can't write file | |
|
Description |
While executing |
Action |
Make sure that the proper value was specified for the | |
See Also |
| |
526 |
WARN: Not initialized | |
|
Description |
While executing |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
527 |
ERROR: Cannot list device index on file | |
|
Description |
While executing |
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 | |
See Also |
| |
528 |
ERROR: Cannot re-initialize device index on file | |
|
Description |
While executing |
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 | |
See Also |
| |
530 |
ERROR: Device list not initialized | |
|
Description |
The |
Action |
Make sure the device specified with the | |
See Also |
| |
539 |
ERROR: Can't get vtoc on device | |
|
Description |
The |
Action |
Make sure the device specified with the | |
See Also |
| |
544 |
WARN: No entries found | |
|
Description |
A |
Action |
No action required. | |
See Also |
| |
552 |
ERROR: Migration not allowed | |
|
Description |
The |
Action |
Change the configuration to have the | |
See Also |
| |
553 |
ERROR: Invalid group name | |
|
Description |
The |
Action |
Use the | |
See Also |
| |
554 |
ERROR: Error occurred (errval): Check ULOG file | |
|
Description |
A |
Action |
Check the event log for messages indicating the nature of the failure. | |
See Also |
| |
555 |
ERROR: Migration time out: Check ULOG file | |
|
Description |
A |
Action |
Check the event log for messages indicating the state of the migration. It may still complete after the time-out occurs. | |
See Also |
| |
557 |
ERROR: Migration not allowed | |
|
Description |
The |
Action |
Change the configuration to have the | |
See Also |
| |
558 |
ERROR: Invalid machine name | |
|
Description |
The |
Action |
Use the | |
See Also |
| |
559 |
ERROR: Error occurred (errval): Check ULOG file | |
|
Description |
A |
Action |
Check the event log for messages indicating the nature of the failure. | |
See Also |
| |
560 |
ERROR: Migration time out: Check ULOG file | |
|
Description |
A |
Action |
Check the event log for messages indicating the state of the migration. It may still complete after the time-out occurs. | |
See Also |
| |
562 |
ERROR: Not running on Master | |
|
Description |
The |
Action |
Execute the command from the configured master machine. | |
See Also |
| |
563 |
ERROR: Can't get log information | |
|
Description |
The |
Action |
Make sure that the | |
See Also |
| |
564 |
ERROR: TLOGDEVICE must be specified | |
|
Description |
The |
Action |
Change the configuration for the machine to define a | |
See Also |
| |
565 |
ERROR: remote log creation failed | |
|
Description |
The |
Action |
Make sure | |
See Also |
| |
566 |
ERROR: local log creation failed | |
|
Description |
The |
Action |
Check the event log on the local for related messages. | |
See Also |
| |
568 |
ERROR: can't open dump file - errno = errval | |
|
Description |
The |
Action |
Check the errno value to determine the reason for the | |
See Also |
| |
569 |
ERROR: command failed, check ULOG file for message | |
|
Description |
The |
Action |
Check the event log for the prior failure message ( | |
See Also |
| |
570 |
ERROR: command failed, check ULOG file for message | |
|
Description |
The |
Action |
Check the event log for the prior failure message. | |
See Also |
| |
571 |
ERROR: command failed, check ULOG file for message | |
|
Description |
The |
Action |
Check the event log for the prior failure message ( | |
See Also |
| |
572 |
ERROR: command failed, check ULOG file for message | |
|
Description |
The |
Action |
Check the event log for the prior failure message ( | |
See Also |
| |
573 |
ERROR: Tmdumptlog: Page num skipped, chksum unmatch | |
|
Description |
While processing a |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
575 |
ERROR: command failed, check ULOG file for message | |
|
Description |
The |
Action |
Check the event log for the prior failure message ( | |
See Also |
| |
576 |
ERROR: command failed, check ULOG file for message | |
|
Description |
The |
Action |
Check the event log for the prior failure message ( | |
See Also |
| |
579 |
ERROR: Not running on Master | |
|
Description |
The |
Action |
Execute the command from the configured master machine. | |
See Also |
| |
580 |
ERROR: Not enough log information | |
|
Description |
The |
Action |
Make sure that the | |
See Also |
| |
581 |
ERROR: Application is still active | |
|
Description |
The |
Action |
Shut down the application and re-run the command. | |
See Also |
| |
583 |
ERROR: Not destroyed | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
584 |
ERROR: remote log destroy failed | |
|
Description |
The |
Action |
Make sure | |
See Also |
| |
585 |
ERROR: tlog_destroy failed | |
|
Description |
The |
Action |
Check the event log on the local for related messages. | |
See Also |
| |
587 |
ERROR: Not running on Master | |
|
Description |
The |
Action |
Execute the command from the configured master machine. | |
See Also |
| |
588 |
ERROR: Not enough log information | |
|
Description |
The |
Action |
Make sure that the | |
See Also |
| |
589 |
ERROR: Application is still active | |
|
Description |
The |
Action |
Shut down the application and re-run the command. | |
See Also |
| |
591 |
ERROR: remote log init failed | |
|
Description |
The |
Action |
Make sure | |
See Also |
| |
592 |
ERROR: tlog_reinit failed | |
|
Description |
The |
Action |
Check the event log on the local for related messages. | |
See Also |
| |
594 |
ERROR: The system is not active | |
|
Description |
The |
Action |
Check the event log for messages related to the failure. | |
See Also |
| |
595 |
ERROR: loadtlog failed, can't open tlog file | |
|
Description |
The |
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 |
| |
596 |
ERROR: can't write tlog dump file - errno = val | |
|
Description |
The |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
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 |
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 |
| |
599 |
ERROR: can't close tlog dump file - errno = errno. | |
|
Description |
The |
Action |
This error is ignored and processing continues. No action required. | |
See Also |
|