Re: Synchronizing 2 tables in same database -how ?

From: Jonathan Lewis <jonathan_at_jlcomp.demon.co.uk>
Date: Thu, 20 Nov 2003 11:31:57 -0000
Message-ID: <bpi8l2$i6i$1$8302bc10@news.demon.co.uk>

Given your description, I don't think you want to follow either of my suggestions. It may be best simply to:

    Switch synonym to clone table.
    Drop bitmaps on table to be loaded
    Load table
    Recreate bitmaps (nologging)
    Switch synonyms to loaded table
    Drop clone table
    Create clone table as select nologging     Create indexes nologging
    Create bitmaps nologging.

Even at 60GB the CTAS stuff should fit within your remaining few hours.

--
Regards

Jonathan Lewis
http://www.jlcomp.demon.co.uk

  The educated person is not the person
  who can answer the questions, but the
  person who can question the answers -- T. Schick Jr


One-day tutorials:
http://www.jlcomp.demon.co.uk/tutorial.html
____Belgium__November (EOUG event - "Troubleshooting")
____UK_______December (UKOUG conference - "CBO")


Three-day seminar:
see http://www.jlcomp.demon.co.uk/seminar.html
____UK___November


The Co-operative Oracle Users' FAQ
http://www.jlcomp.demon.co.uk/faq/ind_faq.html


"Christian Svensson" <chse30_at_hotmail.com> wrote in message
news:ccc2a7eb.0311200248.fbcacd0_at_posting.google.com...


> Hi,

>

> See the background on a previous post on this subject.

>

> I saw by the way that when you declare the replicated object, you

type


> in the database link, but if i do a databaselink that points to the

> same SID, then it may work. I will give this a try.

>

> /Christian

>

>

> "Jonathan Lewis" <jonathan_at_jlcomp.demon.co.uk> wrote in message

news:<bpgsiu$i60$1$830fa7b3_at_news.demon.co.uk>...


> > It seems an unusual exercise, would you care to explain

> > why you want to do it.

> >

> > One options (which I haven't tried) is to create loopback

> > database links, so the database appears to be two other

> > databases - then you might be able to do multi-master

> > replication.

> >

> > More simply, and less resource intensive perhaps, create

> > triggers on the tables to do synchronized locking and

> > updates by primary key.  Set a global variable in each

> > trigger to say 'I am coming from a trigger' so that the

> > triggered update to one doesn't replicate itself back in

> > an infinite loop.  You may run into some interesting

> > scalability and deadlock problems, of course.

> >

> >

> > --

> > Regards

> >

> > Jonathan Lewis

> > http://www.jlcomp.demon.co.uk

Received on Thu Nov 20 2003 - 05:31:57 CST