System Messages: LIBTUX Catalog 1200-1299
|
![]() |
![]() |
1200 |
ERROR: Cannot re-attach BB - process lost its BB slot while detached | |
|
Description |
The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to the bulletin board, the context for the client or server does not match. This indicates that either the bulletin board is corrupted or the application was re-booted while the client or server was not attached. |
Action |
Check with the administrator to see if the application was re-booted. Contact your Oracle TUXEDO system Technical Support. | |
1201 |
ERROR: Cannot re-attach BB - magic number mismatch | |
|
Description |
The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to the bulletin board, the wrong magic number was found. This indicates that either the bulletin board is corrupted or a new release of the application was booted while the client or server was not attached. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1202 |
ERROR: Cannot re-attach BB - wrong release of software | |
|
Description |
The application is running with the TMPROTECTED SYSTEM_ACCESS value. After reattaching to the bulletin board, the wrong release was found. This indicates that either the bulletin board is corrupted or a new release of the application was booted while the client or server was not attached. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1203 |
WARN: Cannot override system default access method PROTECTED | |
|
Description |
The application called tpinit with the TPSA_FASTPATH flag set, but the configuration has SYSTEM_ACCESS set to PROTECTED,NO_OVERRIDE. tpinit will ignore this flag and run in TPSA_PROTECTED mode. |
Action |
Change the application to use TPSA_PROTECTED mode, or contact the administrator about allowing overriding of the SYSTEM_ACCESS mode. | |
See Also |
| |
1204 |
WARN: Cannot override system default access method FASTPATH | |
|
Description |
The application called tpinit with the TPSA_PROTECTED flag set, but the configuration has SYSTEM_ACCESS set to FASTPATH, NO_OVERRIDE. tpinit will ignore this flag and run in TPSA_FASTPATH mode. |
Action |
Change the application to use TPSA_FASTPATH mode, or contact the administrator about allowing overriding of the SYSTEM_ACCESS mode. | |
See Also |
| |
1205 |
WARN: Unable to open MACHINE ENVFILE filename for reading | |
|
Description |
In the process of booting a server, the ENVFILE specified in the MACHINES section on the configuration could not be opened for reading. The server will still be booted, but the environment will not be modified. |
Action |
Check the machine environment file to see that it exists in the correct directory with the right name and with read permission for the configuration administrator. It may be necessary to shut down the server and re-start it with the correct environment. | |
See Also |
| |
1214 |
ERROR: Cannot perform deferred type/subtype resolution in global tables (type/subtype) | |
|
Description |
The application is running with the TMPROTECTED SYSTEM_ACCESS value. An operation was done on a typed buffer, but checking of the type/subtype was deferred. When the checking was finally done, the type/subtype was not recognized by the system. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1219 |
ERROR: Invalid parameter | |
|
Description |
An invalid parameter was passed to an internal routine during security processing. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1220 |
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. | |
1222 |
ERROR: Unable to open TUXCONFIG file to Resources section | |
|
Description |
While trying to read the configuration file during security processing, the program was unable to open the RESOURCES section. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1223 |
ERROR: Unable to open Resources section of TUXCONFIG file | |
|
Description |
While trying to read the configuration file during security processing, the program was unable to read the RESOURCES section. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1224 |
ERROR: Possibly corrupted key in database | |
|
Description |
The system key created and stored in the file APPDIR/.adm/.keydb for use by the WSH in security applications has become corrupted. This error disables the WSH from being able to handle new incoming connections from workstation clients. Note that current implementations of the security interfaces within the Oracle TUXEDO system will not generate this error, but future ones may if they have more stringent requirements on the key characteristics used for encryption. |
Action |
Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key information correctly. | |
See Also |
Oracle TUXEDO Administrator's Guide | |
1225 |
ERROR: Error while decrypting password | |
|
Description |
The security information stored and accessed by the TUXEDO System/T has become corrupted and cannot be processed correctly by the WSH in order to allow workstation clients to access the application. This error disables the WSH from being able to handle new incoming connections from workstation clients. |
Action |
Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key information correctly. If this does not clear the problem, then remove TUXCONFIG and security information from all sites and reboot. | |
See Also |
Oracle TUXEDO Administrator's Guide | |
1226 |
ERROR: Invalid password in TUXCONFIG file | |
|
Description |
The security information stored and accessed by the TUXEDO System/T has become corrupted and cannot be processed correctly by the WSH in order to allow workstation clients to access the application. This error disables the WSH from being able to handle new incoming connections from workstation clients. |
Action |
Shut down the application on the offending site, and remove the binary TUXCONFIG file and the key database APPDIR/.adm/.keydb. Then reboot the site; this will automatically re-create the security key information correctly. If this does not clear the problem, then remove TUXCONFIG and security information from all sites and reboot. | |
See Also |
Oracle TUXEDO Administrator's Guide | |
1227 |
ERROR: Unable to open TUXCONFIG file to read MACHINES section | |
|
Description |
While trying to read the application password, the program was unable to find the *MACHINES section in the configuration file. This should not occur. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1233 |
ERROR: Unable to shutdown, clients/servers still attached | |
|
Description |
The BBL was unable to shut itself down because clients and/or servers are still attached to the Bulletin Board. It is the BBL 's responsibility to clean up and remove the Bulletin Board prior to terminating. However, the Bulletin Board was not removed since clients and/or servers were still attached to it. |
Action |
First, make sure all application servers have been shut down prior to attempting to shut down the BBL. The | |
1236 |
WARN: TMDEBUG contains non-numeric characters in first number | |
|
Description |
The format of the TMDEBUG variable is invalid. The allowable formats for TMDEBUG are: number If |
Action |
Make sure the TMDEBUG variable is valid. TMDEBUG may be incorrectly set and exported in the environment. It may also be incorrectly set in an environment file using the ENVFILE parameter in the *MACHINES or *SERVERS section of the configuration file. | |
See Also |
| |
1237 |
WARN: TMDEBUG contains non-numeric characters in 2nd part of range | |
|
Description |
See Message 1236 above. |
Action |
See Message 1236 above. | |
1238 |
WARN: TMDEBUG regular expression invalid. Ignoring regular expression. | |
|
Description |
See Message 1236 above. |
Action |
See Message 1236 above. | |
1239 |
ERROR: Failed to change group via setgid() | |
|
Description |
The calling process failed to change its group ID while trying to become the administrator. The effective user ID of the calling process is super-user. |
Action |
Make sure the calling process has permission to change its group ID to the group ID the Oracle TUXEDO system application administrator belongs to. | |
See Also |
| |
1240 |
ERROR: Failed to change user via setuid() | |
|
Description |
The calling process failed to change its user ID while trying to become the administrator. The effective user ID of the calling process is super-user. |
Action |
Make sure the calling process has permission to change its user ID to the user ID the Oracle TUXEDO system application administrator belongs to. | |
See Also |
| |
1241 |
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. | |
1242 |
ERROR: Invalid table type | |
|
Description |
The calling process failed to open a configuration table in the TUXCONFIG file. An invalid table type was passed to the system routine responsible for opening configuration tables. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1243 |
ERROR: Invalid table type | |
|
Description |
The calling process failed to close a configuration table in the TUXCONFIG file. An invalid table type was passed to the system routine responsible for closing configuration tables. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1244 |
ERROR: Invalid table type | |
|
Description |
The calling process failed to seek a configuration table in the TUXCONFIG file. An invalid table type was passed to the system routine responsible for seeking configuration tables. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1245 |
ERROR: Invalid table type | |
|
Description |
The calling process failed to write a configuration table in the TUXCONFIG file. An invalid table type was passed to the system routine responsible for writing configuration tables. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1246 |
ERROR: More than one wild card in entry ranges | |
|
Description |
The calling process found more than one wild card in the ranges string, ranges, while parsing the string based on a packed decimal field type. |
Action |
Make sure there is no more than one wild card in the ranges string ranges. | |
See Also |
| |
1247 |
ERROR: Cannot have a '-' in front of MAX or MIN | |
|
Description |
While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry. |
Action |
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX. | |
See Also |
| |
1248 |
ERROR: Cannot have a '-' in front of MAX or MIN | |
|
Description |
While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry. |
Action |
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX. | |
See Also |
| |
1249 |
ERROR: Cannot have a '-' in front of MAX or MIN | |
|
Description |
While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry. |
Action |
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX. | |
See Also |
| |
1250 |
ERROR: Cannot have a '-' in front of MAX or MIN | |
|
Description |
While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry. |
Action |
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not contain a '-' in front of MIN or MAX. | |
See Also |
| |
1251 |
ERROR: Cannot have a '-' and a '+' sign in front of a number | |
|
Description |
While attaching to the Bulletin Board and loading all of the information that is in the TUXCONFIG file into the Bulletin Board, the calling process failed to get a data routing entry. The failure occurred while parsing a range string into data based on the field type information of one of the entries in the ROUTING section of the configuration file. The calling process was unable to create the data routing entry. |
Action |
Make sure the RANGES parameter in the ROUTING section of the UBBCONFIG file is valid. The range strings may not have '-+' in front of number. | |
See Also |
| |
1253 |
ERROR: shmat failure: errno = errno, key = ipckey | |
|
Description |
The calling process failed to create/attach to the Bulletin Board while invoking the |
Action |
| |
See Also |
| |
1254 |
ERROR: shmget(creat) failure: errno = errno, key = key | |
|
Description |
The calling process failed to create/get to the Bulletin Board while invoking the |
Action |
| |
See Also |
| |
1255 |
ERROR: shmctl(chown) failure: errno = errno, key = key | |
|
Description |
The calling process failed to perform a shared memory control operation on the Bulletin Board while invoking the |
Action |
| |
See Also |
| |
1256 |
ERROR: shmat failure: errno = errno, id = id | |
|
Description |
The calling process failed to create/attach to the Bulletin Board while invoking the |
Action |
| |
See Also |
| |
1257 |
ERROR: func: bad value of _gp_fsoffset variable or supplied offset | |
|
Description |
An invalid VTOC file system offset was passed to func. |
Action |
Make sure the FSOFFSET environment variable is set correctly. If the problem persists after resetting the FSOFFSET environment variable, contact your Oracle TUXEDO system Technical Support. | |
1259 |
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. | |
1260 |
ERROR: Service request problem: func | |
|
Description |
The calling process failed in a Oracle TUXEDO system internal function called func while trying to add a new service table entry. |
Action |
Look through the userlog for other messages related to this failure. If found, refer to the appropriate system messages. If not, consult your Oracle TUXEDO system Technical Support. | |
1261 |
ERROR: Service request problem: string | |
|
Description |
The calling process failed in a Oracle TUXEDO system internal function because of string while trying to add a new service table entry. |
Action |
Look through the userlog for other messages related to this failure. If found, refer to the appropriate system messages. If not, consult your Oracle TUXEDO system Technical Support. | |
1262 |
ERROR: Permission denied to boot server | |
|
Description |
When security is turned on, that is, the SECURITY parameter is specified in the RESOURCES section of the application configuration file, a server may only be booted by the administrator of the application. This means that the user ID and group ID of the user attempting to boot the server should match the user ID and group ID of the application administrator. If they do not match, the server will fail to boot and exit gracefully. |
Action |
Make sure that the TUXCONFIG environment variable is set correctly. If it is pointing to the right application, make sure that the UID and GID parameters are properly set in the RESOURCES section of the configuration file. Also verify that the ID of the user that is attempting to boot the server is set correctly using the UNIX | |
See Also |
| |
1263 |
ERROR: tpsvrinit() returned in transaction mode | |
|
Description |
The application server has been placed in transaction mode during its initialization in |
Action |
Verify that if a transaction is started in | |
See Also |
| |
1264 |
WARN: Ticket stuck high - retrying | |
|
Description |
While monitoring the integrity of the Bulletin Board, the BBL found a Oracle TUXEDO system user level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do so, the BBL failed to lock the Bulletin Board, and will attempt to lock it again. |
Action |
No action required. | |
1265 |
WARN: Ticket stuck high - resetting | |
|
Description |
While monitoring the integrity of the Bulletin Board, the BBL found a Oracle TUXEDO system user level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. The BBL managed to lock the Bulletin Board, transfer the ownership of the semaphore, and adjust the statistics. |
Action |
No action required. | |
1266 |
WARN: Ticket stuck high - retrying | |
|
Description |
While monitoring the integrity of the Bulletin Board, the BBL found a Oracle TUXEDO system user level semaphore with no owner. In addition, another process was waiting to be served. The BBL must therefore become the owner of the semaphore and delegate it to the waiting process. While trying to do so, the BBL failed to lock the Bulletin Board, and will attempt to lock it again. |
Action |
No action required. | |
1270 |
INFO: TM_BBL_SAFE_WAKEUP option is selected | |
|
Description |
The |
Action |
If this option was not intended, unset the TM_BBL_SAFE_WAKEUP environment variable and restart the | |
1274 |
ERROR: tpreturn xa_end TMFAIL returned errstring | |
|
Description |
During a call to |
Action |
Check the error reporting mechanism for the associated resource manager to determine the cause of the problem. | |
1275 |
ERROR: tpreturn TPESVCERR xa_end(0xhexval) returned errstring | |
|
Description |
During a call to |
Action |
Check the error reporting mechanism for the associated resource manager to determine the cause of the problem. | |
1276 |
WARN: Forcing deletion of table entries for server group/id | |
|
Description |
A server died and the administrative processes were unable to restart or clean up after the server. The server and service entries for the server will be deleted from the bulletin board. |
Action |
No action required. | |
1278 |
ERROR: Cannot join application - permission denied | |
|
Description |
An ATMI function was called in a client before calling |
Action |
This is an application error. If the application has security turned on, then | |
See Also |
| |
1279 |
ERROR: Cannot join application - accesser limit exceeded | |
|
Description |
An ATMI function was called in a client before calling |
Action |
This is a application configuration problem. The number of accessers is too small and must be reconfigured to allow more clients. | |
See Also |
| |
1285 |
WARN: tpreturn message send blocked, will try file transfer | |
|
Description |
A server process encountered a message queue blocking condition when returning a message to the client via |
Action |
The system will automatically attempt to return the message using a temporary file. Performance may be degraded if this occurs frequently. Check the kernel parameters related to message queue size, and increase them if necessary. | |
See Also |
Oracle TUXEDO Installation Guide and Message No. 1286 below. | |
1286 |
ERROR: tpreturn could not send reply errno_val | |
|
Description |
A server process encountered an error when returning a reply message to the client via |
Action |
Check the kernel parameters related to message queue size, and increase them if necessary. | |
See Also |
Oracle TUXEDO Installation Guide | |
1287 |
ERROR: Failure to allocate memory for file message transfer, size size | |
|
Description |
When receiving a message that was transferred in a file because it was too large to put on a message queue, |
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. | |
1288 |
ERROR: File transfer creat failed, file=filename, errno=errno_val | |
|
Description |
The UNIX kernel call |
Action |
Check temporary directory's permissions. Check disk space and inode counts for the temporary file system. | |
1289 |
ERROR: File transfer write failed, file=filename, errno=errno_val | |
|
Description |
The UNIX kernel call |
Action |
Check directory and file permissions for the temporary files. Check disk space and inode counts for the temporary file system. | |
1290 |
ERROR: File transfer close failed, file=filename, errno=errno_val | |
|
Description |
The UNIX kernel call |
Action |
Check disk space and inode counts for the temporary file system. | |
1291 |
ERROR: File transfer fstat failed, file=filename, errno=errno_val | |
|
Description |
The UNIX kernel call |
Action |
Check directory and file permissions for the temporary files, disk space and inode counts for the temporary file system, the PERM parameter in the RESOURCES section of the configuration file, and check for any cron job or other process that might be deleting files from the temporary file directory. | |
1292 |
ERROR: File transfer open failed, file=filename, errno=errno_val | |
|
Description |
The UNIX kernel call |
Action |
Check directory and file permissions for the temporary files, the PERM parameter in the RESOURCES section of the configuration file, and check for any cron job or other process that might be deleting files from the temporary file directory. On Windows platforms, check that the setting of the TMP environment variable includes a drive letter, and points to a directory with read and write permissions for both servers and native clients. If the Oracle ProcMGR service is configured to "Log in as Local System Account", then the TMP directory should be on a local (non-network) drive. | |
1293 |
ERROR: File transfer read failed, file=filename, errno=errno_val | |
|
Description |
The UNIX kernel call |
Action |
Check directory and file permissions for the temporary files, disk space and inode counts for the temporary file system, the PERM parameter in the RESOURCES section of the configuration file, and for any cron job or other process that might be deleting files from the temporary file directory. | |
1294 |
ERROR: File transfer close failed, file=filename, errno=errno_val | |
|
Description |
The UNIX kernel call |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
1295 |
WARN: File transfer unlink failed, file=filename, errno=errno_val | |
|
Description |
The UNIX kernel call |
Action |
Check directory and file permissions for the temporary files. If the sticky bit is set for the directory, one user might not be able to delete another user's files. Check the PERM parameter in the RESOURCES section of the configuration file. As a temporary measure, delete filename manually. It is no longer needed by the Oracle TUXEDO system. If there are many such files, schedule a cron job to periodically delete files older than a certain threshold. | |
1296 |
WARN: Cannot retrieve own server group table entry | |
|
Description |
While booting, a server was unable to retrieve its own server table entry. This particular failure by itself will not cause the server to be incapable of processing service requests, but may be indicative of problems elsewhere in the system. If the output from |
Action |
In the normal case, where | |
See Also |
| |
1297 |
INFO: Boot process migrating location of group group_name to machine machine_name | |
|
Description |
The |
Action |
No action required. | |
See Also |
|
![]() |
![]() |
![]() |