Icon View Incident Report

Serious Serious
Reported By: Uli Becker
Reported On: 10/14/2009
For: Version 2.03 Build 4
# 3090 Dead Sessions on the EDB Server Containing Updateable Views Can Cause Lock Errors

App1 and App2 are accessing the same database "Informa". App1 accesses a field that is not existent in the database and is thus terminated leaving a dead session. (Normally that doesn't happen off course, I just ran it to produce a dead session.)

This produces the lock error for sure on my computer:

1. Starting EDBSrvr.exe
2. Starting app1 - error message (field xy not found).
3. app1 is closed leaving a dead session
3. Opening app2: no error, dead session still present
4. When the dead session is removed after timeout:
5. Opening app2 results in #300 error.
6. This error continues until EDVSrvr is restarted.

Comments Comments
The problem was with the closing of the database containing the open updateable view. There was an issue with the closing of any table cursors referenced by the view that would result in the database not being unlocked properly due to an internal AV. Subsequent attempts to open the database would cause a lock error.

Resolution Resolution
Fixed Problem on 10/27/2009 in version 2.03 build 5

Products Affected 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 VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial