Re: imp.exe full=y imports SYSTEM's objects, violates constraints...
Why do not simply leave the same structure in place, stop the original
database, copy the files over to the new server, create a service and
then upgrade it in the server?
Another approach, which I works on now, is to do tablespaces export/import.
Move all the user data and indexes to standalone tablespaces and then
you can copy the tablespaces to any place on the new server and import them.
Branimir Petrovic wrote:
>Purpose of the exercise is to come up with the least troublesome
>way (find simplest, most straightforward procedure with min amount
>of steps) to move one development database from one Win "box" to
>another Win "box" (may be with higher patch level and quite
>likely with tablespaces/files sitting in different locations)...