I don't think we can go with the truncate table thing since there is too much weirdness around here in when a client -- and there are multiple clients -- might update: Network problems, box crashed, sunspots (Don't forget about the sunspots!). So if there are entries still hanging around in the MLOG table, we want to keep them.
> -----Original Message----- > > I do it all the time. Actually you don't have to lock the > table; you may > simply quiesce the table, meaning no transations will be allowed. > > Steps: > > Quiesce the table > Apply all the pending logs in the deferred trans queue on > secondary database > Truncate The MLOG$ table. > > No issues; in fact I think (note sure) it is supported by > Oracle. And it > should be; MLOG$ tables are just plain simple tables anyway. > > Hope this helps. > > Arup Nanda > -- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Stephen Lee 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).