Rman compression of backupsets

Hi Gurus,
I am in the process of implementing backup startegy using rman.Does rman by default compress the backupsets ?if so what would be the compression ratio?if i compress with "backup as compressed backupset" it would be CPU instensive by what means?does this do addition compression on the already compressed backupset which rman does ?Please your Repps will be invaluable.
Regards

Hi there,
I generally dnt like to say that read docs but some times thats really easy to do.Mostly all of your questions are posted in this page.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup002.htm#BRBSC138
Rman doesnt by default does the compression.One can enable it if he wants.Yes it will be really intensive for the performane and as per the docs,it will be visible.I am not sure about the rate of it but its significant for the tape media.Again,oracle doesnt recommend combining both tape compression and rman compression both and recommends to go for tape/hardware compression in comparison to rman.
I didnt get this,
does this do addition compression on the already compressed backupset which rman does
What does what?If you are talking about rman compression than it has already done the compression or you are asking about rman plus o/s compression or vice versa?
Aman....

Similar Messages

RMAN compression in Oracle 10g R2 Standard

Hi,
We're currently using Oracle 10g R2 Standard Edition on our production databases. I'm revising our backup strategy and I am very interested in RMAN compressed backupsets.
However, can you use the standard compression feature of RMAN in Standard Edition? Or do you need to upgrade to Enterprise Edition? I couldn't find this information in the Oracle documentation.
Please shed some light on this issue. Many thanks in advance.

Hi,
I don't think compressing the backupsets is forbidden with a SE license : it is not listed as an unavailable feature. Check note 465465.1 and contact your sales representative if you have similar doubts.
Best regards
Phil

Creating Standby From RMAN Compressed backup taken on Primary ....

I am creating a Standby from RMAN Compressed backup taken on Primary.
On Primary, I have taken Compressed backup as follows:
RMAN> run
allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG format '/dboracle/orbit_pr_bkp/primary_%U';
backup current controlfile for standby format '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
oracle@apl06635orbvu1:/dboracle/orbit_pr_bkp>ls -ltr
total 51652
-rw-r----- 1 oracle dba 11972608 Jan 7 13:45 primary_0tm1h32n_1_1
-rw-r----- 1 oracle dba 15762432 Jan 7 13:45 primary_0sm1h32n_1_1
-rw-r----- 1 oracle dba 16785920 Jan 7 13:45 primary_0rm1h32n_1_1
-rw-r----- 1 oracle dba 1088000 Jan 7 13:45 primary_0um1h32v_1_1
-rw-r----- 1 oracle dba 32768 Jan 7 13:45 primary_12m1h33r_1_1
-rw-r----- 1 oracle dba 7143424 Jan 7 13:47 primary_cntl.bkp
On Standby, I restored the control file as below:
RMAN> restore standby controlfile from '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
Starting restore at 10-JAN-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output filename=/dboracle/orbit_dr/oradata/ORBIT_DR/controlfile/o1_mf_6lo6nwfr_.ctl
output filename=/dboracle/orbit_dr/flash_recovery_area/ORBIT_DR/controlfile/o1_mf_6lo6nwky_.ctl
Finished restore at 10-JAN-11
But, When I am trying to restore the datafiles, RMAN is throwing error:
RMAN> run {
allocate channel d1 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
allocate channel d2 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
restore database;
2> 3> 4> 5>
released channel: ORA_DISK_1
allocated channel: d1
channel d1: sid=155 devtype=DISK
allocated channel: d2
channel d2: sid=151 devtype=DISK
Starting restore at 10-JAN-11
released channel: d1
released channel: d2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 01/10/2011 05:38:56
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 3 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
What would be the correct RMAN command?
Regards, Anirban

After your RESTORE the (standby) controlfile, you must MOUNT the database instance with "ALTER DATABASE MOUNT".
You can also then query the controlfile with a "LIST BACKUP" or "LIST BACKUP SUMMARY" in RMAN to see if the deseired backups have been cataloged in the controlfile.
Don't specify the format for the ALLOCATE CHANNEL when you RESTORE DATABASE. In fact, you don't need to ALLOCATE CHANNEL at all when the device type is the default value of DISK if your are on 10gR2 or above.
Hemant K Chitale

OLTP compression and Backupset Compression

We are testing out a new server before we migrate our production systems.
For the data we are using OLTP compression.
I am now testing performance of rman backups, and finding they are very slow and CPU bound (on a single core).
I guess that this is because I have also specified to create compressed backupsets.
Of course for the table blocks I can understand this attempt at double compression will cause slowdown.
However for index data (which of course cannot be compressed using OLTP compression), compression will be very useful.
I have attempted to improve performance by increasing the parallelism of the backup, but I from testing this only increases
the channels writing the data, there is still only one core doing the compression.
Any idea how I can apply compression to index data, but not the already compressed table segments?
Or is it possible that something else is going on?

Hi Patrick,
You can also check my compression level test.
http://taliphakanozturken.wordpress.com/2012/04/07/comparing-of-rman-backup-compression-levels/
Thanks,
Talip Hakan Ozturk
http://taliphakanozturken.wordpress.com/

ORA-01858 error in RMAN during backup backupset format '/test/rman/%U'

Hello!
I am trying to perform bacup using command
RMAN> backup backupset completed after 'sysdate-1' format '/tmp/test/%U';
as described in:
asmcmd scripts
All backupsets are copied to /tmp/test/.
Everything is going fine except the last message from RMAN:
input backupset count=5342 stamp=660348635 creation_time=17-JUL-08
channel ORA_DISK_1: starting piece 1 at 18-JUL-08
piece handle=/tmp/test/6ujlo7mr_1_2 comment=NONE
channel ORA_DISK_1: finished piece 1 at 18-JUL-08
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
input backupset count=5343 stamp=660348722 creation_time=17-JUL-08
channel ORA_DISK_1: starting piece 1 at 18-JUL-08
piece handle=/tmp/test/6vjlo7pi_1_2 comment=NONE
channel ORA_DISK_1: finished piece 1 at 18-JUL-08
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
input backupset count=5344 stamp=660348810 creation_time=17-JUL-08
channel ORA_DISK_1: starting piece 1 at 18-JUL-08
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 07/18/2008 10:59:48
ORA-01858: a non-numeric character was found where a numeric was expected
I suspect that rman is performing, at the end of backup, some internal work (store something in control file based catalog or so) and catches ORA-01858.
The destination catalog is local catalog (not nfs mounted remote dir).
RMAN is spawned from the same node the Oracle Database is running on.
I tested it on two servers.
Error occurs on both of them:
version 10g (ia-32) - flash recovery area on filesystem
and version 11g (Aix) - flash on ASM
RMAN-oracle10> show all ;
using target database controlfile instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
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 DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/opt/oracle/10gSE/dbs/snap_dbname.dbf'; # default
RMAN-oracle11> show all ;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name O2DB 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 COMPRESSED BACKUPSET;
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
CONFIGURE COMPRESSION ALGORITHM 'BZIP2'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.1.0/dbname_1/dbs/snapcf_dbname.f';
How to diagnose the problem?
How check what RMAN is exactly doing when error occurs?
Or maybe there is better way to achieve this:
I want to move backupset from asm realm to remote server without storing them on local, non asm disk.
Any suggestions kindly welcome!
Thanx!

Solution:
NLS_DATE_FORMAT mus be set mannualy;
export NLS_DATE_FORMAT='YYYY_MM_DD'
solved the problem..
https://metalink.oracle.com/metalink/plsql/f?p=130:15:12788270042070262572::::p15_database_id,p15_docid,p15_show_header,p15_show_help,p15_black_frame,p15_font:BUG,6198368,1,1,1,helvetica
Metalinking before posting is the rule of thumb : )

RMan backup stores backupsets into $ORACLE_HOME

Rman backups are currently storing backupsets into the $ORACLE_Home
WHy would that be.???????
how can i check the default dsik device????

ok herewith is the out as requested.
oracle $ rman
Recovery Manager: Release 11.2.0.2.0 - Production on Thu Mar 10 11:55:17 2011
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN> connect target
connected to target database: MAC (DBID=710471977)
RMAN> connect catalog rman/sun011gR2@sun0
connected to recovery catalog database
RMAN> show all
2> ;
RMAN configuration parameters for database with db_unique_name MAC_D are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
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 8 BACKUP TYPE TO COMPRESSED BACKUPSET;
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
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 '/u1/oracle/product/11.2.0/db_1/dbs/snapcf_MAC.f'; # default
RMAN>
{Code}
Did not see any changes...or might have overlooked.

How does one enable rman compression in brbackup ?

brtools latest version
aix 5.3, oracle 10.2
i changed
#rman_compress = no | yes
to
rman_compress = yes
backup_dev_type = disk
disk_copy_cmd = rman
rman_compress = yes
can someone, anyone tell me what to change in initSID.sap and or the command line to make this work ?
-pete "if ones life depended on this stuff, there would be no one alive"

Hi Pete,
Parameter should be <b>compress = yes</b>
You can change init<SID>.sap using vi.
Regards
Juan

Can I use rman 64 bit backupsets to restore/recover on a 32bit platform?

Hi,
rman is creating daily backupsets on my 64bit prod database.
In case of failure, may I use those backupsets to restore on a 32 bit database?
Cheers,
phil

First of all you should specify the specific DB version you are working with, since there are certain constraints you should be aware with the 64/32 interoperability. You may take a look at this thread --> Re: can i do dataguard between oracle 64 bit to oracle 32 bit? where the 64/32 bit problem is addressed with data guard. I know you are concerned about the rman issue, not data guard, but there you will find some references on the 64/32 interoperability on both, oracle documents and metalink notes.
~ Madrid

RMAN: Using older backupset but all archivelogs

I was reading on asktom.com about his method of backing up a database:
Take full hot backups via RMAN Mon-Wed-Friday, but backup the archive logs nightly.
One of the benefits was that if pre-Wed backup a block becomes corrupt and backed up, and you don't notice it until Thursday, then you could use the Monday night full backup and all the the archive logs to roll the database forward to current. Hopefully, the block wouldn't be written in a corrupt manner the second time around.
So, how do you instruct RMAN to use a backup older than the most current, but to use all archive logs thru current?
Thanks,
Chuck

And something else related that I haven't found the answer for:
If you are using the control file to store RMAN's restore/recovery information, and you run the command
RMAN> BACKUP DATABASE FULL KEEP FOREVER NOLOGS;
What happens to this status if the situation arises where you lose your control file and have to resync RMAN with a new control file? Is the KEEP FOREVER status attached to the backupset, and RMAN registers this when the resync occurs?
Thanks,
Chuck

Rman creating many backupsets

Hi all,
Rman is creating an awful lot of backupsets for one of our databases during the regular d0/c1 backup schedule.
It's a very simple script we're using, we're not using anything like maxsetsize/maxpiecesize/maxopenfiles/filesperset etc.
So it's pretty basic, see the output of show all below:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 100 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/afs1/MOT/rman/ctl/%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/afs6/Staging/oracle/%d_%s_%t_%p';
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' FORMAT '%d_%s_%t_%p' PARMS 'ENV=(NSR_SERVER=pwxs51,NSR_GROUP=PROD)';
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 '/afs5/PROD/db/tech_st/10.2.0/dbs/snapcf_PROD.f'; # default
And here's our incremental level 1 script (same issue with d0 btw).
configure retention policy to recovery window of 100 days;
configure controlfile autobackup on;
configure default device type to sbt;
configure device type sbt parallelism 1;
configure channel device type sbt format '%d_%s_%t_%p' PARMS 'ENV=(NSR_SERVER=pwxs51,NSR_GROUP=PROD)';
RUN
set command id to 'RMAN onl c1 to nsr';
backup incremental level 1 database;
backup archivelog all not backed up 1 times;
delete noprompt archivelog until time 'sysdate-1/24' backed up 1 times to device type sbt;
There's a total of 91 datafiles, yet somehow the backup is creating 41 backupsets.
The odd thing is that we have a development clone of this database (on different node), which is being backupped with pretty much the same script/configuration to the same tapeserver and this backup is only creating 2 backupsets.
It's a 10.2.0.3 database on Solaris 9.
It's not really a problem as far as I'm concerned, I just would like to know what is causing rman to create this many backupsets.
Btw the disk parallelism 4 is configured for a weekly disk backup, which is also showing this many backupsets.
It's not an extremely big database, about 200GB.
Does anyone know what could be causing this?
Thanks in advance,
BR,
Lauris

Sorry, there's no limit to the files per set configured either.
I hit the maximum characters for a post when trying to post the output.
So for the PROD db I've had to reduce it to last nights backup only.
The 2 entries from March 5th are from this morning's archive spooling job.
P.START_TIME||''||P.HANDLE||''||COUNT(D.FILE#)
+04-MAR-10 c-4252449814-20100304-00 1+
+04-MAR-10 /afs1/MOT/rman/ctl/c-4252449814-20100304-01 1+
+04-MAR-10 c-4252449814-20100304-02 1+
+04-MAR-10 /afs1/MOT/rman/ctl/c-4252449814-20100304-03 1+
+04-MAR-10 PROD_22453_712782223_1 10+
+04-MAR-10 PROD_22454_712782408_1 10+
+04-MAR-10 PROD_22455_712782423_1 1+
+04-MAR-10 PROD_22456_712782427_1 1+
+04-MAR-10 PROD_22457_712782442_1 1+
+04-MAR-10 PROD_22458_712782487_1 1+
+04-MAR-10 PROD_22459_712782532_1 1+
+04-MAR-10 PROD_22460_712782547_1 1+
+04-MAR-10 PROD_22461_712782603_1 1+
+04-MAR-10 PROD_22462_712782648_1 1+
+04-MAR-10 PROD_22463_712782703_1 1+
+04-MAR-10 PROD_22464_712782758_1 1+
+04-MAR-10 PROD_22465_712782804_1 1+
+04-MAR-10 PROD_22466_712782889_1 1+
+04-MAR-10 PROD_22467_712782964_1 1+
+04-MAR-10 PROD_22468_712783019_1 1+
+04-MAR-10 PROD_22469_712783094_1 1+
+04-MAR-10 PROD_22470_712783160_1 1+
+04-MAR-10 PROD_22471_712783215_1 1+
+04-MAR-10 PROD_22472_712783260_1 1+
+04-MAR-10 PROD_22473_712783315_1 1+
+04-MAR-10 PROD_22474_712783381_1 1+
+04-MAR-10 PROD_22475_712783416_1 1+
+04-MAR-10 PROD_22476_712783691_1 1+
+04-MAR-10 PROD_22477_712783716_1 1+
+04-MAR-10 PROD_22478_712783742_1 4+
+04-MAR-10 PROD_22479_712783745_1 3+
+04-MAR-10 PROD_22480_712783752_1 3+
+04-MAR-10 PROD_22481_712783937_1 5+
+04-MAR-10 PROD_22482_712784123_1 5+
+04-MAR-10 PROD_22483_712784308_1 2+
+04-MAR-10 PROD_22484_712784311_1 2+
+04-MAR-10 PROD_22485_712784327_1 2+
+04-MAR-10 PROD_22486_712784352_1 6+
+04-MAR-10 PROD_22487_712784547_1 2+
+04-MAR-10 PROD_22488_712784554_1 2+
+04-MAR-10 PROD_22489_712784570_1 3+
+04-MAR-10 PROD_22490_712784577_1 2+
+04-MAR-10 PROD_22491_712784642_1 2+
+04-MAR-10 PROD_22492_712784649_1 5+
+04-MAR-10 c-4252449814-20100304-04 1+
+04-MAR-10 /afs1/MOT/rman/ctl/c-4252449814-20100304-05 1+
+05-MAR-10 c-4252449814-20100305-00 1+
+05-MAR-10 /afs1/MOT/rman/ctl/c-4252449814-20100305-01 1+
Redo:
P.START_TIME||''||P.HANDLE||''||COUNT(R.SEQUENCE#)
+03-MAR-10 PROD_22393_712647079_1 56+
+03-MAR-10 PROD_22397_712690268_1 54+
+03-MAR-10 PROD_22441_712698364_1 9+
+04-MAR-10 PROD_22445_712733473_1 55+
+04-MAR-10 PROD_22449_712776691_1 55+
+04-MAR-10 PROD_22493_712784679_1 9+
+05-MAR-10 PROD_22497_712819874_1 54+
And for the development copy db (named DEV0) backups from past 3 days:
P.START_TIME||''||P.HANDLE||''||COUNT(D.FILE#)
+03-MAR-10 DEV0_2103_712630857_1 38+
+03-MAR-10 DEV0_2104_712633523_1 38+
+03-MAR-10 c-4252449814-20100303-00 1+
+03-MAR-10 /afs4/DEV0/db/tech_st/10.2.0/dbs/c-4252449814-20100303-01 1+
+03-MAR-10 DEV0_2110_712713531_1 38+
+04-MAR-10 DEV0_2111_712716417_1 38+
+04-MAR-10 c-4252449814-20100304-00 1+
+04-MAR-10 /afs4/DEV0/db/tech_st/10.2.0/dbs/c-4252449814-20100304-01 1+
+04-MAR-10 DEV0_2117_712799889_1 38+
+05-MAR-10 DEV0_2118_712802825_1 38+
+05-MAR-10 c-4252449814-20100305-00 1+
+05-MAR-10 /afs4/DEV0/db/tech_st/10.2.0/dbs/c-4252449814-20100305-01 1+
+32 rows selected.+
Redo:
P.START_TIME||''||P.HANDLE||''||COUNT(R.SEQUENCE#)
+26-FEB-10 DEV0_2070_711942703_1 1+
+26-FEB-10 DEV0_2074_712022211_1 20+
+27-FEB-10 DEV0_2077_712097440_1 1+
+27-FEB-10 DEV0_2081_712108557_1 1+
+28-FEB-10 DEV0_2084_712190509_1 4+
+28-FEB-10 DEV0_2088_712194956_1 1+
+01-MAR-10 DEV0_2091_712459919_1 1+
+01-MAR-10 DEV0_2095_712540585_1 2+
+02-MAR-10 DEV0_2098_712546862_1 1+
+02-MAR-10 DEV0_2102_712626975_1 2+
+03-MAR-10 DEV0_2105_712635762_1 1+
+03-MAR-10 DEV0_2109_712713420_1 2+
+04-MAR-10 DEV0_2112_712719205_1 1+
+04-MAR-10 DEV0_2116_712799797_1 2+
+05-MAR-10 DEV0_2119_712805603_1 1+
+15 rows selected.+
So for the PROD db the amount of datafiles in a backupset is not always the same, sometimes it's 6 but its 1 most of the times.
Br,
Lauris

Cannot set RMAN compression algorithm

hi guys...
I am using the oracle database 11g on OEL5 with compatible parameter set to 11.2.0.0.0
when i use the following command in the RMAN it gives an error as shown below.
RMAN> configure compression algorithm 'bzip';
using target database control file instead of recovery catalog
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 10/16/2010 15:24:42
RMAN-06806: compression algorithm 'bzip' of release DEFAULT not found
help please...

RMAN gives a error and let me show the output of the V$RMAn_COMPRESSION_ALGORITHM view as well
RMAN> configure compression algorithm 'bzip2';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of configure command at 10/16/2010 15:29:30
RMAN-06806: compression algorithm 'bzip2' of release DEFAULT not found
SQL> select * from V$RMAN_COMPRESSION_ALGORITHM;
ALGORITHM_NAME
INITIAL_RELEASE TERMINAL_RELEASE
ALGORITHM_DESCRIPTION
ALGORITHM_COMPATIB IS_ REQ
BASIC
10.0.0.0.0
good compression ratio
9.2.0.0.0 YES NO
ALGORITHM_NAME
INITIAL_RELEASE TERMINAL_RELEASE
ALGORITHM_DESCRIPTION
ALGORITHM_COMPATIB IS_ REQ
LOW
11.2.0.0.0
maximum possible compression speed
11.2.0.0.0 YES YES
ALGORITHM_NAME
INITIAL_RELEASE TERMINAL_RELEASE
ALGORITHM_DESCRIPTION
ALGORITHM_COMPATIB IS_ REQ
MEDIUM
11.2.0.0.0
balance between speed and compression ratio
11.0.0.0.0 YES YES
ALGORITHM_NAME
INITIAL_RELEASE TERMINAL_RELEASE
ALGORITHM_DESCRIPTION
ALGORITHM_COMPATIB IS_ REQ
HIGH
11.2.0.0.0
maximum possible compression ratio
11.2.0.0.0 YES YES

RMAN - Cataloging a backupset

Hi all,
On 9i how i can include a backupset on RMAN catalog ?
On 10g I know that using this command bellow run ok.
catalog start with 'D:\backup\' noprompt;
can anybody help me?
Wander(Brazil)

You cannot catalog a backup set with Oracle 9i according to the documentation.

Can RMAN use foreign backupset?

Hello, i'm new with rman and i don't know if there is a possibility to do something like that:
i want to recover some tables i saved in a compressed backup set from another database.
Is RMAN able to open a backup file coming from a database that is not the database target?
Thanks for your help

No, RMAN isn't able to do that.
This would require ordinary export, or using the transportable_tablespace feature of export.
Sybrand Bakker
Senior Oracle DBA

RMAN after first backupset failure

I try to backup a database with RMAN 8.0 and after first backupset my backup stopped. I supposed it's a problem in recovery catalog. Any suggestion ? Thanks.

But RMAN doesn't return an error or something elseThen what else you are expecting?? Can you post the exact output so that we can have a better look.
Daljit Singh

10G RMAN Compression

Guru,
What are the default features available along with 10g R2 EnterPrise Edition , Especially for RMAN Backup ?
What are the features required for licensing in 10g R2 EE version .
Regsards,
Raju

PRaju wrote:
Guru,
What are the default features available along with 10g R2 EnterPrise Edition , Especially for RMAN Backup ?
What are the features required for licensing in 10g R2 EE version .
Regsards,
Raju
Your questions are answered in the documentation -- http://www.oracle.com/pls/db102/homepage
RMAN: Oracle Database Search Results: RMAN
License: http://www.oracle.com/pls/db102/ranked?word=License&partno=b14199
There are more features available in the later versions -- Database 12c Release 1 and Database 11g Release 2
Thanks,
Hussein

Rman compression of backupsets

Similar Messages

Maybe you are looking for