Kbase P133414: FIND with EXCLUSIVE-LOCK unsuccessful on Oracle DataServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/01/2010 |
|
Status: Unverified
SYMPTOM(s):
FIND with EXCLUSIVE-LOCK unsuccessful on Oracle DataServer
Error 138 find record just updated from within one session
** <file-name> record not on file. (138)
The sqlcrc for the sql statement is 0
FACT(s) (Environment):
FIND with NO-LOCK for the same record works
All Supported Operating Systems
OpenEdge 10.1x
CAUSE:
Bug# OE00177602
CAUSE:
There is a rare scenario where the dataserver code may confuse cursor handles and query the wrong table when performing a FIND with EXCLUSIVE-LOCK from the ABL. It is clear that the record indeed exists but the record cannot be found with a lock even though finding it with NO-LOCK is successful.
FIX:
To workaround this problem use the dataserver connection parameter -Dsrv skip-schema-check