Re: Importing to a different instance on same server

I'm confused. What do you mean "it reimported back into the production database". Do you mean that when you ran import, it tried to load all the objects back into the production database? If so, that would be because, like everything else, when you don't explicity tell Oracle or its applications what to connect to, it uses the instance named by ORACLE_SID as the default connection.

So to import into the second database, you either have to re-set your ORACLE_SID, or you have to explicitly tell import what database you want it to connect to:

imp system/manager_at_TEST full=y etc etc etc.

For that to work, of course, you need a tnsnames.ora with the correct tns alias set in it.

Regards
HJR

--

Oracle Resources : http://www.geocities.com/howardjr2000
========================================


"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!

>

>

>

>