Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 7 of 7 total |
Restore Database Failure (a particular table is flagged wrong version) |
Thu, Jun 8 2017 7:09 PM | Permanent Link |
Andrew Hill | Tim, I have a Database Backup that I cannot Restore.
Reverse Engineer SQL of current Database and Reverse Engineer SQL of the Restore Database (now in it's own separate database location) are identical. Reverse Engineer Upgrade referencing both shows no schema difference ? I can send backups of both databases privately but not publicly. How can we see all the info in EDBConfig ? Andy |
Mon, Jun 12 2017 6:26 AM | Permanent Link |
Adam Brett Orixa Systems | Andrew
Have you used the "Reverse-Engineer Database", "Upgrade" option in EDB Manager to actually compare the two versions? If they are really identical the resulting script should be empty. If the backup file is restoring, is there a problem in just using the newly restored db? Adam |
Mon, Jun 12 2017 6:51 AM | Permanent Link |
Roy Lambert NLH Associates Team Elevate | Adam
>Have you used the "Reverse-Engineer Database", "Upgrade" option in EDB Manager to actually compare the two versions? He says he has <<Reverse Engineer Upgrade referencing both shows no schema difference ?>> >If the backup file is restoring, is there a problem in just using the newly restored db? I've been helping him a bit off forum. His question to me was <<From time-two-time I BackUp remote, DownLoad and Restore data to local for review purposes. The problem is that sometimes the Restore Database Structure is not identical to the local Database Structure and the Restore process fails (EDB Never explains why [it may be the fact that I changed a VARCHAR from 20 to 25 in length –or- an extra field –or- a field position changed]). How do we get EDB to explain what is miss matched in the failed restore process ?>> The only suggestion I could make was to save with catalog so that it can overwrite. I also suggested COMPARE DATABASE which I suppose reverse engineer upgrade is equivalent to. I suppose Andy's real questions are 1) why is this happening 2) how do I sort it out 3) how do I stop it happening again Roy Lambert |
Tue, Jun 13 2017 12:35 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Roy,
<< How do we get EDB to explain what is miss matched in the failed restore process ? >> The short answer is "you can't". EDB itself doesn't know *why* they are mismatched, only that the checksums for the table structures are different. However, having said that: Rolf Frei reported a bug last week that involves the computation of the checksum for indexes when altering tables, so there is a fix coming that involves this area of the engine. Tim Young Elevate Software www.elevatesoft.com |
Tue, Jun 13 2017 12:35 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Andrew,
<< Tim, I have a Database Backup that I cannot Restore. Reverse Engineer SQL of current Database and Reverse Engineer SQL of the Restore Database (now in it's own separate database location) are identical. Reverse Engineer Upgrade referencing both shows no schema difference ? I can send backups of both databases privately but not publicly. >> Please email me the backups, and I'll take a look. Tim Young Elevate Software www.elevatesoft.com |
Sun, Jun 18 2017 12:10 AM | Permanent Link |
Andrew Hill | Tim, I did drop and Re-Create an Index and now that you have acknowledged the Index bug I will wait for your update to test - Andy
|
Mon, Jun 19 2017 2:22 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Andrew,
<< Tim, I did drop and Re-Create an Index and now that you have acknowledged the Index bug I will wait for your update to test >> No, that's not what I said. I was simply indicating that there is a fix to this *area* of EDB, not that this fix necessarily has anything to do with what you're seeing. I can only tell you that once I confirm that it is, indeed, what is causing what you're seeing. It could be something else entirely, thus I need your databases in order to tell you whether it is even an issue with EDB. Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Sunday, May 19, 2024 at 08:46 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |