dba_advisor_findings procedure

Free Oracle Tips

HTML Text

Home
E-mail Us
Oracle Articles

Oracle Training
Oracle News
Oracle Forum
Class Catalog

Our Staff
Our Prices
Help Wanted!

Remote DBA
Oracle Tuning
Emergency 911
RAC Support
Apps Support
Analysis
Design
Implementation
Oracle Support

SQL Tuning
Security
UNIX
Oracle UNIX
Linux
Oracle Linux
Monitoring
Remote help
Remote plans
Remote services
Oracle C++
Oracle Java
Apache
JDeveloper
App Server
Applications
Oracle Forms
Oracle Portal
11i Upgrades
SQL Server
Oracle Concepts
HTML-DB Tips
Software Help
Remote Help
Development
Implementation

Financials Training
Oracle 11i
Oracle Apps 11i
Oracle Workflow
Oracle AR 11i Class
Oracle AP 11i class
Oracle GL 11i class
Oracle HR 11i class
Oracle FA 11i class
11i Project Mgt
11i procurement
11i collections

Oracle Posters
Oracle Books
Oracle Tuning Book
Oracle RAC Book
Oracle Security
Easy Oracle Books
Oracle Scripts
SQL Server DBA
SQL Design Patterns
Ion
Excel-DB

BC Oracle News

Rednecks!
Dress code
Arabian Stallion
Burleson Arabians
Guide Horses
Don Burleson Blog
Golf & Travel

Privacy Policy

dba_advisor_findings procedure

Structure of dba_advisor_findings

The task_id field can be used to gather more information about a specific task. These findings can be in one of four categories as shows in the type field:

Problem
Symptom
Error
Information

These categorizations provide a triage area to look at the PROBLEM items first. These are the items where the type is set to the string PROBLEM. A DBA allowing ADDM to advise on database performance issues will, ideally, work their way down to review and address the INFORMATION items.

Step 1: Create a tuning task

You have a SQL statement (perhaps from a packaged application, and you may not be able to change the code).

create_tuning_task (
sql_text => ‘select * from emp_history
SEE CODE DEPOT FOR FULL SCRIPT
bind_list =>
sql_binds(anydata.ConvertNumber(100)),
usern_name => ‘scott’,
scope => ‘comprehensive’,
time_limit => 60,
task_name => ‘bad_sql’,
description => ‘sql that performs poorly’);

Step 2: Execute the tuning task

Execute_tuning_task (
Task_name => ‘bad_sql’);

The results of this execution have been put into the new catalog tables, and can be seen by querying dba_advisor_% views such as dba_advisor_findings, dba_advisor_recommendations, etc.

Step 3: See the results

set long 10000;
select report_tuning_task (task_name => ‘bad_sql’) from dual;

This will return a complete report of the results, including dba_advisor_findings and recommendations. This report can also be run via OEM

The above text is an excerpt from "Oracle Database 10g New Features: Oracle10g Reference for Advanced Tuning and Administration", by Rampant TechPress. Written by top Oracle experts, this book has a complete online code deport with ready to use scripts.

To get the code instantly, click here:

http://www.rampant-books.com/book_2003_2_oracle10g.htm

Oracle performance Tuning 10g reference poster

Oracle training & performance tuning books