Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: rman connection authorization

Re: rman connection authorization

From: joel garry <joel-garry_at_home.com>
Date: 5 Jul 2006 17:31:45 -0700
Message-ID: <1152145905.749394.129430@j8g2000cwa.googlegroups.com>

EdStevens wrote:
> 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 ..
> >
> > Microsoft Windows [Version 5.2.3790]
> > (C) Copyright 1985-2003 Microsoft Corp.
> >
> > 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
> >
> > Copyright (c) 1982, 2005, Oracle. All rights reserved.
> >
> >
> > 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
> >
> > 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>
> >
> > 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 ....

Must be something in that home that is different... maybe it couldn't find the correct $ORACLE_HOME/dbs/passwd... ?

jg

--
@home.com is bogus.
http://www.signonsandiego.com/uniontrib/20060705/news_1b5postal.html
Received on Wed Jul 05 2006 - 19:31:45 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US