RE: Generic Import question

  • From: "Storey, Robert (DCSO)" <RStorey@xxxxxxxxxxxxxxxxxx>
  • To: 'rjamya' <rjamya@xxxxxxxxx>, "cicciuxdba@xxxxxxxxx" <cicciuxdba@xxxxxxxxx>
  • Date: Tue, 4 Sep 2012 17:57:05 +0000

I don't use any profiles are resource groups. My schema imports will create the 
public synonyms used by the application.

Still playing with the full.  Just keeps bombing on little things like temp 
filenames being different, etc.


-----Original Message-----
From: rjamya [mailto:rjamya@xxxxxxxxx] 
Sent: Tuesday, September 04, 2012 12:55 PM
To: cicciuxdba@xxxxxxxxx
Cc: Storey, Robert (DCSO); oracle-l@xxxxxxxxxxxxx
Subject: Re: Generic Import question

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@xxxxxxxxx> 
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?
--
//www.freelists.org/webpage/oracle-l


Other related posts: