I agree with the idea of taking an image of the prod db, but think that an
operationally simpler way is to take the last hot backup, restore it to the
new server, and recover appropriately! No downtime on prod, and you get the
added bonus of verifying your hot backups. (I am assuming that the prod
system is running in archivelog?)
<saeedt7777_at_my-deja.com> wrote in message
news:95vjib$sg3$1_at_nnrp1.deja.com...
> Folks,
>
> We have a "live" production database that we want to replicate
> to another development machine. The data does not need to be
> updated to the minute. We can not do backup/restore. Also when we
> use import (the imp utility) it complains about
> foreign keys being non existent and does not create
> some of the constraints.
>
> It seems like the "imp" utility is actually validating some of
> the data in the database. Also I have heard that exp/imp utilities
> are not really suitable to export "live" databases.
>
> Is there a flag to tell imp utility to ignore errors and create
> the constraints no matter what ? Is there an easier and a faster
> way to replicate a "live" production database (full database
> replication) ?
>
> I am interested to know about your experiences.
>
> Thanks,
> Sam
>
>
> Sent via Deja.com
> http://www.deja.com/
Received on Fri Feb 09 2001 - 08:58:26 CST
