RMAN-can't register database

I'm attempting to register a database that is located on a different server from my rman database. Here's the error:
$ rman target system/manager@PROD rcvcat rman/rman@RMANDB
Recovery Manager: Release 8.1.7.4.0 - Production
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
Any help would be appreciated!!!

Hi,
Try using "as sysdba" in your string. This should take the insufficient privileges away.
Hope this helps.
Al

Similar Messages

RMAN: Unable to register database

Hi all,
I have just renamed the db_name, dbid and SID of a database using the DBNEWID Utility.
When I satrt up the database, it seems to start without any errors.
I need to take a backup of this database using RMAN.
But when I try to register the database, I get an error -
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 06/22/2009 15:26:39
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 06/22/2009 15:26:39
ORA-01587: error during control file backup file copy
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 323
Additional information: 1036288
Could anyone please help me resolve this problem?

How do I find out, what path exact path is it trying to access?
When I do a SHOW ALL, all that RMAN does is show the error again.
This is what I get -
RMAN> SHOW ALL;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of show command at 06/23/2009 08:16:28
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at 06/23/2009 08:16:28
ORA-01587: error during control file backup file copy
ORA-27091: unable to queue I/O
ORA-27072: File I/O error
Linux Error: 2: No such file or directory
Additional information: 4
Additional information: 323
Additional information: 602112
Edited by: user10882764 on Jun 23, 2009 5:21 AM
Edited by: user10882764 on Jun 23, 2009 5:22 AM

[RMAN] problem with registering database

Hello, we have RAC environment on two nodes. We created rman catalog database and then registered our database with REGISTER DATABASE command. After that we issued command SHOW ALL and encountered an error:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 21 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
could not read file header for datafile 74 error reason 4
could not read file header for datafile 74 error reason 4
could not read file header for datafile 74 error reason 4
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_easy1.f'; # default
this is new catalog database, which is to replace the old one
how to deal with this problem ?

So you are following up on datafile 74 in this other thread :
problem with datafile recovery
Hemant K Chitale

Un register and register database again in the same catalog

Dear All,
I've a requirement to Un-register the existing database from the catalog by removing all its information, and immediately registering the same database in the same catalog.
Please advice How to unregister and register again by retaining the backup files that are on tape.
Immeidate reply is highly appreciated.
Thanks

http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmrepos.htm#442604
Unregistering a Target Database from the Recovery Catalog
RMAN can unregister a database as well as register it. Make sure this procedure is what you intend, because if you make a mistake, then must reregister the database. In this case, you lose any metadata that is older than the CONTROLFILE_RECORD_KEEP_TIME setting in the target database control file.
To unregister a database:
   1. Start RMAN and connect to the target database. Note down the DBID value that is displayed when you use RMAN to connect to the target database. For example, enter:
% rman TARGET / CATALOG rman/cat@catdb
connected to target database: RDBMS (DBID=1237603294)
connected to recovery catalog database
   2. List the copies and backup sets recorded in the repository (refer to "Listing RMAN Backups, Copies, and Database Incarnations"). For example, enter:
LIST BACKUP SUMMARY;
List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Tag
19      B A A DISK        08-FEB-02       1       1       TAG20020208T155239
20      B F A DISK        08-FEB-02       1       1       TAG20020208T155242
21      B A A DISK        08-FEB-02       1       1       TAG20020208T155331
22      B A A DISK        08-FEB-02       1       1       TAG20020208T155604
   3. Run DELETE statements to delete all existing physical backups (refer to "Deleting Backups and Copies"). For example:
DELETE BACKUP DEVICE TYPE sbt;
DELETE BACKUP DEVICE TYPE DISK;
      RMAN will list the backups that it intends to delete and prompt for confirmation before deleting them.
   4. Use SQL*Plus to connect to the recovery catalog database as the catalog owner, then execute the following query in the recovery catalog to find the correct row of the DB table, setting DB_ID equal to the value you obtained from step 1. For example, enter:
% sqlplus rman/cat@catdb
SQL> SELECT DB_KEY, DB_ID FROM DB WHERE DB_ID = 1237603294;
      This query should return exactly one row.
DB_KEY     DB_ID
         1 1237603294
1 row selected.
   5. While still connected to the recovery catalog, enter the following, where DB_KEY and DB_ID are the corresponding columns from the row you got from the query in step 4:
SQL> EXECUTE dbms_rcvcat.unregisterdatabase(db_key, db_id)
      For example, enter:
SQL> EXECUTE dbms_rcvcat.unregisterdatabase(1, 1237603294)Aron

RMAN catalog and Target database

Hi All,
Please clarify my below doubts.
We have one server "server1" with oracle (catalog database) version 10.2.0.1
I have server "server2", and we have four oracle homes with four oracle users.Each oracle home consist of one database. all database are with 10.2.0.3 version.
All these databases registered with the above catalog database.
1 -> Can we register databases with a lower catalog database.
2 -> Now we are upgrading one database to 10.2.0.5 (in server2), in upgrade step we need to action step -: catalog upgrade. If we run this command actually what will be the result?
3 -> We are upgrading only one database in server2. remaining 3 database are in the version 10.2.0.3, upgrade catalog command will upgrade catalog database to 10.2.0.5 version, am I right?
4 -> Here do I need to run upgrade catalog ?
Thanks,
Asim
Edited by: user229955 on Feb 25, 2012 4:18 PM

Please refer this MOS document *RMAN Compatibility Matrix [ID 73431.1]*
You would surely get your answers if you mark your previous questions as answered rather than keeping it open.

Can't register a database in RMAN catalog (PL/SQL package not current)

Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
Regards

user13064912 wrote:
Hi RMAN experts. I'm trying to register a 10.2.0.1.0 database into a 10.2.0.5.0 RMAN catalog but I get the following error (Note: following was done on the rman server machine, ORACLE_SID=rman, target database is remote)
$ rman catalog rman/rman target sys@MPOWER
Recovery Manager: Release 10.2.0.5.0 - Production on Sat Apr 30 12:54:16 2011
Copyright (c) 1982, 2007, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not current
connected to target database: MPOWER (DBID=**********)
connected to recovery catalog database
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===============
RMAN-00569: =========ERROR MESSAGE STACK FOLLOWS
RMAN-00571: =================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
Basically the error says that there are two packages in the TARGET database (SYS.DBMS_BACKUP_RESTORE and SYS.DBMS_RCVMAN) which are not compatible with the RMAN catalog.
I cannot register the target database into the RMAN catalog.
I highly appretiate if you give me an advice on this.
RegardsCould you try to run the rman at the target database server (MPOWER), instead of rman catalog server ant try to register your database?
Your rman client is higher than your target server. That could be the problem.
Best Regards,
Gokhan
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks

Manually register rman backup with oracle database 10g

Dear All.
I want to restore full backup of database.
I have not configure flash_recovery_area.
how i can manually register full rman backup of database with oracle database 10g.?
Please help me.
Thanks & Regards
Ravi Kumar

This is the 10gR2 documentation on the CATALOG command :
http://docs.oracle.com/cd/B19306_01/backup.102/b14194/rcmsynta011.htm#sthref230
You must be specific when stating the version you are running. Commands may be limited or unavailable in older versions versus more recent versions of Oracle.
Hemant K Chitale

How can i do a RMAN backup of my database from the network ?

i'm using oracle 8i.1.7.3 with win server 2003
i want to know how can i do a RMAN backup of my database (sever machine A) from the network.
i'd like to save the backup in another machine (the same LAN, the same OS ).
to do that i've mapped a logical device in my comptur (z):
when i run rman command i got this error:
channel ORA_DISK_1: starting piece 1 at .......
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command ON ORA_DISK_1 channel at .......
00
ORA-19504: failed TO CREATE file "\\remote\save\"
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 123) The filename, directory name, or volume label syntax is inco
rrect.

Hi,
ORA-19504: failed TO CREATE file "\\remote\save\"make sure you have created this directory and change it's ownership (chown command)to oracle.
also make sure that oracle user has permission to write to this direcotry (chmod command)
hope this helps
cheers, walrus

Unable to register database in RMAN - RedHat 6.2 + Oracle 8.1.6

Is this a bug?? pls suggest the way out...
-Balaji
([email protected])
1. Create rman Tablespace
=============================
create tablespace TS_RMAN
datafile '/u01/orauser/oradata/mydb/TS_RMAN.dbf'
size 5M
autoextend on;
2. Create rman user
=============================
create user rmanusr identified by rmanusr
default tablespace TS_RMAN
temporary tablespace TEMP
quota unlimited on TS_RMAN;
3. Grant roles to rman user
==================================
grant connect, resource,recovery_catalog_owner to rmanusr;
4. I'm logging on the server directly
$rman target system/manager catalog rmanusr/rmanusr
5. RMAN> create catalog tablespace TS_RMAN
.... catalog created!
6. RMAN> register database;
... gives me all these errors messages >>
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-07005: error during channel cleanup
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.DEVICESTATUS
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
ORA-01403: no data found
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.GETPARM
------ end of message -------

Is this a bug?? pls suggest the way out...
-Balaji
([email protected])
1. Create rman Tablespace
=============================
create tablespace TS_RMAN
datafile '/u01/orauser/oradata/mydb/TS_RMAN.dbf'
size 5M
autoextend on;
2. Create rman user
=============================
create user rmanusr identified by rmanusr
default tablespace TS_RMAN
temporary tablespace TEMP
quota unlimited on TS_RMAN;
3. Grant roles to rman user
==================================
grant connect, resource,recovery_catalog_owner to rmanusr;
4. I'm logging on the server directly
$rman target system/manager catalog rmanusr/rmanusr
5. RMAN> create catalog tablespace TS_RMAN
.... catalog created!
6. RMAN> register database;
... gives me all these errors messages >>
RMAN> register database;
RMAN-03022: compiling command: register
RMAN-03023: executing command: register
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-07005: error during channel cleanup
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.DEVICESTATUS
RMAN-03008: error while performing automatic resync of recovery catalog
RMAN-07004: unhandled exception during command execution on channel default
RMAN-10032: unhandled exception during execution of job step 1:
ORA-01403: no data found
RMAN-10031: ORA-65535 occurred during call to DBMS_BACKUP_RESTORE.GETPARM
------ end of message -------

Register Database error in Rman

Hi
I have been trying to register a database in RMAN . Here are the steps I took on OS linux Mandrake 8.1 using ORACLE version 9.2.0.1.0
SQL:
CONNECT sys/password@ora AS SYSDBA
CREATE TABLESPACE "RMAN"
DATAFILE 'C:\ORACLE\ORADATA\W2K1\RMAN01.DBF' SIZE 6208K REUSE
AUTOEXTEND ON NEXT 64K MAXSIZE 32767M
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO;
CREATE USER rman IDENTIFIED BY rman
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE rman
QUOTA UNLIMITED ON rman;
GRANT connect, resource, recovery_catalog_owner TO rman;
rman catalog=rman/rman@ora
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to recovery catalog database
recovery catalog is not installed
RMAN> create catalog tablespace "RMAN";
recovery catalog created
RMAN> exit
Recovery Manager complete.
rman catalog=rman/rman@ora target=sys/password@w2k2
Recovery Manager: Release 9.2.0.1.0 - Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: ora (DBID=1371963417)
connected to recovery catalog database
RMAN> register database;
This is returning the error message
RMAN-00571:
RMAN-00569:
RMAN-00571:
RMAN-03002:failure of register command at 07/16/03 12:56
RMAN-03014:implicit resyncof recovery catalog failed
RMAN-03009:failure of full resync command on default channel at 07/16/03
ORA01001- cursor not valide

Hi,
Change the name of your tablespace RMAN to CATTBS. I believe RMAN is a reserved word in oracle.

Unable to register database in catalog into emrep

Hello guys,
I have a RMAN catalog in one server that works fine, now I tried to move this catalog to the emrep database (In this database I have the Grid Control), as I can´t use export / import because the original database is 10.1.0.5 and the emrep database is 10.1.0.4, I have created a new catalog into the emrep database.
The problem appear when I try to register one database on it:
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/15/2009 12:10:43
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
So, my first question is: Is possible create a RMAN catalog in the same database of Grid Control?
If this is possible, any suggestions that can help me to resolve this errors?
Thanks.

Hello Damorgan, thanks for your answer.
I follow the steps in a remote database ( BEEVODES ) which I want register into catalog ( tstsuse11-emrep ):
oracle@srvdb01 ~]$ echo $ORACLE_BASE
*/u01/app/oracle*
oracle@srvdb01 ~]$ echo $ORACLE_HOME
*/u01/app/oracle/product/10.1.0/db_1*
oracle@srvdb01 ~]$ export ORACLE_SID=BEEVODES
oracle@srvdb01 ~]$ rman target / catalog rman@tstsuse11-emrep
Recovery Manager: Release 10.1.0.5.0 - 64bit Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: BEEVODES (DBID=822996874)
recovery catalog database Password:
connected to recovery catalog database
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of register command on default channel at 09/16/2009 12:12:49
RMAN-10015: error compiling PL/SQL program
RMAN-10033: error during compilation of job step 1: ORA-01041: internal error. hostdef extension doesn't exist
ORA-04029: error ORA-3113 occurred when querying ORA_KGLR7_DEPENDENCIES
But I continue with the same error.
I supose the instalation of emrep is ok, because the Grid Control ( installed there ) works fine.
Thanks again.

Rman: can't open catalog

Hi, Completely new to all this rman stuff. Reading up in the Oracel Database 10g DBA Handbook which has a step by step on RMAN. I have failed at the first hurdle, getting error message "rman: can't open catalog" when I type "rman catalog rman/rman001" havingf set up the Oracle SID alreafy. If I type "rman" and nothing else the sessions hangs?
Any thoughts and advice most welcome.

export ORACLE_SID
export ORACLE_HOME
export PATH
export ORACLE_BASE
Now Create RMAN catalog
1. Create tablespace specific for rman catalog
2. Create user schema specific for rman repository
3. Grant connect,resource,sysdba,recovery_catalog_owner roles to rmanuser
4. Now connect using RMAN utility
rman target rmanuser/password@sid catalog rmanuser/password@sid
5. On RMAN prompt now create the catalog using 'CREATE CATALOG' command
6. Register database;
Now RMAN catalog is ready. If you start taking backup the information about the backup sets will go to the catalog in the schema that you created. Controlfile is the default repository for RMAN. You can work with RMAN witout catalog aswell. For advantages/disadvantages go to http://oracle.com/technology
documentation section and download RMAN documents.

RMAN-06403 When registering remote target DB

I'm running Oracle 10.2 Enterprise on RHEL4 (local pc) and Solaris (target db). I have a test db locally on my PC. I established the recovery catalog and successfully tested out backup functionality on my local test db. Now, I reset my SID and attempt to register a remote target database from within RMAN, I get the below error:
[oracle@tony dbs]$ rman target / \ catalog rman/rman@t_dev
Recovery Manager: Release 10.2.0.1.0 - Production on Mon Jun 25 16:04:41 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database (not started)
connected to recovery catalog database
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 06/25/2007 16:04:45
RMAN-06403: could not obtain a fully authorized session
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux Error: 2: No such file or directory
The recovery catalog database is running. The target database is also running. I can tnsping the target database and also connect via sqlplus with the connect string username/password@target_db.
Why am I generating this error connecting to a remote db in rman?
Thanks.

I get the below error when I grant sysdba & sysoper to rman. This was suggested in another post:
SQL> grant sysdba to rman;
Grant succeeded.
SQL> grant sysoper to rman;
Grant succeeded.
SQL> exit
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
[oracle@tony dbs]$ rman target sys/oracle@es_dev catalog rman/rman@t_dev
Recovery Manager: Release 10.2.0.1.0 - Production on Tue Jun 26 17:19:22 2007
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

Error while registering database

Hi,
I get "RMAN-03008: error while performing automatic resync of recovery catalog" while registering a database which is located on my server.
Following is the procedure i have done to register it.
C:\Documents and Settings\yogeshn.RITPL>rman target=sys/sys@oracle10 catalog=rman/rman@rman_db
Recovery Manager: Release 10.2.0.3.0 - Production on Mon Dec 12 12:23:02 2011
Copyright (c) 1982, 2005, Oracle. All rights reserved.
PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is
not current
PL/SQL package SYS.DBMS_RCVMAN version 10.02.00.00 in TARGET database is not cur
rent
connected to target database: ORACLE10 (DBID=2437633359)
connected to recovery catalog database
RMAN> connect target;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06167: already connected
RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03008: error while performing automatic resync of recovery catalog
ORA-00904: : invalid identifier
RMAN>
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

PL/SQL package SYS.DBMS_BACKUP_RESTORE version 10.02.00.00 in TARGET database is not currentIt seems the rman version (10.2.0.3) is higher than the target database version, this is not supported. Make sure rman executable and target database are on the same level.

RMAN restore from active database, ASM

I'm attempting to refresh a stage database from a prod database using RMAN restore from active database. Both are on ASM. After working through various hurdles, I've got one issue I'm a bit stuck on. I've got a handful of data files that do NOT have OMF names (ie MSTRDATA/mstrmdpd/datafile/gsa_indx instead of MSTRDATA/mstrmdpd/datafile/gsa_indx.351.714779777) and these are failing when I do the restore. The syntax I'm using in RMAN is as follows:
duplicate target database to dwstage
from active database
spfile parameter_value_convert 'dwprod','dwstage'
SET DB_FILE_NAME_CONVERT '+DWPROD','+DWSTAGE'
SET LOG_FILE_NAME_CONVERT '+DWPROD','+DWSTAGE';
The error message I'm getting is this:
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 04/21/2011 13:26:24
ORA-17628: Oracle error 19505 returned by remote Oracle server
continuing other job steps, job failed will not be re-run
Normally from what I've seen/read this error can be traced back to needing to pre-create the directories for the controlfiles etc, but since 90% of the datafiles copied correctly...
Any suggestions as to a way around this, or am I going to be forced to restore from a backupset?

This fails saying that "ORA-12528: TNS:listener: all appropriate instances are blocking new connections" which is quite normal given that the listener is havig a handle in BLOCKED state for this AUXDB as it is in NOMOUNT state.
Could you please help me on how to proceed?
One option can be to create the controlfile manually and mount the instance before doing the duplicate. I hope Rman can continue from there.
Another option is to go for backup based duplicate.
Is there any other way to go?
Provide static registration on AUXILIARY side for your auxiliary instance and try again.For example change listener.ora file as
SID_LIST_LISTENER =
(SID_LIST =
    (SID_DESC =
      (GLOBAL_DBNAME = AUXDB)
      (ORACLE_HOME = <your oracle home>)
      (SID_NAME = AUXDB)
LISTENER =
(DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = <auxiliary host/ip>)(PORT = 1521))
)And restart listener on auxiliary host then try again

RMAN-can't register database

Similar Messages

Maybe you are looking for