RMAN backup Compression algorithms?

Hi Experts,

Please help me, I'm a little confused here.

1. which algorithm of Compression in RMAN needs license of Advanced Compression in the list below?

  • BASIC
  • LOW
  • MEDIUM
  • HIGH

2. I'm under the impression that you don't need Advanced Compression license if you use BASIC ALGORITHM of COMPRESSION, but I could be wrong please advise.

Kind regards

ZKM

Basic compression is not license required...

http://docs.Oracle.com/database/121/BRADV/rcmconfa.htm#CHDEHCEB

Supported Compression levels

Oracle database provides two types of compression algorithms: a default compression algorithm and a group of algorithms of compression available with Oracle Advanced Compression option. The default algorithm is a standard Oracle database feature, while Oracle Advanced Compression option is sold separately.

Default compression

You can configure the default compression algorithm, which does not require Oracle Advanced Compression option.

Tags: Database

Similar Questions

  • cannot set RMAN compression algorithm

    Hi guys...

    I use the oracle 11g on OEL5 11.2.0.0.0 compatible parameter database

    When I use the following command in the RMAN, it gives an error as shown below.

    RMAN > set up the "bzip" compression algorithm

    using the control file of the target instead of recovery catalog database
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the command configure at 2010-10-16 15:24:42
    RMAN-06806: compression algorithm "bzip" of output by DEFAULT not found

    help please...

    vishnusivathej wrote:
    Hi guys...

    I use the oracle 11g on OEL5 11.2.0.0.0 compatible parameter database

    When I use the following command in the RMAN, it gives an error as shown below.

    RMAN > set up the "bzip" compression algorithm

    using the control file of the target instead of recovery catalog database
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the command configure at 2010-10-16 15:24:42
    RMAN-06806: compression algorithm "bzip" of output by DEFAULT not found

    help please...

    Click on the following link:
    http://kkempf.WordPress.com/2009/09/09/11gr2-RMAN-you-are-too-dumb-to-pick-a-compression-algorithm/

    Kamran Agayev a.
    Oracle ACE
    - - - - - - - - - - - - - - - - - - - - -
    My video tutorials of Oracle - http://kamranagayev.wordpress.com/oracle-video-tutorials/

  • RMAN backup space free after compression subpartition

    Hello!

    I have a strange situation. I have a table with partitions of range and 8 subpartitions. I compressed subpartitions according to this trick:
    [http://husnusensoy.wordpress.com/2008/01/23/compressing-subpartition-segments/]
    with excellent results. I released half of the disk space. But written rman still the same number of bytes to bands. Can someone explain why?

    My Oracle is company 10.2.0.4@itanium with HP - UX 11.23.

    Thans in advance.

    Table structure:
    CREATE TABLE tab
(
  STREAM_ID                     NUMBER(38)      NOT NULL,
  STREAMROW                     NUMBER(38)      NOT NULL,
  EVENTBEGINDATE                DATE
  [...]
)
TABLESPACE DATA
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
LOGGING
PARTITION BY RANGE (EVENTBEGINDATE)
SUBPARTITION BY HASH (STREAM_ID, STREAMROW)
(  
  PARTITION P_MIN VALUES LESS THAN (TO_DATE(' 2006-11-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    NOLOGGING
    COMPRESS
    TABLESPACE TYTAN_UDATA
    PCTFREE    0
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                BUFFER_POOL      DEFAULT
               )
    SUBPARTITIONS 8 STORE IN (DATA,DATA,UDATA,DATA,DATA,DATA,DATA,DATA),  
  PARTITION P_2006_11_01 VALUES LESS THAN (TO_DATE(' 2006-11-02 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
    NOLOGGING
    COMPRESS
    TABLESPACE DATA
    PCTFREE    0
    INITRANS   1
    MAXTRANS   255
    STORAGE    (
                BUFFER_POOL      DEFAULT
               )
[...]

    It is a documented feature. Only unused blocks of RMAN backups if:

    -you are backing up to disk (NOT) - or
    -blocks were never used by any measure

    See here for more details: http://oradbatips.blogspot.com/2010/02/tip-86-what-it-is-missed-when-rman.html

    --
    Ronny Egner
    My Blog: http://blog.ronnyegner-consulting.de

    Published by: Ronny Egner on June 16, 2010 16:07

  • The user managed based backup Rman backup cold cold vs

    Hi all

    I just want to know the advantages and disadvantages for backup managed user cold and cold backup Rman.

    What is the best cold backup?

    Some some can help me?

    Thank you

    Cedric Joshi

    Hello

    Both are good only... If you took the clod backup (managed by the user), you can also do with RMAN catalog.

    I feel clod RMAN backup is good.

    Reason:

    ======

    ++ with RMAN you can avoid used used block, you can only backup used blocks

    ++ RMAN has its own compression algorithm

    ++ We also have the ability to assign multiple channels to parallelize the backup

  • RMAN backup runs twice (sequential) even if it is not configured in this way

    Hello

    I started experimenting with RMAN as another way for backup (currently we use backup with storage). I'm running a few tests every day to check the overhead and time there and also check the storage space needed for our system.

    At first, everything seems fine, I tested a few default options and then started to configure the RMAN suite better our needs.

    The problem:

    During my recent tests found that RMAN's backup of my database twice, but I could not find out where I configure it to run this way.

    I even put a basic Vanilla with the same features, but it produces a single backup set.

    I enclose my test RMAN environment configuration, and I hope that someone will be able to indicate where I configured RMAN to do 2 sets of backup.

    RMAN > show all.

    Db_unique_name MSCA RMAN database configuration settings are:

    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default

    CONFIGURE BACKUP OPTIMIZATION # by default

    SET UP DEFAULT DISK DEVICE TYPE; # by default

    CONFIGURE CONTROLFILE AUTOBACKUP ON;

    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default

    SET UP THE DEVICE TYPE DISK BACKUP FOR PARALLELISM BACKUPSET TABLET 1 TYPE;

    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default

    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default

    CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT ' / oracle/MSCA/db/rman_bkup/MSCA/df_%d_%T_%U.rmn' MAXPIECESIZE 10 G;

    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default

    CONFIGURE ENCRYPTION OF DATABASE # by default

    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default

    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default

    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default

    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / oracle/MSCA/db/rman_bkup/msca_dbs/snapcf_MSCA.f';

    Here is the result of the end of the backup set 1. You can see it took 2 hours, then immediately, he began another work of backup (highlighted in RED)

    channel ORA_DISK_1: finished piece 5 to 02 - OCT-14

    piece handle=/oracle/MSCA/db/rman_bkup/MSCA/df_MSCA_20140902_09phg6h0_5_1.rmn tag = TAG20140902T115927 comment = NONE

    channel ORA_DISK_1: full game backup, duration: 02:05:08

    channel ORA_DISK_1: from complete compressed datafile backup set

    channel ORA_DISK_1: specifying datafile (s) in the backup set

    Thank you

    Saar

    You present, evidence that it is '2 backups of a database'.  I see two backupsets, each with a different set of data files in your ad.  If the backup is spanning two backupsets - you probably more than 64 files of data.

    Hemant K Collette

  • Hot RMAN backup fails every time in R12.

    Hi experts,

    Please suggest me that I have to plan rman backup hot. I have "write" command to perform hot backup. When I take backup hot of 1st time the backup completed successfully. but when I run the same command resume backup for the second day. it is impossible to give space issue I havhot e calendar for daily use rman backup.

    I had to take the backup hot daily and I want backup overwrite the backup file according to the daily backup.

    Please suggest me what I need to make changes in the configuration of rman and the rman command.

    OS - réhèl 5.6

    Database - 11.1

    EBS - r12.3

    configuration of RMAN:

    RMAN > show all.

    Database with db_unique_name UAT RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / d06/UAT/rman_hot_backup/Backup_daily%d_DB_%u_%s_%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BZIP2 '; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / d06/UAT/db/tech_st/11.1.0/dbs/snapcf_UAT.f'; # by default

    RMAN >


    ##############################################################################################################


    RMAN command that I used to make hot extra strength 0 cumulative backup.


    RMAN > run
    {
    allocate channels c1 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
    allocate channel c2 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
    allocate channels c3 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
    allocate channel c4 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
    cumulative incremental database backup level 1 more archivelog;
    output channel c1;
    output channel c2.
    output channel c3.
    output channel c4.
    }

    If something bad in the configuration of rman and my order please suggest me to take the backup hot every day with success.


    concerning

    pritesh Rodriguez

    Hi Pritesh, thanks for the update. You can mark this thread as answered if your questions have been answered. cordially Karan

  • RMAN: Backups not exipring after the window of redundancy.

    Hello

    I meet backup sbt_tape and the use of the slot block:

    run{
ALLOCATE CHANNEL C1 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C2 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C3 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
ALLOCATE CHANNEL C4 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
backup incremental level 0 database filesperset=1 format '%d_L0_DF%f_%T_%u.dbf' tag 'DB_L0_DF_#_DT_UNQNO';
backup current controlfile format '%d_L0_CF_%T_%u.ctl' tag 'DB_L0_CF_DT_UNQNO';
backup incremental level 0 archivelog all filesperset=1 format '%d_L0_AL_%h_%e_%T_%u.arc' tag 'DB_L0_ARC#_DT_UNQNO';
crosscheck backup of database;
crosscheck backup of archivelog all;
delete noprompt expired backup of database;
delete noprompt expired backup of archivelog all;
}

    My backups work perfectly, but for some reason, my backups expire even though my redudancy is set to 7 days.

    In my dest backup, I have backups as old as March 13, which should have been expired since a long time back.

    Any ideas what could be wrong?

    RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name IWTPR are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP OFF;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so, ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/IWTPR/snapcf_IWTPR.f';
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/iwtpr/snapcf_iwtpr.f';

    Thanks in advance,

    aBBy.

    Details of env: RAC 4 node cluster running 11.2.0.3.4 GI/RDBMS on RHEL 5. 6

    AB007 wrote:

    Hello

    I meet backup sbt_tape and the use of the slot block:

    1. Run {}
    2. ALLOCATE CHANNELS C1 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
    3. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
    4. ALLOCATE channel C2 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
    5. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
    6. ALLOCATE CHANNELS C3 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
    7. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
    8. ALLOCATE CHANNELS C4 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
    9. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
    10. filesperset database backup incremental level 0 = 1 format '% d_L0_DF%f_%T_%u.dbf' tag "DB_L0_DF_ #_DT_UNQNO";
    11. backup current controlfile '% d_L0_CF_%T_%u.ctl' format tag "DB_L0_CF_DT_UNQNO".
    12. incremental backup of level 0 archivelog all filesperset = 1 format '% d_L0_AL_%h_%e_%T_%u.arc' tag "DB_L0_ARC #_DT_UNQNO";
    13. cross-checking of backup of database;
    14. backup duplication of the archivelog all;
    15. delete noprompt expired backup of database;
    16. delete expired backup noprompt to archivelog all;
    17. }

    My backups work perfectly, but for some reason, my backups expire even though my redudancy is set to 7 days.

    In my dest backup, I have backups as old as March 13, which should have been expired since a long time back.

    Any ideas what could be wrong?

    1. RMAN > show all.
    2. using the control file of the target instead of recovery catalog database
    3. RMAN settings for database with db_unique_name IWTPR are:
    4. CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
    5. CONFIGURE BACKUP OPTIMIZATION
    6. CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';
    7. CONFIGURE CONTROLFILE AUTOBACKUP
    8. CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    9. CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO "%F" # by default
    10. SET UP THE DEVICE TYPE DISK PARALLELISM 4 TYPE OF BACKUP TO COMPRESSED BACKUPSET;
    11. SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.
    12. CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
    13. CONFIGURE BACKUP COPIES OF DATA FILE FOR THE 'SBT_TAPE' UNIT 1;
    14. CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
    15. CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE 'SBT_TAPE' 1;
    16. CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so, ENV is (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
    17. CONFIGURE MAXSETSIZE TO UNLIMITED;
    18. CONFIGURE THE DATABASE ENCRYPTION
    19. CONFIGURE THE ENCRYPTION ALGORITHM "AES128";
    20. CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD;
    21. CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;
    22. CONFIGURE the SNAPSHOT CONTROLFILE NAME to "+ IWTPRFRA/IWTPR/snapcf_IWTPR.f";
    23. CONFIGURE the SNAPSHOT CONTROLFILE NAME to "+ IWTPRFRA/iwtpr/snapcf_iwtpr.f";

    Thanks in advance,

    aBBy.

    Details of env: RAC 4 node cluster running 11.2.0.3.4 GI/RDBMS on RHEL 5. 6

    You are confusing "expired" with "obsolete".

    When a backupset is created, an account of which is placed in the control file.

    If you backup ' overlap ', rman checks these records against reaility.  If no backup turns out have disappeared, his file is marked as "expired".  That follow-up with a 'delete expired backup', and missing backups (expired) records will be deleted from the repository.

    What you want is "delete obsolete.  Which will remove any backup that is no longer necessary to enforce the retention period.

    BTW, "redundancy" and "x days" are mutually exclusive.

  • RMAN backup recovery point in time

    Hi all

    Here's my rman backup script configuration and rman.
    Because of size constraints I save my logs to archive by rman and delete.
    I wanted to know if it was possible to go at a certain time using these archiving logs.
    ex: -.
    Racing script at 10:00 in the evening daily say it ran on March 1 and March 2, to 22:00, if I want to recover until 14:00 on March 2, will be March 2 backup enough or I'll need March 1 backup and archive logs until 14:00 for which I need to physcially archive backup logs daily , with rman.
    RUN
{ 
  ALLOCATE CHANNEL ch1 DEVICE TYPE DISK;
  ALLOCATE CHANNEL ch2 DEVICE TYPE DISK;
  ALLOCATE CHANNEL ch3 DEVICE TYPE DISK;
  BACKUP DATABASE INCLUDE CURRENT CONTROLFILE format 'G:\Oracle\flash_recovery_area\TEST\BACKUPSET\tmp\rman_backup\df_%d_%s_%p_%T';
  DELETE NOPROMPT OBSOLETE;
  SQL "ALTER SYSTEM ARCHIVE LOG CURRENT";
  BACKUP ARCHIVELOG ALL DELETE INPUT format 'G:\Oracle\flash_recovery_area\TEST\BACKUPSET\tmp\rman_backup\arc_%d_%s_%p_%T';

}
    RMAN configuration parameters for database with db_unique_name TEST are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
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 'G:\Oracle\flash
_recovery_area\TEST\BACKUPSET\tmp\RMAN_BACKUP\CTL_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOA
D TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\PRODUCT\11.2.0\DBHOME_1\DATABA
SE\SNCFTEST.ORA'; # default

    Hello;

    RMAN> startup mount
RMAN> restore database until time "to_date('02-MAR-2013 09:00:00', dd-mon-rrrr hh24:mi:ss')";
RMAN> recover database;
RMAN> alter database open;

    Best regards

    mseberg

  • Why are my RMAN backup files still around?

    Environment:

    Oracle 11.2.0.3 EE on Solaris 64 bit

    Good morning (at least it's morning here at the moment),

    I have a test database that I have currently configured to do an incremental backup of level 0, every morning at about 03:00.

    I also do one "archivelog backup all" every 4 hours during the day.

    My archivelog deletion policy is "saved 2 times".

    I put RMAN in place with a 8 day recovery window (ALL - see below).

    I have multiple RMAN files dated 11 days ago.

    Question: Why these files are still around?
    RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name APSMDMP2 are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 3;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE DISK MAXPIECESIZE 5 G;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT   '/rman/APSMDMP2/APSMDMP2_%T_%t_%s_%p';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO DISK;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11203/db_1/dbs/snapcf_APSMDMP2.f';
    I have several entries in V$ ARCHIVED_LOG with a BACKUP_COUNT = 1 but they are all dated to 21 days ago and have DELETED status as shown here:
     SEQUENCE# ARC APPLIED   DEL S CTIME                         BACKUP_COUNT
---------- --- --------- --- - ----------------------------- ------------
      4625 YES NO        YES D 09-oct-2012 13:21:09                     1
      4626 YES NO        YES D 09-oct-2012 13:21:48                     1
      4627 YES NO        YES D 09-oct-2012 13:22:23                     1
      4628 YES NO        YES D 09-oct-2012 13:22:50                     1
    I am able to see the content of the RMAN files, but I don't see anything that would cause them to not be removed during the RMAN runs. Here is an example of one of the files:
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ -------------------
6493    Incr 0  22.75G     DISK        01:35:54     2012-10-19:04:36:13
        BP Key: 6493   Status: AVAILABLE  Compressed: YES  Tag: FULL_DAILY
        Piece Name: /rman/APSMDMP2/APSMDMP2_20121019_797050819_6508_1
  List of Datafiles in backup set 6493
  File LV Type Ckp SCN    Ckp Time            Name
  ---- -- ---- ---------- ------------------- ----
  2    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/sysaux01.dbf
  4    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/users01.dbf
  5    0  Incr 564035766  2012-10-19:03:00:19 /u01/oradata/APSMDMP2/data_process_dt01_01.dbf
  9    0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/gmx_src_dt01_01.dbf
  10   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/gmx_src_ix01_01.dbf
  12   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/adm_data_ix01_01.dbf
  13   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/patrol01_01.dbf
  16   0  Incr 564035766  2012-10-19:03:00:19 /u07/oradata/APSMDMP2/becosp_base_data_01.dbf
  18   0  Incr 564035766  2012-10-19:03:00:19 /u07/oradata/APSMDMP2/becosp_base_data_02.dbf
  27   0  Incr 564035766  2012-10-19:03:00:19 /u06/oradata/APSMDMP2/data_process_dt01_03.dbf
  30   0  Incr 564035766  2012-10-19:03:00:19 /u05/oradata/APSMDMP2/adm_data_dt01_02.dbf
    I use the "DELETE NOPROMPT OBSOLETE' after each database and backup archivelog. Here is my command file 0 extra strength:
    backup incremental level 0 cumulative database tag 'full_db';
backup archivelog all not backed up 2 times tag 'full_arch';
DELETE NOPROMPT OBSOLETE;
    I know I can manually remove the files and everything with a resync OVERLAP but I was trying to understand why it happened in the first place.

    Any suggestions are welcome.

    Please let me know if you need more information.

    Thank you very much!!

    -gary

    Hmm

    Perhaps, I see your logic.

    I post a thread as an editing tool that explains better than any I've seen.

    Give him a look and see if the answer isn't here.

    Best regards

    mseberg

  • RAC RMAN backup

    Hello

    DB is 10.2.0.4 OS = BSG (CARS with 2 nodes BD01, db02). Here are the types of automated RMAN backups taken on db01.

    -OCR
    -Voting record
    -Talespaces Snapshot
    -Archivelog (hourly)
    -Backup incremental level 0 (SUNDAY)
    -backup incremental level 1 (Mon - Sat)
    -Automatic backup of the control file and SPFILE (CONTROLFILE AUTOBACKUP ON)

    Two big questions please. First of all, are these types of backups/backup are enough to RESTORE FULL speaking of RMAN backup on a RAC environment with 2 nodes? Otherwise please suggest what I need to backup?

    Second, home backup location is /rman that I can see on db01 ONLY. This directory of /rman that I don't see on db02. My question is what db02 failure can I restore from directory /rman? or do I need to automate the backup also schedules on db02 separately?
    [root@db01~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G  2.9G  814M  79% /
/dev/sda3             190M   34M  147M  19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G  137M  3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G  225M  3.5G   6% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G  3.7G  3.8G  50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G  379M  3.4G  11% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G  8.7G  2.6G  78% /oracle
10.10.28.140:/vol/px4cinconso
                       40G  1.4G   39G   4% /inconso_px
/dev/mapper/36001ec9000d5ea810000061349015d98
                      1.3T  551G  665G  46% /rman
    [root@db02~]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
                      3.9G  887M  2.9G  24% /
/dev/sda3             190M   34M  147M  19% /boot
tmpfs                  16G     0   16G   0% /dev/shm
/dev/mapper/VolGroup00-LogVol05
                      3.9G  137M  3.6G   4% /home
/dev/mapper/VolGroup00-LogVol03
                      3.9G  261M  3.5G   7% /tmp
/dev/mapper/VolGroup00-LogVol02
                      7.8G  3.7G  3.8G  50% /usr
/dev/mapper/VolGroup00-LogVol04
                      3.9G  355M  3.4G  10% /var
/dev/mapper/VolGroup00-ORACLE_BASE
                       12G  6.5G  4.8G  58% /oracle
10.10.28.140:/vol/px4cinconso
                       40G  1.4G   39G   4% /inconso_px
    [oracle@db01~]$ rman target /

Recovery Manager: Release 10.2.0.5.0 - Production on Fri Feb 24 11:49:59 2012

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: F1 (DBID=1245145263)

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 28 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rman/f1/fullbackup/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/10.2.0/db/dbs/snapcf_f11.f'; # default
    # Script for backup

level0 ()
run {
  allocate channel c1 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/fullbackup/$ORACLE_SID-data-%U-%t';
  allocate channel c2 type disk  maxpiecesize 2000M format '/rman/$ORACLE_SID/archive/$ORACLE_SID-arch-%U-%t';
  backup incremental level 0 tag = weeklyfull database channel c1 
  plus archivelog tag = ARCH_$TODAY delete all input channel c2;
  release channel c1;
  release channel c2;
}

run {
  allocate channel c1 type disk;
  delete noprompt obsolete;
  release channel c1;
}
    Bundle of thanks.

    Kind regards

    Published by: 910385 on February 24, 2012 03:00

    Hi 910385,
    The error on the node db02

    ORA-19504: cannot create the file ' / rman/fp1/backup/c-1245145263-20120210-11.

    is caused by your installation.
    You have a /rman of mount point visible only on the node db01.
    The controlfile autobackup setting triggers the creation of a backup of the controlfile:
    -during the rman backup (this seems to work only on db01)
    -in the case of a structural change in the database (eg. Adding a data file).
    Sessions to make a structural change can be connected to one of your two instances, but the instance on db02 cannot create controlfile autobackup in /rman.
    You must change the configuration and put the backup on a shared disk that is seen by the two systems.
    Strangely, you have a shared file system:

    10.10.28.140:/vol/px4cinconso 40G 1.4 G 39G 4% /inconso_px

    Better would be to make a second for rman...
    Kind regards
    Tycho

  • Purge the rman backup

    Hello, since the alert.log file find this error:

    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc3_25352.trc file:
    ORA-19809: limit exceeded for file recovery
    ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
    ARC3: 19809 creation error archive log file ' DATA01'+.
    Sea 25 09:51:58 Jan 2012
    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
    ORA-19815: WARNING: 59055800320 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.
    ************************************************************************
    You have choice to free up space in the recovery area:
    + 1. Consider changing the RMAN RETENTION POLICY. If you are using Data Guard +.
    then consider changing POLICY of DELETE ARCHIVELOG RMAN.
    + 2. Back up files on a tertiary device such as a tape using RMAN.
    SAFEGUARDING RECOVERY AREA command.
    + 3. Add disk space and increase the db_recovery_file_dest_size setting to +.
    reflect the new space.
    + 4. Delete unnecessary files by using the RMAN DELETE command. If operation +.
    the system control has been used to remove the files, and then use the RMAN DUPLICATION and
    Commands DELETE has EXPIRED.
    ************************************************************************
    Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
    ORA-19809: limit exceeded for file recovery
    ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
    ARC0: error creating 19809 archive log file ' DATA01'+.

    So I'm trying to purge the rman backup, but I have an error message:


    rman target = oratest@oraprdlnx1:~$ /+.
    Recovery Manager: release 11.2.0.1.0 - Production on sea Jan 25 09:47:30 2012
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: TEST (DBID = 2044700519)

    + RMAN > show all; +.

    using the control file of the target instead of recovery catalog database
    RMAN settings for database with db_unique_name TEST are:
    CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
    CONFIGURE BACKUP OPTIMIZATION # by default
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/oratest/product/11.2.0/dbhome_1/dbs/snapcf_TEST1.f'; # by default

    + RMAN > allocate channel for maintenance of type; disc +.

    allocated channel: ORA_MAINT_DISK_1
    channel ORA_MAINT_DISK_1: SID = 237 instance = type of TEST1 = DISK

    + RMAN > crosscheck backup; +.

    "" element of verified backup: turned out to be "AVAILABLE"
    backup handle piece = RECID = 68 = 758320264 STAMP DATA01/test/autobackup/2011_08_04/s_758320263.794.758320265 +.
    Cut objects 1

    RMAN > delete obsolete; ** +

    RMAN retention policy apply to the order
    RMAN retention policy is set to 1 redundancy
    Remove the following obsolete backups and copies:
    Making key time filename/handle type
    -------------------- ------ ------------------ --------------------
    Backup Set 25 July 4, 11
    Backup total 25 4 July 11 1omgk64v_1_1
    Backup Set 26 July 4, 11
    Backup total 26 July 4, 11 1pmgk650_1_1
    Backup Set 24 July 4, 11
    Total backup, 24 4 July 11 1qmgk650_1_1
    Backup Set 21 July 4, 11
    Backup total 21 4 July 11 1rmgk650_1_1
    Backup Set 28 July 4, 11
    28 1vmgk69v_1_1 July 4, 11 total backup
    Save game 29 July 4, 11
    Backup total 29 July 4, 11 20mgk6a0_1_1
    Backup Set 30 July 4, 11
    Backup total 30 4 July 11 21mgk6a0_1_1
    Save game 31 July 4, 11
    Backup total 31 July 4, 11 22mgk6a0_1_1
    Backup Set 34 4 July 11
    Backup total 34 4 July 11 c-2044700519-20110704-07
    Backup Set 35 July 4, 11
    Total backup, 35 26mgk8ib_1_1 4 July 11
    Backup Set 36 4 July 11
    Backup total 36 4 July 11 c-2044700519-20110704-08
    Backup Set 41 4 July 11
    Backup total 41 4 July 11 28mgk94i_1_1
    Backup Set 42 4 July 11
    Backup total 42 4 July 11 29mgk94j_1_1
    Backup Set 37 July 4, 11
    Backup total 37 4 July 11 2amgk94j_1_1
    Backup Set 40 July 4, 11
    Backup total 40 July 4, 11 2bmgk94j_1_1
    Backup Set 38 July 4, 11
    Backup total 38 4 July 11 2cmgk95c_1_1
    Backup Set 39 July 4, 11
    Backup total 39 4 July 11 2dmgk95k_1_1
    Backup Set 43 July 4, 11
    Backup total 43 July 4, 11 c-2044700519-20110704-09
    Backup Set 46 4 July 11
    Backup total 46 4 July 11 2fmgk99f_1_1
    Backup Set 47 July 4, 11
    Backup total 47 4 July 11 2gmgk99g_1_1
    Backup Set 44 4 July 11
    Backup total 44 4 July 11 2hmgk99g_1_1
    Backup Set 48 4 July 11
    Backup total 48 4 July 11 2imgk99g_1_1
    Backup Set 45 4 July 11
    Backup total 45 4 July 11 2jmgk9a9_1_1
    Backup Set 50 4 July 11
    Backup total 50 4 July 11 2kmgk9aq_1_1
    Backup Set 49 July 4, 11
    Backup total 49 4 July 11 2lmgk9aq_1_1
    Backup Set 51 4 July 11
    51 4 July total backup has 11 c-2044700519-20110704-0
    Backup Set 56 4 July 11
    Total backup 56 2rmgk9qb_1_1 July 4, 11
    Backup Set 55 July 4, 11
    Backup total 55 4 July 11 2smgk9qb_1_1
    Backup Set 58 4 July 11
    Backup total 58 4 July 11 b c-2044700519-20110704-0
    Backup Set 60 4 July 11
    Total backup 60 2umgk9tb_1_1 July 4, 11
    Backup Set 61 4 July 11
    Backup total 61 4 July 11 2vmgk9tc_1_1
    Backs up the entire 62 4 July 11
    Backup total 62 4 July 11 30mgk9tc_1_1
    Backup Set 66 4 July 11
    Backup total 66 4 July 11 34mgk9ua_1_1
    Backs up the entire 65 4 July 11
    Backup total 65 4 July 11 35mgk9ua_1_1
    Backup Set 67 4 July 11
    Total backup, July 4, 11 c-2044700519-20110704-0 67C
    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
    RMAN-06091: any string allocated for maintenance (of a suitable type)

    How can I purge the db dest file recovery?

    Thank you!!!

    RMAN-00571: ===========================================================
    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
    RMAN-00571: ===========================================================
    RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
    RMAN-06091: any string allocated for maintenance (of a suitable type)

    There is a metalink note that talks about this error.

    Met RMAN-03002 and RMAN-06091 when deleting obsolete backups [567555.1 ID]
    RMAN could not remove obsolete in right Backupsets change Sbt_tape to disk and again Server [ID 1287755.1]

    HTH

    Kind regards
    Nagendra Chillale

    Published by: NC on January 25, 2012 17:00

  • recover the database on windows xp linux rman backup

    Hi guys,.

    I am recovering a xp database that runs on Centos 5.3 on windows xp.

    That's what I did.
    backup database
    Run {}
    maxcorrupt for the data file the value 2 to 1;

    CONFIGURE REDUNDANCY 5 RETENTION STRATEGY;
    CONFIGURE BACKUP OPTIMIZATION
    SET UP DEFAULT DISK DEVICE TYPE; # by default
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
    SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
    CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
    CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
    CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
    CONFIGURE ENCRYPTION OF DATABASE # by default
    CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
    CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / usr/lib/oracle/xe/app/oracle/product/10.2.0/server/dbs/snapcf_XE.f'; # by default
    compressed backup backupset database;
    backup current controlfile;
    backup SPFile;
    }

    FTP files on Windows
    SQL > startup mount restrict exclusive;
    SQL > drop database;

    SQL > startup nomount;
    RMAN > set dbid = 7898909
    RMAN > recover automatic backup controlfile;

    And then the problems begin.
    because the controlfile contains the former locations of tablespaces (linux).
    I try with set newname for data file does not work because old tablespaces are not there.
    If I try to backup the controlfile to find and change the locations, it still does not because I don't have the files of data in place.

    In short; How to restore and recover the database from a backup of linux on windows?

    Hello

    Rman backups are not portable between operating system platforms.
    You must use the convert command.
    Please follow the link which explains the controls and the procedure below.
    http://download.Oracle.com/docs/CD/B19306_01/backup.102/b14191/dbxptrn.htm#CHDCFFDI

    Kind regards
    Tycho

  • RMAN backup gets already

    Hi all;

    RMAN > set the channel 1 device type disc format ' / u01/rmanbkp ";

    new RMAN configuration settings:

    CONFIGURE the CHANNEL 1 DEVICE TYPE DISK FORMAT ' / u01/rmanbkp ";

    new RMAN configuration settings are stored successfully

    output channel: ORA_DISK_1

    RMAN > list backup;

    specification does not match the backups in the repository

    RMAN > backup database tag = "NORMAL_BKP_15_jul_15";

    From 25 July 15 backup

    allocated channel: ORA_DISK_1

    channel ORA_DISK_1: SID = 20 type of device = DISK

    channel ORA_DISK_1: from complete compressed datafile backup set

    channel ORA_DISK_1: specifying datafile (s) in the backup set

    Enter a number of file datafile = 00005 name=/u03/app/oracle/oradata/crms/tbs02.dbf

    Enter a number of file datafile = 00001 name=/u02/app/oracle/oradata/crms/system01.dbf

    Enter a number of file datafile = name=/u01/crmsx4.dbf 00024

    channel ORA_DISK_1: starting piece 1 to July 25, 15

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 25/07/2015 10:30:26

    ORA-19504: cannot create the file ' / u01/rmanbkp.

    ORA-27038: created file already exists

    Additional information: 1

    There is no file physically in/u01/rmanbkp

    DB version: 11.2.0.1 on (Redaht)

    RMAN > set the channel 1 device type disc format ' / u01/rmanbkp ";


    Specify format with extension, something like below

    RMAN > set up the channel 1 device type disk format ' / u01/rmanbkp/backup%U';

    http://docs.Oracle.com/CD/B28359_01/backup.111/b28273/rcmsubcl010.htm

  • RMAN backup error

    Hello

    I get an error when you try to run an Oracle database backup using a windows batch file that calls a settings file to execute RMAN commands. This is handled by the windows scheduler.

    It's been in place for several months and worked fine until today.

    Oracle Version - 11G 11.2.0.2.0

    OS - Windows server 2008 R2

    * Note *-I have changed for security reasons password and company information.

    Here are the contents of the batch file:

    echo: [email protected] > > \\CCCODS09\c$\Support\DB_Backup\Max.log

    echo to: [email protected] > > \\CCCODS09\c$\Support\DB_Backup\Max.log

    Echo subject: Max Backup log > > \\CCCODS09\c$\Support\DB_Backup\Max.log

    RMAN @\\CCCODS09\c$\Support\DB_Backup\Max.txt > > \\CCCODS09\c$\Support\DB_Backup\Max.log

    copy \\CCCODS09\c$\Support\DB_Backup\Max.log \\ccvmds51\c$\inetpub\mailroot\Pickup\email.txt

    del \\CCCODS09\c$\Support\DB_Backup\Max.log

    Here is the content of the Max.txt settings file:

    connect sys/password@maxof target;

    Run {}

    backup as compressed backupset actual additional database tag 0 = = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-DATAFILE-%U.BKP';

    backup as compressed backupset archivelog all delete tag all input = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-LOGFILE-%U.BKP';

    backup as compressed backupset current controlfile tag = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-CONTROLFILE-%U.BKP";

    }

    "exit";

    And here is the log file:

    Recovery Manager: release 11.2.0.2.0 - Production on Mon Nov 17 05:30 2014

    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.

    RMAN > Connect target *.

    2 > run {}

    3>           = backup as compressed backupset actual additional database tag 0 = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-DATAFILE-%U.BKP';

    4>           backup as compressed backupset archivelog all delete tag all input = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-LOGFILE-%U.BKP';

    5>           as a compressed backupset backup current controlfile tag = "format='\\cccobu02\oracle\cccods09\Max\%T_Max-HOT-BACKUP-OF-FULL-DATABASE-AND-LOGS-CONTROLFILE-%U.BKP ';

    {6 >}

    7 > exit;

    connected to target database: MAX (DBID = 1234567890)

    From backup 17 November 14

    DBGSQL: TARGET > select nvl (max (al.recid), '0'), nvl (max (al.recid), 0) in : txtparmvalue,: parmvalue of al v$ archived_log where in al.status ('X', 'A') and al.is_recovery_dest_file = 'YES' and al.creator = "RMAN"

    DBGSQL: SQLCODE = 1008

    RMAN-00571: ===========================================================

    RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

    RMAN-00571: ===========================================================

    RMAN-03002: failure of the backup at 17/11/2014 05:30:16 command

    RMAN-03014: implicit recovery catalog Resync failed

    ORA-01008: not all variables

    Complete recovery manager.

    If you need more information please let me know.

    Any help to fix this would be appreciated.

    Thank you

    Hello

    This is considered to be a bug for 11.2.0.2 version.

    Please see this document of MOS

    ORA-01008: RMAN backup does not work with assorted errors 11.2.0.2 If cursor sharing is turned on (Doc ID 1472116.1)

    Kind regards

    Shivananda

  • Can RMAN backup in 2 places due to the lack of space?

    Oracle 11.2.0.4 on RHEL 6.4

    We have a DB production with RMAN backup (L0) enlarged with compression of 400 GB. We usually tape backup. But, today, I need to save this DB for the local file system.

    I don't have a single file with 400 GB of free space system. But, I

    /ora_backup with 300 GB freespace

    and

    /U04 with 150 GB freespace

    Is it possible to load RMAN instead of 300 GB of backup in the directory/ora_backup/rman pieces and the remaining items of backup to the directory/u04/rman ?

    Hello

    You can use a running script rman with two channels and write each channel on a different disk location, but be sure to choose the number of data file (size of the data file).

    RMAN > run

    {

    ALLOCATE CHANNEL c1 DEVICE TYPE DISK FORMAT ' / ora_backup/%U';

    ALLOCATE CHANNEL c2 DEVICE TYPE DISK FORMAT ' / u04/%U';

    BACKUP INCREMENTAL LEVEL = 0

    (CHANNEL DATAFILE 1,2,3,4 c1)

    (DATAFILE 5,6,7 CHANNEL c2);

    }

    In this example:

    I choose to backup datafile 1, 2, 3 and 4 on the /ora_backup directory, I choose to backup datafile 5, 6 and 7 on the /u04 directory.

    Best regards

Maybe you are looking for

  • Updating BIOS for Satellite M100-150

    May indicate the reference of BIOS for Satellite M100-150 for Windows XP download, on an official website, I can not download, the reference does not work.I use the translator so that for the quality of the translation, I don't answer. :)

  • HP Printer Wizard

    Hello where can I download "HP printer Assistant" for the printer hp deskjet 1050. I uninstalled it but now I want to use. Thank you for your time, sakina.

  • Windows 7 - Office updates fail after reboot

    I am running Windows 7 32 bit, and last night I downloaded Microsoft Office 2010 and installed (upgrade of my edition of 2007 in the process). By the time I wanted to shut down the computer that he reported that 6 updates have been downloaded and mus

  • Windows XP - HP Officejet 4500

    Original title: Help! I have a HP Officejet 4500. I can print online. However, I can't print from my PC. I get a pop up telling me that the printer is unable to print what I sent to her. I tried to go to printers & faxes, then properties, then settin

  • Samsung j3: service plugin

    I just tried the plugin on a new phone by1 clear memory cache via the parameter-> of storage.2. go to apply via the game shop2.1 compensation data2.2 uninstalling the plug in3 reinstall the app4 by going to settings-> more connections->printing. Turn