Icon View Incident Report

Serious Serious
Reported By: Krisztian Kepes
Reported On: 1/28/2010
For: Version 2.03 Build 7
# 3142 Altering a Database to Point to a New Empty Path Can Cause Existing Catalog to Be Copied to New Path

I used a local config for my first tests, in dir named "c:\d\first test". I created some DBs, and tables, and other testify objects here. This config is points to "c:\d\first test\db" as "THEDB". For example THEDB is containing the table "A".

When the testify age ended, I tried to migrate our DBISAM DB under EDB. For this I copy the config files from "c:\d\first test", and copy them into "c:\d\Scroll4", which is the folder of our new product.

After this is I reparameterized the Local Session in the EDB Manager to point "c:\d\Scroll4". Ok. Then I tried to set the new location of the "THEDB" to point at "c:\d\Scroll4\db".

Next I very wondered, because the table, named A REMAINS!

I do not understand it!!! The "c:\d\Scroll4\db" was EMPTY! Why the system remembered to table A?

Comments Comments
The problem was caused by the addition of the CatalogVersion property to the Databases table in the 2.03 B7 system Configuration database. This addition was causing the new database catalog to be opened after the ALTER DATABASE, and would result in it being created to match the existing database catalog in the prior path, even though the new path was originally empty.

Resolution Resolution
Fixed Problem on 1/29/2010 in version 2.03 build 8

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