Re: copy a DB from Solaris to HP-UX

"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:3fabb82e$0$249$ed9e5944_at_reading.news.pipex.net...
> "Howard J. Rogers" <hjr_at_dizwell.com> wrote in message
> news:3faa9e15$0$9224$afc38c87_at_news.optusnet.com.au...
> >
> > "Joe" <emanonii_at_yahoo.com> wrote in message
> > news:63bb2d27.0311060517.22595651_at_posting.google.com...
> > > Because the they want minimal downtime and the initial load involves
> > > either shipping a tape across the country or FTPing 50gb. In either
> > > case, there will be a number of hours where no changes could be made
> > > to the source system. Is there a way where after the export/import is
> > > done that any changes could be rolled to the new box?
> >
> >
> > Yes: Log Miner (your existing production system would need to be in
> > archivelog mode). You can manually extract the SQL Statements from a
known
> > time from the logs, and produce SQL scripts to run against your new
> > database.
> >
> > But it's problematicas to whether you'd trap every possible change in
this
> > way... it's wide open to user error.
> >
> > That's why I'd agree with Richard: investigate alternatives such as
> Streams,
> > replication, or third party products.
>
> Does streams capture nologging operations?
>
> Niall in almost total ignorance of streams.
>

Volker really answered you. Just to make it explicit: 9i introduced the 'alter database force logging' command (and its reverse 'alter database no force logging'). Almost worth the licence fee on its own.

Regards
HJR Received on Fri Nov 07 2003 - 12:10:06 CST