View Incident Report

Serious

Reported By: Heiko Knuettel
Reported On: 10/21/2008
For: Version 2.02 Build 1

# 2827 Referencing a Different Database In a UNION/EXCEPT/INTERSECT Query Causes Dangling Read Lock

Whenever I execute a query like the following in the memory database context, a read lock is placed on the disk database catalog that doesn't get released when I close & free the query or when I drop the memory table. It gets released only when I close the session. Don't know if this is intentional, but when 2 or 3 of these locks are present, database.Open begins to fail and I'm getting these "cannot lock the catalog diskdb for read access" errors logged.

CREATE TABLE xy AS SELECT field1, field1 FROM diskdb.table1 UNION ALL
SELECT field1, field2 FROM diskdb.table2 WITH DATA

Resolution

Fixed Problem on 10/21/2008 in version 2.02 build 2

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

More Support Options

Search Incident Reports

Support Forums

Frequently Asked Questions

Technical Bulletins

Technical Articles

Product Manuals

Roadmap