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

Similar Messages

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

INCREMENTAL MERGE BACKUP & RECOVERY

INCREMENTAL MERGE BACKUP & RECOVERY
=====================================
1) 개요
RMAN을 이용하여 database의 Image copy를 Backup하고 그 Backup에 retention policy만큼의 Incremental Backup을 적용하여서 복구의 시간을 단축한 Backup의 방법입니다.
즉 retention policy에 설정되어있는 시간 전의 최후의 시간까지 Image Copy를 보장하는 방법이며 Disk Space는 Incremental Backup만 사용하는 방법보다는 Image Copy를 사용하는 것임으로 많이 소요됩니다.
물론 Backup & Recovery 정책에 따라서 Retention Policy를 Recovery Window나 Redundancy 2이상으로 설정할 수 있으나, Incremental Merge Backup & Recovery의 장점을 극대화 하기 위해서는 Redundancy 1 (Default)로 설정하는 것을 권해드립니다.
2) 장점
- Recovery 시에 최근 Incremental Backup의 정보들이 적용이 되어있기 때문에 최소한의 시간으로 Recovery 작업을 진행하실 수 있습니다. 물론 장점을 극대화 하시기 위해서는 Retention Policy를 redundancy 1로 설정해 주시길 권해드립니다.
- Datafile들의 Destination을 Backup된 Image Copy가 있는 곳으로 Switch 하여 Restore하는 시간을 단축하셔서 Recovery를 진행하실 수도 있으나 Recovery 후의 관리의 용이성을 위해 부득히한 경우를 재외하고는 권장하지 않습니다.
3) Syntax
- Backup
RMAN> BACKUP INCREMENTAL LEVEL 1
FOR RECOVER OF COPY
WITH TAG WEEKLY DATABASE;
위 명령어를 사용하시면 WEEKLY라는 Tag로 생성된 Copy가 없을 시에는 Image Copy를 Weekly라는 Tag로 구분하여 Backup을 받게 됩니다.
* 여기서 Copy라 함은 FOR RECOVER OF COPY라는 구문을 사용하여서 만든 Image Copy를 뜻합니다.
RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY;
위 명령어를 사용하시면 현재 받았던 Incremental Backup을 Weekly라는 Tag를 가지고 있는 Database Copy에 적용을 하게 됩니다.
RMAN> Delete Obsolete;
위 명령어를 사용하시면 현재의 Image Copy에 적용된 Incremental Backup을 재외한 나머지 Incremental Backup들이 Delete됩니다.
-Recovery
RMAN> switch database to copy;
문제가 발생하셨을 때 위 명령어를 사용하시면 모든 datafile의 pointer들은 image backup copy를 바라보게 됨으로 Restore의 시간을 절약할 수 있습니다.
4) Retention Policy에 따른 Syntax 변화
* 기본적으로 INCREMENTAL MERGE BACKUP & RECOVERY의 장점인 Recovery 시간을 극대화 하기 위해서는 Retention Policy를 redundancy 1(Default)로 설정하시는 것을 권장해드립니다.
하지만 User가 Backup & Recovery 계획을 변경하여 retention policy를 recovery window 또는 redundancy 1 이상으로 설정해 주시면 Obsolete한 Backupset을 Delete하는 부분과 Backupset을 적용시키는 부분을 수정해 주셔야합니다.
- Recovery Window of 2
Recovery Window를 2일로 설정해 놓으시면 Backup시에는 똑같은 Syntax를 사용하실 수 있으나 Recover copy of database 명령어는 아래와 같이 바뀌어야 합니다.
RMAN> BACKUP INCREMENTAL LEVEL 1
FOR RECOVER OF COPY
WITH TAG WEEKLY DATABASE;
RMAN> RECOVER COPY OF DATABASE WITH TAG WEEKLY until time 'sysdate-2';
왜냐하면 retention policy에 마춰서 image copy도 2일전의 상태로 보관되어야하며 그에 따라서 2일동안의 Backupset들도 보관되어야하기 때문입니다. 만약 until time을 사용하지 않으시면 incremental backup들이 obsolete 상태로 안변하게 됩니다.
- Redundancy 2 이상
Redundancy 2이상으로 설정해 주시면 2개 이상의 Tag를 보관하는 효과로서 역시 예상대로 Obsolete로 안 변하는 현상이 발생됩니다.
DAY 1)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag DAILY)가 생성됩니다.
DAY 2)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag WEEKLY)와 한개의 Backupset (Tag DAILY)가 생성됩니다.
DAY 3)
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG DAILY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG WEEKLY DATABASE;
RMAN> BACKUP INCREMENTAL LEVEL 1 FOR RECOVER OF COPY WITH TAG MONTHLY DATABASE;
-위와 같이 실행하시면 한개의 Database Copy (Tag MONTHLY)와 두개의 Backupset (Tag DAILY, Tag WEEKLY)가 생성됩니다.
DAY 4)
RMAN> Delete Obsolete;
- 위와 같이 실행하시면 DAILY Tag와 관련된 부분이 Delete 됩니다. (최신 2개의 Tag관련 Backup만 보관)
RMAN> Delete Obsolete redundancy 1
- 위와 같이 실행하시면 DAYLY Tag와 WEEKLY Tag 관련된 부분이 Delete 됩니다. (Redundancy 1로 설정한 것과 똑같은 효과)
Reference:
Article-ID: Note 351455.1
Title: Oracle Suggested Strategy & Backup Retention
Article-ID: Note 303861.1
Title: Incrementally Updated Backup In 10G
글 수정:
hunlee

I would always include an archivelog backup:
... with tag 'fullbackup’ database plus archivelog delete all input;
And at the end:
delete obsolete noprompt;
That delete incrmental backups already applied to the basic image copies.
Your configuration allows only limited point in time recoveries. As soon as an incremental backup is applied to the image copies, you cannot go back in time. To change this you can add a 'until time' clause, for example:
recover
copy of database
with tag 'fullbackup until time 'sysdate-11';
This creates a recovery window of 10 days, only image copies older than 10 days will be changed.
Werner

Using rman to backup a remote database

I am after a good guide or advice on how (what) to install and (how to) run Oracle RMAN
to backup a remote Oracle database.
RMAN must be installed and run on a Solaris (SunOS 5.8) box remote from the Solaris
box (also SunOS 5.8) running the Oracle database but connected to it via a TCP/IP
network.
The Oracle Recovery Manager and Database version is 9.2.0.1.0.
RMAN must perform the backup of the remote database over the network and store
the backup on a disk local to the RMAN box.
The backups may be full or incremental and may be "hot" backups taken while the
Oracle database is open.
The disk files are to be then backed up to tape using Veritas.
What software do I need to install on the RMAN box ?
What software do I need to install on the remote Oracle database box ?
Thanks,
Brett Morgan.

writes to a NFS-mounted diskRman is writing to disk or tape (when is bundled (libraries needed) with some backup software for tapes such as Veritas). The disk device could be local, or mounted disk form other host or storage (over NFS as Werner mentioned, SMB and others).

Got error when creating a standby DB from rman: no backup or copy... Why?

We try to create standby database from a production DB on another server (10.2.0.4). The RMAN backup is in the nfs file system which is also mounted to the target server (the DR box). So, the access path for the rman backup is the same look from primary DB server and DR DB server. I started the RMAN run:
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
5> DUPLICATE TARGET DATABASE for standby
6> nofilenamecheck
7> dorecover;
8> }
9>
10> exit
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=582 devtype=DISK
allocated channel: aux2
channel aux2: sid=584 devtype=DISK
Starting Duplicate Db at 21-JUN-12
contents of Memory Script:
set until scn 12198261770353;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 21-JUN-12
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/21/2012 16:33:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
===========================================================================
The backups should have controlfile. There is rman show all display:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/inbound/online/controlfile_auto%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/inbound/online/%d_%T_%t_%s';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/inbound/online/snapcf_inbound.f';
Why and how to fix? Thanks for help!

Here is the list of command:
RMAN> list backup of controlfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
5518 Full 4.57M DISK 00:00:07 17-JUN-12
BP Key: 5518 Status: AVAILABLE Compressed: NO Tag: TAG20120617T035926
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120617-00
Control File Included: Ckp SCN: 12197994840698 Ckp time: 17-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5522 Full 4.57M DISK 00:00:00 18-JUN-12
BP Key: 5522 Status: AVAILABLE Compressed: NO Tag: TAG20120618T010158
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120618-00
Control File Included: Ckp SCN: 12198041382572 Ckp time: 18-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5526 Full 4.57M DISK 00:00:01 19-JUN-12
BP Key: 5526 Status: AVAILABLE Compressed: NO Tag: TAG20120619T010352
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120619-00
Control File Included: Ckp SCN: 12198090424606 Ckp time: 19-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5530 Full 4.57M DISK 00:00:02 20-JUN-12
BP Key: 5530 Status: AVAILABLE Compressed: NO Tag: TAG20120620T010304
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120620-00
Control File Included: Ckp SCN: 12198146424201 Ckp time: 20-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5534 Full 4.57M DISK 00:00:02 21-JUN-12
BP Key: 5534 Status: AVAILABLE Compressed: NO Tag: TAG20120621T010357
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
Control File Included: Ckp SCN: 12198210334547 Ckp time: 21-JUN-12
==================================================================
I tried to catalog the controlfile:
RMAN> catalog controlfilecopy '/backup/inbound/online/controlfile_autoc-2080040856-20120621-00';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 06/21/2012 17:24:32
ORA-19563: control file header validation failed for file /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
====================================================================
We have level 1 backup everyday, except Sunday. I have level 0 backup on Sunday. I alos tried the metalink note RMAN Duplicate For Standby Fails with Rman-06024: No Backup Or Copy Of The Control File Found To Restore [ID 466321.1]. It does not work.
Thanks for help!

Rman incremental backup

Hi,
we are using oracle10g(10.2.0.3).
is it possible to apply rman incremental backup on top of manual full backup?
Note:There is no level 0 backup available
Thanks
With Regards
Umair

Yes, you can.
Register your manual backup in recovery catalog as level 0 backup. Then take a fresh incremental backup. I have demonstrated the same in my article. You may download the same from here .
Go through the section "Rolling forward a backup".
Regards,
S.K.

Quesion about the Basic concept of RMAN incremental backup

I have a problem in understanding the basic concept of two types RMAN Incremental backup ie. Differential and Cumulative. I just don't understand how cumulative incremental backup consumes more space than Differential backup.
Have a look at the scenario in which Differential backup is used.
1. On Sunday midnight, a LEVEL0 backup is taken.
2. On Monday midnight all the blocks that was changed since Sunday midnight are stored in the backup media (tape or disk)
3. On Tuesday midnight all the blocks that was changed since monday midnight are stored in the backup media.
4. On Wednesday midnight, all the blocks that was changed since tuesday midnight are stored in the backup media.
At this point, in the backup media, you have all the changed blocks from sunday midnight to wednesday midnight eventhough it was stored in a daily basis. If you had taken a cumulative backup at wednesday midnight the backup media would have contained the same changed blocks from sunday midnight(LEVEL0) to wednesday midnight, but all at one go instead of daily basis. I don't understand how cumulative backup consumes more space when the backup media contains the same amount of changed blocks as it were in the case of the Differential backup.

Considering the Scenario you given:
Sunday : Level 0 backup.
Monday : You have taken an incremental backup then there will not be any difference in size of backup set for differential or cumulative as the changes from last Level0 backup are considered.
Tuesday : A cumulative backup (n-1) will have changed blocks since Sunday's Level0 backup but a differential backup(n) will only have changed blocks since Monday. So definitely there will be more space consumed by cumulative backups compared to differentials.
Hope it helps ...
Bhupinder

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 & Hot backup cloning taking long time

Dear DBAs,
We are doing both RMAN & Hot backup cloning foe that taking more time to restore data files to TEST instance. scp taking too much time to copy to target server because of its volume of data (1.5 TB) & Mounting the RMAN backups drive on test server and restoring from that drive taking more than 8 hours.
I heard that some companies are using some device to move heavy volume Hot backup copy from source to dest faster for clone the instance easily with in minutes. What is that device name to take hot backup copies from source and restore it in target server.
Test server Specs
Processor 8 cores with 32GB Memory.
Thanks
DBA

Hot backup is not recommanded for the database size more than 1T.
RMAN backup and restore is the only opiton available for a DBA.
Other option is to use EMC Symmentrix/BCV's/Snapshots. EMC uses pair of disks to achive synch the produciton data with test server. read more about EMC symmentrix or ask your storage team.

11g RMAN UNDO backup optimization

Hi all?
I have tested 11g RMAN UNDO backup optimization
1st I fill the undo tablespace by sql manipulations and not commiting
2nd backed undo_ts up by RMAN (size 24m)
3rd I made a commit
Then backed undo tablespace again but backup_size didn’t change (24m)
Then I made some more manipulations and backed undo_ts again. This time backup_size reduced. (11m)
Then I restarted db and backed up undo_ts again. This time backup size became what I expected (600K)
The question is why 11g rman undo tablespace backup size didn’t reduce after commit?
according to 11g undo optimization it had to
SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
SUM(BYTES)
13172736
SQL> begin
for i in 1..100000 loop
insert into testundo values(i);
end loop;
end;
2 3 4 5 6
PL/SQL procedure successfully completed.
SQL> SQL> update testundo set
id=2 where id>0;
2
update testundo set
ERROR at line 1:
ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
SUM(BYTES)RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
10 Full *24.54M* DISK 00:00:04 10-JUN-10
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142437
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
List of Datafiles in backup set 10
File LV Type Ckp SCN Ckp Time Name
6 Full 577669 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
SQL> commit;
Commit complete.RMAN> backup datafile 6 format 'after commit.backup';
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
11 Full *24.54M* DISK 00:00:02 10-JUN-10
BP Key: 11 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142541
Piece Name: /home/oracle/product/11/Db_1/dbs/after commit.backup
List of Datafiles in backup set 11
File LV Type Ckp SCN Ckp Time Name
6 Full 577705 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
SQL> alter system archive log current;
System altered.
SQL> commit;
Commit complete.
SQL> select count(*) from testundo;
COUNT(*)
100000
SQL> delete from testundo;
100000 rows deleted.
SQL> commit;
Commit complete.
SQL> insert into testundo values(1);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system flush buffer_cache;
System altered.RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
13 Full *11.03M* DISK 00:00:01 10-JUN-10
BP Key: 13 Status: AVAILABLE Compressed: NO Tag: TAG20100610T143359
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
List of Datafiles in backup set 13
File LV Type Ckp SCN Ckp Time Name
6 Full 578410 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
RMAN>
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 393375744 bytes
Fixed Size 1300156 bytes
Variable Size 352323908 bytes
Database Buffers 33554432 bytes
Redo Buffers 6197248 bytes
Database mounted.
Database opened.
SQL> RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
14 Full *600.00K* DISK 00:00:02 10-JUN-10
BP Key: 14 Status: AVAILABLE Compressed: NO Tag: TAG20100610T152843
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
List of Datafiles in backup set 14
File LV Type Ckp SCN Ckp Time Name
6 Full 580347 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
Thanks in advance
Turkel

Hi Turkel,
The space used for undo is also related to the undo retention setting.
As it seems you do a test update and proceed with backups on:
- 14:24:37 (-> 25M)
- 14:25:41 (-> 25M)
- 14:33:59 (-> 11M)
- 15:28:43 (-> 600K)
The first two backups probably are still within the undo retention period for the update.
The third backup shows a partly empty undo (is your setting 900?).
The last falls outside the retention period for the update resulting in the small backup size.
Regards,
Tycho

Creating Standby From RMAN Compressed backup taken on Primary ....

I am creating a Standby from RMAN Compressed backup taken on Primary.
On Primary, I have taken Compressed backup as follows:
RMAN> run
allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG format '/dboracle/orbit_pr_bkp/primary_%U';
backup current controlfile for standby format '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
oracle@apl06635orbvu1:/dboracle/orbit_pr_bkp>ls -ltr
total 51652
-rw-r----- 1 oracle dba 11972608 Jan 7 13:45 primary_0tm1h32n_1_1
-rw-r----- 1 oracle dba 15762432 Jan 7 13:45 primary_0sm1h32n_1_1
-rw-r----- 1 oracle dba 16785920 Jan 7 13:45 primary_0rm1h32n_1_1
-rw-r----- 1 oracle dba 1088000 Jan 7 13:45 primary_0um1h32v_1_1
-rw-r----- 1 oracle dba 32768 Jan 7 13:45 primary_12m1h33r_1_1
-rw-r----- 1 oracle dba 7143424 Jan 7 13:47 primary_cntl.bkp
On Standby, I restored the control file as below:
RMAN> restore standby controlfile from '/dboracle/orbit_pr_bkp/primary_cntl.bkp';
Starting restore at 10-JAN-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
output filename=/dboracle/orbit_dr/oradata/ORBIT_DR/controlfile/o1_mf_6lo6nwfr_.ctl
output filename=/dboracle/orbit_dr/flash_recovery_area/ORBIT_DR/controlfile/o1_mf_6lo6nwky_.ctl
Finished restore at 10-JAN-11
But, When I am trying to restore the datafiles, RMAN is throwing error:
RMAN> run {
allocate channel d1 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
allocate channel d2 type disk format '/dboracle/orbit_pr_bkp/primary_%U';
restore database;
2> 3> 4> 5>
released channel: ORA_DISK_1
allocated channel: d1
channel d1: sid=155 devtype=DISK
allocated channel: d2
channel d2: sid=151 devtype=DISK
Starting restore at 10-JAN-11
released channel: d1
released channel: d2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 01/10/2011 05:38:56
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
What would be the correct RMAN command?
Regards, Anirban

After your RESTORE the (standby) controlfile, you must MOUNT the database instance with "ALTER DATABASE MOUNT".
You can also then query the controlfile with a "LIST BACKUP" or "LIST BACKUP SUMMARY" in RMAN to see if the deseired backups have been cataloged in the controlfile.
Don't specify the format for the ALLOCATE CHANNEL when you RESTORE DATABASE. In fact, you don't need to ALLOCATE CHANNEL at all when the device type is the default value of DISK if your are on 10gR2 or above.
Hemant K Chitale

Rman hot backup

hello
i am using rman hot backup script to take backup database everyday but the problem is it is working but not deleting old backup older than 2 days .
also i have question .. my database is in archive log mode and everyday about 6-7 .arch files generating in my archive directory.
it is not deleting the old files but generating new files everyday so adding up to the space.
SQL> show parameter archive
NAME TYPE VALUE
archive_lag_target integer 0
log_archive_config string
log_archive_dest string /u03/archive_logs/DEVL
log_archive_dest_1 string
also should i set dest_1 as archive location or just log_archive_dest
whats is the difference.?
my rman script is
RMAN Hot backup.unix script
The RMAN hot backup script rman_backup.sh:
# !/bin/bash
# Declare your environment variables
export ORACLE_SID=DEVL
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1
export PATH=$PATH:${ORACLE_HOME}/bin
# Start the rman commands
rman target=/ << EOF
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/backup/autobackup_control_file%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
run {
allocate channel d1 type disk;
allocate channel d2 type disk;
allocate channel d3 type disk;
allocate channel d4 type disk;
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
CROSSCHECK BACKUP;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/u03/backup/databasefiles_%d_%u_%s_%T';
sql 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/u03/backup/archivelogs_%d_%u_%s_%T' DELETE INPUT;
BACKUP AS COMPRESSED BACKUPSET CURRENT CONTROLFILE FORMAT '/u03/backup/controlfile_%d_%u_%s_%T';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
EXIT;
EOF
thanks

Ahmer Mansoor wrote:
RMAN never deletes the Backups unless there is a space pressure in the Recovery Area. Instead it marks the Backups as OBSOLETE based on Retention Policy (in your case it is 2 Days),
To confirm it SET DB_RECOVERY_FILE_DEST_SIZE to some smaller value, the RMAN will remove all the Obsolete Backups automatically to reclaim space.Be very careful with this. If you generate a LOT of archivelog files and you exceed this size, on the next archivelog switch your database will hang with "cannot continue until archiver freed". RMAN will not automatically remove anything. RMAN only removes stuff when you program it in your script.
See:
http://docs.oracle.com/cd/E14072_01/backup.112/e10642/rcmconfb.htm#insertedID4 Retention Policy (recovery window or redundancy)
things like:
set retention window and number of copies
crosscheck backup
delete obsolete <-- delete old, redundant, no longer necessary backups/archivelogs
delete expired <-- NOTE: If you manually delete files and do not execute delete expired (missing file), the DB_RECOVERY_FILE_DEST_SIZE remains the same. So, you can clean out the space and oracle will still say the location is "full".
Understand that if you also set this parameter too small and your backup recovery window/redundancy are incorrectly set, you can also exhaust the "logical" space of this location again, putting your database at risk. Your parameter could be set to 100G on a 400G file system and even though you have 300G available, Oracle will see the limit of this parameter.
My suggestion, get in a DEV/TEST environment and test to see how to best configure your environment for RMAN database backups/control file, archivelog backups also taking into consideration OS tape backup solutions. I always configure DISK for RMAN backups, then have some other tape backup utility sweep those locations to tape ensuring that I have sufficient backups to reconstitute my database - I also include a copy of the init.ora file, password file as well as the spfile backup in this location.
>
In case of Archivelogs, It is better to create and execute a Purge Job to remove Archivelogs after backup them on tape.I almost agree. I try to keep all archivelogs necessary for recovery from last full backup online. I try to keep a full backup online as well. much faster at restoring stuff instead of trying to locate it on tape.

Cloning DB on a different server from RMAN Tape backup

RDBMS version           : 11.2.0.2 on Solaris 10
Media Management Layer : Netbackup v7
I have done only backups to Tape. I have never done restore,recovery from Tape.
We have a production DB named NEHPROD running on server qualmh214. Every Monday morning an RMAN Full backup for NEHPROD is taken to Tape.
Production server : qualmh214        DB Name:NEHPROD
run
ALLOCATE CHANNEL c1 TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=qualmh214,NB_ORA_POLICY=qualmh214_rman,NB_ORA_SERV=qualmh238,NB_ORA_SCHED=Daily';
backup database   FORMAT 'NEHPROD_%d_%U_%t.rbk' tag='NEHPROD_full';
}I need to create a Test DB in a different server (qualmh199) by restoring directly from NEHPROD's Full backup in tape .
From qualmh199, how can I connect to the Tape Media server ?
Even If I do connect to the Tape media server, how can i get access to tape backups of another DB? In the RMAN run block you can't specify a DB name. Right?
Even if I get access to another DB's backup , How can i specify which Date's Full backup I need to use to restore ?

From qualmh199, how can I connect to the Tape Media server ?You have to allocate channels to tape & need to mention NB parameters as example below.
in RMAN script
ALLOCATE CHANNEL CH1 DEVICE TYPE SBT_TAPE PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64';
SEND 'NB_ORA_SERV=<server.com>, NB_ORA_CLIENT=<target.server>';
Even If I do connect to the Tape media server, how can i get access to tape backups of another DB? In the RMAN run block you can't specify a DB name. Right?If the libraries are installed and you able to perform, you can go for either duplicate database or simple RMAN restore. You can mention other DB names also
Ex: duplicate target database to 'test';
Even if I get access to another DB's backup , How can i specify which Date's Full backup I need to use to restore ?You can mention TAG's if you are using RMAN restore.

Error in RMAN TAPE BACKUP

Dear Gurus,
I got the following error in RMAN TAPE backup.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on default channel at 09/20/2011 02:36:58
ORA-15028: ASM file '+ASMFLASH/gcprod/archivelog/2011_09_15/thread_2_seq_55857.2176.761912673' not dropped; currently being accessed
RMAN>
Recovery Manager complete.my RMAN BACKUP Script is:
rman target sys/*****@gcprod1 nocatalog << EOF
spool log to $v_bdest/clean_catalog_TAPE.log append;
run {
allocate channel c1 type 'sbt_tape' parms
'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt)';
#crosscheck backupset;
#crosscheck copy;
#crosscheck archivelog all;
# included on 21Jan2011 at 9:18 PM
#delete noprompt expired backup;
delete noprompt obsolete;
#delete noprompt expired archivelog all;
# included on 21Jan2011 at 9:18 PM
release channel c1;
exit
EOFMy RMAN RETENTION POLICY IS:
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/app/oracle/product/10.2.0.1/db_1/dbs/snapcf_gcprod1.f';According to retention policy archivelogs of past 3 days should be present rest and all , i have written a script to delete and it is performing well from past 6 months, but now recently we got this error
we have enough archivelog space.
and the archive log pointing in this error is on 15th september archivelog.....today date is 20th september....
My archive log was stored in asm .... i went there and saw that still 15th september archivelogs are present there.
Please help me regarding this
Regards,
Vamsi.....

For RMAN topics, please use: {forum:id=74}.

Rman hot backup script gives error in R12.

hi experts
i m facing following prob when run the backup script. 1 day before the same script runs correctily but now it gives me error at the allocatioion of channel rest of command run correctly.
[root@testerp rman_log]# cat UAT_daily_rman_hot_bkp_01-11-14_140301.log
-bash: /root/.bash_profile: Permission denied
Recovery Manager: Release 11.1.0.7.0 - Production on Sat Jan 11 14:03:01 2014
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: UAT (DBID=2855851979)
connected to recovery catalog database
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "end-of-file": expecting one of: "allocate, alter, advise, backup, beginline, blockrecover, catalog, change, copy, convert, crosscheck, configure, duplicate, debug, delete, execute, endinline, flashback, host, mount, open, plsql, recover, release, replicate, report, restore, resync, repair, }, set, setlimit, sql, switch, startup, shutdown, send, show, transport, validate"
RMAN-01007: at line 12 column 1 file: standard input
RMAN>
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "for"
RMAN-01008: the bad identifier was: c2
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "for"
RMAN-01008: the bad identifier was: c3
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "for"
RMAN-01008: the bad identifier was: c4
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
Starting backup at 11-JAN-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=362 device type=DISK
channel ORA_DISK_1: starting incremental level 1 datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00021 name=/d06/UAT/proddata/a_txn_data06.dbf
input datafile file number=00392 name=/d06/UAT/db/apps_st/data/a_txn_data01.dbf
input datafile file number=00401 name=/d06/UAT/db/apps_st/data/a_txn_data02.dbf
input datafile file number=00402 name=/d06/UAT/db/apps_st/data/a_txn_data03.dbf
input datafile file number=00022 name=/d06/UAT/proddata/a_txn_data07.dbf
input datafile file number=00014 name=/d06/UAT/db/apps_st/data/a_txn_data04.dbf
input datafile file number=00020 name=/d06/UAT/proddata/a_txn_data05.dbf
input datafile file number=00011 name=/d06/UAT/db/apps_st/data/sysaux01.dbf
input datafile file number=00018 name=/d06/UAT/db/apps_st/data/sysaux02.dbf
input datafile file number=00023 name=/d06/UAT/proddata/a_txn_data08.dbf
input datafile file number=00379 name=/d06/UAT/db/apps_st/data/undo01.dbf
input datafile file number=00024 name=/d06/UAT/proddata/sysaux03.dbf
input datafile file number=00025 name=/d06/UAT/proddata/sysaux04.dbf
input datafile file number=00033 name=/d06/UAT/proddata/a_txn_ind11.dbf
input datafile file number=00029 name=/d06/UAT/proddata/a_txn_ind09.dbf
input datafile file number=00030 name=/d06/UAT/proddata/a_txn_ind10.dbf
input datafile file number=00015 name=/d06/UAT/db/apps_st/data/a_txn_ind06.dbf
input datafile file number=00026 name=/d06/UAT/db/apps_st/data/a_txn_ind07.dbf
input datafile file number=00028 name=/d06/UAT/db/apps_st/data/a_txn_ind08.dbf
input datafile file number=00393 name=/d06/UAT/db/apps_st/data/a_txn_ind01.dbf
input datafile file number=00403 name=/d06/UAT/db/apps_st/data/a_txn_ind02.dbf
input datafile file number=00404 name=/d06/UAT/db/apps_st/data/a_txn_ind03.dbf
input datafile file number=00405 name=/d06/UAT/db/apps_st/data/a_txn_ind04.dbf
input datafile file number=00406 name=/d06/UAT/db/apps_st/data/a_txn_ind05.dbf
input datafile file number=00400 name=/d06/UAT/db/apps_st/data/a_media01.dbf
input datafile file number=00353 name=/d06/UAT/db/apps_st/data/system08.dbf
input datafile file number=00013 name=/d06/UAT/db/apps_st/data/system12.dbf
input datafile file number=00352 name=/d06/UAT/db/apps_st/data/system09.dbf
input datafile file number=00394 name=/d06/UAT/db/apps_st/data/a_ref01.dbf
input datafile file number=00407 name=/d06/UAT/db/apps_st/data/a_ref02.dbf
input datafile file number=00396 name=/d06/UAT/db/apps_st/data/a_summ01.dbf
input datafile file number=00395 name=/d06/UAT/db/apps_st/data/a_int01.dbf
input datafile file number=00008 name=/d06/UAT/db/apps_st/data/a_queue02.dbf
input datafile file number=00027 name=/d06/UAT/db/apps_st/data/a_queue03.dbf
input datafile file number=00031 name=/d06/UAT/db/apps_st/data/a_queue04.dbf
input datafile file number=00399 name=/d06/UAT/db/apps_st/data/a_queue01.dbf
input datafile file number=00001 name=/d06/UAT/db/apps_st/data/system01.dbf
input datafile file number=00002 name=/d06/UAT/db/apps_st/data/system02.dbf
input datafile file number=00003 name=/d06/UAT/db/apps_st/data/system03.dbf
input datafile file number=00004 name=/d06/UAT/db/apps_st/data/system04.dbf
input datafile file number=00005 name=/d06/UAT/db/apps_st/data/system05.dbf
input datafile file number=00398 name=/d06/UAT/db/apps_st/data/a_archive01.dbf
input datafile file number=00295 name=/d06/UAT/db/apps_st/data/system06.dbf
input datafile file number=00351 name=/d06/UAT/db/apps_st/data/system07.dbf
input datafile file number=00354 name=/d06/UAT/db/apps_st/data/system11.dbf
input datafile file number=00288 name=/d06/UAT/db/apps_st/data/system10.dbf
input datafile file number=00012 name=/d06/UAT/db/apps_st/data/apps_ts_tools01.dbf
input datafile file number=00016 name=/d06/UAT/db/apps_st/data/a_ref03.dbf
input datafile file number=00019 name=/d06/UAT/db/apps_st/data/MLSEIGL01.dbf
input datafile file number=00032 name=/d06/UAT/db/apps_st/data/RMAN01.dbf
input datafile file number=00397 name=/d06/UAT/db/apps_st/data/a_nolog01.dbf
input datafile file number=00314 name=/d06/UAT/db/apps_st/data/portal01.dbf
input datafile file number=00017 name=/d06/UAT/db/apps_st/data/a_int02.dbf
input datafile file number=00006 name=/d06/UAT/db/apps_st/data/ctxd01.dbf
input datafile file number=00010 name=/d06/UAT/db/apps_st/data/olap.dbf
input datafile file number=00009 name=/d06/UAT/db/apps_st/data/odm.dbf
input datafile file number=00007 name=/d06/UAT/db/apps_st/data/owad01.dbf
channel ORA_DISK_1: starting piece 1 at 11-JAN-14
[root@testerp rman_log]#
backup script is below:
in this script it returns error only at the channel allocaition rest of all backup command i run manually or with scirpt it runs correctly.4
i m not able to know why it returns error only at challnel allocation 1 day before it runs correctly.
[orauat@testerp rman_script]$ cat rman_backup.sh
#!/bin/sh
#ORACLE_SID=UAT
#BACKUP_START_TIME='date +"%y""%m""%d"_"%H""%M""%S"'
#ORACLE_HOME=/d06/UAT/db/tech_st/11.1.0
#PATH=$PATH:${ORACLE_HOME}:${ORACLE_HOME}/bin
#export ORACLE_SID
#export ORACLE_HOME
#export PATH
/d06/UAT/db/tech_st/11.1.0/bin/rman catalog rman/rman007 target sys/sysuat <<EOF
run
allocate channel c1 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_Arch_%c_%U';
sql 'alter system switch logfile';
sql 'alter system switch logfile';
sql 'alter system archive log current';
delete expired archivelog all;
crosscheck archivelog all;
backup archivelog all;
delete noprompt archivelog all completed before 'sysdate-4' backed up 1 times to disk;
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
backup incremental level 1 database;
delete expired backup device type disk;
delete obsolete device type disk;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
exit
EOF
regards
pritesh ranjan

yes the script is edited
i have add some command line and edit it for take the full backup level=0 on the same directory with different formant name but location is same.
can i take full backup level 0 and incremental backup level 1 in the same directory with the different format name.
for exp:
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
i allocate these three channel for incremental level 1 backup;
the backup is done successfully without any error.
after that i have change
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
backup database incremental level 0
after doing the above changes it get the error. with the channel location.
i have to schedule daily incremental backup level 1 and weekly full backup level 0.
plz suggest me i have to take incremental 1 and full incremental level 0 backup on seperate directory for different format name.
regards
pritesh ranjan

Rman merge backup

Similar Messages

Maybe you are looking for