Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> To patch 'n pray or to keep looking for the root cause: that is the question

To patch 'n pray or to keep looking for the root cause: that is the question

From: Branimir Petrovic <BranimirP_at_cpas.com>
Date: Fri, 2 Sep 2005 13:32:26 -0400
Message-ID: <33678E78A2DD4D418396703A750048D401025561@RIKER>


Whether 'tis nobler in the mind to suffer... is yet another nagging question for another occasion, this time though I am facing an issue (non a major one) with Oracle export utility and am pondering options.

Basic facts:

Observation:

What did do I about it so far:

When EXP time is NORMAL export's Elapsed Time: 28.82 (mins)

Load Profile

~~~~~~~~~~~~                      Per Second       Per Transaction
                             ---------------       --------------- 
        Logical reads:              4,339.64            341,056.18


SGA breakdown
Pool   Name                      Begin value        End value  % Diff
------ -------------------- ---------------- ---------------- -------
shared KGLS heap                  31,069,644       57,844,052   86.18
shared KQR M PO                   25,728,948       25,911,320    0.71
shared KQR S PO                    2,769,208        2,769,208    0.00
shared free memory                13,291,884       13,969,300    5.10




When EXP time is SLOW export's Elapsed Time:     72.48 (mins)

Load Profile
~~~~~~~~~~~~                      Per Second       Per Transaction
                            ---------------       --------------- 
		Logical reads:         1,715.26            339,074.86


SGA breakdown
Pool   Name                      Begin value        End value  % Diff
------ -------------------- ---------------- ---------------- -------
shared KGLS heap                     936,152       69,954,168 #######
shared KQR M PO                      277,516       24,946,396 #######
shared KQR S PO                       39,728        2,684,552 #######
shared free memory               163,899,464       13,584,080  -91.71




Options I am pondering about:

  1. Over and above taking statspack snapshots before and after Oracle export, start tracing export sessions, run through some of available profilers and scratch head some more (become even more bewildered as new data emerges)?
  2. Apply "latest and greatest" patch set, and hope that 9.2.0.7 will somehow fix it?
  3. Tuck the issue under the proverbial carpet, behave as if it does not exist, (since I anyway hold no leverage over the most likely culprits - good Elbonian folks)?

What would you do?

Branimir

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Sep 02 2005 - 12:35:32 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US