![]() |
![]() |
|
|
300 |
ERROR: funcname: UNIX sys call error - errno_val | |
|
Description |
An attempt to access the VTOC through a system call such as |
Action |
Contact your BEA TUXEDO system Technical Support. | |
301 |
ERROR: funcname: cannot free space | |
|
Description |
An attempt to free space that was allocated in the VTOC has failed because there are no more available VTOC map entries. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
302 |
ERROR: funcname: bad table name specified | |
|
Description |
An error occurred while either creating a new table entry or accessing an existing table entry in the VTOC. If the error occurred while attempting to create a table, either the table name already exists, or the name has a length of 0 or is greater than the allowable table name size (GP_LOGICAL_NAME). If the error occurred while attempting to access an existing table, either the name doesn't exist, or the name has a length of 0 or is greater than the allowable table name size. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
303 |
ERROR: funcname: invalid arguments or request to function | |
|
Description |
An error occurred because the indicated function was invoked with invalid arguments. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
304 |
ERROR: funcname: bad device name or index specified | |
|
Description |
An attempt to access a device has failed because the name used was either of length 0 or was longer than the allowable length of GP_LOGICAL_NAME. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
305 |
ERROR: funcname: attempt to create overlapping devices | |
|
Description |
An error has occurred because of an overlap in devices. An overlap occurs if the new device begins before the old device ends and the new device ends after the old device begins. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
306 |
ERROR: funcname: no entry remains to create device or table or open table | |
|
Description |
An attempt to either create a device or table, or open a table has failed because there are no more available slots in the device list. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
308 |
ERROR: funcname: bad device type (not character special or regular) | |
|
Description |
An attempt to create a disk entry has failed because an invalid device type has been specified. The only two available device types are character special and regular. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
309 |
ERROR: funcname: cannot obtain lock on VTOC | |
|
Description |
An error has occurred because within the function |
Action |
Contact your BEA TUXEDO system Technical Support. | |
310 |
ERROR: errcode: unknown vtoc error code | |
|
Description |
An error has occurred during an access of the VTOC and has resulted in the indicated unrecognizable error code being returned. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
311 |
ERROR: Cannot locate free block in tlog | |
|
Description |
An attempt to locate and write to a free block in the transaction log has failed. |
Action |
Retry the operation and if the problem persists, contact your BEA TUXEDO system Technical Support. | |
312 |
ERROR: Transaction log wrong page number | |
|
Description |
An attempt to access particular page of the transaction log has failed because the referenced page is outside of the bounds of the transaction log. |
Action |
Retry the operation and if the problem persists, contact your BEA TUXEDO system Technical Support. | |
313 |
ERROR: Log warmstart can only be called by BBL | |
|
Description |
An attempt to warmstart has failed because only the BBL is allowed to initiate warmstarts. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
314 |
INFO: Page page skipped, chksum didn't match | |
|
Description |
The indicated page was skipped while doing a warmstart because the checksum did not match. |
Action |
No action required. | |
315 |
ERROR: TLOG not in an understandable format. Different release | |
|
Description |
The format of the transaction log is unrecognizable. The release of the software is different than the release of the transaction log. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
316 |
ERROR: Transaction log file exists | |
|
Description |
An attempt to create the transaction log has failed because a transaction log already exists. |
Action |
If a transaction log exists, remove it and retry the desired operation. If the problem persists, contact your BEA TUXEDO system Technical Support. | |
317 |
ERROR: Log start can only be called by BBL or TMS | |
|
Description |
A call to internal function _tlog_start() has failed because the caller is neither the BBL nor the TMS. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
318 |
ERROR: Log start cannot get tlog information | |
|
Description |
An error occurred in attempting to open the transaction log. Either the *MACHINES section of the configuration file could not be opened, or the current machine id has not been defined in that configuration file. |
Action |
Check and ensure the accuracy of the TUXCONFIG file, and if the problem persists, contact your BEA TUXEDO system Technical Support. | |
319 |
ERROR: Log start cannot open tlog | |
|
Description |
An error occurred attempting to open the transaction log with read and write access. |
Action |
Check and ensure that the appropriate permissions are set on the transaction log and on the directory in which the transaction log resides. If the problem persists, contact your BEA TUXEDO system Technical Support. | |
320 |
ERROR: BB TLOGSIZE differs from number of pages in TLOG file | |
|
Description |
An error has occurred opening the transaction log because the actual size of the TLOG differs from the size maintained by the BB. |
Action |
Retry the desired operation, and if the problem persists, contact your BEA TUXEDO system Technical Support. | |
327 |
ERROR: Invalid table type desired | |
|
Description |
An internal function has failed because it attempted to access an invalid table. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
328 |
ERROR: No space in Bulletin Board for tablename | |
|
Description |
An attempt to allocate a free entry in the Bulletin Board for tablename has failed because it is full. |
Action |
Re-configure the application to increase the size of the associated table. | |
329 |
ERROR: Tried to free non-alloced tmrte | |
|
Description |
An attempt to free a registry table entry has failed because the table entry has not yet been allocated. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
330 |
ERROR: Invalid table type given | |
|
Description |
An internal function has failed because it attempted to access an invalid table. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
331 |
ERROR: No registry table entries | |
|
Description |
There are no more free entries in the registry table, so an attempt to allocate an entry has failed. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
332 |
ERROR: Memory allocation failure | |
|
Description |
An attempt dynamically to allocate memory from the operating system using malloc() failed. This message is issued when a system process (for example, DBBL or BBL) initializes and its call to |
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 |
| |
333 |
ERROR: No DBBL | |
|
Description |
A program was booted in an MP configuration without the Bulletin Board existing. |
Action |
Clean up any IPC resources and re-boot the application from scratch. | |
See Also |
| |
334 |
ERROR: No BBL | |
|
Description |
A program was booted without the Bulletin Board existing. |
Action |
Clean up any IPC resources and re-boot the application from scratch. | |
See Also |
| |
335 |
ERROR: Wrong bulletin board type or IPCKEY not unique | |
|
Description |
Either the bulletin board type has been changed for this application and the old bulletin board (in shared memory) still exists, or the IPCKEY for the application being booted is not unique (another application is using the same IPCKEY and has attached to shared memory using that IPCKEY as the shared memory id). |
Action |
Edit the UBBCONFIG configuration file, change the IPCKEY to a unique value, reload the TUXCONFIG using tmloadcf, and reboot the application. | |
See Also |
| |
336 |
ERROR: semget err: errno=errno_val, key = key_val | |
|
Description |
While initializing the application, a system semaphore could not be created. |
Action |
Look up the errno_val in errno.h to see its name. There are several possible causes. ENOSPC indicates that not enough semaphores are configured in the operating system; re-configure the OS to have more semaphore identifiers or sets. EACCES indicates that the user executing the command does not have permissions, which could be due to another application using the same ICPKEY. Check the owner of the semaphore using the key_val and the | |
337 |
ERROR: semctl err: errno=errno_val, key=key_val, id=id_val | |
|
Description |
While initializing the application, the status of a system semaphore could not be obtained. |
Action |
Look up the errno_val in errno.h to see its name. There are several possible causes. EACCES indicates that the user executing the command does not have permissions, which could be due to another application using the same ICPKEY. Check the owner of the semaphore using the key_val and the | |
338 |
ERROR: BB semaphore not initialized within 10 seconds (key=0xkey_val). | |
|
Description |
While initializing the application, a program found the BEA TUXEDO system semaphore existed but was not initialized within 10 seconds. |
Action |
Use the | |
339 |
ERROR: Creating process may be dead; manual intervention required. | |
|
Description |
While initializing the application, a program found the BEA TUXEDO system semaphore existed but was not initialized within 10 seconds. This is related to message 338. |
Action |
Use the | |
340 |
ERROR: Wrong configuration file | |
|
Description |
Either the configuration parameters have been changed for this application and the old bulletin board (in shared memory) still exists, or the IPCKEY for the application being booted is not unique (another application is using the same IPCKEY and has attached to shared memory using that IPCKEY as the shared memory id). |
Action |
Edit the UBBCONFIG configuration file, change the IPCKEY to a unique value, reload the TUXCONFIG using tmloadcf, and reboot the application. | |
See Also |
| |
341 |
ERROR: Could not allocate bulletin board shared memory | |
|
Description |
While initializing the BEA TUXEDO application, shared memory could not be allocated for the Bulletin Board. |
Action |
Check that the IPCKEY in the UBBCONFIG configuration file is not being used by another application for shared memory. Check that enough shared memory has been configured. | |
See Also |
| |
342 |
ERROR: Could not allocate bulletin board shared memory | |
|
Description |
While initializing the BEA TUXEDO application, shared memory could not be allocated for the Bulletin Board. |
Action |
Check that the IPCKEY in the UBBCONFIG configuration file is not being used by another application for shared memory. Check that enough shared memory has been configured. | |
See Also |
| |
343 |
ERROR: Could not find DBBL | |
|
Description |
While initializing the BEA TUXEDO application, shared memory could not be allocated for the Bulletin Board. |
Action |
The application is configured as mode MP and the DBBL has not created the BB. Make sure that the DBBL is booted first and did not die. Check that the IPCKEY in the UBBCONFIG configuration file is not being used by another application for shared memory. Check that enough shared memory has been configured. | |
See Also |
| |
344 |
ERROR: Could not allocate bulletin board shared memory | |
|
Description |
While initializing the BEA TUXEDO application, shared memory could not be allocated for the Bulletin Board. |
Action |
Check that the IPCKEY in the UBBCONFIG configuration file is not being used by another application for shared memory. Check that enough shared memory has been configured. | |
See Also |
| |
345 |
ERROR: Cannot find DBBL | |
|
Description |
An attempt was made to send a message to the DBBL and its whereabouts could not be ascertained either from the BB or from a BRIDGE process. |
Action |
Check for a partitioned network, corrupted shared memory, or if all administrative processes are running. | |
346 |
ERROR: Not a Bulletin Board | |
|
Description |
The BEA TUXEDO system application's IPCKEY is clashing with another application's use of UNIX IPC resources, specifically with a UNIX IPC semaphore. |
Action |
Choose another IPCKEY for your BEA TUXEDO system application. | |
See Also |
| |
347 |
ERROR: Bulletin Board version mismatch | |
|
Description |
The process trying to attach to the Bulletin Board differs in release from the Bulletin Board creator. The process fails to join the application. |
Action |
Make sure that $TUXDIR/bin points to the most current release of the BEA TUXEDO System. Also, make sure application processes have been re-linked or re-compiled with the latest release. | |
349 |
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 |
| |
350 |
ERROR: Configuration file parameters do not match existing bulletin board. | |
|
Description |
When a process initially tries to join the application, this message is issued when the process' configuration file parameters do not match the existing bulletin board. This could happen, for example, if the application's ubbconfig file is modified and re-loaded with tmloadcf. |
Action |
Make sure that your TUXCONFIG file matches that with which the system was initialized. | |
See Also |
| |
351 |
ERROR: Error building node tables | |
|
Description |
When a BBL initializes, it populates certain areas of the bulletin board. This message is issued when a BBL encounters an error creating the node table in the bulletin board. The node table contains entries for the machines in the *MACHINES section of the ubbconfig file. This error occurs when a node is running with a pre-4.2.1 release of the BEA TUXEDO system. Releases before 4.2.1 supported at most 50 nodes in an application. |
Action |
If your application contains more than 50 nodes specified in your ubbconfig file, then all nodes in the application must be release 4.2.1 or higher. | |
See Also |
| |
352 |
ERROR: Error resetting ULOGPFX | |
|
Description |
The program failed to set the prefix for the userlog file either because dynamic space allocation failed or because the TUXCONFIG file was corrupted. The userlog prefix will be $APPDIR/ULOG. |
Action |
If other messages in the userlog indicate that the TUXCONFIG file is corrupted, you should re-load the TUXCONFIG file at your earliest convenience. If other messages in the userlog indicate that your system is out of memory, then ensure that 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 |
| |
353 |
ERROR: Error putting ENVFILE file into environment | |
|
Description |
This message is issued when an error occurs putting the process' ENVFILE into its environment. |
Action |
See the userlog for other messages that explain exactly which error occurred as part of processing the process' ENVFILE. | |
See Also |
| |
354 |
WARN: Error changing directory to appdir (path) for LMID (lmid) | |
|
Description |
When this message is issued, an invalid APPDIR pathname is specified in the *MACHINES section for the LMID shown in the message. The processes associated with this LMID will use the default APPDIR for this TUXCONFIG. |
Action |
At your earliest convenience, you should set APPDIR to a valid pathname and re-load your TUXCONFIG with tmloadcf. | |
See Also |
| |
355 |
ERROR: No BBL on this machine | |
|
Description |
The process that issued this message tried to join a site that was in the midst of being shut down. |
Action |
No action required. | |
356 |
ERROR: Reached UNIX limit on semaphore ids | |
|
Description |
The BBL could not create any more semaphore ids because the UNIX system-imposed limit on the maximum number of allowed semaphores system-wide would be exceeded. |
Action |
Contact your BEA TUXEDO system Technical Support about resetting the number of UNIX semaphores as per the IPC tuning guidelines in the BEA TUXEDO Installation Guide. | |
See Also |
BEA TUXEDO Installation Guide | |
357 |
ERROR: Cannot create enough semaphores for BB, (UNIX limit), MAXACCESSERS too high | |
|
Description |
When a BBL initializes, it creates one or more sets of semaphores for serializing access to the bulletin board. The number of semaphores created per machine is roughly equal to the value of MAXACCESSERS on that machine. This message is printed when the BBL cannot create as many semaphores as it needs. |
Action |
If possible, decrease the value of MAXACCESSERS for the machine. If several machines are used in your application, it is advisable to specify for each *MACHINES section entry a MAXACCESSERS value that is roughly the number of System/T client and server processes that will run simultaneously on that machine. | |
See Also |
| |
358 |
ERROR: Reached UNIX limit on semaphore ids | |
|
Description |
The BBL could not create any more semaphore ids because the UNIX system-imposed limit on the maximum number of allowed semaphores system-wide would be exceeded. |
Action |
Contact your BEA TUXEDO system Technical Support about resetting the number of UNIX system semaphores as per the IPC tuning guidelines in the BEA TUXEDO Installation Guide. | |
See Also |
BEA TUXEDO Installation Guide | |
359 |
ERROR: Cannot create enough semaphores for BB, (UNIX limit), MAXACCESSERS too high | |
|
Description |
When a BBL initializes, it creates one or more sets of semaphores for serializing access to the bulletin board. The number of semaphores created per machine is roughly equal to the value of MAXACCESSERS on that machine. This message is printed when the BBL cannot create as many semaphores as it needs. |
Action |
If possible, decrease the value of MAXACCESSERS for the machine. If several machines are used in your application, it is advisable to specify for each *MACHINES section entry a MAXACCESSERS value that is roughly the number of System/T client and server processes that will run simultaneously on that machine. | |
See Also |
| |
360 |
ERROR: semctl for initializing sems failed: errno | |
|
Description |
Once the BBL creates a semaphore set used for serializing access to the BB, it initializes it. This message is issued when the BBL fails to initialize a semaphore set as locked. The issued message contains the UNIX system error number, errno, which can be used to determine the exact nature of the error. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
361 |
ERROR: semctl for initializing sems failed: errno | |
|
Description |
Once the BBL creates a semaphore set used for serializing access to the BB, it initializes it. This message is issued when the BBL fails to initialize a semaphore set with the administrator's UNIX uid, gid, and permissions as specified in the ubbconfig file. The issued message contains the UNIX system error number, errno, which can be used to determine the exact nature of the error. |
Action |
Contact your BEA TUXEDO system Technical Support. | |
See Also |
| |
362 |
ERROR: TPEOS time set errno errno | |
|
Description |
As part of initializing the global transaction table, the BBL calls the |
Action |
Consult the | |
See Also |
| |
364 |
ERROR: Failure during send/receive of remote procedure call | |
|
Description |
An internal error occurred while attempting to send a remote procedure call. |
Action |
Check that the DBBL is running, and retry the desired operation. If the error occurs again, contact your BEA TUXEDO system Technical Support. | |
370 |
ERROR: Error setting time for transaction counter, errno errno | |
|
Description |
As part of starting a new transaction, the |
Action |
Consult the | |
See Also |
| |
376 |
ERROR: tpabort: xa_rollback returned status | |
|
Description |
This message is issued if the process aborting a transaction encounters an error upon calling the database resource manager with |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. See the userlog for more information on the outcome of the transaction. Also, use tmadmin's printtrans command to find out more information about the transaction. | |
See Also |
| |
377 |
ERROR: tpabort state state | |
|
Description |
This message is issued when a transaction is being aborted and the state of the transaction is such that the normal procedure for aborting the transaction could not be followed. The state of the transaction is printed as part of this message. If the state is TMGABORTED, then the transaction has already been aborted; all other states reflect the various stages of two-phase commitment (including heuristic outcomes). |
Action |
See the userlog for more information about this transaction's completion. Also, use tmadmin's printtrans command to find out more information about the transaction. | |
See Also |
| |
378 |
ERROR: Failed to determine uname | |
|
Description |
An attempt to determine the machine id through a call to |
Action |
Make sure the machine's uname is correctly configured. Retry the desired operation; if the error occurs again, contact your BEA TUXEDO system Technical Support. | |
381 |
ERROR: Cannot call ATMI routines until you have joined system | |
|
Description |
This message is issued if |
Action |
Change your application code to not use | |
See Also |
| |
382 |
ERROR: Performed tpforward() with outstanding replies | |
|
Description |
This message is issued when a service routine calls |
Action |
You should alter your service routine to call either | |
See Also |
| |
389 |
WARN: Failed to set priority for TMS request | |
|
Description |
When a request is sent to the TMS to complete a transaction, the priority of the request is set to optimize performance. This message is issued as a warning when the system fails to override the default priority. The request is sent at the default priority. |
Action |
No action required. | |
390 |
ERROR: tpcommit msg failure, check GTT | |
|
Description |
This message is issued when the system encounters an error trying to receive the reply to a request sent to a TMS to complete a transaction. This message is typically issued when a system-level failure occurs. |
Action |
See the userlog for more information about this transaction's completion and about any communication error that may have occurred. Also, use tmadmin's printtrans command to find out more information about the transaction and use the printnet command to see the status of all machine connections in the network. This command will report any network partitions. | |
See Also |
| |
391 |
ERROR: No room to add group name | |
|
Description |
This message is issued when a transaction has visited more than 16 BEA TUXEDO system groups (as defined in the GROUPS section of the ubbconfig file). At that point, the transaction will not continue to propagate nor will it complete successfully. |
Action |
Consider combining groups or using data dependent routing to consolidate requests to servers within the same group in order to allow your transaction to stay within the 16 group maximum. | |
See Also |
| |
392 |
INFO: GTTELOG: GTRID: machine(machine) counter_time(0xtime) counter(0xcount) | |
|
Description |
This message prints out the contents of a global transaction table entry. This includes the transaction identifier (GTRID), the transaction's state, and other pertinent information that can be used by support personnel to help locate problems with global transactions. |
Action |
No action required. | |
See Also |
See Messages No. 393, 394, 395, and 396 in this chapter, and Message No. 408 in the chapter on CMDTUX messages. | |
393 |
INFO: coordinator(group) group_count(count) tran_state(state) | |
|
Description |
This message is a continuation of message 392 in this chapter. |
Action |
No action required. | |
See Also |
See Messages No. 392, 394, 395, and 396 in this chapter, and Message No. 408 in the chapter on CMDTUX messages. | |
394 |
INFO: cmchid(val) q(val2) type(val3) iter(val4) reg_index(val5) | |
|
Description |
This message is a continuation of message 392 in this chapter. |
Action |
No action required. | |
See Also |
See Messages No. 392, 393, 395, and 396 in this chapter, and Message No. 408 in the chapter on CMDTUX messages. | |
395 |
INFO: log_page(val) version(val2) tranflags(val3) | |
|
Description |
This message is a continuation of message 392 in this chapter. |
Action |
No action required. | |
See Also |
See Messages No. 392, 393, 394, and 396 in this chapter, and Message No. 408 in the chapter on CMDTUX messages. | |
396 |
INFO: GR[val]:name(val1)local(val2)state(val3) | |
|
Description |
This message is a continuation of message 392 in this chapter. |
Action |
No action required. | |
See Also |
See Messages No. 392, 393, 394, and 395 in this chapter, and Message No. 408 in the chapter on CMDTUX messages. | |
397 |
ERROR: Cannot allocate entry on GTT | |
|
Description |
This message is issued when no more room exists in the bulletin board to accommodate transactions. This message can occur for a new transaction, in which case the transaction will fail to begin. Or, this message can occur when an existing transaction tries to instantiate itself on a server's bulletin board, in which case the transaction will fail to commit. This message might reflect a transient condition based on a large, "bursty" transaction volume. |
Action |
Consider increasing the MAXGTT entry in your application's ubbconfig file if this message occurs often or if too many transactions fail due to the current MAXGTT setting. If you are already using the maximum value, and if you are also using either the LOGGED value for the CMTRET keyword in the ubbconfig file or the TP_CMT_LOGGED setting for | |
See Also |
| |
398 |
ERROR: Cannot allocate entry on GTT, TMID creation failed | |
|
Description |
This message is issued when no more room exists in the bulletin board to accommodate transactions. This message can occur for a new transaction, in which case the transaction will fail to begin. Or, this message can occur when an existing transaction tries to instantiate itself on a server's bulletin board, in which case the transaction will fail to commit. This message might reflect a transient condition based on a large, "bursty" transaction volume. |
Action |
Consider increasing the MAXGTT entry in your application's ubbconfig file if this message occurs often or if too many transactions fail due to the current MAXGTT setting. If you are already using the maximum value, and if you are also using either the LOGGED value for the CMTRET keyword in the ubbconfig file or the TP_CMT_LOGGED setting for | |
See Also |
| |
399 |
ERROR: xa_forget returned status | |
|
Description |
When a database resource manager (RM) makes a unilateral decision to complete a global transaction and its decision is in conflict with the BEA TUXEDO system's decision, this situation is known as a "heuristic decision". The RM is required to log on stable storage this decision until the BEA TUXEDO system explicitly tells the RM to forget its decision. This error message is issued when the RM encounters an error while processing the "forget" request. |
Action |
Contact your BEA TUXEDO system Technical Support or your database system vendor. |
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|