View Incident Report

Serious

Reported By: Fernando Dias
Reported On: 5/17/2008
For: Version 1.09 Build 3

# 2639 Executing Remote SELECT Statements that Generate Insensitive Query Result Sets Can Cause #9999 Error

I'm getting a strange error (#9999) in EDBManager (EDB 1.09 build 3). I'm using client/server with one of the computers acting as server and client and another only as client.

The error is shown at the end of the execution of a query if any rows of one of the tables involved in a join are updated by other session (from another computer) during the query execution, as follows.

The same query executes successfully if there are no concurrent sessions.

- Session 1 starts the execution of:
    select * from catalogo c left outer join faixas f on f.ref = c.ref 
order by ref, lado, faixa

- Session 2 executes with success:
     update catalogo set titulo = 'novo'

- Session 1 continues the execution, and when the progressbar reaches the end,
   'ElevateDB Error #9999' is displayed.

Comments

The issue was two-fold. First, the query change detection was improperly kicking in when the cursor was opened on the ElevateDB Server, causing the query to be executed again. Secondly, this second execution would improperly try to send query progress updates back to the client when it shouldn't have.

Resolution

Fixed Problem on 5/18/2008 in version 1.09 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 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