Re: Import bug (one last word)

And which normal command would that be? The one that connects you to another user who's password you don't even know?

That sneak in method of saving the encrypted password, changing it, logging in, and changing it back to the encypted one, is a kludge at best. Hardly a normal operation. My point is that this ability is in IMP for one reason - to restore a database. Tablespace quotas aren't much different and IMHO the only reason they aren't overridden by IMP is because Oracle forgot to add that to the utility when quotas were introduced back in 7.x.

"Norman Dunbar" <Norman.Dunbar_at_lfs.co.uk> wrote in message news:E2F6A70FE45242488C865C3BC1245DA7024F1AF1_at_lnewton.leeds.lfs.co.uk...
> Chuck,
>
> you wrote, regarding IMP being a special case and doing spacial things :
>
> >> My argument on this is that it does
> >> things that you normally can't do even as a DBA. It allows a DBA
> doing a
> >> full import to grant permissions on tables he does not own.
>
> But my point, in my last post, was this :
>
> IMP carries out a CONNECT to the user being imported.
> Then it does the grants to other users.
>
> So the DBA user is NOT doing anything different at all.
>
> Check it out, run an imp with indexfile=somefile.txt then edit the
> somefile.txt output.
> You will see, a CONNECT USERNAME, where USERNAME is the one being
> imported.
>
>
> Regards,
> Norman.
>
> -------------------------------------
> Norman Dunbar
> Database/Unix administrator
> Lynx Financial Systems Ltd.
> mailto:Norman.Dunbar_at_LFS.co.uk
> Tel: 0113 289 6265
> Fax: 0113 289 3146
> URL: http://www.Lynx-FS.com
> -------------------------------------
>
Received on Tue Jul 02 2002 - 13:01:30 CDT