Re: Using Snapshots

You need to do a fast refresh, you are now executing a complete refresh. In order to work with fast refresh you need to have snapshot logs at the master site.

Hth,

--
Sybrand Bakker, Oracle DBA
Rod Boyle <boyler_at_mindspring.com> wrote in message news:7tnfr9$njk$1_at_nntp6.atl.mindspring.net...
> We are still using Oracle 7.3.1.2.1., and I know get a life and
upgrade!!!!
>
> Anyway I have a question for those of you out there that may be really
> really good with Snapshots. We are using snapshots but are not the master
> database. Anyway they are set up and running fine, but the problem is
that
> the snapshots pulling the entire table across via just the update rows in
> the table(s). This causes me great pain and suffering do to the fact that
> one of the 141 tables has 364,604 rows at least this last time, and pulls
> each row. This causes my achived redo (yes in ARCHIVELOG mode) logs to go
> absolutely crazy and it finally fills up the partition where I store them.
> I have an automatic backup to tar them to tape if the partition reaches
75%,
> but this does not really help, because the partition fills again and
unless
> someone is sitting there to inject a new tape the database will stop
> processing to to the redos having nowhere to archive to.
>
> My question is how do I fix this the snapshots to update only the rows
that
> need to updated?
>
> Rod Boyle
> boyler_at_mindspring.com
>
>
>
Received on Sat Oct 09 1999 - 11:39:12 CDT