ADDM Report for Task 'TASK_126571' ---------------------------------- Analysis Period --------------- AWR snapshot range from 645 to 649. Time period starts at 12-MAR-15 10.00.06 PM Time period ends at 13-MAR-15 02.00.09 AM Analysis Target --------------- Database 'SPRKPQA' with DB ID 911523440. Database version 11.2.0.3.0. ADDM performed an analysis of instance sprkpqa1, numbered 1 and hosted at mhva011.ezto.mhecloud.mcgraw-hill.com. Activity During the Analysis Period ----------------------------------- Total database time was 586309 seconds. The average number of active sessions was 40.71. Summary of Findings ------------------- Description Active Sessions Recommendation s Percent of Activity ---------------------------------------- ------------------- -------------- - 1 Top SQL Statements 19.65 | 48.28 4 2 Buffer Busy - Hot Objects 16.4 | 40.3 5 3 Global Cache Messaging 11.84 | 29.08 1 4 Top Segments by "User I/O" and "Cluster" 11.25 | 27.65 3 5 Index Block Split 6.6 | 16.2 5 6 ITL Waits 2.23 | 5.47 14 7 Hard Parse .84 | 2.05 0 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Findings and Recommendations ---------------------------- Finding 1: Top SQL Statements Impact is 19.65 active sessions, 48.28% 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 8.21 active sessions, 20.17% of total activity. -------------------------------------------------------------------- Action Run SQL Tuning Advisor on the INSERT statement with SQL_ID "f9xc28hmrx2mq". Additionally, investigate this statement for possible performance improvements. You can supplement the information given here with an ASH report for this SQL_ID. Related Object SQL statement with SQL_ID f9xc28hmrx2mq. INSERT INTO LEARN_SMART_ASSIGNMENT_XREF( ASSIGNMENT_ID , NATIVE_REFERENCE_ID , NATIVE_ISBN , TIME_REMAINING ) VALUES( :1 , :2 , :3 , :4 ) Rationale The SQL spent 49% of its database time on CPU, I/O and Cluster waits. This part of database time may be improved by the SQL Tuning Advisor. Look at data given below and an ASH report for further performance improvements. 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 "f9xc28hmrx2mq" was executed 35569 times and had an average elapsed time of 3.2 seconds. Rationale At least 129 distinct execution plans were utilized for this SQL statement during the analysis period. Rationale Waiting for event "enq: TX - index contention" in wait class "Concurrency" accounted for 25% of the database time spent in processing the SQL statement with SQL_ID "f9xc28hmrx2mq". Rationale Waiting for event "enq: TX - allocate ITL entry" in wait class "Configuration" accounted for 21% of the database time spent in processing the SQL statement with SQL_ID "f9xc28hmrx2mq". Rationale I/O and Cluster wait for INDEX "SPARKPROD.SYS_C0023032" with object ID 85839 consumed 47% of the database time spent on this SQL statement. Recommendation 2: SQL Tuning Estimated benefit is 5.34 active sessions, 13.11% of total activity. -------------------------------------------------------------------- Action Run SQL Tuning Advisor on the INSERT statement with SQL_ID "cqb5wdutfsy5u". Additionally, investigate this statement for possible performance improvements. You can supplement the information given here with an ASH report for this SQL_ID. Related Object SQL statement with SQL_ID cqb5wdutfsy5u. INSERT INTO ASSIGNMENT (ASSIGNMENT_ID, CATEGORY_TYPE, TITLE, START_DATE, DUE_DATE, WEIGHT, MAX_SCORE, ASSIGNMENT_TYPE, DURATION, DISPLAY_TYPE, ASSIGNMENT_NOTE, WEIGHT_YN, SEQUENCE_NO, PUBLISH_TYPE, UPDATED_DATE, CREATED_DATE, ATTACHMENT_ID, PROCTOR_PASSWORD, PARENT_ASSIGNMENT_ID, LINKED_TO_ASSIGNMENT, PRIMARY_INSTRUCTOR_ID,ACCESS_LEVEL,STATUS,ISPOLICYOVERRIDDEN,CATEGORY _ID, PARENT_SECTION_ID, IS_LIBRARY_ASSIGNMENT, PROVIDER, PREVIEW_URL, UUID, HAS_CONTENT_POLICIES, ARE_CONTENT_POLICIES_DIRTY,MANUAL_GRADE_REQUIRED,DESTINATION_ID,IS_CH AT_ASSIGNMENT,SPEECH_VERSION, ASSIGNMENT_TYPE_ID) (SELECT :B2 , CATEGORY_TYPE, TITLE, START_DATE, DUE_DATE, WEIGHT, MAX_SCORE, ASSIGNMENT_TYPE, DURATION, DISPLAY_TYPE, ASSIGNMENT_NOTE, WEIGHT_YN, SEQUENCE_NO, PUBLISH_TYPE, SYSDATE, SYSDATE, ATTACHMENT_ID, PROCTOR_PASSWORD,PARENT_ASSIGNMENT_ID, LINKED_TO_ASSIGNMENT, :B7 , CASE ACCESS_LEVEL WHEN 'course' THEN 'instructor' WHEN 'instructor' THEN 'instructor' WHEN 'section' THEN 'section' WHEN 'None' THEN 'None' END, STATUS,ISPOLICYOVERRIDDEN, CASE GET_NEW_CUSTOME_ALA_ID(CATEGORY_ID, :B6 , :B5 ) WHEN -1 THEN CATEGORY_ID ELSE GET_NEW_CUSTOME_ALA_ID(CATEGORY_ID, :B6 , :B5 ) END , :B4 , 'N', PROVIDER, CASE WHEN :B3 = 'VIDEO' THEN '/connect/previewVideoAssignment.do?assignmentId=' || :B2 WHEN :B3 = 'ALE' THEN '/connect/previewAleAssignment.do?assignmentId=' || :B2 ELSE '/connect/previewAssignment.do?assignmentId=' || :B2 END, UUID ,HAS_CONTENT_POLICIES, ARE_CONTENT_POLICIES_DIRTY,MANUAL_GRADE_REQUIRED,DESTINATION_ID,IS_CH AT_ASSIGNMENT,SPEECH_VERSION, ASSIGNMENT_TYPE_ID FROM ASSIGNMENT WHERE ASSIGNMENT_ID = :B1 ) Rationale The SQL spent 57% of its database time on CPU, I/O and Cluster waits. This part of database time may be improved by the SQL Tuning Advisor. Look at data given below and an ASH report for further performance improvements. 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 "cqb5wdutfsy5u" was executed 92351 times and had an average elapsed time of 0.82 seconds. Rationale Waiting for event "enq: TX - index contention" in wait class "Concurrency" accounted for 37% of the database time spent in processing the SQL statement with SQL_ID "cqb5wdutfsy5u". Rationale I/O and Cluster wait for INDEX "SPARKPROD.ASSIGNMENT4_PK" with object ID 84463 consumed 48% of the database time spent on this SQL statement. Rationale Top level calls to execute the PL/SQL statement with SQL_ID "57ytz63dxg58a" are responsible for 100% of the database time spent on the INSERT statement with SQL_ID "cqb5wdutfsy5u". Related Object SQL statement with SQL_ID 57ytz63dxg58a. begin hm_copy_public_assignments(:1 , :2 , :3 , :4 , :5 , :6 , :7 ,:8 ,:9 ,:10 ); end; Recommendation 3: SQL Tuning Estimated benefit is 4.03 active sessions, 9.91% of total activity. ------------------------------------------------------------------- Action Run SQL Tuning Advisor on the INSERT statement with SQL_ID "59p8bs8dz4qm5". Additionally, investigate this statement for possible performance improvements. You can supplement the information given here with an ASH report for this SQL_ID. Related Object SQL statement with SQL_ID 59p8bs8dz4qm5. INSERT INTO EVTMSGJOB.E_EVENT( EVENT_ID, EVENT_TYPE_ID, EVENT_TIME, EVENT_TRIG_TABLE_ID, SECTION_ID, ACTIVITY_ID, ACTIVITY_ATTEMPT_NUM, STUDENT_ID ) VALUES( EVTMSGJOB.E_EVENT_SEQ.NEXTVAL, :B6 , SYSDATE, :B5 , :B1 , :B2 , :B3 , :B4 ) Rationale The SQL spent 51% of its database time on CPU, I/O and Cluster waits. This part of database time may be improved by the SQL Tuning Advisor. Look at data given below and an ASH report for further performance improvements. 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 "59p8bs8dz4qm5" was executed 171973 times and had an average elapsed time of 0.33 seconds. Rationale Waiting for event "enq: TX - index contention" in wait class "Concurrency" accounted for 39% of the database time spent in processing the SQL statement with SQL_ID "59p8bs8dz4qm5". Recommendation 4: SQL Tuning Estimated benefit is 2.07 active sessions, 5.1% of total activity. ------------------------------------------------------------------ Action Run SQL Tuning Advisor on the INSERT statement with SQL_ID "fcd4q6npcbdw6". Additionally, investigate this statement for possible performance improvements. You can supplement the information given here with an ASH report for this SQL_ID. Related Object SQL statement with SQL_ID fcd4q6npcbdw6. INSERT INTO EVTMSGJOB.E_EVENT( EVENT_ID, EVENT_TYPE_ID, EVENT_TIME, EVENT_TRIG_TABLE_ID, SECTION_ID, ASSIGNMENT_ID ) VALUES( EVTMSGJOB.E_EVENT_SEQ.NEXTVAL, :B4 , SYSDATE, :B3 , :B1 , :B2 ) Rationale The SQL spent 48% of its database time on CPU, I/O and Cluster waits. This part of database time may be improved by the SQL Tuning Advisor. Look at data given below and an ASH report for further performance improvements. 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 "fcd4q6npcbdw6" was executed 93042 times and had an average elapsed time of 0.32 seconds. Rationale Waiting for event "enq: TX - index contention" in wait class "Concurrency" accounted for 41% of the database time spent in processing the SQL statement with SQL_ID "fcd4q6npcbdw6". Rationale Top level calls to execute the PL/SQL statement with SQL_ID "7f00f8wsawkwj" are responsible for 76% of the database time spent on the INSERT statement with SQL_ID "fcd4q6npcbdw6". Related Object SQL statement with SQL_ID 7f00f8wsawkwj. begin copy_section_assignment_xref(:1 , :2 , :3 , :4 ); end; Finding 2: Buffer Busy - Hot Objects Impact is 16.4 active sessions, 40.3% of total activity. -------------------------------------------------------- Read and write contention on database blocks was consuming significant database time. Recommendation 1: Schema Changes Estimated benefit is 5.45 active sessions, 13.39% of total activity. -------------------------------------------------------------------- Action Consider partitioning the INDEX "SPARKPROD.ASSIGNMENT4_PK" with object ID 84463 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 84463. Recommendation 2: Schema Changes Estimated benefit is 5.27 active sessions, 12.94% of total activity. -------------------------------------------------------------------- Action Consider partitioning the INDEX "SPARKPROD.SYS_C0023032" with object ID 85839 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 85839. Recommendation 3: Schema Changes Estimated benefit is 1.17 active sessions, 2.88% of total activity. ------------------------------------------------------------------- Action Consider partitioning the INDEX PARTITION "EVTMSGJOB.E_EVT_EVENT_TIME_ID_IDX.SYS_P5131" with object ID 217038 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 217038. Recommendation 4: Schema Changes Estimated benefit is .81 active sessions, 2% of total activity. --------------------------------------------------------------- Action Consider partitioning the INDEX PARTITION "EVTMSGJOB.E_EVT_EVENT_TIME_ID_IDX.SYS_P5071" with object ID 213403 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 213403. Recommendation 5: Schema Changes Estimated benefit is .73 active sessions, 1.79% of total activity. ------------------------------------------------------------------ Action Consider partitioning the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P5131" with object ID 217026 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 217026. Symptoms That Led to the Finding: --------------------------------- Read and write contention on database blocks was consuming significant database time. Impact is 16.4 active sessions, 40.3% of total activity. Inter-instance messaging was consuming significant database time on this instance. Impact is 11.84 active sessions, 29.08% of total activity. Wait class "Cluster" was consuming significant database time. Impact is 16.19 active sessions, 39.76% of total activity. Wait class "Concurrency" was consuming significant database time. Impact is 7.36 active sessions, 18.07% of total activity. Finding 3: Global Cache Messaging Impact is 11.84 active sessions, 29.08% of total activity. ---------------------------------------------------------- Inter-instance messaging was consuming significant database time on this instance. Recommendation 1: Application Analysis Estimated benefit is 11.84 active sessions, 29.08% of total activity. --------------------------------------------------------------------- Action Look at the "Top SQL Statements" finding for SQL statements consuming significant time on Cluster waits. For example, the INSERT statement with SQL_ID "f9xc28hmrx2mq" is responsible for 33% of Cluster wait during the analysis period. Symptoms That Led to the Finding: --------------------------------- Wait class "Cluster" was consuming significant database time. Impact is 16.19 active sessions, 39.76% of total activity. Finding 4: Top Segments by "User I/O" and "Cluster" Impact is 11.25 active sessions, 27.65% of total activity. ---------------------------------------------------------- Individual database segments responsible for significant "User I/O" and "Cluster" waits were found. Recommendation 1: Segment Tuning Estimated benefit is 5.2 active sessions, 12.77% of total activity. ------------------------------------------------------------------- Action Investigate application logic involving I/O on INDEX "SPARKPROD.ASSIGNMENT4_PK" with object ID 84463. Related Object Database object with ID 84463. Action Look at the "Top SQL Statements" finding for SQL statements consuming significant I/O on this segment. For example, the INSERT statement with SQL_ID "cqb5wdutfsy5u" is responsible for 49% of "User I/O" and "Cluster" waits for this segment. Rationale The I/O usage statistics for the object are: 0 full object scans, 14309 physical reads, 2722 physical writes and 0 direct reads. Recommendation 2: Segment Tuning Estimated benefit is 4.95 active sessions, 12.17% of total activity. -------------------------------------------------------------------- Action Investigate application logic involving I/O on INDEX "SPARKPROD.SYS_C0023032" with object ID 85839. Related Object Database object with ID 85839. Action Look at the "Top SQL Statements" finding for SQL statements consuming significant I/O on this segment. For example, the INSERT statement with SQL_ID "f9xc28hmrx2mq" is responsible for 78% of "User I/O" and "Cluster" waits for this segment. Rationale The I/O usage statistics for the object are: 0 full object scans, 388 physical reads, 977 physical writes and 0 direct reads. Recommendation 3: Segment Tuning Estimated benefit is 1.1 active sessions, 2.71% of total activity. ------------------------------------------------------------------ Action Investigate application logic involving I/O on INDEX PARTITION "EVTMSGJOB.E_EVT_EVENT_TIME_ID_IDX.SYS_P5131" with object ID 217038. Related Object Database object with ID 217038. Rationale The I/O usage statistics for the object are: 0 full object scans, 128 physical reads, 1039 physical writes and 0 direct reads. Symptoms That Led to the Finding: --------------------------------- Wait class "User I/O" was consuming significant database time. Impact is 1.54 active sessions, 3.77% of total activity. Finding 5: Index Block Split Impact is 6.6 active sessions, 16.2% of total activity. ------------------------------------------------------- Contention on index block splits was consuming significant database time. Recommendation 1: Schema Changes Estimated benefit is 1.76 active sessions, 4.33% of total activity. ------------------------------------------------------------------- Action Consider hash partitioning the INDEX "SPARKPROD.ASSIGNMENT4_PK" with object ID 84463 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 84463. Recommendation 2: Schema Changes Estimated benefit is 1.62 active sessions, 3.97% of total activity. ------------------------------------------------------------------- Action Consider hash partitioning the INDEX "SPARKPROD.SYS_C0023032" with object ID 85839 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 85839. Recommendation 3: Schema Changes Estimated benefit is .98 active sessions, 2.42% of total activity. ------------------------------------------------------------------ Action Consider hash partitioning the INDEX PARTITION "EVTMSGJOB.E_EVT_EVENT_TIME_ID_IDX.SYS_P5131" with object ID 217038 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 217038. Recommendation 4: Schema Changes Estimated benefit is .53 active sessions, 1.3% of total activity. ----------------------------------------------------------------- Action Consider hash partitioning the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P5131" with object ID 217026 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 217026. Recommendation 5: Schema Changes Estimated benefit is .42 active sessions, 1.04% of total activity. ------------------------------------------------------------------ Action Consider hash partitioning the INDEX PARTITION "EVTMSGJOB.E_EVT_EVENT_TIME_ID_IDX.SYS_P5071" with object ID 213403 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 213403. Symptoms That Led to the Finding: --------------------------------- Wait class "Concurrency" was consuming significant database time. Impact is 7.36 active sessions, 18.07% of total activity. Finding 6: ITL Waits Impact is 2.23 active sessions, 5.47% of total activity. -------------------------------------------------------- Waits for ITL enqueue were consuming significant database time. Recommendation 1: Schema Changes Estimated benefit is 1.25 active sessions, 3.06% of total activity. ------------------------------------------------------------------- Action Consider increasing INITRANS for the INDEX "SPARKPROD.SYS_C0023032" with object ID 85839 without rebuilding it. Related Object Database object with ID 85839. Rationale The SQL statement with SQL_ID "f9xc28hmrx2mq" was found waiting for the Interested Transaction List (ITL) enqueue on the INDEX "SPARKPROD.SYS_C0023032" with object ID 85839. Related Object SQL statement with SQL_ID f9xc28hmrx2mq. INSERT INTO LEARN_SMART_ASSIGNMENT_XREF( ASSIGNMENT_ID , NATIVE_REFERENCE_ID , NATIVE_ISBN , TIME_REMAINING ) VALUES( :1 , :2 , :3 , :4 ) Recommendation 2: Schema Changes Estimated benefit is 1.25 active sessions, 3.06% of total activity. ------------------------------------------------------------------- Action Consider rebuilding the INDEX "SPARKPROD.SYS_C0023032" with object id 85839 using a higher value for INITRANS. Related Object Database object with ID 85839. Rationale The SQL statement with SQL_ID "f9xc28hmrx2mq" was found waiting for the Interested Transaction List (ITL) enqueue on the INDEX "SPARKPROD.SYS_C0023032" with object ID 85839. Related Object SQL statement with SQL_ID f9xc28hmrx2mq. INSERT INTO LEARN_SMART_ASSIGNMENT_XREF( ASSIGNMENT_ID , NATIVE_REFERENCE_ID , NATIVE_ISBN , TIME_REMAINING ) VALUES( :1 , :2 , :3 , :4 ) Recommendation 3: Schema Changes Estimated benefit is 1.25 active sessions, 3.06% of total activity. ------------------------------------------------------------------- Action Consider hash partitioning the INDEX "SPARKPROD.SYS_C0023032" with object ID 85839 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 85839. Rationale The SQL statement with SQL_ID "f9xc28hmrx2mq" was found waiting for the Interested Transaction List (ITL) enqueue on the INDEX "SPARKPROD.SYS_C0023032" with object ID 85839. Related Object SQL statement with SQL_ID f9xc28hmrx2mq. INSERT INTO LEARN_SMART_ASSIGNMENT_XREF( ASSIGNMENT_ID , NATIVE_REFERENCE_ID , NATIVE_ISBN , TIME_REMAINING ) VALUES( :1 , :2 , :3 , :4 ) Recommendation 4: Schema Changes Estimated benefit is .13 active sessions, .33% of total activity. ----------------------------------------------------------------- Action Consider increasing INITRANS for the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P5131" with object ID 217026 without rebuilding it. Related Object Database object with ID 217026. Recommendation 5: Schema Changes Estimated benefit is .13 active sessions, .33% of total activity. ----------------------------------------------------------------- Action Consider rebuilding the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P5131" with object id 217026 using a higher value for INITRANS. Related Object Database object with ID 217026. Recommendation 6: Schema Changes Estimated benefit is .13 active sessions, .33% of total activity. ----------------------------------------------------------------- Action Consider hash partitioning the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P5131" with object ID 217026 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 217026. Recommendation 7: Schema Changes Estimated benefit is .1 active sessions, .25% of total activity. ---------------------------------------------------------------- Action Consider increasing INITRANS for the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P5071" with object ID 213401 without rebuilding it. Related Object Database object with ID 213401. Recommendation 8: Schema Changes Estimated benefit is .1 active sessions, .25% of total activity. ---------------------------------------------------------------- Action Consider rebuilding the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P5071" with object id 213401 using a higher value for INITRANS. Related Object Database object with ID 213401. Recommendation 9: Schema Changes Estimated benefit is .1 active sessions, .25% of total activity. ---------------------------------------------------------------- Action Consider hash partitioning the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P5071" with object ID 213401 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 213401. Recommendation 10: Schema Changes Estimated benefit is .04 active sessions, .09% of total activity. ----------------------------------------------------------------- Action Consider increasing INITRANS for the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P4951" with object ID 207351 without rebuilding it. Related Object Database object with ID 207351. Recommendation 11: Schema Changes Estimated benefit is .04 active sessions, .09% of total activity. ----------------------------------------------------------------- Action Consider rebuilding the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P4951" with object id 207351 using a higher value for INITRANS. Related Object Database object with ID 207351. Recommendation 12: Schema Changes Estimated benefit is .04 active sessions, .09% of total activity. ----------------------------------------------------------------- Action Consider hash partitioning the INDEX PARTITION "EVTMSGJOB.E_EVENT_PK.SYS_P4951" with object ID 207351 in a manner that will evenly distribute concurrent DML across multiple partitions. Related Object Database object with ID 207351. Recommendation 13: Schema Changes Estimated benefit is .02 active sessions, .06% of total activity. ----------------------------------------------------------------- Action Consider increasing INITRANS for the TABLE PARTITION "EVTMSGJOB.E_EVENT.SYS_P5071" with object ID 213400 without rebuilding it. Related Object Database object with ID 213400. Action Consider increasing PCTFREE for the TABLE PARTITION "EVTMSGJOB.E_EVENT.SYS_P5071" with object ID 213400. Related Object Database object with ID 213400. Recommendation 14: Schema Changes Estimated benefit is .02 active sessions, .06% of total activity. ----------------------------------------------------------------- Action Consider rebuilding the TABLE PARTITION "EVTMSGJOB.E_EVENT.SYS_P5071" with object id 213400 using a higher value for INITRANS. Related Object Database object with ID 213400. Action Consider rebuilding the TABLE PARTITION "EVTMSGJOB.E_EVENT.SYS_P5071" with object ID 213400 using a higher value for PCTFREE. Related Object Database object with ID 213400. Symptoms That Led to the Finding: --------------------------------- Wait class "Configuration" was consuming significant database time. Impact is 2.23 active sessions, 5.48% of total activity. Finding 7: Hard Parse Impact is .84 active sessions, 2.05% of total activity. ------------------------------------------------------- Hard parsing of SQL statements was consuming significant database time. 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. No recommendations are available. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Additional Information ---------------------- Miscellaneous Information ------------------------- Wait class "Application" was not consuming significant database time. Wait class "Commit" was not consuming significant database time. CPU was not a bottleneck for the instance. Wait class "Network" was not consuming significant database time. The network latency of the cluster interconnect was within acceptable limits of 1 milliseconds. Session connect and disconnect calls were not consuming significant database time.