View Incident Report

Serious

Reported By: Alan Craker
Reported On: 11/11/2010
For: Version 2.04 Build 4

# 3347 PUBLISH DATABASE Can Cause Catalog Corruption If Referenced Table(s) Cannot Be Opened Exclusively

ElevateDB version 2.04b4
In the EDBManager, If I have a table open and then execute a PUBLISH DATABASE statement, I get a #300 Cannot lock the table for exclusive access, like I would expect. However, if I then go to open any tables ABOVE the one it bombs out on, I get the Error #100 There is an error in the metadata The internal structure does not match the structure in the catalog. All other tables open fine.

Comments

The failure to lock a table exclusively during the publish operation would cause the catalog update to fail, leaving some of the published tables with an invalid metadata checksum in the table files.

Resolution

Fixed Problem on 11/14/2010 in version 2.05 build 1

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