Kbase P109180: IDXFIX can create a table lock if index key is corrupted and points to recid 0.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
24/10/2008 |
|
Status: Verified
SYMPTOM(s):
IDXFIX can create a table lock if index key is corrupted and points to recid 0.
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
CAUSE:
Any reference to RECID 0 is an invalid reference.
IDXFIX has found an index key that refers to recid 0 which has caused it to acquire a table lock.
Example:
Promon shows the following information:
Usr Name Chain # Rec-id Table Lock Flags
180 foo REC 675 51311759 1 SHR
9988 foo REC 1366 1350 16 SHR
163 foo REC 2841 461570 29 SHR
157 foo REC 4164 113746210 19 SHR
179 foo REC 4708 34900234 1 SHR
176 foo REC 5232 463961 29 SHR
163 foo REC 5696 274602243 35 EXCL
174 foo REC 5992 244593816 1 SHR
188 foo REC 6435 465164 29 SHR
183 foo REC 6842 108213891 1 SHR
187 foo REC 6974 465703 29 SHR
10097 foo REC 9042 207287835 39 SHR
9988 foo REC 9634 3569950 45 SHR &nb.sp;
10097 foo REC 9825 2722435 46 SHR
178 root TAB 9974 0 1 SHR
180 foo TAB 9974 0 1 IX U Q
174 foo TAB 9974 0 1 IX U Q
183 foo TAB 9974 0 1 IX U Q
179 foo TAB 9974 0 1 IX U Q
User 178 is the idxfix process. It should never be attempting to get recid 0.
IDXFIX should not be allowed to table lock..
CAUSE:
Enhancement Request# 20050922-038
CAUSE:
Bug# OE00120738
FIX:
Upgrade to 10.0B or later.