Re: why would enable constraint cause a delete to wait on library cache lock?

> You should first enable novalidate the constraint and then run enable
> validate.
> This way Oracle knows that any *new* DML can't "invalidate" data and can
> calmly scan through the table without locking it, to see whether the rest
of
> the data is valid as well.

Just to avoid misunderstandings: this "calm scan without locking" is executed using enable validate, after enable novalidate has been ran..

Tanel.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Tanel Poder
  INET: tanel.poder.003_at_mail.ee

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).