> 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?
>
Did you create the snapshot with the option fast ?
But not every select of a table can be used to create a snapshot with the
fast option.
Refer to the sql-reference manual page 4-230ff
Regards
Nicolas Bronke
Received on Sat Oct 09 1999 - 12:51:31 CDT
