Qyery dying out

Question

How to optimize this query without using the expalin plan just by seeing the query some one can give some suggesstion
can we break this query in any way.if yes how.
samant
SELECT 'SERVICE_ORDER',
a.service_order_key,
GREATEST( NVL(a.soe_update_ts,'19000101000000'),
NVL(b.soe_update_ts,'19000101000000'),
NVL(c.soe_update_ts,'19000101000000'),
NVL(d.soe_update_ts,'19000101000000'),
NVL(e.soe_update_ts,'19000101000000'),
NVL(f.soe_update_ts,'19000101000000'),
NVL(g.soe_update_ts,'19000101000000'),
NVL(h.soe_update_ts,'19000101000000'),
NVL(k.soe_update_ts,'19000101000000'),
NVL(m.soe_update_ts,'19000101000000'),
NVL(q.soe_update_ts,'19000101000000'),
NVL(r.soe_update_ts,'19000101000000')) soe_update_ts,
a.source_system,
a.classic_objid,
a.service_order_id,
a.sales_order_key,
a.cancel_date,
b.part_status,
f.service_inst_flag,
f.domain,
c.contract_type,
NVL(c.contract_signed_date, '19000101000000'),
a.total_nrc total_nrc_local,
a.total_rc total_rc_local,
a.one_off_charge total_one_off_local,
b.installation_site_key,
d.territory_key,
a.schedule_type,
h.attribute_value,
a.service_id,
NVL(b.abp_service_start_date, '19000101000000'),
e.crd,
NVL(e.ccd, '19000101000000'),
e.icd,
c.currency,
f.speed,
e.acceptance_date,
g.service_end_date,
g.billing_start_date,
NVL(b.abp_service_end_date, '19000101000000'),
h.attribute_desc,
NVL(b.install_date, '19000101000000'),
NVL(g.create_ts, '19000101000000'),
k.org_name,
m.country_name,
e.ccd_failure_code,
e.ccd_failure_reason,
q.role_name,
a.del_ind,
h.attribute_set,
e.pad,
a.nrc_billing_account_key,
a.rc_billing_account_key,
a.usage_billing_account_key,
'' installing_csu_key,
k.bus_org_key
FROM RTS_SERVICE_ORDER_V a,
RTS_SITE_PART_V b,
RTS_SALES_ORDER_V c,
RTS_USR_TER_ROLE_V d,
RTS_KPI_V e,
RTS_X_PART_NUM_V f,
RTS_SERVICE_ORDER_ITEMS_V g,
RTS_PART_ATTRIBUTES_V h,
RTS_BUS_ORG_V j,
RTS_BUS_ORG_V k,
RTS_ADDRESS_V m,
RTS_USER_V n,
RTS_SITE_V p,
RTS_PART_ROLE_V q,
RTS_USR_BUS_ROLE_V r,
RTS_SITE_PART_V s
WHERE (a.watermark > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR b.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR c.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR d.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR e.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR f.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR g.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR h.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR k.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR m.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR q.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT')
OR r.WATERMARK > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT'))
AND a.service_order_key = g.service_order_key (+)
AND g.site_part_key = b.site_part_key (+)
AND b.part_num_key = f.part_num_key (+)
AND a.sales_order_key = c.sales_order_key (+)
AND n.user_key = d.user_key (+)
AND a.service_order_key = e.service_order_key (+)
AND a.sales_order_key = e.sales_order_key (+)
AND b.site_part_key = q.service_part_key (+)
AND q.tech_part_key = s.site_part_key (+)
AND s.site_part_key = h.site_part_key (+)
AND c.cust_bus_org_key = j.bus_org_key (+)
AND j.bt_ignite_id = k.org_id (+)
AND b.installation_site_key = p.site_key (+)
AND p.prim_address_key = m.address_key (+)
AND j.bus_org_key = r.bus_org_key (+)
AND UPPER(r.role_name (+)) = 'ACCOUNT MANAGER'
AND r.user_key = n.user_key (+)
AND UPPER(d.role_name (+)) = 'ACCOUNT MANAGER';

Answer 1

The first question I would ask is what is the question you are trying to answer here? By that I mean, is this desinged to answer a business question, or is it an attempt to create a "universal" view to answer any question a user or developer might have? If it is the latter, then the easiest way to optimize this is to not do it. Create several different queries/views each designed to answer a specific question, and letthe users/developers use those instead.
If it is the former, I would start by asking if you really need all those outer joins? Although there are cases where an outer join is required, I find it difficult to concieve of a situation where all the joins need to be outer joins. In fact, I believe that most of the outer joins are not required. The set of predicates
WHERE ?.watermark > RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT') ORwill eliminate the made up rows from the outer join, because NULL (the value that watermark will have if the row is made up because of the outer join) can never be greater than (not less than nor equal to, nor not equal to) anything.
Further, you are calling RTS_WATERMARK.GET_WATERMARK 12 times for each row in the query. I would try something along the lines of:
SELECT column_list
FROM table1, table2, ..., tableN
     (SELECT RTS_WATERMARK.GET_WATERMARK ('SOE_EXTRACT') wm
      FROM dual) z
WHERE < joins > and
      (a.watermark > z.wm OR
       b.watermark > z.wm OR
       . . .)Which will at worst get RTS_WATERMARK.GET_WATERMARK called once per row in the query, and at best once per query.
HTH
John