Re: Poor perfmance after large delete

From: Phil Cook <pcook_at_iamerica.net>
Date: 1997/04/21
Message-ID: <01bc4e73$e1cc4f00$95f9adcd@cookp.mo.chaparralsteel.com>#1/1

The highwater marks may be still set at the fully populated point in your tables. You
must perform a truncate to reduce the highwater back to the initial extent. You
may also have a problem with the cost optimizer, try performing any analyze on any
tables that have changed dramatically in cardinality. To get around the constraints,
perform 'alter table xxx disable constraint yyy cascade'. To put the constraints
back on, use sql to 'alter table xxx enable constraint yyy' using the view user_constraints
or all_constraints to find the constraints with status = 'DISABLED'

Phil Cook Received on Mon Apr 21 1997 - 00:00:00 CDT