Re: RMAN Connect Problem

Well, according to the docs supplied by Oracle, RMAN does automatically request a connection to the target database as SYSDBA, but thats all it says! Perhaps it just continues if it doesn't find that the user listed in the connect string does not have that privilege. Anyways, I am using Personal Oracle 8 on Win 95 machine, so it is slightly different than on NT platform. In any case, I know that my database does not have any users with SYSDBA privilege because V$pwdfile_users says there are none.
But then you mentioned the password file again, and I re checked the printed documentation that came with the software, and it mentioned manually setting the ORA_sid_pwfile location in the registry, which hadn't been done! Once I did that, then I was able to log on with svrmgr, using internal account (it now prompts me for the password) and grant sysdba to system. V$pwdfile_users now shows sys, internal and system as having SYSDBA authority! Yippee! RMAN now connects just by supplying user name/password, does not need the database name.
I think the reason why svrmgr never prompted me for password for internal account (although, contrary to what you said, it would never just accept any username/password combo) was because the registry key DBA_AUTHORIZATION was set to the same password as the one already known to the password file. If you set the DBA_AUTHORIZATION key to a value other than the value known to the password file, Oracle will prompt you for the password upon database startup and shutdown.
Well, this ends this thread, thanks for your patience. Will surely try and return the favor if I'm able! Thanks again. John

Howard J. Rogers <howardjr_at_www.com> wrote in message news:39ddc7f5_at_news.iprimus.com.au...
> First off, it's not necessary to be a sysdba to run RMAN (last time I
> checked, anyway -I'm always connecting as system/manager on my targets).
>
> Second off, SYSDBA is actually a system privilege, not a role. But that's
> just being picky, I guess.
>
> Third off, it sounds as if you have a lot of basic configuration issues to
> sort out before you can go much further with rman.
>
> When you create a database, you should have used orapwd to create a
 password
> file, usually called 'orapw<SID>'. Can't remember exactly where you stick
> it off the top of my head on NT, but on Unix it's in ORACLE_HOME/dbs (I
 seem
> to remember), and NT is probably not totally dissimilar (though with no
 OFA
> in version 8 that may not be true). If that password isn't there, then
 yes,
> the 'grant sysdba to blah' command is going to fail. The fact that when
 you
> try this grant it all falls over is probably directly related to the
> confusion about the internal password your system seems to be having: it
> can't find the file, so it doesn't know what the internal password should
> be.
>
> Now you may still be getting connected in server manager because you have
> set up an ORA_DBA local NT group (or, conceivably, an ORA_<sid>_DBA
 group),
> and assigned your user id as a memeber of that NT group -in which case,
 you
> would be using operating system authentication. You could type 'connect
> gibberish/totalrubbish as sysdba' (literally) and it will still connect
 you,
> because you have OS privileges -so it doesn't matter one jot what the hell
> you type. (And no, setting remote_login_passwordfile to exclusive doesn't
> switch off OS authentication -the only thing that does that is if you
 start
> getting rid of your OS groups).
>
> Let's sort out the password authentication stuff, make sure that is
 working,
> and proceed from there.
>
> Incidentally, as a Fourth Off, *someone* must have sysdba privileges in
 your
> database, otherwise it couldn't ever be started up and shutdown, or, in
> fact, created in the first place.
>
> Regards
> HJR
> --
> --------------------------------------------------------------------------
> Opinions expressed are my own, and not those of Oracle Corporation
> Oracle DBA Resources: http://www.geocities.com/howardjr2000
> --------------------------------------------------------------------------
>
> "JS" <ghp_at_videotron.ca> wrote in message
> news:sqiD5.1463$o_3.65612_at_wagner.videotron.net...
> > Thanks again, set the variable to "orcl" then from dos prompt issued
 rman80
> > nocatalog, that launched rman ok, but when issued connect target
> > system/manager, got the denied login message, insufficient privileges,
> > because I know rman is looking for SYSDBA role, which nobody has in my
> > database. Further, if I just do connect target internal, it wants my
> > database password, which I supplied as per the entry I gave when I
 created
> > the password file, but it doesn't recognize that password! I'm confused,
 I
> > have the remote_login_password set to exclusive, but I cannot grant the
> > sysdba role to anybody from sql. Further, even though the password file
 has
> > the password set for internal, svrmgr still allows me to connect without
> > supplying any password. What am I doing wrong? Help!!!!!
> >
>
> [Snip]
>
>
Received on Fri Oct 06 2000 - 16:42:17 CDT