Reorgs in a Replicated environment

Hi,

    I'm trying to determine what might be the best way to do table reorgs in a replicated 24/7 environment running 8.1.6. Currently I'm thinking of setting up a third database in the replication group (1 master definition site, which is inaccessible by the customers, and 2 master sites, available to customers in a load balancing scenario). With this additional site I could restrict access to it, take it offline (dbms_offline_og.begin_load), reload the data, followed by an online
(dbms_offline_of.end_load). Then unrestrict the access and repeat the procedure on
the other master site. Finally allow access to either of the customer master sites. Any suggestions, comments, etc. are welcome. Is there an easier way that I'm overlooking? Do I need more coffee? Has anyone been down this path?

Alan Aschenbrenner

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Aschenbrenner, Alan
  INET: alan.aschenbrenner_at_ihs.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (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).