Home » Developer & Programmer » Designer » Best Practice for Batch Processing of Large Table
Best Practice for Batch Processing of Large Table [message #90641] Wed, 16 June 2004 09:02 Go to next message
Andy Ferretti
Messages: 1
Registered: June 2004
Junior Member
I am wondering if anyone is aware of any best practices documented for design of a batch program that must step through a large table making updates to the large table as well as other dependent tables based on business criteria.  We would want to allow for concurrent on-line transactions (so logging is necessary).  We could commit at reasonable intervals (every 100 records or so).  We would want to support restartability as well as the ability to run multiple threads simultaneously.  Lastly, we would want to avoid problems with rollback segment space.

The programming environment here is java, however any best-practice in the form of a high level algorthm would suffice.
Re: Best Practice for Batch Processing of Large Table [message #90657 is a reply to message #90641] Wed, 30 June 2004 10:43 Go to previous message
andrew again
Messages: 2577
Registered: March 2000
Senior Member
Best to search on asktom.oracle.com, there are several ways discussed.
Previous Topic: Reverse Engineering
Next Topic: Check Constraints
Goto Forum:
  


Current Time: Wed Sep 30 14:11:56 CDT 2020