1366133.1 SQLHC 12.1.06 Report: sqlhc_20180322_092631_7n2f55zw68tqc_1_health_check.html

License    : T
Input      : 7n2f55zw68tqc
SIGNATURE  : 10337101761131282266
SIGNATUREF : 10337101761131282266
RDBMS      : 11.2.0.4.0
Platform   : LINUX
Database   : sdp
DBID       : 3172209698
Host       : dbsdp01
Instance   : 1
CPU_Count  : 16
Num CPUs   : 16
Num Cores  : 16
Num Sockets: 8
Block Size : 8192
OFE        : 11.2.0.4
DYN_SAMP   : 2
EBS        : ""
SIEBEL     : ""
PSFT       : ""
Date       : 2018-03-22/09:26:31
User       : SDPADM

Observations

Observations below are the outcome of several heath-checks on the schema objects accessed by your SQL and its environment. Review them carefully and take action when appropriate. Then re-execute your SQL and generate this report again.
# Type Name Observation Details
1 CBO PARAMETER CURSOR_SHARING CBO initialization parameter "cursor_sharing" with a non-default value of "force" as per V$SQL_OPTIMIZER_ENV. Review the correctness of this non-default value "force" for SQL_ID 7n2f55zw68tqc.
2 CBO PARAMETER _PGA_MAX_SIZE CBO initialization parameter "_pga_max_size" with a non-default value of "658620 KB" as per V$SQL_OPTIMIZER_ENV. Review the correctness of this non-default value "658620 KB" for SQL_ID 7n2f55zw68tqc.
3 DBMS_STATS DBA_AUTOTASK_CLIENT Automatic gathering of CBO statistics is enabled. Be aware that small sample sizes could produce poor quality histograms,
which combined with bind sensitive predicates could render suboptimal plans.
See 465787.1.
4 DBMS_STATS SYSTEM STATISTICS Workload CBO System Statistics are not gathered. CBO is using default values. Consider gathering workload system statistics using DBMS_STATS.GATHER_SYSTEM_STATS.
See also 465787.1.
5 PLAN OPTIMIZER_ENV SQL Area references 2 distinct CBO Environments for this one SQL. Distinct CBO Environments may produce different Plans.
6 PLAN OPTIMIZER_ENV GV$SQL references 2 distinct CBO Environments for this one SQL. Distinct CBO Environments may produce different Plans.
7 PLAN OPTIMIZER_ENV AWR references 3 distinct CBO Enviornments for this one SQL. Distinct CBO Environments may produce different Plans.
8 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
9 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
10 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
11 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
12 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
13 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100"<=:B1 AND "R"."EXPIRE_DATE"
14 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100"<=:B1 AND "R"."EXPIRE_DATE"
15 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100"<=:B1 AND "R"."EXPIRE_DATE"
16 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100"<=:B1 AND "R"."EXPIRE_DATE"
17 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100"<=:B1 AND "R"."EXPIRE_DATE"
18 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
19 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
20 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
21 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
22 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
23 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100"<=:B1 AND "R"."EXPIRE_DATE"
24 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100"<=:B1 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
25 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
26 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100">=:B2 AND "R"."EXPIRE_DATE"
27 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100">=:B2 AND "R"."EXPIRE_DATE"
28 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100"<=:B1 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
29 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100"<=:B1 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
30 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100"<=:B1 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
31 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100"<=:B1 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
32 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100"<=:B1 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
33 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100">=:B2 AND "R"."EXPIRE_DATE"
34 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"=:B2 AND "R"."AUTO_RENEW"=1) .
35 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"=:B2 AND "R"."AUTO_RENEW"=1) .
36 PLAN PREDICATES ORDERING There are plans with same PHV 2063729714 but different predicate ordering. Different ordering in the predicates for 2063729714 can affect the performance of this SQL,
focus on Step ID 8 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
37 PLAN PREDICATES ORDERING There are plans with same PHV 2063729714 but different predicate ordering. Different ordering in the predicates for 2063729714 can affect the performance of this SQL,
focus on Step ID 8 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100">=:B2 AND "R"."EXPIRE_DATE"
38 PLAN PREDICATES ORDERING There are plans with same PHV 2063729714 but different predicate ordering. Different ordering in the predicates for 2063729714 can affect the performance of this SQL,
focus on Step ID 8 predicates ("R"."MOD100">=:B2 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100"<=:B1 AND "R"."EXPIRE_DATE"
39 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
40 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
41 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
42 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
43 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"=:B2 AND "R"."AUTO_RENEW"=1) .
44 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100">=:B2 AND "R"."EXPIRE_DATE"
45 PLAN PREDICATES ORDERING There are plans with same PHV 2560158971 but different predicate ordering. Different ordering in the predicates for 2560158971 can affect the performance of this SQL,
focus on Step ID 6 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."START_RENEW_FLG"=0 AND "R"."MOD100">=:B2 AND "R"."EXPIRE_DATE"
46 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
47 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
48 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
49 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
50 PLAN PREDICATES ORDERING There are plans with same PHV 3006935772 but different predicate ordering. Different ordering in the predicates for 3006935772 can affect the performance of this SQL,
focus on Step ID 5 predicates ("R"."MOD100"<=:B1 AND "R"."RETRY_COUNT"=0 AND "R"."MOD100">=:B2 AND "R"."START_RENEW_FLG"=0 AND "R"."EXPIRE_DATE"
51 VERSION COUNT VERSION COUNT This SQL shows evidence of high version count of 89. Review Execution Plans for details.
52 TABLE SDP.REG Table contains 1 column(s) where the number of distinct values does not match the number of buckets. Review column statistics for this table and look for "Num Distinct" and "Num Buckets". If there are values missing from the frequency histogram you may have Bug 10174050.
If you are referencing in your predicates one of the missing values the CBO can over estimate table cardinality, and this may produce a sub-optimal plan.
You can either gather statistics with 100% or as a workaround: ALTER system/session "_fix_control"='5483301:OFF';
53 TABLE SDP.REG Table contains 1 column(s) where the number of buckets is 1 for a "FREQUENCY" histogram. Review column statistics for this table and look for "Num Buckets" and "Histogram". Possible Bugs 1386119, 4406309, 4495422, 4567767, 5483301 or 6082745.
If you are referencing in your predicates one of the missing values the CBO can over estimate table cardinality, and this may produce a sub-optimal plan.
You can either gather statistics with 100% or as a workaround: ALTER system/session "_fix_control"='5483301:OFF';
54 TABLE SDP.REG Table contains 4 column(s) with no popular values on a "HEIGHT BALANCED" histogram. A Height-balanced histogram with no popular values is not helpful nor desired. Consider dropping this histogram by collecting new CBO statistics while using METHOD_OPT with SIZE 1.
55 TABLE SDP.REG Table has stale statistics. Consider gathering table statistics using DBMS_STATS.GATHER_TABLE_STATS. See 465787.1.
56 TABLE SDP.SERVICE_LIST Table contains 2 column(s) where the number of buckets is 1 for a "FREQUENCY" histogram. Review column statistics for this table and look for "Num Buckets" and "Histogram". Possible Bugs 1386119, 4406309, 4495422, 4567767, 5483301 or 6082745.
If you are referencing in your predicates one of the missing values the CBO can over estimate table cardinality, and this may produce a sub-optimal plan.
You can either gather statistics with 100% or as a workaround: ALTER system/session "_fix_control"='5483301:OFF';
57 TABLE SDP.SERVICE_LIST Table contains 2 column(s) with no popular values on a "HEIGHT BALANCED" histogram. A Height-balanced histogram with no popular values is not helpful nor desired. Consider dropping this histogram by collecting new CBO statistics while using METHOD_OPT with SIZE 1.
58 INDEX SDP.INDX_REG_MOD100 Index referenced by an Execution Plan no longer exists. If a Plan references a missing index then this Plan can no longer be generated by the CBO.
59 INDEX SDP.REG_MOD_IDX Index referenced by an Execution Plan no longer exists. If a Plan references a missing index then this Plan can no longer be generated by the CBO.
60 TABLE PARTITION SDP.PACKAGE_CHARGE_LOG 119 out of 121 partition(s) with number of rows equal to zero according to partition's CBO statistics. If these table partitions are not empty, consider gathering table statistics using GRANULARITY=>GLOBAL AND PARTITION.
61 INDEX PARTITION SDP.INDX_PCKGCHRGLOG_CHRGDATE 119 out of 121 partition(s) with number of rows equal to zero according to partition's CBO statistics. If these index partitions are not empty, consider gathering table statistics using GRANULARITY=>GLOBAL AND PARTITION.
# Type Name Observation Details

SQL Text

SELECT X.* FROM ( SELECT * FROM ( SELECT R.REG_ID, R.PACKAGE_ID, R.SERVICE_ID, R.MSISDN, TO_CHAR(R.EXPIRE_DATE, 'yyyy/MM/dd hh24:mi:ss') EXPIRE_DATE, R.LAST_RETRY_DATE LAST_RENEW_DATE, R.RETRY_COUNT, R.SUBPACKAGE_ID, 0 NEXT_CHARGE_LEVEL, TO_CHAR(SYSDATE,'yyyymmddHH24') NEXT_RETRY_DATE FROM REG R WHERE 1 = 1 AND R.EXPIRE_DATE < SYSDATE AND R.MOD100 >= :B2 AND R.MOD100 <= :B1 AND R.START_RENEW_FLG = 0 AND R.RETRY_COUNT = 0 AND R.AUTO_RENEW = 1 ) EI WHERE 1 = 1 AND NOT EXISTS (SELECT 1 FROM PACKAGE_CHARGE_LOG CL WHERE CL.CHARGE_DATE = TRUNC (SYSDATE) AND CL.REG_ID = EI.REG_ID) ) X, SERVICE_LIST SL WHERE X.SERVICE_ID = SL.SERVICE_ID AND SL.SERVICE_RENEW_IP = :B3 AND ROWNUM <= 250

Tables Summary

Values below have two purposes:
1. Provide a quick view of the state of Table level CBO statistics, as well as their indexes and columns.
2. More easily allow the comparison of two systems that are believed to be similar.
# Table Name Owner Num Rows Table
Sample Size
Last Analyzed Indexes Avg Index
Sample Size
Table
Columns
Columns with
Histogram
Avg Column
Sample Size
1 PACKAGE_CHARGE_LOG SDP 1062683 1062683 22-MAR-18 08:49:26 1 1062683 2 1 533461
2 REG SDP 3724089 3724089 21-MAR-18 22:01:57 6 921608 21 19 328921
3 SERVICE_LIST SDP 275 275 11-MAR-18 22:06:50 2 275 12 4 204
# Table Name Owner Num Rows Table
Sample Size
Last Analyzed Indexes Avg Index
Sample Size
Table
Columns
Columns with
Histogram
Avg Column
Sample Size

Indexes Summary

Values below have two purposes:
1. Provide a quick view of the state of Index level CBO statistics, as well as their columns.
2. More easily allow the comparison of two systems that are believed to be similar.
This section includes data captured by AWR. If this is a stand-by read-only database then the AWR information below is from the Primary database.
# Table Name Table
Owner
Index Name Index
Owner
In MEM
Plan
In AWR
Plan
Num Rows Index
Sample Size
Last Analyzed Index
Columns
Columns with
Histogram
Avg Column
Sample Size
1 PACKAGE_CHARGE_LOG SDP INDX_PCKGCHRGLOG_CHRGDATE SDP 1062683 1062683 22-MAR-18 08:49:28 1 1 5401
2 REG SDP INDX_REG_AUTORENEW SDP YES YES 3896204 602959 21-MAR-18 22:02:22 1 1 14324
3 REG SDP INDX_REG_EXPIREDATE SDP 3722596 3722596 22-MAR-18 08:54:42 1 1 14323
4 REG SDP INDX_REG_MSISDN SDP 3964316 370365 21-MAR-18 22:02:21 1 1 14323
5 REG SDP INDX_REG_RETRYCOUNT SDP YES 3525173 346648 21-MAR-18 22:02:42 1 1 14323
6 REG SDP INDX_REG_SRVPCKGMODID SDP 3689745 304891 21-MAR-18 22:02:14 3 3 14323
7 REG SDP REG_PK SDP 3802874 182190 21-MAR-18 22:02:20 1 0 3724089
8 SERVICE_LIST SDP SERVICE_LIST_PK SDP 275 275 11-MAR-18 22:06:51 1 0 275
9 SERVICE_LIST SDP SERVICE_LIST__UN SDP 275 275 11-MAR-18 22:06:51 1 1 275
# Table Name Table
Owner
Index Name Index
Owner
In MEM
Plan
In AWR
Plan
Num Rows Index
Sample Size
Last Analyzed Index
Columns
Columns with
Histogram
Avg Column
Sample Size

1366133.1 SQLHC 12.1.06 2018-03-22/09:26:31 tool_date: 2014/01/30 executed by: SDPADM