RMAN CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET;

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

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

Similar Messages

  • Step by Step RMAN configuration for full hot backup daily

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

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

  • OSB / RMAN configuration for recovery area backup

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

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

  • RMAN-06466: error parsing configuration string (CONFIGURE DEVICE TYPE DISK

    Hi All
    Windows 2003 and 10.2.0.4
    I get the following message when executing show all; connected to rman
    (I have used grid control 11g for the first configuration of rman. Not sure if it has an impact.)
    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 OFF;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of show command at 09/22/2011 16:04:11
    RMAN-12010: automatic channel allocation initialization failed
    RMAN-06466: error parsing configuration string (CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;)
    RMAN-01005: syntax error: found "backup": expecting one of: "clear, parallelism"
    RMAN-01007: at line 1 column 28 file: Configuration Row
    RMAN>
    Reading the manual Database Backup and Recovery Basics
    I should be able to configure it like this
    RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "backup": expecting one of: ";"
    RMAN-01007: at line 1 column 42 file: standard input
    Anyone that can help me with this ?
    Appreciate your feedback.
    Thanks
    Magnus

    What happens if you type "CONFIGURE DEVICE TYPE DISK CLEAR;" ?

  • 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.

  • Does RMAN in 10g Enterprise Have Backup with *Compression* ?

    hi RMNA experts,
    I use the Enterprise edition of 10g. Using RMAN for database backups.
    Can you request compression in an RMAN backup - to get a smaller backup file?
    Thanks, John

    Yes you can. Here is the script.
    run {
    allocate channel ch1 device type disk;
    backup as compressed backupset incremental level 0 format '/u03/rman_backup/RMAN_DBF_TST<%s:%t:%p>.bkp' database;
    sql 'alter system archive log current';
    backup as compressed backupset format '/u03/rman_backup/RMAN_ARCH_TST<%s:%t:%p>.bkp' archivelog all delete input;
    backup as compressed backupset format '/u03/rman_backup/RMAN_CTL_TST<%s:%t:%p>.bkp' current controlfile;
    Regards
    Asif Kabir

  • CONFIGURE CHANNEL DEVICE TYPE DISK  doesn't function

    Dear all,
    I have a problem with a backup.
    Facts:
    OS: SunOS hod 5.10 Generic_142901-03 i86pc i386 i86pc
    Oracle 11.2.0.1 with RAC
    So, Although i put in rman parameters section the CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rman/backups/%U'; the backup was done but in FRA that is located in
    BS Key  Type LV   Size       Device Type  Elapsed Time  Completion Time
    36 Incr 0 210.82G DISK 10:32:57 24-JAN-13
    BP Key: 36 Status: AVAILABLE Compressed: YES Tag: TAG20130123T210005
    *Piece Name: +DATA/db_name/backupset/2013_01_23/nnndn0_tag20130123t210005_0.442.805496407*
    List of Datafiles in backup set 36...
    ANd my question is:
    How, although i configure that the backups would be in /rman/backups/%U this was located in +DATA (fRA) ??
    what im doing wrong ??
    Thanks for your help.

    thanks for your answer: here is my rman script. We invoked the script like this: rman_db_script.sh SID 0
    #!/bin/ksh
    function email_dba
    if [ -s $email_file ]
    then
    subj="$prog: FAILED on $sid@$box at `date`"
    while read dba_id
    do
    mailx -s "$subj" $dba_id < $email_file
    echo "mailx -s "$subj" $dba_id "
    done < /oracle/app/oracle/dba/util/motifylist.txt
    fi
    # set and check
    function set_and_check
    ps -ef | grep ora_pmon_$sid | grep -v grep > /dev/null
    rc=$?
    if [ $rc != 0 ]
    then
    echo "$prog: database $ORACLE_SID is not online" >> $log_file
    echo "$prog: database $ORACLE_SID is not online" >> $email_file
    # email_dba
    exit 1
    fi
    rtime=`date '+%Y%m%d_%H%M'`
    ORACLE_BASE=/opt/app/oracle
    ORACLE_HOME=/opt/app/oracle/product/11.2.0/dbhome_1
    export ORACLE_HOME
    PATH=$ORACLE_HOME/bin:$PATH
    export PATH
    logdir=/opt/oracle/logs
    log_file=$logdir/$prog.$sid.level${bk_level}.log.$rtime
    email_file="$logdir/$prog.email.$sid"
    cat /dev/null > $email_file
    box=`hostname`
    orauser=oracle
    bk_dir=/rman/backups/$sid
    echo "===== `date '+%Y%m%d %H:%M:%S'` $prog: Started =====" > $log_file
    backup_type="INCREMENTAL LEVEL $bk_level"
    # find $logdir -name $prog.*.log.* -type f -mtime +10 -exec /bin/rm -f {} \;
    # find $bk_dir -name ctl.* -type f -mtime +10 -exec /bin/rm -f {} \;
    echo "ORACLE_SID=$ORACLE_SID" >> $log_file
    echo "ORACLE_USER=$orauser" >> $log_file
    echo "ORACLE_HOME=$ORACLE_HOME" >> $log_file
    echo "BACKUP TYPE=$backup_type" >> $log_file
    return
    # backup database and archive logs to disk
    function backup_dbs_to_disk
    echo "===== Backup $sid to FRA Started At `date` =====" >> $log_file
    $ORACLE_HOME/bin/rman nocatalog << rman_cmd >> $log_file 2>&1
    connect target
         # se haran en el directorio sgte no en el FRA
         CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rman/backups/%U';
    #CONFIGURE CONTROLFILE AUTOBACKUP ON;
    run
    ALLOCATE CHANNEL ch1 TYPE disk ;
    BACKUP $backup_type
    filesperset 10
    DATABASE;
    sql 'alter system archive log current';
    BACKUP filesperset 10 ARCHIVELOG ALL DELETE ALL INPUT;
    sql "alter database backup controlfile to trace as ''$bk_dir/ctl.trc.$rtime''";
    sql "alter database backup controlfile to ''$bk_dir/ctl.$rtime'' reuse";
    RELEASE CHANNEL ch1;
    #CONFIGURE CONTROLFILE AUTOBACKUP OFF;
    rman_cmd
    rc=$?
    if [ $rc != 0 ]
    then
    echo "Backup $sid to Disk Failed At `date`" >> $log_file
    echo "Backup $sid to Disk Failed At `date`" >> $email_file
    email_dba
    exit 1
    else
    echo "===== Backup $sid to Disk Completed At `date` =====" >> $log_file
    fi
    return
    # delete obsolete backups
    function del_obsolete_bk
    echo "===== Delete Obsolete Backups Started At `date` =====" >> $log_file
    $ORACLE_HOME/bin/rman nocatalog << rman_cmd >> $log_file 2>&1
    connect target
    ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;
    Report obsolete;
    delete force noprompt obsolete;
    rman_cmd
    rc=$?
    if [ $rc != 0 ]
    then
    echo "Delete Obsolete Backups Failed At `date`" >> $log_file
    echo "Delete Obsolete Backups Failed At `date`" >> $email_file
    email_dba
    exit 1
    else
    echo "===== Delete Obsolete Backups Completed At `date` =====" >> $log_file
    fi
    return
    # main program
    if [ $# -ne 2 ]
    then
    clear
    echo "\nIncorrect argument, ORACLE_SID Backup_Level needed\n"
    echo "\nUsage: $0 ORACLE_SID BACKUP_LEVEL(0/1)\n"
    return 1
    fi
    sid=$1
    bk_level=$2
    diff_cum=$3
    # prog=`basename $0`
    prog=rman_backup_dbs.sh
    export debug='N'
    if [[ $debug = 'Y' ]];then set -x;fi
    unset ORACLE_SID
    unset ORACLE_HOME
    unset SQLPATH
    ORACLE_SID=$sid
    export ORACLE_SID
    set_and_check
    backup_dbs_to_disk
    del_obsolete_bk
    echo "===== `date '+%Y%m%d %H:%M:%S'` $prog: Completed =====" >> $log_file
    subj="$sid@$box backup completed successfully at `date`"
    # while read dba_id
    # do
    # mailx -s "$subj" $dba_id < $log_file
    # done < /oracle/app/oracle/dba/util/backup/scripts/email_dba.list
    return 0
    # end program
    #############################################################################

  • Rman bis new hard disk ( with my email )

    bjr
    Je fais une sauvegarde par rman comme ci dessus
    ceci est un test en cas du crach du serveur
    Bck_full.bat ( fichier bat)
    rman target internal/0490@act nocatalog cmdfile d:\Essai_Rman\RmanBckFull.rcv
    pause
    RmanBckFull.rcv
    run {
    allocate channel d1 type disk;
    backup
    full
    skip inaccessible
    tag b_db_full
    filesperset 6
    format 'd:\Essai_Rman\Bck_full_%t_s%s_p%p'
    (database);
    release channel d1;
    2 fichiers se sont crees , je les sauvegarde dans un endroit sur avec les fichiers
    arcs
    je remets un nouveau disque dur
    - installation oracle8i
    - creation tables users grants ok
    je copie les arcs dernierement sauvegardes
    je lance la restauration rman comme ci dessous
    Rec_Full.bat
    rman target internal/0490@act nocatalog cmdfile d:\Essai_Rman\RmanRecFull.rcv
    pause
    RmanRecFull.rcv
    run {
    allocate channel d1 type disk;
    recover database;
    release channel d1;
    Mon Analyse est t'elle correcte ????
    Quelles precautions supplementaires doit je prendre ?
    Doit je sauvegarder aussi les redo logs et les control files ??
    merci
    mail is [email protected]

    Cyberpundit wrote:
    Why is it not available "in the other direction"? What is Apple trying to achieve, or limit? Looks like this requirement is one that MANY PEOPLE face.
    Long standing design of iTunes, presumably to prevent people casually swapping media with each other and keep the record companies on board.
    I do not have any backup of my old library etc. Because all the stuff is on my iPhone. Why do I need a separate backup?
    I guessed. Because as you've just found out extracting your media & other data from your iPhone is a non-trivial task.
    Could you please recommend an external software program then that will allow me to:
    1. Extract all my items -- all apps, all music, all the books etc within iBooks, etc.
    2. Then when iTunes has "freshly synced" this new iPhone and thereby erased everything because this is what Apple thinks is "good functionality", the said app should pull all the stuff back into iPhone.
    PLease tell me there's a software (paid or free) that does this? 
    Suggested software listed in the user tip. I don't have a personal recommendation. It isn't quite as simple as buying the software and pushing one button. iTunes can extract all your iTunes purchased content, 3rd party tools for anything else. You need to work through the steps given to get your device to see the new library as the "home" computer and to preserve contacts, calendar info. and application data.
    tt2

  • CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT

    Hello everyone.
    The version I am using oracle 11g
    2 questions:
    1 .- CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ ora_backup / backupset /% F'; I get error
    I want the backup to show the date format, as it can get.
    2 .- CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ ora_backup / backupset /% F_.bak';
    rename the extension back to. Bak, one can view the SQL SERVER.
    Thanks,Bye.
    Edited by: rafelbunyol on 04-feb-2009 5:17
    Edited by: rafelbunyol on 04-feb-2009 5:19

    Hi,
    Probably you were not connected.
    Try:
    connect target /;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ora_backup/backupset/%F';
    My output on the last command:
    new RMAN configuration parameters:
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ora_backup/backupset/%F';
    new RMAN configuration parameters are successfully stored
    Regards,
    Tycho

  • CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT =SHOW DATE

    Hello everyone.
    The version I am using oracle 11g
    2 questions:
    1 .- CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ ora_backup / backupset /% F'; I get error
    I want the backup to show the date format, as it can get.
    2 .- CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ ora_backup / backupset /% F_.bak';
    rename the extension back to. Bak, one can view the SQL SERVER.
    Thanks,Bye.

    %F is only vaild for controlfile autobackups, there are other elements to store the date:
    http://download.oracle.com/docs/cd/B28359_01/backup.111/b28273/rcmsubcl010.htm#i82206
    Werner

  • ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK

    Why does the command
    "ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK;"
    work when running RMAN interactively and not from a script??
    The error I get in the script is...
    18>      ALLOCATE CHANNEL FOR
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01005: syntax error: found "for": expecting one of: "channel_id, double-quoted-string, identifier, single-quoted-string"
    RMAN-01007: at line 18 column 18 file: D:\oracle\ora92\hpcs\Rman_DeleteObsolete.rman
    How can I delete these obsolete backups from the script?

    FIXED IT.
    The ALLOCATE CHANNEL FOR MAINTENANCE DEVICE TYPE DISK command had to be outside of the RMAN RUN BLOCK.
    All works 100% now.

  • FRA changed but incremental RMAN disk backup failed

    This is a 11.1 test database.
    There was a daily FRA RMAN backup scheduled from database control. Because of the filesystem space pressure we changed FRA destination to a new filesystem and removed old FRA directories.
    But this time RMAN failed because it is trying to access the old files as base. How can I force RMAN to make a new base for daily incremental backup and not loose the already scheduled backup.
    Thank you.
    Connected to Oracle Database 11g Enterprise Edition Release 11.1.0.6.0
    Connected as ODS
    SQL> SELECT output FROM v$rman_output ORDER BY recid;
    OUTPUT
    connected to target database: OWB11 (DBID=373788874, not open)
    using target database control file instead of recovery catalog
    echo set on
    run {
    allocate channel oem_disk_backup device type disk;
    recover
    allocated channel: oem_disk_backup
    channel oem_disk_backup: SID=688 device type=DISK
    Starting recover at 12-JUL-08 02:01:13
    no copy of datafile 5 found to recover
    no copy of datafile 7 found to recover
    no copy of datafile 8 found to recover
    channel oem_disk_backup: starting incremental datafile backup set restore
    channel oem_disk_backup: specifying datafile copies to recover
    recovering datafile copy file number=00003 name=/dwh0/app/oracle/product/flash_r
    channel oem_disk_backup: reading from backup piece /ods01/owb11/flash_recovery_a
    OUTPUT
    released channel: oem_disk_backup
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 07/12/2008 02:01:14
    ORA-19870: error while restoring backup piece /ods01/owb11/flash_recovery_area/O
    ORA-19625: error identifying file /dwh0/app/oracle/product/flash_recovery_area/O
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    exit;
    36 rows selected
    SQL>

    assuming you are using the Oracle provided backup procedure (you are pretty scarce on details) you need to make sure you don't have any backups (crosscheck backup and delete expired backup comes to mind), and run the procedure again. It will make a new level 0 backup and incrementals on the following days.
    Please note if you don't use RMAN to clean up your O/S you will always ruin the RMAN catalog!!!
    Sybrand Bakker
    Senior Oracle DBA

  • Output Device LOCL is not type PDF1

    Hi
    I can see the payment specifications waiting to be sent in SOST. But I am getting the error message (below) when I try to print them off. I cannot print. I need to be able to print out the payment specifications by batch. these payment specifications are in .pdf format
    Output device Output Device LOCL is not type PDF1
    Message no. TD429
    Diagnosis
    You have selected an output device that does not have device type specified.
    System Response
    The system will not accept this output device.
    Procedure
    Please enter an output device of the proper device type. The possible values pushbutton allows you to display a list of devices you can enter here.
    Please help me,
    Al Mamun

    Hi,
    check this link:
    http://help.sap.com/saphelp_nw04/helpdata/EN/38/5bc3f2e4bd11d18e2b0000e83dd9fc/content.htm
    and configure LOCL printer in tcode SPAD correctly.

  • Performance statistics on disk to disk backup (Rman) on OEL v4.5

    We just migrated from AIX running Power processor to Oracle Enterprise Linux v4.5 running on IBM xSeries 3850 M2 (Intel Xeon Quad Core). The RMAN backups are taking twice as long as on AIX (it was taking 3.5 hours and now it is taking 7 hours) to landing space (disk to disk backup). Does anyone have any suggestion how to narrow down the different?

    This is a very complicated issue to handle in this forum. This could be anything from an RDBMS setup issue to a host configuration issue to a SAN or network issue. "Slow performance" just isn't specific enough to go into here.
    If you can, I recommend that you open a trouble ticket with Oracle (http://metalink.oracle.com).
    Or, search the Knowledge Base at that same web site.
    Other folk here may be able to help, though.

  • What type of backup DPM takes in recovery point volume

    Hi,
    Please help me to understand what type of backup DPM takes in recovery point volume as it takes more disk space as compare to replica point volume, though replica point volume is initial full copy of data source and why it takes more disk space.
    Thanks in advance.

    Thanks for valuable inputs.
    But I have still doubt on my understanding i.e.
    I have calculated disk space required as per Microsoft formulas given on above mentioned link. Below table is there output.
    Application
    Data   Size
    Retention   Range in Days
    Replica   Volume
    Recovery   Point Volume
    Total   Volume
    Exchange   Mailbox
    700   GB
    7
    906   GB
    1962   GB
    2868   GB
    SQL   Database
    100   GB
    7
    125   GB
    107   GB
    232   GB
    File   & Folders
    500   GB
    7
    750   GB
    72   GB
    822   GB
    Virtual   Machines
    700   GB
    7
    1050   GB
    100   GB
    1150   GB
    So as we are considering during sync frequency DPM transfers changed data to recovery point volume plus volume shadow copy of replica during each express full for 7 days (as per above table) then how/why required disk space for recovery point volume is less
    as compare to replica point volume for SQL, File, VM apps?
    Please help me to understand.
    Does anyone else have an idea regarding the formulas given by MS to calculate required disk space?
    Please help.

Maybe you are looking for