Unfortunately I do not have access to changing rollback segments,
as I am just another developer and not a DBA. I already asked the
DBA, but he told me, that the same things mentioned in other answeres:
Do not update rows, which the cursor relies on, if the cursor
is really big. He suggested the
FORALL statement, but I really can't think of a way to apply it in
this context.
Hans Forbrich <forbrich_at_yahoo.net> wrote in message news:<FV1Xc.7817$A8.4274_at_edtnps89>...
>
> Have you considered sizing your rollback segments to avoid the
> in-the-loop-commit? Generally considered better for performance,
> management, and eliminating the problem.
>
> Or better yet, upgrading to use the new UNDO tablespace capability and then
> sizing properly?
Received on Thu Aug 26 2004 - 04:24:59 CDT
