RMAN merge backup with compression

Hi All,
Os : solaris 10
db: 10.2.0.4
as of now as per our backup strategy we are taking RMAN levle 0 weekly and daily incremental backup as compressed.
we are planning to take RMAN merge backup like below
For full backup on sunday
backup incremental level 0 AS COPY tag 'DEMO_MERGE_DB' database ;rest of the days
BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG 'DEMO_MERGE_DB' DATABASE;My question is , while taking as merge is there any option to compress the backup.
i have gone through but dint see any info regarding this.
Please help...
Thanks in Advance
Mvk

merge backup , updated backup and image copy are these things are same or any difference inbetween..Image copy of backup copy of the data file
merge backup means that you take incremental backup of data and merge it with the image backup copy of the datafile so that backup copy is updated all the time and in case of recovery, you don't need to apply all archives since backup copy because his copy is already up to date till the time of last merge backup.
Now your image copy backup is an updated backup because it is keep on updated with the incremental backups using merge backup strategy.
Salman

Similar Messages

  • MSSQL 2008 R2 - 32bit, TSQL backup with compression, error: There is insufficient system memory in resource pool 'internal' to run this query

    Hello,
    I would like to ask you about advice.
    We have MSSQL 2008 R2, 32 bit. Memory is 4GB, split into 2GB for Windows and 2GB for applications. Database has recovery model simple because we have replicated data into other servers ( 2 ). Contemporary we work with 2 servers. Max memory for MSSQL is 2048
    MB.
    We set the backup as follows:
    USE MSDB
    GO
    DECLARE @JMENO_ZALOHY VARCHAR(120)
    SELECT  @JMENO_ZALOHY = 'E:\backup\BackupSQL\1 Pondeli\DAVOSAM_'+ convert( varchar(2), datepart( hh, getdate() ) ) + '00_DEN_DIFF.bak'
    SELECT  @JMENO_ZALOHY
    BACKUP DATABASE [DAVOSAM]
    TO DISK = @JMENO_ZALOHY
    WITH INIT, DIFFERENTIAL, CHECKSUM, COMPRESSION
    GO
    Every second or third day in log there is error message: 'There is insufficient system memory in resource pool 'internal' to run this query' Accurate in time of backup. The error is still repeat, majority in working hours.
    Today I have found out, that problem is probably in compression of backup. Because if I removed word: compression, a backup normally runs without error.
    Question: Is my hypothesis correct that problem is in backup with compression?
    Thank you David

    Hello, today evening I have ran backup command bellow. All is OK. Probably MSSQL has cleaned memory. Next attempt I will try in peak next week.
    Since time I have removed word compression, in error log is not any error.
    I have checked memory as soon as memory gets on top, it is about 1.707 GB the MSSQL writes into log this messgages:
    2014-03-14 15:00:04.63 spid89      Memory constraints resulted reduced backup/restore buffer sizes. Proceding with 7 buffers of size 64KB.
    2014-03-14 15:00:08.74 Backup      Database differential changes were backed up. Database: DAVOSAM, creation date(time): 2014/01/12(22:03:10), pages dumped: 16142, first LSN: 1894063:1673:284,
    last LSN: 1894063:1792:1, full backup LSN: 1894053:15340:145, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\backup\BackupSQL\5 Patek\DAVOSAM_1500_DEN_DIFF.bak'}). This is an informational message. No user action is required.
    2014-03-14 15:00:12.79 spid72      Memory constraints resulted reduced backup/restore buffer sizes. Proceding with 7 buffers of size 64KB.
    2014-03-14 15:00:12.88 Backup      Database differential changes were backed up. Database: WEBFORM, creation date(time): 2014/02/01(05:22:47), pages dumped: 209, first LSN: 125436:653:48, last
    LSN: 125436:674:1, full backup LSN: 125435:689:36, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'E:\backup\BackupSQL\5 Patek\WEBFORM_1500_DEN_DIFF.bak'}). This is an informational message. No user action is required.
    After that the MSSQL reduced memory on 1.692.
    USE MSDB
    GO
    DECLARE @JMENO_ZALOHY VARCHAR(120)
    SELECT  @JMENO_ZALOHY = 'E:\backup\BackupSQL\6 Sobota\DAVOSAM_'+ convert( varchar(2), datepart( hh, getdate() ) ) + '00_DEN_FULL.bak'
    SELECT  @JMENO_ZALOHY
    BACKUP DATABASE [DAVOSAM]
    TO DISK = @JMENO_ZALOHY
    WITH INIT, CHECKSUM, COMPRESSION, MAXTRANSFERSIZE=65536
    GO
    E:\backup\BackupSQL\6 Sobota\DAVOSAM_2100_DEN_FULL.bak
    (1 row(s) affected)
    Processed 467240 pages for database 'DAVOSAM', file 'DavosAM_Data' on file 1.
    Processed 2 pages for database 'DAVOSAM', file 'DavosAM_Log' on file 1.
    BACKUP DATABASE successfully processed 467242 pages in 24.596 seconds (148.411 MB/sec).
    select * from sys.dm_exec_connections
    where net_packet_size > 8192
    session_id  most_recent_session_id connect_time            net_transport                            protocol_type            
                   protocol_version endpoint_id encrypt_option                           auth_scheme                
                 node_affinity num_reads   num_writes  last_read               last_write              net_packet_size client_net_address  
                                client_tcp_port local_net_address                                local_tcp_port
    connection_id                        parent_connection_id                 most_recent_sql_handle
    (0 row(s) affected)
    SELECT SUM (pages_allocated_count * page_size_in_bytes)/1024 as 'KB Used', mo.type, mc.type
    FROM sys.dm_os_memory_objects mo
    join sys.dm_os_memory_clerks mc on mo.page_allocator_address=mc.page_allocator_address
    GROUP BY mo.type, mc.type, mc.type
    ORDER BY 1 DESC;
    KB Used     type                                                         type
    29392       MEMOBJ_SORTTABLE                                             MEMORYCLERK_SQLSTORENG
    9392        MEMOBJ_SOSNODE                                               MEMORYCLERK_SOSNODE
    8472        MEMOBJ_SQLTRACE                                              MEMORYCLERK_SQLGENERAL
    5480        MEMOBJ_SECOLMETACACHE                                        USERSTORE_SCHEMAMGR
    5280        MEMOBJ_RESOURCE                                              MEMORYCLERK_SQLGENERAL
    5008        MEMOBJ_CACHEOBJPERM                                          USERSTORE_OBJPERM
    4320        MEMOBJ_SOSSCHEDULER                                          MEMORYCLERK_SOSNODE
    2864        MEMOBJ_PERDATABASE                                           MEMORYCLERK_SQLSTORENG
    2328        MEMOBJ_SQLCLR_CLR_EE                                         MEMORYCLERK_SQLCLR
    2288        MEMOBJ_SESCHEMAMGR                                           USERSTORE_SCHEMAMGR
    2080        MEMOBJ_SOSDEADLOCKMONITORRINGBUFFER                          MEMORYCLERK_SQLSTORENG
    2008        MEMOBJ_LOCKBLOCKS                                            OBJECTSTORE_LOCK_MANAGER
    1584        MEMOBJ_CACHESTORETOKENPERM                                   USERSTORE_TOKENPERM
    1184        MEMOBJ_LOCKOWNERS                                            OBJECTSTORE_LOCK_MANAGER
    840         MEMOBJ_SNIPACKETOBJECTSTORE                                  OBJECTSTORE_SNI_PACKET
    760         MEMOBJ_SOSDEADLOCKMONITOR                                    MEMORYCLERK_SQLSTORENG
    752         MEMOBJ_SESCHEMAMGR_PARTITIONED                               USERSTORE_SCHEMAMGR
    688         MEMOBJ_RESOURCEXACT                                          MEMORYCLERK_SQLSTORENG
    616         MEMOBJ_SOSWORKER                                             MEMORYCLERK_SOSNODE
    552         MEMOBJ_METADATADB                                            MEMORYCLERK_SQLGENERAL
    480         MEMOBJ_SRVPROC                                               MEMORYCLERK_SQLCONNECTIONPOOL
    424         MEMOBJ_SQLMGR                                                CACHESTORE_SQLCP
    400         MEMOBJ_SBOBJECTPOOLS                                         OBJECTSTORE_SERVICE_BROKER
    384         MEMOBJ_SUPERLATCH_BLOCK                                      MEMORYCLERK_SQLSTORENG
    384         MEMOBJ_RESOURCEDATASESSION                                   MEMORYCLERK_SQLGENERAL
    352         MEMOBJ_SOSSCHEDULERMEMOBJPROXY                               MEMORYCLERK_SOSNODE
    328         MEMOBJ_SBMESSAGEDISPATCHER                                   MEMORYCLERK_SQLSERVICEBROKER
    320         MEMOBJ_METADATADB                                            USERSTORE_DBMETADATA
    296         MEMOBJ_INDEXSTATSMGR                                         MEMORYCLERK_SQLOPTIMIZER
    264         MEMOBJ_LBSSCACHE                                             OBJECTSTORE_LBSS
    224         MEMOBJ_XE_ENGINE                                             MEMORYCLERK_XE
    216         MEMOBJ_GLOBALPMO                                             MEMORYCLERK_SQLGENERAL
    208         MEMOBJ_PROCESSRPC                                            USERSTORE_SXC
    200         MEMOBJ_SYSTASKSESSION                                        MEMORYCLERK_SQLCONNECTIONPOOL
    200         MEMOBJ_REPLICATION                                           MEMORYCLERK_SQLGENERAL
    192         MEMOBJ_SOSSCHEDULERTASK                                      MEMORYCLERK_SOSNODE
    176         MEMOBJ_SQLCLRHOSTING                                         MEMORYCLERK_SQLCLR
    168         MEMOBJ_SYSTEMROWSET                                          CACHESTORE_SYSTEMROWSET
    128         MEMOBJ_RESOURCESUBPROCESSDESCRIPTOR                          MEMORYCLERK_SQLGENERAL
    128         MEMOBJ_CACHESTORESQLCP                                       CACHESTORE_SQLCP
    128         MEMOBJ_RESOURCESEINTERNALTLS                                 MEMORYCLERK_SQLSTORENG
    120         MEMOBJ_BLOBHANDLEFACTORYMAIN                                 MEMORYCLERK_BHF
    120         MEMOBJ_SNI                                                   MEMORYCLERK_SNI
    88          MEMOBJ_QUERYNOTIFICATON                                      MEMORYCLERK_SQLOPTIMIZER
    72          MEMOBJ_HOST                                                  MEMORYCLERK_HOST
    72          MEMOBJ_INDEXRECMGR                                           MEMORYCLERK_SQLOPTIMIZER
    64          MEMOBJ_RULETABLEGLOBAL                                       MEMORYCLERK_SQLGENERAL
    56          MEMOBJ_SERVICEBROKER                                         MEMORYCLERK_SQLSERVICEBROKER
    56          MEMOBJ_REMOTESESSIONCACHE                                    MEMORYCLERK_SQLGENERAL
    56          MEMOBJ_PARSE                                                 CACHESTORE_PHDR
    48          MEMOBJ_CACHESTOREBROKERTBLACS                                CACHESTORE_BROKERTBLACS
    48          MEMOBJ_APPENDONLYSTORAGEUNITMGR                              MEMORYCLERK_SQLSTORENG
    40          MEMOBJ_SBASBMANAGER                                          MEMORYCLERK_SQLSERVICEBROKER
    32          MEMOBJ_OPTINFOMGR                                            MEMORYCLERK_SQLOPTIMIZER
    32          MEMOBJ_SBTRANSPORT                                           MEMORYCLERK_SQLSERVICEBROKERTRANSPORT
    32          MEMOBJ_CACHESTOREBROKERREADONLY                              CACHESTORE_BROKERREADONLY
    32          MEMOBJ_DIAGNOSTIC                                            MEMORYCLERK_SQLGENERAL
    32          MEMOBJ_UCS                                                   MEMORYCLERK_SQLSERVICEBROKER
    24          MEMOBJ_STACKSTORE                                            CACHESTORE_STACKFRAMES
    24          MEMOBJ_CACHESTORESXC                                         USERSTORE_SXC
    24          MEMOBJ_FULLTEXTGLOBAL                                        MEMORYCLERK_FULLTEXT
    24          MEMOBJ_APPLOCKLVB                                            OBJECTSTORE_LOCK_MANAGER
    24          MEMOBJ_FULLTEXTSTOPLIST                                      CACHESTORE_FULLTEXTSTOPLIST
    24          MEMOBJ_CONVPRI                                               CACHESTORE_CONVPRI
    16          MEMOBJ_SQLCLR_VMSPY                                          MEMORYCLERK_SQLCLR
    16          MEMOBJ_VIEWDEFINITIONS                                       MEMORYCLERK_SQLOPTIMIZER
    16          MEMOBJ_SBACTIVATIONMANAGER                                   MEMORYCLERK_SQLSERVICEBROKER
    16          MEMOBJ_AUDIT_EVENT_BUFFER                                    OBJECTSTORE_SECAUDIT_EVENT_BUFFER
    16          MEMOBJ_HASHGENERAL                                           MEMORYCLERK_SQLQUERYEXEC
    16          MEMOBJ_SBTIMEREVENTCACHE                                     MEMORYCLERK_SQLSERVICEBROKER
    16          MEMOBJ_ASYNCHSTATS                                           MEMORYCLERK_SQLGENERAL
    16          MEMOBJ_BADPAGELIST                                           MEMORYCLERK_SQLUTILITIES
    16          MEMOBJ_QSCANSORTNEW                                          MEMORYCLERK_SQLQUERYEXEC
    16          MEMOBJ_SCTCLEANUP                                            MEMORYCLERK_SQLGENERAL
    16          MEMOBJ_XP                                                    MEMORYCLERK_SQLXP
    8           MEMOBJ_SECURITY                                              MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_CACHESTOREBROKERRSB                                   CACHESTORE_BROKERRSB
    8           MEMOBJ_EXCHANGEXID                                           MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_CACHESTOREVENT                                        CACHESTORE_EVENTS
    8           MEMOBJ_CACHESTOREXPROC                                       CACHESTORE_XPROC
    8           MEMOBJ_DBMIRRORING                                           MEMORYCLERK_SQLUTILITIES
    8           MEMOBJ_SERVICEBROKERTRANSOBJ                                 CACHESTORE_BROKERTO
    8           MEMOBJ_CACHESTOREOBJCP                                       CACHESTORE_OBJCP
    8           MEMOBJ_CACHESTOREXMLDBELEMENT                                CACHESTORE_XMLDBELEMENT
    8           MEMOBJ_ENTITYVERSIONINFO                                     MEMORYCLERK_SQLSTORENG
    8           MEMOBJ_AUDIT_MGR                                             MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_EXCHANGEPORTS                                         MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_DEADLOCKXML                                           MEMORYCLERK_SQLSTORENG
    8           MEMOBJ_CACHESTORETEMPTABLE                                   CACHESTORE_TEMPTABLES
    8           MEMOBJ_HTTPSNICONTROLLER                                     MEMORYCLERK_SQLHTTP
    8           MEMOBJ_CACHESTOREVIEWDEFINITIONS                             CACHESTORE_VIEWDEFINITIONS
    8           MEMOBJ_CACHESTOREPHDR                                        CACHESTORE_PHDR
    8           MEMOBJ_CACHESTOREXMLDBTYPE                                   CACHESTORE_XMLDBTYPE
    8           MEMOBJ_CACHESTORE_BROKERUSERCERTLOOKUP                       CACHESTORE_BROKERUSERCERTLOOKUP
    8           MEMOBJ_EVENTSUBSYSTEM                                        MEMORYCLERK_SQLGENERAL
    8           MEMOBJ_CACHESTOREBROKERDSH                                   CACHESTORE_BROKERDSH
    8           MEMOBJ_SOSDEADLOCKMONITORXMLREPORT                           MEMORYCLERK_SQLSTORENG
    8           MEMOBJ_CACHESTOREXMLDBATTRIBUTE                              CACHESTORE_XMLDBATTRIBUTE
    8           MEMOBJ_CACHESTOREBROKERKEK                                   CACHESTORE_BROKERKEK
    8           MEMOBJ_QPMEMGRANTINFO                                        MEMORYCLERK_SQLQUERYEXEC
    8           MEMOBJ_CACHESTOREQNOTIFMGR                                   CACHESTORE_NOTIF
    (101 row(s) affected)
    David

  • 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

  • RMAN online backup with dbconsole.

    I want to run an online (hot) backup of a 10g enterprise edition database using dbconsole. There is no option for this on the web page that I can see. I thought I could trick the software by selecting 'whole backup' and then edit the RMAN script and enter the command 'backup database plus archivelog'. That command was documented as the way to run an onlne backup in the Oracle Press book 'Oracle Database 10g, RMAN Backup & Recovery'.
    But there was a message stating that the database would be brought down during the backup, obviously ignoring the command mentioned above.
    1. Can I perform a hot backup with dbconsole?
    2. If so, how?

    You can also review the following;
    OBE
    Performing Backups and Recovering Your Database
    Performing Backups
    http://www.oracle.com/technology/obe/10gr2_db_single/ha/rman/rman_otn.htm#t1
    Adith

  • Rman merge backup

    I read the Incrementally Updated Backup In 10G [ID 303861.1]
    It very good RMAN 10g features .
    I have level 0 impage copy and t increamental backup in the disk
    another increamental backup will run tonight
    Assume that one of my databasefile is corrupt
    how to recover in the merge database backup
    what is the base I will start
    Oracle 10.2.0.5

    It's not really a "merge database backup" but an "Incrementally Updated Backup".
    If you lose only a single datafile in your database you can use
    RESTORE DATAFILE n FROM DATAFILECOPY
    RECOVER DATAFILE nso RMAN would copy only that datafile from your Incrementally Updated Backup after which you still need to RECOVER DATAFILE to bring it uptodate (synchronise) with the rest of the database.
    Hemant K Chitale

  • Backup with rman hang

    I tested this step of backup of rman on my newly installed 10g R2 SE on AIX box, but it seemed hung there (at least after 2 hours, nothing continue)
    RMAN> run {
    backup as compressed backupset incremental level 0 cumulative device type disk tag 'BAANBK$LEVEl_0' database;
    Starting backup at 10-JAN-07
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting compressed incremental level 0 datafile backupset
    channel ORA_DISK_1: specifying datafile(s) in backupset
    input datafile fno=00006 name=/dbbaan/oradata/baanbk/baandbs02.dbf
    input datafile fno=00007 name=/dbbaan/oradata/baanbk/baandbs03.dbf
    input datafile fno=00008 name=/dbbaan/oradata/baanbk/baandbs04.dbf
    input datafile fno=00009 name=/dbbaan/oradata/baanbk/baandbs05.dbf
    input datafile fno=00010 name=/dbbaan/oradata/baanbk/baandbs06.dbf
    input datafile fno=00011 name=/dbbaan/oradata/baanbk/baanidx01.dbf
    input datafile fno=00012 name=/dbbaan/oradata/baanbk/baanidx02.dbf
    input datafile fno=00013 name=/dbbaan/oradata/baanbk/baanidx03.dbf
    input datafile fno=00014 name=/dbbaan/oradata/baanbk/baanidx04.dbf
    input datafile fno=00015 name=/dbbaan/oradata/baanbk/baanidx05.dbf
    input datafile fno=00016 name=/dbbaan/oradata/baanbk/baanidx06.dbf
    input datafile fno=00017 name=/dbbaan/oradata/baanbk/baanidx07.dbf
    input datafile fno=00001 name=/dbbaan/oradata/baanbk/system01.dbf
    input datafile fno=00002 name=/dbbaan/oradata/baanbk/undotbs01.dbf
    input datafile fno=00003 name=/dbbaan/oradata/baanbk/undotbs02.dbf
    input datafile fno=00004 name=/dbbaan/oradata/baanbk/sysaux01.dbf
    input datafile fno=00005 name=/dbbaan/oradata/baanbk/baandbs01.dbf
    input datafile fno=00018 name=/dbbaan/oradata/baanbk/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 10-JAN-07
    That´s all i got on screen. Where is the rman log, so I can check what was going? The same script is running well on my 10gR2 EE at RHEL3. Tried without the "compressed" came out the same hung.

    $ rman target / nocatalog
    Recovery Manager: Release 10.2.0.1.0 - Production on Wed Jan 10 13:20:24 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: BAANBK (DBID=905495458)
    using target database control file instead of recovery catalog
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 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 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 CHANNEL DEVICE TYPE DISK FORMAT '/dbrecovery/flash_recovery_area/%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 '/oracleapp/oracle/product/10.2.0/db_1/dbs/snapcf_baanbk.f'; # default
    This is the same configuration as that of RHEL3
    This is a dev box, so no other activity.
    Message was edited by:
    user508054
    Message was edited by:
    user508054

  • RMAN backup with smallest backup size

    Oralce 11g2 on Redhat 5. The diskspace is our tightest resource, and we want to an incremental backup with level0 on Sunday and level 1 every week days and Saturday. I am to use the comamnds to do the job--Sunday
    backup incremental level 0 tag 'level_0' database plus archivelog;
    --Other days
    backup incremental level 1 database plus archivelog delete all input;I do not think this is the best practice nor produce smallest backup files.
    What are you comments and opinions. Thanks

    Pavan, Thank you for reply. Here are the info requested
    what is size of DB ??
    ~250GB, including UNDO and TEMP. It is a dev database and not very big. But we have total 800GB disk space. After setting some housekeeoing folders, and allow some space for data growth, it leaves 180GB for flash_recovery_area.
    what would be max size of archive logs generated per day ??
    Variable from less than 1 GB to 12 GB
    Are you taking backups to tape or Disk ??
    Disk. In the 180GB flash_recovery_area, Current backup size is 152GB. If a backup fails to delete obsolete files, the next backup will fill the flash_recovery_area.
    Provide the Rman configuration information ??
    RMAN> show all;
    RMAN configuration parameters for database with db_unique_name TDEV2 are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    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';
    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 MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_tdev2.f'; # default

  • Rman backup with corrupted block

    Hello,
    Firstly - I have problem on non-production database 11.2.0.1.0, so I am not deeply worried about data. But I need to understand what happened with database backups and how to prevent such things in future.
    So - I have EM scheduled weekly full backup and daily incremental backups. Later there was problem with hardware and some corrupted blocks in database were found. The weekly backup ran without error and obsolete backups were deleted. Now it is not possible to "recover corruption list" because no backup without corruption exists (RMAN-06023: no backup or copy of datafile 6 found to restore). I am not worried about the lost data, but I need to find out how come the backup contains corrupted block.
    I have checked the data file using dbv utility
    DBVERIFY - Verification starting : FILE = /opt/oracle/oradata/orcl/users03.dbf
    DBV-00200: Block, DBA 27525766, already marked corrupt
    csc(0x0001.7b01729f) higher than block scn(0x0000.00000000)
    Page 2359942 failed with check code 6054
    DBVERIFY - Verification complete
    Total Pages Examined         : 3840000
    Total Pages Processed (Data) : 453896
    Total Pages Failing   (Data) : 1
    Total Pages Processed (Index): 2959104
    Total Pages Failing   (Index): 0
    Total Pages Processed (Other): 424025
    Total Pages Processed (Seg)  : 0
    Total Pages Failing   (Seg)  : 0
    Total Pages Empty            : 2975
    Total Pages Marked Corrupt   : 1
    Total Pages Influx           : 0
    Total Pages Encrypted        : 0
    Highest block SCN            : 2156227446 (1.2156227446)As you can see the datafile 6 - user03.dbf has errors. Also backups now contain errors.
    1) So how is it possible that the EM scheduled backup ran without problems and the backup now contains corrupted blocks. How to prevent this in future ? I know there is setting MAXCORRUPT. How can I check its current value ? How can I configure it using EM scheduled backups ?
    2) Secondly, meanwhile I studied the RMAN commands. So I have suspended EM backup jobs, and executed follwing command. And backup ran without error again. How is this possible, if data file users06.dbf has corrupted block ?
    Thanks !
    RMAN> run {
    set MAXCORRUPT for datafile 6 to 0;
    backup as compressed backupset datafile 6;
    2> 3> 4>
    executing command: SET MAX CORRUPT
    Starting backup at 07-NOV-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    using channel ORA_DISK_5
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: starting piece 1 at 07-NOV-12
    channel ORA_DISK_1: finished piece 1 at 07-NOV-12
    piece handle=/opt/oraBackup/rman/nrnpo0sg_1_1 tag=TAG20121107T200120 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 01:13:05
    Finished backup at 07-NOV-12
    Starting Control File and SPFILE Autobackup at 07-NOV-12
    piece handle=/opt/oraBackup/rman/c-1253245572-20121107-03 comment=NONE
    Finished Control File and SPFILE Autobackup at 07-NOV-12

    I have updated database to 11.2.0.3
    However, the problem still persists. rman backup went ok on broken file
    oracle@orcl-cluster:~> sqlplus
    SQL*Plus: Release 11.2.0.3.0 Production on Tue Nov 20 09:24:11 2012
    Copyright (c) 1982, 2011, Oracle.  All rights reserved.
    Enter user-name: system
    Enter password:
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select * from V$DATABASE_BLOCK_CORRUPTION;
         FILE#     BLOCK#     BLOCKS CORRUPTION_CHANGE# CORRUPTIO
             6    2359942          1                  0 FRACTURED
            25    1855622          1                  0 FRACTURED
    oracle@orcl-cluster:~> rman target /
    Recovery Manager: Release 11.2.0.3.0 - Production on Tue Nov 20 08:04:57 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: ORCL (DBID=1253245572)
    RMAN> backup as compressed backupset datafile 6;
    Starting backup at 20-NOV-12
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=1596 device type=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: SID=1568 device type=DISK
    allocated channel: ORA_DISK_3
    channel ORA_DISK_3: SID=2357 device type=DISK
    allocated channel: ORA_DISK_4
    channel ORA_DISK_4: SID=2341 device type=DISK
    allocated channel: ORA_DISK_5
    channel ORA_DISK_5: SID=86 device type=DISK
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: starting piece 1 at 20-NOV-12
    channel ORA_DISK_1: finished piece 1 at 20-NOV-12
    piece handle=/opt/oraBackup/rman/2rnqovpp_1_1 tag=TAG20121120T080513 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 01:10:35
    Finished backup at 20-NOV-12
    Starting Control File and SPFILE Autobackup at 20-NOV-12
    piece handle=/opt/oraBackup/rman/c-1253245572-20121120-00 comment=NONE
    Finished Control File and SPFILE Autobackup at 20-NOV-12
    RMAN> backup validate datafile 6;
    Starting backup at 20-NOV-12
    using channel ORA_DISK_1
    using channel ORA_DISK_2
    using channel ORA_DISK_3
    using channel ORA_DISK_4
    using channel ORA_DISK_5
    channel ORA_DISK_1: starting compressed full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00006 name=/opt/oracle/oradata/orcl/users03.dbf
    channel ORA_DISK_1: backup set complete, elapsed time: 00:03:05
    List of Datafiles
    =================
    File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
    6    OK     1              2975         3840000         6489027926
      File Name: /opt/oracle/oradata/orcl/users03.dbf
      Block Type Blocks Failing Blocks Processed
      Data       0              453912
      Index      0              2959091
      Other      0              424022
    Finished backup at 20-NOV-12Edited by: kamilp on Nov 20, 2012 12:23 AM

  • RMAN Automatic backup/recovery with oracle fail safe, windows cluster

    Hello,
    I have question,
    1) Whether it is possible to do "RMAN Automatic Backup and recovery" in environment as ?
    Environment: -
    a. Windows clustering with windows server 2003 Enterprise Edition R2 (Two Node Clustering)
    b. Shared disk ( RAID )
    c. Oracle 10g standard edition one
    d. Oracle fail safe v3.3.3 (for redundancy)
    Here we have single oracle instance operating on single database whose files are located on shared disk.
    2) If answer to above question is yes please specify if there is some good documentation to it.
    Any help regarding this will be greatly appreciated.
    Thanks in advance,
    Rahul

    You just need to make sure that the RMAN scripts are always able to connect to the target database instance whether instance runs on cluster node 1 or cluster node 2
    here, If oracle services(resources) will shift from Node1 to Node2 (due to media or any failure) during RMAN Backup then there will be break in connection, will it destroy my backup or will it get started automatically without any harm?
    and also I want to know,
    Do we need to setup another server which will have RMAN backup script running?

  • Rman backup with  standby database

    Hi All,
    I am looking for some suggestions for rman backup with standby  database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at  sql 'alter system archive log current' in rman  with standby as target. which gives following errors  with or without noswitch clause
    RMAN> sql 'alter system archive log current noswitch';
    sql statement: alter system archive log current noswitch
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
    ORA-01109: database not open
    Recovery Manager: Release 11.2.0.1.0
    Oracle databaes  Release 11.2.0.1.0 64 bit
    OS:RHEL 6 x86-64 bit
    Secondly, do I need to cancel manged recovery while taking rman backups on standby.
    I scanned thru MOS but could find solutions for rman with active DG.
    Thanks in advance

    726d07e6-b870-431f-8c22-a499c3ec4e0c wrote:
    Hi All,
    I am looking for some suggestions for rman backup with standby  database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at  sql 'alter system archive log current' in rman  with standby as target. which gives following errors  with or without noswitch clause
    RMAN> sql 'alter system archive log current noswitch';
    sql statement: alter system archive log current noswitch
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12
    RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitch
    ORA-01109: database not open
    Recovery Manager: Release 11.2.0.1.0
    Oracle databaes  Release 11.2.0.1.0 64 bit
    OS:RHEL 6 x86-64 bit
    Secondly, do I need to cancel manged recovery while taking rman backups on standby.
    I scanned thru MOS but could find solutions for rman with active DG.
    Thanks in advance
    "I scanned thru MOS but could find solutions for rman with active DG."
    Howto make a consistent RMAN backup in an Standby database in Active DataGuard mode (Doc ID 1419923.1)

  • RMAN Backup with ASM and Standby in place

    Hi All,
    We are planning to upgrade our database from 10.2.0.2 to 10.2.0.3. We have ASM as storage on primary and phisical standby is in place.
    I want to make a cut of point for backup, i.e if I restore till that poit on primary standby should continue to work. I need not create standby.
    We are using rman for backup and primary db uses asm for data,archive and redolog storage.
    I have a online complete db backup at 12:00PM. At say 6:00pm i take primary down and apply all archives on standby and cancel recovery on standby along with taking it down. On primary i mount db and take controlfile backup and all archive log backup using rman.
    Now i continue with upgrade and many more changes on primary. I will not touch standby. We decide to revertback at 10pm on primary. If I wan to return back to 6:00pm state on primary and standby.
    I believe I will restore controlfile backup taken at 6:00pm with db in mount phase. Restore dbfiles from online backup and recover using archives.
    My question is do i need to open with resetlogs? Then I will lose my standby which was up to date at 6:00pm. Can I not backup redofiles at 6:00pm with db in mount phase and i restore them then i need not open with reset logs and my stnadby will continue from that point.
    Please guide me..Is there way to backup redologs when db is in mount phase and using asm for storage using rman.

    There are quite a bunch of steps involved and you need to do some documentation reading.
    Do you plan to create the test database on the same machine or different RAC system?
    Which version of Oracle are you using? What OS?
    There is plenty of information on the web if you search for "duplicate database RAC ASM". Did you try?

  • Rman archivelog backup fails with rman-03002,ora-19563

    Hi,
    D:\ Oracle- -\BIN\RMAN TARGET / NOCATALOG
    RMAN> backup archivelog all;
    RMAN-03002: Error with backup command on 06-25-2013
    ORA-19563: Header-Validation is not successful.
        fails with the given errors.
    11.2.0.2 PROD DB on Windows Server 2008  R2 Enterpriise.
    When I issue BACKUP INCREMENTAL LEVEL 0 DATABASE; it works fine. but with archivelog it is creating problems. Unfortunatly, I have not found exactly the same problem on google and on Oracle support.
    The DB is using INIT.ORA and last time when I switched the mode to archive log mode I set the parameter like SCOPE=MEMORY as SPFILE was not in use and ALTER SYSTEM with SCOPE=BOTH  FRA destination and size, but after the DB restarting of course that setting is gone and I am having these problems.
    Please suggest.
    Thanks a lot.
    Best Regards,

    Hi,
    Thanks a lot.
    I don't think that archivelogs were relocated, except I changed the location yesterday.
    As I wrote at the start that because of INIT.ORA file being in use instead of SPFILE. I set DB_RECOVERY_FILE_DEST, DB_RECOVERY_DEST_SIZE after changing the DB mode to ARCHIVELOG, but DB was restarted by somebody else, and as the parameter changing was NOT PERMANENT, it rollback.
    LOG_ARCHIVE_DEST was set to d:\oradata\db with archivelog mode but db_recovery_file_dest and size was set to 0. Now here, I have no idea that whether archivelogs were not being backed up or deleted physically, but I guess that as log_archive_dest parameter is deprecated and mode is set to archivelog with no real ARCHIVELOG DESTINATION. Please correct me if I am wrong or totally wrong :-)
    I performed DELETED EXPIRED ARCHIVELOG ALL, and it deleted 49 EXPIRED objects.
    Now CROSSCHECK ARCHIVELOG ALL and LIST ARCHIVELOG ALL shows nothing.
    LIST BACKUP OF ARCHIVELOG ALL has of course those 49 archivelog gap.
    Could you please tell the impacts of those 49 missing archivelogs. Retention policy is set to 14 days. I mean the risk is for 14 days right? As anyhow, the older backups are being DELETED according to retention policy of RMAN.

  • Restore incremental backup with rman

    Dear Friends
    can u tell me how to restore an incremental backup with rman? i backup my rman with statement below :
    1. backup full database format '/oracle/PRD/sapbackup/%U';
    the results was :
    -rw-r----- 1 oraprd dba 19006996480 Jun 10 12:08 0ojiit4n_1_1
    -rw-r----- 1 oraprd dba 12746752 Jun 10 12:08 0pjiiu6b_1_1
    2. after that i do incremental backup :
    backup incremental level 1 cumulative database format '/oracle/PRD/sapbackup/%U';
    the results was :
    -rw-r----- 1 oraprd dba 173400064 Jun 10 13:44 0ujij2k0_1_1
    -rw-r----- 1 oraprd dba 12746752 Jun 10 13:44 0vjij3qc_1_1
    what statement i need to run for restore the incremental backup?

    run{
    ALLOCATE CHANNEL c1 DEVICE TYPE DISK;
    RESTORE DATABASE;
    RECOVER DATABASE;
    The above command will restore your database from the last good RMAN backup. Your last backup is incremental level backup as you posted. The above command will fullfill your requirements

  • Catalog backup not compressed with Lightroom 6

    Lightroom 6 is said to compress the catalog backup into a zip file.
    When I try this with a small test catalog it works fine.
    However when I backup my real catalog (75 000 photos, 7.5 GB) the file is not compressed. LR6 behaves exactly as LR5. 
    I tried several times but it is always the same.
    Did someone meet the same problem ?
    Any advice ?
    Thanks.
    Michel (Paris)

    Thank you Ian for your answer.
    However I don't think I misunderstood how Lightroom backup works. Maybe I was not very clear in my explanation (English is not my mother tongue !).
    I run a test with a small catalog (test_backup.lrcat), which I created just for this purpose. In this case the catalog backup is compressed in a zip archive 
    However, when I open Lightroom with my actual catalog (lightroom-6.lrcat), then the catalog backup is not compressed (it's just a copy of the catalog).
    I don't understand why LR6 does not compress the catalog backup in the last case.

  • Incremental RMAN backup and compression

    Does RMAN compress the data for the incremental Level 0 and Level 1 backups. More specifically - Can I use Advanced compression if olny use incremental backups ?

    you would use the comfigure command to use zlib which is does not compress as well as bzip2 which does not require the advanced compression option, but zlib does not consume as much cpu as bzip2.
    now for the backup you have 2 options. you can configure backupsets to compress
    CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET ;
    or it using table
    CONFIGURE DEVICE TYPE sbt BACKUP TYPE TO COMPRESSED BACKUPSET ;
    Then do you backups as backup sets
    database
    backup as backupset incremental level 1 tag hot_1_${DTE} DATABASE NOT BACKED UP SINCE TIME 'SYSDATE - .6';
    archivelogs
    backup as compressed backupset format '${INST_LOWER}_Archive_%d_%s_%p_%t' archivelog all not backed up 1 times ;

Maybe you are looking for