Dba_outstanding_alerts-addm

can any one tell me ADDM. I have got message from dba_outstanding_alerts.
EVENT_CLASS Warning 5
Metrics "Database Time Spent Waiting (%)" is at 60.98381 for event class "Other"
Run ADDM to get more performance analysis about your system.
please clarify this alert.

dbaforu,
I presume you have not read the documentation that i have pointed out;
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/diagnsis.htm
+6.2.4.1 Running ADDM Using addmrpt.sql+
To invoke ADDM analysis for the scenario previously described, you can simply run the addmrpt.sql script at the SQL prompt:
+@$ORACLE_HOME/rdbms/admin/addmrpt.sql+
When running the addmrpt.sql report to analyze the specific time period in the example scenario, you need to:
+1.+
Identify the last snapshot that was taken before or at 7 P.M. and the first snapshot that was taken after or at 9 P.M. of the previous night from the list of recent snapshots that the report initially displays. The output is similar to the following:
Listing the last 3 days of Completed Snapshots
+...+
Snap
Instance     DB Name        Snap Id    Snap Started    Level
main         MAIN               136 20 Oct 2003 18:30      1
+137 20 Oct 2003 19:00 1+
+138 20 Oct 2003 19:30 1+
+139 20 Oct 2003 20:00 1+
+140 20 Oct 2003 20:30 1+
+141 20 Oct 2003 21:00 1+
+142 20 Oct 2003 21:30 1+
+2.+
Provide the snapshot Id closest to 7 P.M. when prompted for the beginning snapshot and the 9 P.M. snapshot Id when prompted for the ending snapshot.
Enter value for begin_snap: 137
Begin Snapshot Id specified: 137
Enter value for end_snap: 141
End   Snapshot Id specified: 141
+3.+
Enter a report name or accept the default name when prompted to specify the report name.
Enter value for report_name:
Using the report name addmrpt_1_137_145.txt
Running the ADDM analysis on the specified pair of snapshots ...
Generating the ADDM report for this analysis ...
After the report name is specified, ADDM analysis over the specific time frame is performed. At the end of the analysis, the SQL script displays the textual ADDM report of the analysis. You can review the report to find the top performance issues affecting the database and possible ways to solve those issues.
Instructions for running the report addmrpt.sql in a non-interactive mode can be found at the beginning of the $ORACLE_HOME/rdbms/admin/addmrpt.sql file.
Ogan

Similar Messages

  • 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

  • Unable to generate ADDM snapshot reports as the error_count is 1

    Hi,
    my db is on 10.1.0.2 windows 2003 server.
    errors while generating ADDM snapshots, was schedule for every 15 minutes,
    the error_count is 1 from dba_hist_snap, these errors are continous and generates a trace file on m000_no
    *** ACTION NAME:(Auto-Flush Slave Action) 2007-10-26 11:15:46.171
    *** MODULE NAME:(MMON_SLAVE) 2007-10-26 11:15:46.171
    *** SERVICE NAME:(SYS$BACKGROUND) 2007-10-26 11:15:46.171
    *** SESSION ID:(564.28596) 2007-10-26 11:15:46.171
    *** KEWROCISTMTEXEC - encountered error: (ORA-00001: unique constraint (SYS.WRH$_SQLBIND_PK) violated
    *** SQLSTR: total-len=701, dump-len=240,
    STR={insert into wrh$_sqlbind   (snap_id, dbid, instance_number,    sql_id, child_number, name, position, dup_position,    datatype, datatype_string, character_sid,    precision, scale, max_length, was_captured,    last_captured, value_string, v}
    *** KEWRAFM1: Error=13509 encountered by kewrfteh;
    any suggestions what should be done, i need an immediate solution to stop these errors happening, i am unable to generate a snapshot report .

    Rajesh,
    your URLs are not viewable for most of the forum users, as they are in the Oracle Intranet. Better you use the internal help list for this question.
    Regards
    Rainer

  • Need understanding on the ADDM

    Hi,
    Db version 11.2.0.3
    EBS version 12.1.3
    OS : Linux
    I have 2 SEV-1 SR's going on with Oracle on which we are working with them. I ran a ADDM from yesterday Morning till today afternoon( Almost 25 Hours).
    My understanding :
    1. Update query 85ag5gkm9wzmb is taking maximum of time and resources ( One SR is for this - this is Autoinvoice Master Program).
    2. SGA and PGA are undersized. Current SGA is 24Gb and PGA is 6Gb. Do I really need to increase SGA and PGA ? My previous has been that on increasing
    SGA/PGA to suggested value , it will further prompt for increasing.
    3. SYS.DBMS_SPACE.AUTO_SPACE_ADVISOR_JOB_PROC needs some action from my end, should I disable this job , what does it really do ? i am trying to figure that out ,
    any help on this will be appreciated.
    Please confirm if my understanding is correct and other suggestion/inputs you can provide. Also please suggest how to find if I/O is a bottleneck in the system ? I can see db file sequential read and db file scattered reads in the AWR but they are mostly by the update statement 85ag5gkm9wzmb.
    Below is the ADDM for reference.
              ADDM Report for Task 'TASK_10569'
    Analysis Period
    AWR snapshot range from 6708 to 6733.
    Time period starts at 19-DEC-13 11.30.37 AM
    Time period ends at 20-DEC-13 12.30.43 PM
    Analysis Target
    Database 'PROD' with DB ID 221722471.
    Database version 11.2.0.3.0.
    ADDM performed an analysis of instance PROD, numbered 1 and hosted at
    hostname.domainname.in.
    Activity During the Analysis Period
    Total database time was 448593 seconds.
    The average number of active sessions was 4.98.
    Summary of Findings
       Description                               Active Sessions      Recommendations
                                                 Percent of Activity  
    1  Top SQL Statements                        3.44 | 69.1          6
    2  Top Segments by "User I/O" and "Cluster"  2.64 | 53.06         5
    3  Undersized SGA                            .94 | 18.91          1
    4  Undersized PGA                            .28 | 5.66           0
    5  PL/SQL Execution                          .19 | 3.9            5
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              Findings and Recommendations
    Finding 1: Top SQL Statements
    Impact is 3.44 active sessions, 69.1% 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 2.26 active sessions, 45.37% of total activity.
       Action
          Run SQL Tuning Advisor on the UPDATE statement with SQL_ID
          "85ag5gkm9wzmb".
          Related Object
             SQL statement with SQL_ID 85ag5gkm9wzmb.
             UPDATE RA_CUST_TRX_LINE_GL_DIST LGD SET (AMOUNT, ACCTD_AMOUNT) =
             (SELECT /*+ index(rec1 RA_CUST_TRX_LINE_GL_DIST_N6) ordered */
             NVL(LGD.AMOUNT, 0) - ( SUM(LGD2.AMOUNT) - ( DECODE(LGD.GL_DATE,
             REC1.GL_DATE, 1, 0) * CTL.EXTENDED_AMOUNT ) ), NVL(LGD.ACCTD_AMOUNT,
             0) - ( SUM(LGD2.ACCTD_AMOUNT) - ( DECODE(LGD.GL_DATE, REC1.GL_DATE,
             1, 0) * DECODE(:B2 , NULL, ROUND( CTL.EXTENDED_AMOUNT *
             NVL(CT.EXCHANGE_RATE,1), :B3 ), ROUND( ( CTL.EXTENDED_AMOUNT *
             NVL(CT.EXCHANGE_RATE,1) ) / :B2 ) * :B2 ) ) ) FROM
             RA_CUSTOMER_TRX_LINES CTL, RA_CUSTOMER_TRX CT,
             RA_CUST_TRX_LINE_GL_DIST LGD2, RA_CUST_TRX_LINE_GL_DIST REC1 WHERE
             CTL.CUSTOMER_TRX_LINE_ID = LGD2.CUSTOMER_TRX_LINE_ID AND
             CTL.CUSTOMER_TRX_ID = CT.CUSTOMER_TRX_ID AND LGD.CUSTOMER_TRX_LINE_ID
             = CTL.CUSTOMER_TRX_LINE_ID AND LGD2.ACCOUNT_SET_FLAG = 'N' AND
             REC1.CUSTOMER_TRX_ID = CT.CUSTOMER_TRX_ID AND REC1.ACCOUNT_CLASS =
             'REC' AND REC1.LATEST_REC_FLAG = 'Y' AND NVL(LGD.GL_DATE, TO_DATE(
             2415021, 'J') ) = NVL(LGD2.GL_DATE, TO_DATE( 2415021, 'J') ) GROUP BY
             CTL.CUSTOMER_TRX_LINE_ID, REC1.GL_DATE, CTL.EXTENDED_AMOUNT,
             CTL.REVENUE_AMOUNT, CT.EXCHANGE_RATE ), PERCENT = (SELECT /*+
             index(rec2 RA_CUST_TRX_LINE_GL_DIST_N6) */ DECODE(LGD.ACCOUNT_CLASS
             || LGD.ACCOUNT_SET_FLAG, 'SUSPENSEN', LGD.PERCENT, 'UNBILLN',
             LGD.PERCENT, 'UNEARNN', LGD.PERCENT, NVL(LGD.PERCENT, 0) - (
             SUM(NVL(LGD4.PERCENT, 0)) - DECODE(REC2.GL_DATE, NVL(LGD.GL_DATE,
             REC2.GL_DATE), 100, 0) ) ) FROM RA_CUST_TRX_LINE_GL_DIST LGD4,
             RA_CUST_TRX_LINE_GL_DIST REC2 WHERE LGD.CUSTOMER_TRX_LINE_ID =
             LGD4.CUSTOMER_TRX_LINE_ID AND REC2.CUSTOMER_TRX_ID =
             LGD.CUSTOMER_TRX_ID AND REC2.CUSTOMER_TRX_ID = LGD4.CUSTOMER_TRX_ID
             AND REC2.ACCOUNT_CLASS = 'REC' AND REC2.LATEST_REC_FLAG = 'Y' AND
             LGD4.ACCOUNT_SET_FLAG = LGD.ACCOUNT_SET_FLAG AND
             DECODE(LGD4.ACCOUNT_SET_FLAG, 'Y', LGD4.ACCOUNT_CLASS,
             LGD.ACCOUNT_CLASS) = LGD.ACCOUNT_CLASS AND NVL(LGD.GL_DATE, TO_DATE(
             2415021, 'J') ) = NVL(LGD4.GL_DATE, TO_DATE( 2415021, 'J') ) GROUP BY
             REC2.GL_DATE, LGD.GL_DATE ), LAST_UPDATED_BY = :B1 , LAST_UPDATE_DATE
             = SYSDATE WHERE CUST_TRX_LINE_GL_DIST_ID IN (SELECT /*+ index(rec3
             RA_CUST_TRX_LINE_GL_DIST_N6) */ MIN(DECODE(LGD3.GL_POSTED_DATE, NULL,
             LGD3.CUST_TRX_LINE_GL_DIST_ID, NULL) ) FROM RA_CUSTOMER_TRX_LINES
             CTL, RA_CUSTOMER_TRX T, RA_CUST_TRX_LINE_GL_DIST LGD3,
             RA_CUST_TRX_LINE_GL_DIST REC3 WHERE T.REQUEST_ID = :B5 AND
             T.CUSTOMER_TRX_ID = CTL.CUSTOMER_TRX_ID AND (CTL.LINE_TYPE IN (
             'TAX','FREIGHT','CHARGES','SUSPENSE' ) OR (CTL.LINE_TYPE = 'LINE' AND
             CTL.ACCOUNTING_RULE_ID IS NULL )) AND LGD3.CUSTOMER_TRX_LINE_ID =
             CTL.CUSTOMER_TRX_LINE_ID AND LGD3.ACCOUNT_SET_FLAG = 'N' AND
             REC3.CUSTOMER_TRX_ID = T.CUSTOMER_TRX_ID AND REC3.ACCOUNT_CLASS =
             'REC' AND REC3.LATEST_REC_FLAG = 'Y' AND
             NVL(T.PREVIOUS_CUSTOMER_TRX_ID, -1) = DECODE(:B4 , 'INV', -1,
             'REGULAR_CM', T.PREVIOUS_CUSTOMER_TRX_ID,
             NVL(T.PREVIOUS_CUSTOMER_TRX_ID, -1) ) GROUP BY
             CTL.CUSTOMER_TRX_LINE_ID, LGD3.GL_DATE, REC3.GL_DATE,
             CTL.EXTENDED_AMOUNT, CTL.REVENUE_AMOUNT, T.EXCHANGE_RATE HAVING (
             SUM(NVL(LGD3.AMOUNT, 0)) <> CTL.EXTENDED_AMOUNT *
             DECODE(LGD3.GL_DATE, REC3.GL_DATE, 1, 0) OR
             SUM(NVL(LGD3.ACCTD_AMOUNT, 0)) <> DECODE(LGD3.GL_DATE, REC3.GL_DATE,
             1, 0) * DECODE(:B2 , NULL, ROUND( CTL.EXTENDED_AMOUNT *
             NVL(T.EXCHANGE_RATE,1), :B3 ), ROUND( ( CTL.EXTENDED_AMOUNT *
             NVL(T.EXCHANGE_RATE,1) ) / :B2 ) * :B2 ) ) UNION SELECT /*+
             index(rec5 RA_CUST_TRX_LINE_GL_DIST_N6) INDEX (lgd5
             ra_cust_trx_line_gl_dist_n6) index(ctl2 ra_customer_trx_lines_u1) */
             TO_NUMBER( MIN(DECODE(LGD5.GL_POSTED_DATE||LGD5.ACCOUNT_CLASS||
             LGD5.ACCOUNT_SET_FLAG, 'REVN', LGD5.CUST_TRX_LINE_GL_DIST_ID, 'REVY',
             LGD5.CUST_TRX_LINE_GL_DIST_ID, 'TAXN', LGD5.CUST_TRX_LINE_GL_DIST_ID,
             'TAXY', LGD5.CUST_TRX_LINE_GL_DIST_ID, 'FREIGHTN',
             LGD5.CUST_TRX_LINE_GL_DIST_ID, 'FREIGHTY',
             LGD5.CUST_TRX_LINE_GL_DIST_ID, 'CHARGESN',
             LGD5.CUST_TRX_LINE_GL_DIST_ID, 'CHARGESY',
             LGD5.CUST_TRX_LINE_GL_DIST_ID, 'UNEARNY',
             LGD5.CUST_TRX_LINE_GL_DIST_ID, 'UNBILLY',
             LGD5.CUST_TRX_LINE_GL_DIST_ID, NULL ) ) ) FROM
             RA_CUST_TRX_LINE_GL_DIST LGD5, RA_CUST_TRX_LINE_GL_DIST REC5,
             RA_CUSTOMER_TRX_LINES CTL2, RA_CUSTOMER_TRX T WHERE T.REQUEST_ID =
             :B5 AND T.CUSTOMER_TRX_ID = REC5.CUSTOMER_TRX_ID AND
             CTL2.CUSTOMER_TRX_LINE_ID = LGD5.CUSTOMER_TRX_LINE_ID AND
             REC5.CUSTOMER_TRX_ID = LGD5.CUSTOMER_TRX_ID AND REC5.ACCOUNT_CLASS =
             'REC' AND REC5.LATEST_REC_FLAG = 'Y' AND (CTL2.LINE_TYPE IN (
             'TAX','FREIGHT','CHARGES','SUSPENSE') OR (CTL2.LINE_TYPE = 'LINE' AND
             (CTL2.ACCOUNTING_RULE_ID IS NULL OR LGD5.ACCOUNT_SET_FLAG = 'Y' )))
             GROUP BY LGD5.CUSTOMER_TRX_LINE_ID, LGD5.GL_DATE, REC5.GL_DATE,
             LGD5.ACCOUNT_SET_FLAG, DECODE(LGD5.ACCOUNT_SET_FLAG, 'N', NULL,
             LGD5.ACCOUNT_CLASS) HAVING SUM(NVL(LGD5.PERCENT, 0)) <> DECODE(
             NVL(LGD5.GL_DATE, REC5.GL_DATE), REC5.GL_DATE, 100, 0) )
       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 "85ag5gkm9wzmb" was executed 20 times and had
          an average elapsed time of 9763 seconds.
       Rationale
          Top level calls to execute the PL/SQL statement with SQL_ID
          "gccbpwamzp78q" are responsible for 100% of the database time spent on
          the UPDATE statement with SQL_ID "85ag5gkm9wzmb".
          Related Object
             SQL statement with SQL_ID gccbpwamzp78q.
             declare l_header_rounding_flag VARCHAR2 ( 1 ) ; BEGIN select
             trx_header_level_rounding into l_header_rounding_flag from
             ar_system_parameters ; :return_value:i_return_value := arp_rounding .
             correct_dist_rounding_errors ( :request_id , NULL , NULL ,
             :rows_processed:i_rows_processed , :error_msg:i_error_msg , NULL ,
             NULL , :trx_class , 'N' , :debug_mode , l_header_rounding_flag , 'N'
             ) ; END ;
       Recommendation 2: SQL Tuning
       Estimated benefit is .42 active sessions, 8.39% of total activity.
       Action
          Run SQL Tuning Advisor on the SELECT statement with SQL_ID
          "d9xccqfmfjvns".
          Related Object
             SQL statement with SQL_ID d9xccqfmfjvns.
             SELECT RCT.CUSTOMER_TRX_ID K_TRX_ID, RCT.TRX_NUMBER, SUM
             (APS.AMOUNT_DUE_REMAINING) CM_AMOUNT_APPLIED,RCT.TRX_DATE FROM
             APPS.RA_CUSTOMER_TRX_ALL RCT, APPS.AR_PAYMENT_SCHEDULES_ALL APS,
             APPS.RA_CUST_TRX_TYPES_ALL TCTTA, APPS.AR_CUSTOMERS AC,
             APPS.HZ_CUSTOMER_PROFILES HCP, APPS.RA_TERMS RT WHERE
             RCT.CUST_TRX_TYPE_ID = TCTTA.CUST_TRX_TYPE_ID AND AC.CUSTOMER_ID =
             RCT.BILL_TO_CUSTOMER_ID AND RCT.CUSTOMER_TRX_ID=APS.CUSTOMER_TRX_ID
             AND AC.CUSTOMER_ID = HCP.CUST_ACCOUNT_ID AND RCT.BILL_TO_SITE_USE_ID
             = HCP.SITE_USE_ID AND RT.TERM_ID = HCP.STANDARD_TERMS AND TCTTA.TYPE
             IN ('INV') AND UPPER(TCTTA.NAME) IN ( SELECT UPPER(MEANING) FROM
             FND_LOOKUP_VALUES WHERE LOOKUP_TYPE = :B3 ) AND RCT.TRX_DATE <= NVL
             (TO_DATE(:B2 , 'RRRR/MM/DD HH24:MI:SS'), RCT.TRX_DATE) AND
             AC.CUSTOMER_ID = :B1 GROUP BY RCT.CUSTOMER_TRX_ID,
             RCT.TRX_NUMBER,RCT.TRX_DATE HAVING SUM (APS.AMOUNT_DUE_REMAINING) > 0
             ORDER BY RCT.TRX_DATE
       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 "d9xccqfmfjvns" was executed 123412 times and
          had an average elapsed time of 0.29 seconds.
       Rationale
          Top level calls to execute the PL/SQL statement with SQL_ID
          "bcxz2s8wj5spc" are responsible for 100% of the database time spent on
          the SELECT statement with SQL_ID "d9xccqfmfjvns".
          Related Object
             SQL statement with SQL_ID bcxz2s8wj5spc.
             BEGIN XXSD_APPLY_CM_APPLY_TO_INV(:errbuf,:rc,:A0,:A1,:A2,:A3); END;
       Recommendation 3: SQL Tuning
       Estimated benefit is .3 active sessions, 6.04% of total activity.
       Action
          Run SQL Tuning Advisor on the SELECT statement with SQL_ID
          "2ujt2fg615ymk".
          Related Object
             SQL statement with SQL_ID 2ujt2fg615ymk.
             SELECT HP.PARTY_NAME PARTY_NAME, RCT.TRX_NUMBER TRX_NUMBER,
             RCT.TRX_DATE TRX_DATE, APS.AMOUNT_DUE_ORIGINAL AMOUNT_DUE_ORIGINAL,
             APS.AMOUNT_DUE_REMAINING OUTSTANDING_AMOUNT, RCTT.NAME
             TRANSACTION_TYPE FROM RA_CUSTOMER_TRX_ALL RCT,
             AR_PAYMENT_SCHEDULES_ALL APS, RA_CUST_TRX_TYPES_ALL RCTT,
             HZ_CUST_ACCOUNTS HCA, HZ_PARTIES HP, APPS.AR_CUSTOMERS AC,
             APPS.HZ_CUSTOMER_PROFILES HCP, APPS.RA_TERMS RT, HZ_PARTY_SITES HPS,
             HZ_CUST_ACCT_SITES_ALL HCASA, HZ_CUST_SITE_USES_ALL HCSUA WHERE 1 = 1
             AND RCT.BILL_TO_CUSTOMER_ID = HCA.CUST_ACCOUNT_ID AND HCA.PARTY_ID =
             HP.PARTY_ID AND APS.CUSTOMER_TRX_ID = RCT.CUSTOMER_TRX_ID AND
             APS.ORG_ID = RCT.ORG_ID AND RCTT.CUST_TRX_TYPE_ID =
             RCT.CUST_TRX_TYPE_ID AND RCTT.ORG_ID = RCT.ORG_ID AND AC.CUSTOMER_ID
             = HCA.CUST_ACCOUNT_ID AND AC.CUSTOMER_ID = RCT.BILL_TO_CUSTOMER_ID
             AND AC.CUSTOMER_ID = HCP.CUST_ACCOUNT_ID AND RCT.BILL_TO_SITE_USE_ID
             = HCP.SITE_USE_ID AND RT.TERM_ID = HCP.STANDARD_TERMS AND
             HPS.PARTY_SITE_ID = HCASA.PARTY_SITE_ID AND HCASA.CUST_ACCOUNT_ID =
             AC.CUSTOMER_ID AND HCASA.CUST_ACCT_SITE_ID = HCSUA.CUST_ACCT_SITE_ID
             AND HCSUA.SITE_USE_ID = RCT.BILL_TO_SITE_USE_ID AND RCT.TRX_DATE
             BETWEEN NVL (TO_DATE (:B6 , 'RRRR/MM/DD HH24:MI:SS' ), '1-JAN-1900' )
             AND NVL (TO_DATE (:B5 , 'RRRR/MM/DD HH24:MI:SS' ), '31-DEC-2100' )
             AND RCTT.NAME = NVL (:B4 , RCTT.NAME) AND RT.TERM_ID = NVL (:B3 ,
             RT.TERM_ID) AND HP.PARTY_NAME = NVL (:B2 , HP.PARTY_NAME) AND ( (CASE
             WHEN :B1 = 'Open' THEN APS.AMOUNT_DUE_REMAINING END != 0 ) OR ((CASE
             WHEN :B1 = 'Closed' THEN APS.AMOUNT_DUE_REMAINING END = 0 ) ) OR CASE
             WHEN :B1 IS NULL THEN 1 END = 1 )
       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 "2ujt2fg615ymk" was executed 19 times and had
          an average elapsed time of 1368 seconds.
       Rationale
          At least 2 distinct execution plans were utilized for this SQL statement
          during the analysis period.
       Rationale
          Top level calls to execute the PL/SQL statement with SQL_ID
          "g969dx1d0uucf" are responsible for 100% of the database time spent on
          the SELECT statement with SQL_ID "2ujt2fg615ymk".
          Related Object
             SQL statement with SQL_ID g969dx1d0uucf.
             BEGIN XXSD_TRX_DETAIL_REPORT(:errbuf,:rc,:A0,:A1,:A2,:A3,:A4,:A5);
             END;
       Recommendation 4: SQL Tuning
       Estimated benefit is .2 active sessions, 4.04% of total activity.
       Action
          Run SQL Tuning Advisor on the SELECT statement with SQL_ID
          "gy02p15c6bf0w".
          Related Object
             SQL statement with SQL_ID gy02p15c6bf0w.
             SELECT SUM (RECEIPTS) -  SUM (PAYMENTS)  FROM (SELECT
             AIP.ACCOUNTING_DATE GL_DATE , DECODE(NVL(APC.VENDOR_NAME ,
             APC.REMIT_TO_SUPPLIER_NAME )  , 'FD Investment' , 'FD' , 'Payment' ) 
             TYPE , APC.DOC_SEQUENCE_VALUE VOUCHER_NO , APC.CREATION_DATE
             VOUCHER_DATE , TO_CHAR (APC.CHECK_NUMBER )  CHECK_NUMBER , TO_CHAR
             (NVL(APC.FUTURE_PAY_DUE_DATE , APC.CHECK_DATE )  , 'DD-MON-YYYY' ) 
             CHECK_DATE , NVL(APC.VENDOR_NAME , APC.REMIT_TO_SUPPLIER_NAME ) 
             VENDOR_NAME , API.ACCTS_PAY_CODE_COMBINATION_ID ACCOUNT_CODE ,
             'Supplier Payment' DESCRIPTION , TO_CHAR (DECODE(SIGN(SUM
             (AIP.AMOUNT) )  , -1 , SUM (AIP.AMOUNT *  NVL(AIP.EXCHANGE_RATE , 1 )
             ) *  -1  , SUM (0) )  )  RECEIPTS , TO_CHAR (DECODE(SIGN(SUM
             (AIP.AMOUNT) )  , 1 , SUM (AIP.AMOUNT *  NVL(AIP.EXCHANGE_RATE , 1 ) 
             ) , SUM (0) )  )  PAYMENTS , TO_NUMBER (SUM (AIP.AMOUNT * 
             NVL(AIP.EXCHANGE_RATE , 1 )  ) )  PAYMENTS1 , CBA.BANK_ACCOUNT_NAME
             BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM BANK_ACCOUNT_NUM ,
             BANK.PARTY_NAME BANK_NAME , BRANCH.PARTY_NAME BRANCH_NAME FROM
             APPS.AP_INVOICE_PAYMENTS_ALL AIP , APPS.AP_INVOICES_ALL API ,
             APPS.AP_CHECKS_ALL APC , APPS.CE_BANK_ACCOUNTS CBA ,
             APPS.CE_BANK_ACCT_USES_ALL CBU , HZ_PARTIES BANK , HZ_PARTIES BRANCH 
             WHERE API.INVOICE_ID =  AIP.INVOICE_ID  AND AIP.CHECK_ID = 
             APC.CHECK_ID  AND APC.CE_BANK_ACCT_USE_ID =  CBU.BANK_ACCT_USE_ID 
             AND CBA.BANK_ACCOUNT_ID =  CBU.BANK_ACCOUNT_ID  AND CBA.BANK_ID = 
             BANK.PARTY_ID  AND CBA.BANK_BRANCH_ID =  BRANCH.PARTY_ID  AND ( (
             APC.STATUS_LOOKUP_CODE IN ( 'NEGOTIABLE' , 'CLEARED' , 'VOIDED' ,
             'RECONCILED UNACCOUNTED' , 'RECONCILED' , 'CLEARED BUT UNACCOUNTED' )
             AND AIP.ACCOUNTING_DATE <  :b1  AND APC.FUTURE_PAY_DUE_DATE IS NULL 
             )  OR ( APC.STATUS_LOOKUP_CODE IN ( 'NEGOTIABLE' )  AND
             APC.FUTURE_PAY_DUE_DATE <  :b1 ) )  AND CBA.BANK_ACCOUNT_ID =  :b2 
             AND AIP.INVOICE_PAYMENT_TYPE IS NULL   AND ( API.ORG_ID IS NULL   OR
             API.ORG_ID =  :b3 )   GROUP BY AIP.ACCOUNTING_DATE ,
             DECODE(NVL(APC.VENDOR_NAME , APC.REMIT_TO_SUPPLIER_NAME )  , 'FD
             Investment' , 'FD' , 'Payment' )  , APC.DOC_SEQUENCE_VALUE ,
             APC.CREATION_DATE , TO_CHAR (APC.CHECK_NUMBER )  , TO_CHAR
             (NVL(APC.FUTURE_PAY_DUE_DATE , APC.CHECK_DATE )  , 'DD-MON-YYYY' )  ,
             NVL(APC.VENDOR_NAME , APC.REMIT_TO_SUPPLIER_NAME )  ,
             API.ACCTS_PAY_CODE_COMBINATION_ID , 'Supplier Payment' ,
             CBA.BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM , BANK.PARTY_NAME ,
             BRANCH.PARTY_NAME  UNION ALL SELECT APID.ACCOUNTING_DATE GL_DATE ,
             DECODE(POV.VENDOR_NAME , 'FD Investment' , 'FD' , 'I' )  TYPE ,
             API.DOC_SEQUENCE_VALUE VOUCHER_NO , API.CREATION_DATE VOUCHER_DATE ,
             API.INVOICE_NUM CHECK_NUMBER , TO_CHAR (API.INVOICE_DATE ,
             'DD-MON-YYYY' )  CHECK_DATE , POV.VENDOR_NAME VENDOR_NAME ,
             API.ACCTS_PAY_CODE_COMBINATION_ID ACCOUNT_CODE , NVL(API.DESCRIPTION
             , API.INVOICE_NUM )  DESCRIPTION , TO_CHAR (SUM (API.INVOICE_AMOUNT *
             NVL(API.EXCHANGE_RATE , 1 )  ) )  RECEIPTS , TO_CHAR (SUM (0) ,
             'fm999999999990.00' )  PAYMENTS , TO_NUMBER (SUM (0) )  PAYMENTS1 ,
             CBA.BANK_ACCOUNT_NAME BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM
             BANK_ACCOUNT_NUM , BANK.PARTY_NAME BANK_NAME , BRANCH.PARTY_NAME
             BRANCH_NAME FROM APPS.AP_INVOICE_DISTRIBUTIONS_ALL APID ,
             APPS.AP_INVOICE_LINES_ALL APLA , APPS.AP_INVOICES_ALL API ,
             APPS.PO_VENDORS POV , APPS.CE_BANK_ACCOUNTS CBA , HZ_PARTIES BANK ,
             HZ_PARTIES BRANCH   WHERE API.INVOICE_ID =  APID.INVOICE_ID  AND
             APLA.INVOICE_ID =  APID.INVOICE_ID  AND APLA.LINE_NUMBER = 
             APID.INVOICE_LINE_NUMBER  AND API.VENDOR_ID =  POV.VENDOR_ID  AND
             CBA.BANK_ACCOUNT_ID =  :b2  AND CBA.ASSET_CODE_COMBINATION_ID = 
             APID.DIST_CODE_COMBINATION_ID  AND CBA.BANK_ID =  BANK.PARTY_ID  AND
             CBA.BANK_BRANCH_ID =  BRANCH.PARTY_ID  AND APID.MATCH_STATUS_FLAG = 
             'A'  AND NVL(API.PAYMENT_STATUS_FLAG , 'N' )  !=  'N'  AND
             APID.ACCOUNTING_DATE <  :b1  AND ( API.ORG_ID IS NULL   OR API.ORG_ID
             =  :b3 )   GROUP BY APID.ACCOUNTING_DATE , DECODE(POV.VENDOR_NAME ,
             'FD Investment' , 'FD' , 'I' )  , API.DOC_SEQUENCE_VALUE ,
             API.CREATION_DATE , API.INVOICE_NUM , TO_CHAR (API.INVOICE_DATE ,
             'DD-MON-YYYY' )  , POV.VENDOR_NAME ,
             API.ACCTS_PAY_CODE_COMBINATION_ID , NVL(API.DESCRIPTION ,
             API.INVOICE_NUM )  , CBA.BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM ,
             BANK.PARTY_NAME , BRANCH.PARTY_NAME  UNION ALL SELECT ACRH.GL_DATE
             GL_DATE , DECODE(ACRH.STATUS , 'REVERSED' , 'REV' ,
             DECODE(ACRH.CREATED_FROM , 'RATE ADJUSTMENT TRIGGER' , 'ERF' ,
             'Receipt' )  )  TYPE , ACR.DOC_SEQUENCE_VALUE VOUCHER_NO ,
             ACR.CREATION_DATE VOUCHER_DATE , ACR.RECEIPT_NUMBER CHECK_NUMBER ,
             TO_CHAR (ACR.RECEIPT_DATE , 'DD-MON-YYYY' )  CHECK_DATE ,
             NVL(SUBSTR(HP.PARTY_NAME , 1 , 50 )  , 'Miscellaneous Activity' ) 
             VENDOR_NAME , ACRH.ACCOUNT_CODE_COMBINATION_ID ACCOUNT_CODE ,
             'Customer Receipt' DESCRIPTION , TO_CHAR (SUM (DECODE(ACRH.STATUS ,
             'REVERSED' , NVL(ADA.ACCTD_AMOUNT_DR , 0 )  , 'CLEARED' ,
             NVL(ADA.ACCTD_AMOUNT_DR , 0 )  , 'REMITTED' , NVL(ADA.ACCTD_AMOUNT_DR
             , 0 )  , 'CONFIRMED' , NVL(ADA.ACCTD_AMOUNT_DR , 0 )  ) ) ,
             'fm999999999990.00' )  RECEIPTS , TO_CHAR (SUM (DECODE(ACRH.STATUS ,
             'REVERSED' , NVL(ADA.ACCTD_AMOUNT_CR , 0 )  , 'CLEARED' ,
             NVL(ADA.ACCTD_AMOUNT_CR , 0 )  , 'REMITTED' , NVL(ADA.ACCTD_AMOUNT_CR
             , 0 )  , 'CONFIRMED' , NVL(ADA.ACCTD_AMOUNT_CR , 0 )  ) ) ,
             'fm999999999990.00' )  PAYMENTS , TO_NUMBER (TO_CHAR (SUM (0) )  ) 
             PAYMENTS1 , CBA.BANK_ACCOUNT_NAME BANK_ACCOUNT_NAME ,
             CBA.BANK_ACCOUNT_NUM BANK_ACCOUNT_NUM , BANK.PARTY_NAME BANK_NAME ,
             BRANCH.PARTY_NAME BRANCH_NAME FROM APPS.AR_CASH_RECEIPT_HISTORY_ALL
             ACRH , APPS.AR_CASH_RECEIPTS_ALL ACR , APPS.HZ_PARTIES HP ,
             APPS.HZ_CUST_ACCOUNTS HCA , APPS.CE_BANK_ACCOUNTS CBA ,
             APPS.CE_BANK_ACCT_USES_ALL CBAU , APPS.AR_DISTRIBUTIONS_ALL ADA ,
             HZ_PARTIES BANK , HZ_PARTIES BRANCH   WHERE ACRH.CASH_RECEIPT_ID = 
             ACR.CASH_RECEIPT_ID  AND CBAU.BANK_ACCT_USE_ID = 
             ACR.REMIT_BANK_ACCT_USE_ID  AND CBAU.BANK_ACCOUNT_ID = 
             CBA.BANK_ACCOUNT_ID  AND HCA.PARTY_ID =  HP.PARTY_ID     AND
             ACR.PAY_FROM_CUSTOMER =  HCA.CUST_ACCOUNT_ID     AND CBA.BANK_ID =
             BANK.PARTY_ID  AND CBA.BANK_BRANCH_ID =  BRANCH.PARTY_ID  AND
             ACRH.STATUS IN ( 'CLEARED' , 'REMITTED' , 'CONFIRMED' , 'REVERSED' ) 
             AND ACRH.CASH_RECEIPT_HISTORY_ID =  ADA.SOURCE_ID  AND
             ADA.SOURCE_TABLE =  'CRH'  AND ADA.SOURCE_TYPE !=  'BANK_CHARGES' 
             AND CBA.BANK_ACCOUNT_ID =  :b2  AND ACRH.GL_DATE <  :b1  AND (
             ACR.ORG_ID IS NULL   OR ACR.ORG_ID =  :b3 )  AND ( (
             ACR.REVERSAL_DATE IS NOT NULL   AND ACRH.STATUS =  'REVERSED' )  OR (
             ACRH.CASH_RECEIPT_HISTORY_ID IN (SELECT INCRH.CASH_RECEIPT_HISTORY_ID
             FROM APPS.AR_CASH_RECEIPT_HISTORY_ALL INCRH   WHERE
             INCRH.CASH_RECEIPT_ID =  ACR.CASH_RECEIPT_ID  AND INCRH.STATUS != 
             'REVERSED'   )) )   GROUP BY ACRH.GL_DATE , DECODE(ACRH.STATUS ,
             'REVERSED' , 'REV' , DECODE(ACRH.CREATED_FROM , 'RATE ADJUSTMENT
             TRIGGER' , 'ERF' , 'Receipt' )  )  , ACR.DOC_SEQUENCE_VALUE ,
             ACR.CREATION_DATE , ACR.RECEIPT_NUMBER , TO_CHAR (ACR.RECEIPT_DATE ,
             'DD-MON-YYYY' )  , NVL(SUBSTR(HP.PARTY_NAME , 1 , 50 )  ,
             'Miscellaneous Activity' )  , ACRH.ACCOUNT_CODE_COMBINATION_ID ,
             'Customer Receipt' , CBA.BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM ,
             BANK.PARTY_NAME , BRANCH.PARTY_NAME  UNION ALL SELECT ACRH.GL_DATE
             GL_DATE , DECODE(ADJ.REASON_CODE ,  NULL  , 'ADJ' , ADJ.REASON_CODE
             ||  ' - ADJ'  )  TYPE , ACR.DOC_SEQUENCE_VALUE VOUCHER_NO ,
             ACR.CREATION_DATE VOUCHER_DATE ,  NULL  CHECK_NUMBER ,  NULL 
             CHECK_DATE , NVL(SUBSTR(HP.PARTY_NAME , 1 , 50 )  , 'Miscellaneous
             Activity' )  VENDOR_NAME , ACRH.ACCOUNT_CODE_COMBINATION_ID
             ACCOUNT_CODE , NVL(ACR.COMMENTS , ACR.RECEIPT_NUMBER )  DESCRIPTION ,
             TO_CHAR (SUM (-1 *  ADJ.AMOUNT ) , 'fm999999999990.00' )  RECEIPTS , 
             NULL  PAYMENTS , TO_NUMBER (TO_CHAR (SUM (0) )  )  PAYMENTS1 ,
             CBA.BANK_ACCOUNT_NAME BANK_ACCOUNT_NAME , CBA.BANK_ACCOUNT_NUM
             BANK_ACCOUNT_NUM , BANK.PARTY_NAME BANK_NAME , BRANCH.PARTY_NAME
             BRANCH_NAME FROM APPS.AR_CASH_RECEIPT_HISTORY_ALL ACRH ,
             APPS.AR_CASH_RECEIPTS_ALL ACR , APPS.HZ_PARTIES HP ,
             APPS.HZ_CUST_ACCOUNTS HCA , APPS.CE_BANK_ACCOUNTS CBA ,
             APPS.CE_BANK_ACCT_USES_ALL CBAU , APPS.AR_RECEIVABLE_APPLICATIONS_ALL
             APP , APPS.AR_ADJUSTMENTS_ALL ADJ , HZ_PARTIES BANK , HZ_PARTIES
             BRANCH   WHERE ACRH.CASH_RECEIPT_ID =  ACR.CASH_RECEIPT_ID  AND
             APP.CASH_RECEIPT_ID =  ACRH.CASH_RECEIPT_ID  AND APP.DISPLAY =  'Y' 
             AND APP.STATUS =  'APP'  AND APP.APPLICATION_TYPE =  'CASH'  AND
             ADJ.CUSTOMER_TRX_ID =  APP.APPLIED_CUSTOMER_TRX_ID  AND
             ADJ.CHARGEBACK_CUSTOMER_TRX_ID IS NULL   AND ADJ.TYPE =  'CHARGES' 
             AND CBAU.BANK_ACCT_USE_ID =  ACR.REMIT_BANK_ACCT_USE_ID  AND
             CBAU.BANK_ACCOUNT_ID =  CBA.BANK_ACCOUNT_ID  AND ACRH.CASH_RECEIPT_ID
             =  ACR.CASH_RECEIPT_ID  AND HCA.PARTY_ID =  HP.PARTY_ID     AND
             ACR.PAY_FROM_CUSTOMER =  HCA.CUST_ACCOUNT_ID     AND CBA.BANK_ID =
             BANK.PARTY_ID  AND CBA.BANK_BRANCH_ID =  BRANCH.PARTY_ID  AND
             ACRH.STATUS IN ( 'CLEARED' , 'REMITTED' , 'CONFIRMED' , 'REVERSED' ) 
             AND CBA.BANK_ACCOUNT_ID =  :b2  AND ACRH.GL_DATE <  :b1  AND (
             ACR.ORG_ID IS NULL   OR ACR.ORG_ID =  :b3 )  AND ( (
             ACR.REVERSAL_DATE IS NOT NULL   AND ACRH.STATUS =  'REVERSED' )  OR (
             ACRH.CASH_RECEIPT_HISTORY_ID IN (SELECT MIN
             (INCRH.CASH_RECEIPT_HISTORY_ID) FROM APPS.AR_CASH_RECEIPT_HISTORY_ALL
             INCRH   WHERE INCRH.CASH_RECEIPT_ID =  ACR.CASH_RECEIPT_ID  AND
             INCRH.STATUS !=  'REVERSED'   )) )   GROUP BY ACRH.GL_DATE ,
             DECODE(ADJ.REASON_CODE ,  NULL  , 'ADJ' , ADJ.REASON_CODE ||  ' -
             ADJ'  )  , ACR.DOC_SEQUENCE_VALUE , ACR.CREATION_DATE ,  NULL  , 
             NULL  , NVL(SUBSTR(HP.PARTY_NAME , 1 , 50 )  , 'Miscellaneous
             Activity' )  , ACRH.ACCOUNT_CODE_COMBINATION_ID , NVL(ACR.COMMENTS ,
             ACR.RECEIPT_NUMBER )  ,  NULL  , CBA.BANK_ACCOUNT_NAME ,
             CBA.BANK_ACCOUNT_NUM , BANK.PARTY_NAME , BRANCH.PARTY_NAME  UNION ALL
             SELECT PT.TRANSACTION_DATE GL_DATE , DECODE(PT.CREATED_FROM_DIR ,
             'PAYMENT' , 'Payment' )  TYPE , PT.TRXN_REFERENCE_NUMBER VOUCHER_NO ,
             TRUNC (PT.CREATION_DATE )  VOUCHER_DATE , PT.BANK_TRXN_NUMBER
             CHECK_NUMBER , TO_CHAR (PT.TRANSACTION_DATE , 'DD-MON-YYYY' ) 
             CHECK_DATE , DESTBA.BANK_ACCOUNT_NAME VENDOR_NAME ,
             GCC.CODE_COMBINATION_ID ACCOUNT_CODE , 'Inter Bank Transfer' ACC_DESC
             , '0' RECEIPTS , TO_CHAR (SUM (PT.PAYMENT_AMOUNT) )  PAYMENTS ,
             TO_NUMBER (SUM (PT.PAYMENT_AMOUNT) )  PAYMENTS1 ,
             SRCBA.BANK_ACCOUNT_NAME BANK_ACCOUNT_NAME , SRCBA.BANK_ACCOUNT_NUM
             BANK_ACCOUNT_NUM , BANK.PARTY_NAME BANK_NAME , BRANCH.PARTY_NAME
             BRANCH_NAME FROM APPS.HZ_ORGANIZATION_PROFILES SBANKORGPROFILE ,
             APPS.HZ_CODE_ASSIGNMENTS SBANKCA , APPS.HZ_PARTIES SBRANCHPARTY ,
             APPS.HZ_ORGANIZATION_PROFILES SBRANCHORGPROFILE ,
             APPS.HZ_CODE_ASSIGNMENTS SBRANCHCA , APPS.HZ_RELATIONSHIPS SBRREL ,
             APPS.HZ_CODE_ASSIGNMENTS SBRANCHTYPECA , APPS.HZ_CONTACT_POINTS
             SBRANCHCP , APPS.HZ_CONTACT_POINTS SEDICP ,
             APPS.HZ_ORGANIZATION_PROFILES DBANKORGPROFILE ,
             APPS.HZ_CODE_ASSIGNMENTS DBANKCA , APPS.HZ_PARTIES DBRANCHPARTY ,
             APPS.HZ_ORGANIZATION_PROFILES DBRANCHORGPROFILE ,
             APPS.HZ_CODE_ASSIGNMENTS DBRANCHCA , APPS.HZ_RELATIONSHIPS DBRREL ,
             APPS.HZ_CODE_ASSIGNMENTS DBRANCHTYPECA , APPS.HZ_CONTACT_POINTS
             DBRANCHCP , APPS.HZ_CONTACT_POINTS DEDICP ,
             APPS.CE_PAYMENT_TRANSACTIONS PT , APPS.CE_BANK_ACCOUNTS SRCBA ,
             APPS.CE_BANK_ACCOUNTS DESTBA , APPS.XLE_ENTITY_PROFILES SRCLE ,
             APPS.XLE_ENTITY_PROFILES DESTLE , APPS.GL_CODE_COMBINATIONS GCC ,
             APPS.HZ_PARTIES HZP , HZ_PARTIES BANK , HZ_PARTIES BRANCH   WHERE
             SYSDATE  BETWEEN TRUNC (SBANKORGPROFILE.EFFECTIVE_START_DATE )  AND
             NVL(TRUNC (SBANKORGPROFILE.EFFECTIVE_END_DATE )  , SYSDATE  +  1  )  
             AND SBANKCA.CLASS_CATEGORY =  'BANK_INSTITUTION_TYPE'  AND
             SBANKCA.CLASS_CODE IN ( 'BANK' , 'CLEARINGHOUSE' )  AND
             SBANKCA.OWNER_TABLE_NAME =  'HZ_PARTIES'  AND ( SBANKCA.STATUS =  'A'
             OR SBANKCA.STATUS IS NULL  )  AND SBANKCA.OWNER_TABLE_ID = 
             SBANKORGPROFILE.PARTY_ID  AND SBRANCHPARTY.PARTY_TYPE = 
             'ORGANIZATION'  AND SBRANCHPARTY.STATUS =  'A'  AND
             SBRANCHORGPROFILE.PARTY_ID =  SBRANCHPARTY.PARTY_ID  AND SYSDATE 
             BETWEEN TRUNC (SBRANCHORGPROFILE.EFFECTIVE_START_DATE )  AND
             NVL(TRUNC (SBRANCHORGPROFILE.EFFECTIVE_END_DATE )  , SYSDATE  +  1  )
             AND SBRANCHCA.CLASS_CATEGORY =  'BANK_INSTITUTION_TYPE'  AND
             SBRANCHCA.CLASS_CODE IN ( 'BANK_BRANCH' , 'CLEARINGHOUSE_BRANCH' ) 
             AND SBRANCHCA.OWNER_TABLE_NAME =  'HZ_PARTIES'  AND (
             SBRANCHCA.STATUS =  'A'  OR SBRANCHCA.STATUS IS NULL  )  AND
             SBRANCHCA.OWNER_TABLE_ID =  SBRANCHPARTY.PARTY_ID  AND
             SBANKORGPROFILE.PARTY_ID =  SBRREL.OBJECT_ID  AND
             SBRREL.RELATIONSHIP_TYPE =  'BANK_AND_BRANCH'  AND
             SBRREL.RELATIONSHIP_CODE =  'BRANCH_OF'  AND SBRREL.STATUS =  'A' 
             AND SBRREL.SUBJECT_TABLE_NAME =  'HZ_PARTIES'  AND
             SBRREL.SUBJECT_TYPE =  'ORGANIZATION'  AND SBRREL.OBJECT_TABLE_NAME =
             'HZ_PARTIES'  AND SBRREL.OBJECT_TYPE =  'ORGANIZATION'  AND
             SBRREL.SUBJECT_ID =  SBRANCHPARTY.PARTY_ID  AND
             SBRANCHTYPECA.CLASS_CATEGORY    =  'BANK_BRANCH_TYPE'  AND
             SBRANCHTYPECA.PRIMARY_FLAG    =  'Y'  AND
             SBRANCHTYPECA.OWNER_TABLE_NAME    =  'HZ_PARTIES'  AND
             SBRANCHTYPECA.OWNER_TABLE_ID    =  SBRANCHPARTY.PARTY_ID  AND

    Hi Karan,
    If your DB node has 48 GB and there are no other applications/program running on the server than I believe you still have for room for SGA/PGA resize.
    GSS was scheduled to run at 20% till last week ( runs every week) while i just made it to run for auto_sample_size by giving the percent as 0. I have checked and found that most of the tables had good stats , though one of the programs has started to take too much time after that. So for now i have reverted it back to 20%.
    10% - 20% is the percentage which I usually go with and this works well for me. Anyways that being said 10% default would do the trick in most cases.
    The update statement which is causing the trouble is a seeded oracle program so we have checking that with oracle. ( Auto_invoice_master).
    Yes as recommended, Please get confirmation from SR as well.
    Please also see note:
    How To Setup AutoInvoice For Optimal Performance (Doc ID 1083467.1)
    Troubleshooting AutoInvoice Performance Issues (Doc ID 1089196.1)
    Thanks &
    Best Regards

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

  • 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

  • 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

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

  • License position for ADDM, ASH and AWR

    What's the license position for ADDM, ASH & AWR ?
    I see these are freely available via OEM DB Control on my database instance. However I think I remember seeing ( though I can't find it now ) something that said they are chargeable ( under the Oracle Diagnostics pack license ? ). So even though they are freely accessible from OEM, if you use them you become liable for a license fee !
    I understood that AWR is really the replacement for Stats Pack but that Stats Pack is still in 11g because it is free ( whilst ADDM, ASH and AWR are not ) - is that correct ?
    I have not been able to find any documentation pertaining to the licensing / chargability ( or otherwise ) of these producs / features
    Can anyone clear the confusion ?

    Hi,
    Statspack is still free and the diagnostic features are licenced.
    Pricing details can be obtained from
    http://www.oracle.com/us/corporate/pricing/price-lists/index.html
    http://www.oracle.com/us/corporate/pricing/technology-price-list-070617.pdf
    -Aravind

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

  • 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