Any idea on Enhance commit usage ?

Question

Hi
Due to some performance related issues I have to use enhance commit .
I need to do intermittent commits --( I know it is not okay but rollback segment is too small ) for every 1000 records
the prev code was somewhat like
begin
for i in ( select * from table)
loop
do some calculations .....
then do an update on table 2 ...
then do an insert on table 3 .
if counter = 1000 then
commit; counter:=0;
else counter:=counter +1;
end if ;
end loop;
commit;
end ;
Now DBA has asked to use enhance commit to better performance as otherwise parallel users are facing issues .
I can then use commit write nowait or commit write immediate .
Can anyone help on this ?
Should i replace commit with enhance commit ?
Or should i add an enhance commit in the loop after the update?
SHUBH
Message was edited by:
SHUBH

Answer 1

Before using that method (intermittent commits inside a fetch loop), I will rather design and code a thread-safe parallel enabled process.
Which means that the process an be run via a loop, where on each iteration that process finds a new unique set of unprocessed rows to process. Or that multiple copies of the process can be started concurrently, without one treading on another.
I fail to see any sensible technical argument for writing code with intermittent commits in PL/SQL.