David Ng wrote:
...
> I got a problem with a data loading program. The program always terminated
> with Oracle error
> of "Snapshot too old" even the program commit evey 50 record. ...
Try increasing the OPTIMAL parameter for the rollback segment, so its
extents are kept longer. For heavy duty batch runs we created a special
rollback segment in its own tablespace and set OPTIMAL so its extents
are never released. Use SET TRANSACTION or put the other rollback
segments offline to force use of the big one. You might have to make
the tablespace larger too, until you discover how much you have to
retain to make your program work.
I think "Snapshot too old" happens to readers of data, not writers.
Maybe your load program does some SELECTs for editing too, or maybe
constraints cause implicit SELECTs? If you're sure your data is clean,
another thought is to drop the indexes on the table being loaded and
create them again when you're through. Good luck!
--
Welcome to our web page -- it's at
http://www.quidnunc.net/~deanguer/index.htm
Received on Fri Aug 28 1998 - 23:55:15 CDT
