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.
1800 |
WARN: Server RESTART set to Y and MAXGEN set < 2 on server entry servername | |
|
Description |
A server entry for servername is configured with the |
Action |
No action is required. Normally, the | |
See Also |
| |
1801 |
WARN: Error while parsing filename. | |
|
Description |
|
Action |
Edit the file specified by the " | |
1802 |
ERROR: Error adding element to heap. | |
|
Description |
|
Action |
If this error occurs consistently, contact BEA TUXEDO system Technical Support. | |
1803 |
ERROR: Unable to parse -s option. | |
|
Description |
While |
Action |
Make sure the | |
1804 |
ERROR: Unable to build function table. | |
|
Description |
|
Action |
If this error occurs consistently, contact the BEA TUXEDO system Technical Support. | |
1805 |
WARN: Could not open file filename. | |
|
Description |
The file specified to |
Action |
Make sure that the given filename exists. One useful trick is to specify filename as a full path name, rather than a relative path name. | |
1806 |
WARN: File recursion is not supported. | |
|
Description |
The " |
Action |
Remove any lines from | |
1812 |
WARN: Could not read filetype file filename on LMID | |
|
Description |
While booting the system or updating the MIB, a security file could not be read on the specified machine. Normally, this will occur when security is configured but one or more of the security files have not been populated (for example, |
Action |
No action is needed if the associated information is not required for the application. | |
See Also |
| |
1813 |
ERROR: Could not encrypt filetype file for propagation to LMID | |
|
Description |
While booting the system or updating the MIB, a directory needed to hold the security file could not be created. |
Action |
Verify that the | |
See Also |
| |
1814 |
ERROR: Could not propagate filetype file to LMID: Failed to make directory | |
|
Description |
While booting the system or updating the MIB, a directory needed to hold the file could not be created. |
Action |
Verify that the | |
See Also |
tmboot (1) | |
1815 |
ERROR: Could not propagate filetype file to LMID: Invalid file type for directory | |
|
Description |
While booting the system or updating the MIB, a directory needed to hold the file could not be created because a file exists with the same path name. |
Action |
Remove the file.adm or adm and retry the command. | |
1816 |
ERROR: Could not propagate filetype file to LMID: Cannot change mode of directory | |
|
Description |
While booting the system or updating the MIB, the permissions of a directory needed to hold the file could not be changed. |
Action |
Change ownership of the | |
See Also |
| |
1817 |
ERROR: Could not propagate filetype file to LMID: Cannot open file | |
|
Description |
While booting the system or updating the MIB, a security file could not be opened for reading or writing. |
Action |
Verify that the file system containing | |
1818 |
ERROR: Could not propagate filetype file to LMID: Cannot write to file | |
|
Description |
While booting the system or updating the MIB, a write failed on a security file being propagated to the specified LMID. |
Action |
Verify that the file system containing | |
See Also |
| |
1819 |
ERROR: Could not propagate filetype file to LMID: Error decrypting the file | |
|
Description |
While booting the system or updating the MIB, there was an encryption problem when propagating one of the security files. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1820 |
ERROR: Could not propagate filetype file to LMID: Unknown error | |
|
Description |
While booting the system or updating the MIB, there was an unrecognized return code encountered. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
1821 |
ERROR: MAXACLGROUPS parameter must be > 0 and <= 16384 | |
|
Description |
The |
Action |
Correct the value of | |
See Also |
| |
1824 |
ERROR: MAXACLCACHE parameter must be >= 10 and <= 32000 | |
|
Description |
The |
Action |
Correct the value of | |
See Also |
| |
1825 |
ERROR: Current work directory path name is too long | |
|
Description |
While executing |
Action |
Check that the directory hierarchy has the proper permissions and is no longer than 78 characters, and re-execute the command. | |
1827 |
ERROR: Absolute path name of the input file is too long | |
|
Description |
The length of the absolute path name of the input file is greater than |
Action |
Specify a shorter path name. | |
1828 |
ERROR: Security level must be USER_AUTH, ACL or MANDATORY_ACL. | |
|
Description |
In order to run |
Action |
Change the security level in the | |
1829 |
ERROR: Security level must be USER_AUTH, ACL or MANDATORY_ACL. | |
|
Description |
In order to run |
Action |
Change the security level in the | |
1830 |
ERROR: client name is invalid. | |
|
Description |
The client name given to |
Action |
Change the name given to the command in order to comply with the specifications. | |
1831 |
ERROR: new user name is not valid. | |
|
Description |
The new user name given to |
Action |
Change the name given to the command in order to comply with the specifications. | |
1832 |
ERROR: can't execute command | |
|
Description |
An error occurred while compiling a server with the buildserver command. The message prints the exact compilation command. |
Action |
Check the command that it is valid (e.g., files exist and have the correct permissions). Check the errors generated by the compiler and correct them. | |
See Also |
| |
1833 |
ERROR: Group numbers must be between 0 and max. | |
|
Description |
Group identifiers must be between 0 and 16383. |
Action |
Change the group number to be within the proper boundaries. Re-run the command that caused the error. | |
1834 |
ERROR: Group numbers must be between 0 and max. | |
|
Description |
Group identifiers must be between 0 and 16383. |
Action |
Change the group number to be within the proper boundaries. Re-run the command that caused the error. | |
1835 |
ERROR: Group name is invalid. | |
|
Description |
The group name given to |
Action |
Change the name given to the command in order to comply with the specifications. | |
1836 |
WARN: Server(pid) processing terminated with SIGKILL after SVCTIMEOUT | |
|
Description |
The BBL has terminated the local server with process id pid using the |
Action |
Either increase the configured service timeout value, or modify the server to complete the service within the allotted time interval. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1837 |
WARN: Server(pid) processing terminated with SIGTERM after SVCTIMEOUT | |
|
Description |
The BBL has terminated the local server with process id pid using the |
Action |
Either increase the configured service timeout value, or modify the server to complete the service within the allotted time interval. | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1838 |
ERROR: .SysServiceTimeout: queue, group group, id srvid server sent SIGTERM due to a service time-out | |
|
Description |
The |
Action |
The administrator may need to configure the service time-out higher in order to accommodate a heavily loaded system.
(The service time-out is specified using the | |
See Also |
BEA TUXEDO Administrator's Guide, | |
1839 |
ERROR: can't execute command | |
|
Description |
An error occurred while compiling a client with the buildclient command. The message prints the exact compilation command. |
Action |
Check the command that it is valid (e.g., files exist and have the correct permissions). Check the errors generated by the compiler and correct them. | |
See Also |
| |
1850 |
INFO: TM_RESTARTSRVTIMEOUT is set to secs seconds | |
|
Description |
The |
Action |
If the indicated timeout time is incorrect, change the value of the TM_RESTARTSRVTIMEOUT environment variable and restart the application. | |
1851 |
INFO: TM_BOOTTIMEOUT is set to secs seconds | |
|
Description |
The |
Action |
If the indicated timeout time is incorrect, change the value of the TM_BOOTTIMEOUT environment variable and restart the application. | |
See Also |
| |
1852 |
INFO: TM_BOOTTIMEOUT is set to secs seconds | |
|
Description |
The |
Action |
If the indicated timeout time is incorrect, change the value of the TM_BOOTTIMEOUT environment variable and restart the application. | |
1853 |
INFO: TM_SHUTDOWNTIMEOUT is set to secs seconds | |
|
Description |
The |
Action |
If the indicated timeout time is incorrect, change the value of the TM_SHUTDOWNTIMEOUT environment variable and restart the | |
See Also |
| |
1854 |
INFO: TM_BOOTTIMEOUTKILL option is selected | |
|
Description |
The |
Action |
If this option was not intended, unset the TM_BOOTTIMEOUTKILL environment variable and restart the | |
1855 |
INFO: TM_BOOTPRESUMEDFAIL option is selected | |
|
Description |
The |
Action |
If this option was not intended, unset the TM_BOOTPRESUMEDFAIL environment variable and restart the | |
1856 |
INFO: TM_RESTARTSRVTIMEOUTKILL option is selected | |
|
Description |
The |
Action |
If this option was not intended, unset the TM_RESTARTSRVTIMEOUTKILL environment variable and restart the application. | |
1857 |
WARN: Server process ID pid on site lmid failed to shut down within secs seconds | |
|
Description |
|
Action |
Investigate the reason for the failure of the server to respond. If necessary, use the -w or -k options to shutdown the server. | |
See Also |
| |
1858 |
ERROR: Server process ID pid on site lmid failed to initialize within TM_BOOTTIMEOUT seconds | |
|
Description |
|
Action |
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function. | |
1859 |
ERROR: Server process ID pid failed to initialize within secs seconds | |
|
Description |
|
Action |
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function. | |
1860 |
ERROR: On restart, server process ID pid failed to initialize within secs seconds | |
|
Description |
The |
Action |
Investigate the failure of the server to restart. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function. | |
1861 |
ERROR: Server process ID pid failed to initialize within secs seconds | |
|
Description |
The |
Action |
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function. | |
See Also |
| |
1862 |
INFO: Process ID=pid Assume started (timeout). | |
|
Description |
|
Action |
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function. | |
1863 |
INFO: Process ID=pid Assume failed (timeout). | |
|
Description |
|
Action |
Investigate the failure of the server to boot. There may be a problem with the executable file, or one of the required libraries, or a delay in the initialization code in tpsvrinit() or other function. | |
1864 |
INFO: Process ID=pid Assume failed (pipe). | |
|
Description |
While booting BEA TUXEDO system processes or servers, |
Action |
Investigate the failure of the server to report completion of initialization. | |
1865 |
WARN: Process ID=pid Assume failed (network). | |
|
Description |
While booting BEA TUXEDO system processes or servers, |
Action |
Investigate the failure of the server to report completion of initialization. There may be a problem with the network. | |
1866 |
ERROR: Attempt to send SIGKILL to site lmid process ID pid failed (errno=errno_val, tperrno=tperrno_val) | |
|
Description |
|
Action |
No action necessary. | |
1867 |
INFO: SIGKILL delivered to site lmid process ID pid | |
|
Description |
|
Action |
No action necessary. | |
1868 |
ERROR: Attempt to send SIGKILL to process ID pid failed (reason) | |
|
Description |
|
Action |
No action necessary. | |
1869 |
INFO: SIGKILL delivered to process ID pid | |
|
Description |
|
Action |
No action necessary. | |
1870 |
ERROR: The TM_RESTARTSRVTIMEOUT value (string) is non-numeric or outside the valid range | |
|
Description |
The |
Action |
If the indicated timeout time is incorrect, change the value of the TM_RESTARTSRVTIMEOUT environment variable and restart the application. | |
1871 |
ERROR: The TM_BOOTTIMEOUT value (string) is non-numeric or outside the valid range | |
|
Description |
The |
Action |
Change the value of the TM_BOOTTIMEOUT environment variable and run | |
1872 |
ERROR: The TM_BOOTTIMEOUT value (string) is non-numeric or outside the valid range | |
|
Description |
The |
Action |
Change the value of the TM_BOOTTIMEOUT environment variable and start the | |
See Also |
| |
1873 |
ERROR: The TM_SHUTDOWNTIMEOUT value (string) is non-numeric or outside the valid range | |
|
Description |
The |
Action |
Change the value of the TM_SHUTDOWNTIMEOUT environment variable and run | |
See Also |
|