I have a major problem. I just restored my database from a backup and catalog too. But I keep getting Error #100 Version mismatch

I'm using v2 b4 and the backup is v2b4 but I keep getting this error how do I fix this?

Michael Thompson <cross7@roadrunner.com> wrote:

I have a major problem. I just restored my database from a backup and catalog too. But I keep getting Error #100 Version mismatch

I'm using v2 b4 and the backup is v2b4 but I keep getting this error how do I fix this?

I need to give more information. The database nor the cat file were not replaced I just restored my catalog file when restoring my programming
file.

Michael Thompson <cross7@roadrunner.com> wrote:

Michael Thompson <cross7@roadrunner.com> wrote:

I have a major problem. I just restored my database from a backup and catalog too. But I keep getting Error #100 Version mismatch

I'm using v2 b4 and the backup is v2b4 but I keep getting this error how do I fix this?

I need to give more information. The database nor the cat file were not replaced I just restored my Config file when restoring my programming
file.

Michael,

<< I have a major problem. I just restored my database from a backup and
catalog too. But I keep getting Error #100 Version mismatch

I'm using v2 b4 and the backup is v2b4 but I keep getting this error how do
I fix this?

I need to give more information. The database nor the cat file were not
replaced I just restored my Config file when restoring my programming file.
>>

Per my email response:

Something above is not correct.  If you are using 2.01 B4 and the
configuration file is at most 2.01 B4 or lower, then EDB will use it just
fine.  You only get a version mismatch error when EDB detects that a
configuration or catalog file is *newer* than the EDB version being used.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Thats what I thought, but that isn't what I was getting. Because of time contraints I had to roll back the database about two weeks which is no big
deal this is my test datal. But I was concerned because I shouldn't have gotten this error. In any case it caused me to rethink my backups too.

Thanks

Michael


"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote:

Michael,

<< I have a major problem. I just restored my database from a backup and
catalog too. But I keep getting Error #100 Version mismatch

I'm using v2 b4 and the backup is v2b4 but I keep getting this error how do
I fix this?

I need to give more information. The database nor the cat file were not
replaced I just restored my Config file when restoring my programming file.
>>

Per my email response:

Something above is not correct.  If you are using 2.01 B4 and the
configuration file is at most 2.01 B4 or lower, then EDB will use it just
fine.  You only get a version mismatch error when EDB detects that a
configuration or catalog file is *newer* than the EDB version being used.

--
Tim Young
Elevate Software
www.elevatesoft.com

Michael,

<< Thats what I thought, but that isn't what I was getting. Because of time
contraints I had to roll back the database about two weeks which is no big
deal this is my test datal. But I was concerned because I shouldn't have
gotten this error. In any case it caused me to rethink my backups too. >>

If you want to send me the files, I can tell you exactly which file
(configuration, database catalog, etc.) contains the version mismatch.  If
EDB says there's a version mismatch, then there is most definitely a version
mismatch.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

>>If EDB says there's a version mismatch, then there is most definitely a version
mismatch.<<

Just curious how this has gone out, because I had a similar problem last week.

I added an index to a table, after that EDB Manager froze. After 2 minutes I killed the
task. When reopening EDB Manager and trying to reopen the table, I got an error message I
don't remember, maybe saying some files are corrupt. I checked the files - the tables
didn't have an .old, but the catalog had, written just 2 minutes before. I deleted the
catalog, renamed the .old catalog, and after reopening EDB Manager I got this "version
mismatch" error.

Heiko

Heiko,

<< I added an index to a table, after that EDB Manager froze. After 2
minutes I killed the task. When reopening EDB Manager and trying to reopen
the table, I got an error message I don't remember, maybe saying some files
are corrupt. I checked the files - the tables didn't have an .old, but the
catalog had, written just 2 minutes before. I deleted the catalog, renamed
the .old catalog, and after reopening EDB Manager I got this "version
mismatch" error. >>

How big was the table that you were indexing ?  Can you send me the table ?

If any of the files are updated, they are copied/renamed to an .old version
first.  There's no way for EDB to update a physical file without this taking
place.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

sorry, the whole db is deleted and re-migrated (no harm done, was just for test purposes),
and on the second try everything was fine. Small table, index created in less than a
second. No chance to reproduce this.

I just wondered if this could be somehow related with this thread...that EDB maybe does
something to files BEFORE they are backed up, or renamed to .old

Heiko

Heiko,

<< I just wondered if this could be somehow related with this thread...that
EDB maybe does something to files BEFORE they are backed up, or renamed to
..old >>

No, not that I'm aware of.  I'll do some tests, though, to make sure that
I'm not missing anything.

--
Tim Young
Elevate Software
www.elevatesoft.com