Kbase P128830: FIND CURRENT statement in CREATE procedure causes table lock
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
9/4/2009 |
|
Status: Unverified
SYMPTOM(s):
FIND CURRENT statement in CREATE procedure causes table lock
Client Session A aborted the creation of a record
Client Session B is attempting to create a record in the same table
Client Session B receives the following error: Table <table name> is locked. Record create failed. (328) (6527)
Promon shows Transaction state Dead with Flags SHR
Record Locking Table in Promon reads:
Record Locking Table:
Usr Name Chain # Rec-id Table LockFlags Tran State Tran ID
5 REC 158 20685188 84 SHR Dead 10118959
This behaviour does appear in 10.1B, 10.1B01, 10.1B02 and 10.1B03
FACT(s) (Environment):
This behaviour does not appear in 10.1A02 or 9.1E04
ABL/4GL code contains FIND CURRENT statement within the CREATE procedure
All Supported Operating Systems
OpenEdge 10.1B
CAUSE:
Bug# OE00164808
FIX:
Upgrade to OpenEdge 10.1C or later.
As a workarounds, choose one of the following:
1. Start the session using the -nosavepoint client session startup parameter.
Or
2. Remove the FIND CURRENT statement from the CREATE procedure.