- Full Description
This book is an anthology of effective database management techniques representing the collective wisdom of the OakTable Network. With an emphasis upon performancebut also branching into security, national language, and other issuesthe book helps you deliver the most value for your companys investment in Oracle Database technologies. Youll learn to effectively plan for and monitor performance, to troubleshoot systematically when things go wrong, and to manage your database rather than letting it manage you.
What youll learn
- Adopt a rational approach to database management; eliminate guesswork
- Add value to your organization as a database professional
- Manage and optimize performance
- Exploit different platform technologies
- Secure your organization's data
- Gain deep understanding of database internals and structures
Who this book is for
This book is aimed at Oracle database administrators who want to further their careers by implementing sound and proven database administration practicesand especially repeatable and predictable practicesin their daily work.
- Table of Contents
Table of Contents
- Battle Against Any Guess
- A Partly Cloudy Future
- Developing a Performance Methodology
- The DBA as Designer
- Running Oracle on Windows
- Managing SQL Performance
- PL/SQL and the CBO
- Understanding Performance Optimization Methods
- Choosing a Performance Optimization Method
- Managing the Very Large Database
- Troubleshooting Latch Contention
- Measuring for Robust Performance
- User Security
- Securing Data
- Source Code/Downloads
Please Login to submit errata.On page 62:
The table at the bottom of page 62 has an issue with column alignment.
The figures for the row "DB CPU" are shown under the wrong column headings.
The figure 9,739 belongs under the column heading "Time(s)". The figure 22.43 belongs under the column heading "% DB Time".
All the tables in this chapter (and maybe others) are lacking a caption.
Top 5 Timed Foreground Events
wait % DB
Event Waits Time(s) (ms) time Wait Class
------------------------------ ------------ ----------- ------ ------ ----------
DB CPU 47 43.7
db file sequential read 27,633 21 1 20.2 User I/O
db file scattered read 2,205 4 2 3.8 User I/O
control file sequential read 1,233 2 1 1.6 System I/O
write complete waits 1 1 999 .9 Configurat
On page 68:
page 68: quote "DB time analysis can also be performed over many dimensions: SQL ID, ...
I disagree. The metric "DB time" is not available per SQL ID. The author does not offer any information on where he thinks "DB time" per SQL ID can be retrieved. For example V$SQL does not have information on "DB time" as such. As you can see here, these are the columns of V$SQL that contain the word "time":
SQL> $grep -i time t.log
According to page 9-8 in Oracle Database Reference Release 11.2 DB time contains "connection management call elapsed time". Since V$SQL does not have information on "connection management call elapsed time" it is impossible to derive DB time from the data in V$SQL.
On page 68:
The information that "DB time" and "DB CPU" for service_name, module, and action are available in v$serv_mod_act_stats is missing. It should be noted that v$serv_mod_act_stats is populated only after using DBMS_MONITOR.SERV_MOD_ACT_STAT_ENABLE has been used. Using google books I get "No results found for this book for v$serv_mod_act_stats".