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.
802 |
ERROR: Cannot start servers, memory allocation failure | |
|
Description |
During the booting of servers, memory could not be allocated for an internal structure. |
Action |
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX | |
803 |
ERROR: Cannot start servers, memory allocation failure | |
|
Description |
During the booting of servers, memory could not be allocated for an internal structure. |
Action |
Remove processes that may be tying up physical memory, ensure that the application IPC key is correct, or verify that the UNIX | |
804 |
ERROR: Cannot start TMS servers, error reading *GROUP section | |
|
Description |
During the |
Action |
Verify that the environment variable | |
See Also |
| |
805 |
ERROR: Cannot start servers, error reading *SERVERS section | |
|
Description |
During the |
Action |
Verify that the environment variable | |
See Also |
| |
808 |
ERROR: Skipping aout=a.out, LOC=lmid - illegal LMID specification. | |
|
Description |
During the |
Action |
Verify that the correct lmid is used in the configuration file and reload the configuration once the server entry has been corrected. | |
See Also |
| |
809 |
ERROR: Argument vector formation error | |
|
Description |
During the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
810 |
ERROR: Aout=a.out - too many arguments | |
|
Description |
During the |
Action |
Reduce the number of arguments or the length of parameters set, such as path names, wherever possible. Note that internal options may be added to the command line. Therefore, even if the command line options specified by the user have fewer than 256 characters, this error may occur. | |
See Also |
| |
812 |
ERROR: Illegal machine id value | |
|
Description |
During the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
813 |
ERROR: Illegal machine id value, mid, for a.out | |
|
Description |
During the |
Action |
Contact your BEA TUXEDO system Technical Support. | |
814 |
ERROR: Cannot propagate TUXCONFIG file | |
|
Description |
During the
|
Action |
| |
See Also |
| |
815 |
ERROR: Cannot fork | |
|
Description |
|
Action |
The system resources are being used intensively. Try the boot command again. If this situation persists, contact your UNIX system administrator. | |
See Also |
| |
816 |
ERROR: Cannot exec, executable file not found | |
|
Description |
While starting a BEA TUXEDO system or server process, the executable file was not found. |
Action |
For a BEA TUXEDO system process, make sure that the | |
See Also |
| |
817 |
ERROR: Cannot exec, network send error | |
|
Description |
While trying to contact a remote site to start BEA TUXEDO system processes or servers, a network error has occurred. Check the userlog to find out specific details of the failure. |
Action |
The boot command may be tried again. If the error persists, contact your network administrator. | |
See Also |
| |
818 |
WARN: Process id=pid Assume started (network). | |
|
Description |
While booting BEA TUXEDO system processes or servers, |
Action |
No action is necessary, however, it is useful to note the status of system processes during this scenario. | |
See Also |
| |
819 |
INFO: Process id=pid Assume started (pipe). | |
|
Description |
While booting BEA TUXEDO system processes, |
Action |
No action is necessary, however, it is useful to note the status of system processes during this scenario. | |
See Also |
| |
821 |
INFO: Duplicate server. | |
|
Description |
A |
Action |
No action is necessary. | |
822 |
ERROR: No BBL available, cannot boot | |
|
Description |
While starting a server process, the BBL was not available; the server cannot join the application without this system process. All outstanding requests to boot servers will be ignored. |
Action |
Make sure that the BBL is running on the site that failed, and reissue the | |
823 |
ERROR: No DBBL available, cannot boot | |
|
Description |
While starting a server process on the master site, the DBBL was not available; the server cannot join the application without this system process. All outstanding requests to boot servers will be ignored. |
Action |
Make sure that the DBBL is running on the master site, and reissue the | |
See Also |
| |
825 |
ERROR: Process a.out at lmid failed with /T tperrno (tperrno_val) | |
|
Description |
This message prints out a BEA TUXEDO system /T error that has occurred in the process a.out while booting on the machine lmid. |
Action |
Check the userlog for messages from the a.out process to further determine what failure has occurred. | |
See Also |
| |
826 |
ERROR: Process a.out at lmid failed with code error_code | |
|
Description |
This message prints out a BEA TUXEDO system error number that has occurred in the process a.out while booting on the machine lmid. |
Action |
Check userlog messages for the a.out process to further determine what failure has occurred. | |
See Also |
| |
827 |
ERROR: Fatal error encountered; initiating user error handler | |
|
Description |
A fatal error has occurred and the user error handler is invoked. |
Action |
Check previous userlog messages to further determine what failure has occurred. | |
See Also |
| |
828 |
ERROR: Cannot create error process - fork() failed | |
|
Description |
The system, in trying to initiate the user error handler, could not fork a new process (the |
Action |
This error is directly related to system resources (too many processes, lack of swap space, etc). Consult your UNIX system administrator for appropriate actions. | |
829 |
ERROR: Error executing `error_cmd - error | |
|
Description |
The user has specified a command error_cmd to be executed if any process fails to boot (via the |
Action |
The command specified should be checked. | |
See Also |
| |
830 |
ERROR: Could not get BB parameters | |
|
Description |
An error has occurred while trying to read the data from the Bulletin Board. This error could occur in a variety of situations including not being able to open the |
Action |
Verify that the environment variable | |
See Also |
| |
835 |
ERROR: Could not read *MACHINES section | |
|
Description |
During the |
Action |
Verify that the environment variable | |
See Also |
| |
840 |
ERROR: Could not read *GROUPS section | |
|
Description |
During the |
Action |
Verify that the environment variable | |
See Also |
| |
841 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. | |
See Also |
| |
842 |
ERROR: Could not read *SERVERS section | |
|
Description |
During the |
Action |
Verify that the environment variable | |
See Also |
| |
843 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. | |
See Also |
| |
844 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. | |
See Also |
| |
845 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. | |
See Also |
| |
846 |
ERROR: Illegal ctype | |
|
Description |
The ctype of this entry in the TODO list is not CT_MCHID as expected. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
847 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using |
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. | |
See Also |
| |
848 |
ERROR: Machine id mismatch for GROUP set group_number | |
|
Description |
The group_number used is present in the internal groups structure but the corresponding machine id doesn't match. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
853 |
ERROR: tmloadcf error on lmid for TUXCONFIG file file creation | |
|
Description |
While activating a remote machine, an error occurred when running |
Action |
This output may be used to further diagnose what has occurred during the | |
See Also |
| |
854 |
ERROR: tmloadcf error on lmid tmloadcf output: | |
|
Description |
This message prints the output that occurred from |
Action |
This output may be used to further diagnose what has occurred during the | |
See Also |
| |
856 |
ERROR: tmdump failed - can't find BBL | |
|
Description |
While attempting to dump the Bulletin Board a system process, the BBL was not available; we cannot join the application without this system process. |
Action |
Make sure that the BBL is running on the site that failed, and reissue the dump command. | |
857 |
ERROR: tmdump failed - can't find DBBL | |
|
Description |
While attempting to dump the Bulletin Board a system process, the DBBL was not available; we cannot join the application without this system process. |
Action |
Make sure that the DBBL is running on the site that failed, and reissue the dump command. | |
858 |
ERROR: tmdump failed | |
|
Description |
The system was unable to create a buffer for the dump request message to be sent. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
859 |
ERROR: tmdump failed | |
|
Description |
Sending the system message to request a dump of the BBL has failed. |
Action |
Examine the userlog for additional error messages. Contact your BEA TUXEDO system Technical Support. | |
860 |
ERROR: Invalid option option_val | |
|
Description |
The option specified is not a valid option to the |
Action |
Correct the options to the | |
See Also |
| |
862 |
ERROR: Current work directory path name is too long | |
|
Description |
While executing |
Action |
Check that the directory hierarchy has the proper permissions and is not longer than 78 characters, and re-execute the command. | |
863 |
ERROR: Absolute path name of the output file is too long | |
|
Description |
The length of the absolute path name of the output file is greater than |
Action |
Specify a shorter path name. | |
864 |
ERROR: Can't open file filename | |
|
Description |
While executing |
Action |
Check that the input ( | |
See Also |
| |
865 |
ERROR: command: Parse failed | |
|
Description |
While executing |
Action |
Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command. | |
See Also |
| |
866 |
ERROR: command: Severe error found. Stop syntax checking. | |
|
Description |
While executing |
Action |
Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command. | |
See Also |
| |
867 |
ERROR: command: Above errors found during syntax checking | |
|
Description |
While executing |
Action |
Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command. | |
See Also |
| |
868 |
ERROR: command cannot run on a non-master node | |
|
Description |
|
Action |
Change the value of | |
See Also |
| |
869 |
ERROR: Can't open file filename | |
|
Description |
While executing |
Action |
Check that this file still exists and has read permission. Re-execute the command. | |
See Also |
| |
870 |
ERROR: command: Error found in parsing input | |
|
Description |
While executing |
Action |
Re-execute the command. If the problem happens again, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
871 |
INFO: TUXCONFIG file filename has been created | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
872 |
INFO: TUXCONFIG file filename has been updated | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
873 |
ERROR: TUXCONFIG environment variable not set | |
|
Description |
While executing |
Action |
Set and export the | |
See Also |
| |
874 |
ERROR: TUXOFFSET environment variable must >= 0 | |
|
Description |
While executing |
Action |
Set and export the | |
See Also |
| |
875 |
ERROR: TUXCONFIG not set or incorrectly set | |
|
Description |
While executing |
Action |
Check that either the | |
See Also |
| |
876 |
ERROR: The value of -b option (blocks) is too small. | |
|
Description |
While executing |
Action |
If | |
See Also |
| |
877 |
ERROR: TUXCONFIG file needs at least nblocks size-byte blocks | |
|
Description |
While executing |
Action |
If | |
See Also |
| |
878 |
ERROR: Can't create TUXCONFIG tuxconfig | |
|
Description |
While executing |
Action |
A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command. | |
See Also |
| |
879 |
INFO: A new file system has been created. (size = nblocks size-byte blocks) | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
880 |
ERROR: Can't create tablename | |
|
Description |
While executing |
Action |
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command. | |
See Also |
| |
881 |
ERROR: Can't open tablename | |
|
Description |
While executing |
Action |
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command. | |
See Also |
| |
882 |
ERROR: Can't write tablename | |
|
Description |
While executing |
Action |
A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command. | |
See Also |
| |
883 |
ERROR: tmloadcf cannot run on an active node | |
|
Description |
While executing |
Action |
If the application is active, shut down the application using | |
See Also |
tmconfig (1), | |
885 |
WARN: TUXCONFIG file not created: exiting | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
887 |
WARN: TUXCONFIG file not updated: exiting | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
892 |
ERROR: Error processing configuration file | |
|
Description |
While executing |
Action |
If the
If the error continues to happen, check for disk-type error conditions that might cause problems reading the file. Finally, contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
893 |
WARN: Continuing processing - overwriting old TUXCONFIG file | |
|
Description |
While executing |
Action |
No action required. | |
See Also |
| |
850 |
WARN: Process id=val Assume started (network). | |
|
Description |
While booting BEA TUXEDO system processes or servers, |
Action |
No action is necessary, however, it is useful to note the status of system processes during this scenario. | |
See Also |
| |
851 |
INFO: Process id=val Assume started (pipe). | |
|
Description |
While booting BEA TUXEDO system processes, |
Action |
No action is necessary, however, it is useful to note the status of system processes during this scenario. | |
See Also |
|