This book is an anthology of effective database management techniques representing the collective wisdom of the OakTable Network. With an emphasis upon performance, but also branching into security, national language, and other issues, the book helps you deliver the most value for your company's investment in Oracle Database technologies.

Related Titles

This book is an anthology of effective database management techniques representing the collective wisdom of the OakTable Network. With an emphasis upon performancebut also branching into security, national language, and other issuesthe book helps you deliver the most value for your companys investment in Oracle Database technologies. Youll 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 youll 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 practicesand especially repeatable and predictable practicesin their daily work.

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 RUNTIME_MEM NUMBER FIRST_LOAD_TIME VARCHAR2(76) APPLICATION_WAIT_TIME NUMBER CONCURRENCY_WAIT_TIME NUMBER CLUSTER_WAIT_TIME NUMBER USER_IO_WAIT_TIME NUMBER PLSQL_EXEC_TIME NUMBER JAVA_EXEC_TIME NUMBER CPU_TIME NUMBER ELAPSED_TIME NUMBER LAST_LOAD_TIME VARCHAR2(76) LAST_ACTIVE_TIME DATE

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:

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".