RE: RMAN: Duplication and SYSDBA

From: Powell, Mark D <mark.powell_at_eds.com>
Date: Tue, 5 Dec 2006 10:23:43 -0500
Message-ID: <D1DC33E67722D54A93F05F702C99E2A93DB021@usahm208.amer.corp.eds.com>

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_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Stefan Knecht

	Sent: Tuesday, December 05, 2006 8:42 AM
	To: jweatherman91_at_alumni.wfu.edu
	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.

Stefan

On 12/5/06, John P Weatherman <jweatherman91_at_alumni.wfu.edu> 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
		
		--
		http://www.freelists.org/webpage/oracle-l

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Dec 05 2006 - 09:23:43 CST