export import question.

[dbaperson]

Hello members,

Our oracle 10g database export file on HP-UX is around 60 gb in size. It takes around seven hours to export the entire database. The problem is migrating the export file to Windows server 2003. It is taking forever using ftp. The idea is to create the database on windows. I am looking for a much faster way to do this database copy. I am not looking into RMAN or tablespace transport currently due to the endian issue. Is there any way to mount the windows drive on solaris and make a copy like NFS. What would be the fastest way to copy from one system to another? How long would it take to import a 60 gb file? Any ideas will be appeciated.

 

[Dagon]

Have you tried compressing the file before copying it ? You should be able to use something like gzip on the UNIX system and then PKUNZIP on windows. Make sure you do a binary copy as well.

 

[Thargy]

One of the advantages of transportable tablespaces is that they avoid the endian issue, hence their name.

http://www.oracle.com/technology/deploy/availability/htdocs/xtts.htm

refers.

Second, do you really need to export the entire database? In my admittedly limited experience, wise users tend not to write to the system tablespaces, so there's no value therein, and no point exporting them.

If you can just export the schemas needed, you ought to be able to divide your whopper up into several smaller files, and move them in parallel.

Also, expdp and impdb have optimisation, which for large volumes of data improves performance over the original exp and imp utilities. I suggest that you look into these as possible solutions.



Regards

T

 

[pete91z]

expdp and impdp also have parallel options so you can spread the export over several files.