Options for Reducing Contention Between Autorefresh and Dynamic Load Operations

There are two methods to reduce contention between autorefresh and dynamic load operations.

You can enable each or both if:

• If you see error messages indicating lock contention between autorefresh and dynamic load operations, then enable the DynamicLoadReduceContention database system parameter by setting the value to 1 with the ttDbConfig built-in procedure. See Reducing Contention for Dynamic Read-Only Cache Groups with Incremental Autorefresh.

• If you notice that commit operations for autorefresh are taking an unusually long time, then look for a TT47087 informational message in the support log. Locate the tt1stXactCommitTime and tt2ndXactCommitTime entries within this message. If the time indicated for either of both of these entries unusually high or is a major portion of the time indicated in the Duration entry, this may indicate that the durable commit of transaction logs is slow. In this case, you have the option to set the CacheCommitDurable cache configuration parameter to 0 with the ttCacheConfig built-in procedure. For more details on the CacheCommitDurable cache configuration parameter, see Reducing Lock Contention for Read-Only Cache Groups with Autorefresh and Dynamic Load.

Enable both options if there is a small autorefresh interval in conjunction with a high number of dynamic load requests.