Re: importing dmp on different tablespace

I have to admit that I didn't know that this was the behaviour of import. I've not used it in this way. The only thing I would say in Oracles defence is that it is not enough for user B to have quota on tablespace AA_T, they must have *sufficient* quota. So It would be easy to envisage a situation where the import runs say 75% of the way thorugh before running out of space.

regards

--
Niall Litchfield
Oracle DBA
Audit Commission UK
<faheemrao_at_my-deja.com> wrote in message news:90tfae$go1$1_at_nnrp1.deja.com...


>

>

> Hi ,Niall

>

> Thanks a lot for your suggestion,

> I will try your trick.:))

>

> But I have one more question that. If your are going to import the dmp

> file in a database where  there is no AA_T tablespace then , the import

> utility will going to import the dmp file into the default tablespace

> of the to_user,

> At that time oracle should give an error that tablespace AA_T not

> found. but it does not. SO why oracle is not intelligent enough that if

> we  want to import that  dmp file into the same database in another

> user that have no quota on tablespace AA_T, then oracle  gives an error

> that no quota, on tablespace AA_T.

> I know that  before importing the dmp  import utility checks that

> tablespace AA_T exists or not, then it proceeds. But Actually Oracle

> should also checks that  either the to_user have any quota on

> tablespace AA_T or not , if not then it should import the data  in the

> default tablespace of the to_user.

>

> what do you say about this??

>

>

> any body else have the answer of this ???

>

> Thanks

>

>

> Faheem Rao

>

>

> In article <90tbg9$jfk$1_at_soap.pipex.net>,

>   "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote:

> > hi

> >

> > The import utility can be thought of as running creation scripts for

 each


> > database object that is imported. Therefore it will effectively be

 running


> >

> > create table foo(bar varchar2(20)) tablespace AA_T storage (whatever

 the


> > storage clause was) on import. Hence your errors. The simple

 solution. Pre


> > run your table creation scripts to create empty tables under schema

 b. THEN


> > run the import with ignore=y. This will populate your tables

 correctly.


> >

> > You do NOT want to create these tables in the system tablespace. They

 should


> > go elsewhere.

> >

> > --

> > Niall Litchfield

> > Oracle DBA

> > Audit Commission UK

> > (BTW For Howard - A while ago I stated that I left system accounts

 using the


> > system tablespace. I have since found that you were right and the

 oracle


> > recommendation is to set all users except sys to use different

> > tablespaces. )

> > <faheemrao_at_my-deja.com> wrote in message

 news:90rbev$vdd$1_at_nnrp1.deja.com...


> > >

> > >

> > > I have  two schemas

> > > Schema AA default tablespace AA_T

> > > Schema BB default tablespace System ,no qauota on AA_T

> > >

> > > both exist on same database

> > > I am trying to import the dump of AA schema into the schema BB.

> > >

> > > but when I try to do that oracle gives me errot that no privilige on

> > >

> > > tabelspace AA_T

> > >

> > > now when I grant priviliges to schema BB on AA_T then it import the

> > > data on the  tablespace AA_T .

> > > I want to import that schema on system tableapce or any other than

 AA_T


> > >

> > > I am struc here.

> > >

> > > any help would be very appreciated.

> > >

> > > thanks in advanc

> > >

> > >

> > > Faheem Rao

> > >

> > >

> > >

> > > Sent via Deja.com http://www.deja.com/

> > > Before you buy.

> >

> >

>

>

> Sent via Deja.com http://www.deja.com/

> Before you buy.