Results 1 to 4 of 4
  1. #1
    Join Date
    Oct 2003

    Unanswered: replication failover steps

    Can someone provide failover steps for Oracle master to master replication.Thank You

  2. #2
    Join Date
    Sep 2002

    Re: replication failover steps

    Originally posted by raj_7997
    Can someone provide failover steps for Oracle master to master replication.Thank You
    Please explain what you mean by 'Failover' in this case. Failover is more closely associated with a standby database, not with Master to Master replication.


  3. #3
    Join Date
    Oct 2003

    failover steps

    Thanks for your help. What we plan in similar to standby. Where the primary and secondary are interchanged (right word?).
    Currently all our applications point to a primary site. We want to change that to secondary site where the triggers etc are not enabled. One of the tasks would be to enable the triggers. I am looking for a comprehensive list of similar things to be done and other precautions to be taken. If some1 has recently done this can they share their experiences.

  4. #4
    Join Date
    Apr 2003
    Greenville, SC (USA)
    Really not to bad ... Master to Master replication only for Enterprise Edition ... Snapshot replication for Standard Edition...

    Either case the process is not TOOO Bad...

    1. Redo and Rollbacks..Start with

    5 redo groups using 32mg redo logs
    5 rollback segments with optimal size of 64mg

    2. Replicate tablespace

    Create a separate tablespace for the replication objects
    Set the initial,next,pctincrease for the tablespace
    - alter tablespace replicate default storage (initial 512k next 1m pctincrease 1);

    3. Set SYS tablespaces
    alter user sys default tablespace replicate;
    alter user system default tablespace replicate;

    4. Replication system scripts

    connect internal
    ** Ensure all objects are valid at this point

    5. Change settings for SYS tables

    alter table sys.source$ storage (next 1m);
    alter INDEX sys.i_source1 storage (next 1m);

    6. Create anonymous public db link FROM databases - and set global database names

    7. Create the replication Administrator

    create user repadmin identified by repadmin
    default tablespace replicate temporary tablespace temporary_data;

    execute dbms_repcat_admin.grant_admin_any_schema('REPADMIN ');
    -- or to a specific schema --
    execute dbms_defer_sys.register_propagator('REPADMIN');

    8. Create private db link (from REPADMIN)

    9. Create propagator and receiver accounts (from SYS) - If there are different ...

    create user proprep identified by pusher
    default tablespace replicate temporary tablespace temporary_data;

    execute dbms_defer_sys.register_propagator('PROPREP');

    10. Set up your replication groups ... and add the objects to the groups.
    **** Set up the replication "refresh" job to a LARGE rollback segment.

    11. All user triggers MUST be modified so they don't execute fully during the replication process ...

    .... At the beginning of each trigger, have it check to see if this is a
    replication transaction ... if so, return

    if dbms_reputil.from_remote() OR DBMS_SNAPSHOT.I_AM_A_REFRESH()
    end if;


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts