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]
Similar Messages
-
Rman backup with standby database
Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
Hi All,
I am looking for some suggestions for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';
sql statement: alter system archive log current noswitch
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
ORA-01109: database not open
Recovery Manager: Release 11.2.0.1.0
Oracle databaes Release 11.2.0.1.0 64 bit
OS:RHEL 6 x86-64 bit
Secondly, do I need to cancel manged recovery while taking rman backups on standby.
I scanned thru MOS but could find solutions for rman with active DG.
Thanks in advance
"I scanned thru MOS but could find solutions for rman with active DG."
Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1) -
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 KumarThis 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 -
Remove RMAN information from target database control file
Dear Gurus,
Can any one inform me that how I can remove RMAN related information from Target database control file without recreating the control file.
Regards,
asifI want to remove all RMAN related infromation from control file including the destination specification where backup sets were being created becuase that destination is no more available,
configuration information also need to be removed from control file without recreating the control file.
kindly help,
regards,
asif -
[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 -
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 PMPlease 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. -
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,
Sameercheck 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,
AlexI'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-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,
johnJohnvd 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-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 PMHello 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.... -
RMAN: To Register 8i Database in 9i Catalog
Dear friends,
I am working with Oracle 9.0.1.1 under W2K. Recently I configured Recovery Catalog database in our 9i server. Now I wanted to register two target databases that are running in another server Oracle 8i (same network).
When I tried to register, I encounter the error like "RMAN version not combatible with Oracle 9.0.1.1 ... Target database version is too old"
Is it possible to register the target database 8i into 9i catalog??? If not, what could be the alternative?
Thanks in advance,
M M SheriffHey Sheriff,
have a look at the link below. It shows you all the compatibilities of RMAN catalog and target databases
and executables. I'm sure that you can use the 8i catalog and executable for oracle9i targets.
Hope this was a little helpful...
Cheers,
Ralf
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=73431.1 -
hello,
i would like to know if AWM 11.2.0.3.0A works against with oracle database 12c in pdb mode or not .
regards
jmI have attempted to connect 11g versions of AWM to 12c and get this error:
'This version of Analytic Workspace Manager is incompatible with the database instance. The Analytic Workspace Manager version is 11.2.0.3.0 and the database compatible version is 12.1.0.0.0'
So unfortunately it is not compatible, and there is currently no AWM for 12c
I also contacted Oracle support and they wont give me any information about a release date or any information on the xml template specification for 12c.
I guess we will just have to wait till they release a version of AWM that supports 12c...
Laszlo -
Error RMAN connection to auxiliary database ORA- 12514
Hi,
I'm trying to make a clone of my database in another server but when I'm trying to connect as follow the RMAN return
to me the error ORA-12514.
C:\Documents and Settings\joses.morales>rman TARGET sys/pass@iswgen nocatalog
AUXILIARY sys/[email protected]
Recovery Manager: Release 8.1.7.4.1 - Production
RMAN-06005: connected to target database: ISWGEN (DBID=2348350645)
RMAN-06009: using target database controlfile instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
For more information:
- the auxiliary database is started whit nomount option.
- this is my listener.ora in the auxiliary host
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = WSSP61)(PORT = 1521))
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = oracle8)
(ORACLE_HOME = C:\oracle\ora81)
(SID_NAME = iswgen)
(SID_DESC =
(GLOBAL_DBNAME = oracle8)
(ORACLE_HOME = C:\oracle\ora81)
(SID_NAME = oracle8)
- this is my tnsnames.ora in the auxiliary host
ISWGEN =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = wssp61)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = iswgen)
ORACLE8 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = WSSP61)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = oracle8)
- this is my tnsnames.ora in the target host
iswgen =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = gdcoracle)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = iswgen)
iswgen.wssp61 =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = wssp61)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = iswgen)
- target server: gdcoracle
- auxiliary server: wssp61
- global name in auxiliary: Oracle8
- intances in auxiliary: Oracle8 & Iswgen
I was expecting the follow message:
connected to target database: ISWGEN (DBID=519338572)
using target database control file instead of recovery catalog
connected to auxiliary database: ISWGEN.WSSP61 (not mounted)
Can anybody help me to resolve this error ORA-12514??
ThanksI'm try to connect to the auxiliary server at SQLPLUS and I get the follow:
C:\Documents and Settings\joses.morales>sqlplus /nolog
SQL*Plus: Release 8.1.7.0.0 - Production on Sex Jun 1 12:26:09 2007
(c) Copyright 2000 Oracle Corporation. All rights reserved.
SQL> conn sys@iswgen
Informe a senha:
ERROR:
ORA-12514: TNS:listener nao conseguiu resolver o SERVICE_NAME fornecido no
descitor de conexao
SQL> conn sys@iswgen as sysdba
Informe a senha:
ERROR:
ORA-12514: TNS:listener nao conseguiu resolver o SERVICE_NAME fornecido no
descitor de conexao
SQL> conn internal as sysdba
Conectado.
SQL>
Any sugestions?
Thanks everyone and regards -
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/ -
Duplicate target database for standby failing with below error
Hello All, Need your assistance
We are creating a physical standby database (standalone) from 2 node RAC database, OS =RHEL5 and DB =11gR2
What we did: We took RMAN backup of primary DB along with archives and copied to standby server in same location. We have modified necessory prameters on primary as well as standby too.
The command we used :
RMAN>connect target sys/pwd@primary auxiliary sys/pwd@stdby
RMAN> run {
allocate auxiliary channel ch1 type disk;
duplicate target database for standby dorecover nofilenamecheck;
release channel ch1;
Note we tried : duplicate target database for standby as well as duplicate target database for standby nofilenamecheck methods too....But no luck..we are getting following error.
channel ch1: reading from backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
channel ch1: ORA-19870: error while restoring backup piece /u01/BDB/BWFCCPRD_5fmpdvce_1_1
ORA-19501: read error on file "/u01/BDB/BWFCCPRD_5fmpdvce_1_1", block number 121856 (block size=8192)
ORA-27072: File I/O error
Additional information: 4
Additional information: 121856
Additional information: 1036288
failover to previous backup
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 10/20/2011 09:16:11
RMAN-05501: aborting duplication of target database
RMAN-05556: not all datafiles have backups that can be recovered to SCN 41855007833
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
could you pease help to resolve this ....?
Note : Creating standby using RMAN 11g new feature : duplicate target database for standby from active database is not possible in our environment since the network bandwith is tooooo low, We have tried and not able to succeed because of n/w issue, So we are doing this alternate method...!!!
Looking for your valuable advises...
Thanks in Advance....Take the fresh backup and also check the space crunch. The below clink may help you
ORA-27072: File I/O error Additional information: 2
--neeraj
Edited by: Vishen on Oct 20, 2011 2:14 PM
Maybe you are looking for
-
Lack of color calibratio​n box in toolbox
I have a photosmart d7360. It has been printing excessive greens in the grey area and the print quality pattern printout shows Lt Magenta as a magenta color and Magenta as a pale violet. The suggested solution from HP is as follows Click Start , poin
-
ITunes crashes every time I attempt 'Create AAC Version'
Why, all of a sudden, using Windows XP and latest version of iTunes, does my iTunes crash every time I attempt to 'Create AAC Version' of any song? I've been converting to AAC for years, and I don't think I downloaded any updates recently but out of
-
Itunes: An unknown error occurred (-50): external disk sleeping
Hi All. I posted this question about a year ago, but never got a usable answer. However, now I have more info, and thought I'd give it another try. I have an external disk that I attach via USB to my iMac running OS X 10.6.8, which is left on almost
-
Itunes9 crashes when CD put into computer
Hello Everytime i put a CD into my computer itunes crashes.So its impossible for me to put any of my music onto my nano. Ive tried reinstalling itunes and quick time but i keep getting the same message "itunes has stopped working". Ive even tried ins
-
Hi All, Does anyone know if you can use discoverer with a remedy database or any other sort of database other than Oracle ? Cheers Sandy