システム・メッセージ: LIBTUXカタログ6800-6899


6800	*WARN: rule* not supported rule**
	Description	The rule is not supported by this machine.
	Action	Please upgrade this Tuxedo version or install the new rolling patch.

6801	*ERROR: Line lineno, bad section type*
	Description	The section type is invalid.
	Action	Contact Oracle Customer Support.

6802	*ERROR: Line lineno, bad message severity*
	Description	The event action message severity is invalid.
	Action	Please check the line event message severity, the valid values are: Information, Warn, Critical and Fatal.
	See Also	See TSAM Plug-in Event User Guide
6803	エラー: パラメータ・ファイルは存在します
	説明	ルール・ファイルが存在します。
	アクション	ファイルを削除するか、名前を変更してください。

6804	エラー: 書き込むためにオープンできません
	説明	書込みのためにルール・ファイルをオープンできません。
	アクション	ディレクトリまたはファイル名が正しく、書込み権限があるかどうかを確認してください。

6805	エラー: パラメータ・ファイルにstatを実行できません
	説明	パラメータ・ファイルから情報を取得できません。
	アクション	ディレクトリまたはファイル名が正しく、アクセス権があるかどうかを確認してください。

6806	エラー: バッファ・サイズが小さすぎます
	説明	掲示板にルールを保持するための十分な領域がありません。
	アクション	構成に応じてUBBCONFIGのMAXSPDATAの値を増やしてください。
	関連項目	TSAMプラグイン・イベント・ユーザー・ガイドを参照してください。
6807	*WARN: Line lineno, duplicated rule rule, use new one*
	Description	The global or report policy is repetitious.
	Action	Delete the repetitious rule.

6808	*WARN: Line lineno, duplicated rule, ignore it*
	Description	The service,call path or BBL rule is repetitious.
	Action	Delete the repetitious rule.

6809	ERROR: The buffer size is too small, the required size is bufsize
	Description	There is no enough space in bulletin board to hold the rules.
	Action	Please increase MAXSPDATA in UBBCONFIG according to your configuration.
	See Also	See TSAM Plug-in Event User Guide
6810	エラー: メモリー割当てエラー
	説明	オペレーティング・システムから動的にメモリーを割り当てようとしましたが失敗しました。
	アクション	マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。

6811	エラー: トリガー・ルールに対してmutexをロックできませんでした
	説明	TSAMプラグイン・イベント・トリガー・プロセスでmutexのロックに対して内部エラーが発生しました。
	アクション	Oracleカスタマ・サポートに連絡してください。

6812	エラー: イベント・アクション処理で失敗したFML32バッファを割当てできませんでした
	説明	TSAMプラグイン・イベント・トリガー・プロセスでTuxedo FML32型付きバッファを割り当てようとしましたが、失敗しました。
	アクション	マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。この問題が解決しない場合は、Oracleカスタマ・サポートに連絡してください。

6813	エラー: イベント・アクション処理で失敗したFML32バッファを再割当てできませんでした
	説明	TSAMプラグイン・イベント・トリガー・プロセスでTuxedo FML32型付きバッファを再割当てしようとしましたが、失敗しました。
	アクション	マシンのメモリー量およびプロセスによって使用されるメモリー量に対して、オペレーティング・システム・パラメータが正しく設定されていることを確認してください。マシンのメモリー使用量を減らすか、マシンの物理メモリー量を増やしてください。この問題が解決しない場合は、Oracleカスタマ・サポートに連絡してください。

6814	*ERROR: Fcpy32 returns error(number) in event action handling*
	Description	TSMA PLug-in event trigger process failed to invoke Fcpy32 routine.
	Action	Contact Oracle Customer Support.

6815	*ERROR: Fchg32 returns error(number) in event action handling*
	Description	TSMA PLug-in event trigger process failed to invoke Fchg32 routine.
	Action	Contact Oracle Customer Support.

6816	*ERROR: tppost returns error(number) in event action handling*
	Description	TSMA PLug-in event trigger process failed to invoke tppost routine when post an event to Tuxedo Event Broker.
	Action	The most likely reason is Tuxedo Event Broker is not configured in your Tuxedo domain but the destination of the event is specified to "eventbroker" in the trigger rules file. Setup TMUSREVT server in UBBCONFIG.
	See Also	See Manual of TMUSREVT(5).
6817	*ERROR: Line lineno, bad destination*
	Description	The action destination is invalid.
	Action	Please check the event action destination. The valid values are: 'eventbroker' or 'tsammanager'.
	See Also	See TSAM Plug-in Event User Guide
6818	*ERROR: Line lineno, event name is too long*
	Description	The event name is too long.
	Action	The maximum length of event name is 31.

6819	*ERROR: Line lineno, field_name* cannot exist in the rule rule_section section**
	Description	The field can not be configured in the rule section.
	Action	Please check if the keyword is in a suitable rule section. We support different keywords for different rule section. Please reference TSAM Plug-in Event User Guide for detail.
	See Also	See TSAM Plug-in Event User Guide
6820	*ERROR: A workstation client(ip address address) does not have a proper application password*
	Description	The application password authentication was failed for a workstation client.
	Action	Check ULOG and find the ip address. Then make sure the client on this address has a correct application password if the security level is APP_PW or above.

6821	ERROR: xa_rollback returned error for group groupname
	Description	This message is issued when Oracle TUXEDO tries unsuccessfully to rollback a transaction via xa_rollback() after receiving a reply. The message prints the error code that the function returned.
	Action	Contact your Oracle 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.

6822	ERROR: xa_rollback returned errcode for group groupname
	Description	This message is issued if a process attempting to commit a transaction could not unlock the bulletin board. It then attempted to roll back the transaction, and encountered an error when calling the database resource manager's `xa_rollback()` routine. The message prints the error code that `xa_rollback()` returned.
	Action	Contact your Oracle TUXEDO system Technical Support or your database system vendor. The database system documentation or error logs may contain more information about why `xa_rollback()` failed.

6823	エラー: TSAM SDKライセンスにはTuxedo SDKライセンスが必要です
	説明	TSAM SDKライセンスを使用するTuxedo SDKライセンスがないため、TSAMライセンスのチェックに失敗しました。
	アクション	TSAM SDKライセンスには有効なTuxedo SDKライセンスが必要です。Oracleサポートに連絡してTuxedo SDKライセンスを入手してください。

6824	エラー: TSAMのライセンスがありません
	説明	TSAMのライセンスがありませんが、TSAMの機能が使用されています。
	アクション	TSAMは、個別のライセンスが必要な製品です。Oracleサポートに連絡してTSAMライセンスを入手してください。

6825	エラー: TSAMライセンスの期限が切れています
	説明	TSAMライセンス日付の期限が切れています。
	アクション	Oracleサポートに連絡してTSAMライセンスを更新してください。

6826	INFO: TSAM License Serial #: serial, Expiration date
	Description	TSAM License information.
	Action	None.

6827	INFO: TSAM Licensed to : owner
	Description	TSAM License owner information.
	Action	None.

6828	ERROR: Field name not found for id fieldid
	Description	While doing service contract discovery, discovery process parses the FML buffer to get buffer field contract detail information when buffer type is FML or FML32. The operation tries to get FML/FML32 field name using the buffer field identifier. Upon the operation failure, this message is displayed.
	Action	Make sure FML/FML32 required environment variables are set correctly for the server that enabled service contract discovery.

6829	ERROR: Call .SCD failed with error val
	Description	Service contract discovery module failure. Cannot send contract information to TMMETADATA server.
	Action	Make sure TMMETADATA server is configured correclty in UBBCONFIG. If TMMETADATA is in "readonly" mode, "-o" must be specified for the output text file.
	See Also	`TMMETADATA`(5)
6830	警告: SCA管理スレッドの作成中にエラーが発生しました。SCA管理スレッドなしで開始します。
	説明	通常SCAサーバーでscaadmin統計リクエストの処理に使用されるSCA管理スレッドで使用するためのmutexまたはcondition変数を作成しようとして、エラーが発生しました。このため、サーバーで現在実行されている他の操作がある場合は、scaadmin統計リクエストの処理が遅延します。
	アクション	サーバーを再起動して、問題が引き続き発生するかどうかを確認してください。問題が解決しない場合は、Oracleサポートに連絡してください。

6831	警告: SCA管理スレッドの作成に失敗しました。SCA管理スレッドなしで開始します。
	説明	通常SCAサーバーでのscaadmin統計リクエストの処理に使用されるSCA管理スレッドの作成中に、スレッド作成エラーが発生しました。このため、サーバーで現在実行されている他の操作がある場合は、scaadmin統計リクエストの処理が遅延します。
	アクション	サーバーを再起動して、問題が引き続き発生するかどうかを確認してください。オペレーティング・システムを確認して、システムに十分なスレッド・リソースがあるかどうかを確認してください。問題が解決しない場合は、Oracleサポートに連絡してください。

6832	警告: SCAサーバーが非スレッドのプラットフォーム上で実行しています。
	説明	このハードウェア・プラットフォームではマルチスレッド機能がサポートされていないため、このSCAサーバーが、通常scaadmin統計リクエストの処理に使用される管理スレッドを作成できませんでした。このため、サーバーで現在実行されている他の操作がある場合は、scaadmin統計リクエストの処理が遅延します。
	アクション	アクションは不要です。

6833	*ERROR: Workstation client(ip address address) does not have proper application password*
	Description	Workstation client is using wrong application password.
	Action	Use correct application password in workstation client.

6834	*ERROR: Workstation client(ip address address) authentication failure*
	Description	Workstation client authentication failure.
	Action	Check the tuxedo application security setting and ensure workstation client is compliant.

6835	*ERROR: Service servicename* in BEGIN session role is forwarding request**
	Description	Service in BEGIN session role is forwarding a request
	Action	Do not use tpforward in services where SESSIOROLE is set to BEGIN

6836	*ERROR: Service servicename* in END session role is forwarding request**
	Description	Service in END session role is forwarding a request
	Action	Do not use tpforward in services where SESSIOROLE is set to END

6837	ERROR: Service servicename in BEGIN session role cannot be invoked with TPNOREPLY flag
	Description	Service in BEGIN session role cannot be invoked with TPNOREPLY flag
	Action	Do not call services where SESSIONROLE is set to BEGIN with TPNOREPLY flag if you want to use Client/Server affinity feature correctly.

6838	ERROR: Service servicename in END session role cannot be invoked with TPNOREPLY flag
	Description	Service in END session role cannot be invoked with TPNOREPLY flag
	Action	Do not call services where SESSIONROLE is set to END with TPNOREPLY flag if you want to use Client/Server affinity feature correctly.

6839	ERROR: Service servicename in BEGIN session role in conversation server
	Description	Service in BEGIN session role is advertised by conversation server
	Action	Do not allow services on the conversation server to be set with BEGIN session role.

6840	ERROR: Service servicename in END session role in conversation server
	Description	Service in END session role is advertised by conversation server
	Action	Do not allow services on the conversation server to be set with END session role.

6841	ERROR: Install Oracle TSAM before enabling TM_RQSTLIVETIME.
	Description	To enable the Clean Stale Request feature, Oracle TSAM must be installed first
	Action	Purchase Oracle TSAM and install.

6842	*INFO: Message request dropped. In queue longer than times SCANUNIT, as specified by TM_RQSTLIVETIME.
	Description	A stale message request is dropped.
	Action	None.

6843	*ERROR: File filename* specified in TM_RQSTLIVETIME cannot be opened.**
	Description	File specified in TM_RQSTLIVETIME cannot be found or is unreadable.
	Action	Specify a valid file (under $APPDIR) in TM_RQSTLIVETIME. Lines in this file must use the format: =. For example: TOUPPER=2 IDL:beasys.com/Simple:1.0=3 default=2

6844	*ERROR: [Unable to find `TUXCONFIG` file RMS section]**
	Description	`tmboot` cannot find the `RMS` section of the Tuxedo configuration file.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, `TUXCONFIG` is not corrupted, and `TUXCONFIG` was propagated to all machines in MP mode.
	See Also	`UBBCONFIG`(5), `tmboot`(1)
6845	ERROR: Unable to read the `RMS` section of the `TUXCONFIG` file
	Description	`tmboot` cannot read the `RMS` section of the Tuxedo configuration file.
	Action	Verify that the environment variable `TUXCONFIG` is set correctly and exported, `TUXCONFIG` is not corrupted, and `TUXCONFIG` was propagated to all machines in MP mode.
	See Also	`UBBCONFIG`(5), `tmboot`(1)
6846	*ERROR: Resource manager identifier rmid* of group groupname error.**
	Description	The `RMID` attribute of a resource manager specified in `RMS` section must be between 1 and 31, inclusive.
	Action	Make sure the `RMID` configured in `RMS` is a valid value.
	See Also	`UBBCONFIG`(5)
6847	*ERROR: Resource manager identifier rmid* xa switch is not set.**
	Description	The required xa switch symbol specified by rmid in the `RMS` section cannot be found in the internal xa switch symbol table which was created when building this server. A Tuxedo serverwhich supports MRM initializes its xa switch table in booting stage by matching the resource manager name specified in `OPENINFO` string and the name specified by `buildserver` with `-r` option. If a matched resource manager is found, this server sets the xa switch table with the rmid otherwise this message is logged.
	Action	Make sure the resource manager name is correct and consistent with the name in the `RM` file.
	See Also	`UBBCONFIG`(5), `buildserver`(1)
6848	*ERROR: Resource manager identifier rmid* xa switch is not supported.**
	Description	It is not allowed to configure an old preliminary version of XA resource manager in `RMS` section.
	Action	Delete the item which specifies an old preliminary version of XA resource manager.
	See Also	`UBBCONFIG`(5), `buildserver`(1)
6850	ERROR: tprmopen TPERMERR xa_open for resource manager rmid returned errstring
	Description	The call to `xa_open`() from within `tprmopen` returned the XA error value string. As a result, resource manager rmid could not be opened.
	Action	Look for `RMID=`rmid in the TUXCONFIG file to determine which resource manager rmid is associated with. Verify that the `OPENINFO` string for this resource manager matches the proper syntax and configuration values for that resource manager. Check the error reporting mechanism for the recource manager to determine if there is any further information about the cause of the problem. Contact the resource manager vendor technical support organization if needed.
	See Also	`tprmopen`(3), Distributed Transaction Processing: The XA Specfication, X/Open Company Limited, 1991.
6851	*エラー: TUXCONFIGファイルのRMSセクションを読み取れません。**
	説明	`tprmclose`()関数が、構成されているリソース・マネージャに関する情報を取得するためにTUXCONFIGファイルを読み取れませんでした。このため、`tprmclose`()はリクエストされたリソース・マネージャをクローズできませんでした。
	アクション	Tuxedoの実行中にTUXCONFIGファイルまたはTuxedo共有メモリーが誤って削除されなかったことを検証してください。このエラーが常に発生する場合は、Oracleサポートに連絡してください。
	関連項目	`tprmclose`(3)
6852	*ERROR: tprmclose resource manager rmid* TPERMERR xa_close returned errstring.**
	Description	The call to `xa_close`() from within `tprmclose` returned the XA error value string. As a result, resource manager rmid could not be closed.
	Action	Look for `RMID=`rmid in the TUXCONFIG file to determine which resource manager rmid is associated with. Check the error reporting mechanism for that recource manager to determine the cause of the problem. Contact the resource manager vendor technical support organization or Oracle support as appropriate.
	See Also	`tprmclose`(3), Distributed Transaction Processing: The XA Specfication, X/Open Company Limited, 1991.
6853	ERROR: tprmstart resource manager rmid xa_start returned errstring
	Description	The call to `xa_start`() from within `tprmstart` returned the XA error value string. As a result, resource manager rmid could not be associated with the transaction.
	Action	Look for `RMID=`rmid in the TUXCONFIG file to determine which resource manager rmid is associated with. Check the error reporting mechanism for that recource manager to determine the cause of the problem. Contact the resource manager vendor technical support organization or Oracle support as appropriate.
	See Also	`tprmstart`(3), Distributed Transaction Processing: The XA Specfication, X/Open Company Limited, 1991.
6854	エラー: 進行中のトランザクションでtprmcloseが呼び出されました
	説明	`tprmclose()`が、(`tpbegin()`または`txbegin()`が呼び出された)グローバル・トランザクション内で呼び出されました。
	アクション	`tprmclose()`を呼び出す前に、`tpcommit()`または`tpabort()`によってトランザクションが完了している必要があります。
	関連項目	`tpabort`(3c)、`tpbegin`(3c)、`tpclose`(3c)、`tpcommit`(3c)、`tprmopen`
6856	ERROR: Cannot find xa switch symbol with specific resource manager name in OPENINFO string.
	Description	The resource names specified in `buildserver` are not consistent with the resource names specified in the `OPENINFO` string in the `RMS` sections.
	Action	Make sure all the required resource manager symbols are imported while executing `buildserver` with `-r` option, and the resource manager name is consistent with the name configured in `OPENINFO` string in `RMS` section.
	See Also	`buildserver`(1), `UBBCONFIG`(5)
6857	ERROR: FML32 field name fieldname specified for routing criteria routingname has field type typenum which exceeds the allowed maximum of maxtypenum
	Description	FML32 field fieldname was specified for routing entry routingname, but this field has type typenum which is greater than the maximum allowable type number maxtypenum, which is currently equal to 7.
	Action	Specify a routing field with a valid type. The only FML32 types currently allowed for routing are short (0), long (1), char (2), float (3), double (4), string (5), and carray (6).
	See Also	`UBBCONFIG`(5), `Programming an Oracle Tuxedo ATMI Application Using FML`
6858	ERROR: FML32 field name fieldname specified for routing criteria routingname has field number fldnum which exceeds the allowed maximum of maxroutefldnum
	Description	FML32 field fieldname was specified for routing entry routingname, but this field has number fldnum which is greater than the maximum allowable routing field number maxroutefldnum, which is currently equal to 8191.
	Action	Specify a routing field with a field number less than or equal to 8191.
	See Also	`UBBCONFIG`(5), `Programming an Oracle Tuxedo ATMI Application Using FML`
6867	エラー: TLOGがデータベースに格納されている場合、TLOGNAMEを指定する必要があります
	説明	データベースにtlogを書き込む場合は、データベースでの競合を避けるために`TLOGNAME`を設定する必要があります。
	アクション	`UBBCONFIG`で`TLOGNAME`を設定してください。
	関連項目	`ubbconfig`(5)
6868	ERROR: action met a database error:errmsg
	Description	You met a database error :errmsg when tuxedo write/read tlog infomation from database.
	Action	Contact your DBA according to the error message.

6869	*WARN: TM_ENVFILE_BEFOREBOOT doesn't taken effect for servername.*
	Description	Environment variable "TM_ENVFILE_BEFOREBOOT" doesn't taken effect for this server.
	Action	None.

6870	WARNING: Could not load OCI library. Library name is longer than the allowed length.
	Description	Failed to load OCI library dynamically.
	Action	Check the user OCI library name specified by the user. Make sure the lenth of OCI library name is no longer than 255.

6871	WARNING: Could not load OCI library. oci_generic_init failed.
	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.

6872	WARNING: Could not create OCI environment. _OCIEnvCreate failed with errcode = %d.
	Description	Failed to setup the OCI environment for ECID propagation from Oracle Tuxedo to Oracle DB.
	Action	Make sure that the environment variables for OCI have been set correctly. If the problem persists, contact Oracle Customer Support.

6873	WARNING: Could not register OCI roundtrip callback. Status = %d.
	Description	Failed to setup the OCI environment for ECID propagation from Oracle Tuxedo to Oracle DB.
	Action	Check the version of OCI library. Make sure that the OCI library supports the OCI roundtrip callback feature.

6874	WARNING: Could not register OCI roundtrip callback context. Status = %d.
	Description	Failed to setup the OCI environment for ECID propagation from Oracle Tuxedo to Oracle DB.
	Action	Check the version of OCI library. Make sure that the OCI library supports the OCI roundtrip callback feature.

6875	*ERROR: Could not load DMS library libname, err = code.*
	Description	Failed to load DMS library libname dynamically, receive error 'code'.
	Action	Check the Oracle Tuxedo installation. If the installation is fine but problem persists, contact Oracle Customer Support.

6876	*ERROR: Could not get DMS library function funname, err = code.*
	Description	The process received the error 'code' while trying to read the DMS function funname from the DMS library.
	Action	Check the Oracle Tuxedo installation. If the installation is fine but problem persists, contact Oracle Customer Support.

6877	*ERROR: nzos_SetThrUse returned error error_number* [error_string]**
	Description	An error occurred while setting up the Oracle NZ security layer to operate in multithreaded mode. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string.
	Action	Verify that the application is not linked with a different version of the Oracle security layers than the version provided with Tuxedo. If the problem persists, contact Oracle customer support.

6878	*ERROR: nzos_SetSqlnetFunc returned error error_number* [error_string]**
	Description	An error occurred while setting up callback functions for the Oracle NZ security layer. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string.
	Action	Verify that the application is not linked with a different version of the Oracle security layers than the version provided with Tuxedo. If the problem persists, contact Oracle customer support.

6879	*ERROR: NZ Toolkit initialization returned error error_number* [error_string]**
	Description	An error occurred while initializing the Oracle NZ security layer. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string.
	Action	Verify that the application is not linked with a different version of the Oracle security layers than the version provided with Tuxedo. If the problem persists, contact Oracle customer support.

6880	エラー: SEC_PRINCIPAL_LOCATIONが設定されていません
	説明	SSL接続のサーバー側のプロセスまたは相互認証を使用したSSL接続のクライアント側のプロセスは、SSL接続の相手側が検証するセキュリティ資格証明を提供する必要があります。セキュリティ資格証明にOracle Walletが使用されている場合は、SEC_PRINCIPAL_LOCATIONを使用してウォレットの位置を指定します。従来のセキュリティ資格証明が使用されている場合は、SEC_PRINCIPAL_LOCATIONで秘密鍵の位置を指定します。 SEC_PRINCIPAL_PASSVARパラメータは、SEC_PRINCIPAL_LOCATIONをオープンするために必要なパスワードを含む環境変数の名前を指定します。(掲示板にアタッチされていないプロセスでは、これに相当するパスワードを含む環境変数はSEC_PRINCIPAL_PASSWORDです。)
	アクション	TUXCONFIGファイルのSEC_PRINCIPAL_LOCATIONおよびSEC_PRINCIPA_PASSVARパラメータを適切な値に設定してください。

6881	*ERROR: Cannot stat Oracle Wallet \"wallet_loc\"*
	Description	The `stat`() system call failed on Oracle Wallet location wallet_loc for a reason other than that this file or directory failed to exist.
	Action	Ensure that permissions allow searching all directories above wallet_loc and taht there is not a looping symbolic link in the wallet_loc path.

6882	*ERROR: Cannot open Oracle Wallet \"wallet_loc\", error error_number* [error_string]**
	Description	Tuxedo was unable to open the Oracle Wallet located in directory wallet_loc. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string.
	Action	Ensure that the wallet_loc directory exists, that it contains an `ewallet.p12` file, that this file is readable, and that it is a valid PKCS 12 file.

6883	*ERROR: nzosSetCredential returned error error_number* [error_string]**
	Description	The function used to set SSL security credentials in the Oracle NZ security layer failed. The error returned by the Oracle NZ security layer was error_number and a text description of that error is error_string.
	Action	Examine the error returned by the Oracle NZ security layer for information about the cause of the error. Ensure that the Oracle Wallet contains all credentials needed by the application. For example, if the process is on the server side of the SSL connection, ensure that the Oracle Wallet contains a private key and a certificate.

6884	ERROR: No supported cipher suites found. Please check the configured minimum bits = minbits and maximum bits = maxbits
	Description	No supported SSL cipher suites with a strengh of between minbits and maxbits were found.
	Action	Change the values of minbits and maxbits. Remember that 0 bit SSL cipher suites (which do not actually use any encryption) are not allowed in Tuxedo 12c and above.

6885	*"ERROR: SSL Handshake failed with error error_number* [error_string]**
	Description	An error occurred during the SSL handshake process and this process was unable to establish an SSL connection. 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 cause tlisten to generate a `trace-`pid`.log`. The trace output will contain information sent during the SSL handshake and can be very helpful in determining why a particular certificate chain is not considered valid or why there is some other error in the SSL handshake process.