Title: RE: 9.2.0.3 online index builds resolved (we hope)

Curious me ... how big is the table that gets 'complete turnover of data in 15 minutes' ...??

Raj
--------------------------------------------------------------------------------
Rajendra dot Jamadagni at nospamespn dot com
All Views expressed in this email are strictly personal.
QOTD: Any clod can have facts, having an opinion is an art !


-----Original Message-----
Sent: Thursday, June 05, 2003 11:30 AM
To: Multiple recipients of list ORACLE-L



As we found out last night, the "fix" doesn't fix anything.  The online
index rebuild will still hang indefinitely and lock the table.

Since there is bound to be some inquisitive mind out there wanting know why
we have a nightly online index rebuild: This is on tables that have complete
turnover in their data every 15 minutes .... COOL!  The index sizes grow
approximately five-fold in a day.  The DBA's here didn't write the app, and
during the design phase (using the term very loosely), we told them (in our
best cartoon voice)
Y-O-U-'-L-L  B-E  S-O-R-R-Y
(Actually, it's us that's sorry since we are the ones that have to deal with
it.)

We upgraded to 9.2.0.3 because of the show stopping shared pool
fragmentation in 8.1.7.4.  We apparently got rid of one problem and picked
up another one. (SURPRISE!)  I guess I'll have to write some logic in the
script to detect when the index build gets stuck and kill it.  Oracle really
should be begging us to be become a beta test site.  We can screw up a steel
ball.

*********************************************************************This e-mail 
message is confidential, intended only for the named recipient(s) above and may 
contain information that is privileged, attorney work product or exempt from 
disclosure under applicable law. If you have received this message in error, or are 
not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 
and delete this e-mail message from your computer, Thank 
you.*********************************************************************1

Reply via email to