Re: RMAN: Duplication and SYSDBA

  • From: "Stefan Knecht" <knecht.stefan@xxxxxxxxx>
  • To: mark.powell@xxxxxxx
  • Date: Tue, 5 Dec 2006 17:09:48 +0100

Yes, absolutely. But that wouldn't explain why SYSTEM would "loose" its
SYSDBA privilege. As far as I know that can only happen when a) it gets
revoked or b) a new passwordfile gets created. (which would be the case
here, during a duplicate database).


On 12/5/06, Powell, Mark D <mark.powell@xxxxxxx> wrote:

 We do not use a password file and I can log on as a sysdba.  I believe
that anyone in the Oracle owner group, normally DBA, can do so when no
password file is used.

-- Mark D Powell --
Phone (313) 592-5148

*From:* oracle-l-bounce@xxxxxxxxxxxxx [mailto:
oracle-l-bounce@xxxxxxxxxxxxx] *On Behalf Of *Stefan Knecht
*Sent:* Tuesday, December 05, 2006 8:42 AM
*To:* jweatherman91@xxxxxxxxxxxxxx
*Cc:* oracle-l
*Subject:* Re: RMAN: Duplication and SYSDBA

 The SYSDBA privilege is special. Users that have it, are stored in the
password file, not in the database. You must've recreated that file when you
created a clone of the database.

After a duplicate you will have to re-grant the SYSDBA privilege to all
the users that had it in the original, if you wish to keep it.


On 12/5/06, John P Weatherman <jweatherman91@xxxxxxxxxxxxxx> wrote:
> All,
> After replicating to a development database with RMAN (duplicate target
> database to ...) we are noticing that an account (SYSTEM) is losing its
> SYSDBA grant.  I haven't been able to find any documentation that this
> is or is not supposed to be happening.  Does anyone have any
> experience/insight into what may be happening?  Could I be missing a
> setting somewhere or is this just a "manually reissue to grant when
> adding the tempfile" type of thing?
> TIA,
> John
> ---
> John P Weatherman
> Oracle DBA
> Madison River Communications
> --

Other related posts: