Re: Oracle Archive Solution
From: rjamya <rjamya_at_gmail.com>
Date: Mon, 23 Apr 2012 13:56:56 -0400
Message-ID: <CAGurbTMaMb9X3rWDAKpZpqYb15-sUO7mON92B7QBHe+u9QtpWg_at_mail.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 :)
Date: Mon, 23 Apr 2012 13:56:56 -0400
Message-ID: <CAGurbTMaMb9X3rWDAKpZpqYb15-sUO7mON92B7QBHe+u9QtpWg_at_mail.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-lReceived on Mon Apr 23 2012 - 12:56:56 CDT