System Messages: CMDTUX Catalog 800-899


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 `sysgen` process sizing parameters are correct.

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 `sysgen` process sizing parameters are correct.

804	*ERROR: Cannot start TMS servers, error reading GROUP section**
	Description	During the `tmboot` process, the GROUPS section of the configuration file could not be read.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, or that `TUXCONFIG` is not corrupted (try a `tmunloadcf`), or `TUXCONFIG` was propagated to all machines in the configuration.
	See Also	`tmboot`(1), `tmunloadcf`(1)
805	*ERROR: Cannot start servers, error reading SERVERS section**
	Description	During the `tmboot` process, the SERVERS section of the configuration file could not be read.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported. Make sure the `TUXCONFIG` file is not corrupted (try a `tmunloadcf`). Verify that the `TUXCONFIG` file was propagated to all machines in the configuration.
	See Also	`tmboot`(1), `tmunloadcf`(1)
808	*ERROR: Skipping aout=a.out, LOC=lmid* - illegal LMID specification.**
	Description	During the `tmboot` process, the server specification used an illegal lmid and consequently the server a.out was not started.
	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	`tmboot`(1), `tmloadcf`(1), `ubbconfig`(5)
809	ERROR: Argument vector formation error
	Description	During the `tmboot` process, the command line options for a server to be booted is generated. An error has occurred in forming this string. The problem associated with this error is probably not caused by something the user has done.
	Action	Contact your Oracle TUXEDO system Technical Support.

810	*ERROR: Aout=a.out* - too many arguments**
	Description	During the `tmboot` process, the command line options for a server to be booted are generated. The resultant command line options string is longer that 256 characters and cannot be processed.
	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	`tmboot`(1)
812	ERROR: Illegal machine id value
	Description	During the `tmboot` process, the specified servers are booted. The machine section of the `TUXCONFIG` file is read and an error has occurred in retrieving this information. The problem associated with this error is probably not caused by something the user has done.
	Action	Contact your Oracle TUXEDO system Technical Support.

813	ERROR: Illegal machine id value, mid, for a.out
	Description	During the `tmboot` process, the specified servers are booted. The machine section of the `TUXCONFIG` file is read and an error has occurred in retrieving this information. The problem associated with this error is probably not caused by something the user has done.
	Action	Contact your Oracle TUXEDO system Technical Support.

814	ERROR: Cannot propagate TUXCONFIG file
	Description	During the `tmboot` process, the `TUXCONFIG` file was not successfully propagated to the remote machine. This error may occur in a variety of ways. The network listener process `tlisten` may not be reached. This could be due to a mismatch of the network listener address in the `UBBCONFIG` file (the `NLSADDR` value) and the actual address that the `tlisten` process is using. If the `TAGENT` on a remote node encounters an error while trying to process the configuration file.
	Action	Verify the network listener address in the `TUXCONFIG` and the address used for the `tlisten` process. Examine the userlog for further error messages from the `TAGENT` process.
	See Also	`tlisten`(1), `tmboot`(1), `ubbconfig`(5)
815	ERROR: Cannot fork
	Description	`tmboot` was unable to `fork()` a child process in order to start a Oracle TUXEDO system process.
	Action	The system resources are being used intensively. Try the boot command again. If this situation persists, contact your UNIX system administrator.
	See Also	`tmboot`(1)
816	ERROR: Cannot exec, executable file not found
	Description	While starting a Oracle TUXEDO system or server process, the executable file was not found.
	Action	For a Oracle TUXEDO system process, make sure that the `TUXDIR` value of the lmid is set properly. The executables should be found in `${TUXDIR}/bin`. For a server process, check the value of `APPDIR` for that lmid. Make sure that the server executable file is located in that directory.
	See Also	`tmboot`(1), `ubbconfig`(5)
817	ERROR: Cannot exec, network send error
	Description	While trying to contact a remote site to start Oracle 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	`tmboot`(1)
818	*WARN: Process id=pid* Assume started (network).**
	Description	While booting Oracle TUXEDO system processes or servers, `tmboot` did not receive the status from a network call. The system issues this message to point out that it is not aware of the process status.
	Action	No action is necessary, however, it is useful to note the status of system processes during this scenario.
	See Also	`tmboot`(1)
819	*INFO: Process id=pid* Assume started (pipe).**
	Description	While booting Oracle TUXEDO system processes, `tmboot` receives an interrupt and the system issues this message to point out that it is not aware of the process status. Even though the `boot` process is interrupted (and perhaps aborted by the administrator), the local Oracle TUXEDO system process currently being started may succeed or fail.
	Action	No action is necessary, however, it is useful to note the status of system processes during this scenario.
	See Also	`tmboot`(1)
821	INFO: Duplicate server.
	Description	A `boot` command has been issued for a server that is already running. This message is issued to inform the administrator that a redundant `boot` command has been issued.
	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 `boot` command that originally failed.

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 `boot` command that originally failed.
	See Also	`tmboot`(1)
825	*ERROR: Process a.out* at lmid failed with /T tperrno (tperrno_val)**
	Description	This message prints out a Oracle 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	`tmboot`(1)
826	ERROR: Process a.out at lmid failed with code error_code
	Description	This message prints out a Oracle 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	`tmboot`(1)
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	`tmboot`(1)
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 `fork()` system call returns -1).
	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 `-e` option). The system, in trying to initiate the user error handler, could not exec a new process (the `execl()` system call returns an error).
	Action	The command specified should be checked.
	See Also	`tmboot`(1)
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 `TUXCONFIG` file, an error in reading information from the `TUXCONFIG` file, trying to read a `TUXCONFIG` file from an old release, etc.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, or that the `TUXCONFIG` file is not corrupted (try a `tmunloadcf`). Also make sure that the `TUXCONFIG` file was propagated to all machines in the configuration. Check the userlog for additional details on this failure.
	See Also	`tmboot`(1), `tmunloadcf`(1)
835	*ERROR: Could not read MACHINES section**
	Description	During the `tmboot` process, the MACHINES section of the configuration file could not be read.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, or that the `TUXCONFIG` file is not corrupted (try a `tmunloadcf`), or the `TUXCONFIG` file was propagated to all machines in the configuration.
	See Also	`tmboot`(1), `tmunloadcf`(1)
840	*ERROR: Could not read GROUPS section**
	Description	During the `tmboot` process, the GROUPS section of the configuration file could not be read.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, or that the `TUXCONFIG` file is not corrupted (try a `tmunloadcf`), or the `TUXCONFIG` file was propagated to all machines in the configuration.
	See Also	`tmboot`(1), `tmunloadcf`(1)
841	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc()` failed while setting up an entry for the IPC sizing information requested.
	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	`tmboot`(1)
842	*ERROR: Could not read SERVERS section**
	Description	During the `tmboot` process, the SERVERS section of the configuration file could not be read.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, or that the `TUXCONFIG` file is not corrupted (try a `tmunloadcf`), or the `TUXCONFIG` file was propagated to all machines in the configuration.
	See Also	`tmboot`(1), `tmunloadcf`(1)
843	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc()` failed while setting up an entry for the IPC sizing information requested.
	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	`tmboot`(1)
844	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc()` failed while setting up an entry for system processes to be started.
	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	`tmboot`(1)
845	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc()` failed while setting up an entry for system processes to be started.
	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	`tmboot`(1)
846	ERROR: Illegal ctype
	Description	The ctype of this entry in the TODO list is not CT_MCHID as expected.
	Action	Contact your Oracle TUXEDO system Technical Support.

847	ERROR: Memory allocation failure
	Description	An attempt dynamically to allocate memory from the operating system using `malloc()` failed while setting up a list of message queues to be created.
	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	`tmboot`(1)
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 Oracle 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 `tmloadcf` to load the TUXCONFIG file. Additional information will be printed if tmloadcf printed any errors.
	Action	This output may be used to further diagnose what has occurred during the `tmloadcf` failure.
	See Also	`tmboot`(1), `tmloadcf`(1)
854	*ERROR: tmloadcf error on lmid* tmloadcf output:**
	Description	This message prints the output that occurred from `tmloadcf` from the remote site when the `TUXCONFIG` file was being propagated.
	Action	This output may be used to further diagnose what has occurred during the `tmloadcf` failure.
	See Also	`tmboot`(1)
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 Oracle 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 Oracle TUXEDO system Technical Support.

860	ERROR: Invalid option option_val
	Description	The option specified is not a valid option to the `tmloadcf` command.
	Action	Correct the options to the `tmloadcf` command as per the usage message.
	See Also	`tmloadcf`(1)
862	ERROR: Current work directory path name is too long
	Description	While executing `tmloadcf`, an attempt to get the current working directory path failed. This can indicate that either the directory pathname is greater than 78 characters in length or that the directory hierarchy is not readable.
	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 `MAXTLSTRING`. This file is given as the argument to the `-o` command line option.
	Action	Specify a shorter path name.

864	ERROR: Can't open file filename
	Description	While executing `tmloadcf`, the specified input file cannot be opened.
	Action	Check that the input (`UBBCONFIG`) file exists and is readable, and re-execute the command.
	See Also	`tmloadcf`(1)
865	*ERROR: command: Parse failed*
	Description	While executing `tmloadcf`, an error occurred parsing the input `UBBCONFIG` file.
	Action	Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command.
	See Also	`tmloadcf`(1)
866	*ERROR: command: Severe error found. Stop syntax checking.*
	Description	While executing `tmloadcf`, an error occurred in the input `UBBCONFIG` file such that the `TUXCONFIG` file cannot be loaded. These errors include missing sections, multiple occurrences of sections, dynamic space allocation errors, etc, such that parsing of the input `UBBCONFIG` file was terminated before reading the entire file.
	Action	Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command.
	See Also	`tmloadcf`(1)
867	*ERROR: command: Above errors found during syntax checking*
	Description	While executing `tmloadcf`, one or more errors occurred in the input `UBBCONFIG` file such that the `TUXCONFIG` file cannot be loaded. Normally, this message indicates that the entire `UBBCONFIG` file was read and checked for errors.
	Action	Earlier warning or error messages will indicate the nature of the error. Correct these problems and re-execute the command.
	See Also	`tmloadcf`(1)
868	*ERROR: command* cannot run on a non-master node**
	Description	`tmloadcf` was run on a machine whose `uname()` does not match the physical machine name associated with the `MASTER LMID` in the RESOURCES section of the `UBBCONFIG` file.
	Action	Change the value of `MASTER` in the RESOURCES section, or change the machine name associated with the `LMID` associated with `MASTER` in the MACHINES section, or run the command on the `MASTER` machine.
	See Also	`tmloadcf`(1), `ubbconfig`(5)
869	ERROR: Can't open file filename
	Description	While executing `tmloadcf`, the specified file, filename, could not be opened for reading. `tmloadcf` works by reading the input twice, and this failure occurs on the second pass. If the input is not from a file (for example, from the standard input), then the input is put into a temporary file and this file cannot be opened for reading.
	Action	Check that this file still exists and has read permission. Re-execute the command.
	See Also	`tmloadcf`(1)
870	*ERROR: command: Error found in parsing input*
	Description	While executing `tmloadcf`, an error was found during the second pass of parsing the input.
	Action	Re-execute the command. If the problem happens again, contact your Oracle TUXEDO system Technical Support.
	See Also	`tmloadcf`(1)
871	*INFO: TUXCONFIG file filename* has been created**
	Description	While executing `tmloadcf`, the input `UBBCONFIG` has been successfully processed and a new `TUXCONFIG` file or device, filename, has been created (that is, it did not exist and a new one was created).
	Action	No action required.
	See Also	`tmloadcf`(1)
872	*INFO: TUXCONFIG file filename* has been updated**
	Description	While executing `tmloadcf`, the input `UBBCONFIG` file has been processed and an existing `TUXCONFIG` file or device has been updated with the information.
	Action	No action required.
	See Also	`tmloadcf`(1)
873	ERROR: TUXCONFIG environment variable not set
	Description	While executing `tmloadcf`, the `TUXCONFIG` environment variable has not been set and exported.
	Action	Set and export the `TUXCONFIG` environment variable and re-execute the command.
	See Also	`tmloadcf`(1)
874	ERROR: TUXOFFSET environment variable must >= 0
	Description	While executing `tmloadcf`, the `TUXOFFSET` environment variable is not set correctly to a non-negative integer offset.
	Action	Set and export the `TUXOFFSET` environment variable to a non-negative integer offset and re-execute the command.
	See Also	`tmloadcf`(1)
875	ERROR: TUXCONFIG not set or incorrectly set
	Description	While executing `tmloadcf`, an error occurred in checking the `TUXCONFIG` device.
	Action	Check that either the `TUXCONFIG` device or file does not exist (if it is being created for the first time) or that it exists and is a valid configuration file. Contact your Oracle TUXEDO system Technical Support.
	See Also	`tmloadcf`(1)
876	*ERROR: The value of -b option (blocks) is too small.*
	Description	While executing `tmloadcf`, the size specified for the `-b` option on the command is too small to hold the configuration.
	Action	If `TUXCONFIG` is a UNIX file, it is recommended that the `-b` option not be specified so that `tmloadcf` can size the configuration file correctly. If `TUXCONFIG` is a raw device, then the -b option should be used to specify the total size in blocks of the device; if this was done, then a larger raw device is needed. CMDTUX message 877 indicates the minimum number of blocks needed for the file or device.
	See Also	`tmloadcf`(1)
877	*ERROR: TUXCONFIG file needs at least nblocks* size-byte blocks**
	Description	While executing `tmloadcf`, the size specified for the `-b` command line option was too small. The minimum size needed is specified as nblocks.
	Action	If `TUXCONFIG` is a UNIX file, it is recommended that the `-b` option not be specified so that `tmloadcf` can size the configuration file correctly. If `TUXCONFIG` is a raw device, then the `-b` option should be used to specify the total size in blocks of the device; if this was done, then a larger raw device is needed. The minimum number of blocks needed is specified in this message, nblocks.
	See Also	`tmloadcf`(1)
878	ERROR: Can't create TUXCONFIG tuxconfig
	Description	While executing `tmloadcf`, creation of the `TUXCONFIG` file failed.
	Action	A subsequent system message will indicate the nature of the failure. Correct the problem and re-execute the command.
	See Also	`tmloadcf`(1)
879	*INFO: A new file system has been created. (size = nblocks* size-byte blocks)**
	Description	While executing `tmloadcf`, a new `TUXCONFIG` file or device was created with the specified size, nblocks.
	Action	No action required.
	See Also	`tmloadcf`(1)
880	ERROR: Can't create tablename
	Description	While executing `tmloadcf`, a failure occurred while trying to create the specified tablename. One table is created for each of the sections in the `UBBCONFIG` file.
	Action	A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
	See Also	`tmloadcf`(1)
881	ERROR: Can't open tablename
	Description	While executing `tmloadcf`, a failure occurred while trying to open the specified tablename. One table is created and opened for each of the sections in the `UBBCONFIG` file.
	Action	A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
	See Also	`tmloadcf`(1)
882	ERROR: Can't write tablename
	Description	While executing `tmloadcf`, a failure occurred while trying to write the specified tablename. One table is created, opened, and written for each of the sections in the `UBBCONFIG` file.
	Action	A subsequent system message will indicate the nature of the error. Correct the problem and re-execute the command.
	See Also	`tmloadcf`(1)
883	ERROR: tmloadcf cannot run on an active node
	Description	While executing `tmloadcf`, the configuration file could not be loaded because the application is active on the current machine.
	Action	If the application is active, shut down the application using `tmshutdown`, or make the change using the dynamic reconfiguration program `tmconfig`. If the application is not active, then another application is using the same IPC key. Choose another IPC key and re-execute the command.
	See Also	tmconfig (1), `tmloadcf`(1), tmshutdown (1)
885	WARN: TUXCONFIG file not created: exiting
	Description	While executing `tmloadcf`, the `TUXCONFIG` file did not exist. When asked if the `TUXCONFIG` file should be created, the administrator did not respond positively so the file was not created and loaded.
	Action	No action required.
	See Also	`tmloadcf`(1)
887	WARN: TUXCONFIG file not updated: exiting
	Description	While executing `tmloadcf`, the `TUXCONFIG` file already exists. When asked if the `TUXCONFIG` file should be overwritten, the administrator did not respond positively so the file was not updated.
	Action	No action required.
	See Also	`tmloadcf`(1)
892	ERROR: Error processing configuration file
	Description	While executing `tmloadcf` for an existing `TUXCONFIG`, an error occurred in reading the RESOURCES section of the configuration.
	Action	If the `TUXCONFIG VTOC` is only being used to hold the `TUXCONFIG` tables (and not the `TLOG` or a `TUXEDO/D` database), then the first thing to try is to recreate a new `TUXCONFIG`. If the `TUXCONFIG` is a UNIX file, simply remove it. If it is stored on a raw disk, erase it by doing: `echo "" >$TUXCONFIG` If the error continues to happen, check for disk-type error conditions that might cause problems reading the file. Finally, contact your Oracle TUXEDO system Technical Support.
	See Also	`tmloadcf`(1)
893	WARN: Continuing processing - overwriting old TUXCONFIG file
	Description	While executing `tmloadcf` for an existing `TUXCONFIG`, an error occurred in reading the RESOURCES section of the configuration but the configuration does not appear to be for the current release. The configuration will be overwritten.
	Action	No action required.
	See Also	`tmloadcf`(1)
850	*WARN: Process id=val* Assume started (network).**
	Description	While booting Oracle TUXEDO system processes or servers, `tmboot` did not receive the status from a network call. The system issues this message to point out that it is not aware of the process status.
	Action	No action is necessary, however, it is useful to note the status of system processes during this scenario.
	See Also	`tmboot`(1)
851	*INFO: Process id=val* Assume started (pipe).**
	Description	While booting Oracle TUXEDO system processes, `tmboot` receives an interrupt and the system issues this message to point out that it is not aware of the process status. Even though the `boot` process is interrupted (and perhaps aborted by the administrator), the local Oracle TUXEDO system process currently being started may succeed or fail.
	Action	No action is necessary, however, it is useful to note the status of system processes during this scenario.
	See Also	`tmboot`(1)