When definition SQL statements, utilities, and operation commands are used to process a shared table or shared index, HiRDB may internally issue the LOCK statement with IN EXCLUSIVE MODE specified and lock the target table and RDAREAs at all back-end servers. If any application accesses a table or index in a corresponding RDAREA, deadlock or server-to-server global deadlock may occur.

HiRDB internally issues the LOCK statement for the following definition SQL statements:

• CREATE TABLE, DROP TABLE, and PURGE TABLE for a shared table
• CREATE INDEX and DROP INDEX for a shared index
• DROP SCHEMA for a schema containing a shared table
• Change to the free space reusage facility for a shared table (ALTER TABLE)
• Add or remove the primary key for a shared table (ALTER TABLE)

HiRDB internally issues the LOCK statement for the following utilities:

• Database load utility (pdload)
• Database reorganization utility (pdrorg -k reld, rorg, ixrc, ixmk, ixor)
• Free page release utility (pdreclaim)
• Database definition utility (pddef)
• Data dictionary import/export utility (pdexp)
• Database structure modification utility (pdmod -a initialize rdarea)

HiRDB internally issues the LOCK statement for the following operation command:

• pdorend

For details about the utilities and operation commands that cannot be executed on shared RDAREAs, see 14.6(8) Notes about using shared RDAREAs.