Re: Tuning a series of batch statements

Some answers :

More or less the sequence of events pointed by you refering the commit process is right. The main problem here is : every time you commit, the database need to write a LOT of info. If your I/O is weel-tunned, the redo log files are spread is separated disks, there are sufficient log space in each file, if index,tables, redo logs and rollbacks are separated, then it does not have more nothing to make, by the Oracle side.
 My feeling of the problem, by your desc, is : if you dig in Oracle internals, you can get maybe 5 or 10% more performance, but if you alter the app the results will be MUCH better. The path, here, will be to try the various batch progs run in the same session, thus the update made by on prog will be available to the others, and commit fewer times. Another way can be to write some inter-process communication info to a text file, alleviating the db´s work.

[]s

        Chiappa

Sent via Deja.com
http://www.deja.com/ Received on Thu Jan 11 2001 - 06:21:56 CST