RE: ** replication remove

May be I have missed something but if replication of materialized view
is now built in CATPROC and is no more an add on script, so you don't
uninstall this capability.
To stop the replication just remove the snapshot logs, propagator, jobs
related to the propagation and target Mview.
 
For streams, I paid the hard price to know that removing streams from an
installed DB is done using  oracle distributed 'remove_streams92.plb'
package and is not very good. I can testify that you data dictionary is
corrupted somewhere after it is applied on your DB. If you remove and
reinstall the streams, you will have weird things happening in your
exceptions queues and error messages. Some rules remains pending witch
do not belong to any rule sets and conflict with existing rules.
 It is ok on a test DB, until the pain is too high and you will end with
recreating the DB from scratch. I tried re-run CATPROC and catalog, but
this  does not remove the corruption.
 
bp

  _____  

From: A Joshi [mailto:ajoshi977@xxxxxxxxx] 
Sent: Monday, 23 October, 2006 4:52 PM
To: Yavor_Ivanov@xxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: ** replication remove


Yavor,
    Thanks. Master2Master. Advanced replication. Thanks a lot for
pointing me to the note 241943.1. 
So if it is de-supported then what would be the way to get rid of
replicaiton. Once the database is replicated it would be difficult to do
database quiesce (suspend) also. since there will not be a secondary.
Thanks. 

Yavor Ivanov <Yavor_Ivanov@xxxxxxxx> wrote:

        What kind of replication? Master2Master, Mview, Streams?
        What version of oracle?
        I did not play with catrepr, but according to metalink note
241943.1 CATREPR.SQL id no longer supported as of 9.2.0.2
        
        Regards,
        Yavor
        
        On Sun, 22 Oct 2006 17:41:03 +0300, A Joshi wrote:
        
        > Hi,
        > I am planning to copy a database that is replicated to another
server. It will not be replicated on this new server. So in order to
remove replication I plan to remove all replication software using
catrepr.sql.
        > I think last time I did this I also had to execute
sys.dbms_internal_trigger.destroy
        > for some tables. So my question is is catrepr.sql enough to
remove replication or is there a better way to remove the replication.
Or some order to be followed. Thanks for the help.
        >
        > 
        > ---------------------------------
        > Get your own web address for just $1.99/1st yr. We'll help.
Yahoo! Small Business.
        
        --
        http://www.freelists.org/webpage/oracle-l
        
        
        


  _____  

How low will we go? Check out Yahoo! Messenger's low PC-to-Phone call
rates.
<http://us.rd.yahoo.com/mail_us/taglines/postman8/*http://us.rd.yahoo.co
m/evt=39663/*http://voice.yahoo.com> 

Other related posts: