DETAILED ADDM REPORT FOR TASK 'ADDM:3795507742_1_24447' WITH ID 68644 --------------------------------------------------------------------Analysis Period: Database ID/Instance: Database/Instance Names: Host

Name: Database Version: Snapshot Range: Database Time: Average Database Load: 21-FEB-2012 from 10:05:19 to 10:07:58 3795507742/1 QBILL/QBILL saturn 10.2.0.4.0 from 24446 to 24447 384 seconds 2.4 active sessions

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ FINDING 1: 47% impact (182 seconds) ----------------------------------SQL statements consuming significant database time were found. RECOMMENDATION 1: SQL Tuning, 29% benefit (113 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "0567mpmx8shpa". RELEVANT OBJECT: SQL statement with SQL_ID 0567mpmx8shpa and PLAN_HASH 3454304597 SELECT SUM(UI.AMOUNT) FROM QBILL.USER_INVOICES UI,USER_ORDERS UO WHERE UI.USER_ORDERS_ID = UO.ID AND UI.FLAG != 7 AND UO.SALES_MAN_ID = :b1 AND UI.AMOUNT > 0 AND (TRUNC(UI.ISSUE_DATE) >= :b2 OR :b2 IS NULL ) AND (TRUNC(UI.ISSUE_DATE) <= :b4 OR :b4 IS NULL ) RATIONALE: SQL statement with SQL_ID "0567mpmx8shpa" was executed 149 times and had an average elapsed time of 0.76 seconds. RECOMMENDATION 2: SQL Tuning, 4.6% benefit (18 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "adzd007q7us0w". RELEVANT OBJECT: SQL statement with SQL_ID adzd007q7us0w and PLAN_HASH 298606279 select * from (select null table_catalog, decode (o1.owner, 'PUBLIC', NULL, o1.owner) table_schema, o1.object_name table_name, decode(o1.owner,'SYS',decode(o1.object_type,'TABLE','SYSTEM TABLE','VIEW','SYSTEM VIEW',o1.object_type),'SYSTEM',decode(o1.object_type,'TABLE','SYSTEM TABLE','VIEW','SYSTEM VIEW',o1.object_type),o1.object_type) table_type, null table_guid, null description, null table_propid, null date_created, null date_modified from all_objects o1 where ((o1.object_type = 'TABLE' and o1.generated != 'Y') or o1.object_type = 'VIEW') union select null table_catalog, decode (o2.owner, 'PUBLIC', NULL, o2.owner) table_schema, o2.object_name table_name, o2.object_type table_type, null table_guid, null description, null table_propid, null date_created, null date_modified from all_objects o2, all_objects o3, all_synonyms s where o2.object_type = 'SYNONYM' and ((o3.object_type = 'TABLE' and o3.generated != 'Y') or o3.object_type = 'VIEW') and o2.owner = s.owner and o2.object_name = s.synonym_name and s.table_owner = o3.owner and s.table_name = o3.object_name) tables order by 4,2,3 RATIONALE: SQL statement with SQL_ID "adzd007q7us0w" was executed 4 times and had an average elapsed time of 4.6 seconds. RECOMMENDATION 3: SQL Tuning, 4.4% benefit (17 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "56rb4wp51ya5j". RELEVANT OBJECT: SQL statement with SQL_ID 56rb4wp51ya5j and PLAN_HASH 756008878 SELECT ROWID,get_service_name (service_id),ID,SERVICE_ID,INTERNET,CONN_SITE,(SELECT MOBILE_NR FROM CUST_INFO CF WHERE CF.CUST_ID=USER_SERVICES.CUST_ID ),CUST_ID,customers_pkg.GET_CUST_NAME (cust_id),STATUS,START_DT,END_DT,(SELECT pager_NR FROM CUST_INFO CF WHERE CF.CUST_ID=USER_SERVICES.CUST_ID ),SERV_PHONE FROM USER_SERVICES WHERE ID IN (select user_service_id from trans_log TG where TG.event_id=37 and TG.source_tbl in (168,219,259) and TG.user_service_id =USER_SERVICES.ID AND TG.ID IN (SELECT MAX(ID) FROM TRANS_LOG TG2 WHERE TG2.USER_SERVICE_ID=USER_SERVICES.ID)AND TG.TRANS_DT between '22-JAN-12' and '21-FEB-12') and STATUS='Z' AND SERVICES1.Serv_Ceased_With_Port_Conn(ID)='Y' RATIONALE: SQL statement with SQL_ID "56rb4wp51ya5j" was executed 1 times and had an average elapsed time of 17 seconds. RECOMMENDATION 4: SQL Tuning, 4.3% benefit (16 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID

file:///C|/Users/ashabbir/Desktop/addm_68644.html[2/21/2012 10:16:12 AM]

"9d338shrtmff6". RELEVANT OBJECT: SQL statement with SQL_ID 9d338shrtmff6 and PLAN_HASH 122909277 SELECT SUM(DECODE(SERVICE_COD,1,(USED_DURATION) / 3600 ,0)),SUM(DECODE(SERVICE_COD,2,(USED_DURATION) / 3600 ,0)) FROM USER_LOGIN_V WHERE LOG_NUMBER = :b1 AND (LOG_OUT_DATE BETWEEN :b2 AND :b3 OR :b4 = 'Y' ) RATIONALE: SQL statement with SQL_ID "9d338shrtmff6" was executed 1 times and had an average elapsed time of 16 seconds. RECOMMENDATION 5: SQL Tuning, 4.2% benefit (16 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "cp47z77xda5gv". RELEVANT OBJECT: SQL statement with SQL_ID cp47z77xda5gv and PLAN_HASH 756008878 SELECT ROWID,get_service_name (service_id),ID,SERVICE_ID,INTERNET,CONN_SITE,(SELECT MOBILE_NR FROM CUST_INFO CF WHERE CF.CUST_ID=USER_SERVICES.CUST_ID ),CUST_ID,customers_pkg.GET_CUST_NAME (cust_id),STATUS,START_DT,END_DT,(SELECT pager_NR FROM CUST_INFO CF WHERE CF.CUST_ID=USER_SERVICES.CUST_ID ),SERV_PHONE FROM USER_SERVICES WHERE ID IN (select user_service_id from trans_log TG where TG.event_id=37 and TG.source_tbl in (168,219,259) and TG.user_service_id =USER_SERVICES.ID AND TG.ID IN (SELECT MAX(ID) FROM TRANS_LOG TG2 WHERE TG2.USER_SERVICE_ID=USER_SERVICES.ID)AND TG.TRANS_DT between '22-JAN-12' and '21-FEB-12') and STATUS='Z' AND SERVICES1.Serv_Ceased_With_Port_Conn(ID)!='Y' FINDING 2: 46% impact (176 seconds) ----------------------------------Wait event "SQL*Net more data from client" in wait class "Network" was consuming significant database time. RECOMMENDATION 1: Application Analysis, 46% benefit (176 seconds) ACTION: Investigate the cause for high "SQL*Net more data from client" waits. Refer to Oracle's "Database Reference" for the description of this wait event. RECOMMENDATION 2: Application Analysis, 46% benefit (176 seconds) ACTION: Investigate the cause for high "SQL*Net more data from client" waits in Module "TOAD background query session". RECOMMENDATION 3: Application Analysis, 46% benefit (176 seconds) ACTION: Investigate the cause for high "SQL*Net more data from client" waits in Service "SYS$USERS". RECOMMENDATION 4: Application Analysis, 43% benefit (164 seconds) ACTION: Investigate the cause for high "SQL*Net more data from client" waits with P1 ("driver id") value "1413697536" and P2 ("#bytes") value "33". SYMPTOMS THAT LED TO THE FINDING: SYMPTOM: Wait class "Network" was consuming significant database time. (46% impact [176 seconds]) FINDING 3: 34% impact (129 seconds) ----------------------------------Time spent on the CPU by the instance was responsible for a substantial part of database time. RECOMMENDATION 1: SQL Tuning, 29% benefit (113 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "0567mpmx8shpa". RELEVANT OBJECT: SQL statement with SQL_ID 0567mpmx8shpa and PLAN_HASH 3454304597 SELECT SUM(UI.AMOUNT) FROM QBILL.USER_INVOICES UI,USER_ORDERS UO WHERE UI.USER_ORDERS_ID = UO.ID AND UI.FLAG != 7 AND UO.SALES_MAN_ID = :b1 AND UI.AMOUNT > 0 AND (TRUNC(UI.ISSUE_DATE) >= :b2 OR :b2 IS NULL ) AND (TRUNC(UI.ISSUE_DATE) <= :b4 OR :b4 IS NULL ) RATIONALE: SQL statement with SQL_ID "0567mpmx8shpa" was executed 149 times and had an average elapsed time of 0.76 seconds. RATIONALE: Average CPU used per execution was 0.74 seconds. RECOMMENDATION 2: SQL Tuning, 4.6% benefit (18 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "adzd007q7us0w". RELEVANT OBJECT: SQL statement with SQL_ID adzd007q7us0w and PLAN_HASH 298606279 select * from (select null table_catalog, decode (o1.owner, 'PUBLIC', NULL, o1.owner) table schema, o1.object name table name,
file:///C|/Users/ashabbir/Desktop/addm_68644.html[2/21/2012 10:16:12 AM]

decode(o1.owner,'SYS',decode(o1.object_type,'TABLE','SYSTEM TABLE','VIEW','SYSTEM VIEW',o1.object_type),'SYSTEM',decode(o1.object_type,'TABLE','SYSTEM TABLE','VIEW','SYSTEM VIEW',o1.object_type),o1.object_type) table_type, null table_guid, null description, null table_propid, null date_created, null date_modified from all_objects o1 where ((o1.object_type = 'TABLE' and o1.generated != 'Y') or o1.object_type = 'VIEW') union select null table_catalog, decode (o2.owner, 'PUBLIC', NULL, o2.owner) table_schema, o2.object_name table_name, o2.object_type table_type, null table_guid, null description, null table_propid, null date_created, null date_modified from all_objects o2, all_objects o3, all_synonyms s where o2.object_type = 'SYNONYM' and ((o3.object_type = 'TABLE' and o3.generated != 'Y') or o3.object_type = 'VIEW') and o2.owner = s.owner and o2.object_name = s.synonym_name and s.table_owner = o3.owner and s.table_name = o3.object_name) tables order by 4,2,3 RATIONALE: SQL statement with SQL_ID "adzd007q7us0w" was executed 4 times and had an average elapsed time of 4.6 seconds. RATIONALE: Average CPU used per execution was 4.4 seconds. FINDING 4: 30% impact (114 seconds) ----------------------------------Wait class "User I/O" was consuming significant database time. NO RECOMMENDATIONS AVAILABLE ADDITIONAL INFORMATION: Waits for I/O to temporary tablespaces were not consuming significant database time. The throughput of the I/O subsystem was not significantly lower than expected. FINDING 5: 7.6% impact (29 seconds) ----------------------------------Individual SQL statements responsible for significant user I/O wait were found. RECOMMENDATION 1: SQL Tuning, 4.3% benefit (16 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "9d338shrtmff6". RELEVANT OBJECT: SQL statement with SQL_ID 9d338shrtmff6 and PLAN_HASH 122909277 SELECT SUM(DECODE(SERVICE_COD,1,(USED_DURATION) / 3600 ,0)),SUM(DECODE(SERVICE_COD,2,(USED_DURATION) / 3600 ,0)) FROM USER_LOGIN_V WHERE LOG_NUMBER = :b1 AND (LOG_OUT_DATE BETWEEN :b2 AND :b3 OR :b4 = 'Y' ) RATIONALE: SQL statement with SQL_ID "9d338shrtmff6" was executed 1 times and had an average elapsed time of 16 seconds. RATIONALE: Average time spent in User I/O wait events per execution was 16 seconds. RECOMMENDATION 2: SQL Tuning, 4.2% benefit (16 seconds) ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID "cp47z77xda5gv". RELEVANT OBJECT: SQL statement with SQL_ID cp47z77xda5gv and PLAN_HASH 756008878 SELECT ROWID,get_service_name (service_id),ID,SERVICE_ID,INTERNET,CONN_SITE,(SELECT MOBILE_NR FROM CUST_INFO CF WHERE CF.CUST_ID=USER_SERVICES.CUST_ID ),CUST_ID,customers_pkg.GET_CUST_NAME (cust_id),STATUS,START_DT,END_DT,(SELECT pager_NR FROM CUST_INFO CF WHERE CF.CUST_ID=USER_SERVICES.CUST_ID ),SERV_PHONE FROM USER_SERVICES WHERE ID IN (select user_service_id from trans_log TG where TG.event_id=37 and TG.source_tbl in (168,219,259) and TG.user_service_id =USER_SERVICES.ID AND TG.ID IN (SELECT MAX(ID) FROM TRANS_LOG TG2 WHERE TG2.USER_SERVICE_ID=USER_SERVICES.ID)AND TG.TRANS_DT between '22-JAN-12' and '21-FEB-12') and STATUS='Z' AND SERVICES1.Serv_Ceased_With_Port_Conn(ID)!='Y' SYMPTOMS THAT LED TO THE FINDING: SYMPTOM: Wait class "User I/O" was consuming significant database time. (30% impact [114 seconds]) INFO: Waits for I/O to temporary tablespaces were not consuming significant database time. The throughput of the I/O subsystem was not significantly lower than expected. FINDING 6: 5.6% impact (21 seconds) ----------------------------------Hard parsing of SQL statements was consuming significant database time.

file:///C|/Users/ashabbir/Desktop/addm_68644.html[2/21/2012 10:16:12 AM]

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. Hard parses due to literal usage and cursor invalidation were not consuming significant database time. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ADDITIONAL INFORMATION ---------------------WARNING: The optimal SGA size could not be determined because of incomplete AWR snapshots. Wait class "Application" was not consuming significant database time. Wait class "Commit" was not consuming significant database time. Wait class "Concurrency" was not consuming significant database time. Wait class "Configuration" was not consuming significant database time. Session connect and disconnect calls were 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.

file:///C|/Users/ashabbir/Desktop/addm_68644.html[2/21/2012 10:16:12 AM]