Kbase P138325: Running a NO-LOCK query from a 10.1A remote client to a 10.1C database fails with an "Attempted to r
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/03/2009 |
|
Status: Verified
SYMPTOM(s):
Running a NO-LOCK query from a 10.1A remote client to a 10.1C database fails with an "Attempted to return record with DBKEY > 32 bits" error
(-----) Attempted to return record with DBKEY > 32-bits to an older client.
FACT(s) (Environment):
Running the same query without the NO-LOCK qualifier succeeds.
The database does not have any tables with RECIDs > 32 bits.
HP-UX 11.x
PA-RISC 64-bit
OpenEdge 10.1A 64-bit
OpenEdge 10.1B 64-bit
OpenEdge Category: Database
CAUSE:
Bug# OE00176456
FIX:
Upgrade to version 10.1C03 or higher
If upgrading is not possible at this time then you can run the query without the NO_LOCK qualifier.
However, note the following when running a query with the NO-LOCK qualifier:
When you read records with NO-LOCK, you have no guarantee of the overall consistency of those records because another user might be in the process of changing them. When values are assigned to indexed fields for a newly created record or are modified in an existing record, the index is immediately updated to reflect the change. However the copy of the data record in the buffers used by the database server might not be updated until later in the transaction.