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 `SHMQMAXMEM` parameter in `UBBCONFIG` file.
	See Also	`UBBCONFIG`(5)
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 `ewallet.p12` file is located. Subsequent attempts to access security credentials for principal_name will use the Oracle Wallet that has been created. When the tlisten process converts legacy security credentials to the Oracle Wallet format, it does so before forking a separate process to run in the background. Therefore, when this informational message is logged by tlisten, the process ID in the userlog will be different from the process ID of the tlisten process that is running in the background. This is an expected behavior.
	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 `fopen()` library call on file wallet_loc failed with errno set to errno.
	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 `chmod()` system call on newly created wallet file wallet_loc failed with errno set to errno.
	Action	Since an `fopen()` on the wallet file succeeded just before the `chmod()` failure, this message is not expected to normally occur. Investigate if another process may have removed, created, or modified the wallet_loc in the interval between the `fopen()` and `chmod()` calls.

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 `TUXNZTRACE=8191` will generate a `trace-`pid`.log` trace file. The trace output can be helpful in determining why an SSL error is occuring. If the process on the other side of the connection is not a Tuxedo process, it is possible that the peer may not support SSL renegotiation. If this is the case, then renegotiation should be turned off.

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 `TUXNZTRACE=8191` will generate a `trace-`pid`.log` trace file. The trace output can be helpful in determining why an SSL error is occuring. If the process on the other side of the connection is not a Tuxedo process, it is possible that the peer may not support SSL renegotiation. If this is the case, then renegotiation should be turned off.

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.