Strange Runtime between to Log-Outputs

Question

Hi,
I'm working on a PL-SQL Package with very strange Runtimes. In the Log-File can be read that most of the operation time is spend between two Log-Outputs. That is very surprising to me.
Below you can see the structure of the Package:
PROCEDURE local_Procedure
Cursor c define;
IS
BEGIN
FETCH c BULK COLLECT ... LIMIT ...
LOOP
FORALL UPDATE
END LOOP;
COMMIT;
CLOSE c;
"1.Print in Log"
END;
PROCEDURE globale_Procedure
IS
BEGIN
local_Procedure();
"2.Print in Log"
END;
What i know is that this time depends on the size of the forall update,
but at the time of the Logging everything should be commited.
Thank you for your help,
best Regards
Marc

Answer 1

snorts There's definitely a problem with your implementation - just because you haven't yet had an error because of it does not mean that you will never get an error. If you don't care about that, then fine, but I will have no sympathy for you when you come running back to the forum to ask how to resolve your ORA-01555 error. *{;-)
You haven't provided a test case for us to see what your code is doing, so we can't give you an answer. Why don't you go away, construct your test case, with results that show the difference in your times, etc.
Also, what Oracle version is your database?
Message was edited by:
Boneist
A much better way to complete your objective would be to use one update statement and use the error logging clause. See: http://www.oracle-base.com/articles/10g/DmlErrorLogging_10gR2.php