Rebuilding MLOG tables

From: Stephen Lee <Stephen.Lee_at_DTAG.Com>
Date: Thu, 12 Jun 2003 12:20:22 -0700
Message-ID: <F001.005B0920.20030612115458@fatcity.com>

Among some of the "Rube Goldberg" applications around here, is one that has multiple replication clients that subscribe to a master. For whatever reason, we might have a client not update for a while and the MLOG table(s) get big. Then, after that, every update has to read up to sky-high high water mark. From the looking around we have done, the thing to do to get the HWM back down without rattling replication seems to be (during a time when we know no updates are going into the master):

lock table xyz in exclusive mode;
alter table mlog$_xyz move tablespace over_there; alter table mlog$_xyz move tablespace back_here; (optional, I suppose) rollback; (release the lock)

Does anyone know of any issues, pitfalls, invitation for disaster, etc. with this?
--

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). Received on Thu Jun 12 2003 - 14:20:22 CDT