This was my original suggestion. The only snag I can think of is if you have a bunch of dependencies like stored procedures and triggers. Even if somebody was selecting from the old table when you renamed it, the select would continue OK ... as long as you don't truncate it. You could even delete from the old table without hosing a running select ... as long as the rollback segment holds up. You could rename the tables, then truncate maybe an hour later.
> -----Original Message----- > > Arup, > > I really appreciate your answer in great details. I got "on > prebuilt table" > work. Thanks a lot for your help. Here is another question: > > Do you see any advantage to use materialized view on prebuilt > table for my > data loading over just simple renaming tables as steps below: > > 1. create table t that is always accessed by applications > 2. create table t1 that is a temp table for loading > 3. load data into table t1 > 4. rename table t to table t2 > 5. rename table t1 to t > 6. rename table t2 to t1 > 7. truncate table t1 for next day loading > > David > > -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: <[EMAIL PROTECTED] 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).
