Re: Import bug

From: Daniel Morgan <dmorgan_at_exesolutions.com>
Date: Fri, 28 Jun 2002 16:19:20 GMT
Message-ID: <3D1C8C6A.8E0DD5FC@exesolutions.com>

Chuck wrote:

> "Knut Talman" <knut.talman_at_mytoys.de> wrote in message
> news:3D1C8527.59974CC4_at_mytoys.de...
> > Chuck wrote:
> > >
> > > "Knut Talman" <knut.talman_at_mytoys.de> wrote in message
> > > news:3D1C7294.35C174C0_at_mytoys.de...
> > > > Chuck wrote:
> > > > >
> > > > > I believe I've just discovered a bug in the import process.Please
> tell
> > > me if
> > > > > you agree. In the case where a user owns tables but has no quota on
> any
> > > > > tablespace, you can export that user but when you try to import it
> the
> > > > > tables will not be created. Even running the import as a DBA user,
> you
> > > still
> > > > > cannot import the the tables.
> > > >
> > > > The user has *no* quota and his tables can't be imported? Which error
> > > messages?
> > >
> > > IMP-00017: following statement failed with ORACLE error 1536:
> > > "CREATE TABLE "PSDBOWNER" ("DBNAME" VARCHAR2(8) NOT NULL ENABLE,
> "OWNERID"
> > > V"
> > > "ARCHAR2(8) NOT NULL ENABLE) PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS
> 255
> > > "
> > > "LOGGING STORAGE(INITIAL 16384 NEXT 8192 MINEXTENTS 1 MAXEXTENTS
> 2147483645
> > > "
> > > "PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
> > > "
> > > " "
> > > IMP-00003: ORACLE error 1536 encountered
> > > ORA-01536: space quota exceeded for tablespace 'USERS'
> >
> > What happens if you execute the statement directly in SQL*Plus when
> connected as
> > the user? Did you try to explicitly remove any quota?

> In sqlplus it fails because use PS (the owner of the PSDBOWNER table) has 0
> quota on the tablespace. Even if attempred as a DBA user. My point is that
> if this is the way import works, it's unreliable is a tool for restoring a
> database. The database if recreated is left missing objects that were in the
> database when it was exported.

I am continuing to read your postings with absolute amazement.

You seem to think that your desire to violate Oracle's security model is a bug.

Quotas on tablespaces exist for a reason. They exist to keep people from taking space that has not been allocated to them.

If the space hasn't been allocated to you ... the reasonable thing to do would be to increase your allocation. If you can not then either you are trying to do something not approved by the DBA responsible for the system (my guess) or you believe that the security model should be compromised by people too lazy to go in with DBA privileges and enter a single line of SQL at the command prompt.

Daniel Morgan Received on Fri Jun 28 2002 - 11:19:20 CDT