Rman: target database upgradation

hi,
My rman catalog database is 11.2.0.1 and target database is 10.2.0.4 (in windows server).
Now i have upgraded my target database to 11.2.0.1 from 10.2.0.4 . After upgradation backup is going fine.
My doubt is, whether the backup will be a valid one, or i have to unregister and register again the target database.
Please clarify my doubt.
Thanks & Regards,

Backup will be a valid one. No need to register again.
Regards
Asif Kabir

Similar Messages

RMAN-target database not found

Hello All:
we have rman config (0 level bkp) for our PROD backup, rman catalog is on a different server. running OK. heaving 0 level backup of our PROD.... no issue.
Now we have one more PROD db implemented recently for payroll on seperate server, so we decided to have rman backup of this also.
we set that rman script to here also and made the neccessary changes.
It is heaving backup, archive backup ... no issue ...
but it error while "RMAN Catalog resync"
that part from script is
## RMAN Catalog resync ##
rman log=/u01/bkp/logs/backup_resync.log << EOF
connect catalog rman/rman@rman
connect target /
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u01/bkp/backup/ctrl_%F';
resync catalog;
EOF
and the error on log file "backup_resync.log" getting:
Recovery Manager: Release 11.1.0.6.0 - Production on Fri Aug 10 04:25:04 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
RMAN>
connected to recovery catalog database
RMAN>
connected to target database: ORCL (DBID=2588904899)
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 08/10/2012 04:25:29
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
RMAN>
Recovery Manager complete.
plese suggest on this, i googled, saying to register the catalog, tried but no luck....
thanks in ADV
Edited by: DOA on 9 Aug, 2012 10:16 PM
Edited by: DOA on 9 Aug, 2012 10:17 PM

Hello vreddy,
Thanks for the reply...
I am bit new with the rman word....
I tried command on server where catalog exist (stating: my PROD and catalog exist on different different server)
(orcl is my PROD db name)
rman target / catalog ORCL
Recovery Manager: Release 10.2.0.1.0 - Production on Fri Aug 10 10:57:29 2012
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: RMAN (DBID=1583459273)
recovery catalog database Password:
asking for some password, which password here we need to supply ?
for more clear picture I also execute command on catalog side:
SQL> select name,DBID,RESETLOGS_TIME from rc_database order by 1;
NAME DBID RESETLOGS
PROD 4247251480 12-MAY-04
RMAN 1583455429 02-JAN-09
db ORCL is not there in the list....

ORA-12514: TNS:listener - RMAN - Target Database

Hi Pals,
Today while configuring two of my machines (On same Network) for RMAN I'm facing some issues while connect to the Catalog Server and register a target database.
Here are more details about the (Environment) -- machines:
Machine 1 - ORCL (Catalog Server)
Machine 2 - PRCL (Target Database)
Both machines and in same network.
Tnsping results: both machines are able to ping each other
Unix Ping results: both machines are able to ping
Listeners: Up and Running on both machines
Names: Listeners (Both Machines)
TNSnames: Created an for both machines in each others tnsnames.ora file.
tnslsnr status: Connected Both Machines)
OS: Linux Red Hat 5
Db: Oracle 11gR2
Status: DB are up and working good and both are in ARCHIVELOG Mode.
Env: VMWARE Team (Version 6)
So, while trying to connect to Catalog Server(DB Name: ORCL) from Target Machine (DB name: PRCL) I'm getting a TNS:Listener based error.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[oracle@localhost ~]$ rman target / catalog rman/oracle90@orcl
Recovery Manager: Release 11.2.0.1.0 - Production on Mon May 21 20:49:08 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PRCL (DBID=459947553)
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04004: error from recovery catalog database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
[oracle@localhost ~]$
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please assist and let me know in case more details required.
Thanks
Prashant Dixit

Hi Tychos/DMorgan,
Below provided are tnsentries and listener.ora file contents from both of the machines.
Yes, i'm using vmware (Team) and have 2 machines in the same network (1st ORCL - 2nd PRCL). Both of them are able to ping each other.
First Machine 1 - ORCL Instance:
*1. listener.ora file:*
+++++++++++++++++++++++++
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1)
(PROGRAM = extproc)
LISTENER1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
ADR_BASE_LISTENER = /u01/app/oracle
----> tnsnames.ora__
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl.localdomain)
PRCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = prcl.localdomain)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Machine 2: PRCL Instance -
listener.ora file
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
# listener.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /u01/app/oracle/product/11.2.0/db_1)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
---> tnsnames.ora file
# tnsnames.ora Network Configuration File: /u01/app/oracle/product/11.2.0/db_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
PRCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = prcl.localdomain)
ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = orcl.localdomain)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
I've tried several options with SERVICE_NAME and HOST name after your's and Morgan's post but no luck so far. Please let me know if need (*tnslsnr* status results as well)
So, this is what i originally have on my machine and yes I'm still getting ORA-12514: TNS:listener error.
Thank you guys for your attention.
Please help.
Thanks
Prashant Dixit
Edited by: OracleAnt ... on May 22, 2012 4:58 PM

RMAN target database Connectivity problem

Error while connecting to target database also tried as sys user but same error
C:\>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Wed Sep 10 11:06:31 2008
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

You can try like this
rman target 'DBNAME'
or set ORACLE_SID=DBNAME
then rman target /
Do you multiple oracle homes?
Is it in windows or in Unix
IF it is unix you should login as ORACLE user and execute the commands
Theuser should have the SYSDBA privilge
In windows the user excuting the command the user should be a part of the ORA_DBA group
Edited by: Maran Viswarayar on Sep 10, 2008 1:34 PM

RMAN-06429: TARGET database is not compatible with this version of RMAN

he Hi,
how can i solve this issue . how i will upgrade the Rman. My production database details are below
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
while i'm configuring rman i'm getting below error . please help me.
C:\Documents and Settings\vj.dcruz>rman target / catalog rman01/rman01@upp
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 08:18:02 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.0 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
rgds,
john

Johnvd wrote:
Hi Hemant,
i'm doing same thing login 10.2.0.0 database and configure the rman but while connect target its saying that my Recovery Manager: Release 11.2.0.1.0 - Production on Wed Sep 14 09:04:59 2011
how its happening is there any where i have to change the path.
Regards,
johnJohn, you need to use the RMAN binary which is located in bin folder of Oracle Database (ie /u01/oracle/product/10.2/db1/bin). You shouldn't use "rman which comes with Oracle 11g client".
If you are using windows, run the following commands in command prompt and then copy/paste the output:
echo 5ORACLE_HOME%
echo %PATH%
If you are using unix, run the following commands in terminal and then copy/paste the output:
echo $ORACLE_HOME
echo $PATH
Regards
Gokhan

RMAN incompatible with TARGET database

I have two databases:
The database with the catalog, version 8.1.7.
The database to be backed up (target), version 8.0.6.
When I try to connect to the target, I get an error stating: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
I've tried changing the "compatible" parameter to 8.0.4, but then I get an error when I restart the database (regarding locally managed tablespaces, which I am not using).
Any idea what I need to do to connect to the target database?
thanks....

Hi !
I guess you have confused the compatible init.ora parameter with RMAN compatible parameter ,
They are entirely different. The excerpts here, which i have taken from the Oracle online docs should
clear your problem.
The compatible parameter specifies the minimum acceptable release of the RMAN executable that can function with the catalog. For example, if the recovery catalog compatibility is set to 8.1.4, then only an RMAN executable of release 8.1.4 or later can connect to the catalog.
You cannot set the compatible parameter to a version that is not supported by the currently-installed DBMS_RCVMAN or DBMS_RCVCAT packages. If you try to set compatibility to a version that is not supported by one of the packages, then you receive an error message that indicates the lowest and highest value you can set, as in the following example:
RMAN> configure compatible = 8.0.1;
RMAN-03022: compiling command: configure
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: configure
RMAN-06455: illegal compatible value 8.0.1: must be between 08.00.04 and 08.01.06
To view the compatibility level of the recovery catalog:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Start a SQL*Plus session and connect to the recovery catalog database as the recovery catalog owner. For example, enter:
SQL> connect rman/rman@rcat
Issue the following query:
SQL> SELECT value FROM config WHERE name='compatible';
VALUE
080106
To create an 8.1.6 recovery catalog that is usable with a pre-8.1.6 RMAN executable:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
This procedure assumes that you have the use of both an 8.1.6 and pre-8.1.6 RMAN executable. The method employed it to use a pre-8.1.6 RMAN executable to create the recovery catalog, and a release 8.1.6 RMAN executable to upgrade it. The compatibility level is automatically set to 8.0.4, which has the implications described in Table 3-1.
Use a pre-8.1.6 RMAN executable to connect to the catalog database. For example, enter:
% rman catalog rman/rman@rcat
Recovery Manager: Release 8.1.5.0.0
RMAN-06008: connected to recovery catalog database
Create the recovery catalog and then exit. For example, enter:
RMAN> create catalog;
RMAN> exit
Note:
If you use a release 8.0 RMAN executable to create the catalog, you must use the catrman.sql script to create the recovery catalog.
Use the 8.1.6 RMAN executable to connect to the newly created recovery catalog:
% rman catalog rman/rman@rcat
Recovery Manager: Release 8.1.6.0.0
RMAN-06008: connected to recovery catalog database
Upgrade the recovery catalog to release 8.1.6:
RMAN> upgrade catalog;
RMAN> exit
The compatibility level of the recovery catalog is now automatically set to 8.0.4.
Regards,
Mohamed Iqbal.
[email protected]

TARGET database is not compatible with this version of RMAN

I am trying to register a database (version 8.0.4) on my catalog database which is version 8.1.7.
I get the following error:
RMAN-06185: Recovery Manager incompatible with TARGET database: RMAN 8.0.4 to 8.0.4 required
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
Does this mean that my RMAN database has to be 8.0.4 ?
What happens if my RMAN database is 8.0.4 and target is 8.1.7 ?
Thanks for any help,
Sameer

check RMAN compatibility matrix
Target/Auxiliary Database|| RMAN Executable|| Catalog Database ||Catalog Schema
8.0.3 8.0.3 >=8.x 8.0.3
8.0.4 8.0.4 >=8.x >= 8.0.4, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.5 8.0.5 >=8.x >= 8.0.5, see "Note 2: 8.1 or Later Catalog Schemas and 8.0 Target Databases"
8.0.6 8.0.6 >=8.x 8.0.6
8.0.6 8.0.6 >=8.1.x >=8.1.x
8.1.5 8.1.5 >=8.1.x >= 8.1.5
8.1.6 8.0.6.1 >=8.x 8.0.6
8.1.6 8.0.6.1 >=8.1.x >= 8.1.x
8.1.6 8.1.x >=8.1.x >= RMAN executable
8.1.7 8.0.6.1 >=8.x 8.0.6
8.1.7 8.0.6.1 >=8.1.x >=8.1.x
8.1.7 8.1.x >=8.1.x >= RMAN executable
9.0.1 >=9.0.1 >=8.1.x >= RMAN executable
In other words to backup 8.0.4 version u need a separate schema in catalog database and which will be only used for 8.0.4

TARGET database is not compatible with RMAN version

Hi all,
we have an issue related to RMAN version.
A few weeks ago we update our 10.2.0.1 Oracle Database to 10.2.0.4 using 6810189 pacth set.
Now when we try to execute RMAN this is the output:
Recovery Manager : Release 11.1.0.6.0 - Production on Jue Nov 20 12:20:57 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Recovery Manager incompatible with TARGET database: RMAN 8.0.4.0 to 10.2.0.4 needed
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-06429: TARGET database is not compatible with this version of RMAN
(I translate the spanish message, maybe the words is not exactly the same in the english version)
As is shown in the output the RMAN version installed by the pacthset is higher than database version, is there a way to downgrade RMAN or to solve this issue?
Thanks in advance,
Alex

I'm pretty sure patchset 6810189 does not install RMAN executable 11g. I did several patchings to 10.2.0.4 and that never happened. Patching may sometimes leave components at a lower level than the patchset,but never the opposite is true. That would be definitely a bug. So you (or someone else) installed 11g software.
Werner

RMAN duplicate target database for standby from active fails to create newname for system tablespace/datafile

When executing 'duplicate target database for standby from active' the system tablespace/datafile (datafile 1) is not cloned. All other datafiles clone successfully. The RMAN process aborts with the following errors while attempting to clone the system tablespace/datafile.
ORA-19558: error de-allocating device
ORA-19557: device error, device type: DISK, device name:
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-17627: ORA-01041: internal error. hostdef extension doesn't exist
ORA-03135: connection lost contact
Here are the details:
Primary is 11.2.0.2 RAC database on an Exadata platform
Standby is 11.2.0.2 Single Instance database (same patch level as primary) on a Red Hat Linux box
This is an ASM to ASM duplication.
This is not unique to this database. We tried another database and go the same behavior - all datafiles clone successfully with the exception of the system tablespace/datafile.
We have traced the RMAN execution and it seems to fail when it is trying to assign a NEWNAME to the system tablespace/datafile.
We even issued an explicit SET NEWNAME command but RMAN ignored it.
We also shutdown the primary and started is up in mount mode thinking that something had ahold of the System Tablespace/datafile.
We also opened up the network firewall to allow permit any,any traffic.
We increased the max_server_processes
and added TCP.NODELAY=yes to the sqlnet.ora file.
There seems to be some artifact present in our Primary System tablespace/data file that is preventing it form being cloned.
checked all alert files grid, asm, and dbhome - no abnormal messages.
We are in the process of restoring the database from a backup but we would prefer to get this working using the 'Active Database' methodology

I successfully created the standby database using RMAN backup and recovery.
I started the managed recovery. Archive logs are being sent from the primary to the standby ( I can see them in ASM), but the standby is not applying them.
I get the following messages in the standby alert log...
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:19:58 2013
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
Tue Nov 26 16:20:01 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:11 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:22 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
Tue Nov 26 16:20:32 2013
Fetching gap sequence in thread 2, gap sequence 154158-154257
I don't see any MRP processes:
select process,
status,
    thread#,
    sequence#,
   block#,
blocks
7     from v$managed_standby;
PROCESS   STATUS          THREAD# SEQUENCE#     BLOCK#     BLOCKS
ARCH      CLOSING               2     154363          1        132
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
ARCH      CONNECTED             0          0          0          0
RFS       IDLE                  0          0          0          0
RFS       IDLE                  1     145418        121          1
RFS       IDLE                  0          0          0          0
PROCESS   STATUS          THREAD# SEQUENCE#     BLOCK#     BLOCKS
RFS       IDLE                  0          0          0          0
12 rows selected.
SQL> SELECT THREAD#, SEQUENCE#, APPLIED FROM V$ARCHIVED_LOG;
   THREAD# SEQUENCE# APPLIED
         2     154356 NO
         2     154357 NO
         1     145411 NO
         2     154358 NO
         2     154360 NO
         2     154361 NO
         1     145414 NO
         1     145415 NO
         2     154362 NO
         2     154363 NO
         1     145416 NO
11 rows selected.
I do have the archive logs that cover sequences 154158-154257
Crosschecked 38 objects
Crosschecked 62 objects
Finished implicit crosscheck backup at 26-NOV-13
Starting implicit crosscheck copy at 26-NOV-13
using channel ORA_DISK_1
using channel ORA_DISK_2
Crosschecked 2 objects
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154377.344.832521989 RECID=29 STAMP=832521990
validation succeeded for archived log
archived log file name=+RECO_XORA/nmuasb00/archivelog/2013_11_26/thread_2_seq_154378.346.832521991 RECID=31 STAMP=832521993
Crosschecked 31 objects

RMAN duplicate target database error

Hello,
I’m trying to use RMAN ‘duplicate target from active database’ to a remote host however I’m getting a confusing error:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/19/2009 13:47:23
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of backup command on aux13 channel at 11/19/2009 13:47:23
ORA-19504: failed to create file "+DATA2"
RMAN-03009: failure of backup command on aux14 channel at 11/19/2009 13:47:23
ORA-19504: failed to create file "+DATA2"
Here’s my script:
connect target sys/<password>@node1;
connect auxiliary sys/<password>@node2;
spool log to '/u01/app/oracle/dba/duplicate111909.log'
run
allocate auxiliary channel aux11 device type disk;
allocate auxiliary channel aux12 device type disk;
allocate channel aux13 device type disk;
allocate channel aux14 device type disk;
duplicate target database to node2 from active database DB_FILE_NAME_CONVERT='+DATA1','+DATA2';
release channel aux14;
release channel aux13;
release channel aux12;
release channel aux11;
spool log off;
exit;
Node1 uses ASM disk group DATA1 and I intend to use ASM disk group DATA2 on node2. Has anyone seen this error before? I have tried various permutations of DB_FILE_NAME_CONVERT clauses but all error with ORA-19504. On a side note I was able to use ASMCMD cp command to copy a datafile from node1 DATA1 to node 2 DATA2. Also, if I use disk group DATA1 on node 2 then the RMAN duplicate command runs successfully, it only errors when using DATA2. And yes +DATA2 is mounted on node2:
SQL> select name, state from v$asm_diskgroup;
NAME STATE
DATA1 MOUNTED
DATA2 MOUNTED
Any and all ideas are welcome. I’m running out of things to check.
Thanks,
RJL

For a duplicate you don't need to give the DB_FILE_NAME_CONVERT especially if you go from a asm to asm diskgroup.
The place where it'll put all the files will be automatically done taking care of the init.ora file parameter db_create_file_dest, (db_create_online_log_dest_1)

How to get RMAN catalog information from Target database?

Hi,
How to get RMAN catalog information from Target database because i don't know about catalog database? is it possible?
Thanks

If you run RMAN backups of a target database using a Catalog schema in another database, the target is not aware of the catalog.
The RMAN backup script would have the connection identifier for the Catalog.
Hemant K Chitale

RMAN-05001 auxiliary .... conflicts with a file used by the target database

I can´t recreate my physical standby.
It worked in the past.
Now I reinstalled the 3 standbyclients.
Copied the spfile from the primary - modified the entries and did a rman backup.
But when issuing the duplicate database command - it comes up with the error above
SPFILE standyby db:
*.db_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
*.log_file_name_convert='+DATA/prim/','+DATA/stdy/','+RECOVERY/prim','+RECOVERY/stdy'
Starting restore at 15-APR-10
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle/stage/33lb65n2_1_1
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=/oracle/stage/33lb65n2_1_1 tag=TAG20100415T102434
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:11
output filename=+REDO1/stdy/controlfile/current.262.716293055
output filename=+REDO2/stdy/controlfile/backup.262.716293055
Finished restore at 15-APR-10
sql statement: alter database mount standby database
released channel: ORA_AUX_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 04/15/2010 10:31:46
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary filename DATA/prim/datafile/system.262.715097535 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.263.715097499 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs3.269.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs2.270.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/example.272.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/users.268.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/sysaux.273.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/undotbs1.271.710521021 conflicts with a file used by the target database+
RMAN-05001: auxiliary filename DATA/prim/datafile/system.264.710521021 conflicts with a file used by the target database+

Hi ,
I feel you are using ASM but still check the below details:
Cause
Production and Auxiliary have same directory structure and are running on two different machines. RMAN must be told not check that the target datafiles are sharing the same names as the duplicated files being created. Otherwise, the following errors will be returned:
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_03.dbf
conflicts with a file used by the target database
RMAN-05001: auxiliary filename /qmaxnt/u04/qmaxntorafiles/table/QMAXAD08_02.dbf
Solution
To implement the solution, please use nofilenamecheck in syntax as follows:
1. Connect to Target, auxiliary, and rman catalog and
2. use script as
run{
set until time "to_date('2005/09/17 14:00:00','yyyy/mm/dd HH24:MI:SS')";
allocate auxiliary channel aux1 type 'sbt_tape';
allocate auxiliary channel aux2 type 'sbt_tape';
duplicate target database for standby dorecover nofilenamecheck;
Make sure to use auxiliary type of channel so RMAN restore take place at auxiliary database.
Thanks,
Rafi.
http://rafioracledba.blogspot.com/

RMAN catalog fails to show target database information when in nomount mode

Hello everyone, I am trying to restore a dev. database from its own backup taken a week back. The DB is in noarchivelog mode and recently 2 of the datafiles were removed from the files system and thus the need to restore the DB from its backup. However rest of the files and control files are intact.
Now, when I put the database in mount mode and connect to the catalog then I can see the DB's incarnation;
:->rman catalog cde01_rman4/xxxxxxx@prman10g target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:54:40 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: EGVBFI2 (DBID=4238332493, not open)
connected to recovery catalog database
RMAN> list incarnation;
List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
84789 84883 EGVBFI2 4238332493 PARENT 2478183021921 17-JAN-04
84789 84790 EGVBFI2 4238332493 CURRENT 2498633332010 10-OCT-07
RMAN>
However I am not able to see DB incarnation in the RMAN catalog if I put the DB in nomount mode (which is required to recover DB);
:->rman catalog cde01_rman4/xxxxxx@prman10g target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 11 13:58:29 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: egvbfi2 (not mounted)
connected to recovery catalog database
RMAN> list incarnation;
RMAN>
Please advice?
Thanks,
Jairaj

Hi,
You won't be able to see incarnation information when the DB is in "nomount" since the incarnation is written in the control file. I don't think the catalog has this information.
Anyway, in order to restore datafiles, the instance must be mounted, so you should be OK.
Mount the instance and just restore the datafiles.
Liron Amitzi
Senior DBA consultant
link: [www.dbsnaps.com]
link: [www.obriumsoftware.com]

RMAN-20001: target database not found in recovery catalog

I am practicing loss off all control files. I have rman catalog backups which are set to autobackup controlfile. So far I did this.
RMAN> startup nomount;
Oracle instance started
Total System Global Area 209715200 bytes
Fixed Size 1272864 bytes
Variable Size 155190240 bytes
Database Buffers 50331648 bytes
Redo Buffers 2920448 bytes
RMAN> restore controlfile from autobackup;
Starting restore at 08-SEP-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
recovery area destination: /u02/flash_recovery
database name (or database unique name) used for search: TEST
channel ORA_DISK_1: autobackup found in the recovery area
channel ORA_DISK_1: autobackup found: /u02/flash_recovery/TEST/autobackup/2009_12_09/o1_mf_s_705171034_5l0kgv4o_.bkp
channel ORA_DISK_1: control file restore from autobackup complete
output filename=/u02/control_files/TEST/control02.ctl
output filename=/u03/oradata/TEST/control03.ctl
Finished restore at 08-SEP-10
RMAN> alter database mount;
database mounted
released channel: ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of alter db command at 09/08/2010 14:54:50
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
I am assuming this has something to do with DBID but ... I don't have it and I don't know how to find it.

Hi BelMan,
Here is output
BS Key Type LV Size Device Type Elapsed Time Completion Time
56869 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56871 Status: AVAILABLE Compressed: NO Tag: TAG20100908T135312
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-00
Control File Included: Ckp SCN: 125665520 Ckp time: 08-SEP-10
BS Key Type LV Size Device Type Elapsed Time Completion Time
56993 Full 11.20M DISK 00:00:00 08-SEP-10
BP Key: 56995 Status: AVAILABLE Compressed: NO Tag: TAG20100908T142547
Piece Name: /u01/oracle/product/10.2.0/db_1/dbs/cf_c-549414289-20100908-01
Control File Included: Ckp SCN: 125668490 Ckp time: 08-SEP-10

Recover Oracle DB 11.1.0.7 using target database controlfile RMAN Hot Backu

Hi All,
DB:11.1.0.7
OS:RHEL Linux 4 64-bit
Could anyone please share the "Steps to recover Oracle DB 11.1.0.7 using target database control file RMAN of previous Hot Backup"
We are not using Recovery Catalog.
Thanks for your time!
Regards,

If the current control file is still present on disk, you can merely issue a RESTORE DATABASE followed by a RECOVER DATABASE.
If you are not attempting a Complete Recovery (i.e. upto the last transaction in the online redo logs) and/or the online redo logs are not available, you would also include a SET UNTIL (scn or log sequence or time) clause in you RESTORE and RECOVER.
If the current control file is not available, you would STARTUP NOMOUNT, then restore the controlfile, then MOUNT the database before proceeding with the RESTORE and RECOVER.
Oracle will automatically identify and restore and apply the necessary archivelogs when you issue the RECOVER DATABASE. You don't need to manually restore them in advance. However, you will need sufficient disk space to restore the archivelogs (e.g. if the backup is 3 days old, Oracle will attempt to restore 3 days of archivelogs).
The standard documentation is at
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmcomre.htm#i1009223
I have numerous examples at
http://hemantoracledba.blogspot.com
and
https://sites.google.com/site/hemantswebsite/oracle-diagnostics/MyOracleBlogBackup_and_RecoveryPosts.pdf
Hemant K Chitale
Edited by: Hemant K Chitale on May 16, 2011 9:45 AM

Rman: target database upgradation

Similar Messages

Maybe you are looking for