RMAN-configure compatible

Hi all,
I've found in docs, that I can use the following statement:
Raise the compatibility of the catalog to the desired level. For example, enter:
RMAN> configure compatible = 8.1.5;
but in my database (8.1.7) there is a message:
RMAN-03022: compiling command: configure
RMAN-06456: command not supported
after raising such statement.
Anyone met such error?
James

The recovery catalog schema version must be greater than or equal to the RMAN client version.
http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/compat003.htm
RMAN Catalog version - 10.2.0.2
Target Database - 11R2
So, you need to upgrade you RMAN catalog database version.
Regards
Asif Kabir
user8610659
Handle:      user8610659
Status Level:      Newbie
Registered:      Nov 11, 2009
Total Posts:      6
Total Questions: *3 (3 unresolved)*
-- Mark your helpful post as correct/helpful and close all the answered threads.

Similar Messages

RMAN Script & RMAN Configuration

Dear All,
This is the first time i am using RMAN. i just wanted to execute the following RMAN script for a testing purpose, for this what are the RMAN configuration i must have to do before executing this script below:
RMAN> run {
shutdown immediate;
startup mount;
backup database;
alter database open;
}This is my current setup of RMAN
RMAN> show all;
RMAN configuration parameters for database with db_unique_name DP are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
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 CHANNEL DEVICE TYPE DISK FORMAT 'E:\RMAN\';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'E:\APP\10004\PRODUCT\11.2.0\DBHOME_1\DATABASE\SNCFDP.ORA'; # defaultKindly advice me and give me a very clear study for this above parameters
Regards
HAMEED
Once i execute that script i got this following error :
+RMAN> run {+
+2> shutdown immediate;+
+3> startup mount;+
+4> backup database;+
+5> alter database open;+
+6> };+
database closed
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area     770019328 bytes
Fixed Size                     1374780 bytes
Variable Size                301991364 bytes
Database Buffers             461373440 bytes
Redo Buffers                   5279744 bytes
Starting backup at 18-MAY-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=134 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00006 name=E:\APP\10004\ORADATA\DP\HAMEED01.DBF
input datafile file number=00007 name=E:\APP\10004\ORADATA\DP\ABDUL01.DBF
input datafile file number=00008 name=E:\APP\10004\ORADATA\DP\TEST01.DBF
input datafile file number=00001 name=E:\APP\10004\ORADATA\DP\SYSTEM01.DBF
input datafile file number=00002 name=E:\APP\10004\ORADATA\DP\SYSAUX01.DBF
input datafile file number=00005 name=E:\APP\10004\ORADATA\DP\EXAMPLE01.DBF
input datafile file number=00003 name=E:\APP\10004\ORADATA\DP\UNDOTBS01.DBF
input datafile file number=00004 name=E:\APP\10004\ORADATA\DP\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 18-MAY-11
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/18/2011 17:22:30
ORA-19504: failed to create file "E:\RMAN\"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
Edited by: Hameed on May 18, 2011 4:59 AM

Dear Chinar, can you please varify this below ,, is it correct,, after given your setup i ran this script,,,
Kindly advice me
Regards
HAMEED
RMAN> run
2> {
3> backup current controlfile;
4> }
Starting backup at 18-MAY-11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=143 device type=DISK
channel ORA_DISK_1: starting full datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
including current control file in backup set
channel ORA_DISK_1: starting piece 1 at 18-MAY-11
channel ORA_DISK_1: finished piece 1 at 18-MAY-11
piece handle=E:\RMAN\FULL_06MCLH66_1_1.BK tag=TAG20110518T180910 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 18-MAY-11
Starting Control File Autobackup at 18-MAY-11
piece handle=E:\RMAN\CFC-796596855-20110518-00 comment=NONE
Finished Control File Autobackup at 18-MAY-11Edited by: Hameed on May 18, 2011 5:55 AM

Showing RMAN configuration parameters 8.1.7

Hi group
What is the RMAN command in 8.1.7 to show RMAN configuration parameters, I know (SHOW ALL;) command is used in 9i version but it doesn't work on 8.1.7.
Thanks you very much

If I remember correctly, you could NOT configure and preserve parameters in 8.1.7 (so CONFIGURE and SHOW are not present in 8.1.7 RMAN).
You could create scripts with all the required commands and save them to the OS or to the Catalog -- preferably at the OS level so that they can be viewed and edited if the Catalog becomes unavailable.
Hemant K Chitale

RMAN Configuration Hisotry

Hello Folks,
Is it possible to get history of RMAN configuration changes which was made in past ? Either from target or from catalog database?
Thanks.

Hi again!
Sorry! NO it is really impossible. There is no table and no view in oracle that is able to show you an old rman configuration!
regards

Step by Step RMAN configuration for full hot backup daily

Dear experts,
i am new to oracle RMAN , i have gone through couple of RMAN guides for configuration ,
i have oracle e-business suite (R12.1.1) and database is ( 11.1.0.7) on red hat enterprise linux 5.3 . All of this is 64 bit.
i have a database about 175 gb which is as usual growing day by day as data entry is taking place.
Untill now we have a cold backup strategy in the midnight 3 am a script down the database and make abc.tar.gz file of 25 gb approx. . This process takes about 100 minutes. But now due to new sales system we want our database up 24/7 .
So we want to configure RMAN hot backup.
I want to take backup on disk.
daily full hot backup.
backupsets
currently database is in no-archivelog
plz help me to proceed with this .
Edited by: user13376823 on Feb 10, 2011 12:17 PM

user13376823 wrote:
Dear all,
i am using this script for my full hot backup ,
run
allocate channel c1 device type disk format '/opt/R12Backups/rman/%U';
allocate channel c2 device type disk format '/opt/R12Backups/rman/%U';
crosscheck backup;
BACKUP DATABASE FORMAT '/opt/R12Backups/rman/proddb_%u_%p_%c';
sql 'alter system switch logfile';
BACKUP ARCHIVELOG ALL DELETE INPUT FORMAT '/opt/R12Backups/rman/archlog%U';
DELETE NOPROMPT OBSOLETE REDUNDANCY =1 device type disk;
DELETE NOPROMPT EXPIRED BACKUPSET OF DATABASE device type disk ;
BACKUP AS COPY CURRENT CONTROLFILE FORMAT '/opt/R12Backups/rman/copy_of_cf_%U';
BACKUP SPFILE FORMAT '/opt/R12Backups/rman/spfile_%U';
release channel c1;
release channel c2;
1.please tell me that it is covering all aspects of a backup . Can i do complete recovery with this backup in case of disaster?
Define "all aspects".
2. i only get database and controlfile backup at my location. There is no backup of archivelogs , What happened with
that ?Without seeing the output that rman generated from running the above block, and without seeing all of the persistent rman settings, it is impossible to diagnose anything. I will say that your script looks overly complex.
Just to give you a point of comparison, here's my setup. First the persistent rman settings. Take note of anything that is NOT marked as "default";
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
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 BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 3;
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
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/ora00/app/oracle/product/10.2.0/db_1/dbs/snapcf_vlnxora1.f'; # defaultAnd here is my basic "full backup" script
[oracle@vmlnx01 bin]$ cat rman_full.scr
connect target /
show all;
run {
backup incremental level 0 database tag='bkup_vlnxora1_full';
backup archivelog all not backed up 2 times tag='bkup_vlnxora1_arch';
delete noprompt archivelog all backed up 2 times to device type disk;
list backup summary;
report obsolete;
quit

RMAN configuration on RAC

We are using RAC 9.2.0.6 and we have configured RMAN as follows:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 7;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\eemp_backup\EEMP\Control files\eEmp_CTL%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;#default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL 1 DEVICE TYPE DISK CONNECT 'SYS@Emp1';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS@Emp2';
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\eemp_backup\EEMP\Rman files\emp_files_%t_Bk_Set%s_Piece%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\EEMP_BACKUP\CONTROLFILE\SNAPCF_V9232
1.F';
RMAN configuration has no stored or default parameters ,'D:\eemp_backup\EEMP\Rman files\emp_files_%t_Bk_Set%s_Piece%p' while i found it in this destination when i fire list backup of database command : C:\ORACLE\APP\PRODUCT\9206\DATABASE\ATHA8I5F_1_1
and tried many times to solve this problem and put the backup set as where i want to put it on but i couldn't
PLEASE help,
Regards
and then i have taken backup as:
rman> backup database plus archivelog;
then when I check the destination of backup set i didn't see them on the configued one which is :

You should place the archivelogs either on the shared storage or the archive logs of all instances at all the nodes.
Actually the concept is, in case of recovery, RMAN should be able to look the archive logs from all the instances.
Regards

RMAN configuration in ORACLE RAC database

Hi there,
We are using RMAN backup strategy for taking backups from one node(eg.node1).Database is RAC database, version 9.2.3. and OS is Solaris 5.10.
this is the configuration which we use, as follows:
Connecting to Prod.Database using catalog database.
rman catalog=rman/rman@CATDB target=sys/oracle@PRODDB(node 2).
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 30;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanback/_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 5;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanback/CMWPROD_%s.bak';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK CONNECT 'SYS/oracle@PRODDB(node2)';
CONFIGURE MAXSETSIZE TO 7 G;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/9.2.3/dbs/snapcf_CMWPROD1.f';
As the above config shows RMAN is connecting to PROD DB (node 2). But we need to take backups (datafiles and as well as archive logs) from two nodes (i.e from node 1 and as well as node 2).
Is there any possibility for taking backups from two nodes?
Thanks,
Balu.

You will need to setup an NFS share such that both nodes can access each other's archived redo logs area. You also need to ensure your LOG_ARCHIVE_DEST_n parameter settings are properly set. Once setup correctly, either node will be able to run the backup and include each other's archived redo log files. Since this is RAC, the data files are shared by design and either node can already backup these files.
Multiple channels would allow 'simultaneous' backup of the archived redo logs.
I would highly recommend using a CFS (single shared file system where all nodes store their archived redo logs distinguished by thread) to store the archived redo logs, this reduces administration and configuration especially when you get ready to scale.
Hope this helps.

RMAN Configuration

What is the difference between these 2 configurations:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
RMAN will automatic remove the previous full backup if I set recovery window to 1 days, please correct me if I am wrong.
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
Don't know what it means?
FAN

user623471 wrote:
What is the difference between these 2 configurations:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
RMAN will automatic remove the previous full backup if I set recovery window to 1 days, please correct me if I am wrong.
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
Don't know what it means?
FANredundancy keep track of number of backups you made while recovery window keep backup for the number of days.
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
it will take one backup set not obsolete t until you dont take second backup completed succesfully.
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 1 DAYS;
it will arbitrarily keep backup till one day on second day the backup set will be treated as obsolete either you backed up second backup successfully or not on the second day.
Khurram

RMAN configuration files

If a database server has a catastrophic failure and RMAN was run previously from that same database server are there any configuration files that RMAN would need to rebuild the database from backups stored on tape or is everything that RMAN needs stored in the backup?
TIA,
Dave

If you have the latest controlfile, spfile, full database and archivelog backups taken by RMAN, then no need of any configuration files.
If you use a recovery catalog even the DBID will be stored. So its not need to be remembered. You can get it from the catalog tables. Here is how
select db_id
from db t1, dbinc t2
where t1.db_key=t2.db_key
and t2.db_name = '&1';

RMAN Configuration in DG Environment

Hi,
I have planned a backup strategy for my Oracle 10g Database using RMAN . Physical standby is used for DG . I wanted to know how can I create a physically seperate catalog server for the above purpose.
OS Version- Windows Server 2003
Regards
Vinita

Hello,
About Standby Database Registration
In a Data Guard environment, the primary and standby databases share the same DBID and database name. To be eligible for registration in the recovery catalog, each database in the Data Guard environment must have different DB_UNIQUE_NAME values. The DB_UNIQUE_NAME parameter for a database is set in its initialization parameter file.
If you use RMAN in a Data Guard environment, then you can use the REGISTER DATABASE command only for the primary database. You can use the following techniques to register a standby database in the recovery catalog:
When you connect to a standby database as TARGET, RMAN automatically registers the database in the recovery catalog.
When you run the CONFIGURE DB_UNIQUE_NAME command for a standby database that is not known to the recovery catalog, RMAN automatically registers this standby database as long as its primary database is registered.
http://download-uk.oracle.com/docs/cd/B28359_01/server.111/b28294/rman.htm#SBYDB04700
Regards,
Vineeth

What is RMAN configure file ?

Hi,
When you create recovery catalog, and start RMAN, where does RMAN get information to decide to get configure from catalog database instead of control file? what is the file name? Thanks.

hi
if you connect ( currently) with target database control file then ur backup information goes in control file instead of recovery catalog..
C:\>rman target=sys/oracle
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1134976990)
RMAN> exit
Recovery Manager complete.
C:\>rman target=sys/oracle nocatalog
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1134976990)
using target database controlfile instead of recovery catalog
RMAN> exit
Recovery Manager complete.
C:\>rman target=sys/oracle catalog=rman/cat
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1134976990)
connected to recovery catalog database
RMAN> exit
Recovery Manager complete.
C:\>rman catalog=rman/cat
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to recovery catalog databaseRMAN> exit
Recovery Manager complete.
C:\>rman target=sys/oracle catalog=rman/cat
Recovery Manager: Release 10.1.0.2.0 - Production
Copyright (c) 1995, 2004, Oracle. All rights reserved.
connected to target database: ORCL (DBID=1134976990)
connected to recovery catalog databasehope this helps
Taj
Message was edited by:
User 52

RMAN configuration (ASM Storage) 10g

hi
i am looking for a RMAN script which can
1. online backup the database to tape for ASM DISKGROUP
2. How can an incremental backup be taken for nologging objects (DWH)
3. can we configure 10g BCT for online tape backup (incremental)
4. how can we refresh the Production ASM database to staging (ASM) like cloning methods
thanks in advance

Hi Shakil,
hi
i am looking for a RMAN script which can
1. online backup the database to tape for ASM DISKGROUP
run {
allocate channel t1 type 'SBT_TAPE' parms="ENV=(BLKSIZE=1048576)";
send 'NB_ORA_POLICY=YOUR_POLICY, NB_ORA_SCHED=YOUR_SCHEDULE, NB_ORA_SERV=YOUR_SERVER';
backup
incremental level 0
skip inaccessible
tag online_backup_level0
filesperset 20
format 'full_online_%d_s%s_p%p_t%t' (database)
plus archivelog tag archived_logs
format 'arch_dia_%d_s%s_p%p_t%t'
include current controlfile tag control_file
format 'ct_file_%d_s%s_p%p_t%t';
release channel t1;
resync catalog;
EOF
2. How can an incremental backup be taken for nologging objects (DWH)
Incremental Backup Algorithm
Each data block in a datafile contains a system change number (SCN), which is the SCN at which the most recent change was made to the block. During an incremental backup, RMAN reads the SCN of each data block in the input file and compares it to the checkpoint SCN of the parent incremental backup. (If block change tracking is enabled, RMAN does not read the portions of the file known to have not changed since the parent incremental backup.) If the SCN in the input data block is greater than or equal to the checkpoint SCN of the parent, then RMAN copies the block.
One consequence of this mechanism is that RMAN applies all blocks containing changed data during recovery—even if the change is to an object created with the NOLOGGING option. Hence, making incremental backups is a safeguard against the loss of changes made by NOLOGGING operations.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmconc1.htm#i1011469
3. can we configure 10g BCT for online tape backup (incremental)
Yes you can.
4. how can we refresh the Production ASM database to staging (ASM) like cloning methods
Yes you can.
thanks in advance
Regards,
Rodrigo Mufalani

OSB / RMAN configuration for recovery area backup

Hi
I am having trouble performing a recovery area backup to tape.
Current config
Media server - attached tape library (OSB installed as media server, admin and client - Contains RMAN Repository) - configured as per guide. I can see the library tapes and have tested an OSB filesystem backup to tape which was fine, this was done from the OSB GUI.
Server 1 - databaseA, DatabaseB (OSB client installed) .
ZFS device - Shared storage where the FRA for DatabaseA belongs. All databaseA backups go here (currently databaseA is running in nonarchivelog mode).
I have set the tape details for databaseA, done a backup to the FRA but the backup recovery area to tape backup just hangs, no real errors and the job list through the obtool and list the job it always has state as 'retryable', I am wondering if I have missed some configuration somewhere? I am using Grid control for this.
I did have a couple of RMAN messages tried to resolve this as per some metalink notes to no avail, I am assuming this is causing the problem? Or am I missing something else?
specification does not match any archived log in the repository
specification does not match any datafile copy in the repository
Can anyone help?

Rest the times on the servers and now get the following errors:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 10/28/2011 16:22:55
ORA-19506: failed to create sequential file, name="16mq8bjj_1_2", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
shmcheck: obscheduled reports that job 'oracle/16.1' has terminated with status 'failed'.
The action at time of failure was 'wait_for_resource'.
The error message was 'unknown'.
exit;

RMAN Configure Channels vs Duplexed Backupsets

What is the difference between "duplexed backupsets" where I create multiple copies of RMAN backups and "Configuring Specific Channels" where I set channels to backup to two separate disks? I am using the duplexed backupset feature now to send 2 copies of the RMAN backups to 2 locations. I was testing the configuration of specific channels but did not see where I waa getting 2 full copies, one on each channel. For duplexed backupsets I configure:
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 2;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'disk1/backup_%d_%T_%U',   '/disk2/backup_%d_%T_%U' MAXPIECESIZE 4 G;;
For channels I set:
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT   '/disk1/backup_%d_%T_%U' MAXPIECESIZE 4 G;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT   '/disk2/backup_%d_%T_%U' MAXPIECESIZE 4 G;
but I cannot tell if I am getting 2 backups on the 2 channels or id RMAN is just making one backup and splitting it up on the 2 channels.
If I set the CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 2 on the channels, then I get 2 backups to disk1 and none to disk2.
What is the proper way to use channels to get 2 full copies of archivlog and database backups one copy on each channel?

Hello,
i have searched in metalink for a while and yes it is bug.
It is described in metalinknote #6316373.8:
Bug 6316373 - CROSSCHECK identifies some files as EXPIRED
It is really new (from 20-AUG-2008) .. i applied the patch and now it is working fine :-))
So everyone who has the same concept.. please apply this patch.
Regards
Stefan

RMAN CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET;

I configure this , How i can clear this ?
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET;

I assume you would have tried
CONFIGURE DEVICE TYPE DISK CLEAR;(as described in the documentation) before asking the question.
What about this does not work for you?

RMAN-configure compatible

Similar Messages

Maybe you are looking for