Re: Problems with snapshot log

Thanks Jining! I'll try that and see what happens.

In article <92tlpl$nnq$1_at_nnrp1.deja.com>,   Jining Han <hanj_at_mailcity.com> wrote:
> In article <92t5gq$8qq$1_at_nnrp1.deja.com>,
> redenm_at_my-deja.com wrote:
> > I saw Michael's email regarding problems with snapshots. I have a
> > problem which is similar but not quite. Here's my situation:
> >
> > I'm using Oracle 8i Lite Ver. 8.0.5.0.1, having a master DB used for
> > replication. I manually updated (deleted old records, inserted new
> > records) one of the tables. When I did a fast refresh (via
> > application), I'm getting the following message:
> >
> > REPAPI-26515: no master log available for PMPTST.TBL_AFFILIATE.
> >
> > I tracked down this error and it points me to MLOG$_TBL_AFFILIATE
 which
> > was missing. I manually (via SQL Plus) re-created said snapshot log
> > and re-tested fast refresh, same error message. Question: does
 this
> > table updates itself when there are changes (deleted old records,
> > inserted new records) on the master table (TBL_AFFILIATE)? If not,
 do
> > I need to consider updating (deleted old records, inserted new
 records)
> > this snapshot log table (via SQL Plus)? I'm new to Oracle
 replication
> > and appreciates any help on this. Thanks.
> >
> > Sent via Deja.com
> > http://www.deja.com/
> >
>
> You not only need this table, but also the internal trigger that
> populate this table with all the transaction information. Your best
> bet would be creating the snapshot log using Replication Manager.
>
> --
> Jining Han
> Sallie Mae
>
> Sent via Deja.com
> http://www.deja.com/
>

Sent via Deja.com
http://www.deja.com/ Received on Wed Jan 03 2001 - 08:27:03 CST