Re: Why dbms_defer_sys.schedule_push with updateable snapshots

Hi,

since you have set "push_deferred_rpc => TRUE" and "refresh_after_errors => TRUE", you don't need the DBMS_DEFER_SYS.SCHEDULE_PUSH. But, if you want to see the data modified in the snapshot site from the master more frenquently than the refresh processes, you have to schedule a push.

Dias

"Jake" <me_at_heyjay.com> wrote in message news:<avs45p$s63$1_at_bob.news.rcn.net>...
> >
> >
> > Correct. What if I just got back from holidays, and logged into
> > the network the first time since 2 weeks? All those transactions
> > would still be waiting for me. Nevertheless, if the replication
> > on demand fails, there's a job scheduled to make sure it's attempted
> > over and over again.
> > Normally, this job will have no work.
> >
>
> Again if I create a refresh group like:
>
> BEGIN
> DBMS_REFRESH.MAKE(
> name => '"SCHEMA.RGNAME"',
> list => '',
> next_date => SYSDATE,
> interval => '/*Every 20 Min*/ sysdate + 20/(60*24)',
> push_deferred_rpc => TRUE,
> refresh_after_errors => TRUE,
> parallelism => 1);
> END;
> /
>
> And all my snapshots are added to my snapshot group. Why do I need the
> DBMS_DEFER_SYS.SCHEDULE_PUSH?
>
> Jake
Received on Mon Jan 13 2003 - 03:03:07 CST