RE: Tracking Temp Segment Usage and Event 10046

[K Gopalakrishnan]

Title: Tracking Temp Segment Usage and Event 10046

Raj:

 

You will be able to identify the processes (along with the SQLs and number of extents) using the 10046 level 8 trace.

If you use the temp files you see the file# ( in the direct path read/write events) as db_files+1 or MAXDBFILES+1

or similar values. DOn't try to map the FILE# with the dictionary or X$KCFIO. THis is the only catch.

 

 

KG

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jamadagni, Rajendra
Sent: Tuesday, September 17, 2002 7:34 AM
To: Multiple recipients of list ORACLE-L
Subject: Tracking Temp Segment Usage and Event 10046

I have a problem with a process and its temp segment usage.

Previously, in RBO (8161) we used to run 8 reports with slightly different parameters in parallel and it used to work fine with all other load on the system and the total TEMP space was 6GB

Since we migrated to CBO (all tables & indexes are analyzed using estimate), these processes fail with unable to extent temp segment error. Currently we have allocated 12GB to temp tablespace.

I also have performance issues so I am doing a 10046 trace at level 8 on this one. Is there a way to identify when this process used temp space, how much and when does it de-allocate?

Would this information be available in 10046 trace or is there something else that I could do to track that ...

Thanks in advance
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!