01.09.2016 Views

Beginning Oracle Database 11g Administration From Novice to Professional

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

358<br />

CHAPTER 16 INSTANCE TUNING<br />

“Then why are you searching here?”<br />

“Because it is so much brighter here!”<br />

The s<strong>to</strong>ry is fictional, and the moral is that you must concentrate your efforts in the<br />

appropriate place. You shouldn’t focus your effort wherever it is most convenient <strong>to</strong> do<br />

so—in fact, the problem might not even be in the <strong>Oracle</strong> database at all.<br />

Here is an example of a case where poor performance was reported but the database<br />

was not the problem. The output shown in Listing 16-1 was produced by using the<br />

procedure <strong>to</strong> trace a poorly performing batch process<br />

and then using the utility <strong>to</strong> summarize the trace data. The session was traced for<br />

about 40 minutes, and the data shows that the <strong>Oracle</strong> database spent only 140.08 seconds<br />

in executing SQL queries. The bulk of the time—2138.67 seconds—was spent waiting for<br />

further instructions from the program. This clearly showed that the database was not the<br />

problem.<br />

Listing 16-1. Sample Output of the Utility

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!