Professional Documents
Culture Documents
Steve Jun
Init.ora settings
ADDM Views
DBA_ADVISOR_TASKS DBA_ADVISOR_LOG DBA_ADVISOR_RECOMMENDATIONS DBA_ADVISOR_FINDINGS
DBMS_WORKLOAD_REPOSITORY
CREATE_SNAPSHOT MODIFY_SNAPSHOT_SETTINGS Retention (minutes) Interval (minutes) TopNSql (number)
DBMS_ADVISOR.GET_TASK_REPORT
TASK_NAME TYPE LEVEL SECTION OWNER
Sample Output
FINDING 1: 100% impact (18758 seconds) -------------------------------------Hard parses due to an inadequately sized shared pool were consuming significant database time. RECOMMENDATION 1: DB Configuration, 100% benefit (11945 seconds) ACTION: Increase the shared pool size by setting the value of parameter "shared_pool_size" to 1712 M. ADDITIONAL INFORMATION: The value of parameter "shared_pool_size" was "1552 M" during the analysis period. SYMPTOMS THAT LED TO THE FINDING: SYMPTOM: Hard parsing of SQL statements was consuming significant database time. (4.3% impact [405 seconds])
Sample Output
FINDING 2: 4.1% impact (385 seconds) -----------------------------------Session connect and disconnect calls were consuming significant database time. RECOMMENDATION 1: Application Analysis, 4.1% benefit (385 seconds) ACTION: Investigate application logic for possible reduction of connect and disconnect calls. For example, you might use a connection pool scheme in the middle tier.
Sample Output
FINDING 3: 100% impact (58925 seconds) -------------------------------------The throughput of the I/O subsystem was significantly lower than expected. RECOMMENDATION 1: Host Configuration, 100% benefit (58925 seconds) ACTION: Consider increasing the throughput of the I/O subsystem. Oracle's recommended solution is to stripe all data file using the SAME methodology. You might also need to increase the number of disks for better performance. Alternatively, consider using Oracle's Automatic Storage Management solution. RATIONALE: During the analysis period, the average data files' I/O throughput was 4.3 M per second for reads and 22 K per second for writes. The average response time for single block reads was 1 milliseconds.
Sample Output
RECOMMENDATION 2: Host Configuration, 11% benefit (716 seconds) ACTION: The performance of file /oracle/temp/pwcis/temp_03.dbf was significantly worse than other files. If striping all files using the SAME methodology is not possible, consider striping this file over multiple disks. RELEVANT OBJECT: database file "/u01/app/oracle/oradata/temp_3.dbf RATIONALE: The average response time for single block reads for this file was 91 milliseconds.
Sample Output
FINDING 4: 8.2% impact (611 seconds) -----------------------------------SQL statements consuming significant database time were found. RECOMMENDATION 1: SQL Tuning, 3.3% benefit (247 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "5uvtb1633rdxt". RELEVANT OBJECT: SQL statement with SQL_ID 5uvtb1633rdxt and PLAN_HASH 3487490115 SELECT FROM c, d WHERE RATIONALE: SQL statement with SQL_ID "5uvtb1633rdxt" was executed 79 times and had an average elapsed time of 2.6 seconds.
Sample Output
RECOMMENDATION 2: SQL Tuning, 3.2% benefit (240 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "54k7d90u0yzfh". RELEVANT OBJECT: SQL statement with SQL_ID 54k7d90u0yzfh and PLAN_HASH 114702621 SELECT FROM a, b WHERE RATIONALE: SQL statement with SQL_ID "54k7d90u0yzfh" was executed 697 times and had an average elapsed time of 0.32 seconds.
Licensing