Kbase 20620: -210015 [JDBC Progress Driver]:Failure getting record lock
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
FACT(s) (Environment):
Progress 9.1x
SYMPTOM(s):
Running an update operation in SQL-92 fails with error.
-210016 [JDBC Progress Driver]:Lock table is full. (7870)
-210015 [JDBC Progress Driver]:Failure getting record lock
CAUSE:
Bug# 20010224-001
CAUSE:
If while an update operation the SQL92 engine does not use index keys, then it locks all the records read. Immediately after reading the record, the SQL92 will evaluate the predicates; if the predicates evaluate to False, it will release the lock on the record just read.
This means that the SQL92 engine will execute lock requests on all the records read, but will retain locks on only on records that satisfy the predicates.
This is for Read Committed isolation level.
If the SQL92 engine reads the index instead of the records themselves to resolve the query it doesn't request a lock on the corresponding records with the default transaction isolation level Read Committed.
FIX:
Add an index for the fields involved in the query.