Tom, I have seen that our RMAN backup in quite intrusive - means the query performance on the database deteriorates considerably during the RMAN backup. Is this normal? What can I do to find out more about the bottlenecks? Any suggestions on how to improve it? Thaks.

I could not compare RMAN vs. hot backup on this database. This is on RMAN for quite sometime. Because of tap server availability problems, our hotbackup schedule overlaps with peak usage time for our overseas users. And they have been complaining about performance deterioration. The queries that take 2 mins would take 15 mins during backup. (But some other queries does not show thismuch variation.).

I wanted to know from you how to find out more about what is happening. And what would be the general guidelines for RMAN tuning. Thank you.

Tom, After I created whole database backup using rman for the first time, when I checked "report need backup", it lists the readonly datafile. Why RMAN did not make a backup of readonly datafile? I thought for the first time when I take a whole database backup, read only datafiles should have been backup. Thanks.

RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 3;
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 SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\ORA92\DATABASE\SNCFPRACTICE.OR
A'; # default


RMAN> backup database
2> format 'C:\oracle\admin\rmanbackup\df_%d_%s_%p.bus';

Starting backup at 01-JUL-03
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00008 name=C:\ORACLE\ORADATA\PRACTICE\TOOLS01.DBF
input datafile fno=00010 name=C:\ORACLE\ORADATA\PRACTICE\XDB01.DBF
input datafile fno=00012 name=C:\ORACLE\ORADATA\PRACTICE\FREELIST_DEMO01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\PRACTICE\INDX01.DBF
input datafile fno=00009 name=C:\ORACLE\ORADATA\PRACTICE\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 01-JUL-03
channel ORA_DISK_2: starting full datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00002 name=C:\ORACLE\ORADATA\PRACTICE\UNDOTBS01.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\PRACTICE\EXAMPLE01.DBF
input datafile fno=00003 name=C:\ORACLE\ORADATA\PRACTICE\CWMLITE01.DBF
input datafile fno=00004 name=C:\ORACLE\ORADATA\PRACTICE\DRSYS01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\PRACTICE\ODM01.DBF
channel ORA_DISK_2: starting piece 1 at 01-JUL-03
channel ORA_DISK_3: starting full datafile backupset
channel ORA_DISK_3: specifying datafile(s) in backupset
including current SPFILE in backupset
including current controlfile in backupset
input datafile fno=00001 name=C:\ORACLE\ORADATA\PRACTICE\SYSTEM01.DBF
input datafile fno=00013 name=C:\ORACLE\ORADATA\PRACTICE\DUMMY01.DBF
input datafile fno=00011 name=C:\ORACLE\ORADATA\PRACTICE\READONLY01.DBF
channel ORA_DISK_3: starting piece 1 at 01-JUL-03
channel ORA_DISK_1: finished piece 1 at 01-JUL-03
piece handle=C:\ORACLE\ADMIN\RMANBACKUP\DF_PRACTICE_1_1.BUS comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:15
channel ORA_DISK_2: finished piece 1 at 01-JUL-03
piece handle=C:\ORACLE\ADMIN\RMANBACKUP\DF_PRACTICE_2_1.BUS comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:02:58
channel ORA_DISK_3: finished piece 1 at 01-JUL-03
piece handle=C:\ORACLE\ADMIN\RMANBACKUP\DF_PRACTICE_3_1.BUS comment=NONE
channel ORA_DISK_3: backup set complete, elapsed time: 00:03:03
Finished backup at 01-JUL-03

RMAN> list backupset;


List of Backup Sets
===================

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
1 Full 33M DISK 00:00:43 01-JUL-03
BP Key: 1 Status: AVAILABLE Tag: TAG20030701T183645
Piece Name: C:\ORACLE\ADMIN\RMANBACKUP\DF_PRACTICE_1_1.BUS
List of Datafiles in backup set 1
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- --------- ----
6 Full 3949506 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\INDX01.DBF
8 Full 3949506 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\TOOLS01.DBF
9 Full 3949506 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\USERS01.DBF
10 Full 3949506 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\XDB01.DBF
12 Full 3949506 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\FREELIST_DEMO01.D
BF

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
2 Full 247M DISK 00:02:54 01-JUL-03
BP Key: 2 Status: AVAILABLE Tag: TAG20030701T183645
Piece Name: C:\ORACLE\ADMIN\RMANBACKUP\DF_PRACTICE_2_1.BUS
List of Datafiles in backup set 2
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- --------- ----
2 Full 3949589 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\UNDOTBS01.DBF
3 Full 3949589 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\CWMLITE01.DBF
4 Full 3949589 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\DRSYS01.DBF
5 Full 3949589 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\EXAMPLE01.DBF
7 Full 3949589 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\ODM01.DBF

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
3 Full 344M DISK 00:02:55 01-JUL-03
BP Key: 3 Status: AVAILABLE Tag: TAG20030701T183645
Piece Name: C:\ORACLE\ADMIN\RMANBACKUP\DF_PRACTICE_3_1.BUS
SPFILE Included: Modification time: 29-JUN-03
List of Datafiles in backup set 3
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- --------- ----
1 Full 3949670 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\SYSTEM01.DBF
11 Full 201816 05-JUN-03 C:\ORACLE\ORADATA\PRACTICE\READONLY01.DBF
13 Full 3949670 01-JUL-03 C:\ORACLE\ORADATA\PRACTICE\DUMMY01.DBF

RMAN> report need backup;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of files with less than 1 redundant backups
File #bkps Name
---- ----- -----------------------------------------------------
11 0 C:\ORACLE\ORADATA\PRACTICE\READONLY01.DBF

"how many redundant backups of that file do you have? (none)"

for that matter I should not have any redundant backup of other files as well as this was my first backup of all files. Why other files are not listed in "report need backup" command? Hope I understood your point. If not, apologies. Thanks.

<quote>I guess it might be due to the extremely low SCN relative to the rest

Try this -- clean out the backups, make the tablespace read/write then read only
-- do it again. If the file is not reported, that was it. <quote>

I tried just like you said. Please see below.


RMAN> backup database;

Starting backup at 02-jul-2003 10:52:31
using channel ORA_DISK_1
using channel ORA_DISK_2
using channel ORA_DISK_3
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00008 name=C:\ORACLE\ORADATA\PRACTICE\TOOLS01.DBF
input datafile fno=00010 name=C:\ORACLE\ORADATA\PRACTICE\XDB01.DBF
input datafile fno=00012 name=C:\ORACLE\ORADATA\PRACTICE\FREELIST_DEMO01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\PRACTICE\INDX01.DBF
input datafile fno=00009 name=C:\ORACLE\ORADATA\PRACTICE\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 02-jul-2003 10:52:36
channel ORA_DISK_2: starting full datafile backupset
channel ORA_DISK_2: specifying datafile(s) in backupset
input datafile fno=00002 name=C:\ORACLE\ORADATA\PRACTICE\UNDOTBS01.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\PRACTICE\EXAMPLE01.DBF
input datafile fno=00003 name=C:\ORACLE\ORADATA\PRACTICE\CWMLITE01.DBF
input datafile fno=00004 name=C:\ORACLE\ORADATA\PRACTICE\DRSYS01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\PRACTICE\ODM01.DBF
channel ORA_DISK_2: starting piece 1 at 02-jul-2003 10:52:39
channel ORA_DISK_3: starting full datafile backupset
channel ORA_DISK_3: specifying datafile(s) in backupset
including current SPFILE in backupset
including current controlfile in backupset
input datafile fno=00001 name=C:\ORACLE\ORADATA\PRACTICE\SYSTEM01.DBF
input datafile fno=00013 name=C:\ORACLE\ORADATA\PRACTICE\DUMMY01.DBF
input datafile fno=00011 name=C:\ORACLE\ORADATA\PRACTICE\READONLY01.DBF
channel ORA_DISK_3: starting piece 1 at 02-jul-2003 10:53:26
channel ORA_DISK_1: finished piece 1 at 02-jul-2003 10:53:41
piece handle=D:\RMANBACKUP\DF_PRACTICE_32_1.BUS comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:06
channel ORA_DISK_2: finished piece 1 at 02-jul-2003 10:55:56
piece handle=D:\RMANBACKUP\DF_PRACTICE_33_1.BUS comment=NONE
channel ORA_DISK_2: backup set complete, elapsed time: 00:03:20
channel ORA_DISK_3: finished piece 1 at 02-jul-2003 10:56:21
piece handle=D:\RMANBACKUP\DF_PRACTICE_34_1.BUS comment=NONE
channel ORA_DISK_3: backup set complete, elapsed time: 00:03:41
Finished backup at 02-jul-2003 10:56:21

RMAN> list backupset;


List of Backup Sets
===================

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ --------------------
24 Full 40M DISK 00:00:56 02-jul-2003 10:53:31
BP Key: 24 Status: AVAILABLE Tag: TAG20030702T105234
Piece Name: D:\RMANBACKUP\DF_PRACTICE_32_1.BUS
List of Datafiles in backup set 24
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- -------------------- ----
6 Full 4023867 02-jul-2003 10:52:37 C:\ORACLE\ORADATA\PRACTICE\INDX01
.DBF
8 Full 4023867 02-jul-2003 10:52:37 C:\ORACLE\ORADATA\PRACTICE\TOOLS0
1.DBF
9 Full 4023867 02-jul-2003 10:52:37 C:\ORACLE\ORADATA\PRACTICE\USERS0
1.DBF
10 Full 4023867 02-jul-2003 10:52:37 C:\ORACLE\ORADATA\PRACTICE\XDB01.
DBF
12 Full 4023867 02-jul-2003 10:52:37 C:\ORACLE\ORADATA\PRACTICE\FREELI
ST_DEMO01.DBF

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ --------------------
25 Full 247M DISK 00:03:10 02-jul-2003 10:55:46
BP Key: 25 Status: AVAILABLE Tag: TAG20030702T105234
Piece Name: D:\RMANBACKUP\DF_PRACTICE_33_1.BUS
List of Datafiles in backup set 25
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- -------------------- ----
2 Full 4023869 02-jul-2003 10:52:40 C:\ORACLE\ORADATA\PRACTICE\UNDOTB
S01.DBF
3 Full 4023869 02-jul-2003 10:52:40 C:\ORACLE\ORADATA\PRACTICE\CWMLIT
E01.DBF
4 Full 4023869 02-jul-2003 10:52:40 C:\ORACLE\ORADATA\PRACTICE\DRSYS0
1.DBF
5 Full 4023869 02-jul-2003 10:52:40 C:\ORACLE\ORADATA\PRACTICE\EXAMPL
E01.DBF
7 Full 4023869 02-jul-2003 10:52:40 C:\ORACLE\ORADATA\PRACTICE\ODM01.
DBF

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ --------------------
26 Full 344M DISK 00:03:38 02-jul-2003 10:56:18
BP Key: 26 Status: AVAILABLE Tag: TAG20030702T105234
Piece Name: D:\RMANBACKUP\DF_PRACTICE_34_1.BUS
SPFILE Included: Modification time: 29-jun-2003 21:06:24
List of Datafiles in backup set 26
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- -------------------- ----
1 Full 4024024 02-jul-2003 10:53:27 C:\ORACLE\ORADATA\PRACTICE\SYSTEM
01.DBF
11 Full 4023774 02-jul-2003 10:51:59 C:\ORACLE\ORADATA\PRACTICE\READON
LY01.DBF
13 Full 4024024 02-jul-2003 10:53:27 C:\ORACLE\ORADATA\PRACTICE\DUMMY0
1.DBF

RMAN> report need backup;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of files with less than 1 redundant backups
File #bkps Name
---- ----- -----------------------------------------------------

RMAN>

Tom, As RMAN uses server processes on the server (where the database is) for its operations, is there a command that I can use in unix to check these processes? does ps -ef show? Also, when I open a Rman session, will there be a dedicated server process created for the session? Thanks.

Tom, my understanding is that target database controlfile is the MASTER and by default if I used RMAN to backup, the rman info is updated in the target database controlfile whether I use catalog or not. Is it correct?

Is there any circumstance that info from catalog is transferred to the target database controlfile?

If I use resync catalog, the rman catalog only PULLS info from the target database. There is no PUSH and PULL. Is it correct? Thanks much.

How much of overhead in running BACKUP VALIDATE DATABASE and RESTORE VALIDATE DATABASE commands to check for block corruptions using RMAN? Can I run these commands anytime? Any suggestion would be appreciated? Thanks.

Tom, I practiced the command as shown below. It appears like it is touching the live datafiles. Please review and clarify. Thanks.

RMAN> backup validate database;

Starting backup at 23-OCT-03
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current SPFILE in backupset
including current controlfile in backupset
input datafile fno=00009 name=/home4/user20/ORADATA/u05/part_01.dbf
input datafile fno=00003 name=/home4/user20/ORADATA/u03/users_01.dbf
input datafile fno=00004 name=/home4/user20/ORADATA/u03/indx_01.dbf
input datafile fno=00001 name=/home4/user20/ORADATA/u01/system_01.dbf
input datafile fno=00005 name=/home4/user20/ORADATA/u02/sample_01.dbf
input datafile fno=00002 name=/home4/user20/ORADATA/u02/undo1_01.dbf
input datafile fno=00006 name=/home4/user20/ORADATA/u01/query_data_01.dbf
input datafile fno=00008 name=/home4/user20/ORADATA/u04/corrupt1.dbf
input datafile fno=00010 name=/home4/user20/ORADATA/u04/undo02_01.dbf
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:37
Finished backup at 23-OCT-03

I also had the problem of poor performance during rman backups. I ended up (reading the manual) and came up with the following command that goes after you select a channel.
setlimit channel c1 readrate 20;
I had to experiment to find the "right" readrate for my system. By using this command, you slow down the backup considerably, but users noticed very liitle performance change.

Where is maxpiecesize useful? If I have a filesystem that has 5 disks each 2G size. If I say,

allocate channel c1 device type disk maxpiecesize=2G;
backup datafile 2;

assuming the datafile size is 10G, will rman backup the datafile 2 in 5 pieces and each piece will be in each of 5 disks? Does it mean that backupset will span disks? Thanks.

Tom, can I tell rman to put each piece in different location, say piece 1 in u01/BACKUP/one_dir/, piece 2 in u02/BACKUP/another_dir and so on? If so, how can it be done? Thanks.

Tom, please see below. RMAN puts all of backup pieces in one location. How do I tell RMAN to put the pieces in different locations? In otherwords, can backup set span disks? Thanks.

RMAN> run
2> {
3> allocate channel c1 device type disk format 'D:\rmanbackup\df_%s_%p.bak' maxpiecesize=50K;
4> allocate channel c2 device type disk format 'C:\rmanbackup\df_%s_%p.bak' maxpiecesize=50K;
5> backup datafile 'C:\oracle\oradata\practice\dummy01.dbf';
6> }

allocated channel: c1
channel c1: sid=16 devtype=DISK

allocated channel: c2
channel c2: sid=17 devtype=DISK

Starting backup at 25-OCT-03
channel c1: starting full datafile backupset
channel c1: specifying datafile(s) in backupset
input datafile fno=00013 name=C:\ORACLE\ORADATA\PRACTICE\DUMMY01.DBF
channel c1: starting piece 1 at 25-OCT-03
channel c1: finished piece 1 at 25-OCT-03
piece handle=D:\RMANBACKUP\DF_55_1.BAK comment=NONE
channel c1: starting piece 2 at 25-OCT-03
channel c1: finished piece 2 at 25-OCT-03
piece handle=D:\RMANBACKUP\DF_55_2.BAK comment=NONE
channel c1: starting piece 3 at 25-OCT-03
channel c1: finished piece 3 at 25-OCT-03
piece handle=D:\RMANBACKUP\DF_55_3.BAK comment=NONE
channel c1: starting piece 4 at 25-OCT-03
channel c1: finished piece 4 at 25-OCT-03
piece handle=D:\RMANBACKUP\DF_55_4.BAK comment=NONE
channel c1: starting piece 5 at 25-OCT-03
channel c1: finished piece 5 at 25-OCT-03
piece handle=D:\RMANBACKUP\DF_55_5.BAK comment=NONE
channel c1: backup set complete, elapsed time: 00:00:10
Finished backup at 25-OCT-03

Starting Control File and SPFILE Autobackup at 25-OCT-03
piece handle=C:\ORACLE\ORA92\DATABASE\C-2686660793-20031025-01 comment=NONE
Finished Control File and SPFILE Autobackup at 25-OCT-03
released channel: c1
released channel: c2

Tom, That example puts backupSET in different locations. My understanding is that within a backupset, we can ask rman to create more than one backuppiece by using maxpiecesize parameter. My question is, can rman place backupPIECE in different locations if a backupset contains say two or three pieces and each piece in different backup locations. I guess not. It appears like the usage of maxpiecesize is for restricting the size of the piece as some operating system has size limit for files. For example, old unix os has 2G file size limit. Is this why we have maxpiecesize clause in rman to restrict the piece size? I am trying to understand the usefulness of maxpiecesize. Sorry for bugging you on this issue. Thanks.

What is the easiest way, to find out what is the most recent time that one can restore it's database , given that a catalog database is been used.

(9.2)

Tom, does 9i R2 database installation have any support for backup to tape using RMAN without any additional purchase of media management software? I heard that Oracle provides Legato tape backup software that comes with the 9i installation? If this is true, can one backup to tape without doing any additional installation of software for tape backups? Thanks.

Tom,

(1) My understanding is that based on the retention policy, rman makes the backups obsolete. Is there a way to force rman to use these obsolete backups or once it is marked obsolete, the backups are useless?

(2) Also, if I used change ... keep sysdate+30 for example, to keep a particular backup overriding the retention policy, does Rman keep the record in the controlfile for 30 days even if the backup exceeds the control_file_record_keep_time? thanks.

This is what we do also.
Glad to know this method is just as 'legitimate' as writing to tape!

<quote>it is just a report, they are still there until you delete them<quote>

But, rman will not consider these obsolete bacups for restore. Right? Thanks.

Dear Tom,

Can I use the same snapshot controlfile to backup multiple databases(one after another) running on the same server?

The following RMAN script will be invoked from SHELL script loop(with different ORACLE_SID)
-----------RMAN Script Begin--------------------------------
set snapshot controlfile name to
'/u01/app/oracle/product/8.1.7/dbs/Rcatctrl.ctl';
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
backup
incremental level 0
skip inaccessible
tag hot_db_bk_level0
filesperset 5
format 'bk_%s_%p_%t'
(database);
}
-----------RMAN Script End---------------------------------

Version 8.1.7.3

If I do not specify the SNAPSHOT CONTROLFILE explicitly it is giving the following error.

RMAN-03006: non-retryable error occurred during execution of command: backup
RMAN-07004: unhandled exception during command execution on channel t1
RMAN-10035: exception raised in RPC: ORA-01580: error creating control backup file /dev/vx/rdsk/dbdg13/Rcatctrl.ctl
ORA-27040: skgfrcre: create error, unable to create file
SVR4 Error: 2: No such file or directory
RMAN-10031: ORA-1580 occurred during call to DBMS_BACKUP_RESTORE.CFILEMAKEANDUSESNAPSHOT


I don't know why it is looking for "/dev/vx/rdsk/dbdg13/Rcatctrl.ctl". I don't know where it got stored?
The directory "/dev/vx/rdsk/dbdg13" does not exist in this server.

Thanks
Sami

re. earlier post:

if you don't specify location, it goes to dbs, correct?
is this going to raw device?

/dev/vx/rdsk/dbdg13/Rcatctrl.ctl : or is it your volume manager issue? df -k should give you some information.

Tom, does it mean that whenever i backup to tape, it is considered a proxy copy as media management software is doing the backups for me? Thanks.

Dear Tom, Really sorry for bothering you.

<asktom>
but you should have to do it once, it'll
remember it in the control files -- so you could just use rman to go into each
"old, upgraded" instance and burn the name into them
</asktom>

When you say "burn the name", you mean run the follwoing command. Am I correct?

set snapshot controlfile name to
'/u01/app/oracle/product/8.1.7/dbs/Rcatctrl.ctl';

FIRST TIME I ran RMAN backup using the following script and it executed fine.

<FIRST_TIME>
-----------RMAN Script Begin--------------------------------
set snapshot controlfile name to
'/u01/app/oracle/product/8.1.7/dbs/Rcatctrl.ctl';
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
backup
incremental level 0
skip inaccessible
tag hot_db_bk_level0
filesperset 5
format 'bk_%s_%p_%t'
(database);
}
-----------RMAN Script End---------------------------------
</FIRST_TIME>



<SECOND_TIME>
-----------RMAN Script Begin--------------------------------
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
backup
incremental level 0
skip inaccessible
tag hot_db_bk_level0
filesperset 5
format 'bk_%s_%p_%t'
(database);
}
-----------RMAN Script End---------------------------------
</SECOND_TIME>
SECOND TIME I Took off
set snapshot controlfile name to
'/u01/app/oracle/product/8.1.7/dbs/Rcatctrl.ctl';
and got the below error again.

<Error>
RMAN-10035: exception raised in RPC: ORA-01580: error creating control backup
file /dev/vx/rdsk/dbdg13/Rcatctrl.ctl
ORA-27040: skgfrcre: create error, unable to create file
SVR4 Error: 2: No such file or directory
RMAN-10031: ORA-1580 occurred during call to
DBMS_BACKUP_RESTORE.CFILEMAKEANDUSESNAPSHOT
</Error>

Is there a way to check what is the SNAPSHOT CONTROLFILE name stored in control file(record)?

Thanks
Sami

RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME CLEAR

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "snapshot": expecting one of: "compatible"
RMAN-01007: at line 1 column 11 file: standard input

RMAN>

RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME CLEAR;

RMAN> SHOW SNAPSHOT CONTROLFILE NAME;

RMAN> CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/8.1.7/dbs/Rcatctrl.ctl';

If I used create controlfile syntax and recreated the controlfile in 9i, I loose all RMAN info. Is this the same behavior in 10g? Also, why does not oracle keep RMAN info after recreating the controlfile? Thanks.

Tom,

I was told there exist a configuration where I can store backup information in BOTH catalog and target database controlfile. However, as much as I have dug, I am unable to find such a configuration.

In essence, I was to perform:
rman target / catalog rman/rman@ran
and
rman target / nocatlog
in one rman session. Is this possible?

Thank you.

Tom, what is the advantage of using PIPE in rman backups? In what circumstances one would use PIPE to backup and restore? Thanks.

</code> http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmarchi.htm#457442 <code>
<Doc>
The Oracle9i server ensures that only one RMAN session accesses a snapshot control file at any point in time. This safeguard is necessary to ensure that two RMAN sessions do not interfere with each other's use of the snapshot control file.
</Doc>

ALLOCATE CHANNEL c1;
ALLOCATE CHANNEL c2;

Will it open 2 RMAN sessions?

Version 8i

Q1)
RMAN>REPORT obsolete
is giving long list of output.

How to capture RMAN>REPORT obsolete output in file (like
spool in SQL*Plus)

Q2)
What is the difference between "REPORT obsolete" and "REPORT obsolete orphan"

Q3) What could be wrong here
RMAN> allocate channel for maintenance type 'sbt_tape';

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: delete_06
RMAN-08500: channel delete_06: sid=63 devtype=SBT_TAPE
RMAN-08526: channel delete_06: VERITAS NetBackup for Oracle8 - Release 3.4GA (030800)

RMAN> crosscheck backup;

RMAN-03022: compiling command: XCHECK
RMAN-03023: executing command: XCHECK
RMAN-08074: crosschecked backup piece: found to be 'EXPIRED'
RMAN-08517: backup piece handle=bk_2576_1_500454332 recid=2514 stamp=500454334
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: XCHECK
RMAN-07004: unhandled exception during command execution on channel delete_06
RMAN-10035: exception raised in RPC: ORA-27191: sbtinfo2 returned error
Additional information: 2
RMAN-10031: ORA-27191 occurred during call to DBMS_BACKUP_RESTORE.VALIDATEBACKUPPIECE

RMAN>

Assuming I have a "FULL" backup of users01.dbf containing employees table that contains 1000 blocks of data. If I truncated employees table and then an incremental level 1 backup of users tablespace is taken, will RMAN include 1000 blocks that once contained data in the incremental backup? Thanks.

Tom,

The Oracle9i Recovery Manager User’s Guide defines a BACKUP SET...
"...A backup set is a complete set of backup pieces that make up a full or incremental backup of the objects specified in the BACKUP command..." [Page 5-13]

But when I run an RMAN 'backup database' command, I am getting several 'backup sets'. I appears that one backup set is being created for each channel open (I have the default configuration: "CONFIGURE DEVICE TYPE DISK PARALLELISM 8")

Therefore there are multiple "backup sets" within a single database "backup"

I have spent about an hour searching the documentation, metalink, AskTom, etc. but I have not seen anything which clearly defines this concept that there are multiple "backup sets" within a single rman "backup".

This may seem trivial, but in the interest of clear and robust definitions this seems confusing.
Would you please explain and/or comment?

Thanks,

Robert.

Forgot to say I am running version 9.2 database.

Hi Tom,

Here is my point more clearly...
Every night I take an rman database backup of the database and it produces, say, 10 backup sets. When I do a 'list backup', it lists hundreds of individual backup sets... but I don't care about each individual backup set... I want to know all the parts (backup sets, backup pieces) for a particular database backup.
I don't see anything in the commands or literature that groups these backup sets together so you know they all go with a single database backup.

Thanks!

Robert.

Thanks Tom,

It just seems that the set of files that make up a single database backup would be an important, logical concept (even the MAIN concept) which RMAN would recognize and define !?

Robert.

I guess "list backup summary" isn't what you are looking for?

Hi Bob,

'list backup SUMMARY' still does the same thing.... it provides no 'key' by which to identify all backup sets belonging to a single database backup.

In all fairness, the 'TAG' feature is doing this to some extent (although it appears to not be 'tagging' the control file backup).... Nevertheless, I still don't understand why RMAN doesn't include a simple, integrated 'header' that groups together ALL pieces (backup sets, backup pieces) of a single 'backup' command.

Thanks,

Robert.

Tom,

i got the below error when running in rman,

run {
allocate channel c1 type disk;
set until time = '2004-05-17:05:53:27';
restore tablespace users;
recover tablespace users;
}

RMAN> run {
2> allocate channel c1 type disk;
3> set until time = '2004-05-17:05:53:27';
4> restore tablespace users;
5> recover tablespace users;
6> }

allocated channel: c1
channel c1: sid=14 devtype=DISK

executing command: SET until clause
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 05/17/2004 18:25:50
ORA-01861: literal does not match format string

RMAN> exit

since i got the above error, i tried setting the env variable, but again there is some error... this is on NT
, it throws error. i need to set the env bcos i had run the script

C:\oracle\ora81b\bin>set NLS_DATE_FORMAT='YYYY-MM-DD:HH24:MI:SS'

C:\oracle\ora81b\bin>set NLS_LANG=american

C:\oracle\ora81b\bin>rman

Recovery Manager: Release 9.2.0.1.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

RMAN> connect catalog rec_cat/rec_cat@sai

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-04004: error from recovery catalog database: ORA-00604: error occurred at recursive SQL level 1
ORA-02248: invalid option for ALTER SESSION

RMAN> exit


Recovery Manager complete.

C:\oracle\ora81b\bin>set NLS_LANG
NLS_LANG=american

C:\oracle\ora81b\bin>set NLS_DATE_FORMAT
NLS_DATE_FORMAT='YYYY-MM-DD:HH24:MI:SS'

Please help me to proceed. thanks for your time and consideration

Tom,

Thanks, its working without giving quotes.

here again i have one doubt.


I did create few tables and experimented the full backup, recovery from rman - it worked without any error. i deleted a datafile and restored it successfully then 

SQL> select to_char( sysdate,'DD-MON-YY HH:MI:SS') from dual;

TO_CHAR(SYSDATE,'D
------------------
17-MAY-04 05:53:27

SQL> create table x (c1 number);

Table created.

SQL> select to_char( sysdate,'DD-MON-YY HH:MI:SS') from dual;

TO_CHAR(SYSDATE,'D
------------------
17-MAY-04 05:53:48

SQL> create table y(c2 varchar2(10));

Table created.

SQL> select to_char( sysdate,'DD-MON-YY HH:MI:SS') from dual;

TO_CHAR(SYSDATE,'D
------------------
17-MAY-04 05:54:05


I wanted to get only table x created by me, not Y .....so i tried the below script....

C:\oracle\ora81b\bin>rman

Recovery Manager: Release 9.2.0.1.0 - Production

Copyright (c) 1995, 2002, Oracle Corporation.  All rights reserved.

RMAN> connect catalog rec_cat/rec_cat@sai

connected to recovery catalog database

RMAN> connect target /

connected to target database: ORACLE (DBID=1399478558)

RMAN>   run {
2>   allocate channel c1 type disk;
3>   set until time = '17-MAY-04:05:53:48';
4>   restore tablespace users;
5>   recover tablespace users;
6>   }

allocated channel: c1
channel c1: sid=12 devtype=DISK

executing command: SET until clause
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of set command at 05/19/2004 10:25:20
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

RMAN> list incarnation of database;


List of Database Incarnations
DB Key  Inc Key DB Name  DB ID            CUR Reset SCN  Reset Time
------- ------- -------- ---------------- --- ---------- ----------
1       2       ORACLE   1363983330       YES 183768     2003-04-09:18:44:51
26      27      ORACLE   1399478558       YES 1          2004-05-17:14:31:58


whats wrong in my steps? ... did i miss any steps/concepts

thanks a lot
 
 

RMAN> allocate channel for maintenance type 'sbt_tape';

RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: delete
RMAN-08500: channel delete: sid=43 devtype=SBT_TAPE
RMAN-08526: channel delete: VERITAS NetBackup for Oracle - Release 4.5FP_3GA (2002121901)

RMAN> send 'NB_ORA_CLIENT=ora-server2';

RMAN-06421: sent command to channel: delete

RMAN> crosscheck backup of database;
... ...

RMAN> delete expired backup of database;

RMAN-03022: compiling command: delete expired
RMAN-03025: performing implicit partial resync of recovery catalog
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03023: executing command: delete expired
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: delete expired
RMAN-07004: unhandled exception during command execution on channel delete
RMAN-20502: DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK

RMAN> crosscheck backup of database;
... ...

RMAN> delete expired backup of database;

RMAN-03022: compiling command: delete expired
RMAN-03025: performing implicit partial resync of recovery catalog
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03023: executing command: delete expired
RMAN-03026: error recovery releasing channel resources
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03006: non-retryable error occurred during execution of command: delete expired
RMAN-07004: unhandled exception during command execution on channel delete
RMAN-20502: DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK

software:
Oracle8.1.7.0 + veritas Netbackup
Solaris8
problem:
How can I delete one specified expired proxy copy.
change proxy ... delete?
the syntax to proxy copy for the above statment should be?
for example:
List of Proxy Copies
Key File S Completion time Ckp SCN Ckp time Handle
------- ---- - --------------- ---------- --------------- ------
123399 1 X 25-MAY-04 283542928 2-MAY-04 bk_oradb_7235_5_527040180

Hi

I have been reading how to limit a backup set size. I read about maxsetsize and set limit channel XXX

What are the differences? I also read that we can play with filesperset parameters to limit backup set size as well, how :-?

cheers

Dear Tom,

I read the RMAN document but it didn't explain how to set "maxcorrupt" value.
<doc>
set maxcorrupt for datafile datafileSpec to integer sets a limit on the number of previously undetected physical block
corruptions that Oracle will allow in a specified datafile or list of datafiles (see "datafileSpec"). If a backup or copy command detects more than the specified number of corruptions, the command aborts. The default
limit is zero, meaning that RMAN tolerates no corrupt locks.
</doc>

Question
========
For example,

How to instruct RMAN to tolerate 5 corrupt blocks for datafile 3 to 7. How & where should I specify maxcorrupt value?

set maxcorrupt for datafile 3 to 7;

Thanks in advance

Tom,
Here's my problem. I recently inherited 12 8.1.6 databases which have been backed up periodically using RMAN/Netbackup for the last 4years or so. It so happens the actual tape retention is only set to 10days! And never has a RMAN "crosscheck" or "delete" ever been issued on these databases! The former DBA's simply backed up their databases and left it at that. No catalog maintanence was being performed.

So I'm now left with a catalog with scores of backup sets and pieces (with an 'AVAILABLE' status) which date back to year 2000, when in reality they don't exist on tape.

Question - Is it worth the while to do a "crosscheck backup" and "delete expired backup" on each target? A crosscheck with so many backup entries will take quite a long time. Besides having a "cleaner catalog", is there any pressing need for me to clean up the mess immediately?

Thanks for your time.

Hi Tom,
What is the difference between " delete expired backup of database" and "delete obsolete"?
Thanks...

Tom,
I've got a fundamental RMAN question. When I register a "new" target database to a catalog, I expect (wrongly) to see only one incarnation in the catalog. But that isn't true.

Why does the catalog of a "newly" registered target database store information about ALL the previous incarnations (of the target) as well? What is the logic behind this? It is not as if any of the previous incarnations or their backup information is stored in the catalog.

I think this is kinda misleading and confusing. It misleads a novice DBA "at first sight" into thinking s/he might have backup information for multiple incarnations in the catalog - when that isn't the case.

In addition, we can get the last 2 incarnations with a "select resetlogs_time,prior_resetlogs_time from v$database;". Even if we wish to restore an even older incarnation, how does this information from the catalog really help? Am more puzzled, than anything else.

Thank you for your time.

Thank you for the response. Hmm..I guess there is no 'intelligence' when resyncing a controlfile with the catalog (to detect if previous incarnations were indeed backed up). It is simply a case of dumping all information from the controlfile to the respository.

Tom,
I am just starting to setup rman in our environment. I use default setting as followed, and I also set the maxbackupsetsize =1GB. I backup the database everyday. Since the RETENTION POLICY TO REDUNDANCY =1, I should expect one backupset/day. But how come there are more than one day’s backup file in the backup directory? When I run the command “report obsolete”, I don’t get any obsolete backup found. Why? Does it mean I need all of these files for my recovery?


RMAN> show all;

using target database controlfile instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\oracle\BACKUP\%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # 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 SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\ORA92\DATABASE\SNCFAAAOEM.ORA'; # default
CONFIGURE EXCLUDE FOR TABLESPACE 'CWMLITE';
CONFIGURE EXCLUDE FOR TABLESPACE 'DRSYS';
CONFIGURE EXCLUDE FOR TABLESPACE 'EXAMPLE';
CONFIGURE EXCLUDE FOR TABLESPACE 'INDX';
CONFIGURE EXCLUDE FOR TABLESPACE 'ODM';
CONFIGURE EXCLUDE FOR TABLESPACE 'XDB';

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found


The following are backup files in the backup directory:

07/21/2004 09:01 PM 100,113,920 B_FJFRF74J_1_1
07/22/2004 09:01 PM 100,172,288 B_FNFRHRGJ_1_1
07/23/2004 09:01 PM 100,401,152 B_FRFRKFSL_1_1
07/24/2004 09:01 PM 100,783,104 B_FVFRN48J_1_1
07/25/2004 09:01 PM 100,721,152 B_G3FRPOKK_1_1
07/26/2004 09:01 PM 100,164,096 B_G7FRSD0K_1_1
07/27/2004 09:01 PM 100,097,024 B_GBFRV1CK_1_1
07/28/2004 09:01 PM 100,109,312 B_GFFS1LOK_1_1
07/29/2004 09:01 PM 100,192,768 B_GJFS4A4U_1_1
07/30/2004 09:01 PM 100,359,680 B_GNFS6UGT_1_1
07/31/2004 09:01 PM 100,895,744 B_GRFS9ISK_1_1
08/01/2004 09:01 PM 100,819,968 B_GVFSC78J_1_1
08/02/2004 09:01 PM 100,103,168 B_H3FSERKK_1_1
08/04/2004 09:01 PM 200,231,424 B_H7FSK4CT_1_1
08/05/2004 09:01 PM 100,367,360 B_HBFSMOOJ_1_1
08/06/2004 09:01 PM 101,084,672 B_HFFSPD4L_1_1
08/07/2004 09:01 PM 100,765,184 B_HJFSS1GK_1_1
08/08/2004 09:01 PM 100,813,312 B_HNFSULSK_1_1
08/09/2004 09:00 PM 144,171,008 B_HPFT1A6I_1_1
08/09/2004 09:00 PM 841,228,288 B_HQFT1A71_1_1
08/09/2004 09:01 PM 100,003,328 B_HRFT1A8J_1_1

Thanks for the quick quick response!!!

RMAN> list backup;


List of Backup Sets
===================

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
499 95M DISK 00:00:05 21-JUL-04
BP Key: 497 Status: AVAILABLE Tag: TAG20040721T210107
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_FJFRF74J_1_1

List of Archived Logs in backup set 499
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 416 72947328 20-JUL-04 73206118 21-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
503 95M DISK 00:00:05 22-JUL-04
BP Key: 501 Status: AVAILABLE Tag: TAG20040722T210107
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_FNFRHRGJ_1_1

List of Archived Logs in backup set 503
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 417 73206118 21-JUL-04 73464864 22-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
507 95M DISK 00:00:05 23-JUL-04
BP Key: 505 Status: AVAILABLE Tag: TAG20040723T210109
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_FRFRKFSL_1_1

List of Archived Logs in backup set 507
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 418 73464864 22-JUL-04 73724040 23-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
511 96M DISK 00:00:05 24-JUL-04
BP Key: 509 Status: AVAILABLE Tag: TAG20040724T210107
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_FVFRN48J_1_1

List of Archived Logs in backup set 511
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 419 73724040 23-JUL-04 73982800 24-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
515 96M DISK 00:00:05 25-JUL-04
BP Key: 513 Status: AVAILABLE Tag: TAG20040725T210108
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_G3FRPOKK_1_1

List of Archived Logs in backup set 515
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 420 73982800 24-JUL-04 74241784 25-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
519 95M DISK 00:00:05 26-JUL-04
BP Key: 517 Status: AVAILABLE Tag: TAG20040726T210107
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_G7FRSD0K_1_1

List of Archived Logs in backup set 519
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 421 74241784 25-JUL-04 74500594 26-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
523 95M DISK 00:00:05 27-JUL-04
BP Key: 521 Status: AVAILABLE Tag: TAG20040727T210108
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_GBFRV1CK_1_1

List of Archived Logs in backup set 523
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 422 74500594 26-JUL-04 74759265 27-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
527 95M DISK 00:00:05 28-JUL-04
BP Key: 525 Status: AVAILABLE Tag: TAG20040728T210108
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_GFFS1LOK_1_1

List of Archived Logs in backup set 527
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 423 74759265 27-JUL-04 75018133 28-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
531 95M DISK 00:00:05 29-JUL-04
BP Key: 529 Status: AVAILABLE Tag: TAG20040729T210118
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_GJFS4A4U_1_1

List of Archived Logs in backup set 531
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 424 75018133 28-JUL-04 75276880 29-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
535 95M DISK 00:00:05 30-JUL-04
BP Key: 533 Status: AVAILABLE Tag: TAG20040730T210117
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_GNFS6UGT_1_1

List of Archived Logs in backup set 535
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 425 75276880 29-JUL-04 75377277 30-JUL-04
1 426 75377277 30-JUL-04 75556195 30-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
539 96M DISK 00:00:05 31-JUL-04
BP Key: 537 Status: AVAILABLE Tag: TAG20040731T210108
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_GRFS9ISK_1_1

List of Archived Logs in backup set 539
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 427 75556195 30-JUL-04 75816167 31-JUL-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
543 96M DISK 00:00:05 01-AUG-04
BP Key: 541 Status: AVAILABLE Tag: TAG20040801T210107
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_GVFSC78J_1_1

List of Archived Logs in backup set 543
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 428 75816167 31-JUL-04 76076290 01-AUG-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
547 95M DISK 00:00:05 02-AUG-04
BP Key: 545 Status: AVAILABLE Tag: TAG20040802T210108
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_H3FSERKK_1_1

List of Archived Logs in backup set 547
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 429 76076290 01-AUG-04 76336391 02-AUG-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
551 190M DISK 00:00:09 04-AUG-04
BP Key: 549 Status: AVAILABLE Tag: TAG20040804T210116
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_H7FSK4CT_1_1

List of Archived Logs in backup set 551
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 430 76336391 02-AUG-04 76608848 03-AUG-04
1 431 76608848 03-AUG-04 76753271 04-AUG-04
1 432 76753271 04-AUG-04 76875829 04-AUG-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
555 95M DISK 00:00:05 05-AUG-04
BP Key: 553 Status: AVAILABLE Tag: TAG20040805T210107
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_HBFSMOOJ_1_1

List of Archived Logs in backup set 555
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 433 76875829 04-AUG-04 77135760 05-AUG-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
559 96M DISK 00:00:05 06-AUG-04
BP Key: 557 Status: AVAILABLE Tag: TAG20040806T210109
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_HFFSPD4L_1_1

List of Archived Logs in backup set 559
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 434 77135760 05-AUG-04 77396134 06-AUG-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
563 96M DISK 00:00:05 07-AUG-04
BP Key: 561 Status: AVAILABLE Tag: TAG20040807T210108
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_HJFSS1GK_1_1

List of Archived Logs in backup set 563
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 435 77396134 06-AUG-04 77655887 07-AUG-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
567 96M DISK 00:00:05 08-AUG-04
BP Key: 565 Status: AVAILABLE Tag: TAG20040808T210108
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_HNFSULSK_1_1

List of Archived Logs in backup set 567
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 436 77655887 07-AUG-04 77914171 08-AUG-04

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
571 95M DISK 00:00:06 09-AUG-04
BP Key: 569 Status: AVAILABLE Tag: TAG20040809T210107
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_HRFT1A8J_1_1

List of Archived Logs in backup set 571
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 437 77914171 08-AUG-04 78170440 09-AUG-04

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
573 Full 137M DISK 00:00:15 10-AUG-04
BP Key: 571 Status: AVAILABLE Tag: TAG20040810T210002
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_HTFT3UIJ_1_1
List of Datafiles in backup set 573
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- --------- ----
8 Full 78426801 10-AUG-04 D:\ORACLE\ORADATA\AAAOEM\TOOLS01.DBF
9 Full 78426801 10-AUG-04 D:\ORACLE\ORADATA\AAAOEM\USERS01.DBF
11 Full 78426801 10-AUG-04 D:\ORACLE\ORADATA\AAAOEM\OEM_REPOSITORY.DBF
12 Full 78426801 10-AUG-04 D:\ORACLE\ORADATA\AAAOEM\OEM_REPOSITORY_INDEX.DBF

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
574 Full 802M DISK 00:00:38 10-AUG-04
BP Key: 572 Status: AVAILABLE Tag: TAG20040810T210002
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_HUFT3UJ2_1_1
Controlfile Included: Ckp SCN: 78426825 Ckp time: 10-AUG-04
List of Datafiles in backup set 574
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- --------- ----
1 Full 78426826 10-AUG-04 D:\ORACLE\ORADATA\AAAOEM\SYSTEM01.DBF
2 Full 78426826 10-AUG-04 D:\ORACLE\ORADATA\AAAOEM\UNDOTBS01.DBF

BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
575 95M DISK 00:00:05 10-AUG-04
BP Key: 573 Status: AVAILABLE Tag: TAG20040810T210108
Piece Name: D:\ORACLE\BACKUP\RMAN_BACKUP\AAAOEM\B_HVFT3UKK_1_1

List of Archived Logs in backup set 575
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 438 78170440 09-AUG-04 78427006 10-AUG-04

BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
576 Full 1M DISK 00:00:01 10-AUG-04
BP Key: 574 Status: AVAILABLE Tag:
Piece Name: D:\ORACLE\BACKUP\C-3797558725-20040810-00
SPFILE Included: Modification time: 02-JUN-04

I run it as an job in OEM, and here is the script:

run {
allocate channel Channel1 type disk format 'd:\oracle\backup\rman_backup\aaaoem\b_%u_%p_%c';
backup
( database setsize 1048576 filesperset 64 include current controlfile );

backup ( archivelog all delete input setsize 1048576 filesperset 64 );

}
allocate channel for maintenance device type disk;
delete obsolete device type disk;

I haven't done any open resetlogs. But I have done something: since the number of the backup file kept growing, I've physically deleted some of the backup files that generated since day one with the OS command, and then within RMAN I did a crosscheck and then delete expired. Since I am doing backup everyday and archive the backup to tape, I only want to keep one backup in the system, is this a appropriate way to maintain the backup? How can I delete those archive?

Hi Tom,
I use RMAN with RC. Every 1st day of each month I take a 0 level incremental backup. And rest of the days of the month I take an incremental level 1 or 2 backups.
Say for example a tablespace is getting full and I add new datafiles or I add a new Tablespace.
Before taking a backup I resync the catalog and issue report need backup.
I get the new tablespaces need to be backed up or the new datafiles do not have a base backup.
In this case, I do a full backup of the new tablespace or a full backup of the tablespace which has been added new datafiles.
Keep in mind that the rest of the database has been done an incremental level 1 or 2 backup. Only the new tablespace or the new datafiles have been backed up full.
My question is if on the next day I do an incremental level 1 backup on the database will it backup all the tablespaces including the new tablespace I added the last day and the new datafiles added.
Or do I have to do it again individually.
Thanks as always...

Tom,

I noticed a lot of questions about Backup set and backup piece as they relate to a backup.

Would it be fair to say : that a backup set is a particular backup operation (or run command) that can back up a tablespace or the whole database; and that backup piece(s) is (are) the physical file (or files) that oracle uses to make up the set?

Thanks

Wayne

Hello Tom,

I have set recovery window to 90 days to ensure recovery to any time within the last 90 days. I have set autobackup of controlfile to on. I registered the database, made a level 1 backup (since level 0 is not yet available it has performed full backup). report obsolete lists the autobackup of controlfile performed after the full backup. Why is it obsolete? Say I lost the current database and I have to recover from the existing backup (only one full backup database so far available and the controlfile autobackup is deleted by delete obsolete backupc command). How would I do it since there is no controlfile.


RMAN> register database;

database registered in recovery catalog
starting full resync of recovery catalog
full resync complete

RMAN> list backup;

RMAN>

RMAN> list archivelog all;


List of Archived Log Copies
Key Thrd Seq S Low Time Name
------- ---- ------- - --------- ----
3377 1 1 A 21-AUG-04 C:\ORACLE\ORADATA\ARCHIVE\TESTDB\TESTDB001001S00001.ARC
3378 1 2 A 22-AUG-04 C:\ORACLE\ORADATA\ARCHIVE\TESTDB\TESTDB001001S00002.ARC

RMAN>

RMAN> list incarnation;


List of Database Incarnations
DB Key Inc Key DB Name DB ID CUR Reset SCN Reset Time
------- ------- -------- ---------------- --- ---------- ----------
3362 3382 UNKNOWN 495384619 NO 25916799 21-AUG-04
3362 3363 TESTDB 495384619 YES 25917804 21-AUG-04

#########################################
Why is DBNAME unknown in the first row?
#########################################

RMAN>

RMAN> show all;

RMAN configuration parameters are:

#########################################
90 days
#########################################

CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 90 DAYS;
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default

#########################################
autobackup on
#########################################
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'c:\oracle\rman_
backups\TESTDB_cf_autobkup_%M_%D_%Y_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # 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 'c:\oracle\rman_backups\TESTDB_%M_%D_
%Y_%t_%p';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'C:\ORACLE\ORA92\DATABASE\SNCFTESTDB.ORA';
# default

#########################################
level 1 backup
#########################################

RMAN> backup incremental level 1 database;

Starting backup at 22-AUG-04
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=9 devtype=DISK
no parent backup or copy of datafile 8 found
no parent backup or copy of datafile 2 found
no parent backup or copy of datafile 1 found
no parent backup or copy of datafile 3 found
no parent backup or copy of datafile 7 found
no parent backup or copy of datafile 4 found
no parent backup or copy of datafile 6 found
no parent backup or copy of datafile 5 found
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00008 name=C:\ORACLE\ORADATA\TESTDB\TESTDB.ORA
input datafile fno=00002 name=C:\ORACLE\ORADATA\TESTDB\UNDOTBS01.DBF
input datafile fno=00001 name=C:\ORACLE\ORADATA\TESTDB\SYSTEM01.DBF
input datafile fno=00003 name=C:\ORACLE\ORADATA\TESTDB\DRSYS01.DBF
input datafile fno=00007 name=C:\ORACLE\ORADATA\TESTDB\XDB01.DBF
input datafile fno=00004 name=C:\ORACLE\ORADATA\TESTDB\INDX01.DBF
input datafile fno=00006 name=C:\ORACLE\ORADATA\TESTDB\USERS01.DBF
input datafile fno=00005 name=C:\ORACLE\ORADATA\TESTDB\TOOLS01.DBF
channel ORA_DISK_1: starting piece 1 at 22-AUG-04
channel ORA_DISK_1: finished piece 1 at 22-AUG-04
piece handle=C:\ORACLE\RMAN_BACKUPS\TESTDB_08_22_2004_534847575_1 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:07:36
Finished backup at 22-AUG-04

Starting Control File and SPFILE Autobackup at 22-AUG-04
piece handle=C:\ORACLE\RMAN_BACKUPS\TESTDB_CF_AUTOBKUP_08_22_2004_C-495384619-200
40822-00 comment=NONE
Finished Control File and SPFILE Autobackup at 22-AUG-04

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 90 days
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set 3396 22-AUG-04
Backup Piece 3397 22-AUG-04 C:\ORACLE\RMAN_BACKUPS\TESTDB_CF_A
UTOBKUP_08_22_2004_C-495384619-20040822-00

#########################################
Why is the autobackup of controlfile obsolete? say i ran delete obsolete bacukup after this then i do not have any backup of controlfile. now assume the database server harddisk crashed and I need to perform recovery from the available backup (without controlfile as it is deleted by delete obsolete) how would I do it?
#########################################

Say I perform another full backup after deleting some rows in a table. When I run report obsolete will it list the second full database backupset as obsolete? If yes, Why is it obsolete?

This is confusing me much!!

Please help!!

Hello,

It appears to me that rman report obsolete and delete obsolete do not work correctly in oracle version 9.2.0.1.0. One of our admins experienced a similar problem and he suggested upgrading to 9.2.0.5.0. Metalink seems to have information about many bugs related to this problem.

Will upgrade the database software and let you know if that solves the problem.

Many thanks!!

Tom,
This might be a bizzare question. Anyway - say I had been backing up a target (DWDEV) using a catalog called RMANCAT for an year. A month ago, I switched to a different catalog called RCAT by simply registering DWDEV on it and initiating new backups using the new catalog (RCAT). Assume, I did not explicitly move backup information from RMANCAT to RCAT and just the DWDEV controlfile was synced with RCAT database. Also, the target's control_file_record_keeptime was always set to 7.

Then bad karma strikes and I lose RMANCAT, the OLD catalog. Assume RMANCAT is just not recoverable (for whatever reason). Then is there a way to DELETE all the age old backups of DWDEV from 11months ago?

Obviously, all the old (1 month and older) backup information is neither available in the new catalog, nor in the target controlfile. So how would one go about this deletion exercise?

Hope I'm not missing something very obvious!

> rm ?

Assume backups are on tape in the tape library. I need to reuse the tapes, except I don't know which specific tapes/devices are reusable.

Just to elaborate. I use TSM/TDPO. There isn't an interface which tells me which piece resides on which physical tape.

> doesn't the tape library have the equivalent of "ls"?

Well according to my TSM administrator - NO, you can't tell which piece resides on which tape. Let me explain.

We backup to a large IBM FastT (basically a disk storage product). Then a background process called "collocation" or something, moves stuff from a) disk to tape AND b) reorgs stuff within the tape library as well. To elaborate on point b - say tape 10, tape 11 were full yesterday. Then, 90% of stuff gets deleted from tape10,11 today. TSM then in the background automatically moves data from tape10,11 to tape20, which had a little bit of freespace on it; and thus freeing up tape 10,11 entirely.

Obviously the TSM catalog has got to keep track of where what sits. Unfortunately, based on the TSM information provided to me - there isn't an interface which tells me which tape backup piece DWDEV_bkup_1111_1111_1 resides on.

May be there is a way. I just don't know how on TSM, yet.
Thanks for your time.

Tom & AR,

TSM does track using a catalog. There is a process to resync the TSM catalog to the RMAN catalog.

But, if your .opt file has not been modified so that each database has a different identifier - It could drive you crazy trying to figure it all out ...

It is alot to read but try: </code> http://www.redbooks.ibm.com/redbooks/pdfs/sg246249.pdf <code>

TOM & AR

Resync-ing the TSM with the RMAN Catalog must be done in the proper order - reference p 5 f 8: </code> http://publib.boulder.ibm.com/tividd/td/DPON/SH26-4112-02/en_US/HTML/anou0010.htm <code>

Wayne

Wayne/Tom,
Thanks for the TSM documentation link. I have looked at the IBM red book documentation before. I looked at it briefly this morning as well. I don't see anything there that tells me how to figure which backup piece resides on which physical tape. I was hoping section 7.4 would go into more detail about the TSM database itself - but it doesn't.

I'm guessing I need to take this up with IBM and/or Oracle support.

Thanks again.
PS : Btw, this was a hypothetical situation. My old RMAN catalog is infact in place, and I can delete backups using the old catalog. However, for curiosity sakes I wanted to know how to go about it.

Tom,

In 9iR2, you can back up the whole database and archivelogs with a single command:

RMAN> backup database plus archivelog;

What are the underline steps for this command? is the following action sequence correct?

1) alter system archive log current
2) backup archivelog all
3) backup database files (how about controlfile if the auto controlfile backup is set?)
4) alter system archive log current
5) backup archivelogs
6) backup controlfile

Currently we are using 817 scripts for 9i DB which cause the controlfile being backed up several times in one full backup.
We want the controlfile back up only once.

thanks,

Tom,

If I use "backup databasse plus archivelog", how can I delete all the archivelogs after the backup? it seems to me that still need to separate the database backup and the archivelog backup with two backup commands.

There are separate commands:

To delete all archivelogs:
-------------------------
1. Backup archivelog all delete all input;
2. Delete archivelog all;
3. Delete archivelog all completed before/after 'sysdate-1';

To delete archivelog backups:
---------------------------------
1. Delete backup of archivelog all;
2. Delete backup of archivelog all completed before/after 'sysdate-1';

Delete archivelog all until sequence = xxxx;
Hope this hepls... ;)

I want delete the archivelogs only after I am sure the archive backup is successful. When use the command:

RMAN> backup archivelog all delete input;
if the backup is successful, it will delete the archivelogs which are already being backed up, not the new ones generated later. If the archive backup fails, it would not remove any.

With "backup database plus archivelogs", dbf files and archives will be backed up, but is it true that you need to issue a separate command to clean up the archives?

Does anything like this exists?

"backup database plus archivelog delete input" which only delete the archivelogs not the datafiles?

Is there anyway where we can findout how many data-blocks to backup?

I've to clarify something.

Oracle 8i doc Chapter 6 of RMAN
---8<---
Performing Incomplete Recovery Without a Recovery Catalog

Even if your database backup included backing up the control file, as it does if you back up datafile 1 or specify include current controlfile, the backup control file contained in the backup set is not self-referential.
---8<---

1. Let say i backed up

Tablespace system include current controlfile.

I would still need to do another controlfile backup because the current controlfile doesn't know about the tablespace system that i've just backed up (read consistent controlfile snapshot) ?

2. With a recovery catalog i don't need to do this right ? because the recovery catalog would contain those entries right ?

Assuming i have a recovery catalog on a separate machine.

When i log in RMAN i get an RMAN prompt. Are the other database features available on the RMAN mode ? like dbms_job ? so instead of using cron to execute my stored scripts i use the dbms_job ?

Thanks.

Hi Tom,

What is Null Compression in RMAN and how does it work?.

Thanks

Hi Tom,

It was a interview question, the interviewer hinted it something related to skipping unused blocks during backups.

Thanks

Thanks....God save us from such interviewers

Tom,
We are implementing RMAN backup plan for our 9i database on Sun, have decided to go with incremental level 0 on Sunday and incremental level 1 on mon,tue,wed,thur,fri and sat. Also planning to use cron to schelude the shell script.Based on the following RMAN SHELL script,
1)can I achieve the above plan ? or
2)Do I have to have separate rman shell script (say level 0 scripr for monday and level 1 script for rest of the day )to run everyday using cron ?

Please guide me.

Thanks,Ram


#!/bin/sh

CUSER=`id |cut -d"(" -f2 | cut -d ")" -f1`

RMAN_LOG_FILE=/products/oracle/logs/hot_db_prod1.out
echo >> $RMAN_LOG_FILE
chmod 666 $RMAN_LOG_FILE
echo Script $0 >> $RMAN_LOG_FILE
echo ==== started on `date` ==== >> $RMAN_LOG_FILE
echo >> $RMAN_LOG_FILE
ORACLE_HOME=/products/oracle/prod1
export ORACLE_HOME
BCK_LOC=/backup/oracle/prod1/hbackup
export BKP_DIR

ORACLE_SID=prod1
export ORACLE_SID

ORACLE_USER=oracle

TARGET_CONNECT_STR=/

RMAN=$ORACLE_HOME/bin/rman
echo >> $RMAN_LOG_FILE
echo "RMAN: $RMAN" >> $RMAN_LOG_FILE
echo "ORACLE_SID: $ORACLE_SID" >> $RMAN_LOG_FILE
echo "ORACLE_USER: $ORACLE_USER" >> $RMAN_LOG_FILE
echo "ORACLE_HOME: $ORACLE_HOME" >> $RMAN_LOG_FILE

echo >> $RMAN_LOG_FILE
echo "NB_ORA_FULL: $NB_ORA_FULL" >> $RMAN_LOG_FILE
echo "NB_ORA_INCR: $NB_ORA_INCR" >> $RMAN_LOG_FILE
echo "NB_ORA_CINC: $NB_ORA_CINC" >> $RMAN_LOG_FILE
echo "NB_ORA_SERV: $NB_ORA_SERV" >> $RMAN_LOG_FILE
echo "NB_ORA_POLICY: $NB_ORA_POLICY" >> $RMAN_LOG_FILE

echo >> $RMAN_LOG_FILE

if [ "$NB_ORA_FULL" = "1" ]
then
echo "Full backup requested" >> $RMAN_LOG_FILE
BACKUP_TYPE="INCREMENTAL LEVEL=0"

elif [ "$NB_ORA_INCR" = "1" ]
then
echo "Differential incremental backup requested" >> $RMAN_LOG_FILE
BACKUP_TYPE="INCREMENTAL LEVEL=1"

elif [ "$NB_ORA_CINC" = "1" ]
then
echo "Cumulative incremental backup requested" >> $RMAN_LOG_FILE
BACKUP_TYPE="INCREMENTAL LEVEL=1 CUMULATIVE"

elif [ "$BACKUP_TYPE" = "" ]
then
echo "Default - Full backup requested" >> $RMAN_LOG_FILE
BACKUP_TYPE="INCREMENTAL LEVEL=0"
fi

CMD_STR="
ORACLE_HOME=$ORACLE_HOME
export ORACLE_HOME
ORACLE_SID=$ORACLE_SID
export ORACLE_SID
$RMAN target $TARGET_CONNECT_STR nocatalog msglog $RMAN_LOG_FILE append << EOF
RUN {
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
$BACKUP_TYPE
SKIP INACCESSIBLE
TAG hot_db_bk_level0
FILESPERSET 5
FORMAT '$BCK_LOC/bk_%s_%p_%t'
DATABASE;
sql 'alter system archive log current';
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE DISK;
ALLOCATE CHANNEL ch01 TYPE DISK;
BACKUP
filesperset 60
FORMAT '$BCK_LOC/al_%s_%p_%t'
ARCHIVELOG ALL DELETE INPUT;
RELEASE CHANNEL ch00;
RELEASE CHANNEL ch01;
ALLOCATE CHANNEL ch00 TYPE DISK;
BACKUP
FORMAT '$BCK_LOC/cntrl_%s_%p_%t'
CURRENT CONTROLFILE;
RELEASE CHANNEL ch00;
}
EOF
"
# Initiate the command string

if [ "$CUSER" = "root" ]
then
su - $ORACLE_USER -c "$CMD_STR" >> $RMAN_LOG_FILE
RSTAT=$?
else
/usr/bin/sh -c "$CMD_STR" >> $RMAN_LOG_FILE
RSTAT=$?
fi

# ---------------------------------------------------------------------------
# Log the completion of this script.
# ---------------------------------------------------------------------------

if [ "$RSTAT" = "0" ]
then
LOGMSG="ended successfully"
else
LOGMSG="ended in error"
fi

echo >> $RMAN_LOG_FILE
echo Script $0 >> $RMAN_LOG_FILE
echo ==== $LOGMSG on `date` ==== >> $RMAN_LOG_FILE
echo >> $RMAN_LOG_FILE

exit $RSTAT

Okay Tom, can you atleast point to a specific (not whole RMAN doc) oracle doc to read about how to use a rman script to perform level 0 and level 1 backup using cronjob?

Thanks,Ram

Hi Tom,
I understand what you saying but unfortunately my manager doesn’t want to have rman catalog and oms since we have only one prod database. That's why I was reluctantly compelled to come up with this kind of script. What all I’m looking for is, a single rman script will dynamically choose backup type based on the day. Say if I run rman script on Sunday, it should perform level 0 backup and if I run on rest of the day, it should perform level 1 backup.

Thanks for your time,
Ram

I'm trying to understand Ram's question, but I'm not sure how having one production database has anything to do with an rman catalog and having one ksh script.

You can have one ksh script run all your incremental backups, you just need to know how to do it... I would have 3 seperate .rcv files, level0, level1, level2 and the ksh script with call the different level* file based up what day of the week it is... pretty simple.

I am trying to understand the use of snapshot controlfile. When RMAN backs up the current controlfile, does it first take a snapshot of the controlfile and uses the snapshot copy to refresh from the current controlfile until RMAN gets consistent version of the controlfile and then actualls backs up the snapshot copy? Thanks.

When rman backs up a tablespace, I see the following in v$session. I have only one rman session but I see two entries and also the 'action' field shows something that I don't understand. What does it mean '0000003 FINISHED66' and after a second when I queried, it shows '0000011 FINISHED118'. Could you clarify? Thanks.

SQL> select module, action from v$session where module like 'RMAN%';

MODULE
------------------------------------------------
ACTION
--------------------------------
RMAN.EXE


RMAN.EXE
0000003 FINISHED66


SQL> /

MODULE
------------------------------------------------
ACTION
--------------------------------
RMAN.EXE


RMAN.EXE
0000011 FINISHED118
 

Tom,
I have few questions on RMAN
1. When I need to clone a database from an existing database, Do I need to have the target database created before cloning?
2. Could you please outline the steps requured for rman cloning including the script

Thanks in advance
San

I've been reading RMAN docs for 9i and it says on chapter 10

---8<---
"Performing Recovery with a Backup Control File and a Recovery Catalog

....

This example restores the control file to its default location, then restores and completely recovers the database:

RESTORE CONTROLFILE;
ALTER DATABASE MOUNT;
RESTORE DATABASE;
RECOVER DATABASE;


If recovery was successful, then open the database and reset the online logs:
ALTER DATABASE OPEN RESETLOGS;

"

---8<---

1.) Why the need to open resetlogs ?? Can't the db just continue without reseting the online redo logs ? after all it should only get the latest SCN of the datafiles and continue thereon.

2.)

---8<---
"After restoring a backup control file, entries for tempfiles in locally-managed temporary tablespaces are removed. Hence, you must add new tempfiles to these tablespaces after you open with the RESETLOGS option. If you do not, then Oracle can display the following error for when attempting to sort: ORA-25153: Temporary Tablespace is Empty. "
---8<---

Why are the tempfile of LMT's removed ? is this still persistent in 10g?

Tom i need a help related to rman.

in 10g we have something like
"show all"

which shows all current rman config.

what is the equivalent in 8.1.7

thanks in advance.

Then how can i set a retention policy in 8.1.7 ?

Hey Thomas, Are you joking ???
You mean to say i cannot delete all the backups which are lets say more than 7 days old with 8.1.7.

I know that these options are available in 9i but unfortunately i cannot upgrade immediately.

What is the other solution ? to manually look for the backups using 'list backup command' and delete them. Will it not cause any problems since i use backupset and not image copies.

Is the command "list backupset ...." documented
I was trying in RMAN Reference manual for 9.2

I am trying to find if I can specify a timeframe with the
command to show the backupsets within the timeframe instead
of listing all the backupsets in the recovery catalog

Is there a way list the content of a backupset
(the datafiles or archive logs belong to the backupset)
given just the known name of the backupset on the disk,
if the bs_key is not known

To get constituent parts of a backup set I can
1. Query the rman catalog RC_BACKUP_PIECE
where handle like '%<backup piece name on disk.%'
2. use the RECID from step 1
3. RMAN>list backupset <RECID>

Is there a simpler way to find the members of a backup
set

Hi Tom,

Many thanks for your efforts to share your knowledge and experience with Oracle professionals around the world.

We have a job that runs at 3am everyday. This job backups the whole database every morning using RMAN. We want to write some scripts to report the status of the backup (successfully completed, failed, etc). If it failed, what was backed up successfully until then. Which RMAN views should I be looking at to confirm the backup status. Please provide some scripts/queries to explain them.

Thanks once again,

Paresh

From above:

**********
Why are the tempfile of LMT's removed ? is this still persistent in 10g?


Followup:
...

2) because tempfiles are not part of the backup, never have been.

**********
OK, I can understand why the contents aren't preserved, but not why the file is destroyed. What is the reasoning here?

Keeping maxsetsize to a lower value, will it give
a performance improvement when doing recovery

Ex if a backup piece is 10G vs. 5G . Will there be a performance impact

Thanks
I am backing up to disk ; keep 1 backup retention on disk
and using veritas backup to tape

Therefore the backup set will be on disk.

Hi Tom,

Oracle Documentation </code> http://oraclesvca2.oracle.com/docs/cd/B10501_01/server.920/a96566/rcmconc1.htm <code>

under heading "Automatic Channel Naming Conventions" says that
"Note that if you run the CONFIGURE DEVICE TYPE command to configure a device type and do not run CONFIGURE CHANNEL for this device type, then RMAN allocates all channels without other channel control options."

It further demonstrates an example,

"For example, assume that you configure the sbt device and run a backup as follows:

CONFIGURE DEVICE TYPE sbt PARALLELISM 1;
BACKUP DEVICE TYPE sbt DATABASE;


In effect, RMAN does the following:

RUN
{
ALLOCATE CHANNEL ORA_SBT_TAPE_1 DEVICE TYPE sbt;
BACKUP DATABASE;
}"

I could not understand the paragraph and the difference between the two Backup commands specified in the example and hence require a better explanation from you.

Thanks and Regards
Vivek

Hello Tom.

As always, we all thank you for the wonderful service you provide to the Oracle user community.

Since this thread appears to have evolved into a "catch-all" thread concerning RMAN, I'll post a question here. This question concerns 9.2.0.5 databases. Do you know if there is a way to change the location of a backupset? I have a backupset that was created on a Windows system and stored on the 'E' drive. I'm trying to recover that backupset on a different system that doesn't have an 'E' drive. So, I store the backupset on the 'G' drive. The RMAN Users Guide indicates that I have to uncatalog the existing record for that backupset in the controlfile and re-catalog it with the new location, but the command you are told to use, CATALOG, doesn't appear to work on backupsets.

I would think that there has to be an easy way to tell RMAN to get the datafiles from a specified backupset, but I haven't had any luck finding it. Can this be done? Or, do I have to always store the backupsets in the same directory structure so RMAN can find it?

Comment to Rich, just above here - due to the very issue you mention, we usually send our RMAN backupsets to a mapped drive. We typically create a directory RMAN_BACKUP on a drive with lots of space. Then we share this drive and map it as W:. Then on any of our windows based oracle servers we just deal with W:RMAN_BACKUP. So if we have to restore to another server we are ok. (as long as you don't run into a "real" W: drive... But, like no one would ever need more than 640k of memory - no one will ever need more than 26 drive letters!)

It's also handy if you flat out don't have room on the machine, but you do have room on another server, you can just map your W: drive over to a share on the machine with lots of space.

Just pick a drive letter that won't be used on any of your machines.

We haven't used SUBST - It might be better then the trick we use, might basically be the same, or might have some limitations (can you subst to a unc name??? I don't know). There are a few problems with the drive mappings to other servers if there is authentication involved - various versions of windows seems to have different not very well documented rules regarding caching authentication credentials etc. - test your scripts over a reboot or two...

By the way - we've never done any stringent benchmarks to see if running to a mapped drive on the same machine incurs any performance penalty - it doesn't "seem" to.

Note this whole issue goes away with your unix flavour of choice! You can just use symlinks and nfs to make it look like things are where ever you'd like.

Holy Cow!!
That worked!!

I didn't know about that command. I'm a Unix guy, by nature. I'm somewhat of a fish out of water with Windoze. Much thanks to both Tom and Dan for the advice.

Note to Dan,
Yeah, the problem goes away if you use Unix. Unfortunately, there are misguided people out there who think MS Windows is where all software should run.

As far as the idea of using a shared drive is concerned, you're right about that, too. We (the DBA group) have been trying to get a network attached storage device for this exact purpose. Again, unfortunately, there are misguided people who think direct attached storage for each system is the way it should be done. And, of course, with no standards for drive letters.


Again, many thanks.

It looks like I spoke too soon. :-(
The virtual drive is there; I can see the files with Windows Explorer and via the 'dir' command from within the Command Prompt.

Unfortunately, RMAN can't see them. My guess at this point is that RMAN is using OS calls that exist lower in the Windows kernel than the code that creates the virtual drive. As a result, that kernel code doesn't know about the virtual drive.

I am beginning to believe that performing a recovery with this particular backupset on this particular server is going to be impossible. So, if I understand this all correctly, there is no way to change the location of a backupset. You must place it into the exact same location as the one in which it was created, even if it is being restored on a completely different system.

Tom, I find it difficult to believe that RMAN doesn't provide the ability by design to specify the backupset location. I can do that with the autobackup controlfiles. Wouldn't this be considered a significant oversight?

Hi again Rich,

You've jogged my memory, and actually I've been in the boat you are in. This is exactly why we back up to a standard location etc. I know there was metalink traffic on this and I thought this was an issue being addressed with RMAN post 8.1.7, I guess it wasn't fixed in 9r2 either. I'm pretty sure it was mentioned as an Enhancement Request.

I did a BAD, BAD, NAUGHTY THING to work around this... This is a high risk manouver... You didn't hear it from me...

I crawled through the RMAN catalog (this was probably an 8i rman, but may have been 9i) until I found the offending path/file name and just changed it (UPDATE ...). and it worked. I have no recollection what table/field it was (this was over a year back), but, as I recall the rman repository isn't that complex.

Many of the tables are keyed by DBID, obviously you want to make sure you are changing the paths for the actual database you are concerned with.

So you may want to try that - NO WARRANTY expressed or implied!!! This is totally the kind of procedure I would only recommend as a last resort. If you accept this advice, and you are captured, I'll deny all knowledge of this note (and by the way, this webpage will self destruct in 10 seconds). And obviously, if you are using this repository to manage production systems - backup the repository!!!! (and make sure you know how to recover without the repository!) You probably want to try this at a time when you don't have other rman processes running so you can recover clean to before your experiments. So you'll have to consider your production schedules.

Good Luck...

P.S. ...all those misguided people at your workplace... are you sure you don't work around here somewhere?

I have been provided with a different test server that has a valid 'E' drive with enough space to store the backupsets. So, my recovery is back on track. Again, many thanks to Tom and Dan for their advice.

Dan, you're right about that tweaking the catalog idea. It would work and it is very risky. I've actually spent some time examining the catalog, so I think I know what I would have to change. But it isn't for the faint-hearted. I would clone the production catalog to a test system and use that instead.

In regards to your PS, no I don't live in the Yukon. Unfortunately, I come across misguided Microsoft Windows people everywhere I go. They seem to be able to thrive in just about any climate and geographical region, just like cockroaches. :-)

Again, my thanks to both of you.

Dear Tom,

I was reading all posts above and

1)Even when we use a catalog, all information is saved in the controlfile of the target database. then using sync we can send this information to the catalog. right?
2)The information in the catalog is saved in the controlfile of the catalog database or in a table?
3)If we lost the controlfile in the target database and we have to recreate it from scratch, we lost also all information about backups?
4)If question 3 is true, Is there any way sending back the information from catalog to target database to update the controlfile again.

Can you clarify these points.
thanks in advance for your help

Hi TOM,

We have situation, where we need to write to TAPE and Disk parallely. The reason is, we are planning to perform local backup with MMS software + remote backup (for disaster solution - we also plan stby in future). The remote tape library is Storage TEK client / server software, where the client software just copies list of folder to tape. So, we need to write to disk for remote copy and to tape for local copy. Awaiting Your Mentation ...

Thanks,
Balaji.v

Hi TOM,

Missed out the question.

CAN RMAN WRITE TO DISK AND TAPE PARALLELY ? We are using RAW file system and plan to backup RMAN to write to local file system on one of the servers for remote copy and to tape parallely. Is that possible. Awaiting your mentation.

Thanks,
Balaji.v

Hi Tom,

Thanks for your quick update. I understand that RMAN needs MMS software.

We plan for MMS too. for local tape backup we plan to use MMS. We also plan for remote backup , where the tape(client) software will be installed on the server which just copies the required folders. No MMS layer in this regard(a limitation for the remote tape device). So we plan for disk backup for the remote tape device which is 500 kms away and RMAN MMS backup for local copy. (Just a disaster strategy plan till Disaster site is set up).

My question is can RMAN write to DISK and TAPE parallely using channels where, tape backup goes to tape via MMS and disk backup to remote tape using the client software. I just want to do parallel backup of both disk(which will be to remote tape) and tape. Is this feasible.

Dear Tom,

I did the following

exercise 1....
* create catalog
* connect to target and catalog
* backup database
* delete controlfile in target
* recreate controlfile
* connect to target and catalog
* list backup, I can see the backup created
* create a new backup
This confirm that even when we lost controlfile in target database, we still can use our RMAN backups if we have a catalog.

Exercise 2...

* RMAN connect to target
* list backup, no backups availables (?) (previous backups were done while connected to catalog )
* backup database
* RMAN connect to target and catalog
* list backup, I can see three backups set
* resync catalog
* RMAN connect to target
* list backup, only newest backup available

from one of you previous link

</Quote
Even after you drop the recovery catalog, the control file still contains records about the backups.
/>

This was not the case, once I am not connected to the catalog I am not able to see backup created while I am connected to the catalog.

Can you explain why my results are differents?

thanks

Yes I did, but then what it is the reason to resync, Is it not sending the informaion in both ways, from controlfile to catalog and catalog to controlfile?

thanks

Tom,
I have used RMAN for backups/restores for a while now. However, I still wonder about the real need for a catalog database.

The way I see it : No matter what your controlfile_keep_time is set to (non-trivial value), no matter how many target incarnations you have - everything is restorable without a catalog. As long as you've been consistently backing up your controlfile (and rest of the stuff), you're good. There are documented ways (slightly painful) to restore everything without using the catalog.

So what is it that a catalog really gives me? A better interface (and better reporting capabilities maybe)? It does nothing to further aid database restores (??).

Thanks.
PS : I posted the same question on Jeff's blog..

Tom

On the housekeeping and retention part though I read the
documentations, I am struggling to arrive a clear point.

I am not doing any housekeeping activity since 1 year and my parameters are as below.

CONFIGURE RETENTION POLICY TO REDUNDANCY 5;

In target database
control_file_record_keep_time 7


Our company policy is keeping 30 days backups at anytime.

My worst problem is if i put LIST BACKUP in rman for finding the details, it take approximately 45 minutes, since it gives the entire backup detals from one year.

I requests the answere for the below questions

1. I need to have the catalog information of 30 days and other than this i need to delete in
a. catalog
b. Control file of target database.
2. By removing the above information, can I still recover backups older than one month, if the backup is available in tape? (Assume that i have removed the catalog and control file information of the backups.)

Thanks very much

Dear Tom,

Could you please figure out most relevant init.ora parameters affecting media recovery (redo appliance) performance?

Which parameters You suggest to set to improve performance of physical standby database?
(there is idea to suspend recovery of standby while it is used in read-only mode for reporting,
and goal is to maximize daily time window for reporting, thought to minimize time needed to apply redo)

Regards,

The word "parallel" was the key one in your followup.
Now i found also good Metalink note on this question:
Note:240875.1

Tom,
Thank you. From your comment and dizwell link, I gather that -
RMAN catalog
a) does NOT add any value to the backups security (or recoverability) when autobackup of the controlfile to tape is activated.

HOWEVER it is
a) a centralized place to store scripts and manage everything
b) convenient when using multiple targets
c) nice place to keep historical data on long-term backups

I hope that captures the essense.

Many thanks.

Tom,

Previously on this post (May 16, 2005), Rich from Florida had asked if it was possible to do a recover from a different location that what RMAN had backed up to. You said you would look into it, and I don't see where you ever answered him :)

I am using 9.2.0.5 with no catalog.
If I did an rman backup to /disk1/rman can I copy this rman backup to /disk2/rman and tell rman to restore from there?

Thank you,

Robert.

Tom,

Thanks a lot for your help.
This is exactly what I needed to know.

Now I would like to make 2 comments, please...

1) The idea of using a link to 'fool' RMAN. This is a great idea and possibly the perfect 'work-around'. I feel like I should have thought about this myself.

2) The fact that RMAN will not let you easily change the location of the backup pieces..... This seems to me an ENORMOUS FAILURE in design!... what were they thinking? Or am I the only person who would have a requirement to restore from a different location than the original backup location !?

Thanks again for all your help and your great service to us!

Robert.

I'm looking for some tricky solution on the following RMAN problem. I want to keep point-in-time backups of a database for a long time.

If I do KEEP LOGS, then I end up keeping all the redo logs since the backup until the current time, which isn't what I want - I just want enough to recover to the end of the backup.

If I do KEEP NOLOGS then I have to do a cold backup, which I can't as its 24X7 production db.

Is there another way to achieve what I want?

Appreciate your expert advise...

Hi Tom,

I have rman set up on a database in 8i. I am going to implement the duplex archive log and I am wondering how can I delete both location but only backup one of them.
I checked the oracle documentation and they show how to delete both after both are backup but in my case I only want to backup one of the location.
The oracle documentation shows the following example:
run {
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
backup
filesperset=20
format='al_%d/%t/%s/%p'
(archivelog like '/oracle/arch/dest1/%' channel t1 delete input)
(archivelog like '/oracle/arch/dest2/%' channel t2 delete input);
}
Now, how can I implement a backup through rman of only one of the location but deleting the archive logs of both locations?

I would appreciate any help you can give me on this.

Thanks

Thomas,
i have a single RMAN catalog and 5 databases to backup with.
Now i do not want to expose the password of the SYS user in the backup scripts. SO want to connect with something like this

connect target /@target_db rcvcat /@recovery_cat

is this possible, how can i achieve this.

In the past when i was making disk backup i used '/' option on the server with SQL_AUTHENTICATION_SERVICEC=NTS and it worked well.

when i user veritas, it generates the encripted passwords automatically. Now i have shifting to Tivoli and not sure whether it has this option.

I have read the document and it talks about hiding the file with connect information. i don't want to do that.

Hi Tom,
We are using Rman to backup our database.
Rman is new tool for me so i would like get your opinion about the following:

For daily backup , we are using this script:
RMAN> run {
2> allocate channel 'dev_0' type 'sbt_tape'
3> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=b3prd,OB2BARLIST=accdb_b3prd_daily)';
4> allocate channel 'dev_1' type 'sbt_tape'
5> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=b3prd,OB2BARLIST=accdb_b3prd_daily)';
6> allocate channel 'dev_2' type 'sbt_tape'
7> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=b3prd,OB2BARLIST=accdb_b3prd_daily)';
8> allocate channel 'dev_3' type 'sbt_tape'
9> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=b3prd,OB2BARLIST=accdb_b3prd_daily)';
10> backup incremental level 1
11> format 'accdb_b3prd_daily<b3prd_%s:%t:%p>.dbf'
12> database;
13> backup
14> format 'accdb_b3prd_daily<b3prd_%s:%t:%p>.dbf'
15> current controlfile;
16> }
17>


For weekly backup we are using the following script:
RMAN> run {
2> allocate channel 'dev_0' type 'sbt_tape'
3> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=b3prd,OB2BARLIST=accdb_b3prd_weekly)';
4> allocate channel 'dev_1' type 'sbt_tape'
5> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=b3prd,OB2BARLIST=accdb_b3prd_weekly)';
6> allocate channel 'dev_2' type 'sbt_tape'
7> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=b3prd,OB2BARLIST=accdb_b3prd_weekly)';
8> allocate channel 'dev_3' type 'sbt_tape'
9> parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=b3prd,OB2BARLIST=accdb_b3prd_weekly)';
10> backup incremental level 0
11> format 'accdb_b3prd_weekly<b3prd_%s:%t:%p>.dbf'
12> database;
13> backup
14> format 'accdb_b3prd_weekly<b3prd_%s:%t:%p>.dbf'
15> archivelog all;
16> backup
17> format 'accdb_b3prd_weekly<b3prd_%s:%t:%p>.dbf'
18> current controlfile;
19> }
20>

The daily backup (incremental level 1) start at 21:00 and finished at about 23:30 , and backup about 40 GB
The weekly backup (incremental level 0) start at 01:45 and finished at about 04:25 , and backup about 500 GB

While the weakly and the daily toke almost the same time , the weakly backed up 12.5 times more.

I looked at the statspack report for 1 houre period of the daily backup and found that:

Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
-------------------------------------------- ------------ ----------- --------
async disk IO 848,206 16,239 60.11
db file sequential read 34,048 8,999 33.31
db file scattered read 886 620 2.30
buffer busy waits 848 558 2.07
sbtwrite2 108,267 205 .76


The windows O.S where the database is located is using async IO.

1. Do you recommand me to change somthing in scripts above ?
2. Can you suggest me where to start looking at?

Thanks.

hello.

i'm using rman backup + ctatalog for our 60G production database.
i'm keeping 7 days of backup on the server + tape,
and extra 7 days on tape ( meaning 14 days of backup , the last 7 available on tape only )
my retention policy to redundancy is set to 7.

1) when i issue delete obsolete -
the last 7 days of backup that exist on tape only will be removed from my catalog and i will not be able to use them in case i need to recover to ... lets say …10 days ago ....
is that true ?

2) but i will be able to use them in a noncatalog mode using the controlfile . is that true ?

thanks.

dornit

Hi Tom,

I was going through the entire discussion here. Initially there was a discussion on backup piece size. I have a doubt regarding this. Does the backup piece size has any relation with the db_block_size? To be more clear, I have two databases (9206) on a server with db_block_size 8192 and 32768 respectively.I am using the same settings (in fact same script) for takin rman backup on both,with MAXPIECESIZE set to unlimited. For the first database (with block size 8192) only one backup piece is created per set while its 2 pieces per set for the second one. Can you comment on this .
Regards,
Susan

Prior to 10g, RMAN was able to skip the backing up of blocks that have NEVER been used. For 10gR2 RMAN, Oracle documentation states that RMAN can now "skip datafile blocks that are not currently used to store data". However, I have not been able to realize this compression even after ensuring that the required conditions were met.

The documented conditions are as follows:
* The COMPATIBLE initialization parameter is set to 10.2
* There are currently no guaranteed restore points defined for the database
* The datafile is locally managed
* The datafile is being backed up to a backup set as part of a full backup or a level 0 incremental backup
* The backup set is being created on disk.

I created a large table in my database and then performed a full database backup. I then dropped the large table with purge to ensure it wasn't in the recyclebin and performed another backup. The backupsets were the same size. As another test, I recreated the table and instead of dropping the table, I truncated all the rows from the table and took another backup. This again produced the same size backupset as the original one. I was expecting to see a smaller backupset for both of these scenarios. There was no other activity on the database during this time period.

Do you know if RMAN can truly perform this level of compression?

As always, thanks for your time !!

Hi Tom,

I am not sure if this is the right way to add a question to an ongoing topic as I am visting asktom after a long time. This is on 8.1.7 (please don't curse me it is the client decision).

Our RMAN backups are taking 15 hours (for a 450 GB db). It used to take 10 hours on a DLT8000 dual tape drive system. I see lots of waits (about 12 hours plus) on 'file open' and 'control file sequential read' events. Spent better part of the day searching web and metalink without much luck.

Thanks a bunch for your help.
Paresh

Hi Tom,

We are trying to make space in the falsh recovery area
and were moving backupsets to disk. We did:

RMAN> backup backupset 162 format '/data.../backupset_162'

We did not us the 'delete input' option (I think we should have).

Now we want to delete a particular copy of a backupset
but they have the same tag so we are not sure how to do it.
We've searched the documentation but could not find it.

We want to delete the one with BP Key 162.


RMAN> list backupset 162;


List of Backup Sets
===================

BS Key Size
------- ----------
162 29G

List of Archived Logs in backup set 162
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 5635 55606405597 20-NOV-06 55606490324 20-NOV-06
1 5636 55606490324 20-NOV-06 55606622565 20-NOV-06
1 5637 55606622565 20-NOV-06 55606642475 20-NOV-06
1 5638 55606642475 20-NOV-06 55606645535 20-NOV-06
1 5639 55606645535 20-NOV-06 55606647821 20-NOV-06
1 5640 55606647821 20-NOV-06 55606650648 20-NOV-06
1 5641 55606650648 20-NOV-06 55606655963 20-NOV-06
1 5642 55606655963 20-NOV-06 55606659201 20-NOV-06
1 5643 55606659201 20-NOV-06 55606661770 20-NOV-06
1 5644 55606661770 20-NOV-06 55606691633 20-NOV-06
1 5645 55606691633 20-NOV-06 55606723407 20-NOV-06
1 5646 55606723407 20-NOV-06 55606755161 20-NOV-06
1 5647 55606755161 20-NOV-06 55606784686 20-NOV-06
1 5648 55606784686 20-NOV-06 55606786651 20-NOV-06
1 5649 55606786651 20-NOV-06 55606788856 20-NOV-06
1 5650 55606788856 20-NOV-06 55606795126 20-NOV-06
1 5651 55606795126 20-NOV-06 55606827391 20-NOV-06
1 5652 55606827391 20-NOV-06 55606859721 20-NOV-06
1 5653 55606859721 20-NOV-06 55606891313 20-NOV-06
1 5654 55606891313 20-NOV-06 55606925234 20-NOV-06
1 5655 55606925234 20-NOV-06 55606959622 20-NOV-06
1 5656 55606959622 20-NOV-06 55606988964 20-NOV-06
1 5657 55606988964 20-NOV-06 55607023551 20-NOV-06
1 5658 55607023551 20-NOV-06 55607066686 20-NOV-06
1 5659 55607066686 20-NOV-06 55607152699 20-NOV-06
1 5660 55607152699 20-NOV-06 55607238371 20-NOV-06
1 5661 55607238371 20-NOV-06 55607351180 20-NOV-06
1 5662 55607351180 20-NOV-06 55607417058 20-NOV-06
1 5663 55607417058 20-NOV-06 55607420238 20-NOV-06
1 5664 55607420238 20-NOV-06 55607422552 20-NOV-06
1 5665 55607422552 20-NOV-06 55607425949 20-NOV-06
1 5666 55607425949 20-NOV-06 55607429076 20-NOV-06
1 5667 55607429076 20-NOV-06 55607431806 20-NOV-06
1 5668 55607431806 20-NOV-06 55607445832 21-NOV-06
1 5669 55607445832 21-NOV-06 55607477819 21-NOV-06
1 5670 55607477819 21-NOV-06 55607509326 21-NOV-06
1 5671 55607509326 21-NOV-06 55607547579 21-NOV-06
1 5672 55607547579 21-NOV-06 55607549646 21-NOV-06
1 5673 55607549646 21-NOV-06 55607551926 21-NOV-06
1 5674 55607551926 21-NOV-06 55607559852 21-NOV-06
1 5675 55607559852 21-NOV-06 55607592103 21-NOV-06
1 5676 55607592103 21-NOV-06 55607624239 21-NOV-06
1 5677 55607624239 21-NOV-06 55607655635 21-NOV-06
1 5678 55607655635 21-NOV-06 55607696995 21-NOV-06
1 5679 55607696995 21-NOV-06 55607723103 21-NOV-06
1 5680 55607723103 21-NOV-06 55607757091 21-NOV-06
1 5681 55607757091 21-NOV-06 55607780711 21-NOV-06
1 5682 55607780711 21-NOV-06 55607841303 21-NOV-06
1 5683 55607841303 21-NOV-06 55650562357 21-NOV-06
1 5684 55650562357 21-NOV-06 55650647194 21-NOV-06
1 5685 55650647194 21-NOV-06 55650733316 21-NOV-06
1 5686 55650733316 21-NOV-06 55650848447 21-NOV-06
1 5687 55650848447 21-NOV-06 55650910412 21-NOV-06
1 5688 55650910412 21-NOV-06 55650913686 21-NOV-06
1 5689 55650913686 21-NOV-06 55650916183 21-NOV-06
1 5690 55650916183 21-NOV-06 55650918546 21-NOV-06
1 5691 55650918546 21-NOV-06 55650923630 21-NOV-06
1 5692 55650923630 21-NOV-06 55650929169 21-NOV-06
1 5693 55650929169 21-NOV-06 55650933398 21-NOV-06
1 5694 55650933398 21-NOV-06 55650935951 21-NOV-06
1 5695 55650935951 21-NOV-06 55650967209 21-NOV-06
1 5696 55650967209 21-NOV-06 55650998838 21-NOV-06

Backup Set Copy #1 of backup set 162
Device Type Elapsed Time Completion Time Compressed Tag
----------- ------------ --------------- ---------- ---
DISK 00:30:06 22-NOV-06 NO TAG20061121T202237

List of Backup Pieces for backup set 162 Copy #1
BP Key Pc# Status Piece Name
------- --- ----------- ----------
162 1 AVAILABLE +FLASHDG/dws/backupset/2006_11_22/annnf0_tag20061121t202237_0.614.607134355

Backup Set Copy #2 of backup set 162
Device Type Elapsed Time Completion Time Compressed Tag
----------- ------------ --------------- ---------- ---
DISK 00:30:06 22-NOV-06 NO TAG20061121T202237

List of Backup Pieces for backup set 162 Copy #2
BP Key Pc# Status Piece Name
------- --- ----------- ----------
163 1 AVAILABLE /data3/rman_backup_sets/backupset_162

Hi Tom, please, I have a question I recovered this database before, now trying to create a test database recovering using rman rman asks a very old redolog I don't have.

This is the full backup I got (including readonlys) incremental 0.
BS Key Type LV Size Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
236 Incr 0 2.60G DISK 00:00:00 23-NOV-06
BP Key: 202 Status: AVAILABLE Compressed: YES Tag: TAG20061123T204043
Piece Name: D:\SERPFLASHBACK\SERPXXXX20061123(FULL_INC_0_BKP2)49I3546D_1_1
List of Datafiles in backup set 236
File LV Type Ckp SCN Ckp Time Name
---- -- ---- ---------- --------- ----
1 Full 121041699 23-NOV-06 E:\ORASERP\DATAFILES\DFL_SYS_SERP
2 Full 121041699 23-NOV-06 E:\ORASERP\DATAFILES\DFL_UNDO_SERP
3 Full 121041699 23-NOV-06 E:\ORASERP\DATAFILES\DFL_USER_SERP
4 Full 118445416 23-OCT-06 E:\ORASERPREADONLY\DFL_READONLY_SERP_2
5 Full 121041699 23-NOV-06 E:\ORASERP\DATAFILES\DFL_LOB_SERP
6 Full 121041699 23-NOV-06 E:\ORASERP\DATAFILES\DFL_STATPACK_SERP
8 Full 121041699 23-NOV-06 D:\ORASERP\DATAFILES\DFL_DRSYS_SERP
9 Full 121041699 23-NOV-06 D:\ORASERP\DATAFILES\DFL_XDB_SERP
12 Full 121041699 23-NOV-06 E:\ORASERP\DATAFILES\SYSAUX_SERP
13 Full 121041699 23-NOV-06 D:\ORASERP\DATAFILES\DFL_INDX_SERP_2
14 Full 118445430 23-OCT-06 E:\ORASERPREADONLY\DFL_READONLY_IDX_2

Oracle wants sequence 964, the last I have is
1 1026 119731884 09-NOV-06 119755021 09-NOV-06

This is the current state of datafile (at the moment of the backupset)


This is from the v$datafiles
STATUS ENABLED CHECKPOINT_CHANGE# CHECKPOINT_TIME UNRECOVERABLE_CHANGE# UNRECOVERABLE_TIME
---------- ---------- -------------------------------------- ------------------ -------------------------------------- ------------------
SYSTEM READ WRITE 123683710 29-Dec-2006 17:01:53 0
ONLINE READ WRITE 123683710 29-Dec-2006 17:01:53 0
ONLINE READ WRITE 123683710 29-Dec-2006 17:01:53 0
ONLINE READ ONLY 118445416 23-Oct-2006 14:55:59 0
ONLINE READ WRITE 123683710 29-Dec-2006 17:01:53 0
ONLINE READ WRITE 123683710 29-Dec-2006 17:01:53 0
ONLINE READ WRITE 123683710 29-Dec-2006 17:01:53 0
ONLINE READ WRITE 123683710 29-Dec-2006 17:01:53 0
ONLINE READ WRITE 123683710 29-Dec-2006 17:01:53 0
ONLINE READ WRITE 123683710 29-Dec-2006 17:01:53 109472472 30-Jun-2006 14:49:25
ONLINE READ ONLY 118445430 23-Oct-2006 14:56:02 0

The only strange I see is 1) an upgrade to 10.2.0.3 and unrecoverable_change#,unrecoverable_time columns.

Could yo please explainme what are unrecoverable_change#,unrecoverable_time, and a clue to understand why a so old logseq is asked.

Thanks Tom happy new year :)

Thank you Tom,
Please answer my question.
I don't say is a bug, my question is how can I want to know which datafile requires that redo log.
The backup was on 29nov and is asking a redolog from previous to 09nov.
Now it doesn't makes sense because if you check there was afull backup and if it needed a redolog this should be maximum two days ago. And if you check at the end rman restore that backup.

I'm worry about this could be causing me problems, there must be a way to say, well if I try to restore this backup, I'll need redologs from X date, so better I leave them on disk and make sure there is a backup at hand.

As I see the only one candidate would be E:\ORASERPREADONLY\DFL_READONLY_SERP_2, but as you can see it was included on full backup

Before executing the recover command how can I know the lower logfile I'll need?

:) Thank you

This is the list after the restore and before recover.
E:\ORASERP\DATAFILES\DFL_SYS_SERP 121041701 29-dic-2006 14:37:31
E:\ORASERP\DATAFILES\DFL_UNDO_SERP 121041701 29-dic-2006 14:37:31
E:\ORASERP\DATAFILES\DFL_USER_SERP 121041701 29-dic-2006 14:37:31
E:\ORASERPREADONLY\DFL_READONLY_SERP_2 0
E:\ORASERP\DATAFILES\DFL_LOB_SERP 121041701 29-dic-2006 14:37:31
E:\ORASERP\DATAFILES\DFL_STATPACK_SERP 121041701 29-dic-2006 14:37:31
D:\ORASERP\DATAFILES\DFL_DRSYS_SERP 121041701 29-dic-2006 14:37:31
D:\ORASERP\DATAFILES\DFL_XDB_SERP 121041701 29-dic-2006 14:37:31


(this is the recent try I did without read onlys because I supposed could be a problem with the read onlys, and I could set them offline)
RMAN> RUN{
2> ALLOCATE CHANNEL d1 DEVICE TYPE disk;
3> RESTORE DATABASE;
4> }

se utiliza el archivo de control de la base de datos destino en lugar del catßlogo de recuperaci=n
canal asignado: d1
canal d1: sid=101 devtype=DISK

Iniciando restore en 29DIC2006

saltando archivo de datos 4; ya se ha restaurado al archivo E:\ORASERPREADONLY\DFL_READONLY_SERP_2
saltando archivo de datos 14; ya se ha restaurado al archivo E:\ORASERPREADONLY\DFL_READONLY_IDX_2
canal d1: iniciando restauraci=n del juego de copias de seguridad de archivos de datos
canal d1: especificando archivo(s) de datos para restaurar del juego de copias de seguridad
restaurando el archivo de datos 00001 en E:\ORASERP\DATAFILES\DFL_SYS_SERP
restaurando el archivo de datos 00002 en E:\ORASERP\DATAFILES\DFL_UNDO_SERP
restaurando el archivo de datos 00003 en E:\ORASERP\DATAFILES\DFL_USER_SERP
restaurando el archivo de datos 00005 en E:\ORASERP\DATAFILES\DFL_LOB_SERP
restaurando el archivo de datos 00006 en E:\ORASERP\DATAFILES\DFL_STATPACK_SERP
restaurando el archivo de datos 00008 en D:\ORASERP\DATAFILES\DFL_DRSYS_SERP
restaurando el archivo de datos 00009 en D:\ORASERP\DATAFILES\DFL_XDB_SERP
restaurando el archivo de datos 00012 en E:\ORASERP\DATAFILES\SYSAUX_SERP
restaurando el archivo de datos 00013 en D:\ORASERP\DATAFILES\DFL_INDX_SERP_2
canal d1: leyendo desde la parte de copia de seguridad D:\SERPFLASHBACK\SERPXXXX20061123(FULL_INC_0_BKP2)49I3546D_1_1
canal d1: parte 1 de la copia de seguridad restaurada
manejador de parte=D:\SERPFLASHBACK\SERPXXXX20061123(FULL_INC_0_BKP2)49I3546D_1_1 etiqueta=TAG20061123T204043
canal d1: restauraci=n terminada, tiempo transcurrido: 01:13:21
restore terminado en 29DIC2006
canal liberado: d1

Thanks Tom,

I found the reason, the backup was on 10.2.0.2 and the database recently upgrade to 10.2.0.3.
This seems a problem only recovering readonly files, for some reason it required older logs, I checked logs and there were nothing strange.
I did another full backup using the same script, and there were no problem. The problem was specific with that backup.

Hi Tom,
wish you are doing fine and thank you fro your great support.

i am confused about "RMAN parallel recovery" , i can't find any resource that detail how we can perform an RMAN parallel recovery.

1)is it possible to perform parallel recovery with RMAN for an Oracle9iR2 database ?

Here is a part i found for the 9i RAC documentation ( http://www.lc.leidenuniv.nl/awcourse/oracle/rac.920/a96596/backup.htm )
=================== start paste===========
Parallel Recovery with RMAN
With RMAN's RESTORE and RECOVER commands, Oracle automatically parallelizes the following three stages of recovery as described in this section:

Restoring Datafiles
Applying Incremental Backups
Applying Redo Logs
Restoring Datafiles
When restoring datafiles, the number of channels you allocate in the RMAN recover script effectively sets the parallelism RMAN uses. For example, if you allocate five channels, you can have up to five parallel streams restoring datafiles.

Applying Incremental Backups
Similarly, when you are applying incremental backups, the number of channels you allocate determines the potential parallelism.

Applying Redo Logs
RMAN applies redo logs using a specific number of parallel processes as determined by the setting for the RECOVERY_PARALLELISM initialization parameter
===============end paste============

2) what is the relation of RECOVERY_PARALLELISM in parallel recovery with RMAN ? i always know it is used only for crash instance recovery.

Thanks

1.My database is in nonarchive log mode(8.1.7) ,Unix Platform.
2. I want to take whole database rman backup.
3. After shutting down the database,I opened the data base in mount mode;
4.After putting rman at the dollar prompt
RMAN>connect target sys/password
RMAN-06005: connected to target database: ZOCC (DBID=3872307383)

What is the next step to be taken ?

All the write ups I have gone through , are using recovery catalog. I want to do it without recovery catalog. If possible through scripts and RUN command.

Sudatta

Hello again,
went through the relevant portions. all the examples are using recovery catalog for backups. my problem is this

RMAN> connect target sys/manager

RMAN-06005: connected to target database: ZOCC (DBID=3872307383)

RMAN> backup database;

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "backup": expecting one of: "allocate, alter, beginline, ca
talog, change, connect, create, crosscheck, configure, debug, delete, drop, exit, endinline
, host, {, library, list, mount, open, print, register, release, replace, report, renormali
ze, reset, resync, rman, rpct"
RMAN-01007: at line 1 column 1 file: standard input

RMAN>
when I query the v$backup_device it shows the following.

SQL> select * from v$backup_device;

DEVICE_TYPE
-----------------
DEVICE_NAME
--------------------------------------------------------------------------------
SBT_TAPE


Is it refusing disk backup because of the SBT_TAPE or I am missing some steps.

Hi Tom

The following is our requirement

We are trying to write an RMAN script to backup all datafiles as image copies in 9.2.0.4 database.

In view of this we would like to create a script with copy commands dynamically from v$datafile;

example

copy datafile 'C:\ORACLE\ORADATA\AKASH\EXAMPLE01.DBF' to '\\NAD0019SB02\ORACLEBACKUPS\TEST\FRI\EXAMPLE01.DBF';

In the above example RMAN expects to append the file name of the datafile at the end eg:'EXAMPLE01.DBF';

To create this we have used


connect / as sysdba
set echo off
set linesize 200
set pagesize 0
set heading off
set feedback off
spool c:\temp\test.sql
select 'copy datafile ''' || name || ''' to ''\\NAD0019SB02\ORACLEBACKUPS\TEST\' || upper(to_char(trunc(sysdate,'dd'),'dy')) ||'\'';'from v$datafile order by name;
spool off

and the output looks like

copy datafile 'C:\ORACLE\ORADATA\AKASH\EXAMPLE01.DBF' to '\\NAD0019SB02\ORACLEBACKUPS\TEST\FRI\';
....
....
....

However executing at rman prompt creates the following error due to the missing file name at the end as shown below

RMAN> run
2> {
3> allocate channel Channel1 type DISK FORMAT '\\NAD0019SB02\ORACLEBACKUPS\TEST\
Full_%d%T_%u_%p_%c';
4> @c:\temp\test.sql
5> copy datafile 'C:\ORACLE\ORADATA\AKASH\EXAMPLE01.DBF' to '\\NAD0019SB02\ORACL
EBACKUPS\TEST\FRI\';

6> copy datafile 'C:\ORACLE\ORADATA\AKASH\INDX01.DBF' to '\\NAD0019SB02\ORACLEBA
CKUPS\TEST\FRI\';

7> copy datafile 'C:\ORACLE\ORADATA\AKASH\SYSTEM01.DBF' to '\\NAD0019SB02\ORACLE
BACKUPS\TEST\FRI\';

8> copy datafile 'C:\ORACLE\ORADATA\AKASH\TOOLS01.DBF' to '\\NAD0019SB02\ORACLEB
ACKUPS\TEST\FRI\';

9> copy datafile 'C:\ORACLE\ORADATA\AKASH\UNDOTBS01.DBF' to '\\NAD0019SB02\ORACL
EBACKUPS\TEST\FRI\';

10> copy datafile 'C:\ORACLE\ORADATA\AKASH\USERS01.DBF' to '\\NAD0019SB02\ORACLE
BACKUPS\TEST\FRI\';

11> **end-of-file**
12> }
released channel: ORA_DISK_1
allocated channel: Channel1
channel Channel1: sid=15 devtype=DISK

Starting copy at 27-APR-07
released channel: Channel1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of copy command on Channel1 channel at 04/27/2007 15:46:52
ORA-19504: failed to create file "\\NAD0019SB02\ORACLEBACKUPS\TEST\FRI\"
ORA-27038: skgfrcre: file exists
OSD-04010: <create> option specified, file already exists
ORA-19600: input file is datafile 3 (C:\ORACLE\ORADATA\AKASH\EXAMPLE01.DBF)
ORA-19601: output file is datafile-copy 0 (\\NAD0019SB02\ORACLEBACKUPS\TEST\FRI\
)

So how do we dynamically add the filename at the end of the copy command.

thank you very much
devi

Hi Tom

I backuped the database to a non-default location, as follows.

run{
SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\BACKUP_DB1\Sunday_ControlFile%F';
backup incremental level 0 database format='d:\backup_db1\Sunday_%u%p%c' tag=sunday_backup;
}


What is the syntax for restoring the above database from the same non-default location 'd:\backup_dpssdb1\' ?


I can restore the controlfile, the "device type disk" tells it the non-default location.

run {
set controlfile autobackup format for device type disk to 'D:\BACKUP_DB1\Sunday_ControlFile%F';
restore control file from autobackup;
}



but am having problem with the datafiles. It always tries to look for the backup in the flash recovery area.


Thank you for your help.

Hey Tom,

Running an RMAN backup on a test box (10.2.0.2.0) - but it's not doing what I'd expect it to do. It doesn't seem to consider any of the datafile backups as obsolete:

RMAN> show all;

using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'X:\RMANBACKUP\c
f_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   'X:\RMANBACKUP\%d_%T_%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 'X:\RMANBACKUP\SNCFOPERA.ORA';

RMAN> list backup of database summary;


List of Backups
===============
Key     TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
------- -- -- - ----------- --------------- ------- ------- ---------- ---
6       B  F  A DISK        20-OCT-07       1       1       NO         TAG200710
20T221416
7       B  F  A DISK        20-OCT-07       1       1       NO         TAG200710
20T221416
13      B  1  A DISK        21-OCT-07       1       1       NO         TAG200710
21T153710
22      B  1  A DISK        21-OCT-07       1       1       NO         TAG200710
21T224703
26      B  1  A DISK        22-OCT-07       1       1       NO         TAG200710
22T030018
30      B  1  A DISK        23-OCT-07       1       1       NO         TAG200710
23T030040
35      B  1  A DISK        24-OCT-07       1       1       NO         TAG200710
24T030024
39      B  1  A DISK        25-OCT-07       1       1       NO         TAG200710
25T030031
43      B  1  A DISK        26-OCT-07       1       1       NO         TAG200710
26T030041
47      B  1  A DISK        27-OCT-07       1       1       NO         TAG200710
27T030032
51      B  1  A DISK        28-OCT-07       1       1       NO         TAG200710
28T030032
55      B  1  A DISK        29-OCT-07       1       1       NO         TAG200710
29T030031
59      B  1  A DISK        30-OCT-07       1       1       NO         TAG200710
30T030034
63      B  1  A DISK        31-OCT-07       1       1       NO         TAG200710
31T030032
67      B  1  A DISK        01-NOV-07       1       1       NO         TAG200711
01T030022
71      B  1  A DISK        02-NOV-07       1       1       NO         TAG200711
02T030035
75      B  1  A DISK        03-NOV-07       1       1       NO         TAG200711
03T030031

RMAN> report obsolete;

RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 3
Report of obsolete backups and copies
Type                 Key    Completion Time    Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set           53     28-OCT-07
  Backup Piece       53     28-OCT-07          X:\RMANBACKUP\CF_C-2312602202-200
71028-00
Backup Set           57     29-OCT-07
  Backup Piece       57     29-OCT-07          X:\RMANBACKUP\CF_C-2312602202-200
71029-00
Backup Set           61     30-OCT-07
  Backup Piece       61     30-OCT-07          X:\RMANBACKUP\CF_C-2312602202-200
71030-00
Backup Set           65     31-OCT-07
  Backup Piece       65     31-OCT-07          X:\RMANBACKUP\CF_C-2312602202-200
71031-00

So, if my retention policy is redundancy 3, and I'm running nightly level 1 backups, why are my old backups not obsolete?

I'm guessing maybe it has to do with the fact that I started with a full backup (not incremental), and my first incremental was a level 1 - is that why it is holding the old full backup?

I'd have thought, from the docs, that the inc level 1 would make itself an inc level 0 if there was no level 0 backup - and so it should be able to age out the old full backup.

Any idea what I'm missing?

Thanks

Tom,
Hope "U" remeber me :-)

I m stuck with this problem

I took complete backup of a database (databse name>>my) using RMAN CLI ( c:\rman nocatalog  target username/password@my   ), then to see how to restore some missing component I removed a dbf file  and got it restored (successful).

Now I removed a control file while DB is shut, now I cant connect to RMAN using previous command i.e c:\rman nocatalog  target username/password@my

Then what I did was using sqlplus I started the DB in NOMOUNT mode so that it doesn¿t look for control file, then again I connect to RMAN , but it says

 

 

C:\Documents and Settings\at0039277>rman nocatalog target wazza/rooney@my

 

Recovery Manager: Release 10.1.0.2.0 - Production

 

Copyright (c) 1995, 2004, Oracle.  All rights reserved.

 

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

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

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

RMAN-00554: initialization of internal recovery manager package failed

RMAN-04005: error from target database:

ORA-12528: TNS:listener: all appropriate instances are blocking new connections

 

 

My database is >>

 

SQL> startup nomount ;

ORACLE instance started.

 

Total System Global Area  171966464 bytes

Fixed Size                   787988 bytes

Variable Size             145750508 bytes

Database Buffers           25165824 bytes

Redo Buffers                 262144 bytes

SQL>

 

 

 

 

 

 

I don¿t know if it¿s the right way to restore and recover a control file¿¿. Could you please suggest some other way to restore it .

What if i dont have another control file to fall back upon... i want to restore the control file that i have stored in backup...then how am i supposed to do it ?

Looks like your problem is that you cannot connect to the database when it is in nomount mode. If you are using dynamic registration with the listener, you cannot normally connect to the database in nomount mode since the database has not registered with the listener. There are 3 ways around it:

a) use static registration with listener by making an entry for the database in listener.ora and restarting the listener.
b) if you are running RMAN on the database server itself, set oracle_sid=my rman target / will connect you to the database in nomount mode.
c) in the TNS entry for the database use UR=A. Example

(SERVER = DEDICATED)
(SERVICE_NAME = my)(UR=A)

As for restoring the controlfile from backup, please see the backup and recovery related documentation.

Hope this will help.

I was able to log into RMAN in nomount mode by the c) option
i.e in the TNS entry for the database use UR=A. Example
(SERVER = DEDICATED)
(SERVICE_NAME = my)(UR=A)


and Thank you Tom for the response

Right now in our production environment we have the following setup

Level 0 backup on Sunday, 2 level 1 backups (we have a critical transaction processing job that runs every night, one level 1 before the processing and one level 1 after the processing). Recently these level 1 backups have been taking longer and longer adding more time to the job. We are looking for alternatives to taking the two level 1 backups. Does this sound right ?

Take a level 0 backup on Sunday, level 1 backup every day at some point say 4:00 pm or 5:00 pm and then before the transaction job we would switch archive logs and get the max archived seq and log it in a file and similarly after the job. Using this information we should be able to recover to those points without actually taking level 1 backups right ?

Thanks.

"You need to have all of the archives since the level 0 - assuming you are not using disk based recovery and further assuming you are not catching your backup up."

What do you mean by disk-based recovery ?

When you say catching your backup up, are you referring to "incrementally updated backups?" I have been reading about this and I have just starting testing this out. Would you recommend this as a standard backup strategy for all databases ? Can you list some advantages / disadvantages to this strategy ?

Have a question about this backup... In this case, we would always have one level 0 backup taken the first time and then we would be catching the same level 0 backup forever, right ? Now what if this one copy of the backup gets corrupted ? Then we would not have any other previous backup to go to right ?

Can this strategy also be used to refresh non prod environments from prod ?

I forgot to mention that we are using Oracle 10.2.0.4. Does the incrementally updated backups apply to this version too ?

Thank you for your response. I have taken an incrementally updated environment in one test environment and trying to recover in another environment. This is the command that I ran

RMAN> run
2> {
3> recover copy of database with tag 'test_inc_bkp';
4> backup incremental level 1 for recover of copy with tag 'test_inc_bkp' database;
5> }

This created some image copies under flash_recovery_area/datafile directory. If we need to restore these image copies to another environment what do we need to do. I tried to run a simple restore command and that error'ed out. Need help trying to understand how that restore would work.

RMAN> run
2> {
3> allocate channel aux1 device type disk;
4> set newname for datafile 1 to '/oradata/testdb/system01.dbf';
5> set newname for datafile 2 to '/oradata/testdb/undotbs01.dbf';
set newname for datafile 3 to '/oradata/testdb/sysaux01.dbf';
set newname for datafile 4 to '/oradata/testdb/users01.dbf';
set newname for datafile 5 to '/oradata/testdb/data01.dbf';
set newname for datafile 6 to '/oradata/testdb/index01.dbf';6> 7> 8> 9>
10> restore database;
}

Error is shown below.

Starting restore at 02-FEB-09

creating datafile fno=1 name=/oradata/testdb/system01.dbf
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/02/2009 13:17:10
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '/orahome/oradata/db1/system01.dbf'

Yes and moreover my set new name is setting the destination to /orahome/oradata/testdb, so why is the restore trying to create to /orahome/oradata/db1

executing Memory Script

executing command: SET NEWNAME  <<<=====
.....


Starting restore at ...

RMAN> run { set newname for datafile 1 to '/tmp/xxx.dbf'; }

executing command: SET NEWNAME

/oradata/db1> touch test

/oradata/db1> ls -ltr
total 0
-rw-r----- 1 oracle dba 0 Feb 2 17:28 test

/oradata/testdb> touch test

/oradata/testdb> ls -ltr test
-rw-r----- 1 oracle dba 0 Feb 2 17:28 test


RMAN> run
2> {
3> allocate channel aux1 device type disk;
4> set newname for datafile 1 to '/oradata/testdb/system01.dbf';
5> set newname for datafile 2 to '/oradata/testdb/undotbs01.dbf';
set newname for datafile 3 to '/oradata/testdb/sysaux01.dbf';
set newname for datafile 4 to '/oradata/testdb/users01.dbf';
set newname for datafile 5 to '/oradata/testdb/data_01.dbf';
set newname for datafile 6 to '/oradata/testdb/index_01.dbf';6> 7> 8> 9>
10> restore database;
11> }

allocated channel: aux1
channel aux1: sid=153 devtype=DISK

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 02-FEB-09

creating datafile fno=1 name=/oradata/testdb/system01.dbf
released channel: aux1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/02/2009 13:17:10
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '/orahome/oradata/db1/system01.dbf'

RMAN> exit


Recovery Manager complete.

RMAN> run
{
allocate channel aux1 device type disk;
set newname for datafile 1 to '/home/ora10gr2/oradata/xxx/system01.dbf';
set newname for datafile 4 to '/home/ora10gr2/oradata/xxx/users01.dbf';
set newname for datafile 3 to '/home/ora10gr2/oradata/xxx/sysaux01.dbf';
set newname for datafile 5 to '/home/ora10gr2/oradata/xxx/o1_mf_undotbs_4rjnw1w7_.dbf.dbf';
restore database;
}
2> 3> 4> 5> 6> 7> 8> 9>
allocated channel: aux1
channel aux1: sid=286 devtype=DISK

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 03-FEB-09

channel aux1: starting datafile backupset restore
channel aux1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /home/ora10gr2/oradata/xxx/system01.dbf
restoring datafile 00003 to /home/ora10gr2/oradata/xxx/sysaux01.dbf
restoring datafile 00004 to /home/ora10gr2/oradata/xxx/users01.dbf

I am using 10gR2. I get the same output like you if I do a normal level 0 rman backup and try to restore to another environment. The test I am doing here is using incrementally updated backups. I have taken the backup from one environment, copied the image copies and trying to restore to another environment. Do you have a worked out example/ test case for this scenario ?

Step 1: Taken an incrementally updated image copy backup from a test database using the following:

run
{
recover copy of database with tag 'test_inc_bkp';
backup incremental level 1 for recover of copy with tag 'test_inc_bkp' database;
}

This generated image copy backups like the following

..overy_area/DG1/datafile> ls -ltr
total 10610896
-rw-r----- 1 oracle dba 2147491840 Jan 30 11:01 o1_mf_data__4r6914z7_.dbf
-rw-r----- 1 oracle dba 1073750016 Jan 30 11:01 o1_mf_idx_g_4r692l7m_.dbf
-rw-r----- 1 oracle dba 492838912 Jan 30 11:02 o1_mf_system_4r6944qf_.dbf
-rw-r----- 1 oracle dba 346038272 Jan 30 11:02 o1_mf_sysaux_4r694y3w_.dbf
-rw-r----- 1 oracle dba 293609472 Jan 30 11:03 o1_mf_undotbs1_4r695f7r_.dbf
-rw-r----- 1 oracle dba 5251072 Jan 30 11:03 o1_mf_users_4r695wh4_.dbf

:..overy_area/DG1/datafile> pwd
/ora.dump/backup/flash_recovery_area/DG1/datafile

Copied these image copy backups to another test environment using scp

Step 2 : Restore on the second test environment.

(a) I have init.ora, password files and I have done a startup nomount

startup nomount pfile='/orahome/OraHome102/dbs/inittestdb.ora';

rman target /

restore controlfile from autobackup ;

sql 'alter database mount';

run
{
allocate channel aux1 device type disk;
set newname for datafile 1 to '/oradata/testdb/system01.dbf';
set newname for datafile 2 to '/oradata/testdb/undotbs01.dbf';
set newname for datafile 3 to '/oradata/testdb/sysaux01.dbf';
set newname for datafile 4 to '/oradata/testdb/users01.dbf';
set newname for datafile 5 to '/oradata/testdb/data_01.dbf';
set newname for datafile 6 to '/oradata/testdb/index_01.dbf';
restore database;
}

This is when I am encountering the error.

RMAN> run
{
allocate channel aux1 device type disk;
set newname for datafile 1 to '/home/ora10gr2/oradata/xxx/system01.dbf';
set newname for datafile 4 to '/home/ora10gr2/oradata/xxx/users01.dbf';
set newname for datafile 3 to '/home/ora10gr2/oradata/xxx/sysaux01.dbf';
set newname for datafile 5 to '/home/ora10gr2/oradata/xxx/o1_mf_undotbs_4rjnw1w7_.dbf.dbf';
restore database;
}
2> 3> 4> 5> 6> 7> 8> 9>
allocated channel: aux1
channel aux1: sid=285 devtype=DISK

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

executing command: SET NEWNAME

Starting restore at 03-FEB-09

channel aux1: restoring datafile 00001
input datafile copy recid=2 stamp=677850377 filename=/home/ora10gr2/oradata/fbra/ORA10GR2/datafile/o1_mf_system_4rjx6471_.dbf
destination for restore of datafile 00001: /home/ora10gr2/oradata/xxx/system01.dbf
....

Just a quick verification question, did you do the backup as an image copy backup ? Do you have the script that you used ? Just looking for something to go with before I open an SR.

I was just talking to a colleague and he happened to mention that he created an SR with Oracle support a few months back about restoring an incrementally updated image copy backup from one environment to another and he tells me that Oracle support came back and said that this strategy is only used for creating backups on the primary site and can be used for disaster recovery but not actually used to refresh from one environment to another. Is this true ?

Ok, that helps.. guess that was false then.. I am also going to try this using the examples above.

Thanks Tom

We have the following policy for deleting archivelogs in our primary database so the flash_recovery_area is maintained.

delete NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'TRUNC(SYSDATE-1)'

But we do not have anything setup for our standby databases, so the flash_recovery_area keeps growing. What is the normal policy to maintain the flash_recovery_area on standby sites ? Is there a separate rman script that can be run. We have both 9i and 10g databases and we want to get options for both versions.

Thanks.

Hi - can you give us some suggestions on the above ?

Thanks for the link above, reg maintaining FRA on standby. Can you elaborate a little more or clarify for our situation ?

We have a primary database and a physical standby. All backups (level 0, level 1, archivelog backups) run from our primary site. From this link above, then all we have to do is

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY

Is that all we have to do ? Will this take care of deleting the logs from the standby as well ? Instead of the "APPLIED ON STANDBY" clause can we specify this based on some timeframe, like delete anything older than 10 days or something like that ?

Hi

When I make the restore from the operating system (not rman),
I can recover by using rman instead of sqlplus.

Rman doesnt allow to use recovery using backup controlfile.
I think it understand automatically.

Do you think making recovery by rman is always better and convinient?

Dear Tom

Seeking your expert advise..

We have a scenario wherein we backup our LIVE databases using bcv (sync bcv, put db in begin backup mode, split, put db in end backup mode, push data from bcv to tape). However, the archivelogs are backed up using RMAN .. (the reasons are a fast backup restore for bcv and an easy maintainence of archive (backup/restore) using recovery catalog.

However, the qa env is fully backed up using RMAN (lvl0 daily)

Fyi, we clone our qa using the live env using 2 methods.. for smaller db's it is very clean.. we use RMAN clone.. & it's done. However, for large db's (>500 gigs), we restore the bcv backup of live of that particular date... so far so good.

Now, the issue is that, when we want to perform a point in time recovery on the (big) restored db (say they want to clone upto a point)..we need to restore some archives as well. In scenarios where the archive volume is less.. we simply restore the archivelogs using 'set archivelog destination to '/tmp'' on production and then copy over the file from prod to qa... However, I am stucj in a situation wherein I have to restore around 350 gigs of archive data from tape!! Now, I am finding difficulty getting support from storage to facilitate that volume on LIVE.

My question - Is there a way I can directly restore archivelog files to another node? I tried connecting from qa machine and listing the backup.. but it says target incarnation not registered in catalog (of course)

Kindly comment what could be BEST for us?

Thanks in anticipation.
Jatin

yes, the target node (qa) can be configured to recognise the tape library - but my problem is that the recovery catalog already has the live db registered there.. and since I restored from bcv backups, the dbid of intented qa is the same as live..

what i have been thiking here here to do is -

I) Configure MML environment setting at alternate client & make sure alternate client is able to connect to media
server.
II) Connect to target (qa) & catalog database & set dbid on rman prompt.
III) At the time of SBT channel allocation use RMAN environment variables to access the MML.
send 'NSR_ENV=(NSR_SERVER=backup-server,NSR_CLIENT=target-server-name)';
IV) Restore require archive log sequence at alternate channel.

1. Will it work?
2. What do I do next?

Should I open resetlogs command on rman prompt? Wont' connect to catalog database after resetlogs register new incarnation in catalog.

How do I rename the database? Should I now use NID?

I am not testing this right now as LIVE DB archivelogs are being backed up using the ONLY rec catalog database.. & my new configurations might lead the LIVE archivelog cleanup to stop as well..

kindly comment.

rgds
jatin

Per the link you have given on March 9, 2009

http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/rman.htm#i1031870

I issued the command,

CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY;

on the standby database in order to delete old archive logs from the flash recovery area of the standby database. When will this take effect ? During what time will the old archivelogs start getting deleted ? Do I have to do anything manually in order for it to take effect the first time ?

Hi - been 2 days since I configured this on my physical standby but the logs are not getting deleted. Can you give me some feedback on what we need to do to get this done ?

The flash recovery area has been growing. Was at 230M and now it is at 334M now. The available filesystem on the box is 83G. The db_Recovery_file_dest_size is set to 4G.

Cool... Thank you very much for the response and the links.

This means that I can set my db_recovery_file_dest_size to something low (that can hold probably 10-15 days of archivelogs), so that my archive log deletion policy on the standby will effectively delete any logs > 10-15 days. Does that make sense to do ?

Hi Tom,

I have two queries on Rman

1. In oracle 10g we have compress backupset command, can we compress the existing backups which is already in the tape. In other words if we upgrade from oracle 9i to oracle 10g, do we still able to compress the existing backups and used it for recovery.

2. I not able to delete only the image copies of datafile . Please let me know how to do it.

thanks
Shaan

This is a continuation to the question about maintenance of flash recovery area on the physical standbys. For our 10g databases, I have followed the suggestion to use the archivelog deletion policy to be set to APPLIED ON STANDBY and since we have flash recovery area on physical standby it makes it easier. How will that work on a 9i environment ?

I am keeping getting an error when doing a datafile image copy with a named target file. It looks like controlfile, spfile image copy target file name resolved to the first name target file.

I could not figure out why? What I did wrong?

backup as copy datafile 1 ; Went through without an error.

Below is the log.

Thanks



rman target /

Recovery Manager: Release 10.2.0.1.0 - Production on Tue May 18 13:59:07 2010

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

connected to target database: ORCL (DBID=1243904500)

RMAN> run {
2> set CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'D:\ORACLE\PRODUCT\
10.2.0\ORADATA\TestDB\contl_sp_back%F';
3> backup as copy datafile 1 format 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\TestDB\SYS
TEM01.DBF';}

executing command: SET CONTROLFILE AUTOBACKUP FORMAT
using target database control file instead of recovery catalog

Starting backup at 18-MAY-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=156 devtype=DISK
channel ORA_DISK_1: starting datafile copy
input datafile fno=00001 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF

output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM01.DBF tag=TAG2010
0518T135913 recid=27 stamp=719330372
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting datafile copy
copying current control file
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/18/2010 13:59:
40
ORA-01580: error creating control backup file D:\ORACLE\PRODUCT\10.2.0\ORADATA\T
ESTDB\SYSTEM01.DBF
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists
continuing other job steps, job failed will not be re-run
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 18-MAY-10
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 05/18/2010 13:59:
42
ORA-19504: failed to create file "D:\ORACLE\PRODUCT\10.2.0\ORADATA\TESTDB\SYSTEM
01.DBF"
ORA-27038: created file already exists
OSD-04010: <create> option specified, file already exists

RMAN> show all;

RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default
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 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 'D:\ORACLE\PRODUCT\10.2.0\DB_2\DATABASE\S
NCFORCL.ORA'; # default

RMAN>
RMAN> backup as copy datafile 1 ;

Starting backup at 18-MAY-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting datafile copy
input datafile fno=00001 name=D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\SYSTEM01.DBF

output filename=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\DATAFILE\O1_MF
_SYSTEM_5Z5SCQOX_.DBF tag=TAG20100518T140735 recid=28 stamp=719330873
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:25
channel ORA_DISK_1: starting datafile copy
copying current control file
output filename=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\CONTROLFILE\O1
_MF_TAG20100518T140735_5Z5SDJT8_.CTL tag=TAG20100518T140735 recid=29 stamp=71933
0881
channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:01
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 18-MAY-10
channel ORA_DISK_1: finished piece 1 at 18-MAY-10
piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\ORCL\BACKUPSET\2010_05
_18\O1_MF_NNSNF_TAG20100518T140735_5Z5SDM4S_.BKP tag=TAG20100518T140735 comment=
NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 18-MAY-10

RMAN>

We are restoring multi-terabyte database in our data center taken from a hot backup on a different database. During the time backup was taken (hot backup ran for more than 30 hours), DBAs created 3 new datafiles. These 3 new datafiles are not part of the hot backup. After the hot backup completed, we backed up controlfile scp'ed it our datacenter for restore purposes.

Using the above controlfile, we mounted the database and started restoring from tapes. We are not using recovery catalog. The restore failed with the following error

RMAN-20201: datafile not found in the recovery catalog
RMAN-06010: error while looking up datafile: 4140

file# 4140 is one of the 3 datafiles.

We are on 10.2.0.4 on Sun SPARC. I am hoping Oracle "touch" the newly created datafiles in our destination and recover database will fill them up using archivelog files.

How to say Oracle to ignore them or just "touch" those 3 datafiles? Any init.ora parameter we need to use or any other RMAN features that I may be missing?

Appreciate your help.

Thanks,

Hi Tom,

The link you have provided doesn't work. It says..

We're sorry, the page you requested was not found.

We have recorded this error (404) to help us fix the problem.
You may wish to try again using one of the tools below.


Thanks,

Hello Tom;


Ley say archivelog sequence 10453 was generated on the 29th.
It is included in the full database backup of 29th and 30th.

When we mount the tape of 29th, and we try to run the below rman command, it searches the archivelog in the backupset of 30th.
As a result, rman session hangs.

RUN
{
allocate channel t1 type 'SBT_TAPE';
restore archivelog sequence 10453;
}



I think by default rman searches the archivelog in the latest backupset.
Is there way to change this behaviour ?
I want rman to restore the archivelog from the backupset of 29th. Not from the 30th

Hello Tom,

Same archivelog was backed up on the 29th and 30th.

When we mount the tape of 29th, by default rman tries to restore the archivelog from the latest backupset which is 30th.

What do I need to do to force the rman to use the backup set of 29th ?

With the database in noarchive log mode, can we do RMAN backup?

Thanks.