RMAN backup deletion by BP key

Hello,
We are having 2 node 11g RAC (ASM) cluster & had set up one ASM disk as FRA on which daily rman backup is performed now as FRA is running out of space we are required to backup FRA so I backup FRA using backup recovery area; now after that all my backups in list backupset summary command are coming as below
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
263 B F A * 28-MAR-11 1 2 YES BACKUP_PRODAILY_032811100000
264 B F A * 28-MAR-11 1 2 YES BACKUP_PRODAILY_032811100000
265 B F A * 28-MAR-11 1 2 YES BACKUP_PRODAILY_032811100000
& for each backup peice I am having two copies one on tape & other on FRA so now I want to remove one copy of every peice i.e FRA's one so taht FRA can be empty, Please tell me how can I delete one copy of each backupset as both copies are having same backupset set but hav different BP KEY as below
RMAN> list backupset 263;
List of Backup Sets
===================
BS Key Type LV Size
263 Full 1001.36M
List of Datafiles in backup set 263
File LV Type Ckp SCN Ckp Time Name
10 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/system.278.742062987
12 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/undotbs1.258.742063665
15 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/apps_ts_media.271.742062841
18 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/apps_ts_queues.285.742063093
27 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/apps_ts_tx_idx.259.742062485
29 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/apps_ts_tx_idx.266.742062695
30 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/ctxd.295.742063149
42 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/apps_ts_media.327.742654423
50 Full 124174871 28-MAR-11 +DATAPROD/prod/datafile/xxmpcd_ts_tx_idx.336.742838847
Backup Set Copy #1 of backup set 263
Device Type Elapsed Time Completion Time Compressed Tag
DISK 00:07:47 28-MAR-11 YES BACKUP_PRODAILY_032811100000
List of Backup Pieces for backup set 263 Copy #1
BP Key Pc# Status Piece Name
651 1 AVAILABLE +FRAPROD/prod/backupset/2011_03_28/nnndf0_backup_prodaily_032811100000_0.393.747007719
Backup Set Copy #2 of backup set 263
Device Type Elapsed Time Completion Time Compressed Tag
SBT_TAPE 00:07:47 25-APR-11 YES BACKUP_PRODAILY_032811100000
List of Backup Pieces for backup set 263 Copy #2
BP Key Pc# Status Media Piece Name
1036 1 AVAILABLE 3764a8c0:4daeb8e0:06c8:0001 FRA_BKP<PROD_361:747007718:1>.dbf
So please tell me how can I remove just one copy so that FRA can be empty.
Thanks & Regards
Saransh Soni

Maybe you may set retention policy to 1,
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
End after taking a backup, you issue the following command so previous backup will be deleted:
RMAN> DELETE OBSOLETE;
Regards
Gokhan

Similar Messages

  • Unable to backup/delete/change encryption key after SSRS 2008 R2 installation

    Hi,
    I am having issue with SSRS 2008 R2 Std installation with Sharepoint integration. hope may get some help from here.
    During the SSRS configuration in the SSRS Config Mgr
    the following error message come up when access web service URL/backup/delete/change encryption key:
    Report service error
    •An internal error occurred on the report server. See the error log for more
    details. (rsInternalError) Get Online Help
    ◦The profile for the user is a temporary profile. (Exception from HRESULT:
    0x80090024)
    I can avoid the issue when use Local system account to run the SSRS but domain account is required for Sharepoint integration.
    Does this have something to do with how the windows user profiles are configured?

    Hi Gone_Fishing,
    Reporting Services uses encryption keys to secure credentials and connection information that is stored in a report server database. In Reporting Services, encryption is supported through a combination of public, private, and symmetric keys that are
    used to protect sensitive data. As to access Web Service URL, we can try to cope the URL, then run it in IE as administrators.
    About the error”The profile for the user is a temporary profile”, Windows will create a temporary profile when it is unable to read the user profile files. For more details, we can refer to the following blog:
    http://journeyintobi.com/2013/11/the-profile-for-the-user-is-a-temporary-profile-or-how-simple-solutions-are-sometimes-really-the-answer-to-a-given-problem/
    Hope this helps.
    Thanks,
    Katherine Xiong
    Katherine Xiong
    TechNet Community Support

  • Rman backups delete

    What commands would I use to do the following:
    Daily I take a full compressed backup. I currently use:
    backup as compressed backupset database;
    And backup my archivelogs. I currently use:
    backup archivelog all;
    Then I want to keep 2 days of backup and archivelogs on disk and maybe 7 days of backup and backed up archivelogs on tape. How do I accomplish this part?

    For what you are doing I like to utilize a storage manager product with my tape system where the files on disk are brought to tape automatically and stub files left in place where the files appear to be in the directory but are really on tape. This way I can just manage RMAN backup pieces and execute dsik based backups normally but manage my disk space better, manage RMAN as normal because as for as RMAN is concerned the files are there on disk. Tivoli Storage Manager (TSM) has a product that does this called HSM, other vendors have Hierarchical Storage Management (HSM) products as well. They are usually pretty inexpensive and remove complication related to managing the backup pieces between disk and tape with RMAN. You get the best of both worlds without having to manage anything differently then just disk based backups and you can use less storage.

  • RMAN never deletes archive log backups

    Hi all,
    I have same problem as some of you have already faced.
    I have some instances 10.2.0.4 running un archive log mode.
    I take full hot backup daily.
    I setup a rman script to backup and delete obsolete backups according to the following policy:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
    CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
    and then:
    run {
    ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
    BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
    CROSSCHECK ARCHIVELOG ALL;
    BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
    CROSSCHECK BACKUP;
    DELETE NOPROMPT OBSOLETE;
    DELETE NOPROMPT EXPIRED BACKUP;
    RELEASE CHANNEL RMAN_BACK_CH01;
    crosscheck archivelog all;
    delete noprompt archivelog all completed before 'sysdate -2';
    DB full backups are being deleted, however archive logs backups are not deleted.
    There are no tablespaces in backup or offline mode.
    How can I know the reason why some archive log backups are kept ?
    Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
    Thanks in advance.

    Hi Fernando,
    This are the ouputpus of the commands:
    RMAN> REPORT OBSOLETE;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to redundancy 1
    no obsolete backups found
    RMAN> LIST BACKUP OF ARCHIVELOG ALL;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    1090 69.65M DISK 00:00:16 23-FEB-11
    BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
    List of Archived Logs in backup set 1090
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
    1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
    1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
    1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
    1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1411 125.43M DISK 00:00:28 24-FEB-11
    BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
    List of Archived Logs in backup set 1411
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
    1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
    1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
    1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1600 164.40M DISK 00:00:37 25-FEB-11
    BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
    List of Archived Logs in backup set 1600
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
    1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
    1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    1829 132.24M DISK 00:00:30 26-FEB-11
    BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
    List of Archived Logs in backup set 1829
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
    1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
    1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2058 218.03M DISK 00:00:48 27-FEB-11
    BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
    Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
    List of Archived Logs in backup set 2058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
    1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2298 205.39M DISK 00:00:45 28-FEB-11
    BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
    Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
    List of Archived Logs in backup set 2298
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
    1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    BS Key Size Device Type Elapsed Time Completion Time
    2546 180.29M DISK 00:00:39 01-MAR-11
    BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
    Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
    List of Archived Logs in backup set 2546
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
    1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
    1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
    1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    2801 85.40M DISK 00:00:19 02-MAR-11
    BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
    Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
    List of Archived Logs in backup set 2801
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
    1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3058 137.93M DISK 00:00:30 03-MAR-11
    BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
    List of Archived Logs in backup set 3058
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
    1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3324 138.96M DISK 00:00:31 04-MAR-11
    BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
    List of Archived Logs in backup set 3324
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3597 178.07M DISK 00:00:39 05-MAR-11
    BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
    List of Archived Logs in backup set 3597
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
    1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
    1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
    1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    3835 198.44M DISK 00:00:43 06-MAR-11
    BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
    List of Archived Logs in backup set 3835
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
    1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4131 185.94M DISK 00:00:40 07-MAR-11
    BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
    List of Archived Logs in backup set 4131
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
    1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4435 161.37M DISK 00:00:35 08-MAR-11
    BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
    List of Archived Logs in backup set 4435
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
    1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
    1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
    1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    4745 79.24M DISK 00:00:18 09-MAR-11
    BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
    Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
    List of Archived Logs in backup set 4745
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
    1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    5270 135.13M DISK 00:00:31 10-MAR-11
    BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
    Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
    List of Archived Logs in backup set 5270
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
    1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
    1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
    1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
    1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
    1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
    RMAN>
    For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
    I'd like to understand why it happens :-)
    Thanks a lot,
    Regards,
    Diego.

  • RMAN backup files are still exist since long time, how to delete?

    Dear sir;
    I'm using the below script to do daily backup, however there are many rman backup files are still exist and consumes HD size, how could I delete these files in daily bases? some files dated in FEB, MAR, APR,
    ============Daily RMAN script=========
    rman target /<<!
    backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
    backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
    backup current controlfile format '/u15/rman/control_%U.rman';
    delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
    delete noprompt obsolete;
    ================================END
    Thanks and best regards
    Ali

    Hi;
    Our backup policy should have 7 days; however we have here some files from JAN, FEB,MAR, APR /2012 WHICH ARE BEYOND THE RETENTION DATE and these files should be deleted by executing " delete noprompt obsolete; ".
    All files are exist in /u15/rman/
    -rw-r----- 1 oracle oinstall 1151763968 Jan 21 01:36 arc_backup_7kn19h4a_1_1.rman
    -rw-r----- 1 oracle oinstall 1136882176 Jan 21 01:36 arc_backup_7ln19h4q_1_1.rman
    -rw-r----- 1 oracle oinstall 1135984640 Jan 21 01:36 arc_backup_7mn19h5a_1_1.rman
    -rw-r----- 1 oracle oinstall 1126627328 Jan 21 01:37 arc_backup_7nn19h5q_1_1.rman
    -rw-r----- 1 oracle oinstall 880606720 Mar 12 02:53 arc_backup_7nn5ldhp_1_1.rman
    -rw-r----- 1 oracle oinstall 1093043712 Jan 21 01:37 arc_backup_7on19h6a_1_1.rman
    -rw-r----- 1 oracle oinstall 9797632 Dec 15 01:04 control_04mu7tcp_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 3 02:55 control_4cn4tm9k_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 4 02:53 control_4on50ahm_1_1.rman
    -rw-r----- 1 oracle oinstall 36896768 Mar 5 02:55 control_56n52v1j_1_1.rman
    -rw-r----- 1 oracle oinstall 16252928 Jan 23 01:40 control_8tn1eq3t_1_1.rman
    -rw-r----- 1 oracle oinstall 16252928 Jan 24 01:40 control_9cn1heg0_1_1.rman
    -rw-r----- 1 oracle oinstall 202940416 Dec 15 01:04 full_backup_01mu7t50_1_1.rman
    -rw-r----- 1 oracle oinstall 1097728 Dec 15 01:04 full_backup_02mu7tcc_1_1.rman
    -rw-r----- 1 oracle oinstall 201285632 Dec 14 01:04 full_backup_0nmu58ou_1_1.rman
    -rw-r----- 1 oracle oinstall 5957304320 Feb 29 02:46 full_backup_2ln4g9l1_1_1.rman
    -rw-r----- 1 oracle oinstall 4128768 Feb 29 02:47 full_backup_2mn4gft8_1_1.rman
    -rw-r----- 1 oracle oinstall 6027075584 Mar 1 02:49 full_backup_32n4o6ov_1_1.rman
    -rw-r----- 1 oracle oinstall 4128768 Mar 1 02:49 full_backup_33n4od66_1_1.rman
    -rw-r----- 1 oracle oinstall 6187171840 Mar 2 02:51 full_backup_3gn4qr50_1_1.rman
    -rw-r----- 1 oracle oinstall 4145152 Mar 2 02:51 full_backup_3hn4r1kn_1_1.rman
    -rw-r----- 1 oracle oinstall 6115786752 Mar 3 02:51 full_backup_40n4tfgu_1_1.rman
    above is a short list of contents.
    to do our daily backup we perform the following script (in daily)
    ==================
    backup incremental level=0 as compressed backupset database format '/u15/rman/full_backup_%U.rman';
    backup archivelog all not backed up 2 times format '/u15/rman/arc_backup_%U.rman';
    backup current controlfile format '/u15/rman/control_%U.rman';
    delete archivelog all backed up 2 times to device type disk completed before 'sysdate-7';
    delete noprompt obsolete;
    ==================
    Thanks and best regards
    Ali

  • Delete RMAN backup

    Oracle 11.2.0.1
    Windows
    I takes RMAN backup at D:\RMAN_BAKCUP of our test database. Now there is space problem, I have to allocate some space to other folder. I shall take cold backup of database by shutdown. How do I start to delete RMAN backup from above location. It is incremental backup. What precautions should be there while deleting RMAN backup with archive logs.
    Can I delete all archive logs too after consistent backup by shutting down the database ?
    I am facing space problem, thats why I though that I shall take cold backup of db and now no need of rman backup as well as archive logs. Am I correct ?
    Thanks.

    user12050217 wrote:
    Oracle 11.2.0.1
    Windows
    I takes RMAN backup at D:\RMAN_BAKCUP of our test database. Now there is space problem, I have to allocate some space to other folder. I shall take cold backup of database by shutdown. How do I start to delete RMAN backup from above location. It is incremental backup. What precautions should be there while deleting RMAN backup with archive logs.
    Can I delete all archive logs too after consistent backup by shutting down the database ?
    I am facing space problem, thats why I though that I shall take cold backup of db and now no need of rman backup as well as archive logs. Am I correct ?
    Thanks.Given what else I've read in this thread (test database, no need for point in time recovery, etc.) A 'cold' backup may be appropriate, but I'd still use rman to do it. I have a similar situation right now with one of my test databases. I took an rman cold backup (database is open MOUNT) with KEEP UNTIL 'SYSDATE + 60'. Once, sometimes twice, a day the developer asks for a restore to the backup. Piece of cake with rman, especially with a little script all ready to go. Would be a bit more difficult with a 'user managed' backup.

  • Deleting old rman backup

    Hi
    Let say I have a rman backup on Monday,Tuesday,Wednesday,Thursday.
    Would it be possible to delete only monday`s backup from rman? Note that it is not obsolete.

    hi,
    how about this:
    delete backup completed before "19-FEB-2010";
    or
    delete backup completed between "17-FEB-2010" and "19-FEB-2010";
    Is it correct/helpful ?
    Edited by: g777 on 2010-02-19 07:39

  • RMAN backup archivelog all delete input

    Hello DBAs,
    what does this command will do?
    RMAN> backup archivelog all delete input;
    DN

    I have set cron job for RMAN> backup archivelog all delete input; and its work.
    But I got following message in my log file.
    Please give ur feed back.
    Recovery Manager: Release 10.1.0.4.0 - 64bit Production
    Copyright (c) 1995, 2004, Oracle. All rights reserved.
    RMAN>
    connected to target database: SIDNAME (DBID=XXXXXXXX)
    using target database controlfile instead of recovery catalog
    RMAN>
    Starting backup at 10-FEB-06
    current log archived
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=269 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=268 devtype=DISK
    channel ORA_DISK_1: starting compressed archive log backupset
    channel ORA_DISK_1: specifying archive log(s) in backup set
    input archive log thread=1 sequence=5701 recid=2412 stamp=581958928
    input archive log thread=1 sequence=5702 recid=2413 stamp=581961105
    input archive log thread=1 sequence=5703 recid=2414 stamp=581964532
    input archive log thread=1 sequence=5704 recid=2415 stamp=582025325
    input archive log thread=1 sequence=5705 recid=2416 stamp=582029976
    input archive log thread=1 sequence=5706 recid=2417 stamp=582031922
    channel ORA_DISK_1: starting piece 1 at 10-FEB-06
    channel ORA_DISK_2: starting compressed archive log backupset
    channel ORA_DISK_2: specifying archive log(s) in backup set
    input archive log thread=1 sequence=5707 recid=2418 stamp=582037207
    input archive log thread=1 sequence=5708 recid=2419 stamp=582038471
    input archive log thread=1 sequence=5709 recid=2420 stamp=582043538
    input archive log thread=1 sequence=5710 recid=2421 stamp=582048518
    input archive log thread=1 sequence=5711 recid=2422 stamp=582055205
    channel ORA_DISK_2: starting piece 1 at 10-FEB-06
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
    12
    ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
    blocksize=512)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 1048576
    channel ORA_DISK_1 disabled, job failed on it will be run on another channel
    RMAN-03009: failure of backup command on ORA_DISK_2 channel at 02/10/2006 18:00:
    12
    ORA-19502: write error on file "/u02/backup/6fhb2t97_1_1", blockno 6145
    (blocksize=512)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 1048576
    channel ORA_DISK_2 disabled, job failed on it will be run on another channel
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of backup command on ORA_DISK_1 channel at 02/10/2006 18:00:
    12
    ORA-19502: write error on file "/u02/backup/backup_6ehb2t97_1_1", blockno 6145 (
    blocksize=512)
    ORA-27063: number of bytes read/written is incorrect
    IBM AIX RISC System/6000 Error: 28: No space left on device
    Additional information: -1
    Additional information: 1048576
    RMAN>
    Recovery Manager complete.
    DN

  • How can i delete old RMAN backup files

    Hi All
    We have configured RMAN backup for one of our clients PROD instance[10.2.0.3] in 2010 Dec.
    Now my doubt is how can i delte old backup files of Dec and January, only this two months backup files only i need to delte.
    kindly suggest me.
    The parameters are :
    CONFIGURE RETENTION POLICY TO NONE;
    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 '/ebiz/backup/PROD-%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 CHANNEL DEVICE TYPE DISK FORMAT '/ebiz/backup/PROD-%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 '/ebiz/oracle/proddb/10.2.0/dbs/snapcf_PROD.f'; # default
    Regards
    Shaik

    Hello,
    You can use this :
    DELETE BACKUP COMPLETED BEFORE TO_DATE('01/31/2011 00:00:00','MM/DD/YY HH24:MI:SS');Regards,
    Sylvie

  • Delete all AVAILABLE valid RMAN backup by RMAN command

    Hi
    We are taking RMAN full backup on disk every day. But right now we don’t have enough space on RMAN backup mount point. So we want to delete all AVAILABLE valid RMAN backup by RMAN command.
    Please guide to delete all AVAILABLE valid RMAN backup by RMAN command.
    -Thanks
    Edited by: Fazlul Kabir Mahfuz on May 13, 2013 11:06 AM

    You can do it by manually delete the backups and archivelogs from OS location. Then use below commands
    RMAN>crosscheck backup;
    It will give status as EXPIRED for backups which are valid but not available at OS level.
    RMAN>delete expired backup;
    Delete all the backups whose status are EXPIRED from database level.
    Similarly for archivelogs
    RMAN>crosscheck archivelog all;
    RMAN>delete expired archivelog all;

  • Delete rman backups

    Hi
    how to delete the rman old backups?
    i tried to issue
    1.)delete obsolete; delete no prompt obsolete;
    Next
    2.)crosscheck backup;
    delete expired backup;
    My retention policy is for 2 days.
    Now i want to know my disk space is getting filled. the backups in that partition is having oct 10 th oct 9th backups
    But if i issue delete obsolete; it said no obsolete backups found
    BUt still the old backups are there. how will i clear the space and how will i delete these backups?
    i guess i cant delete this through normal rm command also .. still its occupying space.pls suggest.
    oracle-10g version

    RMAN> report obsolete;
    RMAN retention policy will be applied to the command
    RMAN retention policy is set to recovery window of 2 days
    no obsolete backups found
    RMAN> report obsolete orphan;
    no obsolete backups found
    RMAN>
    ----------------------------------------l
    ls -lrt
    rw-r----- 1 oracle oinstall 12900327424 Oct 19 04:57 DBBS_FULL_700632559_4496_1
    -rw-r----- 1 oracle oinstall 17884839936 Oct 19 05:28 DBBS_FULL_700633835_4497_1
    -rw-r----- 1 oracle oinstall 15564259328 Oct 19 05:54 DBBS_FULL_700635470_4498_1
    -rw-r----- 1 oracle oinstall 15396831232 Oct 19 06:24 DBBS_FULL_700637346_4499_1
    -rw-r----- 1 oracle oinstall 11847139328 Oct 19 06:41 DBBS_FULL_700638851_4500_1
    -rw-r----- 1 oracle oinstall 12832841728 Oct 19 07:12 DBBS_FULL_700640677_4501_1
    -rw-r----- 1 oracle oinstall 11583221248 Oct 19 08:35 DBBS_arc_DBBS_coks614m_4504
    -rw-r----- 1 oracle oinstall 12025791488 Oct 19 08:36 DBBS_arc_DBBS_cpks614m_4505
    -rw-r----- 1 oracle oinstall 70328320 Oct 19 17:56 DBBS_LVL01_700681556_4537_1
    -rw-r----- 1 oracle oinstall 266862592 Oct 19 17:59 DBBS_LVL01_700681556_4538_1
    -rw-r----- 1 oracle oinstall 315555840 Oct 19 18:06 DBBS_LVL01_700682192_4539_1
    -rw-r----- 1 oracle oinstall 326918144 Oct 19 18:10 DBBS_LVL01_700682347_4540_1
    -rw-r----- 1 oracle oinstall 334602240 Oct 19 18:16 DBBS_LVL01_700682813_4541_1
    -rw-r----- 1 oracle oinstall 1218052096 Oct 19 18:30 DBBS_LVL01_700683413_4543_1
    -rw-r----- 1 oracle oinstall 404602880 Oct 19 18:41 DBBS_LVL01_700684250_4544_1
    -rw-r----- 1 oracle oinstall 123543552 Oct 19 18:50 DBBS_LVL01_700684906_4545_1
    -rw-r----- 1 oracle oinstall 12227190784 Oct 19 18:52 DBBS_LVL01_700683048_4542_1
    -rw-r----- 1 oracle oinstall 61063168 Oct 19 19:01 DBBS_LVL01_700685442_4546_1
    -rw-r----- 1 oracle oinstall 361545728 Oct 19 19:05 DBBS_LVL01_700685527_4547_1
    -rw-r----- 1 oracle oinstall 278085632 Oct 19 19:16 DBBS_LVL01_700686338_4549_1
    -rw-r----- 1 oracle oinstall 848576512 Oct 19 19:16 DBBS_LVL01_700686093_4548_1
    -rw-r----- 1 oracle oinstall 422010880 Oct 19 19:28 DBBS_LVL01_700686984_4551_1
    -rw-r----- 1 oracle oinstall 238927872 Oct 19 19:29 DBBS_LVL01_700686984_4550_1
    -rw-r----- 1 oracle oinstall 409198592 Oct 19 19:40 DBBS_LVL01_700687740_4552_1
    -rw-r----- 1 oracle oinstall 257196032 Oct 19 19:41 DBBS_LVL01_700687786_4553_1
    -rw-r----- 1 oracle oinstall 529489920 Oct 19 19:51 DBBS_LVL01_700688411_4554_1
    -rw-r----- 1 oracle oinstall 110436352 Oct 19 19:52 DBBS_LVL01_700688507_4555_1
    -rw-r----- 1 oracle oinstall 255172608 Oct 19 20:02 DBBS_LVL01_700689113_4556_1
    -rw-r----- 1 oracle oinstall 269983744 Oct 19 20:03 DBBS_LVL01_700689128_4557_1
    -rw-r----- 1 oracle oinstall 205185024 Oct 19 20:10 DBBS_LVL01_700689774_4558_1
    -rw-r----- 1 oracle oinstall 10838016512 Oct 20 08:33 DBBS_arc_DBBS_ehks8lg8_4561
    -rw-r----- 1 oracle oinstall 12192736768 Oct 20 08:35 DBBS_arc_DBBS_eiks8lg8_4562
    -rw-r----- 1 oracle oinstall 11442476544 Oct 20 09:06 DBBS_arc_DBBS_ejks8nb2_4563
    -rw-r----- 1 oracle oinstall 11550635008 Oct 20 09:08 DBBS_arc_DBBS_ekks8nfq_4564
    -rw-r----- 1 oracle oinstall 11564595200 Oct 20 09:40 DBBS_arc_DBBS_elks8p9d_4565
    -rw-r----- 1 oracle oinstall 11148586496 Oct 20 09:42 DBBS_arc_DBBS_emks8pcu_4566
    -rw-r----- 1 oracle oinstall 11379881984 Oct 20 10:22 DBBS_arc_DBBS_enks8r91_4567
    -rw-r----- 1 oracle oinstall 11044812800 Oct 20 10:22 DBBS_arc_DBBS_eoks8rbt_4568
    -rw-r----- 1 oracle oinstall 11134934016 Oct 20 10:56 DBBS_arc_DBBS_epks8tnd_4569
    -rw-r----- 1 oracle oinstall 11645493248 Oct 20 10:58 DBBS_arc_DBBS_eqks8tof_4570
    -rw-r----- 1 oracle oinstall 11573557760 Oct 20 11:31 DBBS_arc_DBBS_erks8vo2_4571
    -rw-r----- 1 oracle oinstall 11303386624 Oct 20 11:33 DBBS_arc_DBBS_esks8vrl_4572
    -rw-r----- 1 oracle oinstall 10233166336 Oct 20 12:05 DBBS_arc_DBBS_euks91sn_4574
    -rw-r----- 1 oracle oinstall 11399922176 Oct 20 12:05 DBBS_arc_DBBS_etks91pr_4573
    -rw-r----- 1 oracle oinstall 11519147520 Oct 20 12:40 DBBS_arc_DBBS_evks93p9_4575
    -rw-r----- 1 oracle oinstall 11412811776 Oct 20 12:41 DBBS_arc_DBBS_f0ks93pi_4576
    -rw-r----- 1 oracle oinstall 8986724864 Oct 20 13:08 DBBS_arc_DBBS_f2ks95rj_4578
    -rw-r----- 1 oracle oinstall 12143316480 Oct 20 13:15 DBBS_arc_DBBS_f1ks95rc_4577

  • Restore spfile from rman backup ---- error.

    Hi,
    I am trying to execute recovery on new machine ...
    I have done the following steps..
    I have one database as ora10g2 as peroduction database on one machine as hosta
    I have created a catalog on another machine cora10g2 (hostb)
    I have taken a full backup from hosta as per following ...
    the following command execute from hosta machine.
    $ rman target sys/<passwd>@ora10g2 catalog rman/rman@cora10g2 ...
    Backup completed ...
    Now I am trying to restore this backup on hostb machine where i have already rman catlog database ..
    I have done the following setting ...on host b
    set oracle_sid=DUP
    and execute following command ...
    rman target / catalog rman/rman@cora10g2
    RMAN> set dbid 2760732370
    executing command: SET DBID
    database name is "BAAN10G2" and DBID is 2760732370
    RMAN>
    RMAN>
    RMAN> startup force nomount ;
    startup failed: ORA-01078: failure in processing system parameters
    LRM-00109: could not open parameter file '/oracle/dbs/baan10g2/dbs/initbaan10g2.ora'
    starting Oracle instance without parameter file for retrival of spfile
    Oracle instance started
    Total System Global Area 159383552 bytes
    Fixed Size 1977112 bytes
    Variable Size 67114216 bytes
    Database Buffers 83886080 bytes
    Redo Buffers 6406144 bytes
    RMAN>
    RMAN>
    RMAN>
    RMAN> show all ;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/backup/control/cntrl_%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO 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 DEVICE TYPE DISK FORMAT '/baanora3/rman/ora10g2/bkup_db_%d_s%s_P%p_t%t' MAXPIECESIZE 1024;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    RMAN>
    RMAN>
    RMAN> list backup of spfile ;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2420 Full 7.33M DISK 00:00:01 14-JUN-07
    BP Key: 2426 Status: AVAILABLE Compressed: NO Tag: TAG20070614T182935
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070614-00
    SPFILE Included: Modification time: 14-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2509 Full 7.33M DISK 00:00:01 15-JUN-07
    BP Key: 2515 Status: AVAILABLE Compressed: NO Tag: TAG20070615T130416
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-00
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2694 Full 7.33M DISK 00:00:01 15-JUN-07
    BP Key: 2739 Status: AVAILABLE Compressed: NO Tag: TAG20070615T131703
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-01
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2760 Full 80.00K DISK 00:00:01 15-JUN-07
    BP Key: 2763 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163437
    Piece Name: /rman/spfile/spfile.ora
    SPFILE Included: Modification time: 15-JUN-07
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2769 Full 7.33M DISK 00:00:02 15-JUN-07
    BP Key: 2771 Status: AVAILABLE Compressed: NO Tag: TAG20070615T163441
    Piece Name: /rman/backup/control/cntrl_c-2760732370-20070615-02
    SPFILE Included: Modification time: 15-JUN-07
    RMAN>
    RMAN>
    RMAN> restore spfile from autobackup ;
    Starting restore at 19-JUN-07
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=36 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=35 devtype=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: sid=34 devtype=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: sid=33 devtype=DISK
    channel ORA_DISK_1: looking for autobackup on day: 20070619
    channel ORA_DISK_1: looking for autobackup on day: 20070618
    channel ORA_DISK_1: looking for autobackup on day: 20070617
    channel ORA_DISK_1: looking for autobackup on day: 20070616
    channel ORA_DISK_1: looking for autobackup on day: 20070615
    channel ORA_DISK_1: looking for autobackup on day: 20070614
    channel ORA_DISK_1: looking for autobackup on day: 20070613
    channel ORA_DISK_1: no autobackup in 7 days found
    channel ORA_DISK_2: looking for autobackup on day: 20070619
    channel ORA_DISK_2: looking for autobackup on day: 20070618
    channel ORA_DISK_2: looking for autobackup on day: 20070617
    channel ORA_DISK_2: looking for autobackup on day: 20070616
    channel ORA_DISK_2: looking for autobackup on day: 20070615
    channel ORA_DISK_2: looking for autobackup on day: 20070614
    channel ORA_DISK_2: looking for autobackup on day: 20070613
    channel ORA_DISK_2: no autobackup in 7 days found
    channel ORA_DISK_3: looking for autobackup on day: 20070619
    channel ORA_DISK_3: looking for autobackup on day: 20070618
    channel ORA_DISK_3: looking for autobackup on day: 20070617
    channel ORA_DISK_3: looking for autobackup on day: 20070616
    channel ORA_DISK_3: looking for autobackup on day: 20070615
    channel ORA_DISK_3: looking for autobackup on day: 20070614
    channel ORA_DISK_3: looking for autobackup on day: 20070613
    channel ORA_DISK_3: no autobackup in 7 days found
    channel ORA_DISK_4: looking for autobackup on day: 20070619
    channel ORA_DISK_4: looking for autobackup on day: 20070618
    channel ORA_DISK_4: looking for autobackup on day: 20070617
    channel ORA_DISK_4: looking for autobackup on day: 20070616
    channel ORA_DISK_4: looking for autobackup on day: 20070615
    channel ORA_DISK_4: looking for autobackup on day: 20070614
    channel ORA_DISK_4: looking for autobackup on day: 20070613
    channel ORA_DISK_4: no autobackup in 7 days found
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 06/19/2007 18:00:13
    RMAN-06172: no autobackup found or specified handle is not a valid copy or piece
    RMAN>
    I am not able to restore spfile from rman backup ;;;

    Hi,
    I would like to know few things
    1. How are you setting the db_name ? you can set db_id at RMAN, how are you setting the db_name ?
    2. Do you have any default init file at default location ? if yes, is the db_name parameter set correctly in that file ?
    Since spfile is yet to be restored, you must set the db_name parameter correctly before you start spfile restore.This can be done with init file at default location which can even contain just one paremeter i.e db_name.

  • Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

    I will explain my scenario below:
    We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
    Please suggest me the best way forward...
    Many Thanks
    Nukesh

    Hi Asif,
    I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
    RMAN> list incarnation;
    using target database control file instead of recovery catalog
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
    2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
    3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
    RMAN> exit
    TEST1DB-> rman target sys@MYTEST1
    Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    target database Password:
    connected to target database: MYTEST (DBID=2433328848, not open)
    RMAN> reset database to incarnation 2;
    using target database control file instead of recovery catalog
    database reset to incarnation 2
    RMAN> run {
    2> restore database until scn 10000;
    3> recover database until scn 10000;
    4> alter database open resetlogs;
    5> };
    Starting restore at 07-NOV-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/07/2010 11:45:18
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
    RMAN-01007: at line 0 column 2 file: standard input
    RMAN>
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO 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 DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
    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 '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
    RMAN> exit
    SQL> select name from v$database;
    NAME
    MYTEST
    SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    SQL>

  • Need help in the RMAN backup

    Hi everybody
    What are the steps needed if move the RMAN backup to other location in the OS level
    (ie) every week i have to move the backup to other location

    There are not problem for example:
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.
    C:\Documents and Settings\comp>set ORACLE_SID=W
    C:\Documents and Settings\comp>sqlplus "/as sysdba"
    SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 26 14:53:08 2010
    Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
    ERROR:
    ORA-01031: insufficient privileges
    Enter user-name:
    C:\Documents and Settings\comp>sqlplus "sys/sm as sysdba"
    SQL*Plus: Release 10.2.0.2.0 - Production on Mon Apr 26 14:53:15 2010
    Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> archive log list;
    Database log mode No Archive Mode
    Automatic archival Disabled
    Archive destination USE_DB_RECOVERY_FILE_DEST
    Oldest online log sequence 12
    Current log sequence 14
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 125829120 bytes
    Fixed Size 1288100 bytes
    Variable Size 71305308 bytes
    Database Buffers 46137344 bytes
    Redo Buffers 7098368 bytes
    Database mounted.
    SQL> alter database archivelog;
    Database altered.
    SQL> alter databaseop;
    alter databaseop
    ERROR at line 1:
    ORA-00940: invalid ALTER command
    SQL> alter database open;
    Database altered.
    SQL> exit
    Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Pr
    oduction
    With the Partitioning, OLAP and Data Mining options
    C:\Documents and Settings\comp>rman target sys/sm
    Recovery Manager: Release 10.2.0.2.0 - Production on Mon Apr 26 14:55:58 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: W (DBID=754336873)
    RMAN> backup database;
    Starting backup at 26-APR-10
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=144 devtype=DISK
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00001 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSTEM01.DBF
    input datafile fno=00003 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSAUX01.DBF
    input datafile fno=00005 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\EXAMPLE01.DBF
    input datafile fno=00002 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\UNDOTBS01.DBF
    input datafile fno=00004 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\USERS01.DBF
    channel ORA_DISK_1: starting piece 1 at 26-APR-10
    channel ORA_DISK_1: finished piece 1 at 26-APR-10
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\2010_04_26
    \O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP tag=TAG20100426T145611 comment=NON
    E
    channel ORA_DISK_1: backup set complete, elapsed time: 00:01:34
    channel ORA_DISK_1: starting full datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    including current control file in backupset
    including current SPFILE in backupset
    channel ORA_DISK_1: starting piece 1 at 26-APR-10
    channel ORA_DISK_1: finished piece 1 at 26-APR-10
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\2010_04_26
    \O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP tag=TAG20100426T145611 comment=NON
    E
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:05
    Finished backup at 26-APR-10
    RMAN> crossckeck backupset;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "identifier": expecting one of: "allocate, alter
    , backup, beginline, blockrecover, catalog, change, connect, copy, convert, crea
    te, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flas
    hback, host, {, library, list, mount, open, print, quit, recover, register, rele
    ase, replace, report, renormalize, reset, restore, resync, rman, run, rpctest, s
    et, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport
    , upgrade, unregister, validate"
    RMAN-01008: the bad identifier was: crossckeck
    RMAN-01007: at line 1 column 1 file: standard input
    RMAN> crosscheck backupset;
    using channel ORA_DISK_1
    crosschecked backup piece: found to be 'EXPIRED'
    backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
    0_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP recid=1 stamp=717346573
    crosschecked backup piece: found to be 'EXPIRED'
    backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
    0_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP recid=2 stamp=717346669
    Crosschecked 2 objects
    RMAN> delete expired backupset
    2> ;
    using channel ORA_DISK_1
    List of Backup Pieces
    BP Key BS Key Pc# Cp# Status Device Type Piece Name
    1 1 1 1 EXPIRED DISK D:\ORACLE\PRODUCT\10.2.0\FLASH_R
    ECOVERY_AREA\W\BACKUPSET\2010_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
    2 2 1 1 EXPIRED DISK D:\ORACLE\PRODUCT\10.2.0\FLASH_R
    ECOVERY_AREA\W\BACKUPSET\2010_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
    Do you really want to delete the above objects (enter YES or NO)? y
    deleted backup piece
    backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
    0_04_26\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP recid=1 stamp=717346573
    deleted backup piece
    backup piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\W\BACKUPSET\201
    0_04_26\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP recid=2 stamp=717346669
    Deleted 2 EXPIRED objects
    now i copy all backup to c:\db
    then
    RMAN> catalog start with 'c:\db';
    searching for all files that match the pattern c:\db
    List of Files Unknown to the Database
    =====================================
    File Name: C:\db\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
    File Name: C:\db\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
    Do you really want to catalog the above files (enter YES or NO)? y
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: C:\db\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
    File Name: C:\db\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
    RMAN> list backupset;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    1 Full 592.76M DISK 00:01:26 26-APR-10
    BP Key: 4 Status: AVAILABLE Compressed: NO Tag: TAG20100426T145611
    Piece Name: C:\DB\O1_MF_NNNDF_TAG20100426T145611_5XBRSX1M_.BKP
    List of Datafiles in backup set 1
    File LV Type Ckp SCN Ckp Time Name
    1 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSTEM01.
    DBF
    2 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\UNDOTBS01
    .DBF
    3 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\SYSAUX01.
    DBF
    4 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\USERS01.D
    BF
    5 Full 947689 26-APR-10 D:\ORACLE\PRODUCT\10.2.0\ORADATA\W\EXAMPLE01
    .DBF
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    2 Full 6.80M DISK 00:00:04 26-APR-10
    BP Key: 3 Status: AVAILABLE Compressed: NO Tag: TAG20100426T145611
    Piece Name: C:\DB\O1_MF_NCSNF_TAG20100426T145611_5XBRWXG2_.BKP
    Control File Included: Ckp SCN: 947720 Ckp time: 26-APR-10
    SPFILE Included: Modification time: 26-APR-10
    RMAN>

  • Archivelog files and Rman backup

    Hi all,
    Please somebody guide me regarding the following concept.
    We have the oracle server version 10.2.0.1.0, working with Windows OS,
    I had set the parameter log_archive_dest_1 for locating archivelog files, then I had changed the archivelog files to the flash recovery area(located in another disk) by using the parameters db_recovery_file_dest_size and db_recovery_file_dest.
    Now the archivelog files are being located at two different location. At this point, If I take backup for archivelog files with the aid of RMAN, then ,
    How will the RMAN take backup from those two different locations?
    Thanks&Regards,
    Jai.

    PROBLEM :
    I have archivelogs duplexed - when running RMAN - rman backups up the archivelogs from both duplexed destinations - from the user manual - this should not be the case, any ideas?
    Details:
    I have archivelogs duplexed
    I have the following set in rman :
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
    CONFIGURE BACKUP OPTIMIZATION ON;
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/rman/WPPMD/control_%F';
    CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 10 BACKUP TYPE TO 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 DEVICE TYPE DISK FORMAT '/backup/rman/WPPMD/backup_%d_%T_%U' MAXPIECESIZE 10 G;
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'LOW' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
    CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_WPPMD.f'; # default
    When I run backups via a script :
    backup incremental level=$RMAN_LEVEL database plus archivelog;
    ($RMAN_LEVEL changes between 0 and 1 depending on the day of the week)
    It backs both duplex copies of the same archivelog
    From the document :
    Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) [ID 360416.1]
    It says :
    Even if your redo logs are being archived to multiple destinations and you use RMAN to back up archived redo logs,
    RMAN selects only one copy of the archived redo log file to include in the backup set. (Since logs with the same log sequence number are identical, there is no need to include more than one copy.)
    But this is not the case ie
    RMAN> list archivelog sequence 2445;
    using target database control file instead of recovery catalog
    List of Archived Log Copies for database with db_unique_name WPPMD
    =====================================================================
    Key Thrd Seq S Low Time
    4640 1 2445 A 17-DEC-10
    Name: /log/recovery_area/WPPMD/archivelog2/1_2445_735315419.dbf
    4639 1 2445 A 17-DEC-10
    Name: /log/recovery_area/WPPMD/archivelog/2010_12_17/o1_mf_1_2445_6jpx9n7c_.arc
    So it still backing up both copies of the archive log.
    Any ideas? is this a bug?
    Thanks
    Luca
    Edited by: user4599449 on 17-Dec-2010 07:05
    Edited by: user4599449 on 17-Dec-2010 07:06

Maybe you are looking for