Comparing execution plans
Dear Team,
We want to avoid the full table scan on table XXTTD_APEX_EMBOOK_SUBLINES_TAB having 24.91 lakh. This table keeps on growing, lets say 2000 per day. While we are working to find alternative plans, We have added hint push_pred and got index range scan on this table. Plan shared below. But the index having poor clustering factor(not sure,please correct me). We kindly request you to share your thoughts.
SELECT HDR.EMBOOK_HEADER_ID
, APRV.MAX_APRV_REQUEST_ID MAX1_APRV
, SUB.MAX_SUB_REQUEST_ID MAX2_SUB
FROM XX_APEX.XXTTD_APEX_EMBOOK_HDR_TAB HDR