Oracle Performance Report how-to

Question

Hello everyone!
I've got a task to check what is the problem of oracle perofrmance on production server which is 150% percents more powerful then test one.
I've run ADDM report on the server, and that was a result
sing the report name addmrpt_1_2_3.txt
Running the ADDM analysis on the specified pair of snapshots ...
Generating the ADDM report for this analysis ...
          ADDM Report for Task 'TASK_9838'
Analysis Period
AWR snapshot range from 2 to 3.
Time period starts at 10-JUN-13 02.40.53 PM
Time period ends at 10-JUN-13 03.35.54 PM
Analysis Target
Database 'mydb' with DB ID u_dont_neew_this.
Database version 11.2.0.3.0.
ADDM performed an analysis of instance mydb, numbered 1 and hosted at
myhost.
Activity During the Analysis Period
Total database time was 2716 seconds.
The average number of active sessions was .82.
Summary of Findings
   Description         Active Sessions      Recommendations
                       Percent of Activity
1  Top SQL Statements  .8 | 97.38           4
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Findings and Recommendations
Finding 1: Top SQL Statements
Impact is .8 active sessions, 97.38% of total activity.
SQL statements consuming significant database time were found. These
statements offer a good opportunity for performance improvement.
   Recommendation 1: SQL Tuning
   Estimated benefit is .42 active sessions, 51.31% of total activity.
   Action
      Run SQL Tuning Advisor on the SELECT statement with SQL_ID
      "7juu3q1kd9jtg".
      Related Object
         SQL statement with SQL_ID 7juu3q1kd9jtg.
         SELECT A1.C_PORT_KIND, A2.C_FILIAL, A2.C_DEPART FROM Z#PRODUCT A2,
         Z#SIM_LOAN_PORT A1 WHERE A1.ID=:B1 AND A1.ID=A2.ID
   Rationale
      The SQL spent 100% of its database time on CPU, I/O and Cluster waits.
      This part of database time may be improved by the SQL Tuning Advisor.
   Rationale
      Database time for this SQL was divided as follows: 100% for SQL
      execution, 0% for parsing, 0% for PL/SQL execution and 0% for Java
      execution.
   Rationale
      SQL statement with SQL_ID "7juu3q1kd9jtg" was executed 54474 times and
      had an average elapsed time of 0.025 seconds.
   Rationale
      Top level calls to execute the PL/SQL statement with SQL_ID
      "2um3zzd1dhjck" are responsible for 100% of the database time spent on
      the SELECT statement with SQL_ID "7juu3q1kd9jtg".
      Related Object
         SQL statement with SQL_ID 2um3zzd1dhjck.
         BEGIN  IBS.Z$U$28413226.P(:1,:2,:3); END;
as i see there is a problem with some procedure, so that is an info for developers.
But the developers ask me for the resources report. As i know in EM there is a beautiful graphic report with resources usage. I'd like to know if it's possible to check resources usage during the snapshot via sqlplus.
regards,
vs

Answer 1

How do you know that the server is '150%' more powerful than the last one?
I presume you figured that out by performing volumetric tests before moving to the new server so you had a point of reference to use? I'm assuming that you're not just going by the specs of the server itself.
The same applies here: all that you're doing in your OP is showing what the top activity is in the database for that period of time; that might be perfectly normal - during our very heaviest times, ADDM is always whining about how 'the SGA is undersized': I'd led to be sceptical of this suggestion as it's 25Gb, but that's a 'normal' item on the report given how much we batter the database during that particular time slot every day. We expect it, we don't consider it out of the ordinary nor a problem.
ASSUMING YOU HAVE THE LICENSE (I presume that you do as you're using ADDM), use AWR to compare two periods in time and see whether something pops out. Failing that, a read of single AWR report will give you a nice amount of information: where the contention is, what the database is waiting on, etc. If you can't determine a point of reference, then at least give the AWR report a look (especially at the wait events and the SQL statistics sections).
Mark