Two other optional attributes are supported in UBBCONFIG *MACHINES section.

SPINTUNING_FACTOR

The option SPINTUNING_FACTOR controls the tuning target. The default value is 100 which is good enough in most scenarios. It can be changed from 1 to 10000 if necessary. A value of 100 indicates that SPINCOUNT will stop tuning as long as less than 1 in 100 attempts to lock result in system level method to get the BB lock and there is sufficient idle CPU. If the number of lock attempts resulting in system level method is higher than 1 and there is sufficient idle CPU time, SPINCOUNT will be increased.

SPINTUNING_MINIDLECPU: Specifies the CPU idle time.

The negative impact of the user level method is the extra cost of the CPU. Too many reties of user level method will cost many CPU time. This option is used to limit the CPU used by the user level method. The Self-Tuning Lock Mechanism will not increase the SPINCOUNT when the limitation of SPINTUNING_MINIDLECPU is reached even if the tuning target is not met. On the contrary, the SPINCOUNT will be decreased when the limitation of SPINTUNING_MINIDLECPU is broken no matter the tuning target is met or not. For example, given the value of 20, the Self-Tuning Lock Mechanism will control the idle CPU time not less than %20 during the adjustment. The default value is 20.

Note:

• If not specified, the default values for these attributes are used.
• The Self-Tuning Lock Mechanism may adjust the SPINCOUNT at each scan unit but may need to adjust by several times to achieve the target.

For more information, see UBBCONFIG(5) and UBBCONFIG(5) Additional Information, Example 2 Self-Tuning Lock Mechanism Configuration, in File Formats, Data Descriptions, MIBs, and System Processes Reference.

You can also set the configuration via TM_MIB. For more information, see TM_MIB(5) in File Formats, Data Descriptions, MIBs, and System Processes Reference.

The following listing shows a UBBCONFIG file example of enabling Self-Tuning Lock Mechanism.

Listing UBBCONFIG File Example of Enabling Self-Tuning Lock Mechanism

*RESOURCES
 
OPTIONS       XPP
...

You can disable this feature by specifying the option NO_SPINTUNING in the UBBCONFIG file.

The following listing shows a UBBCONFIG file example of disabling Self-Tuning Lock Mechanism.

Listing UBBCONFIG File Example of Disabling Self-Tuning Lock Mechanism

*RESOURCES
OPTIONS        XPP,NO_SPINTUNING
...

Another optional attribute is provided in *RESOURCES section.

SHMQMAXMEM numeric_value

Specifies the maximum shared memory size (Megabyte) used for message buffers.

For UNIX platforms and Windows platforms, the numeric_value range is from 1 to 2000 inclusive. For all other platforms, the numeric_value range is from 1 to 96000 inclusive. If SHMQMAXMEM is not specified, a recommended minimum value will be used, which is good enough for almost all of the scenarios.

Run tmloadcf -c to get recommended minimum value. For more information, refer to tmloadcf(1) in Section 1 - Oracle Tuxedo Command Reference.

The following listing shows a UBBCONFIG file example of enabling Shared Memory Interprocess Communication.

Listing UBBCONFIG File Example of Enabling Shared Memory Interprocess Communication

*RESOURCES
OPTIONS       XPP
...

You can disable this feature by specifying the option NO_SHMQ in the UBBCONFIG file.

The following listing shows a UBBCONFIG file example of disabling Shared Memory Interprocess Communication.

Listing UBBCONFIG File Example of Disabling Shared Memory Interprocess Communication

*RESOURCES
OPTIONS       XPP,NO_SHMQ
...

The Oracle Tuxedo Advanced Performance Pack includes this feature by default and cannot be disabled.

The Oracle Tuxedo Advanced Performance Pack includes this feature by default and cannot be disabled.

Listing Configuration Example of Enabling Concurrent Global Transaction Table Lock by Default

*RESOURCES
OPTIONS       XPP

The following listing shows a UBBCONFIG file example of enabling Partial One Phase Read-Only Optimization for RAC.

Listing UBBCONFIG File Example of Enabling Partial One Phase Read-Only Optimization for RAC

*RESOURCES
OPTIONS         XPP
...

You can disable this feature by specifying the option NO_RDONLY1PC in the UBBCONFIG file.

The following listing shows a UBBCONFIG file example of disabling Partial One Phase Read-Only Optimization for RAC.

Listing UBBCONFIG File Example of Disabling Partial One Phase Read-Only Optimization for RAC

*RESOURCES
OPTIONS         XPP,NO_RDONLY1PC
...
 

You can also get/change the configuration via TM_MIB. For more information, see TM_MIB(5) in Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference.

The following listing shows a UBBCONFIG file example of enabling SGMB.

Listing Configuration Example of Enabling SGMB by Default

*RESOURCES
OPTIONS         XPP

You can disable this feature by specifying the option SINGLETON of RMOPTIONS in the UBBCONFIG file.

RMOPTIONS {[...|SINGLETON],*}

The following listing shows a UBBCONFIG file example of disabling SGMB.

Listing Configuration Example of Disabling SGMB Explicitly

*RESOURCES
OPTIONS         XPP
RMOPTIONS    SINGLETON

You can also set this flag when Tuxedo application is inactive through T_DOMAIN class in TM_MIB. For more information, see TM_MIB(5) in Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference.

The following listing shows a UBBCONFIG file example of enabling Common XID.

Listing Configuration Example of Enabling Common XID by Default

*RESOURCES
OPTIONS         XPP

You can disable this feature by specifying the option NO_COMMONXID of RMOPTIONS in the UBBCONFIG file.

RMOPTIONS {[...|NO_COMMONXID],*}

The following listing shows a UBBCONFIG file example of disabling Common XID.

Listing Configuration Example of Disabling Common XID Explicitly

*RESOURCES
OPTIONS         XPP
RMOPTIONS       NO_COMMONXID

You can also set this flag when Tuxedo application is inactive through T_DOMAIN class in TM_MIB. For more information, see TM_MIB(5) in Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference.

The following listing shows a UBBCONFIG file example of enabling XA Transaction Affinity.

Listing Configuration Example of Enabling XA Transaction Affinity by Default

*RESOURCES
OPTIONS         XPP

You can disable this feature by specifying the option NO_XAAFFINITY of RMOPTIONS in the UBBCONFIG file.

RMOPTIONS {[...|NO_XAAFFINITY],*}

The following listing shows a UBBCONFIG file example of disabling XA Transaction Affinity.

Listing Configuration Example of Disabling XA Transaction Affinity Explicitly

*RESOURCES
OPTIONS         XPP
RMOPTIONS     NO_XAAFFINITY

You can also set this flag when Tuxedo application is inactive through T_DOMAIN class in TM_MIB. For more information, see TM_MIB(5) in Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference.

This feature is implemented using FAN technology. See FAN Integration to enable this technology.

This feature is implemented using FAN technology. See FAN Integration to enable this technology.

The following listing shows a UBBCONFIG file example of enabling FAN Integration.

Listing Configuration Example of Enabling FAN by Default

*RESOURCES
OPTIONS     XPP

You can disable this feature by specifying the option NO_FAN of RMOPTIONS in the UBBCONFIG file.

RMOPTIONS {[...|NO_FAN],*}

The following listing shows a UBBCONFIG file example of disabling FAN Integration.

Listing Configuration Example of Disabling FAN Explicitly

*RESOURCES
OPTIONS                XPP
RMOPTIONS       NO_FAN

You can also set this flag when Tuxedo application is inactive through T_DOMAIN class in TM_MIB. For more information, see TM_MIB(5) in Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference.

TMFAN must be configured for Tuxedo to support FAN, specify Tuxedo system server TMFAN in SERVERS section. For more information, see TMFAN(5) in Section 5 - File Formats, Data Descriptions, MIBs, and System Processes Reference.

To support Oracle TAF (Transparent Application Failover) for Tuxedo XA server, threads=t must be included in OPENINFO in UBBCONFIG *GROUPS section.