Exception in Oracle 10g

Question

I've got problems with the following code:
OPEN Gr_Obj_Cur;
LOOP
BEGIN
FETCH Gr_Obj_Cur INTO Gr_Obj_Rec;
EXIT WHEN Gr_Obj_Cur%NOTFOUND;
INSERT INTO ADM.Current_Official_Obj#
(Owner, Name, Obj_Type, Priv)
VALUES (Gr_Obj_Rec.Owner, Gr_Obj_Rec.Name, Gr_Obj_Rec.Obj_Type, 'SELECT');
EXCEPTION
WHEN OTHERS THEN
NULL;
END;
END LOOP;
CLOSE Gr_Obj_Cur;
It iterates aproximately 2000 times. And since I've a unique index built for the Current_Official_Obj# in almost half of cases the insert throws an exception. The latter(throwing an exception) executes pretty long (50sec. for the whole loop).
I tried to run this code In Oracle 9 - and the most surprising is that it works in 0.5sec.
What is the reason for such a strange behavior in Oracle10? Can the exceptions be logged? Is this option tunable? If so then how to turn it off?
Thanx in advance, Aidar

Answer 1

Not sure what you are trying to achieve here. The code itself does not make sense. Why use an explicit cursor fetch loop when the exact same results can be achieved by an implicit cursor running a 'INSERT INTO .. SELECT ... FROM ..'?
Why supress all exceptions, without handling them? I fail to grasp why this would want to be done.
As for comparing 9i with 10G - this will only be valid if the 2 hardware platforms are exactly the same and the data volumes (and number of exceptions raised) are also the same. Even then there can be differences due to PIO vs LIO ratios between the two instances. Etc.