Firewall rules RMAN target database and RMAN catalog database

Hi, we are on Oracle 11.2.0.4 and we just build a new environment, in which case the RMAN catalog is located on a seprate from the target database server. I'm trying to figure if the firewall between these two rules should be two-way, so that the target database and RMAN catalog database can ping each other. If bi-directional rules in place, so what's the reason for this? I understand that during RMAN backup entries are made in the RMAN catalog database, but do not know if the RMAN catalog database must always meet target db. Thank you!

If you run the rman command on the target database server, it acts as a client to the catalog database server by connecting on sqlnet to the catalog database.

If you run the rman command on the catalog database server, it's a sqlnet connection join the target database server.

In both cases, rman is simply a client that connects to the two databases.

Hemant K Collette

Tags: Database

Similar Questions

Information on RMAN catalog database using and any catalog (controlfile)

Hi all.
I´d like some clarification on the subjects of RMAN RMAN usage with or without a recovery catalog (database / schema):
(1) will be the database controfile target always store ALL changes made on RMAN? For example, configure changes persistent RMAN as a retention strategy, controfile autobackup, backup optimization and so forth, these will always record on the target database controlfile, even if we're connecting to RMAN with a recovery catalog?
(2) what happens if we stop using the recovery catalog? I mean, if you don't use stored scripts and shot through the OS jobs or same EM control database, may continue to use then and do not connect more on the recovery catalog? It will be a problem? My target database stops?
I will be the legacy a few databases to administer and they connects to a catalog of recovery of database / schema, it's good, but I want to set up my own backup and restore policies / procedures in a two-step process: (1) have each configuration of RMAN database on controlfile, Later (2) in view of the use of the recovery catalog to centralized databases and keep more disk backup and restore.
Thanks in advance!

(1) Yes, everything about the structure of data is stored in the controlfile. The location of the backup controlfile is also stored in the controlfile.

The backup controlfile location is also stored in the catalog if you synchronize to it.

(2) you can stop immediately using the catalog if you choose, and as long as you have a backup RMAN script file, you can always backup using this file.

The catalog is used to store the location of the backupsets, and copy image. If you have any scripts to store, it can store these too. Really, it's all done catalog.

You can back up and restore/recover without a catalog, as long as you know where all backups are retained.

Block level of SUPPLY of RMAN catalog DB version and target DBs
DB catalog version: 11.2.0.2.3
Target the DBs: 11.2.0.2.3

Currently our catalog DB and target DBs (15 of them) are at the same level of power supply.
Let's apply PSU 5 (11.2.0.2.3) on some of the target DBs. should it apply PSU 5 (11.2.0.2.3) on the DB catalog first before we apply this power on the target of DBs?
Hi TeslaMan,
Probably, you mean that the RDBMS of the catalogue is version 11.2.0.2.3.
If you are upgrading a CPU target databases, you may need to upgrade the catalog to an equal or higher level schema.
Please check the version of the current catalog with the following sql schema.

Select * from RCVER;

Maybe you can create a catalog schema dummy with the task until RDBMS rman cli (perhaps you have tested the processor already?) and check the new version with the same sql.
Kind regards
Tycho

ORA-25408: can not read the appeal during a duplicate backup with rman catalog database safely

Hello
I did a database duplicate backup with rman catalog connection and got the ORA-25408: cannot read error call safely.
The catalog database is running in a Data Guard environment.
During the double process database failover occurred because of a server restart.
The restore of the data files was successful:
RMAN-08023: channel t1: restored the backup part 1
RMAN-08180: channel t1: restoration complete, duration: 00:01:15
RMAN-03091: finished the restoration at 27.08.2014 09:27:10
During execution of script memory:
RMAN-08161: content of the Script from memory:
{
switch from clone datafile;
}
RMAN-08162: execution of Script memory
I got this error:
RMAN-08162: execution of Script memory
RMAN-08031: output channel: t1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of Db in dual at 27/08/2014 09:27:10
RMAN-05501: abandonment of duplicate target database
RMAN-03015: an error has occurred in the script stored memory Script
RMAN-06004: ORACLE recovery catalog database error: ORA-25408: cannot read safely call
Dual boot time: 16:00
Failover time: 18:00
Error time: 09:00 the next day
DB version: 11.2.0.4.0, not the RAC environment, single instances
That's happened? My My db catalog rman session did not survive? Why the error happened at 09:00 (and not 17:00)? Why the session called the catalog rman during switching of the data files?
Can someone explain it to me?
Thank you!

Hello

The connection of the RMAN catalog remains inactive during the backup/restore process, once rman completes the task and try to activate the connection it gets error.

What is expected as you said the rebooted server. If this happens because of the expiration time, we went with the parameter net expire_time to maintain the connection.

Thank you

Bigot

target, auxiliary and catalog database

Hi gurus,
I need to have a few lights on the target, auxiliary and catalog databases.
especially difference between the auxiliary and the database catalog.
Kind regards
Manish

Hello

Your target is the database that you are backing up, and in the case of a duplicate database, it would be the source database. Example below is when I connect to the target database, which is what I want to save (note that below I sign in using the catalog in which case we'll use the controlfile and no catalog).
```
oracle:/home/oracle:testdb #> rman target /

Recovery Manager: Release 11.2.0.3.0 - Production on Mon Feb 17 15:24:02 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: testdb (DBID=2759143361)

RMAN>
```
The auxiliary database is the database which, in the case of a duplicate database, the database that you duplicate would be. So, for example, that if you configure a database ensure using the duplicate database (and maybe double active database database) the main database would be the target and the database pending would be the auxiliary.

The catalog database is when you use a RMAN catalog instead of using the control file... Note below to specify the catalog when you connect and it says 'connected to the datalog retrieval database' once you have connected that he did not in the example above when you signed in using the control file. In this case, the rman information is stored in the control as well as the datalog database file. (Control NB file is always the primary source").
```
oracle:/home/oracle:testdb #> rman target / catalog rman/password@rcat1

Recovery Manager: Release 11.2.0.3.0 - Production on Mon Feb 17 15:24:16 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

connected to target database: testdb (DBID=2759143361)
connected to recovery catalog database

RMAN>
```
There are several reasons why a catalogue database is used... for example:

(1) it can store scripts.

(2) you have a central repository for all of your databases.

(3) you are not limited as to how long you can store your backup information. Thie is determined by the controlfile_record_keep_time parameter when you use the controlfile and you type can be set quite high but then your controlfile can grow quite large as well.

Stor for more information on the recovery catalog, you can see below:

http://docs.Oracle.com/CD/E25054_01/backup.1111/e10642/rcmcatdb.htm

RMAN catalog by default for all databases of the value

Hello
I run a catalog RMAN 11 GR 1 material.
I wonder if it is possible to change a default setting in the RMAN catalog so that he will inherit all new databases.
For example, I would that all new data entered in the catalog for:
BACKUP OPTIMIZATION
REDUNDANCY 7 RETENTION STRATEGY
Thank you
Massi

No, the catalogue cannot "dictate" configurations for databases. Each database maintains configuration in the controlfile and this can be changed that by rman connection (i.e. rman connection to the database target). The command SETS in rman is used to define a "permanent" for a database configuration parameter but must be issued individually for each database.

Hemant K Collette

RMAN on what host target database
Hi guys,.

I have an obligation to present a report that shows the time required for each target listed in the catalog database backup.

I get these details to RC_RMAN_BACKUP_JOB_DETAILS.

Problem:
======
I now host listed in the report with the database name.

Is there a view or something that has the host name of all the registed to target in the catalog databases.

Thank you
Silver
Hello;

The RMAN catalog knows DBID because that's what is needed for backup and restore. I'm almost certain that the host information are not stored in the catalog as RMAN should or do not care about this information.

You can create own search for this table.

Best regards

mseberg

Database SID and SID of target database catalog is be
Hello

my database of catalog SID is PROD @ rmandb
and target database is SID PROD @ test8

How do I configure the tnsnames and connect to the database to record the catalog
RMAN target sys/sys@PROD rcvcat rman/rman@PROD
Save the database;

Verification through tnsping on RMANDB
tnsping PROD

AMT Ping Utility for IBM/AIX RISC System/6000: Version 9.2.0.3.0 - Production on 24 February 2013 21:32:33

Copyright (c) 1997 Oracle Corporation. All rights reserved.

Use settings files:

TNSNAMES adapter used to resolve the alias
Try to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rmandb) (PORT = 1524)) (CONNECT_DATA = (SID = PROD)))
OK (0 msec)

1. is it necessary to have different SIDs?

2. for the two database DBID is different.

Thank you.
981553 wrote:
Hello

my database of catalog SID is PROD @ rmandb
and target database is SID PROD @ test8

How do I configure the tnsnames and connect to the database to record the catalog
RMAN target sys/sys@PROD rcvcat rman/rman@PROD
Save the database;

Verification through tnsping on RMANDB
tnsping PROD

AMT Ping Utility for IBM/AIX RISC System/6000: Version 9.2.0.3.0 - Production on 24 February 2013 21:32:33

Copyright (c) 1997 Oracle Corporation. All rights reserved.

Use settings files:

TNSNAMES adapter used to resolve the alias
Try to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = tcp)(HOST=rmandb) (PORT = 1524)) (CONNECT_DATA = (SID = PROD)))
OK (0 msec)

1. is it necessary to have different SIDs?

2. for the two database DBID is different.

Thank you.

Name two different databases, the same is a very stupid thing to do. I correct that if I could. However, assuming that 'rmandb' and 'test8' are the names of two different servers, your tnsnames would look like this
```
prod_rmandb =
       (DESCRIPTION =
         (ADDRESS_LIST =
           (ADDRESS = (PROTOCOL = TCP)(HOST = rmandb)(PORT = 1521))
             )
         (CONNECT_DATA =
           (SERVICE_NAME = prod)
         )
       )

prod_tes8 =
       (DESCRIPTION =
         (ADDRESS_LIST =
           (ADDRESS = (PROTOCOL = TCP)(HOST = test8)(PORT = 1521))
             )
         (CONNECT_DATA =
           (SERVICE_NAME = prod)
         )
       )
```
And your connection string would be
```
rman target sys/sys@prod_test8 rcvcat rman/rman@prod_rmandb
```

RMAN-06429: TARGET database is not compatible with this version of RMAN
He Hi,.
How can I solve this problem. How I will modernize the Rman. My database of production 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
AMT for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production

while I'm setting up rman I get below error. Please help me.

C:\Documents and Settings\vj.dcruz > target rman / catalog rman01/rman01@upp

Recovery Manager: release 11.2.0.1.0 - Production Wed Sep 14 08:18:02 2011

Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.

Recovery Manager incompatible with the TARGET database: required 8.0.4.0 to 10.2.0.0 RMAN
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-00554: initialization of the package manager internal collection failed
RMAN-06429: TARGET database is not compatible with this version of RMAN

Rgds,
John
Johnvd wrote:
Hi Hemant,

I do the same database connection 10.2.0.0 thing and configure the rman but while connect target its saying that my Recovery Manager: version 11.2.0.1.0 - Production the sea Sep 14 09:04:59 2011

How its happens is there anywhere that I need to change the path.

Kind regards
John

John, you should use the binary RMAN that is located in the bin folder of Oracle database (IE u01/oracle/product/10.2/db1/bin). You should not use "rman which comes with Oracle 11g client".

If you are using windows, run the following commands at the command prompt, and then copy / paste the output:

echo % 5ORACLE_HOME
echo %path%

If you use unix, run the following commands in the terminal and then copy / paste the output:

echo $ORACLE_HOME
echo $PATH

Concerning

Grosbois

Get information directly from the database of the RMAN catalog
All,

Assuming that one is unable to connect to the target database, but can directly connect to the catalog database:

HostName: rman.prod.hobank.net
User name of the operating system: oracle
Oracle SID: RMAN
User RMAN: rman

When you are connected to the RMAN database as user rman (as shown below),

[oracle@rman] sqlplus rman/rman

What views I need to ask for the following information:

-Backups performed
-Backup type (for each backup)
-Calendar

Thanks in advance.

Baffy
You can get all the information backup recovery catalog views. For example, V$ RC_BACKUP_SET, V$ RC_BACKUP_PIECE, V$ RC_BACKUP_FILES, etc. and the view contains the type of backup as
V$ RC_BACKUP_FILES. BACKUP. But I don't understand your 'calendar' means.

Quick question: redundant databases to RMAN catalog
Dear friends,

Can someone tell me if it is possible to set up a database of catalog RMAN redundant, and how this work?

Thank you.

JI Li
Hi Ji Li,
I'm not sure how your environment is building so you can adjust some settings.

The steps would be:
-Clone your current catalog (or a recent backup) to a second machine.
S ' ensure that rman sessions can connect via tns in the catalogue of the second.
-Running following script once a day in an annex separate from the backup.

# Connect to the RMAN catalog
Connect catalog /@.
# Connect to the TARGET database as defined by ORACLE_SID
connection target;
# Assign maintenance channel
assign the channel for the maintenance type 'SBT_TAPE '; # (or 'DISC')
# Resynchronize the changes of physical target in the second database catalog RMAN
Catalogue of resynchronization;
# Check which backup files can be deleted from the catalogue
cross-checking of backup;
# State change of expired backup to deleted
delete the backup expired;
# Channel maintenance
output channel;

Kind regards
Tycho

Edited by: tychos April 30, 2009 05:52

RMAN - Catalog and ControlFile Recovery
I recorded rock database (same host) and Fatima databases (in another machine) in the RECOVERY CATALOG.

I m sticking with Faure database backup using the recovery catalog

RMAN >

Complete recovery manager.
^ C
H:\ > rman target sys/farooq@farooq catalog rman2/cat@rock

Recovery Manager: Release 10.2.0.1.0 - Production on Mon Sep 8 14:41:17 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: FAURE (DBID = 1820635189)
connected to the recovery catalog database

RMAN > register database;

RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure of the register command to the default channel on 2008-09-08 14:41:37
RMAN-20002: target database is already registered in the recovery catalog

RMAN > outline report;

Report of the database schema

List of permanent data files
===========================
Size (MB) Tablespace RB segs Datafile file name
---- -------- -------------------- ------- ------------------------
1 YES D:\ORADATA\FAROOQ\SYSTEM01 480 SYSTEM. DBF
2 35 UNDOTBS1 D:\ORADATA\FAROOQ\UNDOTBS01 YES. DBF
SYSAUX 3 250 NO D:\ORADATA\FAROOQ\SYSAUX01. DBF
4 5 USERS WITHOUT D:\ORADATA\FAROOQ\USERS01. DBF
5 100 EXAMPLE NO D:\ORADATA\FAROOQ\EXAMPLE01. DBF

RMAN > list backup;

RMAN > backup as incremental compressed backupset of level 0 database more archivelog;

From backup 08-SEP-08
Current archived log
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of command thus backup archivelog at 2008-09-08 14:43:03
RMAN-03014: implicit recovery catalog Resync failed
RMAN-06004: error ORACLE recovery catalog database: RMAN-20020: incarnation of the database not defined

RMAN > list incarnation of database;

List of Incarnations of the database
DB key Inc key STATE ID DB name DB reset reset time SNA
------- ------- -------- ---------------- --- ---------- ----------
3641 3649 FAURE 1820635189 PARENT 534907 29 JULY 08
FAURE 3641 3642 1820635189 CURRENT 695424 08-SEP-08

RMAN > RESET DATABASE to incarnation 3642
2 >.

database restore the incarnation 3642

RMAN > backup as incremental compressed backupset of level 0 database more archivelog;

From backup 08-SEP-08
Current archived log
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid = 142 devtype = DISK
channel ORA_DISK_1: starting from backupset journal archive compressed
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence 1 recid = 4 = 664886867 stamp =
archive log entry thread = 1 sequence 2 recid = 5 = 664888152 stamp =
archive log entry thread = 1 sequence = recid 3 = 6 = 664888938 stamp
archive log entry thread = 1 sequence 4 recid = 7 = 664889572 stamp =
archive log entry thread = 1 sequence 5 recid = 8 = 664889658 stamp =
archive log entry thread = 1 sequence 6 recid = 9 = 664891871 stamp =
archive log entry thread = 1 sequence 7 recid = 10 = 664892590 stamp =
archive log entry thread = 1 sequence 8 recid = 11 = 664900983 stamp =
archive log entry thread = 1 sequence 9 recid = 12 = 664902190 stamp =
channel ORA_DISK_1: from room 1 to 08 - SEP-08
channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150314_4D9Y35PK_. Tag BKP = comment TAG20080908T150314 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:26
channel ORA_DISK_1: starting from backupset journal archive compressed
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence 8 recid = 1 stamp = 664886398 =
archive log entry thread = 1 sequence 9 recid = 2 = 664886399 stamp =
archive log entry thread = 1 sequence 10 recid = 3 = 664886403 stamp =
channel ORA_DISK_1: from room 1 to 08 - SEP-08
channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150314_4D9Y407K_. Tag BKP = comment TAG20080908T150314 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:09
Backup finished 08-SEP-08

From backup 08-SEP-08
using channel ORA_DISK_1
channel ORA_DISK_1: additional start-up compressed 0 datafile backupset
channel ORA_DISK_1: specifying datafile (s) in backupset
input datafile fno = 00001 name = D:\ORADATA\FAROOQ\SYSTEM01. DBF
input datafile fno = 00003 name = D:\ORADATA\FAROOQ\SYSAUX01. DBF
input datafile fno = 00005 name = D:\ORADATA\FAROOQ\EXAMPLE01. DBF
input datafile fno = name 00002 = D:\ORADATA\FAROOQ\UNDOTBS01. DBF
input datafile fno = 00004 name = D:\ORADATA\FAROOQ\USERS01. DBF
channel ORA_DISK_1: from room 1 to 08 - SEP-08
channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_NNND0_TAG20080908T150351_4D9Y49WW_. Tag BKP = comment TAG20080908T150351 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:01:15
Backup finished 08-SEP-08

From backup 08-SEP-08
Current archived log
using channel ORA_DISK_1
channel ORA_DISK_1: starting from backupset journal archive compressed
channel ORA_DISK_1: specification of archive log backup set
archive log entry thread = 1 sequence 10 recid = 13 = 664902308 stamp =
channel ORA_DISK_1: from room 1 to 08 - SEP-08
channel ORA_DISK_1: finished piece 1 to 08 - SEP-08
piece handle = D:\ORADATA\FLASH_RECOVERY_AREA\FAROOQ\BACKUPSET\2008_09_08\O1_MF_ANNNN_TAG20080908T150512_4D9Y6T1D_. Tag BKP = comment TAG20080908T150512 = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:02
Backup finished 08-SEP-08

From control file and SPFILE Autobackup 08-SEP-08
piece handle = D:\ORACLE\RMAN_BACKUP\CTL_SP_BAK_C-1820635189-20080908-09 comment = NONE
Control finished and Autobackup SPFILE file 08-SEP-08

RMAN > list backup;

Backup list
===============
S LV TY Device Type delay #Pieces compressed #Copies Tag key
------- -- -- - ----------- --------------- ------- ------- ---------- ---
4615 DISC 08-SEP-08 1 1 YES TAG20080908T150314
4617 B 0 A DRIVE 08-SEP-08 1 1 YES TAG20080908T150351
4650 DISC 08-SEP-08 1 1 YES TAG20080908T150512
4670 HAS NO DISK 1 1 08 - SEP - 08 NO TAG20080908T150517

RMAN >

Now, I m conneting to Faure - target database and obtaining the same information from the control file backup.

H:\ > rman target sys/farooq@farooq

Recovery Manager: Release 10.2.0.1.0 - Production on Mon 8 Sep 15:05:38 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

connected to target database: FAURE (DBID = 1820635189)

RMAN > LIST BACKUP SUMMARY;

using the control file of the target instead of recovery catalog database

Backup list
===============
S LV TY Device Type delay #Pieces compressed #Copies Tag key
------- -- -- - ----------- --------------- ------- ------- ---------- ---
21. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150314
22. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150314
23 B 0 A DRIVE 08-SEP-08 1 1 YES TAG20080908T150351
24. A DRIVE 08-SEP-08 1 1 YES TAG20080908T150512
25 A NO DISK 1 1 08 - SEP - 08 NO TAG20080908T150517

My question: why are the information stored in the database control file (Faure) target so that its stored in the recovery catalog?
Hello

By default, RMAN stored metadata in the file control, all the RMAN is first written to control the file and then catalog of recovery if leaves. For example, when rman creates a new backupset, you can view the information in the v$ backup_set and you can also view the same information of the recovery RC_BAKCUP_SET catalog views.
So every change repository is stored in two places... Control file and optionally recovery_catalog

The catalog of recovery of the RMAN Repository versions are stored in database tables and version control repository os file stored as files in with in the control file.

-Pavan Kumar N

RMAN catalog upgrade 11.2.0.4.7 with 11.2.0.4.0 database

Hello
One of my new database received from group fixes 11.2.0.4.7.
When I want to join this real my rman catalog database, I "PL/SQL package RMAN. DBMS_RCVCAT version 11.02.00.03 in the RCVCAT database is not current."
I can easily do a "catalogue of upgrade", but is there an impact on my other databases running 11.2.0.4.0, which cannot receive the patches group before long.
Thank you for your kind reply.
Eric

Hello

Having the RMAN catalog with a newer version than the database version and will not create any problem.

(Doc ID 73431.1) RMAN compatibility matrix

Thank you

Sundar

RMAN-05501: abandonment of duplicate target database
Hello

I have a little problem with my duplication of the previous day.
The stupif thing is that I created the day before with this script, first time and after that I decided to recreate it in a different folder
and since then, I get this error at the end of the process.

starting media recovery

Journal archived for thread 1 with sequence 13143 is already on the disc in the file /archives/CMOVP/archivelogs/1_13143_810397891.arc
Journal archived for thread 1 with sequence 13144 is already on the disc in the file /archives/CMOVP/archivelogs/1_13144_810397891.arc
Journal archived for thread 1 with sequence 13145 is already on the disc in the file /archives/CMOVP/archivelogs/1_13145_810397891.arc
Journal archived for thread 1 with sequence 13146 is already on the disc in the file /archives/CMOVP/archivelogs/1_13146_810397891.arc
Archive log file name=/archives/CMOVP/archivelogs/1_13143_810397891.arc thread = 1 sequence = 13143
output channel: prm1
output channel: stby1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command duplicate Db at 01/05/2013 23:39:32
RMAN-05501: abandonment of duplicate target database
RMAN-03015: an error has occurred in the script stored memory Script
ORA-00283: cool cancelled due to errors
RMAN-11003: failure in parsing / execution of the SQL statement: alter database recover logfile ' / archives/CMOVP/archivelogs/1_13143_810397891.arc'
ORA-00283: cool cancelled due to errors
ORA-00354: corrupted redo log block header
ORA-00353: journal corruption near block 2048 change 1524092704 time 01/05/2013 22:18:20
ORA-00334: archived log: ' / archives/CMOVP/archivelogs/1_13143_810397891.arc'

I followed all the steps to create the instance of relief, as I said, I've created a first time

What has changed the second time is that I have insert the following parameters in my init.ora

db_file_name_convert = "/ oradata/oradata/cmovelprodco/cmovelprodco ', ' / oradata/oradata/cmovelproddr/cmovelproddr.
LOG_FILE_NAME_CONVERT = "/ oradata/oradata/cmovelprodco/cmovelprodco ', ' / oradata/oradata/cmovelproddr/redolog".

I run the script to duplicate the db:

run
{
allocate channel prm1 type disk;
allocate auxiliary channel stby1 type disk;
DUPLICATE TARGET DATABASE
FOR STANDBY
ACTIVE DATABASE
DORECOVER
NOFILENAMECHECK;
}

But every time I had this type of corruption archivelog
But when I validate the archives (archivelog Validate all) they are [OK]

Clues?
Thxs for your help
okKarol wrote:
To the main Site

SQL > select GROUP #, TYPE, substr (MEMBER, 1, 40) from v$ logfile;

GROUP # TYPE SUBSTR (MEMBER, 1, 40)
---------- ------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------
3 /data1/oracle/CMOVP/redo01g3.rdo online
3 /data2/oracle/CMOVP/redo02g3.rdo online
2 /data2/oracle/CMOVP/redo02g2.rdo online
2 /data1/oracle/CMOVP/redo01g2.rdo online
1 /data1/oracle/CMOVP/redo01g1.rdo online
1 /data2/oracle/CMOVP/redo02g1.rdo online
4 /data1/oracle/CMOVP/Stbyredo01g4.rdo EVE
5 /data2/oracle/CMOVP/Stbyredo01g5.rdo EVE
6 /data1/oracle/CMOVP/Stbyredo01g6.rdo EVE
7 /data2/oracle/CMOVP/Stbyredo01g7.rdo EVE

In secondary Site

1 * select GROUP #, TYPE, substr (MEMBER, 1, 40) in v$ logfile

GROUP # TYPE SUBSTR (MEMBER, 1, 40)
---------- ------- ----------------------------------------------------------------------------------------------------------------------------------------------------------------
/Mcelnetapp/Data1/Oracle/CMOVP/redo01g3.RDO in LINE 3 > I have rename manually
3 /mcelnetapp/data2/oracle/CMOVP/redo02g3.rdo online > renames manually
2 /data2/oracle/CMOVP/redo02g2.rdo online
2 /data1/oracle/CMOVP/redo01g2.rdo online
1 /mcelnetapp/data1/oracle/CMOVP/redo01g1.rdo online > rename manually
1 /mcelnetapp/data2/oracle/CMOVP/redo02g1.rdo online > renames manually
4 /data1/oracle/CMOVP/Stbyredo01g4.rdo EVE
5 /data2/oracle/CMOVP/Stbyredo01g5.rdo EVE
6 /data1/oracle/CMOVP/Stbyredo01g6.rdo EVE
7 /data2/oracle/CMOVP/Stbyredo01g7.rdo EVE

Then
```
SQL> SHUTDOWN IMMEDIATE
```
Move files:
MV /data1/oracle/CMOVP/redo01g2.rdo /mcelnetapp/data1/oracle/CMOVP/redo01g2.rdo
MV /data2/oracle/CMOVP/redo02g2.rdo /mcelnetapp/data2/oracle/CMOVP/redo02g2.rdo
```
SQL> STARTUP MOUNT
SQL> ALTER DATABASE RENAME FILE '/data1/oracle/CMOVP/redo01g2.rdo' to '/mcelnetapp/data1/oracle/CMOVP/redo01g2.rdo';
SQL> ALTER DATABASE RENAME FILE '/data2/oracle/CMOVP/redo02g2.rdo' to '/mcelnetapp/data2/oracle/CMOVP/redo02g2.rdo';
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
```
Concerning
Mr. Mahir Quluzade

How to save a database to use the RMAN catalog using the OEM 11 g grid
How to save a database to use the RMAN catalog using the OEM 11 g grid?

---------------------------------------------------------------------
Enterprise Manager Version: 11.2.0.2
See the availability tab, and then click 'Recovery catalog settings' under the Backup/Restore Configuration.

Choose the option 'Use Recovery Catalog'. Click the 'Add Recovery Catalog' button to add the recovery catalog. And fill required fields like username, host, port, sid, etc..

Talip Hakan Öztürk
http://taliphakanozturken.WordPress.com/

Firewall rules RMAN target database and RMAN catalog database

Similar Questions

Maybe you are looking for