Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Strange error with Oracle 10g XE
A little addition:
The problem seems to be that XE (unlike 9i) does not automatically drop the respective index when a primary key constraint is dropped.
I noticed that after dropping the constraint, the associated index "pk130" is still present. Consequently, when I insert a command "drop index pk130;" before the second SQL statement, I get no more errors.
However, as 9i automatically drops the index "pk130" along with dropping the constraint "pk130", a subsequent attempt to drop the index yields an error with 9i.
Isn't there a solution that works for both 9i and XE? How would the "full" 10g behave (I cannot try as I only have XE at hand)? Received on Wed Sep 27 2006 - 15:50:48 CDT
![]() |
![]() |