View Incident Report

Serious

Reported By: Yusuf Zorlu
Reported On: 5/15/2019
For: Version 2.31 Build 3

# 4742 Row Lock Errors During Update Executions Can Cause a Dangling Read Lock

Update sql is working but if a user had a dataset visible before the update-sql-run and does an .Edit after the updatesql (aborted because of a dataset was in edit) … without doing a .refresh it works and on post the program is locked down + I see following errors on server-side:

ElevateDB Error #300 Cannot lock the table POSITIONEN in the schema Default for write access

Comments

The issue was a dangling read lock that could occur with certain WHERE conditions combined with a row lock error during the execution (because another session had the row locked). Subsequently, any write locks would fail due to the dangling read lock.

Resolution

Fixed Problem on 5/16/2019 in version 2.31 build 4

Products Affected

ElevateDB Additional Software and Utilities
ElevateDB DAC Client-Server
ElevateDB DAC Client-Server with Source
ElevateDB DAC Standard
ElevateDB DAC Standard with Source
ElevateDB DAC Trial
ElevateDB LCL Standard with Source
ElevateDB PHP Standard
ElevateDB PHP Standard with Source
ElevateDB PHP Trial
ElevateDB VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap