Title: Merge
Richard, How about if the "reporting tables" were re-defined as range-partitioned, but with only one partition? Then, instead of modifying the "reporting tables" as they are being read by users, the refresh could instead be performed by populating an empty table from the view (i.e. using INSERT /*+ APPEND */), then performing EXCHANGE PARTITION to swap the newly-populated table with the single partition. So, all direct-path nologging inserts, all direct-path nologging compute-statistics index creations? No downtime for queries, hardly any redo, hardly any undo, no fuss, no muss? Just an idea... Tim Gorman consultant -> Evergreen Database Technologies, Inc. postal => P.O. Box 630791, Highlands Ranch CO 80163-0791 website => http://www.EvDBT.com/ email => Tim@xxxxxxxxx mobile => +1-303-885-4526 fax => +1-303-484-3608 Lost Data? => http://www.ora600.be/ for info about DUDE... On 7/6/2010 6:26 AM, Goulet, Richard wrote: -- //www.freelists.org/webpage/oracle-l |