Dropped constraint not really gone? 1

[ThatRickGuy]

A table I was working on had a 2 column primary key. Due to some design changes I needed to switch to a 3 column primary key. So I dropped the original PK, and created a new one. Only when I tried to create the new constraint (with the same name as the original one), toad popped an error telling me that an object with that name already exists. I made sure my changes were committed, refreshed toad (even closed toad and came back in) and the original constraint is not showing up, but I still can not use that name. Even worse, the constraint is still applied to the table. Yet the table scripts have no mention of the old primary key.

How can I get rid of this phantom?

Thanks,
-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[jaxtell]

I'd start with verifying it's presence in the data dictionary.

select * from all_indexes ai where ai.INDEX_NAME = 'MY_TABLE_PK'

if you find it, and it is what you expected, drop it.

drop index MY_TABLE_PK;

Then try again.

 

[ThatRickGuy]

I just broke down, exported the data, dropped the table, and re-ran the table and constraints scripts. After that, it seems to be working correctly.

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.

 

[ThatRickGuy]

Doh, after looking at the scripts I see exactly what you were talking about. It is the index. Thanks!

-Rick

VB.Net Forum forum796 forum855 ASP.NET Forum
I believe in killer coding ninja monkeys.