Kbase P12411: Seeing IX table lock using 4 GL client, what does this mean.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1x
SYMPTOM(s):
Not doing query by rowid.
Seeing IX table lock using 4 GL client.
CHAIN: TAB, rec-id: 0, Lock:IX.
Record Locking Table:
Usr Name Chain # Rec-id Table Lock Flags
5 pds-batc REC 698 71189858 105 EXCL L
5 pds-batc REC 1285 71033728 100 EXCL L
5 pds-batc REC 1351 71033795 99 EXCL
5 pds-batc REC 1358 71033796 105 EXCL L
5 pds-batc REC 1359 71033797 105 EXCL
5 pds-batc REC 1360 71033799 104 EXCL L
5 pds-batc REC 2356 60231276 26 EXCL
5 pds-batc REC 2590 7508163 48 EXCL
5 pds-batc REC 2829 71369222 36 EXCL L
5 pds-batc REC 2846 71369223 52 EXCL L
5 pds-batc REC 2847 71369224 52 EXCL L
5 pds-batc REC 3126 71369256 299 EXCL
5 pds-batc TAB 3459 0 52 IX L
RETURN - repeat, U - continue uninterrupted, Q - quit
CAUSE:
Implicit table locks are generated when rows in the table are locked.
FIX:
The V9 database supports a hierarchical locking mechanism. It is a two level hierarchy:
- tables
- rows within tables
When the hierarchical locking is active, there are five table lock modes:
- Intent Share (IS)
- Intent Exclusive (IX)
- Shared with Intent Exclusive (SIX)
- Shared (S)
- Exclusive (X)
Implicit table locks ( IS, IX and SIX) are generated when rows in the table are locked.