You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
The text below is an except from the book,
Oracle Performance Firefighting, written by
Craig Shallahamer of
OraPub, Inc.
Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click
here.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
-------------------------------
Figure 5-18. Many factors-such as cost, maintenance, security, the end users' experience and location, and computing system capacity-helped push Oracle to embrace a web-based architecture. This is a highly simplified drawing highlighting the key Oracle architectural components: browser, Oracle client process, Oracle server process, and the Oracle SGA.
Conceptually, all database activity flows through DBMS_MONITOR, and if any activity meets certain specific criteria, the activity is captured. So instead of focusing on a specific user (which you can do), you focus on defining the criteria of interest. Oracle introduced DBMS_MONITOR in Oracle Database 10g, and unlike other diagnostic features, it does not require an additional license.
This package combines many of the ways we have traditionally traced Oracle processes, but extends it to meet modern architecture challenges. DBMS_MONITOR allows for the creation of trace files, including bind variables, SQL, and wait event details. Additionally, it collects v$sesstat and v$sess_time_model-based statistics. DBMS_MONITOR is a very flexible and nicely designed package that eventually every DBA will use.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
|