Kbase P64050: Received lock errors 2087, 6167, 1069, and 142 when loading data to MS SQL Server using the MS SQL S
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/7/2010 |
|
Status: Verified
SYMPTOM(s):
Received lock errors 2087, 6167, 1069, and 142 when loading data to MS SQL Server using the MS SQL Server DataServer
The record was updated while you were holding it. (2087)
Tried to access a record without a valid id (6167)
<filename> record was deleted since you have read it (1069)
** Unable to update <filename> Field. (142)
Received Event Logger error 997: Could not post a "----" event to the Event Viewer. (5180)
FACT(s) (Environment):
Reading Progress db then creating records in MS SQL Server database
Multiple clients creating data against the same tables
MS SQL DataServer
Progress 9.1x
OpenEdge 10.x
Windows
CAUSE:
The executing procedure was not specifying a lock when finding the records. This is causing the record to be found with NO-LOCK. Because of this, the possibility of having the above problems are greater.
FIX:
When writing code against a foreign data source it is very important to specify the correct lock statement, either NO-LOCK or EXCLUSIVE-LOCK. SHARE-LOCK's are not supported the same way as in Progress and should be avoided