
HP NonStop Shadowbase Command Definitions
Consumer Command Descriptions
HP NonStop Shadowbase Command Reference Manual—785421-002
158
be set on the client side Consumer, when they are enabled on the
server side Consumer.
RESOLVELOCKSQ {ON}
{OFF}
Initial Changed
Version Version Values Default Minimum Maximum Alter
3.950 OFF OFF ON No
Client Server Extended Open Target
RESOLVELOCKSQ can be enabled to allow HP Shadowbase to resolve
locking anomalies that might result when, for example, a Consumer lock
collides with an application lock in an active-active scenario; or when a
unique Enscribe alternate keys or unique SQL indices are involved. When
necessary, the RESOLVELOCKSQ algorithm will attempt to store up to
RESOLVELOCKSQMAX events in memory. It uses a flat memory
segment to queue these events. The size of the memory segment is
defined by the RESOLVELOCKSQMEM parameter. After the Consumer
queues RESOLVELOCKSQMAX events or runs out of memory space in
the flat segment, it will then engage an overflow disk queue file to store
the remaining events.
Notes:
If the overflow queue is used, it will be automatically cleared after
RESOLVELOCKSQ processing is complete.
The size one needs for the overflow disk queue is contingent upon the
size of transactions that are involved within a given locking scenario.
Some experimentation might be needed to determine an effective
configuration for your environment.
If this parameter is set to ON the OVFLQFILE parameter must also be
set.
If you are replicating from NonStop to NonStop over TCP/IP,
RESOLVELOCKSQ must be set on both the client and server
Consumer sides (so they match). HP Shadowbase checks this
because it is important for the Collector to know that this is enabled for
this thread.
RESOLVELOCKSQ can be enabled by setting this CONS object
parameter to ON. The default is OFF.
RESOLVELOCKSQMAX
Initial Changed
Version Version Values Default Minimum Maximum Alter
3.950 1000000 0 2147483647 No
Client Server Extended Open Target
Commentaires sur ces manuels