Re: Full import is not really "full"

On Thu, 24 Jul 2003 23:57:39 +0200, Rick Denoire <100.17706_at_germanynet.de> wrote:

> I created an empty DB with appropriate tablespaces in order to do a
> full import from another DB.
>
> It turned out that object privileges on SYS objects granted to an
> account in the source DB were not transfered to the destination DB
> after the full import (otherwise everything else went well). Is that
> the way it should work? So one can not rely that a full import is
> really full? This user is supposed to have select access on tables
> like all_users, v$session, etc. By the way, SYS password changed to
> that of the source DB! Funny.
>
> Bye
> Rick Denoire
>

It's exactly the way it's supposed to work. Nothing owned by SYS (including his password) can ever be exported; and neither can anything granted by SYS. Which is (1) why import can certainly be a bit problematic and (2) you should never get into the habit of logging on as SYS except to do startups, shutdowns, backups and recoveries (use SYSTEM instead).

Incidentally, every user has rights to the all_ views automatically, without the need for a special grant.

The V$ views, fair enough.

~QM Received on Thu Jul 24 2003 - 18:22:56 CDT