My update query is taking more tablespace.. so please advice

Question

Hi All,
My update statement is taking more tablespace suddently. so I got error 'unable to extend the tablespace'. After extended the tablespace, I got completed..but those extended tablespace also got filled immetiately. Can you guys please suggest me for some solutions for this case.
"-- Proc to update the lvl 2 dfus in the dfuprojdraftstatic table with cust orders
procedure update_lvl2_dpds_custorders is
cv cur_type;
v_lvl1_dmdgroup varchar2(50) := null;
v_lvl1_loc varchar2(50) := null;
v_first_one number;
a number;
begin
for x in (select distinct dmdgroup lvl2_dmdgroup, loc lvl2_loc
from dfuprojdraftstatic s
where (dmdunit,dmdgroup,loc) in (select dmdunit,dmdgroup,loc from dfuview v
where u_dfu_lvl = 2)
and dmdunit in (select dmdunit from dmdunit
where u_moe = in_moe) ) loop
v_first_one := 1;
-- Using dynamic sql, loop through the lvl 1 dmdgroups and locs for this lvl 2 dmdgroup and loc
--open cv for v_sql_stmt using v_cntry_cd, x.lvl2_dmdgroup, v_cntry_cd, x.lvl2_loc;
open cv for v_sql_stmt using x.lvl2_dmdgroup,in_moe;
loop
fetch cv into v_lvl1_dmdgroup, v_lvl1_loc;
exit when cv%notfound;
UPDATE dfuprojdraftstatic s
SET u_cust_ordr = (SELECT decode(v_first_one, 1, 0, u_cust_ordr) + nvl(sum(qty), 0)
FROM cust_orders o, mars_week_cal c
WHERE o.mrkt_moe = in_moe
AND o.dmdunit = s.dmdunit
AND o.dmdgroup = v_lvl1_dmdgroup
AND o.loc = v_lvl1_loc
AND o.start_date BETWEEN c.week_start_dat AND c.week_end_dat
AND c.week_start_dat = s.startdate
WHERE startdate >= v_max_dpd
AND (dmdunit,dmdgroup,loc) in (select dmdunit,dmdgroup,loc from dfuview v
where u_dfu_lvl = 2 )
AND dmdunit in (select dmdunit from dmdunit
where u_moe = in_moe )
AND s.dmdgroup = x.lvl2_dmdgroup
AND s.loc = x.lvl2_loc;
dbms_output.put_line('A '||a+1);
if v_first_one = 1 then
v_first_one := 0;
end if;
end loop;
close cv;
end loop;
commit;
end; -- update_lvl2_dpds_custorders
Thanks and Regards,
Sudhakar.M

Answer 1

Without seeing the full code like, for example, the definition of v_sql_stmt, and without knowing you tables and data, my guess would be that, based on the code provided, the update process is extremely inefficient and is likely updating the same row multiple times in this procedure, and even more likely in the entire set of provedures.
Based on the erro message, it appears that you are running a package called batch_upd_dfuprojdraftstatic. Based on the name of the procedure you show, I also suspect that there are several other procedures that update single columns of dfuprojdraftstatic one after the other.
I know that the table dfuprojdraftstatic is at least part of the base for a materialized view (mlog$_dfuprojdraftstatic is the materialized view log attached to the table to track changes for refreshing the materialized view). For each update you issue, Oracle creates a record in the materialized view log tracking what changed. If you do update col1, that creates a record in the log for each row , if you subsequently do update col2 that creates a second record for each row. However, if you do update col1, col2, that only creates a single record for each row. So, updating all of the columns requiring updates at the same time will reduce the number of the materialized view log entries, which should reduce the space required.
You may alos want to loko at purging some of the data form the log using the dbms_mview package.
John