OWB 10g R2 - Migrate Back-end Database from Windows to Unix - Need Help!
699850May 5 2009 — edited May 7 2009Hello.
I have inherited an Oracle Warehouse Builder environment (I am the new Oracle DBA for the project). It is currently OWB 10g R2 (10.2.0.3) running on Windows 2003 against an Oracle 10g R2 database (10.2.0.4) on the same Windows 2003 server. Due to performance issues (on the Windows box) and database lincesing restrictions, I need to move the back end database from the Windows 2003 server to our Oracle Sun Solaris 10 database server.
I am looking for the least impactful way to do this database move to make it as transparent as possible for the developers. My first thought was a full database export/import. Here are the steps I was looking at:
1. Create the new database (same database name) on the Sun Solaris box.
2. Do a full database export on the Windows Oracle database.
3. Import the full database export into the Sun Solaris database.
4. Update OWB database entry in the tnsnames.ora file to point to the new database.
The issues/concerns that I see in doing this:
1. Are there any other configuration files that would need to be updated due to the database move?
2. The developers are using DIRECTORY objects in the database to reference external files - can I move the files from the Windows server to the Unix server and then update the DIRECTORY objects to point to the new location? Will I run into any issues with Warehouse Builder?
3. Unknowns... Since I am not that familiar with Warehouse Builder, I'm not sure if I will run into any other issues...
If the export/import of the entire database is not feasible or advisable, what would be the best way to do this move with the least impact to my developers?
Any help, advice, corrections, etc would be greatly appreciated.
Thanks!
-DC