Re: Importing to a different instance on same server

Roger,

A neat little trick to avoid such confusion.... have different passwords for sys & system in your databases on the same machine. Then you can't accidentally send the production data back into production as it will error since you will have specified the training systems password! But be aware that the import itself can reset these passwords, if you import sys/systems schema, so straight after you need to log into test and reset them.

Kind Regards

Fraser McCallum
MVP Oracle
www.brainbench.com

"Roger Jismalm" <Roger.Jismalm_at_removethisword.unisys.com> wrote in message news:9rikkn$ihr$1_at_si05.rsvl.unisys.com...
> What is the best way to import a production database export to a training
> instance on the same server?
>
> When I first tried to import everything seemed OK, but it reimported back
> into the production database.
>
> After dropping the production instance the import to the training instance
> worked OK.
>
> However this is not a good workaround as production will soon go live!
>
>
>
>
>
Received on Mon Oct 29 2001 - 10:58:01 CST