tips on moving oracle to new machine

Hi,

I was wondering if anyone can provide me with any tips for moving an oracle database from one machine to another in such a way as to map the exported objects to different tablespaces (is this possible)?

I currently have a single processor, single disk NT server as my development database. I am attempting to move the database to a another, a dual processor, dual disk nt server.

I have created an export dump of the data that I want to move. This export file contains all the schema objects of the one user I wish to import into the new server.

I have installed and configured oracle on the new machine. I have created the user I wish to import on the new instance. I have mapped the physical layout of the tablespaces across the physical drives on the new instance and created the tablespaces with all the necessary data files.

On the old machine, all exported data was in 3 tablespaces (lets call them A, B and C) and all table indexes were stored in the same tablespace as the corresponding table.

On the new machine, since I have a second drive, I want to have all indexes stored in an index tablespace stored on one drive. And then I would like the data to be stored in 5 tablespaces (rather than 3) on the other drive.

Is there a way to tell the import program about these new mappings, so that it can move things to the proper location on the way in? In the past I've imported and always seemed to get things imported to the same tablespace that the object was exported from.

If this isn't possible, is my only option basically to import the items and then manually move them (duplicate the tables, create new tables, and then create table as select..., drop indexes and recreate etc...).

Any tips or hints would be greatly appreciated.

Thanks,
Gavin

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Wed Sep 20 2000 - 00:00:00 CDT