The deadlock priority value for commands is normally lower than the deadlock priority value for a UAP. Therefore, if deadlock occurs, it is the command that terminates in an error. To prevent commands from terminating in an error, you can set the deadlock priority value for commands to be higher than the deadlock priority value for a UAP. When you increase the command deadlock priority value, the error occurs in the transaction when deadlock occurs.
You can change the deadlock priority value for the following commands:
Table 9-3 lists the deadlock priority values.
Table 9-3 Deadlock priority values
Type and condition | Deadlock priority value | |||
---|---|---|---|---|
UAP | Value of PDDLKPRIO in client environment definition | 96 | 96 | |
64 | 64 | |||
32 | 32 | |||
Omitted | When X/Open XA interface is used | 96 | ||
When X/Open XA interface is not used and a distributed server is used for the distributed databases | 64 | |||
Utility | 64 | |||
Command | pdhold -b, pdhold -s, pddbchg, pdorbegin, pdorend | Value of pd_command_deadlock_priority* | ||
Other commands | 64 |