Re: Oracle Archive Solution

From: Gints Plivna <gints.plivna_at_gmail.com>
Date: Tue, 24 Apr 2012 09:41:27 +0300
Message-ID: <CAN2wOq00UBEQ0khWL+UrOGATWr=ihJKmJssY+Y5Mm9CJO6msQg_at_mail.gmail.com>



Yeahh, definitely it needs to improve. I needed one week to code the solution and another week to dig up why nested table import doesn't work, find out that it isn't bug, but supposed action and think out how to overcome that.
I have an Iron man aka Oracle poster on the wall behind me and since then there is a small caption on it - "Oracle is stupid (c) Gints <date>", written by one of my colleagues, who was really surprised hearing my statements about Oracle in these days :) Gints

2012/4/23 rjamya <rjamya_at_gmail.com>

> True, but then I'd say the remap functionality in impdp doesn't do a
> complete job, does it? same is true if you have plsql scripts that have
> schema names prefixed, it won't translate them properly. We still have
> issues with importing job or program arguments with remap_schema.
>
> Sorry, didn't want to hijack the thread, but basically impdp needs to
> improve :)
>
> Raj
>
> On Mon, Apr 23, 2012 at 1:45 PM, <gints.plivna_at_gmail.com> wrote:
>
>> [snip] Schema names in both environments were different, according to
>> docs dp import doesn't remap schema for enclosed nested table types. The
>> solution was to make temp tables for enclosed nested tables. So since then
>> I have another very strong argument NOT to use nested tables in DB.
>>
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Apr 24 2012 - 01:41:27 CDT

Original text of this message