Hi

I have a problem with a database. I was restructuring a table to add a foreign key constraint. I got an error message of #401 The Constraint 7678 does not exist in the table. Tried Adding the Constraint again, same symptom.

I tried repairing the referenced table but I am unable to repair, optimise or verify the referenced table - same error.

Hope you can help.

Chris,

<< I have a problem with a database. I was restructuring a table to add a
foreign key constraint. I got an error message of #401 The Constraint 7678
does not exist in the table. Tried Adding the Constraint again, same
symptom.

I tried repairing the referenced table but I am unable to repair, optimise
or verify the referenced table - same error. >>

What version of EDB are you using ?  A very similar bug was just fixed in
2.13:

http://www.elevatesoft.com/incident?action=viewaddr&category=edb&release=2.13&incident=3822

The description on that incident report is a little wonky, but the #401
error would be something similar with a numerically-named constraint.

Tim Young
Elevate Software
www.elevatesoft.com

<<What version of EDB are you using ?  A very similar bug was just fixed in
2.13:

http://www.elevatesoft.com/incident?action=viewaddr&category=edb&release=2.13&incident=3822

The description on that incident report is a little wonky, but the #401
error would be something similar with a numerically-named constraint.

Tim Young>>

Hi Tim, still on 2.12, but that incident report looks like it. I'll update. Unfortunately I recreated the the tables, so I can't definitively report back as to whether it is the problem - sorry.

Thanks for letting me know.

Chris,

<< Hi Tim, still on 2.12, but that incident report looks like it. I'll
update. Unfortunately I recreated the the tables, so I can't definitively
report back as to whether it is the problem - sorry. >>

No problem - if you see anything still with 2.12, please let me know.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

I am seeing a similar error with one of my tables. I was also adding a foreign key to a table "refProgramTree" that references table "refForms". Altering the table failed. But unlike the other user, I'm using 2.13 B2.

Now I can no longer reference the data from refForms. A simple "Select * from refForms" gives me an error:
"ElevateDB Error #401 The constraint 279080 does not exist in the table refProgramTree"

REPAIR TABLE "refForms" STRUCTURE ONLY
produces the same error.

I can reverse engineer the database structure, but it will fail if I try and export the data.
I ran verify and repair on refProgramTree just to be sure, but there is nothing wrong with this table (the table that appears in the error message). The table refProgramTree in the reverse engineer dump does NOT reference refForms table so I don't know what it is complaining about.

Is there a way to repair the table refForms? Or do I blow it away and re-enter the data or restore yesterday's backup and redo my schema changes?

TIA
Barry
v2.13 B2

I ended up restoring the database from a backup.

What I've leaned from all this is if I make extensive changes to the database structure, I will do backups along the way. It is cheap insurance.

Barry

Barry,

<< I am seeing a similar error with one of my tables. I was also adding a
foreign key to a table "refProgramTree" that references table "refForms".
Altering the table failed. But unlike the other user, I'm using 2.13 B2. >>

What do you mean by "altering the table failed" ?  Did it fail with the same
error # and message ?

There were prior bugs with FK alterations that could cause this:

http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.12&incident=3822
http://www.elevatesoft.com/incident?action=viewrep&category=edb&release=2.05&incident=3432

These are all fixed, though.

The issue is an error in the database catalog itself, not the table tiles.
You should be able to simply restore the .old versions of all altered table
files and catalog files and that will get you back to where you were.  You
can determine which files were affected by the timestamps on the .old files.

Tim Young
Elevate Software
www.elevatesoft.com

Barry,

Also, can you send me a pre-alteration version of the database along with
the FK alterations that you were making ?  I'll see if I can reproduce the
problem here.

Tim Young
Elevate Software
www.elevatesoft.com