System Messages: CMDTUX Catalog 7200-7299


7201	*ERROR: Non encrypted part of TLOGDEVICE attribute must be <= val* characters in length**
	Description	The non-encrypted part of the `TLOGDEVICE` 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	`tmloadcf`(1), `ubbconfig`(5)
7203	ERROR: Encryption error for TLOGDEVICE password in machine val
	Description	`tmloadcf` encountered an internal error while encrypting password provided in `TLOGDEVICE`
	Action	Please contact Oracle Customer Support.

7204	ERROR: Re-encryption error for TLOGDEVICE password in machine val
	Description	`TLOGDEVICE` was found encrypted in the `UBBCONFIG` file during `tmloadcf`, but an attempt to decrypt it with an old key failed.
	Action	Replace the encrypted part of `TLOGDEVICE` with the "*****" string, and run `tmloadcf` again

7205	ERROR: EXALOGIC option can only be enabled on an Exalogic machine
	Description	The `EXALOGIC` in the `OPTIONS` can only be set on an Exalogic machine.
	Action	Please contact Oracle Customer Support.

7206	ERROR: Invalid key mkey
	Description	Shared memory key of `tux_msgq_monitor` specified by `-K` option is invalid.
	Action	Specify a positive key.

7207	ERROR: Invalid hostname or ipaddress
	Description	Host name or IP address of `tux_msgq_monitor` specified by `-i` option is invalid.
	Action	Specify a valid host name or IP address in 'X.X.X.X' format that mapped to InfiniBand.

7208	ERROR: Invalid memory size msize
	Description	Shared memory size of `tux_msgq_monitor` specified by `-M` option is invalid.
	Action	Specify a positive size.

7209	ERROR: Invalid port dport
	Description	Listening port of `tux_msgq_monitor` specified by `-d` option is invalid.
	Action	Specify a positive port less than 65535.

7210	ERROR: Parameter -K key is required
	Description	Required parameter `-K` of `tux_msgq_monitor` is not specified.
	Action	Specify `-K` key.

7211	ERROR: Parameter -M memory_size is required
	Description	Required parameter `-M` of `tux_msgq_monitor` is not specified.
	Action	Specify `-M` memory_size.

7212	ERROR: Parameter -d port is required
	Description	Required parameter `-d` of `tux_msgq_monitor` is not specified.
	Action	Specify `-d` port.

7213	ERROR: Parameter -i hostname\|ipaddress is required
	Description	Required parameter `-i` of `tux_msgq_monitor` is not specified.
	Action	Specify `-i` hostname\|ipaddress.

7219	*WARN: Msgq_daemon(pid dpid) died*
	Description	`tux_msgq_monitor` has detected that the monitored Msgq_daemon with pid dpid is dead.
	Action	No action required.

7220	*WARN: restart Msgq_daemon(pid dpid)*
	Description	`tux_msgq_monitor` has restarted new Msgq_daemon with pid dpid.
	Action	No action required.

7221	WARN: Failed to spawn Msgq_daemon
	Description	`tux_msgq_monitor` failed to spawn new Msgq_daemon.
	Action	If this message keeps showing, restart the `tux_msgq_monitor`. Otherwise no action is required.

7222	ERROR: Memory size exceeded limit rlimit
	Description	Shared memory size of `tux_msgq_monitor` specified by `-M` option exceeded the system limit rlimit.
	Action	Specify memory size less than current limit rlimit, or increase soft limit of max locked-in-memory address space.

7223	ERROR: Failed to get resource limit
	Description	`tux_msgq_monitor` failed to get system resource limit.
	Action	Restart the `tux_msgq_monitor`

7224	*WARN: Msgq_daemon(pid dpid) works abnormally, restart it*
	Description	`tux_msgq_monitor` has detected that the new started Msgq_daemon with pid dpid works abnormally and needs to be restarted.
	Action	No action required.

7225	ERROR: shm key is in use
	Description	Shared memory key of `tux_msgq_monitor` specified by `-K` option is being used by another process.
	Action	Specify another key.

7226	ERROR: Unable to get APPDIR environment variable.
	Description	Environment variable `APPDIR` is not set.
	Action	Set environment variable `APPDIR`.

7232	*ERROR: SSL Handshake failed with error error_number* [error_string]**
	Description	The tlisten process experienced an error during the SSL handshake process and was unable to establish a connection with its peer. 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.

7233	*ERROR: SSL Handshake failed with error error_number* [error_string]**
	Description	The SSL connection between tlisten and another process was gracefully closed by the other process while still negotiating the initial encryption parameters.
	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.

7234	ERROR: Connection closed by peer during initial negotiation
	Description	The SSL connection between tlisten and another process was gracefully closed by the other process while still negotiating the initial encryption parameters.
	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.

7235	INFO: Connection closed by peer
	Description	The SSL connection between tlisten and another process was gracefully closed by the other process.
	Action	No action required.

7240	ERROR: The output file name cannot be greater than MAXTLSTRING characters.
	Description	The length of the output file name is greater than MAXTLSTRING.
	Action	Specify a shorter output file name.
	See Also	`tmloadrepos`(1)
7241	ERROR: total service name cannot be greater than %d characters.
	Description	If the -C option is specified, all exported service names are put into buffer, and use character ',' as the separator. The length of buffer cannot exceed 2*MAXTLSTRING.
	Action	Specify fewer services to export from the repository.
	See Also	`tmloadrepos`(1)
7242	ERROR: The number of elements to be allocated (that is, the maximum number of occurrences to be stored for this member), must be less than or equal to 65535.
	Description	The maximum number of occurrences for a field of the VIEW structure which is defined in the metadata repository file must be less than or equal to 65535.
	Action	Specify smaller number of occurrences for a field of the VIEW structure defined in metadata repository file.
	See Also	`tmloadrepos`(1)
7243	WARNING: No View definition in Service(%s).
	Description	If the ��-V�� option is specified, the exported service did not define the FML/FML32 field tables or VIEW/VIEW32 descriptor in the metadata repository file, tmunloadrepos will not generate Oracle Tuxedo view files for this service.
	Action	Specify another service.
	See Also	`tmloadrepos`(1)
7250	ERROR: EXALOGIC_SHARED_PATH must be an absolute pathname.
	Description	The value for `EXALOGIC_SHARED_PATH` parameter must be an absolute pathname.
	Action	Correct the value for `EXALOGIC_SHARED_PATH` parameter to be an absolute pathname.
	See Also	`ubbconfig`(5)
7251	ERROR: EXALOGIC_SHARED_PATH can only be configured when the RDMA option is set.
	Description	The value for `EXALOGIC_SHARED_PATH` parameter can be set only when `RDMA` is specified in the `OPTIONS` parameter in the *RESOURCES section of the `UBBCONFIG` file.
	Action	If the `RDMA` option is set in the *RESOURCES section, then the `EXALOGIC_SHARED_PATH` parameter can be set. If that option is not set, the `EXALOGIC_SHARED_PATH` parameter must be removed.
	See Also	`ubbconfig`(5)
7252	ERROR: EXALOGIC_MSGQ_CACHE_SIZE can only be configured when the RDMA option is set.
	Description	The value for `EXALOGIC_MSGQ_CACHE_SIZE` parameter can be set only when `RDMA` is specified in the `OPTIONS` parameter in the *RESOURCES section of the `UBBCONFIG` file.
	Action	If the `RDMA` option is set in the `*RESOURCES` section, then the `EXALOGIC_MSGQ_CACHE_SIZE` parameter can be set. If that option is not set, the `EXALOGIC_MSGQ_CACHE_SIZE` parameter must be removed.
	See Also	`ubbconfig`(5)
7253	ERROR: EXALOGIC_MSGQ_CACHE_SIZE must be >= 32 and <= 2048.
	Description	The value for `EXALOGIC_MSGQ_CACHE_SIZE` parameter must be between 32 and 2048.
	Action	Correct `EXALOGIC_MSGQ_CACHE_SIZE` parameter with the proper value.
	See Also	`ubbconfig`(5)
7257	ERROR: Unexpected character in version range string. Check the version range string: configured_version_range_string
	Description	The `VERSION_RANGE` string in RESOURCE or GROUP 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 RESOURCE or GROUP section.
	See Also	`ubbconfig`(5)
7258	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 RESOURCE or GROUP section contain invalid numeric_string, the numeric_string should only contains the numeric characters: '0123456789'
	Action	Specify the `VERSION_RANGE` string according to the correct format in RESOURCE or GROUP section.
	See Also	`ubbconfig`(5)
7259	ERROR: the minimum version number invalid_min_value: is not valid, it should be min_value - max_value. Check the version range string: configured_version_range_string
	Description	The minimum version number specified in `VERSION_RANGE` string in RESOURCE or GROUP is out of range. The valid number should be is the range: 0-65535.
	Action	Specify a valid minimum version number in `VERSION_RANGE` string.
	See Also	`ubbconfig`(5)
7260	ERROR: the maximum version number invalid_max_value: is not valid, it should be min_value - max_value. Check the version string: configured_version_range_string
	Description	The maximum version number specified in `VERSION_RANGE` string in RESOURCE or GROUP 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	`ubbconfig`(5)
7261	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 RESOURCE or GROUP section.
	Action	Make sure the minimum version number is less than or equal to the maximum version number in `VERSION_STRING` string.
	See Also	`ubbconfig(5)`
7262	ERROR: `REQUEST_VERSION` number configured_request_version must be min_value =<= max_value or == *
	Description	The request version number specified by `REQUEST_VERSION` in RESOURCE or GROUP 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 RESOURCE or *GROUP section.
	See Also	`ubbconfig`(5)
7263	*ERROR: `VERSION_RANGE`: configured_version_range_string* is not valid**
	Description	The `VERSION_RANGE` string in RESOURCE or GROUP 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 numeric 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. Fox example, the range string may be "0-65535"
	Action	Specify the `VERSION_RANGE` string according to the correct format in RESOURCE or GROUP section.
	See Also	`ubbconfig`(5)
7264	*ERROR: `VERSION_POLICY`: configured_version_policy_string* is not valid**
	Description	The `VERSION_POLICY` string in RESOURCE or GROUP section is invalid, which should be equal to "PROPAGATE".
	Action	Specify the value of `VERSION_POLICY` as "PROPAGATE"
	See Also	`ubbconfig`(5)