OraFAQ Forum: Backup & Recovery

Home » RDBMS Server » Backup & Recovery » RMAN-04005 error

Show: Today's Messages :: Polls :: Message Navigator
E-mail to friend

RMAN-04005 error [message #51913]

Fri, 21 June 2002 03:01

James Briar
Messages: 72
Registered: January 2002
Location: Morden (South London)

Member

If i run a simple batch script called jim.cmd (On an NT server) the script works fine but if i try to run the same batch script in say a few mins time using the "at" command i get the error messages "RMAN-04005: error from target database" and "ORA-01031: Insufficient Privileges".

The jim.cmd file contains :-
set ORACLE_SID=imptest
rman < e:jim.sql > e:jimlog

The jim.sql contains :-
connect target /
connect catalog rman/password@rmandb
print script Backupimptest;

If i just type in jim.cmd on the command line the script runs ok and jimlog contains the correct info.

If i do "at 11:55 e:jim.cmd" the script runs but produces the above errors. RMAN does connect to the recovery catalog database though.

We're using Oracle 8i on an NT 4 server. I'm logged on as the administrator.

When i run jim.cmd using the "at" command" jimlog contains :-

Recovery Manager: Release 8.1.7.0.0 - Production

RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04005: error from target database: ORA-01031: insufficient privileges

RMAN>
RMAN-06008: connected to recovery catalog database

RMAN>
RMAN-03027: printing stored script: Backupimptest
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06171: not connected to target database

RMAN>

Recovery Manager complete.

Report message to a moderator

Re: RMAN-04005 error [message #51918 is a reply to message #51913]

Fri, 21 June 2002 04:01

Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille

Senior Member
Account Moderator

this is bug. Workaround is
to create a passwordfile using orapwd utility
then add initsid.ora entry and restart.
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
grant sysdba/sysoper to RMAN user
svrmgrl> grant sysdba to <user>;
svrmgrl> grant sysoper to <user>;
Now try again.

Report message to a moderator

Re: RMAN-04005 error [message #51963 is a reply to message #51918]

Mon, 24 June 2002 05:23

James Briar
Messages: 72
Registered: January 2002
Location: Morden (South London)

Member

I've tried your fix but it did not work. I did :-

e: orapwd file=e:oracleora81databasepwdimptest.ora password=change_on_install entries=5
e: set ORACLE_SID=imptest
e: sqlplus internal
SQL> grant sysdba to sys;
SQL> grant sysoper to sys;

Also the parameter file had the entry "remote_login_passwordfile=exclusive" already set and i shutdown and restarted the implive database.

I did the above for the rmandb database as well.

Report message to a moderator

Re: RMAN-04005 error [message #51989 is a reply to message #51918]

Tue, 25 June 2002 01:27

James Briar
Messages: 72
Registered: January 2002
Location: Morden (South London)

Member

It now works after setting up the password file etc. I had to amend jim.sql and change "connect target /" to "connect target sys/change_on_install" and now the script runs ok. The script still fails with the RMAN-04005 error if i code "connect target /" in the file. I'll stick with coding "connect target sys/change_on_install" in the jim.sql file from now on.

Thanks very much for your help Mahesh.

Report message to a moderator

Re: RMAN-04005 error [message #396071 is a reply to message #51913]

Fri, 03 April 2009 13:03

dave604
Messages: 2
Registered: April 2009
Location: Vancouver, Canada

Junior Member

Also, if you have installed the grid control agent, check that it's directories in the path are specified AFTER the standard Oracle bin directories.

Report message to a moderator

Re: RMAN-04005 error [message #396072 is a reply to message #396071]

Fri, 03 April 2009 13:08

Mahesh Rajendran
Messages: 10707
Registered: March 2002
Location: oracleDocoVille

Senior Member
Account Moderator

You responded to a post from June 2002. Smile

Report message to a moderator

Re: RMAN-04005 error [message #396204 is a reply to message #396072]

Sat, 04 April 2009 23:28

dave604
Messages: 2
Registered: April 2009
Location: Vancouver, Canada

Junior Member

Yes I know I responded to an old post, but that's because people with the same problem still find the post via google, and I wanted to share how I resolved the problem. Smile

Report message to a moderator

Re: RMAN-04005 error [message #396206 is a reply to message #396204]

Sat, 04 April 2009 23:38

BlackSwan
Messages: 26766
Registered: January 2009
Location: SoCal

Senior Member

dave604 wrote on Sat, 04 April 2009 21:28

Yes I know I responded to an old post, but that's because people with the same problem still find the post via google, and I wanted to share how I resolved the problem. Smile

Some/many/most Original Posters NEVER search for solution before postings their FAQ again, again, again.

This is precisely why FAQ forums exist. QED!

Report message to a moderator

Re: RMAN-04005 error [message #411217 is a reply to message #51913]

Thu, 02 July 2009 08:43

abhishekpatne
Messages: 1
Registered: August 2008

Junior Member

IF any of the above comments won't help u ...then

you should check whether your current logged in ( operating system ) user is member of ora_dba group in windows os.Administrator of the server can add you to ORA_DBA Group

Report message to a moderator

Previous Topic:	Duplicate: read error on file
Next Topic:	How to tell if a database has a recovery catalog

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed Apr 17 21:36:19 CDT 2024