System Messages: LIBTMIB Catalog 600-699

The read-only one-phase commit optimization feature is only supported by specific platforms. The Self-Tuning Lock Mechanism feature is only supported by specific platforms.


600	ERROR: Obtain No.sequence parameter error: Ferror
	Description	An attempt to read No.sequence parameter from an FML32 buffer or an embedded FML32 buffer failed. See Ferror for more reference.
	Action	Check the `METAREPOS`(5) FML32 buffer request and resend the request buffer.
	See Also	`METAREPOS`(5)
601	*ERROR: Adding No.sequence parameter param-name* error for SET operation**
	Description	An attempt to add No.sequence parameter to service definition failed. The parameter param-name might have an invalid parameter name.
	Action	Check the No.sequence occurrence of field `TA_REPOSPARAM` has a valid parameter name value and resend the request.
	See Also	`METAREPOS`(5)
602	*ERROR: Adding No.sequence parameter param-name* - field fieldname error for SET operation**
	Description	An attempt to add parameter-level attribute fieldname of No.sequence parameter information to service definition failed. The attribute might have an invalid value.
	Action	Make sure all param-name parameter-level attributes have valid values and resend the request.
	See Also	`METAREPOS`(5)
603	*ERROR: Adding field field-name* error for SET operation**
	Description	An attempt to add service-level attribute fieldname to service definition failed. The attribute might have an invalid value.
	Action	Make sure the fieldname service-level attribute has a valid value and resend the request.
	See Also	`METAREPOS`(5)
604	ERROR: Fielded buffer is not in single mode
	Description	`METAREPOS` request buffer is not a single mode buffer. Single mode is the only valid mode for `METAREPOS` GET operation.
	Action	Change the request buffer to a valid single mode buffer. More than one service retrieval regular expression can be specified in one TA_REPOSSERVICE field with separator ','.
	See Also	`METAREPOS`(5)
605	ERROR: Memory allocation error for reading service servicename
	Description	An attempt to dynamically allocate memory from the operating system using `calloc` failed while reading service servicename. The system may not have enough memory.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

606	*ERROR: Service servicename* information may be corrupt**
	Description	Failed to parse service servicename information stored in metadata repository. The repository file service servicename may be corrupt.
	Action	Try to re-define service servicename in the repository using `tmloadrepos`.
	See Also	`tmloadrepos`(1)
607	*ERROR: Service servicename* information is illegal**
	Description	The service servicename information has illegal attribute values. The repository file might have been modified without using `tmloadrepos`.
	Action	Try to re-define service servicename in the repository using `tmloadrepos`.
	See Also	`tmloadrepos`(1)
608	*ERROR: Saving service servicename,tpallocation error(tperrno)*
	Description	An attempt to allocate FML buffer for saving service information failed. System may not have enough memory.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

609	*ERROR: Fielded buffer access error (Ferror) when processing repository request*
	Description	An attempt to add service information as FML32 fields into a fielded buffer failed. indicates the FML32 buffer error code.
	Action	Reference the Ferror error description for failure explanation.

610	ERROR: Allocate necessary buffer space error when processing repository request
	Description	An attempt to allocate additional memory failed when handling `METAREPOS` request. System may not have enough memory.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

611	*ERROR: Fielded service appending error (Ferror) when processing repository request*
	Description	An attempt to append an embedded service information FML32 buffer to the top-level FML32 buffer failed.
	Action	Reference the Ferror error description for failure explanation. Ferror indicates the FML32 buffer error code.

612	*ERROR: Service servicename* delete error**
	Description	An attempt to delete service servicename information from the repository failed.
	Action	Make sure the repository file exists and has the proper file permission set for updating.

613	ERROR: Service servicename info not validate:detailmsg
	Description	Service definition is checked as an invalid definition when processing repository SET operation. See detailmsg for more information.
	Action	`tmloadrepos`(1)

614	*ERROR: Adding service servicename* error**
	Description	An attempt to write serialized service information into the repository file failed when processing repository SET operation. May be caused by a system file IO error.
	Action	Make sure the repository file exists and has the proper file permissions set for updating.

616	*ERROR: Updating service servicename* error**
	Description	An attempt to write serialized service information into the repository file failed when processing repository SET operation. May be caused by a system file IO error.
	Action	Make sure the repository file exists and has the proper file permissions set for updating.

617	ERROR: Key field is required for SET operation
	Description	Required key field is missing in the repository SET request buffer.
	Action	See manual page `METAREPOS`(5) for required key field of repository request.

618	ERROR: Error getting service from repository file
	Description	An attempt to read service information from the repository file failed. May be caused by a system file IO error.
	Action	Make sure the repository file exists and has the proper file permissions set for updating.

621	ERROR: Service already exists
	Description	Specified service already exists in the repository file when handling a service creating operation.
	Action	Delete old service definition, then re-create it. Or send an updating request instead of a creating request.
	See Also	`METAREPOS`(5)
622	ERROR: Service does not exist
	Description	Specified service does not exist in the repository file when handling a service deleting or updating request.
	Action	None

623	ERROR: Failed to malloc METAREPOS context memory
	Description	An attempt to dynamically allocate memory using `malloc()` failed while initializing METAREPOS context information. The system may not have enough memory.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

630	*ERROR: Repository file filename* does not exist**
	Description	`tpgetrepos`(3c) / `tpsetrepos`(3c) detected the repository file provided by the input parameter does not exist.
	Action	Make sure the correct repository file path is provided in `tpgetrepos`(3c) or `tpsetrepos`(3c) function.
	See Also	`tpgetrepos`(3c), `tpsetrepos`(3c)
631	*ERROR: Repository file filename* has invalid format**
	Description	`tpgetrepos`(3c) / `tpsetrepos`(3c) detected the given repository file has invalid format.
	Action	Make sure the correct repository file path is provided in `tpgetrepos`(3c) or `tpsetrepos`(3c) function.

632	*ERROR: Repository file filename* is a Jolt repository file**
	Description	`tpsetrepos`(3c) detected the given repository file is a Jolt repository file.
	Action	Make sure a metadata repository file path is provided in `tpsetrepos`(3c) function.

633	ERROR: System error when opening repository file filename
	Description	An unknown system error was encountered when opening the repository file in `tpgetrepos`(3c) or `tpsetrepos`(3c) function.
	Action	Contact Oracle Customer Support.

634	ERROR: Error synchronizing repository file
	Description	An attempt to synchronizing the latest information from repository file failed in a `METAREPOS` SET request. The error might be a system disk IO error, a dynamically allocated memory error, or a corrupt repository file.
	Action	Make sure the operating system parameters are set correctly for the file IO by a process and the working directory hierarchy has the right permissions to the existing file. Make sure the operating system parameters are set correctly for the correct amount of memory. Make sure the repository file is not corrupt.

635	ERROR: MIB_SELF not allowed for non-client/server process
	Description	The `MIB_SELF` `TA_FLAGS` value was set when invoking `tpgetrepos`(3c) or `tpsetrepos`(3c) from an unattached process.
	Action	Remove the `MIB_SELF` flag value setting or defer the request until the process is attached as a client or server.
	See Also	`MIB`(5), `METAREPOS`(5)
636	ERROR: Fielded buffer is neither single mode nor standard mode
	Description	`METAREPOS` request buffer is neither a single mode buffer nor a standard mode buffer. Single mode and standard mode are the valid modes for `METAREPOS` SET operation. If you want to set more than one service definition, use standard mode.
	Action	Follow the description in the `METAREPOS`(5) manpage to produce a valid FML32 buffer request.

637	ERROR: Get No.sequence embedded service data error: Ferror
	Description	An attempt to get No.sequence embedded service information failed. `Ferror` indicates the error number.
	Action	Reference the Ferror error description for failure explanation.

638	*ERROR: Setting service,tpallocation error(tperrno)*
	Description	An attempt to allocate FML buffer for saving service information failed when handling a SET request. System may not have enough memory.
	Action	Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory and/or swap space on the machine.

639	*ERROR: Service name (servicename) is invalid*
	Description	Invalid service name value is specified in a `METAREPOS`(5) SET operation.
	Action	Check and change the service name with a valid string value.

640	ERROR: Error setting file for read-locking
	Description	An attempt to set read-locking to the repository file failed in a `METAREPOS`(5) GET request because another program is using the same repository file.
	Action	Wait a while and try to resend the GET request. If the problem persists, check and stop all abnormal utilities that are accessing the repository file and then resend the GET request.

641	ERROR: Error setting file for write-locking
	Description	An attempt to set write-locking to the repository file failed in a `METAREPOS`(5) SET request because another program is using the same repository file.
	Action	Wait a while and then try to resend the SET request. If the problem persists, check and stop all abnormal utilities that are accessing the repository file and then resend the SET request.

642	ERROR: Repository file is locked by another program
	Description	An attempt to set read-lock to the specified repository file failed in a `tpgetrepos`(3c) or `tpsetrepos`(3c) function. Another `tmloadrepos` program is using the same repository file.
	Action	Stop all abnormal utilities that are accessing the repository file and then try to invoke `tpgetrepos`(3c) or `tpsetrepos` again.

643	ERROR: Cannot read predefined FML field
	Description	An attempt to read predefined FML fields failed when opening repository file. The predefined FML fields used by metadata repository are located in file `$TUXDIR/udataobj/tpadm`.
	Action	Make sure environment variable `TUXDIR` is set correctly and $TUXDIR/udataobj/tpadm can be accessed.
	See Also	`METAREPOS`(5)
644	ERROR: TA_PASSWORD not correctly preprocessed
	Description	Unable to retrieve the oneway encrypted password from MIB attribute TA_PASSWORD.
	Action	Contact Oracle Systems Customer Support.

645	ERROR: TA__ENCPASSWD not correctly preprocessed
	Description	Unable to retrieve the two-way encrypted password from MIB attribute TA__ENCPASSWD.
	Action	Contact Oracle Systems Customer Support.

646	*ERROR: Cannot set T_SERVER because CLOPT length is greater than length* and there is previous release release on site (site_name)**
	Description	For pre-Tuxedo 10gR3 releases, the CLOPT is limited to 256. When Tuxedo is running in a mixed releases MP mode environment on any slave node that runs a release earlier than Tuxedo 10gR3, then CLOPT is limited to 256 for the entire Tuxedo Application domain.
	Action	Either upgrade the older release node to Tuxedo 10gR3 and above, or change the CLOPT to value smaller than or equal to 256.

647	*ERROR: Cannot set T_ROUTING because FIELD length is greater than length* and there is previous release release on site (site_name)**
	Description	For pre-Tuxedo 10gR3 releases, the FIELD of ROUTING section is limited to 30. When Tuxedo is running in a mixed releases MP mode environment on any slave node that runs a release earlier than Tuxedo 10gR3, then FIELD of ROUTING section is limited to 30 for the entire Tuxedo Application domain.
	Action	Either upgrade the older release node to Tuxedo 10gR3 and above, or change the FIELD of ROUTING section to value smaller than or equal to 30.

648	*ERROR: Cannot set T_SERVICE. The SERVICENAME length is greater than length* and there is an older Oracle Tuxedo release release on site (site_name)**
	Description	For Oracle Tuxedo release older than 11gR1, the SERVICENAME in the UBBCONFIG SERVICES section is limited to 15. From TUXEDO 11gR1 and above, the service name has increased to 127. When Oracle Tuxedo is running in a mixed-release MP mode environment on slave nodes that run a release earlier than Oracle Tuxedo 11gR1, then the UBBCONFIG SERVICES section SERVICENAME is limited to 15 for the entire Oracle Tuxedo Application domain.
	Action	Either upgrade the older release node to Oracle Tuxedo 11gR1 and above, or change the SERVICENAME of T_SERVICE to value smaller than or equal to 15.
	See Also	`UBBCONFIG`(5)
649	*ERROR: Cannot set T_DOMAIN. AUTHSVC length is greater than length* and there is an older Oracle Tuxedo release release on site (site_name)**
	Description	For Oracle Tuxedo release older than 11gR1, T_DOMAIN AUTHSVC is limited to 15. From TUXEDO 11gR1 and above, the T_DOMAIN AUTHSVC has increased to 127. When Oracle Tuxedo is running in a mixed-releases MP mode environment on slave nodes that run a release earlier than Oracle Tuxedo 11gR1, T_DOMAIN AUTHSVC is limited to 15 for the entire Oracle Tuxedo Application domain.
	Action	Either upgrade the older release node to Oracle Tuxedo 11gR1 and above, or change the AUTHSVC of T_DOMAIN to value smaller than or equal to 15.
	See Also	`UBBCONFIG`(5)
650	*ERROR: Cannot set T_SVCGRP. SERVICENAME length is greater than length* and there is an older Oracle Tuxedo release release on site (site_name)**
	Description	For Oracle Tuxedo release older than 11gR1, the service name is limited to 15. From TUXEDO 11gR1 and above, the service name has increased to 127. When Tuxedo is running in a mixed-release MP mode environment on slave nodes that run a release earlier than Oracle Tuxedo 11gR1, the service name length is limited to 15 for the entire Oracle Tuxedo Application domain.
	Action	Either upgrade the older release node to Oracle Tuxedo 11gR1 and above, or change the SERVICENAME to value smaller than or equal to 15.

651	ERROR: Cannot find group groupname
	Description	While attempting to set `T_RMS` class parameters associated with a server group, the `TA_SRVGRP` field did not match an existing server group.
	Action	Make sure that the group name you specify is an existing server group.
	See Also	`MIB`(5)
652	*ERROR: Cannot set T_RMS for group groupname* without setting MRM=Y"**
	Description	While attempting to set `T_RMS` class parameters associated with a server group, the specific group in `TA_SRVGRP` is not configured as a multiple resource manager type of group.
	Action	Make sure that the `MRM` of this group is not configured as 'N' in UBBCONFIG.
	See Also	`MIB`(5), `UBBCONFIG`(5)
653	ERROR: Cannot set T_RMS for group groupname because it is specified in previous release releasenumber on site site_name
	Description	When Oracle Tuxedo is running in a mixed-release MP mode environment and the slave node doesn��t support the multiple RM in one group feature, the set request for `T_RMS` is prohibited.
	Action	Either upgrade the slave node to Tuxedo release which supports this feature, or remove the MRM attribute in the group.
	See Also	`TM_MIB`(5), `UBBCONFIG`(5)
654	ERROR: Group does not exist in the system
	Description	A `SET` operation creating a `NEW` `T_RMS` class object specified a value for `TA_SRVGRP` attribute that does not exist in TUXEDO configuration file.
	Action	Select a `TA_SRVGRP` from TUXEDO configuration file.
	See Also	`MIB`(5), `TM_MIB`(5)
655	ERROR: Group does not support multi RMS
	Description	A `SET` operation creating a `NEW` `T_RMS` class object specified a value for `TA_SRVGRP` attribute that does not define "MRM=Y" in TUXEDO configuration file.
	Action	Select another `TA_SRVGRP` defined with "MRM=Y" or modify the TA_SRVGRP defined with "MRM=Y"
	See Also	`MIB`(5), `TM_MIB`(5)
656	ERROR: RM id must be between 1 and 31
	Description	A `SET` operation creating a `NEW` `T_RMS` class object specified a value for `TA_RMID` attribute that is not in the scope from 1 to 31.
	Action	Change TA_RMID to be between 1 and 31.
	See Also	`MIB`(5), `TM_MIB`(5)
657	ERROR: RM name must be specified
	Description	A `SET` operation creating a `NEW` `T_RMS` class object did not specify a value for `TA_RMSNAME` attribute.
	Action	Specify `TA_RMSNAME.`
	See Also	`MIB`(5), `TM_MIB`(5)
658	ERROR: TA_RMSNAME is not unique
	Description	A `SET` operation creating a `NEW` `T_RMS` class object specified a value for `TA_RMSNAME` attribute that is not unique within the class.
	Action	Change `TA_RMSNAME to be unique in the class.`
	See Also	`MIB`(5), `TM_MIB`(5)
659	ERROR: TA_RMSNAME does not exist in the system
	Description	A `SET` operation on `T_RMS` class object specified a value for `TA_RMSNAME` attribute that does not exist in the system.
	Action	Correct and select `TA_RMSNAME` from TUXEDO configuration file.
	See Also	`MIB`(5), `TM_MIB`(5)
660	ERROR: Cannot change TA_RMID
	Description	A `SET` operation on `T_RMS` class object specified a value for `TA_RMID` attribute to change the original one, that is forbidden.
	Action	Remove `TA_RMID from the operation setting T_RMS or change TA_RMID to original one.`
	See Also	`MIB`(5), `TM_MIB`(5)
661	*WARN: TA_OPENINFO, TA_CLOSEINFO and TA_TMSCOUNT ignored due to RMS(RMS) with no TMS*
	Description	A `SET` operation on a `T_RMS` class object specified non-0 length values for either or both of `TA_OPENINFO` and `TA_CLOSEINFO` for a `T_RMS` with no associated `TA_TMSNAME` value. The values specified for `TA_OPENINFO` and `TA_CLOSEINFO` are ignored in this case when configuring `T_RMS`.
	Action	If a `T_RMS` is intended to be associated with a resource manager, then the`T_RMS` attributes should be modified to include the appropriate `TA_TMSNAME` value and the values for `TA_OPENINFO` and `TA_CLOSEINFO` may be configured at that time.
	See Also	`MIB`(5), `TM_MIB`(5)
662	ERROR: Machine associated with RMS does not have a TLOG device
	Description	A `SET` operation on a `T_RMS` class object specified a sever group for that primary or secondary logical machine without an associated `TA_TLOGDEVICE` even though the `T_RMS` is being configured with a non-NULL `TA_TMSNAME` value. A non-NULL value is one which is non-0 length and is not "TMS".
	Action	Either associate `TA_TLOGDEVICE` values with the corresponding machines or change the `T_RMS` so that `TA_TMSNAME` is a NULL.
	See Also	`MIB`(5), `TM_MIB`(5)
663	ERROR: TA_RMSNAME does not match S_GRPNAME
	Description	A `SET` operation on `T_RMS` class object specified values for `TA_RMSNAME` and `TA_SRVGRP` attribute, but they are not match.
	Action	Remove `TA_SRVGRP from the operation setting T_RMS.`
	See Also	`MIB`(5), `TM_MIB`(5)
664	ERROR: Total number of RMS entries with AUTO=Y in server group group must <= Limitation
	Description	A `SET` operation on `T_RMS` class object specified the value for `TA_RMAUTO` attribute to "Y", but total number of RMS entries with AUTO=Y in one server group must <= Limitation.
	Action	Change `TA_RMAUTO` attribute to "N" on this `T_RMS` class object or other one from the same server group.
	See Also	`MIB`(5), `TM_MIB`(5)
665	ERROR: To update or create RM, group cannot have active application servers
	Description	A `SET` operation to create or update `T_RMS` class object, but the corresponding group have active application servers.
	Action	Shutdown the active application servers or select a group without active application servers.
	See Also	`MIB`(5), `TM_MIB`(5)
666	ERROR: Total number of TMS in server group group must be <= Limitation
	Description	A `SET` operation on `T_RMS` class object specified a value for `TA_TMSCOUNT` attribute, but total number of TMS in one server group must <= Limitation.
	Action	Limit `TA_TMSCOUNT` within Limitation.
	See Also	`MIB`(5), `TM_MIB`(5)
667	ERROR: Cannot set NO_XA option; global TA_AUTOTRAN is configured
	Description	A `SET` operation on `TA_OPTIONS` to "NO_XA" is not allowed because the global TA_AUTOTRAN has been configured.
	Action	These 2 settings are incompatible.
	See Also	`TM_MIB`(5) and `ubbconfig`(5)
668	ERROR: Cannot set global TA_AUTOTRAN; NO_XA option is configured
	Description	A `SET` operation on `TA_AUTOTRAN` to "Y" is not allowed because the `TA_OPTIONS` to "NO_XA" has been configured.
	Action	These 2 settings are incompatible.
	See Also	`TM_MIB`(5) and `ubbconfig`(5)
669	INFO: .RMSState: RMS RMS state change to state
	Description	This message indicates that the `T_RMS` specified above changed to a new state.
	Action	This is an informational message.
	See Also	`EVENT_MIB`(5), `TM_MIB`(5)
670	*ERROR: Can not access QM library libname.*
	Description	The process failed when access QM library libname. This error indicates an installation problem.
	Action	Check the TUXEDO installation. If the installation is fine but problem persists contact ORACLE Customer Support.

671	ERROR: Cannot unset the option EXALOGIC if the option SPINTUNING is specified [DESCRIPTION] A `SET` operation on `OPTIONS` without "EXALOGIC" is not allowed with a `SPINTUNING` `OPTIONS` set for the application in the tuxconfig.
Action	Unset the "SPINTUNING" option too if EXALOGIC is unset.
See Also	`TM_MIB`(5) and `ubbconfig`(5)
672	ERROR: Cannot unset the option SPINTUNING because LMID lmid has a configured SPINTUNING_FACTOR [DESCRIPTION] A `SET` operation on `OPTIONS` without "SPINTUNING" is not allowed because the LMID lmid has been configured with a `SPINTUNING_FACTOR`.
Action	Set the "SPINTUNING_FACTOR" to zero before to set the `OPTIONS` without "SPINTUNING".
See Also	`TM_MIB`(5)
673	ERROR: Cannot unset the option SPINTUNING because LMID %s has a configured SPINTUNING_MINIDLECPU [DESCRIPTION] A `SET` operation on `OPTIONS` without "SPINTUNING" is not allowed because the LMID lmid has been configured with a `SPINTUNING_MINIDLECPU`.
Action	Set the "SPINTUNING_MINIDLECPU" to zero before to set the `OPTIONS` without "SPINTUNING".
See Also	`TM_MIB`(5)
674	ERROR: Cannot set the option SPINTUNING because LMID %s has a configured SPINCOUNT [DESCRIPTION] A `SET` operation on `OPTIONS` with "SPINTUNING" is not allowed because the LMID lmid has been configured with a `SPINCOUNT`.
Action	Set the "SPINCOUNT" to zero before to set the `OPTIONS` with "SPINTUNING".
See Also	`TM_MIB`(5)
675	ERROR: TA_RDMADAEMONIP can only be set when the RDMA option is set
	Description	A `SET` operation on the `TA_RDMADAEMONIP` attribute can only be done when setting the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA.
	Action	Set the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA before setting the `TA_RDMADAEMONIP` attribute. If the the `TA_OPTIONS` attribute or the `OPTIONS` parameter in `UBBCONFIG` file is set to RDMA then the `TA_RDMADAEMONIP` attribute must be set.
	See Also	`MIB`(5), `TM_MIB`(5)
676	ERROR: TA_RDMADAEMONPORT can only be set when the RDMA option is set
	Description	A `SET` operation on the `TA_RDMADAEMONPORT` attribute can only be done when setting the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA.
	Action	Set the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA before setting the `TA_RDMADAEMONPORT` attribute. If the the `TA_OPTIONS` attribute or the `OPTIONS` parameter in `UBBCONFIG` file is set to RDMA then the `TA_RDMADAEMONPORT` attribute must be set.
	See Also	`MIB`(5), `TM_MIB`(5)
677	ERROR: TA_RDMAQSIZE can only be set when the RDMA option is set
	Description	A `SET` operation on the `TA_RDMAQSIZE` attribute can only be done when setting the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA.
	Action	Set the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA before setting the `TA_RDMAQSIZE` attribute.
	See Also	`MIB`(5), `TM_MIB`(5)
678	ERROR: TA_RDMAQENTRIES can only be set when the RDMA option is set
	Description	A `SET` operation on the `TA_RDMAQENTRIES` attribute can only be done when setting the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA.
	Action	Set the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA before setting the `TA_RDMAQENTRIES` attribute.
	See Also	`MIB`(5), `TM_MIB`(5)
679	*ERROR: Cannot unset RDMA option because LMID lmid* has RDMA specified parameters**
	Description	The value of `RDMA` for `TA_OPTIONS` cannot be unset when the RDMA specified parameters are defined in `MACHINES` section.
	Action	Remove all RDMA specified parameters in `MACHINES` section before unset the value of `RDMA` for `TA_OPTIONS`.
	See Also	`MIB`(5), `TM_MIB`(5), `ubbconfig`(5)
690	ERROR: Cannot unset RDMA option. EXALOGIC_SHARED_PATH is not empty.
	Description	The value of `RDMA` for `TA_OPTIONS` cannot be unset when `EXALOGIC_SHARED_PATH` are defined in `*RESOURCE` section.
	Action	Remove `EXALOGIC_SHARED_PATH` parameter in `*RESOURCE` section before unset the value of `RDMA` for `TA_OPTIONS`.
	See Also	`MIB`(5), `TM_MIB`(5), `ubbconfig`(5)
691	ERROR: TA_EXALOGIC_MSGQ_CACHE_SIZE can only be set when the RDMA option is set.
	Description	A `SET` operation on the `TA_EXALOGIC_MSGQ_CACHE_SIZE` attribute can only be done when setting the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA.
	Action	Set the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in `UBBCONFIG` file to RDMA before setting the `TA_EXALOGIC_MSGQ_CACHE_SIZE` attribute.
	See Also	`MIB`(5), `TM_MIB`(5), `ubbconfig`(5)
692	ERROR: Cannot unset the EXALOGIC option if the SHMQ option is specified.
	Description	The value of `EXALOGIC` for `TA_OPTIONS` cannot be unset when the `SHMQ` is specified in `TA_OPTIONS`.
	Action	Remove both `SHMQ` and `EXALOGIC` in `TA_OPTIONS`.
	See Also	`MIB`(5), `TM_MIB`(5), `ubbconfig`(5)
693	ERROR: Cannot unset SHMQ option. SHMQMAXMEM is not empty
	Description	The value of `SHMQ` for `TA_OPTIONS` cannot be unset when the `SHMQMAXMEM` is specified in `*RESOURCE` section.
	Action	Remove `SHMQMAXMEM` parameter in `*RESOURCE` section before unset the value of `SHMQ` for `TA_OPTIONS`.
	See Also	`MIB`(5), `TM_MIB`(5), `ubbconfig`(5)
694	ERROR: Cannot set the RDONLY1PC option if the NO_XA option is also specified
	Description	"NO_XA" is not allowed with a `RDONLY1PC` `OPTIONS` set for the application in the tuxconfig.
	Action	Remove the `NO_XA` option when set to `RDONLY1PC` option.
	See Also	`TM_MIB`(5) and `ubbconfig`(5)
695	ERROR: The RDONLY1PC option is not supported on this platform [DESCRIPTION],
Action	Use the platform that supports this feature.
See Also	`ubbconfig`(5)
696	ERROR: The SPINTUNING option is not supported on this platform [DESCRIPTION].
Action	Use the platform that supports this feature.
See Also	`ubbconfig`(5)
697	ERROR: Cannot set the RDONLY1PC option if the EXALOGIC option is not specified
	Description	"EXALOGIC" is not allowed with `RDONLY1PC` `OPTIONS` set for the application in the tuxconfig file.
	Action	Set the `EXALOGIC` option.
	See Also	`TM_MIB`(5) and `ubbconfig`(5)
698	ERROR: TA_SHMQMAXMEM can only be set when the SHMQ option is set.
	Description	A `SET` operation on the `TA_SHMQMAXMEM` attribute can only be done when setting the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in the `UBBCONFIG` file to SHMQ.
	Action	Set the `TA_OPTIONS` attribute value or the `OPTIONS` parameter in the `UBBCONFIG` file to SHMQ before setting the `TA_SHMQMAXMEM` attribute.
	See Also	`MIB`(5), `TM_MIB`(5), `ubbconfig`(5)
699	ERROR: Cannot set TA_SCANUNIT and TA_SCANUNIT_MSEC together
	Description	Can not specify `TA_SCANUNIT` and `TA_SCANUNIT_MSEC` together for MIB `T_DOMAIN` `SET` operation
	Action	Please remove `TA_SCANUNIT` or `TA_SCANUNIT_MSEC` from the MIB `T_DOMAIN` `SET` operation
	See Also	`MIB`(5), `TM_MIB`(5)