CMDTUX Messages 300-399
|
|
|
358
ERROR: LMID lmid must be <= len characters in length.
Description
The LMID parameter in the MACHINES section of the UBBCONFIG file was greater than the system imposed limit of 30 characters.
Action
Change the LMID parameter to be 30 characters or less and re-load the configuration.
See Also
tmloadcf(1), ubbconfig(5)
359
ERROR: LMID lmid appears more than once in the *MACHINES section.
Description
A MACHINES section entry in the UBBCONFIG file had an LMID parameter that had previously been used for another machine. Each machine must have a unique LMID.
Action
Change the LMID parameter to be unique and re-load the configuration.
See Also
tmloadcf(1), ubbconfig(5)
360
ERROR: The TUXOFFSET parameter (offset) of the Master machine machine does not match the TUXOFFSET environment variable (offset).
Description
The TUXOFFSET parameter defined for the Master node of the configuration does not match the TUXOFFSET environment variable of the user running tmloadcf. Since tmloadcf must be run on the Master node, the defined TUXOFFSET must match the TUXOFFSET in the environment.
Action
Change the TUXOFFSET parameter or environment variable and re-load the configuration.
See Also
tmloadcf(1), ubbconfig(5)
361
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while parsing the configuration file.
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
tmloadcf(1), ubbconfig(5)
365
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system failed while trying to load the configuration file in tmloadcf.
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.
369
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system failed while trying to load a configuration file with tmloadcf.
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.
372
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while parsing the configuration file.
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
tmloadcf(1), ubbconfig(5)
373
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while parsing the configuration file.
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
tmloadcf(1), ubbconfig(5)
377
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed while parsing the configuration file.
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
tmloadcf(1), ubbconfig(5)
381
WARN: DBBL tpsvrinit - bad command line options were specified when booting the DBBL
Description
Bad command line options were specified when booting the DBBL.
Action
The system should specify correct command line options for booting the DBBL. Contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
382
ERROR: DBBL tpsvrinit - cannot find the DBBL entry in the Bulletin Board
Description
In a networked application (MP mode), the DBBL server initialization routine cannot find the DBBL entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space might be corrupted.
Action
Check if the DBBL is active. The DBBL should be booted before the BBL in a networked application. Try to shut down the application, remove IPC, and then reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
383
ERROR: DBBL tpsvrinit - cannot update the DBBL entry in the Bulletin Board
Description
In a networked application (MP mode), the DBBL server initialization routine cannot update the DBBL entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space might be corrupted.
Action
Check if the DBBL is active. The DBBL should be booted before the BBL in a networked application. Try to shut down the application, remove IPC, and then reboot the DBBL and BBL. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
384
ERROR: DBBL tpsvrinit - cannot open Bulletin Board image file, filename while restarting the DBBL, errno errno_val
Description
While attempting to restart the DBBL, the DBBL server initialization routine cannot open the Bulletin Board image file.
Action
Check and clean up space in either $TMPDIR or /tmp on your machine, or contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
385
ERROR: DBBL tpsvrinit: cannot get file system information of the Bulletin Board image file, filename errno=errno_val
Description
While attempting to start the DBBL, the DBBL server initialization routine cannot get the file system information for the Bulletin Board image file.
Action
Check and cleanup space in either $TMPDIR or /tmp on your machine. Also, check for proper permissions for the files in either $TMPDIR or /tmp. Contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
386
ERROR: DBBL tpsvrinit - the size of the Bulletin Board image file, filename inconsistent with the UBBCONFIG file
Description
While attempting to restart the DBBL, the DBBL server initialization routine detected that the size of the Bulletin Board image file is inconsistent with the UBBCONFIG file.
Action
Contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1), ubbconfig(5)
387
ERROR: DBBL tpsvrinit: error in reading the Bulletin Board image file, filename errno= errno_val
Description
While attempting to start the DBBL, the DBBL server initialization routine detected error in reading the Bulletin Board image file.
Action
Check file permissions of the Bulletin Board image file either in $TMPDIR or /tmp on your machine, or contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
388
ERROR: DBBL tpsvrinit - cannot recalculate the offsets for routing section
Description
While attempting to restart the DBBL, the DBBL server initialization routine cannot recalculate the offsets for the routing section in the Bulletin Board. Possible causes: 1) Bulletin Board corrupted, 2) VIEWFILES and VIEWDIR environment variables are not set, or 3) viewname or FIELD specified in the routing section are not correct.
Action
Contact your BEA TUXEDO system Technical Support. See messages 621 and 658 later in this chapter for further explanation.
See Also
tmboot(1), ubbconfig(5)
389
ERROR: DBBL tpsvrinit - cannot find DBBL entry in the Bulletin Board
Description
When booting the DBBL, the DBBL server initialization routine cannot find its own entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space might be corrupted.
Action
Check if the DBBL is active. The DBBL should be booted before the BBLs in a networked application. Try to shut down the application, remove IPC, and then reboot the administrative processes. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
390
ERROR: DBBL tpsvrinit - cannot reset the current acting master reference
Description
While attempting start the DBBL, the DBBL server initialization routine cannot reset the current acting master reference because another node has already assumed the master role or the Bulletin Board might be corrupted.
Action
Use tmadmin to assume the role of master node or contact your BEA TUXEDO system Technical Support.
See Also
tmadmin(1), tmboot(1)
391
ERROR: DBBL tpsvrinit - cannot update the DBBL entry in the Bulletin Board
Description
In a networked application (MP mode), the DBBL server initialization routine cannot update the DBBL entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space might be corrupted.
Action
Check if the DBBL is active. The DBBL should be booted before the BBLs in a networked application. Try to shut down the application, remove IPC, and then reboot the administrative processes. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
392
ERROR: DBBL tpsvrinit - system standard init function failed
Description
While attempting to start the DBBL, the call to the system standard initialization function failed.
Action
Check for earlier messages in the userlog that describe the nature of the failure.
See Also
tmboot(1)
394
ERROR: DBBL tpsvrinit - cannot find the current BBL entry in the Bulletin Board
Description
While attempting to start the DBBL, the DBBL server initialization routine needs to set up the internal registry table information on the active BBLs in the system. However, it was unable to find the current BBL entry in the Bulletin Board. The DBBL's copy of the Bulletin Board in its own process space might be corrupted.
Action
Check if the DBBL is active. The DBBL should be booted before the BBLs in a networked application. Try to shut down the application, remove IPC, and then reboot the administrative processes. If the error persists, contact your BEA TUXEDO system Technical Support.
See Also
tmboot(1)
395
ERROR: Memory allocation failure
Description
An attempt dynamically to allocate memory from the operating system using malloc() failed in the DBBL while trying to acquire space for the Bulletin Board or while retrieving the current BBL entry on a restart.
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.
396
ERROR: DBBL tpsvrinit - exceeds maximum number of BBLs on all the application nodes
Description
Maximum number of BBLs (MAXBBL) on all the application nodes has been reached.
Action
System limit for the number of BBLs in an application has been reached. Contact your BEA TUXEDO system Technical Support.
397
ERROR: DBBL tpsvrinit - unable to clean up BBLs, the recovery failed
Description
The DBBL recovery failed because it was not able to clean up BBLs.
Action
Contact your BEA TUXEDO system Technical Support.
398
ERROR: DBBL tpsvrinit - cannot update the DBBL entry in the Bulletin Board
Description
In a networked application (MP mode), the DBBL server initialization routine cannot update the DBBL entry in the Bulletin Board when restarting the DBBL. The DBBL 's copy of the Bulletin Board in its own process space might be corrupted.
Action
Check if the DBBL is active. The DBBL should be booted before the BBL in a networked application. Try to shut down the application, remove IPC, and then reboot the administrative processes. If the error persists, contact your BEA TUXEDO system Technical Support.
399
ERROR: Administrative service request failed
Description
A service request handled by the DBBL failed with a fatal error. These requests include tmadmin requests, tmboot and tmshutdown requests.
Action
The system is unstable and a BEA TUXEDO system reboot is recommended, or contact your BEA TUXEDO system Technical Support.
See Also
tmadmin(1), tmboot(1), tmshutdown(1)
 |
 |
 |