Icon View Incident Report

Serious Serious
Reported By: Stephan Krämer
Reported On: 7/2/2007
For: Version 1.04 Build 4
# 2399 Backing Up an Older Version Database Catalog with the Latest Version Causes Restore Issues

I backup the database A in EDBMgr.

In EDBMgr, I create database B and want to restore the backup of A into that one. -> Result Error: Division by zero.
If I try to restore into the same database A, then I get ElevateDB Error #400 The table already exists.


Comments Comments
This issue was caused by the fact that ElevateDB was not stamping the catalog with the most current version number of the engine during the backup process. This doesn't cause an issue for any database catalogs that are already in 1.04 format due to being modified using 1.04. However, if an older 1.03 or earlier catalog that hasn't been modified using 1.04 was backed up, then the catalog would be saved in the backup in 1.04 format but not stamped with the 1.04 version number. When the restore is then executed, ElevateDB will then try to restore the catalog in 1.03 or earlier format instead of the correct 1.04 format, thus causing all sorts of errors.

If you have any backups that were created using version 1.04 from databases that have not been modified using version 1.04, then you will need to re-execute these backups using 1.04 Build 5 in order to avoid having any issues during restoration. A database is considered "altered" whenever any DDL statements are executed that modify any objects stored in the catalog such as tables, views, functions, or procedures.


Resolution Resolution
Fixed Problem on 7/3/2007 in version 1.04 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 VCL Client-Server
ElevateDB VCL Client-Server with Source
ElevateDB VCL Standard
ElevateDB VCL Standard with Source
ElevateDB VCL Trial

Image