Tim,

I have a table where I changed the primary key and now it won't open saying the tablestructure doesn't match the catalog #100. I tried this same procedure on 2 different systems and in both cases it rendered the table useless. Is there any way of recovering the data?

Kick

2 Questions:
- What version are you using?
- Did you, at any moment, move/copy individual files between database
directories ?

--
Fernando Dias
[Team Elevate]


<Kick> escreveu na mensagem
news:63707DB1-39EA-4DA7-9EE6-07DCA814DE30@news.elevatesoft.com...
> Tim,
>
> I have a table where I changed the primary key and now it won't open
> saying the tablestructure doesn't match the catalog #100. I tried this
> same procedure on 2 different systems and in both cases it rendered the
> table useless. Is there any way of recovering the data?
>

"Fernando Dias" wrote:

< - What version are you using??>
204 build 2

< - Did you, at any moment, move/copy individual files between database
directories ?>
No, I am 100% sure that is not the case!

Kick,

<< I have a table where I changed the primary key and now it won't open
saying the tablestructure doesn't match the catalog #100. I tried this same
procedure on 2 different systems and in both cases it rendered the table
useless. Is there any way of recovering the data? >>

Please send me the database and table files for the table in question.

BTW, just so you know - there are always copies of the last version of the
catalog and table files as .old files in the database directory after
alterations.  Restoring these will put the catalog and table back to where
they were prior to the alter.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

<<Please send me the database and table files for the table in question.>>

Tim, I have attached the table and a document with the steps to reproduce the error. I hope this will help you find the problem.

<<BTW, just so you know - there are always copies of the last version of the
catalog and table files as .old files in the database directory after
alterations.  Restoring these will put the catalog and table back to where
they were prior to the alter.>>
I had found the .old files myself and rolled back, but I still cannot alter the table. The only way to solve it was to delete the table and let edb recreate it, that alter its structure.

--
Tim Young
Elevate Software
www.elevatesoft.com

Kick,

<< Tim, I have attached the table and a document with the steps to reproduce
the error. I hope this will help you find the problem.  >>

Beautiful, thank you.  I'll make sure that a fix is available ASAP.

--
Tim Young
Elevate Software
www.elevatesoft.com

Kick,

<< I had found the .old files myself and rolled back, but I still cannot
alter the table. The only way to solve it was to delete the table and let
edb recreate it, that alter its structure. >>

When you say that you can't alter the table, do you mean that you can't
execute the same ALTER TABLE actions ?

The workaround here is to do two ALTER TABLEs - one for the ALTER CONSTRAINT
and one for the DROP COLUMN, in that order.

I'll have a fix for this, but it won't be until 2.04 B4 due to the nature of
the issue.  The tests for our test framework aren't completely recreated
yet, and I don't want to put in a fix for this without being able to run it
against all of the regression tests.

I'm doing a 2.04 B3 to fix a couple of critical issues that can't wait.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

<<The workaround here is to do two ALTER TABLEs - one for the ALTER CONSTRAINT
and one for the DROP COLUMN, in that order.>>

When I do them in two seperate alterations then the second one (dropping the column) also failes with the same errormessage.

<<I'll have a fix for this, but it won't be until 2.04 B4 due to the nature of
the issue.  The tests for our test framework aren't completely recreated
yet, and I don't want to put in a fix for this without being able to run it
against all of the regression tests.>>

No problem I have worked around this problem so there is no hurry.