Kbase P104218: Unable to read records created via Oracle tools with for each exclusive-lock.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/15/2008 |
|
Status: Verified
SYMPTOM(s):
Unable to read records created via Oracle tools with for each exclusive-lock.
Able to read records created via Oracle tools with for each share or no lock
Able to read and update records created via Progress
Oracle database created via ProToOra
Errors (142) and (1069) when records are read with share lock and try to be updated
** Unable to update Field. (142)
<filename> record was deleted since you have read it (1069)
CAUSE:
When records are created via the Oracle tools, the progress_recid field is not populated. When the lock of a record is being upgraded or the DataServer is trying to get an exclusive-lock on the record, it can not be found because the select is done using the RECID of the record.
The records can be read with forward scrolling since the RECID is not used to find the records.
FIX:
Create an insert trigger in Oracle that will check the progress_recid field to see if it is null and if it is will get the next sequence number and assign to the progress_recid field.