IBM Support

Why there are exclusive locks on system tables after setting INTRA_PARALLEL to NO

Question & Answer


Question

After changing INTRA_PARALLEL from YES to NO and restarting the server, execlusive locks are observed, like: lock_mode lock_type schema.table #locks ------------------------------------------------------------- Intention Exclusive Lock TABLE_LOCK SYSIBM.SYSPLAN 1 Intention Exclusive Lock TABLE_LOCK SYSIBM.SYSPLANDEP 1 Intention Exclusive Lock TABLE_LOCK SYSIBM.SYSSECTION 1 Exclusive Lock ROW_LOCK SYSIBM.SYSPLANDEP 12 Exclusive Lock ROW_LOCK SYSIBM.SYSSECTION 8 Exclusive Lock ROW_LOCK SYSIBM.SYSPLAN 1 In some cases, this would cause lock contention and impacts performance. What's the reason?

[{"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Performance - Lock-Latch","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"9.8;9.7;10.1;10.5;11.1","Edition":"Advanced Enterprise Server;Advanced Workgroup Server;Enterprise Server;Express;Express-C;Personal;Workgroup Server","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
30 April 2025

UID

swg21982368

Page Feedback