Re: Generic Import question
From: rjamya <rjamya_at_gmail.com>
Date: Tue, 4 Sep 2012 13:55:24 -0400
Message-ID: <CAGurbTNxoi92FZXWAAfVxPRJGEuXCcMQaHLYf_Q5FVdcv42q6w_at_mail.gmail.com>
True, but you can script these, there is no need to bring sys/system etc schemas ... because you will need to patch them to bring them to correct db level. To me that is a bigger issue, but yes, public synonyms, profiles etc should be (must be?) handled outside of schema level import.
Date: Tue, 4 Sep 2012 13:55:24 -0400
Message-ID: <CAGurbTNxoi92FZXWAAfVxPRJGEuXCcMQaHLYf_Q5FVdcv42q6w_at_mail.gmail.com>
True, but you can script these, there is no need to bring sys/system etc schemas ... because you will need to patch them to bring them to correct db level. To me that is a bigger issue, but yes, public synonyms, profiles etc should be (must be?) handled outside of schema level import.
Thanks Alan.
Raj
On Tue, Sep 4, 2012 at 1:35 PM, Guillermo Alan Bort
<cicciuxdba_at_gmail.com> wrote:
> My first thought is this:
> Are you 100% you only need those schemas? What about public synonyms? what
> about password verify functions? Profiles? resource groups?.
> basically what about all the configurations that are not part of schemas?
-- http://www.freelists.org/webpage/oracle-lReceived on Tue Sep 04 2012 - 12:55:24 CDT