System Messages: LIBTUX Catalog 6900-6999
|
![]() |
![]() |
6900 |
ERROR: Failed to free qtype SHMQ (qindex), error = errno | |
|
Description |
Internal error occurs when trying to free shared memory queue on process termination. |
Action |
Contact Oracle Customer Support. | |
6901 |
WARN: Failed to allocate SHMMSG with size number, try local memory | |
|
Description |
Shared memory message resource is temporarily unavailable or requested size exceeds maximum shared memory message buffer size, use local memory for allocation. |
Action |
None. | |
6902 |
ERROR: Failed to send notification to IPCQ (qid), error = errno | |
|
Description |
Internal error occurs when trying to send notification message to System V IPC queue. Usually happens when System V IPC queue is full. |
Action |
If the problem is persistent, contact Oracle Customer Support. | |
6903 |
ERROR: Failed to send SHMMSG to SHMQ (qindex), error = errno | |
|
Description |
Internal error occurs when trying to send shared memory message to shared memory queue. |
Action |
Contact Oracle Customer Support. | |
6904 |
ERROR: Failed to receive SHMMSG from SHMQ (qindex), mtype = msgtype, error = errno | |
|
Description |
Internal error occurs when trying to receive shared memory message with specific message type from shared memory queue. |
Action |
Contact Oracle Customer Support. | |
6905 |
ERROR: Failed to allocate SHMMSG | |
|
Description |
Shared memory message resource is temporarily unavailable, no free shared memory message buffer left. |
Action |
Configure more shared memory resource used for shared memory messages. Enlarge | |
See Also |
| |
6906 |
ERROR: Failed on semop (number), errno = errno | |
|
Description |
Internal error occurs in semop system call on shared memory queue lock operation. |
Action |
Contact Oracle Customer Support. | |
6907 |
ERROR: File open failed on Oracle Wallet "wallet_loc" and subsequent attempt to dynamically create security credentials failed | |
|
Description |
Tuxedo was unable to open an Oracle Wallet in directory wallet_loc and was also unable to find legacy security credentials. |
Action |
Determine if the intention was for the application to use an Oracle Wallet or if the intention was for the application to use legacy security credentials. The location of the Oracle Wallet or the legacy security credentials is determined by the SEC_PRINCIPAL_LOCATION and SEC_PRINCIPAL_NAME parameters as explained in the Using Security In ATMI Applications documentation. Ensure that appropriate security credentials exist in the specified location. | |
6908 |
INFO: Security credentials for principal principal_name have been converted to Oracle Wallet wallet_loc | |
|
Description |
This message is printed when the ULOG_SSLINFO=y environment variable is set and Tuxedo converts legacy security credentials to an Oracle Wallet. The wallet_loc printed is the directory where the |
Action |
No action required. | |
6909 |
ERROR: Cannot convert certificate to X509 for principal principal_name | |
|
Description |
When converting legacy security credentials to the Oracle Wallet format, Tuxedo uses the plugin framework to obtain each certificate in the certificate chain for principal principal_name. An error occurred while converting one of these certificates to an intermediate X509 format needed before the Oracle Wallet is created. |
Action |
Verify that all certificates in the certificate chain for principal_name contain valid data. If the default plugin framework implementation using LDAP is used, then the ldapsearch command available in many operating systems can be helpful in manually retrieving the certificates in the chain. | |
6910 |
ERROR: Cannot open wallet_loc for writing as a new wallet (errno=errno) | |
|
Description |
While attempting to convert legacy security credentials to the Oracle Wallet format, the |
Action |
Ensure that the operating system permissions allow the current user to create file wallet_loc and that there is space in the filesystem to allow creation of this file. | |
6911 |
ERROR: Cannot change permissions on new wallet wallet_loc (errno=errno); will not attempt to create wallet | |
|
Description |
While attempting to convert legacy security credentials to the Oracle Wallet format, the |
Action |
Since an | |
6913 |
ERROR: Failed to initialize xalan library. | |
|
Description |
|
Action |
Check whether libxalan-c library is available. | |
See Also |
DDR XPath. | |
6914 |
ERROR: Invalid XPath expression. | |
|
Description |
The application use DDR XPath feature and an invalid XPath expression is used. |
Action |
Check the XPath expression. | |
See Also |
DDR XPath. | |
6915 |
ERROR: Cannot evaluate the XPath expression. | |
|
Description |
|
Action |
Check whether the XPath can be used for the xml content. | |
See Also |
DDR XPath. | |
6916 |
WARN: .SysBBDeadLocked: USEM[val] lock appears to be hung: held by pid=val on host hostname. | |
|
Description |
The process has held the lock on the Bulletin Board for a longer than normal period of time. The process could still be live, but incorrectly holding the user-level semaphore. |
Action |
Check the status of the process that is holding the lock. It might be hung, or it is holding the lock for too long a period of time while operating. | |
6917 |
ERROR: SSL renegotiation handshake failed with error error_number [error_string] | |
|
Description |
This process requested a renegotiation of the SSL connection and the SSL handshake failed during the renegotiation. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string. |
Action |
If the problem occurs repeatedly, setting the environment variable | |
6918 |
ERROR: SSL renegotiation failed with error error_number [error_string] | |
|
Description |
This process requested a renegotiation of the SSL connection and the request to renegotiate the connection or to flush unwritten data failed. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string. |
Action |
If the problem occurs repeatedly, setting the environment variable | |
6919 |
ERROR: Cannot convert certificate chain to X509 for principal "principal_name" | |
|
Description |
While invoking the plugin framework to verify a certificate chain, an error occurred while converting one of the certificates in the chain to X509 format. |
Action |
The original security credentials for principal_name may have been in either Oracle Wallet format or in in legacy format. By the time of this message, the credentials will be in a Wallet (unless the environment TUXCREATEWALLET=TEMP is set to prevent saving legacy security credentials as a Wallet.) Examine the certificates in the Wallet to ensure that they are all valid. The location of the wallet is based on the SEC_PRINCIPAL_LOCATION and SEC_PRINCIPAL_NAME parameters, where SEC_PRINCIPAL_NAME corresponds to principal_name. The Using Security in ATMI Applications document provides further information on the location of the Oracle Wallet and on how to display certificates in a Wallet. | |
6920 |
ERROR: Certificate in local chain with subject subject has expired | |
|
Description |
One or more of the certificates in the certificate chain for principal subject has expired. |
Action |
If subject should be allowed to access the application, then examine the certificates in the certfiicate chain and obtain new certificates from your certificate authority. | |
6921 |
ERROR: Certificate in local chain with subject subject is not yet valid | |
|
Description |
One or more of the certificates in the certificate chain for principal subject is not valid until some time in the future. |
Action |
If the clock setting on the current machine is incorrect, have the administrator fix the time. If subject should be allowed to access the application, then examine the certificates in the certfiicate chain and obtain new certificates from your certificate authority that are currently valid. | |
6922 |
INFO: Use address as the binding address to estalish connection. | |
|
Description |
Use the specified IP address as the binding address to estalish connection. |
Action |
No action required. | |
6929 |
ERROR: Cannot load OCI library | |
|
Description |
Failed to load OCI library dynamically. |
Action |
Check the user OCI library name specified by the user. Make sure that the OCI library can be accessed successfully. | |
6930 |
ERROR: Cannot enable staic OCI UCB registration | |
|
Description |
The static OCI UCB registration is only supported by XA server which is associated with Oracle Database. |
Action |
Check if the server is XA server and connects to a Oracle Database. | |
6931 |
WARN: Cannot update instance information | |
|
Description |
The server cannot update its instance information into BB due to some reason. Any feature which depends on the instance information cannot work well on this server. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
6932 |
ERROR: Cannot get OCI service context | |
|
Description |
The server fails to retrieve its instance information from the Oracle database because it cannot get OCI service context. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
6933 |
ERROR: Cannot get OCI environment context | |
|
Description |
The server fails to retrieve its instance information from the Oracle database because it cannot get OCI environment context. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
6934 |
ERROR: Cannot deregister OCI UCB for OCISessionBegin:error | |
|
Description |
The server fails to deregister its OCI UCB for OCISessionBegin because of the error. |
Action |
Check the error reporting mechanism for the associated resource manager. | |
6935 |
ERROR: Cannot deregister OCI UCB for OCISessionBegin:errno | |
|
Description |
The server fails to deregister its OCI UCB for OCISessionBegin because of the errno. |
Action |
Check the error reporting mechanism for the associated resource manager. | |
6936 |
WARN: Cannot store instance information for database[database name] instance[instance name] service[service name], errno=error. No instance information is used for this process | |
|
Description |
The server fails to store its instance information into BB. Any feature which depends on this information can not work well on this server. |
Action |
Check the error reporting mechanism for the associated resource manager. | |
6937 |
ERROR: Cannot get current exit callback for OCISessionBegin:error | |
|
Description |
The server fails to get the current exit UCB for OCISessionBegin because of the error. |
Action |
Check the error reporting mechanism for the associated resource manager. | |
6938 |
ERROR: Cannot get current exit callback for OCISessionBegin:errno | |
|
Description |
The server fails to get the current exit UCB for OCISessionBegin because of the errno. |
Action |
Check the error reporting mechanism for the associated resource manager. | |
6939 |
ERROR: Cannot register exit callback for OCISessionBegin:error | |
|
Description |
The server fails to register the exit UCB for OCISessionBegin because of the error. |
Action |
Check the error reporting mechanism for the associated resource manager. | |
6940 |
ERROR: Cannot register exit callback for OCISessionBegin:errno | |
|
Description |
The server fails to register the exit UCB for OCISessionBegin because of the errno. |
Action |
Check the error reporting mechanism for the associated resource manager. | |
6943 |
ERROR: Cannot add Tuxedo package to environment variable ORA_OCI_UCBPKG | |
|
Description |
For servers that use dynamic callback registration, the |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
6944 |
WARN: Ignore unknown -F option input argument argument | |
|
Description |
The argument of -F option is unknown. The argument of -F option can be but not litmited to "noECID". |
Action |
Check the usage of -F option. | |
6951 |
ERROR: cannot add data into META_TCM, err=error | |
|
Description |
The internal buffer META_TCM cannot store more data. |
Action |
Contact your Oracle TUXEDO system Technical Support. | |
6953 |
INFO: Page page skipped, unsupported feature | |
|
Description |
The page page in TLOG is skipped because the transaction in this page is logged by a feature which is not supported by current Tuxedo application. |
Action |
Confirm which feature logged this page, enable this feature in the current Tuxedo application and retry. | |
6954 |
ERROR: RM down | |
|
Description |
The RM which is associated with tuxedo server is down. |
Action |
Check RM status. | |
6955 |
INFO: Page page skipped, unsupported feature | |
|
Description |
The page page was skipped because bypass domain feature is not enabled. |
Action |
No action required. | |
6956 |
WARN: tpreturn called with TPSUCCESS after original transaction has been aborted | |
|
Description |
A service was invoked within a transaction and |
Action |
No action is required. However, the application may want to ensure that ATMI calls such as |
![]() |
![]() |
![]() |