Re: Large Table Migration to another m/c
Date: Mon, 21 Mar 1994 04:15:10 CST
Message-ID: <1994Mar21.041510.22076_at_amoco.com>
In article 11711_at_oracle.us.oracle.com, skanga_at_us.oracle.com (Shiraz Kanga) writes:
-->In article <CMr3M8.Dx8_at_shakti.ncst.ernet.in> hemant_at_shakti.ncst.ernet.in (STOCKHOLDING CORPORATION OF INDIA LTD.) writes:
-->>
-->>We have a table having in excess of 20million rows. We expect that the
-->>export file will exceed 2GB.
[chomp]
-->>Could you please suggest alternatives ?
-->>
-->
-->Well the obvious solution would be to use a portable (and reliable) compresion
-->utility and I believe there are several out there like maybe GNU's gzip stuff.
-->
-->And there are also other options like not doing a full export but breaking it
-->up into pieces (by user or by tablespace, etc) and moving each chunk
-->separately onto the new machine. That way you may not need to compress at all.
-->
-->Hope this helps
I would have thought the obvious solution would be to export the table to TAPE.(directly) Then take the tape to the other machine and import.
Dontcha have a tape drive ?
--- ------------------------------------------------------------------------------ David Crowson =%^) |"For my part, I travel not to go anywhere, but to go. Oracle DBA(Ver.4,5,6,7)| I travel for travel's sake. The great affair is to Amoco Exploration | move, to get down off this featherbed of civilisation Ealing, London, UK. | and to find the globe granite underneath and strewn "My views not Amoex's" | with cutting flints" : Robert Louis StevensonReceived on Mon Mar 21 1994 - 11:15:10 CET