Venu,
Another issue to be concerned about is the possibility of
encountering an ORA-1555 error. This error may be triggered by a condition
called 'Fetch Across Commits'. The cursor must maintain read consistency
while it is open. If you are updating the source data and the undo entries
are overwritten (assuming you commit periodically), then a read consistent
version cannot be created. There are two docs/presentations to review. The
first is 'Cats Dogs and ORA-01555' which is available at
www.evdbt.com/papers.htm. The other is 'UNDO Internals' at
www.optimaldba.com/library.html.
Dan Fink
-----Original Message-----
Sent: Tuesday, December 17, 2002 8:54 PM
To: Multiple recipients of list ORACLE-L
A small question to all gurus on the list...
I have a stored procedure (SP) which runs at specific intervals. It
fetches a list of user names and few (2 columns) of their details into a
cursor and processes them one by one in a cursor FOR loop.
Now my question is, Is there a chance of the SP running out of memory
when the number of users increases (may be a few hundreds of thousands).
If yes how to estimate the maximum number of user names my cursor can
handle? Is there any calculation for this? How to overcome this problem?
Is there anything else that has to be taken into account when doing
this?
Thanks in advance!
Venu G.
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Fink, Dan
INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
