RE: Tracking Temp Segment Usage and Event 10046

[Jamadagni, Rajendra]

Title: Tracking Temp Segment Usage and Event 10046

I spent last two days working on that SQR and finally nailed it. Developers were using DISTINCT as a rule and CBO was choosing incorrect indexes.

 

I had to do following to make it work ...

 

1. we put hints in appropriate places

2. created 3 new indexes to help the queries

3. Created 1 MV

4. Change the pl/sql code to be more efficient

5. Remove unnecessary distinct conditions.

 

After all this said and done, I finally have the SQR taking around 375 seconds compared to about 1500 seconds. Even if I run all 8 of them in parallel it doesn't blow the TEMP segments.

 

Now comes the difficult part, to explain the development the things that we had to do and why we had to do them.

 

I think I am really starting to see the power of event 10046 ... I just wish I should learn more on event 10053 as well, but that will come too eventually.

 

I am still going to track the temp segment usage though ...

 

Thanks everyone for all your kind suggestions, I am not done yet, there is more work to be done.

 

Raj

______________________________________________________

Rajendra Jamadagni              MIS, ESPN Inc.

Rajendra dot Jamadagni at ESPN dot com

Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.

QOTD: Any clod can have facts, but having an opinion is an art!

-----Original Message-----
From: Khedr, Waleed [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 18, 2002 11:03 AM
To: Multiple recipients of list ORACLE-L
Subject: RE: Tracking Temp Segment Usage and Event 10046

I'd start looking at the execution plans first and examine if there is any Cartesian joins and the order the tables get joined.

 

Waleed

********************************************************************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.*********************************************************************2