Re: rman connection authorization

From: EdStevens <quetico_man_at_yahoo.com>
Date: 5 Jul 2006 09:42:20 -0700
Message-ID: <1152117740.554752.14500@75g2000cwc.googlegroups.com>

EdStevens wrote:
> DA Morgan wrote:
> > EdStevens wrote:
> > > Platform: Oracle 10.2.0.1.0 on Win2k
> > >
> > > Logged on to the box with a local user that is a member of both the
> > > local Administrators group and the local ora_dba group.
> > >
> > > Connection to db with sqlplus, using local credentials, is quite happy:
> > >
> > > C:\TEMP>sqlplus "/ as sysdba"
> > > SQL*Plus: Release 10.2.0.1.0 - Production on Tue Jun 13 12:23:12 2006
> > > Copyright (c) 1982, 2005, Oracle. All rights reserved.
> > >
> > > Connected to:
> > > Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
> > >
> > > But connecting to rman requires me to spell it out ...
> > >
> > > C:\TEMP>rman target / nocatalog
> > >
> > > Recovery Manager: Release 10.2.0.1.0 - Production on Tue Jun 13
> > > 12:23:26 2006
> > >
> > > Copyright (c) 1982, 2005, Oracle. All rights reserved.
> > >
> > > RMAN-00571: ========================
> > > RMAN-00569: ==== ERROR MESSAGE STACK FOLLOWS ====
> > > RMAN-00571: ======================================
> > > RMAN-00554: initialization of internal recovery manager package failed
> > > RMAN-04005: error from target database:
> > > ORA-01031: insufficient privileges
> > >
> > > C:\Documents and Settings\1oraadmin>rman target sys/*********
> > > Recovery Manager: Release 10.2.0.1.0 - Production on Tue Jun 13
> > > 12:50:38 2006
> > > Copyright (c) 1982, 2005, Oracle. All rights reserved.
> > > connected to target database: EPSREP (DBID=2061389341)
> > > RMAN> quit
> > > Recovery Manager complete.
> > >
> > > So, what am I overlooking? I've never before had a problem with "rman
> > > target / nocatalog"
> >
> > Where did you get NOCATALOG?
> >
> > just: rman target / will get you in.
> > --
> > Daniel A. Morgan
> > University of Washington
> > damorgan_at_x.washington.edu
> > (replace x with u to respond)
> > Puget Sound Oracle Users Group
> > www.psoug.org

> Well, this just gets more curious ..

> C:\Documents and Settings\1oraadmin>sqlplus "/ as sysdba"

> SQL*Plus: Release 10.2.0.1.0 - Production on Thu Jun 15 08:21:33 2006

>
>

> Connected to:
> Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
> With the Partitioning, OLAP and Data Mining options

> SQL> exit

> === so, things are correctly set up for connecting with local sysdba
> credentials

> Disconnected from Oracle Database 10g Enterprise Edition Release
> 10.2.0.1.0 - Pr
> oduction
> With the Partitioning, OLAP and Data Mining options

> C:\Documents and Settings\1oraadmin>rman target /

> Recovery Manager: Release 10.2.0.1.0 - Production on Thu Jun 15
> 08:23:41 2006

>


> RMAN-00571: ===========================================================

> RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

> RMAN-00571: ===========================================================

> RMAN-00554: initialization of internal recovery manager package failed
> RMAN-04005: error from target database:
> ORA-01031: insufficient privileges

> C:\Documents and Settings\1oraadmin>

>
> but rman doesn't like it.

For the record, Oracle support finally came up with a solution, but it raises still more questions. The box had two Oracle homes on it, one for a single 10g datbase and one for the 10g oem agent. In the PATH environment variable, the agent home preceeded the db home. Flipping that -- putting the db home first -- solved the problem and allowed 'c:\rman / target' to connect as it is supposed to. Of course, that raises the question of why path ordering should matter in this particular issue .... Received on Wed Jul 05 2006 - 11:42:20 CDT