tcp100 wrote:
> Oh.. And for details, I think this will work.. We're dealing only with
> about half a million rows - the database size is about 700mb. Not too
> crazy at all.
>
> Most of these are inserts, I will wager that there are no deletes save
> for the occasional development / administrative one, and few updates.
>
> I think this process will work - of course incremental would be better,
> but from what I'm hearing, copying a redo log over and restoring it
> won't meet my zero downtime requirement -- but it could meet a "low"
> downtime requirement if reasonable.. (Unfortunately that's not where I
> stand.)
>
> Thanks again for the advice...
>
> -Chris
>
>
>
Nonsense.
The 'solution' of Mr. Hinsdale is *extreemly* complicated, and you
won't have ANY downtime using a standby database.
The only thing that can go wrong is unreadable archives (as a result of
the copy procedure) and/or not all archives being applied.
--
Sybrand Bakker
Senior Oracle DBA
Received on Wed Jan 03 2007 - 00:06:39 CST
