Re: Why dbms_defer_sys.schedule_push with updateable snapshots

From: Jake <Im_at_nottelling.com>
Date: Sat, 11 Jan 2003 13:58:07 -0600
Message-ID: <avpsv3$ed5$1@bob.news.rcn.net>

>
> afaik, the push job pushed out deferred transactions (i.e.
> transactions not cascaded to all snapshots), the purge job
> purges transaction/data records from the master tables, only
> for those transactions that have been propagated to all
> registered snapshots.
> If you picture refresh on demand, the mechanism, and the need
> for it, becomes obvious.
>
> Grtz, Frank
>

Maybe I'm being thick but are you saying: 1) when I refresh, the changes that occurred at my local (snapshot) don't get pushed to the master?
2) the local changes (at the snapshot) are only applied at the master site, during the push job?

I thought during a refresh, first the local changes are pushed to the master, then all the changes are pulled to the snapshot

Jake Received on Sat Jan 11 2003 - 13:58:07 CST