Kbase P176613: Progress crashes with error 49 when creating new record for buffer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
28/03/2011 |
|
Status: Verified
SYMPTOM(s):
Progress crashes with error 49.
SYSTEM ERROR: Memory violation. (49)
Table contains either a database schema trigger or session schema trigger which populates a key field.
Client session #1 does a FIND NO-LOCK on a record and keeps this buffer in scope.
Client session #2 deletes the record that client session #1 has in the buffer.
Client session #1 creates a record for the same table in a different buffer and the dbkey assigned to the new record is the same as the dbkey of the record in the first buffer (i.e. we reuse empty dbkeys).
Stack Trace:
bflbiru
bfu
profldu
fdfldu
fmfldu
rnuassgn
rnRealAssign
rnassign
rnexec_entry
rninterpret
umeDispatchEvent
wvRunDispatcher
iodispatch
rnrq
main
FACT(s) (Environment):
OpenEdge 10.2A
OpenEdge 10.2B
All Supported Operating Systems
CAUSE:
Bug# OE00100951
CAUSE:
Due to a fix for a different issue it became possible for us to not clean up some pointers properly before assigning a dkbey for a new record.
FIX:
Upgrade to OpenEdge 10.2B03 or later.