Hello

Probably caused by a broken connection during a script that try to alter a
table now
I got the error:
"#100 There is an error n the metadata for the table TableName (The internal
structure does not match the structure in the catalog)

I try to repair the table and I try to replace the table with the .Old
tables without success
What else can I do?

I'm using ver 2.04B4

Thanks Sorin

Sorin


If you have a backup restore from that. If not and the data isn't important delete the table files and ElevateDB will recreate them when you try to open it.

Roy Lambert [Team Elevate]

"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
> If you have a backup restore from that. If not and the data isn't
> important delete the table files and ElevateDB will recreate them when you
> try to open it.
>

It's a client data. I believe that they have a backup but this mean lossing
the data they insert since the backup.
Yes the data is important.

Are there a way to fix the table?

Thanks Sorin

Sorin,

> I try to repair the table and I try to replace the table with the .Old
> tables without success
> What else can I do?

If you can do a select query against the table,  you can do the following:

1. Drop all indexes, constraints, and triggers from the table.  Basically
you need to get it to the point where you would normally be able to drop the
table.

2. Create a copy of the table using:

create table <tempname> as select * from <tablename> with data

3. Drop the original table.

4. Rename <tempname> to <tablename>

5. Put your indexes, constraints, and triggers back and restructure the
table if it isn't an exact match of what you were expecting.

If you can't read the table using a query, you are back to restoring from a
backup.

--

---------------------------------------
 Terry Swiers
 Millennium Software, Inc.
 http://www.1000years.com
 http://www.atrex.com

Now shipping Atrex 13.  For more information go to
 http://www.atrex.com/news.asp

Atrex Electronic Support Options:
 Atrex Knowledgebase: http://www.atrex.com/atrexkb.asp
 Email: mailto:support@atrex.com
 Newsgroup: news://news.1000years.com/millennium.atrex
 Fax: 1-925-829-1851
 Phone: 1-925-828-5892 (M-F, 9a-5p Pacific)
 ---------------------------------------

Terry,

> If you can't read the table using a query, you are back to restoring from a
> backup.

Sure, but it *must* be possible to restore the table data. I had such a
case before and a lot of trouble restoring important data.

Regards Uli

>> If you can't read the table using a query, you are back to restoring from
>> a backup.

No I can't read the table using query.
If I try to run a select it's raise the same #100 error

Thanks
Sorin

Sorin


EMail or phone Tim for support - he's the only one who may be able to do something.

Roy Lambert

Sorin,

<< Probably caused by a broken connection during a script that try to alter
a table now >>

Did you run the ALTER TABLE with 2.04 B4 ?  If so, then it is impossible for
an ALTER TABLE to cause this type of error.  Did you copy around any files,
or restore the database at any time ?

--
Tim Young
Elevate Software
www.elevatesoft.com

Sorin,

<< Are there a way to fix the table? >>

It depends upon what happened to cause the error.  If restoring the .old
versions of the database catalog and table files doesn't work, then
something/someone has copied over the files incorrectly from another
location.

Please email me the database catalog and table files, along with the .old
files, as a .zip file.  It's important that the creation/modification
dates/times on the files are intact.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

> Did you run the ALTER TABLE with 2.04 B4 ?

Yes this for shure

<If so, then it is impossible for
> an ALTER TABLE to cause this type of error.  Did you copy around any
> files, or restore the database at any time ?

I believe (not shure) that the error was cause because there wasn't enough
space on the driver.
I did play with the data trying to fix the problem but this was on a copy of
the original data,
the error on the original disk start straight after running the script.
I make a mistake and didn't copy the error message.

Thanks
Sorin