Database Tuning (MOSC)

MOSC Banner

direct path read temp happens even though v$pga_target_advice size seems ok

edited Oct 23, 2013 10:55PM in Database Tuning (MOSC) 12 commentsAnswered ✓
 Hi,
Could anybody point me into right direction, since it seems that I am do not understand why this is happening.

The Application is performing lots of sort, but eventhough pga_aggregate_target seems to have a big enough value.

- The temp size grows till it reaches 60GB.
- The pga_aggregate_target=256MB (I had it at 2g, but that did not make any difference - still the same amount of temp needed??)
- The advisor:

    TARGET_MB  SIZE_FACT EXTRA_R_W_MB CACHE_HIT_PERC ESTD_OVERALLOC_COUNT
---------- ---------- ------------ -------------- --------------------
        32       ,125   5298876416             21                    0
        64        ,25   5298876416             21                    0
       128         ,5   5298876416             21                    0
       192        ,75   1324719104             51                    0
       256          1   1324719104             51                    0
       307        1,2   1324719104             51                    0
       358        1,4   1324719104             51                    0
       410        1,6   1324719104             51                    0
       461        1,8   1324719104             51                    0
       512          2   1324719104             51                    0
       768          3   1324719104             51                    0

 TARGET_MB  SIZE_FACT EXTRA_R_W_MB CACHE_HIT_PERC ESTD_OVERALLOC_COUNT

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center