Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Strange error with Oracle 10g XE

Re: Strange error with Oracle 10g XE

From: Robbert van der Hoorn <reply_at_forum.only>
Date: Thu, 28 Sep 2006 11:15:17 +0200
Message-ID: <451b92b0$0$4516$e4fe514c@news.xs4all.nl>

"Jens Lenge" <spampot_at_gmx.net> wrote in news:1159390248.774714.70490_at_k70g2000cwa.googlegroups.com...
>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)?
>

Jens,

10.2 EE does not show this behaviour and does drop both the constraint AND the index.

Robbert van der Hoorn
OSA IT BV
The Netherlands Received on Thu Sep 28 2006 - 04:15:17 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US