Rman backup Compress question

Oracle ver 10.2.0.1 -- 24/7
250G database. I ran the script
run {
allocate channel c1 type disk format '/hotbackup/%d/db_%d_t%t_s%s_p%p%c';
set limit channel c1 kbytes 2024800;
sql "alter system archive log current";
backup as compressed backupset
incremental level 0
filesperset=20 (database include current controlfile);
release channel c1;
# Backup all archive log files
allocate channel t1 type disk format '/hotbackup/%d/al_%d_%s_%p%c';
backup as compressed backupset filesperset=20 (archivelog all delete input);
release channel t1;
delete noprompt backup completed before 'sysdate-1';
And the backup file is still around 220G. Is there another way to compress? Anybody have an idea how to make the backup smaller?
Thank You

How many CPU's does your server have?
And why don't you let RMAN choose the default's regarding the files per set, the backup set piece size, etc. Whenever you run a compressed backup, RMAN would normally use at approx.12% of CPU per channel. A 45hr backup time is clearly unacceptable that too when it is a 24/7 database but as your are using a single channel, which might be the culprit. I would suggest to use about 4 channels (depending on your CPU load) and do not put any restrictions on the files per set and backup set piece size.
We do a compressed backup to disk of a 230G database on a 8 proc server with 4 channels allocated and the backup normally completes in about 1.45 hours and the FULL backup size produced is around 30G ( level 0 is a FULL backup).

Similar Messages

  • RMAN backup compression and tape hardware compression

    Hello,
    Should tape backup compression be ON and RMAN compression OFF? What is the correct Oracle answer?
    Common knowledge says that if both hardware and software compression were allowed to be enabled at the same time the resulting file in some cases may actually be bigger than the original file. Hardware data compression is done by specialized chips and faster than software compression and increases the tape performance.
    I was reading somewhere some time ago that tape hardware will actually not attempt to compress data if the the data being processed cannot be compressed any further. But even if this is a hoax, wouldn't rman compression, at the cost of CPU, save I/O bandwidth?
    Thanks.
    Edited by: MaC on Dec 19, 2010 4:00 PM

    MaC wrote:
    I just located Oracle document ID 1018242.1, which outlines:
    Use either hardware or software compression, but NOT both. Using both will actually increase the size of the resulting file. The rule of thumb is: compression + compression = no_compression.
    Sounds kind a logic.I was actually going to post the same sentence but you did find it on your own :) . Another thing which is worth to mention that from 11.2, the RMAN backup compression is licensed with 4 options, High, Medium and Low . These all three options requires you to have Advanced Compression License to buy. There is another 4th option, Default which is free from license and the compression ratio of that lies in between of Medium and Low.
    HTH
    Aman....

  • Rman backup optimization question

    Hi,
    I have come across a RAM related question and would like to understand the answer:
    The RMAN configuration has backup optimization set to ON. Which of the following commands will this setting affect?
    a) Backup Archivelog with ALL or LIKE options, b) Backup Backupset ALL, c) Backup Tablespace, d) Backup Database
    I believe all of the above are affected by backup optimization, however, only a, b and d seems correct, not c. I wonder why tablespace is not affected - it does not say read only, etc.?
    Any ideas? Thanks.

    Thanks for the quick response!
    Meanwhile I did a few tests below, and yes, tablespace does obviously not use backup optimization. But why? Doesn't the same like backup database apply? Isn't using the same retention policy?
    RMAN> backup database;
    skipping datafile 5; already backed up 2 time(s)
    RMAN> backup archivelog ALL;
    skipping archived log file /u02/fra/ORCL/ar...; already backed up 1 time(s)
    RMAN> backup tablespace example;
    input datafile file number=00005
    piece handle=/u02/fra/ORCL/backupset....
    RMAN> backup tablespace example;
    input datafile file number=00005
    piece handle=/u02/fra/ORCL/backupset....

  • RMAN backup  tag question

    I am little confused even after I read the RMAN doc. If I have a full level 0 backup tag "mybk$level_0" database, then my level 1 incremental backup tag has to be the same - "mybk$level_1" or "mybk$level_0".
    I just run the incremental backup through the whole weekend and noticed the each run would generated two identical "spfile, controlefile" backup, one before the archivelog backup, one after it. Why?

    The tag name can be the same as what you set. Tag names can be of different names and different formats, does not need to be a specific name. You can replace mybk with myarchive if you think that is more meaningful. You can also attach date and time variable with the tags to make them more meaning full.
    It doesn't have to be this way,
    { backup incremental level 1 cumulative device type disk tag 'mybk%LEVEL_1' database;
    recover copy of database;
    backup device type disk tag 'mrarchive' archivelog all not backed up; }
    If you are calling the rman backup from shell script you can attach the dates to tags as below.
    export TDATE=`date +%a%m%d%y`
    tag="Archive_${TDATE}"
    or
    tag "Archive_${TDATE}"
    Below note if from one of the online resources available:
    Tags for Backups and Image CopiesYou can assign a user-specified character string called a tag to backup sets and image copies (either copies created by RMAN or copies created by an operating system utility). A tag is a case-insensitive symbolic name for a backup set or file copy such as weekly_backup. You can specify the tag rather than the filename when executing the RESTORE or CHANGE command. The maximum length of a tag is 30 characters.
    If you do not specify a tag name, then by default RMAN creates a tag for backups and copies (except for control file autobackups) in the format TAGYYYYMMDDTHHMMSS, where YYYY is the year, MM is the month, DD is the day, HH is the hour (in 24-hour format), MM is the minutes, and SS is the seconds. For example, a backup of datafile 1 may receive the tag TAG20020208T133437. The date and time refer to when RMAN started the backup. If multiple backup sets are created by one BACKUP command, then each backup piece is assigned the same default tag.
    When applied to a backup set, a tag applies to a specific copy of the backup set. If you do not duplex a backup set, that is, make multiple identical copies of it, then a one-to-one correspondence exists between the tag and the backup set. For example, BACKUP COPIES 1 DATAFILE 7 TAG foo creates one backup set with tag foo. However, you can back up this backup set and give this new copy of the backup set the tag bar. So, the backup set has two identical copies: one tagged foo and the other tagged bar.
    Tags do not need to be unique, so multiple backup sets or image copies can have the same tag name, for example, weekly_backup. When a tag is not unique, then with respect to a given datafile, the tag refers to the most current suitable file. By default, RMAN selects the most recent backups to restore unless qualified by a tag or a SET UNTIL command. The most current suitable backup containing the specified file may not be the most recent backup, as can occur in point-in-time recovery.
    For example, if datafile copies are created each Monday evening and are always tagged mondaypmcopy, then the tag refers to the most recent copy (assuming that no SET UNTIL command is issued before restore or recovery). Thus, if complete recovery is desired, this command switches datafile 3 to the most recent Monday evening copy:
    SWITCH DATAFILE 3 TO DATAFILECOPY TAG mondaypmcopy;
    Tags can indicate the intended purpose or usage of different classes of backups or file copies. For example, datafile copies that are suitable for use in a SWITCH can be tagged differently from file copies that should be used only for RESTORE.
    Note:
    If you specify a tag when specifying input files to a RESTORE or SWITCH command, then RMAN considers only backup sets with a matching tag when choosing which backup to use

  • RMAN Backup/Recover question

    Should I be able to back up a db using RMAN in a 10.1.0.2 installation and recover using RMAN in a 10.1.0.3 installation (using same OS, etc.)?

    user13419193 wrote:
    Hii..
    Thanks for reply and I got yr point.
    But Sorry for again questioning, here i want database recovery on same server.
    Than what to do?
    Do i have to create database thriough dbca on same server??
    RegardsWhere are your backup files now? Confirm you still have them and they didn't get dropped as part of your deleting/dropping the database.
    If, as you say, you deleted the entire database, there really is no concept of 'same server'. You want to restore/recover the database onto a server which does not currently have any copy/version of that particular database. Whether or not there ever WAS one on that box is pretty much meaningless, except for the fact there may be some bits and pieces we can use. But the basic technique is the same.
    You haven't state your OS, which is important. If its Windows, you'll need to use oradim to recreate the service. Once that is done, rman can connect to an 'idle' instance and proceed from there.
    Once rman connects to an idle instance, you restore the control file from backup, then mount the database (open the control file) then restore and recover the db. rman will use information in the resotred control file to locate the backupsets and process the rest of the operation. there are details that need to be attended to but that's the overall outline.
    Edited by: EdStevens on Oct 7, 2011 8:37 AM

  • RMAN Backup Plan Question

    Hello -
    If I'm backing up specific datafiles (say 3 datafiles in one RMAN script) and I have 4 of these scripts - so a total of 12 files being backup up, should I have a separate script that just backs up all of the archived log files? Or should I include a Backup Archivelog all command in each specific script?

    backup each datafile once according to your backup shedule there is no advantage of backup each data file foure times it conversly decrade or slow down your backup working. there is no need to include archive logs in your scripts. I think you should create seprate sript for archived logs.

  • Compressing rman backup

    Hi all,
    My database is growing up adn becomes very big, i have a problem of the backup because when i take full backup it gives error of disk space. I want to reduce the size of my backup and i know the existance of compressing rman backup.
    My question is how to set rman compressed backup and is compress option working for incremental backup or not. I want this because i'm taking full backup once a week ansd incremental backup every monday till saturday.
    Thanks for the help
    Ratsarevo.

    Hi,
    Thanks all for your replies, No i'm reassured for my backup type.
    Here is my backup configuration:
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/data1/rman_backup/%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 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 CHANNEL 1 DEVICE TYPE DISK FORMAT '/data1/rman_backup/%d_%T_%U';
    CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/data2/rman_backup/%d_%T_%U';
    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 '/data1/rman_backup/snapcf_abdb.f';
    Is it good for compressed backup ?
    Thanks

  • Related to Unused compression in RMAN backup for 10.2.0.4 database

    Hi
    I recently read through one of the document related to Unused compression in RMAN backup for 10.2.0.4 database. According to this
    Unused Block Compression is done, if all of the following conditions apply:
    + The COMPATIBLE initialization parameter is set to 10.2
    + There are currently no guaranteed restore points defined for the database
    + The datafile is locally managed
    + The datafile is being backed up to a backup set as part of a full backup or a level 0 incremental backup
    + The backup set is being created on disk.
    I have two queries
    1) What is meant by "uaranteed restore points defined for the database"
    2) If backup is being directly taken to tape, this feature would not be used
    Rgds
    Harvinder

    1. Normal and Garanteed Restore Points
    2. No

  • How to make an encrypted compressed RMAN backup and recovery

    Hallo!I am trying to make an RMAN backup that is compressed (definitely use compressed backup set in OEM).
    But my emphasis is to make the backup encrypted with a key (hoping to use Public Key Infrastructure )such that the database data can be sent via the network and the recepient can use a decryption key to decrypt the data.
    The recepient must also use a password to access the encrypted file for decryption.
    Is it possible to do this?If so please give the steps.
    Thanks.

    You can encrypt the backupset with RMAN Encrypted Backups, however Oracle Advanced Security Option (additional cost) is required.

  • How to find the compression algorithm  used on a RMAN Backup

    I have list of backups taken using different compression alogrithms. I need to query and find out the compression algorithm used on existing RMAN Backup. I tried querying the view V$RMAN_BACKUP_JOB_DETAILS.
    For Example I ran script below for backing up database with compressed backupsets;
    On RMAN
    connect target /
    connect catalog rman/sqw1298@rcat
    set COMPRESSION ALGORITHM 'HIGH'
    backup filesperset 1 format '<%d_%s:%t:%p:%f>.df' incremental level 0 database;Edited by: Sivaprasad S on Sep 1, 2012 12:32 AM
    Edited by: Sivaprasad S on Sep 1, 2012 12:36 AM

    I used the query below to get the RMAN backup details, here I am missing detail of compression algorithm
    SELECT SESSION_KEY, INPUT_TYPE, STATUS,
    TO_CHAR(START_TIME,'mm/dd/yy hh24:mi') start_time,
    TO_CHAR(END_TIME,'mm/dd/yy hh24:mi') end_time,
    ELAPSED_SECONDS/3600 hrs,
    COMPRESSION_RATIO ,
    INPUT_BYTES_DISPLAY, OUTPUT_BYTES_DISPLAY, TIME_TAKEN_DISPLAY
    FROM V$RMAN_BACKUP_JOB_DETAILS
    ORDER BY SESSION_KEY;Output
    SESSION_KEY     INPUT_TYPE     STATUS     START_TIME     END_TIME     HRS     COMPRESSION_RATIO     INPUT_BYTE     OUTPUT_BYTES_DI     TIME_TAKEN_DISP
    417     DB INCR     COMPLETED     8/23/2012 16:01     8/23/2012 16:33     0.529444444     1.06917899     244.67G     228.84G     0:31:46
    423     DB INCR     COMPLETED     8/23/2012 16:43     8/23/2012 17:14     0.510277778     1.0692043     244.59G     228.76G     0:30:37
    435     DB INCR     COMPLETED     8/24/2012 11:39     8/24/2012 12:13     0.571666667     1.06899247     244.64G     228.85G     0:34:18
    441     DB INCR     COMPLETED     8/24/2012 13:52     8/24/2012 14:23     0.511666667     1.0690053     244.60G     228.81G     0:30:42
    447     DB INCR     COMPLETED     8/24/2012 16:30     8/24/2012 16:58     0.467222222     2609.07178     244.60G     96.00M     0:28:02
    457     DB INCR     COMPLETED     8/25/2012 12:30     8/25/2012 13:01     0.527222222     1.06896188     244.68G     228.90G     0:31:38
    467     DB INCR     COMPLETED     8/26/2012 16:30     8/26/2012 16:56     0.4325     739.556573     244.65G     338.75M     0:25:57On the output I need to have the compression algorithm used for each backup.
    Hope this is crystal clear now.

  • RMAN backup and TSM question

    We have rman backup file name contains the datetime so it is unique and easy to tell. But TSM keeps every file 4 versions, so the backup file (always 1 version because of unique name) will stay on tape forever. I have no idea about TSM, according to your experience, what is the normal solution here?

    Dedicated forum for {forum:id=74}.
    But quickly, in general, "DBA" and "TSM/Storage manager" need to agree on media manager use and setup the system accordingly.
    Edited by: orafad on May 19, 2011 3:00 PM

  • RMAN backup and restore for Disaster Recovery

    Hi Guys,
    I am very new to Oracle and have a question about RMAN backup and restore feature. I am simulating a disaster recovery scenario by having two VMs running oracle 11g, say hosta and hostb, hosta is sort of production db and the other a disaster recovery db (one that will be made primary when disaster occurs). My goal is to backup production db using RMAN and restore it on the other machine. For some reason when I restore the db on hostb, the command restores the previous backup but not the most recent one e.g. I took a backup yesterday (09/20) and applied it to the hostb that worked fine, but when I try to apply a fresh backup from today (09/21) it always picks up the old backup. Here's a dump of the screen:
    Starting restore at 21-SEP-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /oracle/app/dev/oradata/forums/s
    ystem01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /oracle/app/dev/oradata/forums/s
    ysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /oracle/app/dev/oradata/forums/u
    ndotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /oracle/app/dev/oradata/forums/u
    sers01.dbf
    channel ORA_DISK_1: reading from backup piece /oracle/app/dev/flash_recovery_are
    a/FORUMS/backupset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp
    channel ORA_DISK_1: piece handle=/oracle/app/dev/flash_recovery_area/FORUMS/back
    upset/o1_mf_nnnd0_TAG20110920T040950_77jx3zk7_.bkp tag=TAG20110920T040950
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
    Finished restore at 21-SEP-11
    Notice that it reads the backup piece from this location /oracle/app/dev/flash_recovery_are
    a/FORUMS/backupset/
    whereas my latest backups are stored at a different location.
    I am executing following steps at the RMAN prompt on hosta and hostb:
    hosta (production site)
    backup as compressed backupset database plus archivelog
    backup current controlfile format'/oracle/oracle_bkup/ctl_%U'
    backup spfile
    hostb (Disaster site)
    set dbid=13732232063
    startup force nomount
    restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/2011_09_21/o1_mf_nnsnf_TAG20110921T114945_77ndg9ys_.bkp'
    shutdown immediate
    /* create a init<db_name>.ora file with SPFILE= /oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora */
    startup force pfile='/export/home/dev/restore_db/initforums.ora' nomount
    restore controlfile from '/export/home/dev/restore_db/backupset/2011_09_21/ctl_1hmn3mic_1_1'
    /* restart rman here */
    quit
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset/2011_09_21' noprompt;
    /* call the next two commands on run */
    restore database;
    recover database;
    alter database open resetlogs
    quit
    Any help will be greatly appreciated.
    Thanks,
    Rajesh

    Thanks guys, I really appreciate all your help here. I redid everything all over again to get all the information you guys wanted. Since I noticed that more eyes are looking into this I am going to reiterate my steps one more time followed by specific answers to questions. My first backup on Host B is located under ..../restore_db/backupset whereas the subsequent one is under .../restore_db/backupset/backupset2.
    I take backup on Host A using:
    rman target /
    backup as compressed backupset database plus archivelog;
    backup spfile;
    quit;
    I restore the backup on Host B using:
    set dbid=13732232063;
    startup force nomount;
    restore spfile to '/oracle/app/dev/product/11.2.0/dbhome_1/dbs/spfileforums.ora' from '/export/home/dev/restore_db/backupset/o1_mf_nnsnf_TAG20110928T171830_787gbpxh_.bkp'
    shutdown immediate;
    startup force nomount;
    restore controlfile from '/export/home/dev/restore_db/backupset/o1_mf_ncsnf_TAG20110928T171638_787gbkxn_.bkp'
    quit;
    /* restart rman here */
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset' noprompt;
    restore database;
    recover database;
    alter database open resetlogs;
    quit;
    I take another backup on Host A using (notice no spfile backup this time):
    backup as compressed backupset database plus archivelog;
    quit;
    I restore the database on Host B using:
    alter database mount;
    catalog start with '/export/home/dev/restore_db/backupset/backupset2' noprompt;
    recover database;
    alter database open;
    quit;
    Output of List Backup of database (I have done this after I recovered the second time, also note that it is referring to backupset2 which is were my second backup is stored)
    RMAN> list backup of database;
    using target database control file instead of recovery catalog
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    89 Full 261.87M DISK 00:01:37 28-SEP-11
    BP Key: 91 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
    Piece Name: /export/home/dev/restore_db/backupset/o1_mf_nnndf_TAG2011092
    8T171638_787g77rx_.bkp
    List of Datafiles in backup set 89
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    97 Full 259.16M DISK 00:00:00 28-SEP-11
    BP Key: 100 Status: AVAILABLE Compressed: YES Tag: TAG20110928T18352
    7
    Piece Name: /export/home/dev/restore_db/backupset/backupset2/o1_mf_nnndf
    TAG20110928T183527787lv0nb_.bkp
    List of Datafiles in backup set 97
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1816853 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf
    Output of list backup (done after restoring the control file)
    RMAN> list backup;
    BS Key Size Device Type Elapsed Time Completion Time
    87 89.20M DISK 00:00:26 28-SEP-11
    BP Key: 87 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_annnn_TAG20110928T171526_787g50bm_.bkp
    List of Archived Logs in backup set 87
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 34 1302253 20-SEP-11 1306439 20-SEP-11
    1 35 1306439 20-SEP-11 1307647 20-SEP-11
    1 36 1307647 20-SEP-11 1307701 20-SEP-11
    1 37 1307701 20-SEP-11 1311393 20-SEP-11
    1 38 1311393 20-SEP-11 1311511 20-SEP-11
    1 39 1311511 20-SEP-11 1332479 20-SEP-11
    1 40 1332479 20-SEP-11 1344418 20-SEP-11
    1 41 1344418 20-SEP-11 1350409 20-SEP-11
    1 42 1350409 20-SEP-11 1350449 20-SEP-11
    1 43 1350449 20-SEP-11 1350854 21-SEP-11
    1 44 1350854 21-SEP-11 1350895 21-SEP-11
    1 45 1350895 21-SEP-11 1353114 21-SEP-11
    1 46 1353114 21-SEP-11 1353254 21-SEP-11
    1 47 1353254 21-SEP-11 1353865 21-SEP-11
    1 48 1353865 21-SEP-11 1353988 21-SEP-11
    1 49 1353988 21-SEP-11 1375403 21-SEP-11
    1 50 1375403 21-SEP-11 1376149 21-SEP-11
    1 51 1376149 21-SEP-11 1376206 21-SEP-11
    1 52 1376206 21-SEP-11 1376246 21-SEP-11
    1 53 1376246 21-SEP-11 1379990 21-SEP-11
    1 54 1379990 21-SEP-11 1380229 21-SEP-11
    1 55 1380229 21-SEP-11 1380266 21-SEP-11
    1 56 1380266 21-SEP-11 1380528 21-SEP-11
    1 57 1380528 21-SEP-11 1380724 21-SEP-11
    1 58 1380724 21-SEP-11 1380861 21-SEP-11
    1 59 1380861 21-SEP-11 1381033 21-SEP-11
    1 60 1381033 21-SEP-11 1381077 21-SEP-11
    1 61 1381077 21-SEP-11 1402243 22-SEP-11
    1 62 1402243 22-SEP-11 1423341 22-SEP-11
    1 63 1423341 22-SEP-11 1435456 22-SEP-11
    1 64 1435456 22-SEP-11 1454415 23-SEP-11
    1 65 1454415 23-SEP-11 1490903 23-SEP-11
    1 66 1490903 23-SEP-11 1491266 23-SEP-11
    1 67 1491266 23-SEP-11 1491347 23-SEP-11
    1 68 1491347 23-SEP-11 1492761 23-SEP-11
    1 69 1492761 23-SEP-11 1492891 23-SEP-11
    1 70 1492891 23-SEP-11 1493678 23-SEP-11
    1 71 1493678 23-SEP-11 1493704 23-SEP-11
    1 72 1493704 23-SEP-11 1494741 23-SEP-11
    1 73 1494741 23-SEP-11 1494790 23-SEP-11
    1 74 1494790 23-SEP-11 1510154 23-SEP-11
    1 75 1510154 23-SEP-11 1514286 23-SEP-11
    1 76 1514286 23-SEP-11 1531967 24-SEP-11
    1 77 1531967 24-SEP-11 1543266 24-SEP-11
    1 78 1543266 24-SEP-11 1558427 24-SEP-11
    1 79 1558427 24-SEP-11 1566924 24-SEP-11
    1 80 1566924 24-SEP-11 1578292 24-SEP-11
    1 81 1578292 24-SEP-11 1596894 25-SEP-11
    BS Key Size Device Type Elapsed Time Completion Time
    88 84.03M DISK 00:00:30 28-SEP-11
    BP Key: 88 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171526
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_annnn_TAG20110928T171526_787g63s9_.bkp
    List of Archived Logs in backup set 88
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 82 1596894 25-SEP-11 1609028 25-SEP-11
    1 83 1609028 25-SEP-11 1622303 25-SEP-11
    1 84 1622303 25-SEP-11 1626430 25-SEP-11
    1 85 1626430 25-SEP-11 1634486 25-SEP-11
    1 86 1634486 25-SEP-11 1648398 25-SEP-11
    1 87 1648398 25-SEP-11 1669259 26-SEP-11
    1 88 1669259 26-SEP-11 1686820 26-SEP-11
    1 89 1686820 26-SEP-11 1686959 26-SEP-11
    1 90 1686959 26-SEP-11 1689168 26-SEP-11
    1 91 1689168 26-SEP-11 1704759 26-SEP-11
    1 92 1704759 26-SEP-11 1719597 27-SEP-11
    1 93 1719597 27-SEP-11 1740407 27-SEP-11
    1 94 1740407 27-SEP-11 1750125 27-SEP-11
    1 95 1750125 27-SEP-11 1765592 27-SEP-11
    1 96 1765592 27-SEP-11 1781498 28-SEP-11
    1 97 1781498 28-SEP-11 1802311 28-SEP-11
    1 98 1802311 28-SEP-11 1811009 28-SEP-11
    1 99 1811009 28-SEP-11 1813811 28-SEP-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    89 Full 261.87M DISK 00:01:37 28-SEP-11
    BP Key: 89 Status: AVAILABLE Compressed: YES Tag: TAG20110928T171638
    Piece Name: /oracle/app/dev/flash_recovery_area/FORUMS/backupset/2011_09
    _28/o1_mf_nnndf_TAG20110928T171638_787g77rx_.bkp
    List of Datafiles in backup set 89
    File LV Type Ckp SCN Ckp Time Name
    1 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/system01.dbf
    2 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/sysaux01.dbf
    3 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/undotbs01.dbf
    4 Full 1813849 28-SEP-11 /oracle/app/dev/oradata/forums/users01.dbf

  • Oracle 9i RMAN backup filling up all disk and failing at the very end

    Hello to all and thank you in advance for any input from any of you.
    I am new in oracle and the only one in my company with a little bit of oracle knowledge, which is not a whole lot.
    I inherited a few servers (Linux and Windows based). We mostly run all our production environment on a Linux box hosting oracle 10g release 10.2.0.1 but we had a legacy application server that still runs on 9i release 9.2.0.1.0. This server is a windows 2003 box, the previous DBA or someone else with admin rights to this machine compressed the whole drive where oracle resides, when I started summarying the oracle assets, I saw this server with no backups scheduled and a compressed disk with very limited space after this compression, only 13 GB left, the database if uncompressed would definitively filled up all the disk. The machine is in used and cannot be taken down for more than a couple of hours. We tried adding another disk but the machine only accept it as a hot spare. The database is in archive mode, when I tried to run a RMAN backup, it start filling up the database drive until it's empty and it crashes the whole machine, it seems like the buffer is growing and growing until it fills up the whole drive. The only way to get the server up and running again is to reboot the machine since the server is more than 6 years old we are not please with this action because we are afraid the machine would go south in one of those reboots.
    Has anyone heard of similar issues when running RMAN on a compressed drive? Can the compressed disk have any involvement in this kind of odd behaviour? I tried running the backup in debug mode and creating a log in a different disk (the one where the backup is going to) and still the same issue. Again any help is much appreciate,
    Sincerely,
    Alex

    Sybrand,
    Thank you for your fast response, I am going to use your previous post to answer one by one your question,
    1 The Oracle binaries --- on a compressed drive > Yes
    2 The Oracle database control files redo log files and datafiles on that same compressed drive? > Yes
    3 The archived redo log ditto? > Yes
    I know for a fact (as I have been using that in 9i) you can create a RMAN backup on a compressed drive, and you can have your archived redo go to a compressed drive. No problemo! > Excellent good news!!!
    But I would never touch the data files. Please note backup sets are multiplexed files consisting of multiple datafiles, so RMAN would need to do some calculations to decompress several blocks at the same time and to calculate a new block and compress it.
    Do you have enough space to:
    a) (preferred) to make datafile copies instead of a backup >
    Not in the drive that hosts the oracle instance but yes on an external usb drive (1TB) I attached to use as a backup repository, maybe this is why I am having these issues. I only have 13 GB left on that drive where the oracle instance resides (actually as I explained in a previous reply to Mark, the server only has 3 slots for disks, two of them as configured as RAID 1 and the other is a hot spare because the RAID configuration manager cannot can only added as hot-spare. The raided disk are partitioned in two, one small partition is for the OS and the other is for the oracle instance). When you said make a copy of the datafiles, I assumed you are talking about doing manual backups, and copying the database after using using "alter tablespace tablespace_name begin backup; then copy the file; alter tablespace tablespace_name end backup;
    b) use filesperset=1 on the backup command line, so the multiplexing (and associated calculations) stop. I have not tried the option of fileperset yet but I can tryi it and see if that helps.
    Can you post the last few lines of the RMAN log where RMAN bombs out? Note: the last few lines. Not all of it, or you must send some paracetamol in conjunction! >
    When I ran the debug option, I stopped the backup at less than 20% because I didn't want to reboot the system in the middle of the production time, the backup consumed at least 3 GB during the time was running. The times I ran the RMAN backup I didn't used the debug option so I don't have a log long enough to send unless you want the last few lines of what I have.
    Thanks again for your input,
    Sincerely,
    Alex

  • RMAN backup on RAC

    Hi,
    DB=10.2.0.4 OS=RHL (RAC with 2 nodes db01,db02). Following are the types of automated RMAN backups taken on db01.
    - OCR
    - Voting Disk
    - Talespaces Snapshot
    - Archivelog (every hour)
    - Backup Incremental level 0 (SUNDAY)
    -- backup incrementa level 1 (Mon-SAT)
    - Autobackup of Control file and SPFILE (CONTROLFILE AUTOBACKUP ON)
    Two main questions please. First, are these backups/backup types are enough FOR FULL RESTORE when talking about RMAN backup on RAC environment with 2 nodes? If not please suggest what else I need to backup?
    Secondly, backup home location is /rman which I can see on db01 ONLY. This /rman directory I cannot see on db02. My question is that In case of db02 failure can I restore from this /rman directory? or do I need to automate backup schedules also on db02 separately?
    [root@db01~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                          3.9G  2.9G  814M  79% /
    /dev/sda3             190M   34M  147M  19% /boot
    tmpfs                  16G     0   16G   0% /dev/shm
    /dev/mapper/VolGroup00-LogVol05
                          3.9G  137M  3.6G   4% /home
    /dev/mapper/VolGroup00-LogVol03
                          3.9G  225M  3.5G   6% /tmp
    /dev/mapper/VolGroup00-LogVol02
                          7.8G  3.7G  3.8G  50% /usr
    /dev/mapper/VolGroup00-LogVol04
                          3.9G  379M  3.4G  11% /var
    /dev/mapper/VolGroup00-ORACLE_BASE
                           12G  8.7G  2.6G  78% /oracle
    10.10.28.140:/vol/px4cinconso
                           40G  1.4G   39G   4% /inconso_px
    /dev/mapper/36001ec9000d5ea810000061349015d98
                          1.3T  551G  665G  46% /rman
    [root@db02~]# df -h
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/VolGroup00-LogVol00
                          3.9G  887M  2.9G  24% /
    /dev/sda3             190M   34M  147M  19% /boot
    tmpfs                  16G     0   16G   0% /dev/shm
    /dev/mapper/VolGroup00-LogVol05
                          3.9G  137M  3.6G   4% /home
    /dev/mapper/VolGroup00-LogVol03
                          3.9G  261M  3.5G   7% /tmp
    /dev/mapper/VolGroup00-LogVol02
                          7.8G  3.7G  3.8G  50% /usr
    /dev/mapper/VolGroup00-LogVol04
                          3.9G  355M  3.4G  10% /var
    /dev/mapper/VolGroup00-ORACLE_BASE
                           12G  6.5G  4.8G  58% /oracle
    10.10.28.140:/vol/px4cinconso
                           40G  1.4G   39G   4% /inconso_px
    [oracle@db01~]$ rman target /
    Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: F1 (DBID=1245145263)
    RMAN> show all;
    using target database control file instead of recovery catalog
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 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 '/rman/f1/fullbackup/%F';
    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 ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default
    # Script for backup
    level0 ()
    run {
      allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
      allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
      backup incremental level 0 tag = weeklyfull database channel c1
      plus archivelog tag = ARCH_$TODAY delete all input channel c2;
      release channel c1;
      release channel c2;
    run {
      allocate channel c1 type disk;
      delete noprompt obsolete;
      release channel c1;
    }Bundle of thanks.
    Regards,
    Edited by: 910385 on Feb 24, 2012 3:00 AM

    Hi,
    THanks alot for your feedback. Makes my life easier :) . But actually I started studying this all subject because of the following error message in the log file. I found out about this error that doesn't seem to harm. Just wait for the job to finish or it will sort out automatically. Here are the lines from the log file.
    Fehler in Backuplogs gefunden:/oracle/log/fcp11-backup-2300.log: RMAN-00571:
    ===========================================================brRMAN-00569: ===============
    ERROR MESSAGE STACK FOLLOWS ===============brRMAN-00571:
    ===========================================================brRMAN-03009: failure of
    Control File and SPFILE Autobackup command on c1 channel at 02/08/2012
    06:10:41brORA-00230: operation disallowed: snapshot control file enqueue unavailableI studied few important lines from one of my book, Oracle 11g RMAN backup and recovery (Roberg G Freeman) that I am going to write after the following MAIN ISSUE:
    Node 1
    RMAN> show all;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_fp11.f'; # default
    Node 2
    RMAN> show all;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_fp12.f'; # default
    Thing which I just noticed regarding the above RMAN error is that snapcf_fp11.f can be seen on the Node 1 on todays date but snapcf_fp12.f was only on 10th jan.
    [oracle@db01dbs]$ ls -lrth
    -rw-r----- 1 oracle oinstall  20M Feb 27 15:10 snapcf_fcp11.f
    [oracle@db02dbs]$ ls -lrth
    -rw-r----- 1 oracle oinstall  20M Jan 10 13:28 snapcf_fcp12.fTHe few lines from the book which I mentioned above are: (Though you might not need to read those lines):
    "You need to move the snapshot control file to a shared location if you plan to run backups from more than one node. If you do not move the snapshot control file to a shared file system such as OCFS or an ASM disk group, then you must make sure that the local destination is identical on all nodes."
    My question is of course, how to sort out the above log file error. Becuse in our case, backups are run only from one node, and snaphost control file is not being moved to ASM disk groups. Local destination is also same on both the Nodes, isn't it (with different names). Why on Node 2 last snapshot was taken on 10th jan while on Node 1 it is todays date which seems fine.
    Control file and SPFILE which I noticed are stored on ASM disk groups also, so being shared between the two Nodes.
    (Sanme names/same location for control file and SPFILE on Node 1 and Node 2)
    Control file:
    +REDO1/fp1/controlfile/current.256.652803827
    +DATA1/fp1/controlfile/current.441.652869697
    SPFILE:
    +DATA1/fp1/spfilefcp1.oraPlease suggest.
    Thank you.
    Regards,
    Edited by: 910385 on Feb 27, 2012 7:43 AM

  • Rman backup size

    Oracle11gr2,solaris10.
    how do i check the size of my daily rman lvl0 backup.
    i do a backup as compresses level 0.
    i find the sizes listed in rman>list backupset summary; but i wanted to get as a consolidated.
    My fra gets filled up after backing up the database continuously for 4 days. I remove the oldest backupset folder to release fra. I wanted to get a trend of how much rman is using each day for its backup.
    Thanks
    San~

    SQL> select ctime "Date"
      2       , decode(backup_type, 'L', 'Archive Log', 'D', 'Full', 'Incremental') backup_type
      3       , bsize "Size MB"
      4  from (select trunc(bp.completion_time) ctime
      5          , backup_type
      6          , round(sum(bp.bytes/1024/1024),2) bsize
      7     from v$backup_set bs, v$backup_piece bp
      8     where bs.set_stamp = bp.set_stamp
      9     and bs.set_count  = bp.set_count
    10     and bp.status = 'A'
    11     group by trunc(bp.completion_time), backup_type)
    12  order by 1, 2;
    Date      BACKUP_TYPE    Size MB
    03-JUL-10 Archive Log       7.31
    03-JUL-10 Full             29.81
    03-JUL-10 Incremental    2853.85
    04-JUL-10 Archive Log       3.59
    04-JUL-10 Full              7.45
    04-JUL-10 Incremental       3.05refer : How to find backupset sizes for full and incremental backups answered by ebrian      
    How to find backupset sizes for full and incremental backups
    Total questions     45 (39 unresolved) : mark the question as answered if you get the answer for your questions.
    Announcement: Forums Etiquette / Reward Points
    Posters, please mind these common-sense rules when participating here:
    - When asking a question, provide all the details that someone would need to answer it. Consulting documentation first is highly recommended.
    - When answering a question, please be courteous and respectful; there are different levels of experience represented here. A poorly worded question is better ignored than flamed - or better yet, help the poster ask a better question.
    - It is considered good etiquette to reward answerers with points (as "helpful" - 5 pts - or "correct" - 10pts).
    - See more tips in the FAQ
    Thanks for doing your part to make this community as valuable as possible for everyone!
    - OTN Edited by: rajeysh on Jul 7, 2010 2:11 AM

Maybe you are looking for

  • Multi Mailbox Search Date Range Results Inaccurate

    Hi All, I have an Exchange 2010 server with SP3 /RU3 installed. When I do a multi mailbox search using OWA /ECP and put in a start and end date from the Date Range dropdown box, my search results shows me more than just the intended date range of ema

  • JSF-JPA error in netbeans

    hi IDE: Netbeans7.1 Server:Weblogic 10.0 JSF:2.1 JPA:toplink essential JPA 1.0 When i`m inserting JPA in my JSF project following error Shown, Any one have Idea abt it? init: deps-module-jar: deps-ear-jar: deps-jar: library-inclusion-in-archive: libr

  • Errors installing the psoftware

    hey guys. I cannot seem to update or install any software onto my imac everytime i try i get the installer saying "There were errors installing the software" along with "Please try installing again". How can i resolve this problem? ive verified permi

  • Mixed phone numbers and names after sinc N9 and ov...

    I have problem with my contact list. After i synchonised my previous N79 with N9, everything was fine. AFter adding new contacts to the new phone i wanted to synchronise it with ovi, i did so but it made completely mess with all my contacts. I cant s

  • Why Lightroom keeps using 30% CPU power all the time?

    Hello all, I am relatively new to LIghtRoom. I started working on a new set of photos  (400 app.). I opened it as new directory. Since then, all the time I work on theses pictures Lightroom keeps using app. 30% of CPU time. The over all time I spent