Suggestions please

Scenario: two networked servers. One server currently houses a 9i database. Database is to be moved to the new server. (Both servers are Solaris). Database is 24x7, so downtime must be minimal. Database is only 20GB in size.

The two servers cannot share storage of any kind, so my original idea of creating new tablespaces within the same database but on the new box's storage and then moving tables/indexes across to the new tablespaces is not a go-er (unless maybe an NFS mount would do the trick...??). For the same reason, my other idea of using dbms_redefinition to move the data across and incurring minimal table locking is not a flyer.

There is a possibility of creating a new database on the new server, populating it with empty copies of the source tables, and then populating the new tables via dblinks... but the concern is that clients will modify data in the source tables as the move takes place (thanks to the 24x7 ruke0, and therefore another possibility has been discussed of setting up replication between the two databases to capture post-initial-setup DML... but replication to handle the move of a 20GB database strikes me as absurd.

Basically, I'm just casting around for suggestions as to how you would approach the issue.

Anyone got any timings on a 20GB export and import?

Regards
HJR Received on Mon Apr 19 2004 - 06:14:56 CDT