Re: Copying table from one database to another db which have long raw column & huge data

  • From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
  • To: Raja Subramaniyan <raja.s28@xxxxxxxxx>
  • Date: Tue, 23 Apr 2013 09:22:52 -0300

Well, I just told you. the restrictions are the buffer size in traditional
exp, and the fact that you can't use a network link with datapump.
Cheers

Alan.-


On Tue, Apr 23, 2013 at 3:09 AM, Raja Subramaniyan <raja.s28@xxxxxxxxx>wrote:

> Thanks Alan. I am preferring exp / expdp methods to proceed. Please let me
> know if there any constraints for using that for LONG RAW DType.
>
> Regards,
> Raja.S
>
>
> On Tue, Apr 23, 2013 at 10:45 AM, Guillermo Alan Bort <
> cicciuxdba@xxxxxxxxx> wrote:
>
>> if you are going with traditional export (the one with exp) then you need
>> to ensure you have a large enough buffer (think along the lines of largest
>> row). Datapump is your best bet from 10g on. Though  dblink replication
>> won't work on long data, it's easy enough to export only tables containing
>> longs to a dump and  duplicate the rest with datapump over network link.
>>
>> hth
>>
>> Alan.-
>>
>>
>> On Tue, Apr 23, 2013 at 1:13 AM, Raja Subramaniyan <raja.s28@xxxxxxxxx>wrote:
>>
>>> Hi,
>>> I need to safely transfer databases / tables with LONG RAW coloumns from
>>> one machine to another.
>>>
>>> What parameters have to be used to make exp work with the LONG RAW data
>>> type and what are all the steps have to be taken?
>>>
>>> Thanks
>>> Raja
>>>
>>>
>>> --
>>> //www.freelists.org/webpage/oracle-l
>>>
>>>
>>>
>>
>


--
//www.freelists.org/webpage/oracle-l


Other related posts: