システム・メッセージ: CMDGWカタログ3800-3899


3800	WARN: SSL_RENEGOTIATION > 0 specified with NWPROTOCOL of LLE.
	Description	An entry in the DM_TDOMAIN section of the DMCONFIG(5) file did not specify an NWPROTOCOL parameter or specified the default value of LLE, but this DM_TDOMAIN section entry also specfied a non-default value for the SSL_RENEGOTIATION parameter. The SSL_RENEGOTIATION parameter is only relevant when NWPROTOCOL is set to SSL_ONE_WAY. This connection will use LLE encryption and the SSL_RENEGOTIATION value specified will be ignored.
	Action	Modify the DMCONFIG file to specify consistent parameters for the DM_TDOMAIN section and reexecute dmloadcf(1)
	See Also	dmconfig(5)
3802	警告: TA_DMSSL_RENEGOTIATION > 0がLLEのTA_DMNWPROTOCOLで指定されました
	説明	DM_MIB(5)のT_DM_TDOMAINクラスのエントリを追加または更新するリクエストで、LLEのTA_DMNW_PROTOCOL値とともにTA_DMSSL_RENEGOTIATIONに対してゼロ以外の値が指定されました。 SSL再ネゴシエーションは、TA_DMNW_PROTOCOLがSSL_ONE_WAYに設定されている場合にのみ実行できます。MIB呼出しは正常に完了しますが、この警告メッセージが記録されます。
	アクション	アクションは不要です。ただし、このDM_MIB操作が今後再実行される予定がある場合は、DM_1MIB呼出しのパラメータを更新してください。
	関連項目	DM_MIB(5)
3803	エラー: パスワードの暗号化に失敗しました。
	説明	DMADMサーバーは、256ビットAESを使用してパスワードを正常に暗号化できませんでした。
	アクション	`$TUXDIR/udataobj/lic.txt`ファイルで256ビット暗号化の使用が許可されていることを検証してください。 256ビット暗号化のライセンスがある場合は、TUXEDOのテクニカル・サポート・センターに連絡してください。

3804	エラー: パスワードの暗号化に失敗しました。
	説明	システムは、256ビットAESを使用してパスワードを正常に暗号化できませんでした。
	アクション	`$TUXDIR/udataobj/lic.txt`ファイルで256ビット暗号化の使用が許可されていることを検証してください。 256ビット暗号化のライセンスがある場合は、TUXEDOのテクニカル・サポート・センターに連絡してください。

3805	ERROR: SSL_RENEGOTIATION > 0 specified with NWPROTOCOL of SSL. (SSL_RENEGOTIATION > 0 can only be specified with NWPROTOCOL of SSL_ONE_WAY.)
	Description	An entry in the DM_TDOMAIN section of the DMCONFIG(5) specified an NWPROTOCOL value of SSL and also specfied a non-default value for the SSL_RENEGOTIATION parameter. Due to technical issues with the underlying SSL encryption software, SSL_RENEGOTIATION is supported for an NWPROTOCOL of SSL_ONE_WAY, but is not supported for the two-way SSL used when NWPROTOCOL is set to SSL. This connection will use two-way SSL without renegotiaton.
	Action	Modify the DMCONFIG file to specify consistent parameters for the DM_TDOMAIN section and reexecute dmloadcf(1).
	See Also	dmconfig(5)
3806	*ERROR: Unknown CONNECTION_POLICY <type>. Only ON_DEMAND, ON_STARTUP, INCOMING_ONLY, PERSISTENT_DISCONNECT are recognized*
	Description	The value type specified for the `CONNECTION_POLICY` parameter for local domain is not valid. `ON_DEMAND`, `ON_STARTUP`, `INCOMING_ONLY`, and `PERSISTENT_DISCONNECT` are the acceptable CONNECTION_POLICY parameter values recognized by the local GWTDOMAIN Domain Gateway.
	Action	Specified a valid value and reload the configuration file.
	See Also	`dmconfig`(5)
3807	*ERROR: Unknown CONNECTION_POLICY <type>. Only ON_DEMAND, ON_STARTUP, INCOMING_ONLY, LOCAL, PERSISTENT_DISCONNECT are recognized values for remote TDOMAIN*
	Description	The value type specified for the `CONNECTION_POLICY` parameter for remote TDOMAIN is not valid. `ON_DEMAND`, `ON_STARTUP`, `INCOMING_ONLY`, `LOCAL`, and `PERSISTENT_DISCONNECT` are the acceptable CONNECTION_POLICY parameter values recognized by the remote GWTDOMAIN Domain Gateway.
	Action	Specified a valid value and reload the configuration file.
	See Also	`dmconfig`(5)
3808	*ERROR: field name: String value "field value" must be <= length* characters in length when an older Oracle Tuxedo release exists.**
	Description	An error was detected by the Domain Administrative server while processing a dynamic reconfiguration. The value field value found for entry field name is too long. The value must be less than or equal to length characters in length. For pre-Oracle Tuxedo 11gR1 releases, the resource name length is limited to 15 and remote service name is limited to 30.
	Action	Correct the value field value for the entry field name and retry the operation.
	See Also	`dmconfig`(5)
3809	*ERROR: Cannot set TA_DMRESOURCENAME. Service name length is greater than length* and there is an older Oracle Tuxedo release length on site site_name.**
	Description	An error was detected by the Domain Administrative server while processing a dynamic reconfiguration on TA_DMRESOURCENAME. The value of TA_DMRESOURCENAME is too long. The value must be less than or equal to length characters in length. For pre-Oracle Tuxedo 11gR1 releases, the resource name length is limited to 15.
	Action	Correct the value field value for the entry field name and retry the operation.
	See Also	`dmconfig`(5)
3810	ERROR: if set type=QSPACE, RDOM (or RACCESSPOINT ) must be set.
	Description	An error was detected when setting resource type to QSPACE but no value for RDOM (or RACCESSPOINT ).
	Action	Please specify a value to RDOM (or RACCESSPOINT ).
	See Also	`dmconfig`(5)
3820	*ERROR: Non encrypted part of DMTLOGDEV attribute must be <= val* characters in length**
	Description	The non-encrypted part of the `DMTLOGDEV` value entry of the configuration file must be <= 200 characters.
	Action	Specify a value that is less than or equal to 200 characters.
	See Also	`dmloadcf`(1), `dmconfig`(5)
3822	ERROR: Encryption error for DMTLOGDEV password
	Description	`dmloadcf` encountered an internal error while encrypting password provided in `DMTLOGDEV`
	Action	Please contact Oracle Customer Support.

3823	ERROR: Re-encryption error for DMTLOGDEV password
	Description	`DMTLOGDEV` was found encrypted in the `DMCONFIG` file during `dmloadcf`, but an attempt to decrypt it with an old key failed.
	Action	Replace the encrypted part of `DMTLOGDEV` with the "*****" string, and run `dmloadcf` again

3824	ERROR: DMTLOGNAME must be set when DMTLOG is stored in database
	Description	When you want write tlog into database,`DMTLOGNAME` must be set avoid conflict.
	Action	Set `DMTLOGNAME` in `DMCONFIG`.
	See Also	`dmconfig`(5)
3836	ERROR: Either "all" or a specific remote event has to be specified.
	Description	The event name or "all" is not specified when executing `advertiseevent` or `unadvertiseevent` subcommand.
	Action	Specify the event name or "all" when executing `advertiseevent` or `unadvertiseevent` subcommand.
	See Also	`dmadmin`(1)
3837	ERROR: _dmcf_open failed: Cannot open DM_EVT_IN section
	Description	Failed to open `DM_EVT_IN` section in `BDMCONFIG` file.
	Action	Shut down the application and re-generate the `BDMCONFIG` file.
	See Also	`dmconfig`(5)
3838	ERROR: _dmcf_open failed: Cannot open DM_EVT_OUT section.
	Description	Failed to open `DM_EVT_OUT` section in `BDMCONFIG` file.
	Action	Shut down the application and re-generate the `BDMCONFIG` file.
	See Also	`dmconfig`(5)
3839	*ERROR: Cannot read DM_EVT_IN section of BDMCONFIG file (string).*
	Description	Failed to read `DM_EVT_IN` section in `BDMCONFIG` file.
	Action	Shut down the application and re-generate the `BDMCONFIG` file.
	See Also	`dmconfig`(5)
3840	*ERROR: Cannot read DM_EVT_OUT section of BDMCONFIG file (string).*
	Description	Failed to read `DM_EVT_OUT` section in `BDMCONFIG` file.
	Action	Shut down the application and re-generate the `BDMCONFIG` file.
	See Also	`dmconfig`(5)
3841	ERROR: Cannot add DM_EVT_OUT entry into table.
	Description	The `GWADM` administrative server received a request to dynamically add a `DM_EVT_OUT` section entry to the shared memory. The server was unable to add the entry.
	Action	Contact Oracle Tuxedo Technical Support.
	See Also	`dmadmin`(1)
3842	ERROR: Cannot setup links from DM_EVT_OUT entry to routing/rdomentry.
	Description	The `GWADM` administrative server received a request to dynamically update a `DM_EVT_OUT` section entry. This message indicates that the update operation failed because it could not set up the links from the new (updated) entry to the remote domain entry.
	Action	Make sure the remote domain in the updated `DM_EVT_OUT` section entry exists in the `BDMCONFIG` file.
	See Also	`dmadmin`(1)
3843	ERROR: Cannot delete DM_EVT_OUT entry from table.
	Description	The `GWADM` administrative server received a request to dynamically delete a `DM_EVT_OUT` section entry from the shared memory. The server was unable to delete the entry.
	Action	Contact Oracle Tuxedo Technical Support.
	See Also	`dmadmin`(1)
3844	ERROR: Cannot find DM_EVT_OUT entry in table.
	Description	The `GWADM` administrative server received a request to dynamically update a `DM_EVT_OUT` section entry from the shared memory, but the server was unable to find the entry.
	Action	Make sure the corresponding `DM_EVT_OUT` section entry is correctly configured in `BDMCONFIG` file.
	See Also	`dmadmin`(1)
3845	ERROR: event name not specified.
	Description	The event name or "all" is not specified when executing `advertiseevent` or `unadvertiseevent`.
	Action	Specify event name or "all" when executing `advertiseevent` or `unadvertiseevent`.
	See Also	`dmadmin`(1)
3846	ERROR: Invalid event name specified.
	Description	The specified event name when executing `advertiseevent` or `unadvertiseevent` is not a valid event name.
	Action	Make sure the event name specified when executing `advertiseevent` or `unadvertiseevent` is configured in `DM_EVT_OUT` section in the BDMCONFIG file `DM_EVT_OUT` section.
	See Also	`dmadmin`(1)
3848	*ERROR: failed to unsubscribe event event_name.*
	Description	The `GWADM` administrative server failed to unsubscribe the event to event broker when user executes `unadvertiseevent` subcommand in dmadmin.
	Action	Make sure that this event has not been unsubscribed before.
	See Also	`dmadmin`(1)
3849	*ERROR: failed to subscribe event event_name.*
	Description	The `GWADM` administrative server failed to subscribe the event to event broker when user executes `advertiseevent` subcommand in `dmadmin`.
	Action	Make sure that this event has not been subscribed before.
	See Also	`dmadmin`(1)
3853	Cannot add DM_EVT_IN entry into table.
	Description	The `GWADM` administrative server received a request to dynamically add a `DM_EVT_IN` entry to the shared memory. The server was unable to add the entry.
	Action	Contact Oracle Tuxedo Technical Support.
	See Also	`dmadmin`(1)
3854	ERROR: Cannot setup links from DM_EVT_IN entry to ACL entry.
	Description	The `GWADM` administrative server received a request to dynamically update a `DM_EVT_IN` entry. The update operation failed because it could not set up links from the new (updated) entry to the ACL entry.
	Action	Make sure the ACL in the updated `DM_EVT_IN` entry exists in the `BDMCONFIG` file.
	See Also	`dmadmin`(1)
3855	ERROR: Cannot delete DM_EVT_IN entry from table.
	Description	The `GWADM` administrative server received a request to dynamically delete a `DM_EVT_IN` entry from the shared memory. The server was unable to delete the entry.
	Action	Contact Oracle Tuxedo Technical Support.
	See Also	`dmadmin`(1)
3856	*ERROR: Duplicated event name (REVTNAME) occurs in DM_EVT_IN section.**
	Description	The `REVTNAME` and `LACCESSPOINT` combination in `DM_EVT_IN` section has duplicated entry in the `BDMCONFIG` file.
	Action	Make sure `REVTNAME` and `LACCESSPOINT` combination in `DM_EVT_IN` section is unique.
	See Also	`dmconfig`(5)
3857	*ERROR: Duplicate event:LDOM:RDOM combination exists for event_name* in DM_EVT_OUT section*
	Description	The event_name, `LACCESSPOINT` and `RACCESSPOINT` combination in `DM_EVT_OUT` section has duplicated entries in the `BDMCONFIG` file.
	Action	Make sure event_name, `LACCESSPOINT` and `RACCESSPOINT` combination in `DM_EVT_OUT` section is unique.
	See Also	`dmconfig`(5)
3858	*ERROR: EVT_TRAN(string) can only be either Y or N.*
	Description	In `BDMCONFIG` file , the `EVT_TRAN` for the entry in `DM_EVT_OUT` section is not set to be either Y or N.
	Action	Make sure `EVT_TRAN` for the entry of `DM_EVT_OUT` section in `BDMCONFIG` file is set to be either Y or N.
	See Also	`dmconfig`(5)
3861	ERROR: Cannot get remote domain.
	Description	The `GWADM` administrative server failed to get remote domain for one event in `DM_EVT_OUT` section.
	Action	Make sure any of the events in `DM_EVT_OUT` section at least has one remote domain whose type is TDOMAIN.
	See Also	`dmadmin`(1)
3862	ERROR: failed to allocate memory for remote domains for DM_EVT_OUT entry.
	Description	The `GWADM` administrative server failed to allocate memory to store remote domains for `DM_EVT_OUT` section entry.
	Action	Contact Oracle Tuxedo Technical Support.
	See Also	`dmadmin`(1)
3863	ERROR: Cannot find DM_EVT_IN entry in table.
	Description	The `GWADM` administrative server received a request to dynamically update a `DM_EVT_IN` section entry. But `GWADM` server failed to find out the entry in `DM_EVT_IN` section shared memory table.
	Action	Make sure `DM_EVT_IN` section entry to be updated has been configured in `BDMCONFIG` file.
	See Also	`dmadmin`(1)
3865	ERROR: Get internal buffer failed.
	Description	`GWADM` administrative server failed to get internal buffer to contact with `GWTDOMAIN` to do dynamic configuration.
	Action	Contact Oracle Tuxedo Technical Support.
	See Also	`dmadmin`(1)
3866	ERROR: Operation failed: unable to contact gateway.
	Description	`GWADM` administrative server failed to contact with `GWTDOMAIN` to do dynamic configuration.
	Action	Contact Oracle Tuxedo Technical Support.
	See Also	`dmadmin`(1)
3867	エラー: イベントのサービスを照会できません。
	説明	`DM_EVT_OUT`セクションのエントリを削除する際、`GWADM`管理サーバーが`GWTDOMAIN`によってイベントを処理する`GWTDOMAIN`サービスの取得に失敗しました。
	アクション	Oracle Tuxedoのテクニカル・サポートに連絡してください。
	関連項目	`dmadmin`(1)
3868	ERROR: Cannot delete service of event.
	Description	When deleting entry in `DM_EVT_OUT` section, `GWADM` administrative server failed to unadvertise the `GWTDOMAIN` service of where `GWTDOMAIN` handles the event.
	Action	Contact Oracle Tuxedo Technical Support.
	See Also	`dmadmin`(1)
3869	ERROR: Unexpected character in version range string. Check the version range string: configured_version_range_string
	Description	The `VERSION_RANGE` string in DM_IMPORT section contains an unexpected character. It should only contain numeric character and '-'. The correct format is "minimum_version* - maximum_version". The minimum_version and maximum_version is numberic string and should only contain numeric character: '0123456789'.
	Action	Specify the VERSION_RANGE string according to the correct format in *DM_IMPORT.
	See Also	`dmconfig`(5)
3870	ERROR: The invalid_string is not a valid numeric string. Check the version range string: configured_version_range_string
	Description	The `VERSION_RANGE` string in DM_IMPORT section is invalid, it should only contain numeric character and '-'. The correct format is "minimum_version* - maximum_version". The minimum_version and maximum_version is numberic string and should only contain numeric character: '0123456789'.
	Action	Specify the `VERSION_RANGE` string according to the correct format in *DM_IMPORT section.
	See Also	`dmconfig`(5)
3871	ERROR: The minimum version number invalid_min_value: is not valid, it should min_value <= max_value, please check the version range string: configured_version_range_string
	Description	The minimum version number specified in `VERSION_RANGE` string in DM_IMPORT section is out of range, the valid number should be in the range: 0-65535.
	Action	Specify a valid maximum version number in `VERSION_RANGE` string.
	See Also	`dmconfig`(5)
3872	ERROR: The maximum version number max_value: is not valid, it should min_value <= max_value. Check the version string: configured_version_range_string
	Description	The maximum version number specified in VERSION_RANGE string in *DM_IMPORT section is out of range, the valid number should be in the range: 0-65535.
	Action	Specify a valid maximum version number in VERSION_RANGE string.
	See Also	`dmconfig`(5)
3873	ERROR: The maximum version: max_value < minimum version: min_value. Check the version string: configured_version_range_string
	Description	The minimum version number is great than the maximum version number in `VERSION_STRING` string in *DM_IMPORT section.
	Action	Make sure the minimum version number is less than or equal to the maximum version number in VERSION_STRING string.
	See Also	`dmconfig`(5)
3874	ERROR: The import service imported_service_name `VERSION_RANGE` configured_version_range_string *is not correct. The valid number should be "0-65535"*
	Description	The `VERSION_RANGE` string in DM_IMPORT section is invalid. It should only contain numeric character and '-'. The correct format is "minimum_version* - maximum_version". The minimum_version and maximum_version is a numberic string and should only contain numeric character: '0123456789'. The value of the minimum_version should be less than or equal to the value of the maximum_version. The value of minimum_version and maximum_version should be in the range: 0-65535. (e.g., the range may be "0-65535").
	Action	Specify the VERSION_RANGE string according to the correct format in *DM_IMPORT section.
	See Also	`dmconfig`(5)
3877	ERROR: The `REQUEST_VERSION` value configured_request_version is invalid, should be in the range min_value-max_value
	Description	The request version number specified by `REQUEST_VERSION` in DM_IMPORT section is not in valid range. The valid range is: 0-65535. Otherwise, it should be equal to ''.
	Action	Specify a valid request version number or .. for `REQUEST_VERSION` in DM_IMPORT section.
	See Also	`dmconfig`(5)
3878	*ERROR: The `VERSION_POLICY` value configured_version_policy_string* is invalid, current only support "PROPAGATE"**
	Description	The `VERSION_POLICY` string in *DM_IMPORT section is invalid. It should be equal to "PROPAGATE".
	Action	Specify the value of `VERSION_POLICY` as "PROPAGATE".
	See Also	`dmconfig`(5)