Explain message in ADDM report

Hi Experts,
I got some messages from ADDM as
1)23-JAN-09 PROBLEM 7203341 1 Application Analysis
Message : Wait event "SQL*Net more data from client" in wait clas
s "Network" was consuming significant database time.
Command To correct: UNDEFINED
Action Message : Investigate the cause for high "SQL*Net more data from
client" waits. Refer to Oracle's "Database Reference" for the description o
f this wait event.
2)
23-JAN-09 PROBLEM 7689364 2 Host Configuration
Message : The throughput of the I/O subsystem was significantly l
ower than expected.
Command To correct: UNDEFINED
Action Message : The performance of file G:\ORACLE\ORADATA\SALE\STREA
MS_TBS02.DBF was significantly worse than other files. If striping all file
s using the SAME methodology is not possible, consider striping this file o
ver multiple disks
07-JAN-09 PROBLEM 9025281 2 Host Configuration
Message : Waits on event "log file sync" while performing COMMIT
and ROLLBACK operations were consuming significant database time.
Command To correct: UNDEFINED
Action Message : Investigate the possibility of improving the performanc
e of I/O to the online redo log files
4)
16-JAN-09 PROBLEM 37542906 0 Segment Tuning
Message : Individual database segments responsible for significan
t user I/O wait were found.
Command To correct: UNDEFINED
Action Message : Investigate application logic involving I/O on TABLE "SALE_POSITION" with object id 93135.
plus as
PLAN_HASH 1025094865 INSERT /*+ BYPASS_RECURSIVE_CHECK */ INTO "SALE"."SALE_LAST_INPUT_CHANGE" SELECT LAST.ID, LAST.SENT_DATE_UTC, IO.IO_NUM, IO.STATUS FROM SALE_LAST_INPUT_BASE LAST, BASE BASE, POSITION POSITION, IO_STATUS IO WHERE POSITION.MSG_ID=BASE.MSG_ID AND LAST.PRDL_ID=BASE.ID SQL statement with SQL_ID "4s23dt29b0nx9" was executed 1 times and had an average elapsed time of 218 seconds.
Based on my understand,
Msg 1 means that have lots of application need to put into DB--waiting for
Msg 2 means i need to add more disk to hold datafile for that tablespace.
Msg 3 means that there are big/large transaction with commmit block.
Msg 4 means that lot of data insert inot database without commit;
From alert, I also got message as
*** ACTION NAME:(GATHER_STATS_JOB) 2009-01-27 22:05:55.754
*** MODULE NAME:(DBMS_SCHEDULER) 2009-01-27 22:05:55.754
*** SERVICE NAME:(SYS$USERS) 2009-01-27 22:05:55.754
*** SESSION ID:(303.6683) 2009-01-27 22:05:55.754
ORA-00054: resource busy and acquire with NOWAIT specified
*** 2009-01-27 22:05:55.848
GATHER_STATS_JOB: GATHER_TABLE_STATS('"SALE"','"SALE_LAST_INPUT_CHANGE"','""', ...)
ORA-00054: resource busy and acquire with NOWAIT specified
Plz help me to correct above message.
Thanks,
Jim

Hi,
AWR: Automatic Workload Repository
oracle take every 60 minutes a snapshot of statistic in memory and after analysed by ADDM ( automatic database diagnostic monitor) default option, but you can change every 10 minutes or ...
http://www.oracle-base.com/articles/10g/AutomaticWorkloadRepository10g.php
http://www.datadisk.co.uk/html_docs/oracle/addm.htm
http://www.rampant-books.com/t_andert_38_addm_awr_db.htm
http://www.remote-dba.net/oracle_10g_new_features/db_management.htm
http://www.sc.ehu.es/siwebso/KZCC/Oracle_10g_Documentacion/server.101/b10752/diagnsis.htm

Similar Messages

  • Cannot generate AWR/ADDM reports in Oracle 10g

    Hi,
    We are running 10.2.0.3.0 and troublshooted the performance problem for some queries. But when tried to run AWR/ADDM reports from OEM and got the following messages:
    Insufficient Data in Interval. For displaying data on this page, two historical snapshots are needed. Make sure that two snapshots are present in the target database instance. In addition modify the interval so that it is contained within two available snapshots
    I checked the scheduled jobs in this DB,
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - 64bit Production
    With the Partitioning, Real Application Clusters, Oracle Label Security and Data Mining options
    SQL> select JOB_NAME from dba_scheduler_jobs;
    JOB_NAME
    PURGE_LOG
    FGR$AUTOPURGE_JOB
    GATHER_STATS_JOB
    AUTO_SPACE_ADVISOR_JOB
    Has anyone anyidea why AWR/ADDM reports cannot be run? Thanks
    Liz

    Hi,
    If you want you can execute snapshot at your required time as suggested by people.
    However Oracle 10g by default take snap at every one hour.
    To check
    select snap_id, to_char(BEGIN_INTERVAL_TIME,'DD-MON-YYYY HH24:MI') BEGIN_INTERVAL_TIME,
    to_char(END_INTERVAL_TIME,'DD-MON-YYYY HH24:MI') END_INTERVAL_TIME
    from dba_hist_snapshot
    You can generate AWR Report by executing following SQL, Connect as SYS
    SQL> @$ORACLE_HOME/rdbms/admin/awrrpt.sql
    Input required details it asks, you can get AWR report in HTML or text format.
    ADDM Report:
    @$ORACLE_HOME/rdbms/admin/addmrpt.sql

  • Query regarding the ADDM Report

    Hi All,
    My DB performance was quite slow during the last weekend because we had a major data load job and dbms_stats.gather_schema_stats jobs running simultaneously. So, we got an ADDM report generated for these 2 days and from that i could extract 2 things:
    1. The performance was slow because the dbms_stats.gather_schema_stats job was running simultaneoulsy on it.
    2. I could see that some of the SELECT queries on the tables in the schema got executed 145445335, 35, 30 and 20 times repeatedly on the DB. Now this leaves me shocked. Can anyone possibly explain the reason behind it? Was it because a gather_schema_stats was also running on the DB? But how would a select be affected by it? Would it be because it had a exclusive locks on those DB objects during the time it was running?
    Kindly suggest.
    Thanks in advance.

    Hi,
    Thanks for your response.
    No, i cannot see any of the terms like library cache locks and library cache pins with those SQL statements. The only things is see is:
    RECOMMENDATION 1: SQL Tuning, 15% benefit (28820 seconds)
    ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
    "725bgkkhqs73v".
    RELEVANT OBJECT: SQL statement with SQL_ID 725bgkkhqs73v and
    PLAN_HASH 2688602638
    SELECT column1 from table1;
    ACTION: Investigate the SQL statement with SQL_ID "725bgkkhqs73v" for
    possible performance improvements.
    RELEVANT OBJECT: SQL statement with SQL_ID 725bgkkhqs73v and
    PLAN_HASH 2688602638
    RATIONALE: SQL statement with SQL_ID "725bgkkhqs73v" was executed 32
    times and had an average elapsed time of 900 seconds.
    Also, my DB is 10.2.0.3.0 and OS is HP-UNX B.11.23.

  • Explain plan in AWR report?

    Is there any way to generate the explain plan in AWR report?Is it possible to generate the explain plan in AWR?
    Pandu

    Hi,
    AWR: Automatic Workload Repository
    oracle take every 60 minutes a snapshot of statistic in memory and after analysed by ADDM ( automatic database diagnostic monitor) default option, but you can change every 10 minutes or ...
    http://www.oracle-base.com/articles/10g/AutomaticWorkloadRepository10g.php
    http://www.datadisk.co.uk/html_docs/oracle/addm.htm
    http://www.rampant-books.com/t_andert_38_addm_awr_db.htm
    http://www.remote-dba.net/oracle_10g_new_features/db_management.htm
    http://www.sc.ehu.es/siwebso/KZCC/Oracle_10g_Documentacion/server.101/b10752/diagnsis.htm

  • High SQL version count and low executions from ADDM Report!!

    Hi, all.
    I am reading an ADDM Report.
    I found something strange.
    In the "SQL ordered by Version Count" section,
    an applicaion sql statement has the value of 45 Version count
    but has the value of 1 Executions. The time interval is one hour.
    The database has only one applicaion user,
    and thus all sessions connect to the same user.
    What does "45 version count" mean??
    The application is using bind variables.
    How can I reduce this number??
    I am hitting "library cache lock" wait event from time to time.
    Thanks and Regards.
    Message was edited by:
    user507290
    Message was edited by:
    user507290
    Message was edited by:
    user507290

    You could get a high version count if the bind variables are character type and allow large variations in length, see:
    http://jonathanlewis.wordpress.com/2007/01/05/bind-variables/
    The oddity of lots of versions with only one execution could be an unlucky timing thing relating to cursor invalidation - the child cursors can be left trailing with zero'ed statistics rather than being cleared out when they should be.
    Problems with library cache lock can be a consequence of large numbers of versions - simply because many people want, and may have to create, different child cursors for the same statement at the same time. (However, you've already received some comments about RAC and gathering stats which can be an underlying cause of that issue).
    Looking at it from a different angle, are there any global temporary tables involved, and if so are they 'on commit preserve rows', and Is this 10.1 or 10.2 ?
    Regards
    Jonathan Lewis
    http://jonathanlewis.wordpress.com
    http://www.jlcomp.demon.co.uk

  • Performance issue in DB need help with analysing this ADDM report

    Hi,
    My environment:
    Os: RHEL5U3 / 11.1.0.7 64 bit / R12.1.1 64 bit
    Issue:
    Few days are am facing serious of performance problem in our Production instance. Normally the issue will occur 5 to 10 minutes occasionally per day. At the time of issue we not able to access the EBS application its taking time to load. But backend all the oracle, listener and apps services are up and running. No locks at table and session level. Cpu and memory usage is normal.
    We have monitored using "Enterprise Manager" for this issue and we found the wait session present more in Active session tab. At this time EBS application is not able access its loading too time. After some time the in Active session tab the wait session came normal and when we try to access the EBS application its working fine.
    We try to find the cause of the issue by running addm report. But am not able to understand what its says. Kindly suggests me
    ADDM Report for Task 'TASK_42656'
    Analysis Period
    AWR snapshot range from 14754 to 14755.
    Time period starts at 17-APR-12 11.00.22 AM
    Time period ends at 17-APR-12 12.00.33 PM
    Analysis Target
    Database 'PRD' with DB ID 1789440879.
    Database version 11.1.0.7.0.
    ADDM performed an analysis of instance PRD, numbered 1 and hosted at
    advgrpdb.advgroup.ae.
    Activity During the Analysis Period
    Total database time was 18674 seconds.
    The average number of active sessions was 5.17.
    Summary of Findings
    Description Active Sessions Recommendations
    Percent of Activity
    1 Top SQL by DB Time 3.43 | 66.33 5
    2 Buffer Busy 2.52 | 48.81 5
    3 Buffer Busy 1.39 | 26.81 2
    4 Log File Switches .91 | 17.56 1
    5 Buffer Busy .56 | 10.87 2
    6 Undersized SGA .38 | 7.37 1
    7 Commits and Rollbacks .28 | 5.42 1
    8 Undo I/O .18 | 3.53 0
    9 CPU Usage .13 | 2.57 1
    10 Top SQL By I/O .11 | 2.21 1
    Findings and Recommendations
    Finding 1: Top SQL by DB Time
    Impact is 3.43 active sessions, 66.33% of total activity.
    SQL statements consuming significant database time were found.
    Recommendation 1: SQL Tuning
    Estimated benefit is 1.59 active sessions, 30.8% of total activity.
    Action
    Investigate the SQL statement with SQL_ID "a49xsqhv0h31b" for possible
    performance improvements.
    Related Object
    SQL statement with SQL_ID a49xsqhv0h31b.
    SELECT R.Conc_Login_Id, R.Request_Id, R.Phase_Code, R.Status_Code,
    P.Application_ID, P.Concurrent_Program_ID, P.Concurrent_Program_Name,
    R.Enable_Trace, R.Restart, DECODE(R.Increment_Dates, 'Y', 'Y', 'N'),
    R.NLS_Compliant, R.OUTPUT_FILE_TYPE, E.Executable_Name,
    E.Execution_File_Name, A2.Basepath, DECODE(R.Stale, 'Y', 'C',
    P.Execution_Method_Code), P.Print_Flag, P.Execution_Options,
    DECODE(P.Srs_Flag, 'Y', 'Y', 'Q', 'Y', 'N'), P.Argument_Method_Code,
    R.Print_Style, R.Argument_Input_Method_Code, R.Queue_Method_Code,
    R.Responsibility_ID, R.Responsibility_Application_ID, R.Requested_By,
    R.Number_Of_Copies, R.Save_Output_Flag, R.Printer, R.Print_Group,
    R.Priority, U.User_Name, O.Oracle_Username,
    O.Encrypted_Oracle_Password, R.Cd_Id, A.Basepath,
    A.Application_Short_Name, TO_CHAR(R.Requested_Start_Date,'YYYY/MM/DD
    HH24:MI:SS'), R.Nls_Language, R.Nls_Territory,
    R.Nls_Numeric_Characters, DECODE(R.Parent_Request_ID, NULL, 0,
    R.Parent_Request_ID), R.Priority_Request_ID, R.Single_Thread_Flag,
    R.Has_Sub_Request, R.Is_Sub_Request, R.Req_Information,
    R.Description, R.Resubmit_Time, TO_CHAR(R.Resubmit_Interval),
    R.Resubmit_Interval_Type_Code, R.Resubmit_Interval_Unit_Code,
    TO_CHAR(R.Resubmit_End_Date,'YYYY/MM/DD HH24:MI:SS'),
    Decode(E.Execution_File_Name, NULL, 'N', Decode(E.Subroutine_Name,
    NULL, Decode(E.Execution_Method_Code, 'I', 'Y', 'J', 'Y', 'N'),
    'Y')), R.Argument1, R.Argument2, R.Argument3, R.Argument4,
    R.Argument5, R.Argument6, R.Argument7, R.Argument8, R.Argument9,
    R.Argument10, R.Argument11, R.Argument12, R.Argument13, R.Argument14,
    R.Argument15, R.Argument16, R.Argument17, R.Argument18, R.Argument19,
    R.Argument20, R.Argument21, R.Argument22, R.Argument23, R.Argument24,
    R.Argument25, X.Argument26, X.Argument27, X.Argument28, X.Argument29,
    X.Argument30, X.Argument31, X.Argument32, X.Argument33, X.Argument34,
    X.Argument35, X.Argument36, X.Argument37, X.Argument38, X.Argument39,
    X.Argument40, X.Argument41, X.Argument42, X.Argument43, X.Argument44,
    X.Argument45, X.Argument46, X.Argument47, X.Argument48, X.Argument49,
    X.Argument50, X.Argument51, X.Argument52, X.Argument53, X.Argument54,
    X.Argument55, X.Argument56, X.Argument57, X.Argument58, X.Argument59,
    X.Argument60, X.Argument61, X.Argument62, X.Argument63, X.Argument64,
    X.Argument65, X.Argument66, X.Argument67, X.Argument68, X.Argument69,
    X.Argument70, X.Argument71, X.Argument72, X.Argument73, X.Argument74,
    X.Argument75, X.Argument76, X.Argument77, X.Argument78, X.Argument79,
    X.Argument80, X.Argument81, X.Argument82, X.Argument83, X.Argument84,
    X.Argument85, X.Argument86, X.Argument87, X.Argument88, X.Argument89,
    X.Argument90, X.Argument91, X.Argument92, X.Argument93, X.Argument94,
    X.Argument95, X.Argument96, X.Argument97, X.Argument98, X.Argument99,
    X.Argument100, R.number_of_arguments, C.CD_Name,
    NVL(R.Security_Group_ID, 0), NVL(R.org_id, 0) FROM
    fnd_concurrent_requests R, fnd_concurrent_programs P, fnd_application
    A, fnd_user U, fnd_oracle_userid O, fnd_conflicts_domain C,
    fnd_concurrent_queues Q, fnd_application A2, fnd_executables E,
    fnd_conc_request_arguments X WHERE R.Status_code = 'I' And
    ((R.OPS_INSTANCE is null) or (R.OPS_INSTANCE = -1) or
    (R.OPS_INSTANCE =
    decode(:dcp_on,1,FND_CONC_GLOBAL.OPS_INST_NUM,R.OPS_INSTANCE))) And
    R.Request_ID = X.Request_ID(+) And R.Program_Application_Id =
    P.Application_Id(+) And R.Concurrent_Program_Id =
    P.Concurrent_Program_Id(+) And R.Program_Application_Id =
    A.Application_Id(+) And P.Executable_Application_Id =
    E.Application_Id(+) And P.Executable_Id =
    E.Executable_Id(+) And P.Executable_Application_Id =
    A2.Application_Id(+) And R.Requested_By = U.User_Id(+) And R.Cd_Id
    = C.Cd_Id(+) And R.Oracle_Id = O.Oracle_Id(+) And Q.Application_Id =
    :q_applid And Q.Concurrent_Queue_Id = :queue_id And (P.Enabled_Flag
    is NULL OR P.Enabled_Flag = 'Y') And R.Hold_Flag = 'N' And
    R.Requested_Start_Date <= Sysdate And ( R.Enforce_Seriality_Flag =
    'N' OR ( C.RunAlone_Flag = P.Run_Alone_Flag And (P.Run_Alone_Flag =
    'N' OR Not Exists (Select Null From Fnd_Concurrent_Requests Sr
    Where Sr.Status_Code In ('R', 'T') And Sr.Enforce_Seriality_Flag =
    'Y' And Sr.CD_id = C.CD_Id)))) And Q.Running_Processes <=
    Q.Max_Processes And R.Rowid = :reqname And
    ((P.Execution_Method_Code != 'S' OR
    (R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) IN
    ((0,98),(0,100),(0,31721),(0,31722),(0,31757))) AND
    ((R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) NOT IN
    ((510,40112),(510,40113),(510,41497),(510,41498),(530,41859),(530,418
    60),(535,41492),(535,41493),(535,41494)))) FOR UPDATE OF
    R.status_code NoWait
    Rationale
    SQL statement with SQL_ID "a49xsqhv0h31b" was executed 4686 times and
    had an average elapsed time of 1.2 seconds.
    Rationale
    Waiting for event "buffer busy waits" in wait class "Concurrency"
    accounted for 85% of the database time spent in processing the SQL
    statement with SQL_ID "a49xsqhv0h31b".
    Rationale
    Waiting for event "log file switch (checkpoint incomplete)" in wait
    class "Configuration" accounted for 9% of the database time spent in
    processing the SQL statement with SQL_ID "a49xsqhv0h31b".
    Recommendation 3: SQL Tuning
    Estimated benefit is .56 active sessions, 10.91% of total activity.
    Action
    Investigate the SQL statement with SQL_ID "5d7957yktf3nn" for possible
    performance improvements.
    Related Object
    SQL statement with SQL_ID 5d7957yktf3nn.
    UPDATE ICX_SESSIONS SET TIME_OUT = :B2 WHERE SESSION_ID = :B1
    Rationale
    SQL statement with SQL_ID "5d7957yktf3nn" was executed 266 times and had
    an average elapsed time of 7.6 seconds.
    Rationale
    Waiting for event "buffer busy waits" in wait class "Concurrency"
    accounted for 86% of the database time spent in processing the SQL
    statement with SQL_ID "5d7957yktf3nn".
    Rationale
    Waiting for event "log file switch (checkpoint incomplete)" in wait
    class "Configuration" accounted for 7% of the database time spent in
    processing the SQL statement with SQL_ID "5d7957yktf3nn".
    Finding 2: Buffer Busy
    Impact is 2.52 active sessions, 48.81% of total activity.
    Read and write contention on database blocks was consuming significant
    database time.
    Recommendation 1: Application Analysis
    Estimated benefit is 1.42 active sessions, 27.44% of total activity.
    Action
    Trace the cause of object contention due to SELECT statements in the
    application using the information provided.
    Related Object
    Database object with ID 34562.
    Rationale
    The SELECT statement with SQL_ID "a49xsqhv0h31b" was significantly
    affected by "buffer busy" waits.
    Related Object
    SQL statement with SQL_ID a49xsqhv0h31b.
    SELECT R.Conc_Login_Id, R.Request_Id, R.Phase_Code, R.Status_Code,
    P.Application_ID, P.Concurrent_Program_ID, P.Concurrent_Program_Name,
    R.Enable_Trace, R.Restart, DECODE(R.Increment_Dates, 'Y', 'Y', 'N'),
    R.NLS_Compliant, R.OUTPUT_FILE_TYPE, E.Executable_Name,
    E.Execution_File_Name, A2.Basepath, DECODE(R.Stale, 'Y', 'C',
    P.Execution_Method_Code), P.Print_Flag, P.Execution_Options,
    DECODE(P.Srs_Flag, 'Y', 'Y', 'Q', 'Y', 'N'), P.Argument_Method_Code,
    R.Print_Style, R.Argument_Input_Method_Code, R.Queue_Method_Code,
    R.Responsibility_ID, R.Responsibility_Application_ID, R.Requested_By,
    R.Number_Of_Copies, R.Save_Output_Flag, R.Printer, R.Print_Group,
    R.Priority, U.User_Name, O.Oracle_Username,
    O.Encrypted_Oracle_Password, R.Cd_Id, A.Basepath,
    A.Application_Short_Name, TO_CHAR(R.Requested_Start_Date,'YYYY/MM/DD
    HH24:MI:SS'), R.Nls_Language, R.Nls_Territory,
    R.Nls_Numeric_Characters, DECODE(R.Parent_Request_ID, NULL, 0,
    R.Parent_Request_ID), R.Priority_Request_ID, R.Single_Thread_Flag,
    R.Has_Sub_Request, R.Is_Sub_Request, R.Req_Information,
    R.Description, R.Resubmit_Time, TO_CHAR(R.Resubmit_Interval),
    R.Resubmit_Interval_Type_Code, R.Resubmit_Interval_Unit_Code,
    TO_CHAR(R.Resubmit_End_Date,'YYYY/MM/DD HH24:MI:SS'),
    Decode(E.Execution_File_Name, NULL, 'N', Decode(E.Subroutine_Name,
    NULL, Decode(E.Execution_Method_Code, 'I', 'Y', 'J', 'Y', 'N'),
    'Y')), R.Argument1, R.Argument2, R.Argument3, R.Argument4,
    R.Argument5, R.Argument6, R.Argument7, R.Argument8, R.Argument9,
    R.Argument10, R.Argument11, R.Argument12, R.Argument13, R.Argument14,
    R.Argument15, R.Argument16, R.Argument17, R.Argument18, R.Argument19,
    R.Argument20, R.Argument21, R.Argument22, R.Argument23, R.Argument24,
    R.Argument25, X.Argument26, X.Argument27, X.Argument28, X.Argument29,
    X.Argument30, X.Argument31, X.Argument32, X.Argument33, X.Argument34,
    X.Argument35, X.Argument36, X.Argument37, X.Argument38, X.Argument39,
    X.Argument40, X.Argument41, X.Argument42, X.Argument43, X.Argument44,
    X.Argument45, X.Argument46, X.Argument47, X.Argument48, X.Argument49,
    X.Argument50, X.Argument51, X.Argument52, X.Argument53, X.Argument54,
    X.Argument55, X.Argument56, X.Argument57, X.Argument58, X.Argument59,
    X.Argument60, X.Argument61, X.Argument62, X.Argument63, X.Argument64,
    X.Argument65, X.Argument66, X.Argument67, X.Argument68, X.Argument69,
    X.Argument70, X.Argument71, X.Argument72, X.Argument73, X.Argument74,
    X.Argument75, X.Argument76, X.Argument77, X.Argument78, X.Argument79,
    X.Argument80, X.Argument81, X.Argument82, X.Argument83, X.Argument84,
    X.Argument85, X.Argument86, X.Argument87, X.Argument88, X.Argument89,
    X.Argument90, X.Argument91, X.Argument92, X.Argument93, X.Argument94,
    X.Argument95, X.Argument96, X.Argument97, X.Argument98, X.Argument99,
    X.Argument100, R.number_of_arguments, C.CD_Name,
    NVL(R.Security_Group_ID, 0), NVL(R.org_id, 0) FROM
    fnd_concurrent_requests R, fnd_concurrent_programs P, fnd_application
    A, fnd_user U, fnd_oracle_userid O, fnd_conflicts_domain C,
    fnd_concurrent_queues Q, fnd_application A2, fnd_executables E,
    fnd_conc_request_arguments X WHERE R.Status_code = 'I' And
    ((R.OPS_INSTANCE is null) or (R.OPS_INSTANCE = -1) or
    (R.OPS_INSTANCE =
    decode(:dcp_on,1,FND_CONC_GLOBAL.OPS_INST_NUM,R.OPS_INSTANCE))) And
    R.Request_ID = X.Request_ID(+) And R.Program_Application_Id =
    P.Application_Id(+) And R.Concurrent_Program_Id =
    P.Concurrent_Program_Id(+) And R.Program_Application_Id =
    A.Application_Id(+) And P.Executable_Application_Id =
    E.Application_Id(+) And P.Executable_Id =
    E.Executable_Id(+) And P.Executable_Application_Id =
    A2.Application_Id(+) And R.Requested_By = U.User_Id(+) And R.Cd_Id
    = C.Cd_Id(+) And R.Oracle_Id = O.Oracle_Id(+) And Q.Application_Id =
    :q_applid And Q.Concurrent_Queue_Id = :queue_id And (P.Enabled_Flag
    is NULL OR P.Enabled_Flag = 'Y') And R.Hold_Flag = 'N' And
    R.Requested_Start_Date <= Sysdate And ( R.Enforce_Seriality_Flag =
    'N' OR ( C.RunAlone_Flag = P.Run_Alone_Flag And (P.Run_Alone_Flag =
    'N' OR Not Exists (Select Null From Fnd_Concurrent_Requests Sr
    Where Sr.Status_Code In ('R', 'T') And Sr.Enforce_Seriality_Flag =
    'Y' And Sr.CD_id = C.CD_Id)))) And Q.Running_Processes <=
    Q.Max_Processes And R.Rowid = :reqname And
    ((P.Execution_Method_Code != 'S' OR
    (R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) IN
    ((0,98),(0,100),(0,31721),(0,31722),(0,31757))) AND
    ((R.PROGRAM_APPLICATION_ID,R.CONCURRENT_PROGRAM_ID) NOT IN
    ((510,40112),(510,40113),(510,41497),(510,41498),(530,41859),(530,418
    60),(535,41492),(535,41493),(535,41494)))) FOR UPDATE OF
    R.status_code NoWait
    UPDATE ICX_SESSIONS SET LAST_CONNECT = SYSDATE WHERE SESSION_ID = :B1
    Recommendation 1: Schema Changes
    Estimated benefit is .03 active sessions, .62% of total activity.
    Action
    Consider rebuilding the TABLE "APPLSYS.FND_LOGIN_RESP_FORMS" with object
    ID 34651 using a higher value for PCTFREE.
    Related Object
    Database object with ID 34651.
    Rationale
    The UPDATE statement with SQL_ID "cqc5crhxxt36t" was significantly
    affected by "buffer busy" waits.
    Related Object
    SQL statement with SQL_ID cqc5crhxxt36t.
    UPDATE FND_LOGIN_RESP_FORMS FLRF SET END_TIME = SYSDATE WHERE
    FLRF.LOGIN_ID = :B2 AND FLRF.LOGIN_RESP_ID = :B1 AND FLRF.END_TIME IS
    NULL AND (FLRF.FORM_ID, FLRF.FORM_APPL_ID) = (SELECT F.FORM_ID,
    F.APPLICATION_ID FROM FND_FORM F, FND_APPLICATION A WHERE F.FORM_NAME
    = :B4 AND F.APPLICATION_ID = A.APPLICATION_ID AND
    A.APPLICATION_SHORT_NAME = :B3 )
    Symptoms That Led to the Finding:
    Wait class "Concurrency" was consuming significant database time.
    Impact is 2.53 active sessions, 48.87% of total activity.
    Finding 4: Log File Switches
    Impact is .91 active sessions, 17.56% of total activity.
    Log file switch operations were consuming significant database time while
    waiting for checkpoint completion.
    This problem can be caused by use of hot backup mode on tablespaces. DML to
    tablespaces in hot backup mode causes generation of additional redo.
    Recommendation 1: Database Configuration
    Estimated benefit is .91 active sessions, 17.56% of total activity.
    Action
    Verify whether incremental shipping was used for standby databases.
    Symptoms That Led to the Finding:
    Wait class "Configuration" was consuming significant database time.
    Impact is .91 active sessions, 17.63% of total activity.
    Finding 5: Buffer Busy
    Impact is .56 active sessions, 10.87% of total activity.
    A hot data block with concurrent read and write activity was found. The block
    belongs to segment "ICX.ICX_SESSIONS" and is block 243489 in file 36.
    Recommendation 1: Application Analysis
    Estimated benefit is .56 active sessions, 10.87% of total activity.
    Action
    Investigate application logic to find the cause of high concurrent read
    and write activity to the data present in this block.
    Related Object
    Database block with object number 37562, file number 36 and block
    number 243489.
    Rationale
    The SQL statement with SQL_ID "5d7957yktf3nn" spent significant time on
    "buffer busy" waits for the hot block.
    Related Object
    SQL statement with SQL_ID 5d7957yktf3nn.
    UPDATE ICX_SESSIONS SET TIME_OUT = :B2 WHERE SESSION_ID = :B1
    Rationale
    The SQL statement with SQL_ID "326up1aym56dd" spent significant time on
    "buffer busy" waits for the hot block.
    Related Object
    SQL statement with SQL_ID 326up1aym56dd.
    UPDATE ICX_SESSIONS SET LAST_CONNECT = SYSDATE WHERE SESSION_ID = :B1
    Recommendation 2: Schema Changes
    Estimated benefit is .56 active sessions, 10.87% of total activity.
    Action
    Consider rebuilding the TABLE "ICX.ICX_SESSIONS" with object ID 37562
    using a higher value for PCTFREE.
    Related Object
    Database object with ID 37562.
    Symptoms That Led to the Finding:
    Wait class "Concurrency" was consuming significant database time.
    Impact is 2.53 active sessions, 48.87% of total activity.
    Finding 6: Undersized SGA
    Impact is .38 active sessions, 7.37% of total activity.
    The SGA was inadequately sized, causing additional I/O or hard parses.
    The value of parameter "sga_target" was "4096 M" during the analysis period.
    Recommendation 1: Database Configuration
    Estimated benefit is .12 active sessions, 2.33% of total activity.
    Action
    Increase the size of the SGA by setting the parameter "sga_target" to
    4608 M.
    Symptoms That Led to the Finding:
    Wait class "User I/O" was consuming significant database time.
    Impact is .7 active sessions, 13.57% of total activity.
    Hard parsing of SQL statements was consuming significant database time.
    Impact is .13 active sessions, 2.51% of total activity.
    Contention for latches related to the shared pool was consuming
    significant database time.
    Impact is 0 active sessions, .03% of total activity.
    Wait class "Concurrency" was consuming significant database time.
    Impact is 2.53 active sessions, 48.87% of total activity.
    Finding 7: Commits and Rollbacks
    Impact is .28 active sessions, 5.42% of total activity.
    Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
    were consuming significant database time.
    Recommendation 1: Host Configuration
    Estimated benefit is .28 active sessions, 5.42% of total activity.
    Action
    Investigate the possibility of improving the performance of I/O to the
    online redo log files.
    Rationale
    The average size of writes to the online redo log files was 163 K and
    the average time per write was 68 milliseconds.
    Symptoms That Led to the Finding:
    Wait class "Commit" was consuming significant database time.
    Impact is .28 active sessions, 5.42% of total activity.
    Finding 8: Undo I/O
    Impact is .18 active sessions, 3.53% of total activity.
    Undo I/O was a significant portion (26%) of the total database I/O.
    No recommendations are available.
    Symptoms That Led to the Finding:
    The throughput of the I/O subsystem was significantly lower than
    expected.
    Impact is .08 active sessions, 1.46% of total activity.
    Wait class "User I/O" was consuming significant database time.
    Impact is .7 active sessions, 13.57% of total activity.
    Finding 9: CPU Usage
    Impact is .13 active sessions, 2.57% of total activity.
    Time spent on the CPU by the instance was responsible for a substantial part
    of database time.
    Recommendation 1: SQL Tuning
    Estimated benefit is .13 active sessions, 2.57% of total activity.
    Finding 10: Top SQL By I/O
    Impact is .11 active sessions, 2.21% of total activity.
    Individual SQL statements responsible for significant user I/O wait were
    found.
    Recommendation 1: SQL Tuning
    Estimated benefit is .11 active sessions, 2.22% of total activity.
    Action
    Run SQL Tuning Advisor on the SQL statement with SQL_ID "b3pnc5yctv2z5".
    Related Object
    SQL statement with SQL_ID b3pnc5yctv2z5.
    INSERT INTO ZX_TRANSACTION_LINES_GT( APPLICATION_ID ,ENTITY_CODE
    ,EVENT_CLASS_CODE ,TRX_ID ,TRX_LEVEL_TYPE ,TRX_LINE_ID ,LINE_CLASS
    ,LINE_LEVEL_ACTION ,TRX_LINE_TYPE ,TRX_LINE_DATE
    ,LINE_AMT_INCLUDES_TAX_FLAG ,LINE_AMT ,TRX_LINE_QUANTITY ,UNIT_PRICE
    ,PRODUCT_ID ,PRODUCT_ORG_ID ,UOM_CODE ,PRODUCT_CODE ,SHIP_TO_PARTY_ID
    ,SHIP_FROM_PARTY_ID ,BILL_TO_PARTY_ID ,BILL_FROM_PARTY_ID
    ,SHIP_FROM_PARTY_SITE_ID ,BILL_FROM_PARTY_SITE_ID
    ,SHIP_TO_LOCATION_ID ,SHIP_FROM_LOCATION_ID ,BILL_TO_LOCATION_ID
    ,SHIP_THIRD_PTY_ACCT_ID ,SHIP_THIRD_PTY_ACCT_SITE_ID ,HISTORICAL_FLAG
    ,TRX_LINE_CURRENCY_CODE ,TRX_LINE_CURRENCY_CONV_DATE
    ,TRX_LINE_CURRENCY_CONV_RATE ,TRX_LINE_CURRENCY_CONV_TYPE
    ,TRX_LINE_MAU ,TRX_LINE_PRECISION ,HISTORICAL_TAX_CODE_ID
    ,TRX_BUSINESS_CATEGORY ,PRODUCT_CATEGORY ,PRODUCT_FISC_CLASSIFICATION
    ,LINE_INTENDED_USE ,PRODUCT_TYPE ,USER_DEFINED_FISC_CLASS
    ,ASSESSABLE_VALUE ,INPUT_TAX_CLASSIFICATION_CODE ,ACCOUNT_CCID
    ,BILL_THIRD_PTY_ACCT_ID ,BILL_THIRD_PTY_ACCT_SITE_ID ,TRX_LINE_NUMBER
    ,TRX_LINE_DESCRIPTION ,PRODUCT_DESCRIPTION ,USER_UPD_DET_FACTORS_FLAG
    ,DEFAULTING_ATTRIBUTE1 ) SELECT :B4 ,:B3 ,:B2
    ,PRL.REQUISITION_HEADER_ID ,:B1 ,PRL.REQUISITION_LINE_ID ,'INVOICE'
    ,NVL(PRL.TAX_ATTRIBUTE_UPDATE_CODE,'UPDATE') ,'ITEM'
    ,NVL(PRL.NEED_BY_DATE, SYSDATE) ,'N' ,NVL(PRL.AMOUNT,
    PRL.UNIT_PRICE*PRL.QUANTITY) ,PRL.QUANTITY ,PRL.UNIT_PRICE
    ,PRL.ITEM_ID ,(SELECT FSP.INVENTORY_ORGANIZATION_ID FROM
    FINANCIALS_SYSTEM_PARAMS_ALL FSP WHERE FSP.ORG_ID=PRL.ORG_ID)
    ,(SELECT MUM.UOM_CODE FROM MTL_UNITS_OF_MEASURE MUM WHERE
    MUM.UNIT_OF_MEASURE=PRL.UNIT_MEAS_LOOKUP_CODE) ,MSIB.SEGMENT1
    ,PRL.DESTINATION_ORGANIZATION_ID ,PV.PARTY_ID ,PRH.ORG_ID
    ,PV.PARTY_ID ,PVS.PARTY_SITE_ID ,PVS.PARTY_SITE_ID
    ,PRL.DELIVER_TO_LOCATION_ID ,(SELECT HZPS.LOCATION_ID FROM
    HZ_PARTY_SITES HZPS WHERE HZPS.PARTY_SITE_ID = PVS.PARTY_SITE_ID)
    ,(SELECT LOCATION_ID FROM HR_ALL_ORGANIZATION_UNITS WHERE
    ORGANIZATION_ID=PRH.ORG_ID) ,PRL.VENDOR_ID ,PRL.VENDOR_SITE_ID ,NULL
    ,NVL(PRL.CURRENCY_CODE, :B9 ) ,NVL2(PRL.CURRENCY_CODE, PRL.RATE_DATE,
    SYSDATE) ,NVL2(PRL.CURRENCY_CODE, PRL.RATE, :B8 )
    ,NVL2(PRL.CURRENCY_CODE, PRL.RATE_TYPE, :B7 )
    ,FC.MINIMUM_ACCOUNTABLE_UNIT ,NVL(FC.PRECISION, 2) ,NULL
    ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
    NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.TRX_BUSINESS_CATEGORY, NULL),
    NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
    NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_CATEGORY, NULL), NULL )
    ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
    NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_FISC_CLASSIFICATION,
    NULL), NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
    NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.LINE_INTENDED_USE, NULL), NULL )
    ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
    NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.PRODUCT_TYPE, NULL), NULL )
    ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
    NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.USER_DEFINED_FISC_CLASS, NULL),
    NULL ) ,DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
    NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.ASSESSABLE_VALUE, NULL), NULL )
    ,DECODE(:B6 , 'REQIMPORT', PRL.TAX_NAME,
    DECODE(PRL.TAX_ATTRIBUTE_UPDATE_CODE, 'CREATE',
    NVL2(PRL.PARENT_REQ_LINE_ID, ZXLDET.INPUT_TAX_CLASSIFICATION_CODE,
    NULL), NULL ) ) ,NVL((SELECT PRD.CODE_COMBINATION_ID FROM
    PO_REQ_DISTRIBUTIONS_ALL PRD WHERE PRD.REQUISITION_LINE_ID =
    PRL.REQUISITION_LINE_ID AND ROWNUM = 1), MSIB.EXPENSE_ACCOUNT )
    ,PV.VENDOR_ID ,PVS.VENDOR_SITE_ID ,PRL.LINE_NUM ,PRL.ITEM_DESCRIPTION
    ,PRL.ITEM_DESCRIPTION ,(SELECT 'Y' FROM DUAL WHERE :B6 = 'REQIMPORT'
    AND PRL.TAX_NAME IS NOT NULL) ,PRL.DESTINATION_ORGANIZATION_ID FROM
    PO_REQUISITION_HEADERS_ALL PRH, PO_REQUISITION_LINES_ALL PRL,
    ZX_LINES_DET_FACTORS ZXLDET, PO_VENDORS PV, PO_VENDOR_SITES_ALL PVS,
    MTL_SYSTEM_ITEMS_B MSIB, FND_CURRENCIES FC WHERE
    PRH.REQUISITION_HEADER_ID = :B5 AND PRH.REQUISITION_HEADER_ID =
    PRL.REQUISITION_HEADER_ID AND ZXLDET.APPLICATION_ID(+) = :B4 AND
    ZXLDET.ENTITY_CODE(+) = :B3 AND ZXLDET.EVENT_CLASS_CODE(+) = :B2 AND
    ZXLDET.TRX_LEVEL_TYPE(+) = :B1 AND ZXLDET.TRX_LINE_ID(+) =
    PRL.PARENT_REQ_LINE_ID AND PV.VENDOR_ID(+) = PRL.VENDOR_ID AND
    PVS.VENDOR_SITE_ID(+) = PRL.VENDOR_SITE_ID AND
    MSIB.INVENTORY_ITEM_ID(+) = PRL.ITEM_ID AND MSIB.ORGANIZATION_ID(+) =
    PRL.ORG_ID AND FC.CURRENCY_CODE(+) = PRL.CURRENCY_CODE AND
    NVL(PRL.MODIFIED_BY_AGENT_FLAG, 'N') = 'N' AND NVL(PRL.CANCEL_FLAG,
    'N') = 'N' AND NVL(PRL.CLOSED_CODE, 'OPEN') <> 'FINALLY CLOSED' AND
    PRL.LINE_LOCATION_ID IS NULL AND PRL.AT_SOURCING_FLAG IS NULL
    Rationale
    SQL statement with SQL_ID "b3pnc5yctv2z5" was executed 3 times and had
    an average elapsed time of 138 seconds.
    Rationale
    Average time spent in User I/O wait events per execution was 137
    seconds.
    Symptoms That Led to the Finding:
    Wait class "User I/O" was consuming significant database time.
    Impact is .7 active sessions, 13.57% of total activity.
    Additional Information
    Miscellaneous Information
    Wait class "Application" was not consuming significant database time.
    Wait class "Network" was not consuming significant database time.
    Session connect and disconnect calls were not consuming significant database
    time.
    The database's maintenance windows were active during 100% of the analysis
    period.
    Regards
    Athish

    Few days are am facing serious of performance problem in our Production instanceFor production issues, please log a SR.
    Was this working before? If yes, any changes been done recently?
    Do you have the statistics collected up to date?
    Please see these docs.
    AutoInvoice Performance Issue When Processing Tax [ID 1059275.1]
    R12 : System Hangs When Attempting To Save Blanket Release After Applying Patch 11817843 [ID 1333336.1]
    Thanks,
    Hussein

  • Display Error Message in BW Report based on Customer Exit Variable

    Hi
    I need to display an error message in the BW report based on the value of a customer exit variable - i was able to do this successfully in BW3.5 using the below code.
      WHEN 'ZUPN'. "Here ZUPN is the customer exit variable
        IF i_step = 1.
          <check for condition -- if successful, variable flag = 1, else variable flag = 0>
          IF flag = 0.
            MESSAGE e157(00). "Error Message
          ENDIF.
        ENDIF.
    I have upgraded my system to BI 7.0 now. Whenever the variable check is not successful, it displays a blank screen instead of the error message in the report. Please advice if we need to change the code and how ??

    Bhanu,
      Thanks for u r reply.This warning message appears every time i execute the report through portal.
    Any idea ?
    Regards
    Mano

  • Details about ADDM report

    Hi,
    I have a small 'orcl' database on my local machine, and I did not perform heavy activity on it. Today and yesterday I performed just some simple queries, like:
    SELECT COUNT(*)
    FROM   products p, (SELECT prod_id, AVG(unit_cost) ac FROM costs GROUP BY prod_id) c
    WHERE  p.prod_id = c.prod_id AND
           p.prod_list_price < 1.15 * c.ac;
    or
    select * from products;
    from the 'sh' schema. Today I run a ADDM report, and this is the result:
    ADDM Report for Task 'TASK_557'
    Analysis Period
    AWR snapshot range from 490 to 494.
    Time period starts at 17-JUL-13 11.00.34 PM
    Time period ends at 18-JUL-13 05.31.00 PM
    Analysis Target
    Database 'ORCL' with DB ID 1346555844.
    Database version 11.2.0.3.0.
    ADDM performed an analysis of instance orcl, numbered 1 and hosted at ROGER.
    Activity During the Analysis Period
    Total database time was 499 seconds.
    The average number of active sessions was .01.
    Summary of Findings
       Description                   
    Active Sessions
    Recommendations
    Percent of Activity
    1  I/O Throughput                
    .01 | 100      
    2
    2  Hard Parse                    
    0 | 29.47      
    0
    3  Hard Parse Due to Sharing Criteria  0 | 8.89       
    1
    4  Row Lock Waits                
    0 | 7.37       
    0
    5  PL/SQL Compilation            
    0 | 4.04       
    1
    6  Unusual "User I/O" Wait Event 
    0 | 4.02       
    1
    7  Commits and Rollbacks         
    0 | 3.08       
    1
    8  Shared Pool Latches           
    0 | 2.78       
    0
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Findings and Recommendations
    Finding 1: I/O Throughput
    Impact is .01 active sessions, 100% of total activity.
    The throughput of the I/O subsystem was significantly lower than expected.
       Recommendation 1: Host Configuration
       Estimated benefit is .01 active sessions, 100% of total activity.
       Action
    Consider increasing the throughput of the I/O subsystem. Oracle's
    recommended solution is to stripe all data files using the SAME
    methodology. You might also need to increase the number of disks for
    better performance.
       Rationale
    During the analysis period, the average data files' I/O throughput was
    1.4 K per second for reads and 1 K per second for writes. The average
    response time for single block reads was 18 milliseconds.
       Recommendation 2: Host Configuration
       Estimated benefit is 0 active sessions, 17.55% of total activity.
       Action
    The performance of some data and temp files was significantly worse than
    others. If striping all files using the SAME methodology is not
    possible, consider striping these file over multiple disks.
       Rationale
    For file D:\ORACLE\APP\ORADATA\ORCL\SYSTEM01.DBF, the average response
    time for single block reads was 168 milliseconds, and the total excess
    I/O wait was 70 seconds.
    Related Object
    Database file
    "D:\ORACLE\APP\ORADATA\ORCL\SYSTEM01.DBF"
       Rationale
    For file D:\ORACLE\APP\ORADATA\ORCL\SYSAUX01.DBF, the average response
    time for single block reads was 16 milliseconds, and the total excess
    I/O wait was 16 seconds.
    Related Object
    Database file
    "D:\ORACLE\APP\ORADATA\ORCL\SYSAUX01.DBF"
       Symptoms That Led to the Finding:
    Wait class "User I/O" was consuming significant database time.
    Impact is 0 active sessions, 30.87% of total activity.
    Finding 2: Hard Parse
    Impact is 0 active sessions, 29.47% of total activity.
    Hard parsing of SQL statements was consuming significant database time.
    Hard parsing SQL statements that encountered parse errors was not consuming
    significant database time.
    Hard parses due to literal usage and cursor invalidation were not consuming
    significant database time.
    The Oracle instance memory (SGA and PGA) was adequately sized.
       No recommendations are available.
    Finding 3: Hard Parse Due to Sharing Criteria
    Impact is 0 active sessions, 8.89% of total activity.
    SQL statements with the same text were not shared because of cursor
    environment mismatch. This resulted in additional hard parses which were
    consuming significant database time.
    Common causes of environment mismatch are session NLS settings, SQL trace
    settings and optimizer parameters.
       Recommendation 1: Application Analysis
       Estimated benefit is 0 active sessions, 8.89% of total activity.
       Action
    Look for top reason for cursor environment mismatch in
    V$SQL_SHARED_CURSOR.
       Symptoms That Led to the Finding:
    Hard parsing of SQL statements was consuming significant database time.
    Impact is 0 active sessions, 29.47% of total activity.
    Finding 4: Row Lock Waits
    Impact is 0 active sessions, 7.37% of total activity.
    SQL statements were found waiting for row lock waits.
       No recommendations are available.
       Symptoms That Led to the Finding:
    Wait class "Application" was consuming significant database time.
    Impact is 0 active sessions, 7.78% of total activity.
    Finding 5: PL/SQL Compilation
    Impact is 0 active sessions, 4.04% of total activity.
    PL/SQL compilation consumed significant database time.
       Recommendation 1: Application Analysis
       Estimated benefit is 0 active sessions, 4.04% of total activity.
       Action
    Investigate the appropriateness of PL/SQL compilation. PL/SQL
    compilation can be caused by DDL on dependent objects.
    Finding 6: Unusual "User I/O" Wait Event
    Impact is 0 active sessions, 4.02% of total activity.
    Wait event "Disk file operations I/O" in wait class "User I/O" was consuming
    significant database time.
       Recommendation 1: Application Analysis
       Estimated benefit is 0 active sessions, 4.02% of total activity.
       Action
    Investigate the cause for high "Disk file operations I/O" waits. Refer
    to Oracle's "Database Reference" for the description of this wait event.
       Symptoms That Led to the Finding:
    Wait class "User I/O" was consuming significant database time.
    Impact is 0 active sessions, 30.87% of total activity.
    Finding 7: Commits and Rollbacks
    Impact is 0 active sessions, 3.08% of total activity.
    Waits on event "log file sync" while performing COMMIT and ROLLBACK operations
    were consuming significant database time.
       Recommendation 1: Host Configuration
       Estimated benefit is 0 active sessions, 3.08% of total activity.
       Action
    Investigate the possibility of improving the performance of I/O to the
    online redo log files.
       Rationale
    The average size of writes to the online redo log files was 21 K and the
    average time per write was 7 milliseconds.
       Rationale
    The total I/O throughput on redo log files was 0 K per second for reads
    and 0.7 K per second for writes.
       Rationale
    The redo log I/O throughput was divided as follows: 0% by RMAN and
    recovery, 100% by Log Writer, 0% by Archiver, 0% by Streams AQ and 0% by
    all other activity.
       Symptoms That Led to the Finding:
    Wait class "Commit" was consuming significant database time.
    Impact is 0 active sessions, 3.08% of total activity.
    Finding 8: Shared Pool Latches
    Impact is 0 active sessions, 2.78% of total activity.
    Contention for latches related to the shared pool was consuming significant
    database time.
    Waits for "library cache load lock" amounted to 1% of database time.
    Waits for "latch: shared pool" amounted to 1% of database time.
       No recommendations are available.
       Symptoms That Led to the Finding:
    Wait class "Concurrency" was consuming significant database time.
    Impact is 0 active sessions, 3.12% of total activity.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Additional Information
    Miscellaneous Information
    Wait class "Configuration" was not consuming significant database time.
    CPU was not a bottleneck for the instance.
    Wait class "Network" was not consuming significant database time.
    Session connect and disconnect calls were not consuming significant database
    time.
    The database's maintenance windows were active during 94% of the analysis
    period.
    Being a small local database, my question is: do I really need to do something? For example at Finding 5: PL/SQL Compilation, what I really need to do? Or ar Finding 1: I/O Throughput
    Thanks.

    Hi,
    Mainly in ADDM you can consider
    Recommendation
    Estimated benefit
    You have generated the report for ~18 hr time interval.
    for test/local  you can ignore this.

  • Error in generating ADDM Report(Oracle 11g 64 bit EE on linux RHEL 5)

    I collected .dmp file from production using awrextr.sql and imported in our development side using awrload.sql .
    I am able to generate awr snapshots report out of it without any trouble.
    But When I try to generate addm report using addmrpti.sql I am facing following error(Please see output pasted below)
    Specify the Report Name
    ~~~~~~~~~~~~~~~~~~~~~~~
    The default report file name is addmrpt_1_7149_7156.txt. To use this name,
    press <return> to continue, otherwise enter an alternative.
    Enter value for report_name:
    Using the report name addmrpt_1_7149_7156.txt
    Running the ADDM analysis on the specified pair of snapshots ...
    begin
    ERROR at line 1:
    ORA-13711: Some snapshots in the range [7149, 7156] are missing key statistics.
    ORA-06512: at "SYS.DBMS_ADVISOR", line 201
    ORA-06512: at line 27
    Generating the ADDM report for this analysis ...
    ERROR:
    ORA-13608: The specified name NULL is invalid.
    ORA-06512: at "SYS.PRVT_ADVISOR", line 3122
    ORA-06512: at "SYS.DBMS_ADVISOR", line 585
    ORA-06512: at line 1
    End of Report
    Report written to addmrpt_1_7149_7156.txt
    SQL>
    Any clue or help will be really helpful for us.

    hello,
    have a look at this'
    ORA-13711:Some snapshots in the range [string, string] are missing key statistics.
    Cause:      Some AWR tables encountered errors while creating one or more
    snapshots in the given range. The data present in one or more of these missing
    tables is necessary to perform an ADDM analysis.
    Action:      Look in DBA_HIST_SNAP_ERROR to find what tables are missing in
    the given snapshot range. Use the ERROR_NUMBER column in that view
    together with the alert log to identify the reason for failure and take necessary action to
    prevent such failures in the future. Try running ADDM on a different snapshot range
    that does not include any incomplete snapshots.thanks and regards
    VD
    Edited by: Dixit on Aug 31, 2009 1:52 AM
    Edited by: Dixit on Aug 31, 2009 1:53 AM

  • Error messages while generating reports

    I am using CR XI SP4 and i get the following message when generating reports:
    com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException: Unknown Database Connector Error
    Error in File D:\Temp\{67475350-F4E8-466A-B1E9-414965812A20}.rpt:
    Unknown Database Connector Error---- Error code:-2147482942 Error code name:failed
         at com.crystaldecisions.sdk.occa.report.lib.ReportSDKServerException.throwReportSDKServerException  (Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.t.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.cf.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.z.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.ak.if(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.ad.int(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.bk.for(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.w.a(Unknown Source)
         at com.crystaldecisions.proxy.remoteagent.w.if(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(Unknown Source)
         at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setTableLocation(Unknown Source)
    In the RAS log file i see:
    ErrorLog 2009  7 21 17:45:16.188 732 3648 (\servers\ras\dtsagent\cdtsagent.cpp:3113): CDTSagent::doOneRequest reqId=250: CSResultException thrown.   ErrorSrc:"CRPE" FileName:"\servers\ras\dtsagent\reporthandler.cpp" LineNum:13209 ErrorCode:706 ErrorMsg:"Unknown Database Connector Error
    Error in File D:\Temp\{67475350-F4E8-466A-B1E9-414965812A20}.rpt: Unknown Database Connector Error"
    Any assistance would be appreciated
    Thanks

    hi,
    You are able to login in to application, Means your authentication is working.
    Open RPD in online mode and try to view data.
    Check your connection pool setting in General tab.
    Check you have selected appropriate Data Source Name, Call Interface.
    Thanks,
    Sainath Baludu.

  • Multiple executions of a query found in the ADDM Report

    Hi,
    I generated an ADDM Report on my DB for the time when the DB performance was very slow. Below are some lines from it:
    RECOMMENDATION 1: SQL Tuning, 15% benefit (28820 seconds)
    ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID
    "725bgkkhqs73v".
    RELEVANT OBJECT: SQL statement with SQL_ID 725bgkkhqs73v and
    PLAN_HASH 2688602638
    select column1,column2 from table1;
    ACTION: Investigate the SQL statement with SQL_ID "725bgkkhqs73v" for
    possible performance improvements.
    RELEVANT OBJECT: SQL statement with SQL_ID 725bgkkhqs73v and
    PLAN_HASH 2688602638
    select column1, column2 from table1;
    RATIONALE: SQL statement with SQL_ID "725bgkkhqs73v" was executed 32 times and had an average elapsed time of 900 seconds.
    Can anyone help me out with the reason behind these repeated executions of the SQL query thus resulting in a avg elapsed time of 15 mins. Also, I could see that some queries ran on the DB even for 145,445,335 times, however the total time elapsed for executing these queries was only 0.000048 seconds.
    COuld it be because there was exclusive locks on those tables during the times there queries were getting executed or do I need to look at query tuning here? Kindly help.

    yeah. posting it here:
    select column1,column2 from table1;
    Plan hash value: 2688602638
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | | | 4 (100)| |
    | 1 | HASH GROUP BY | | 1 | 77 | 4 (25)| 00:00:01 |
    | 2 | TABLE ACCESS BY INDEX ROWID| column1 | 1 | 18 | 1 (0)| 00:00:01 |
    | 3 | NESTED LOOPS | | 1 | 77 | 3 (0)| 00:00:01 |
    | 4 | TABLE ACCESS FULL | column2 | 1 | 59 | 2 (0)| 00:00:01 |
    | 5 | INDEX RANGE SCAN | x_abc | 1605 | | 1 (0)| 00:00:01 |
    SQL_ID 725bgkkhqs73v
    select column1, column2 from table1;
    Plan hash value: 2947532035
    | Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
    | 0 | SELECT STATEMENT | | | | 4 (100)| |
    | 1 | HASH GROUP BY | | 41 | 1476 | 4 (50)| 00:00:01 |
    | 2 | TABLE ACCESS BY INDEX ROWID | column1 | 14 | 252 | 1 (0)| 00:00:01 |
    | 3 | NESTED LOOPS | | 50 | 1800 | 2 (0)| 00:00:01 |
    | 4 | TABLE ACCESS BY INDEX ROWID| column1 | 3 | 54 | 1 (0)| 00:00:01 |
    | 5 | INDEX RANGE SCAN | X_abc| 1602 | | 1 (0)| 00:00:01 |
    | 6 | INDEX RANGE SCAN | XAK_def| 14 | | 1 (0)| 00:00:01 |
    Does this shed any light?
    Thanks in advance for all your help!

  • Error trying to generate addmrpt (ADDM Report) on Oracle 10.1.0.4

    Hello,
    When I launch $ORACLE_HOME/rdbms/admin/addmrpt.sql on my Fedora 3 Oracle 10g connected using sys as sysdba (or system), I get the following error :
    Specify the Begin and End Snapshot Ids
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Entrez une valeur pour begin_snap : 210
    Begin Snapshot Id specified: 210
    Entrez une valeur pour end_snap : 211
    End Snapshot Id specified: 211
    Specify the Report Name
    ~~~~~~~~~~~~~~~~~~~~~~~
    The default report file name is addmrpt_1_210_211.txt. To use this name,
    press <return> to continue, otherwise enter an alternative.
    Entrez une valeur pour report_name :
    Using the report name addmrpt_1_210_211.txt
    Running the ADDM analysis on the specified pair of snapshots ...
    begin
    ERREUR a la ligne 1 :
    ORA-13711: Des statistiques de cle sont absentes de certains cliches dans la
    plage [210, 211].
    ORA-06512: a "SYS.PRVT_ADVISOR", ligne 1283
    ORA-06512: a "SYS.DBMS_ADVISOR", ligne 190
    ORA-06512: a ligne 27
    Generating the ADDM report for this analysis ...
    ERROR:
    ORA-14552: operation DDL, COMMIT ou ROLLBACK interdite dans une instruction DML
    ou une interrogation
    ORA-06512: a "SYS.PRVT_ADVISOR", ligne 1750
    ORA-13608: Le nom de tache ou d'objet NULL n'est pas valide.
    ORA-06512: a "SYS.DBMS_ADVISOR", ligne 569
    ORA-06512: a ligne 1
    Any help to solve this problem ?
    Oups, when I use awrrpt on the same snapshot, I get a correct report.
    Regards,
    Freddy

    Please refer to the patchnote.htm that is bundled with 10.1.0.4.0 patch set. Only you are aware of what type of database configuration you have. You will want to pay close attention to "7.2.1.3 Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE Initialization Parameters" and "7.2.2 Upgrade the Release 10.1 Database".
    Basically, I believe you have missed these required steps after installing the 10.1.0.4.0 patch set from the OUI:
    (pasted from the patchnote.htm)
    13.     Enter the following SQL*Plus commands:
    14.     SQL> STARTUP UPGRADE
    15.     SQL> SPOOL patch.log
    16.     SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\catpatch.sql
    17.     SQL> SPOOL OFF
    18.     
    19.     Review the patch.log file for errors and inspect the list of components that is displayed at the end of catpatch.sql script.
    This list provides the version and status of each SERVER component in the database.
    20.     If necessary, rerun the catpatch.sql script after correcting any problems.
    21.     Restart the database:
    22.     SQL> SHUTDOWN
    23.     SQL> STARTUP
    24.     
    25.     Run the utlrp.sql script to recompile all invalid PL/SQL packages now instead of when the packages are accessed for the first time. This step is optional but recommended.
    26.     SQL> @ORACLE_BASE\ORACLE_HOME\rdbms\admin\utlrp.sql

  • ADDM report not being generated

    I noticed that addm reports are not being generated from last 2 days. So I did the following:
    SQL> exec dbms_workload_repository.create_snapshot;
    BEGIN dbms_workload_repository.create_snapshot; END;
    ERROR at line 1:
    ORA-13516: AWR Operation failed: only a subset of SQL can be issued
    ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 10
    ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 33
    ORA-06512: at line 1
    I got above error. I am not sure what that means. I also ran below SQL:
    SQL> select nam.ksppinm name, val.KSPPSTVL, nam.ksppdesc description
    2 from x$ksppi nam, x$ksppsv val
    3 where nam.indx = val.indx and
    4 nam.ksppinm = '_awr_restrict_mode'
    5 order by 1
    6 ;
    awrrestrict_mode
    FALSE
    AWR Restrict Mode
    What could be the reason that the reports are not being generated anymore

    Check Note:308003.1 - AWR Snapshots Not Generating

  • How to use awr and addm reports

    Hi,
    to use awr and addm reports does we should have separate license or oracle server software license is enough.
    which tool do we use to read this awr and addm reports in real time.
    please give your valuable suggestions.
    thank you!

    Seeing as you seem to want to continue the discussion on someone else's old thread rather than your own one
    AWR files in oracle
    If i don't then it is difficult to find the queries thata re related to my application as most of those are the sysqueries, i just need schema specific queries in the SQL ordered by Elapsed Time section. Perhaps you are using the wrong tool?
    A system-level report like AWR or ADDM is no use to you as it seems your application code is not significant at the system level.
    You might want to consider tracing the sessions from your application using client_id or module to identify sessions belonging to your application then possibly use TRCSESS and TKPROF.

  • How to apply recommendations given by addm report

    Hi Gurus
    Actually the addm report of my test database is giving some recommendations and i am not getting ,how to apply those on my database.
    so i am putting some data here,if anybody could give me some hint regarding that it would be of great help as i am new in dba.
    Waits on event "log file sync" while performing COMMIT and ROLLBACK operations were consuming significant database time. RECOMMENDATION 1: Application Analysis, 9.9% benefit (147 seconds) ACTION: Investigate application logic for possible reduction in the number of COMMIT operations by increasing the size of transactions. RATIONALE: The application was performing 112 transactions per minute with an average redo size of 3655 bytes per transaction. RECOMMENDATION 2: Host Configuration, 9.9% benefit (147 seconds) ACTION: Investigate the possibility of improving the performance of I/O to the online redo log files. RATIONALE: The average size of writes to the online redo log files was 3 K and the average time per write was 4 milliseconds. SYMPTOMS THAT LED TO THE FINDING: Wait class "Commit" was consuming significant database time. (9.9% impact [147 seconds]) FINDING 6: 8% impact (119 seconds) ---------------------------------- Wait event "process startup" in wait class "Other" was consuming significant database time. RECOMMENDATION 1: Application Analysis, 8% benefit (119 seconds) ACTION: Investigate the cause for high "process startup" waits. Refer to Oracle's "Database Reference" for the description of this wait event. Use given SQL for further investigation. RATIONALE: The SQL statement with SQL_ID "NULL-SQLID" was found waiting for "process startup" wait event. RELEVANT OBJECT: SQL statement with SQL_ID NULL-SQLID RECOMMENDATION 2: Application Analysis, 8% benefit (119 seconds) ACTION: Investigate the cause for high "process startup" waits in Service "SYS$BACKGROUND". FINDING 7: 6.3% impact (93 seconds)
    NO RECOMMENDATIONS AVAILABLE ADDITIONAL INFORMATION: Hard parses due to cursor environment mismatch were not consuming significant database time. Hard parsing SQL statements that encountered parse errors was not consuming significant database time. Parse errors due to inadequately sized shared pool were not consuming significant database time. Hard parsing due to cursors getting aged out of shared pool was not consuming significant database time. Hard parses due to literal usage and cursor invalidation were not consuming significant database time. FINDING 8: 4.3% impact (63 seconds) ----------------------------------- The throughput of the I/O subsystem was significantly lower than expected. RECOMMENDATION 1: Host Configuration, 4.3% benefit (63 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. SYMPTOMS THAT LED TO THE FINDING: Wait class "User I/O" was consuming significant database time. (13% impact [191 seconds]) FINDING 9: 4.1% impact (60 seconds) ----------------------------------- Buffer cache writes due to small log files were consuming significant database time. NO RECOMMENDATIONS AVAILABLE SYMPTOMS THAT LED TO THE FINDING: The throughput of the I/O subsystem was significantly lower than expected. (4.3% impact [63 seconds]) Wait class "User I/O" was consuming significant database time. (13% impact [191 seconds]) FINDING 10: 3.5% impact (51 seconds) ------------------------------------ Wait event "class slave wait" in wait class "Other" was consuming significant database time. RECOMMENDATION 1: Application Analysis, 3.5% benefit (51 seconds) ACTION: Investigate the cause for high "class slave wait" waits. Refer to Oracle's "Database Reference" for the description of this wait event. Use given SQL for further investigation. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ADDITIONAL INFORMATION ---------------------- Wait class "Administrative" was not consuming significant database time. Wait class "Application" was not consuming significant database time. Wait class "Cluster" was not consuming significant database time. Wait class "Concurrency" was not consuming significant database time. Wait class "Configuration" was not consuming significant database time. Wait class "Network" was not consuming significant database time. Wait class "Scheduler" was not consuming significant database time. The analysis of I/O performance is based on the default assumption that the average read time for one database block is 10000 micro-seconds. An explanation of the terminology used in this report is available when you run the report with the 'ALL' level of detail.
    regards
    Richa

    I'm not sure what about the recommendations you don't understand as what you posted seems quite clear. Take #1 for example:
    Investigate application logic for possible reduction in the number of COMMIT operations by increasing the size of transactions.is telling you that it appears you are doing incremental commits. Are you? Can you change it if you are?
    When you respond please include full version information.

Maybe you are looking for

  • New Apple TV starts as 720 not 1080?

    Hi I have just bought a new Apple TV directly from Apple. I am connecting to a Sony Bravia TV, but when connecting it reports resolution as 720, not 1080. I have tried a different cable, but no joy. I also have BT Vision through another AV channel an

  • Load the dynamic values in shuttle

    Hi, I have one Managed bean which holds the arraylist. i want to load the list in to shuttle. if possible help me to send the piece of code. Thanks

  • Ipod won't register on the computer

    i have a new ipod nano, and when i hook it up to my computer, it doesn't show up anywhere that my ipod is hooked into the computer. i've bought new usb cords, and tried resetting it many times, but nothing has helped. i can't restore it, because the

  • Computer is low on memory even though I have 100GB available

    Trying to use my programs like Adobe Bridge keeps crashing and saying I'm low on memory even tough I have 90-100GB of free space. All other programs are closed and I tried clearing the memory in the system terminal program. Any ideas on what's going

  • Why is my video in iPhoto

    I have a Iphone C5 and i was filming with the camera and the video is in iphoto. Plus, how do i pause, fast forward and rewind my video in iphoto?