Moving Data from One Server to Another

Hi Badri,

What is the need of instaling old version and upgrade it to new version? Its criminal wastage of time and also Oracle export/Import is existing for the same exact reason- to copy the database from a lower version to upper version

@ramumorla
Creating dump will take 3 to 4 hours i have 26 GB of images data that alone will take 6 hours so total of 10 hours and import will take around 10 hours as well so you see the downtime will be 24 hours.

@gvsbnarayana
bot version on same machine then upgrade ok.

any other suggestion i want to minimize down time .

The best option would be

If it is same plarofrm.. then

++ Install 9i on new server
++ use transportable tablespace option to move data  
++ Now upgrade to 10g on new server.

or

++ upgrade to 10g in old server
++ Install 10g on new server.
++ use transportable tablespace option to move data (in 10g you can do it in cross platform also)

with the above you will be saving lot of time

Hi ramumorla,
   export/import is a time consuming process and does have lots of implications.
Can you guess how much time will it take to export and how much more time is needed for an import of a 40GB database?
I accept the fact that export/import is a very good tool for upgrade but this option looses battel when the volume is high.
HTH
Regards,
Badri.

How can you say export import is a time consuming process? Are you doing on the network or on the sever? Please read my steps,  I wanted to run the export on the server itself.

Below metalink references may help you

Subject:       How To Use RMAN CONVERT DATABASE for Cross Platform Migration
        Doc ID:       Note:413586.1

Hi ramumorla,
    Yes, I have tried many times, export of a 5 GB of data is completed in less than one hour and then import takes 4-6 hours on our high end database servers on the same host.
Import is always 4-6 times slower than export. You may try on large volumes once.
I repeat, export/import is one good tool for smaller volume upgrades.
Regards,
Badri.

@ramumorla
Hi the export is taking 6 hours and the import is taking the same.


Let me look in to the transportable tablespace option.

Use datapump instead of export/import.  It's much more efficient.  It will take a while, but it is much better than export/import is.  Plus, after 10g, export/import will no longer be supported.  We just migrated our database (3 terabytes) from one server to another and it took all day, but datapump was our only solution.

Export data pump is not available for 9i

Export import is the only way to do this in the most cleanest and simplest way, while if you consider time required to install 10g on the old machine and upgrade , backup, restore on a new machine, export is the simplest way... Please go through the process below.

_____________________________________________________________________________________________

To obtain the cleanest possible export, run INVALID.SQL script to check for invalid objects on 9i DB (source server) and run VALIDATE.SQL (UTLRP.SQL?)to recompile any invalid objects

Export the 9i DB

Shutdown the 9i DB to stop users from establishing a session

Copy the Oracle 9i EXPORT.DMP and IMPORT.PAR files to the 10g DB (destination server)

Ensure tablespaces have been created/configured in the 10g DB to coincide with the 9i DB

Take the 10g DB out of ARCHIVELOG mode

Import the 9i DB into the 10G DB

Check import logs for errors

Reset passwords for system (and other) 10g accounts back to the original 9i DB accounts

Make sure users are pointing to proper tablespaces

Run INVALID.SQL script on 10g DB again to check for invalid objects and run VALIDATE.SQL (UTLRP.SQL?) to recompile any invalid objects

Recompile all PL/SQL modules that may be in an INVALID state, including packages, and types on 10G DB using UTLRP.SQL (is this same as above?)

Check the local applications and DB links on the 10g DB

Ensure MS Access apps are able to connect and work

Give the Oracle Devs the OK to change the hardcoded connect string from the old to the new

Give the MS Access Devs the OK to change the ODBC Connect String from the old to the new

Deploy the new Oracle registry key LOCAL default parameter key connect string to all WS

Put the 10g DB back into ARCHIVELOG mode

Verify the nightly backup client is configured properly

Monitor the alert log and dump directories for possible issues

Ok i have decided to go with import export the reson why i choose that is

I have 30 GB of images and 10 GB of data the data is taking almost 2.5 hours to export and images are taking 4 hours.
What i have decided is to import the images on the new server and start tracking the new images.
once the images are imported i will stop the user from accessing the old server and export the data.
Import the data
import the new images may be 1 gb
and then get the user back online

After importing it to the new server do i have to rebuild the indexes on the table or not?

Imran, All the constraints/Indexes will be built for you withoiut you doing anything through import, But to make sure, just go through the logs that are generated by exp/imp commands

thanks and pls look into this question

https://www.experts-exchange.com/questions/22501742/Reclaiming-Space-in-Tablespace.html