Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Import bug

Re: Import bug

From: Thomas Kyte <tkyte_at_oracle.com>
Date: 28 Jun 2002 16:44:14 -0700
Message-ID: <afisce06qs@drn.newsguy.com>


In article <afij6r$el99n$1_at_ID-85580.news.dfncis.de>, "Chuck" says...
>
>
>"Howard J. Rogers" <dba_at_hjrdba.com> wrote in message
>news:afii1n$pj4$1_at_lust.ihug.co.nz...
>> Altering a users quota to zero after they've created tables is a perfectly
>> valid (though slightly unusual) thing to do, so I think you've got a
>point,
>> sort of.
>>
>> I'd agree with you that you might consider it a problem, except that it's
>> dead easy to fix it: you just re-set the user's quota in the new database,
>> and run import again for that particular schema. You then re-re-set the
>> quota when all is finished. Fiddly, perhaps. But not terminal.
>>
>> I think, fundamentally, it's an issue of perception as to what import
>does.
>> All it does, in fact, is to read a bunch of 'create table' and 'insert
>into'
>> statements from the dump file. It's therefore dumb, and can't be expected
>to
>> finesse things by inventing commands which aren't in the dump file -that
>> really would be a bug if it did!
>
>Actuallty it does a little more than that. If you log on as a DBA and try to
>grant permissions on someone elses tables, you can't do it. Run a full
>import as that same DBA user and you can. Import behaves this way because if
>it didn't you would never be able to use it to completely restore a
>database.
>
>

well, in 9iR2 a dba can grant on someone elses table but... IMP does a "become user" (special priv you might notice out there). It in effect does an SU -- something you could actually do if you wanted -- given the proper privs.

In any case, as others have pointed out -- if you made the user have a 0 quota after they created an object -- IMP cannot (it would be a bug if it did) create those objects again. It is just running SQL as that user and that user is NOT ALLOWED to create that object. Period.

As HJR said -- it is very trivial for you to detect and correct.

--
Thomas Kyte (tkyte@oracle.com)             http://asktom.oracle.com/ 
Expert one on one Oracle, programming techniques and solutions for Oracle.
http://www.amazon.com/exec/obidos/ASIN/1861004826/  
Opinions are mine and do not necessarily reflect those of Oracle Corp 
Received on Fri Jun 28 2002 - 18:44:14 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US