RMAN questions

From: Steve Baldwin <stbaldwin_at_multiservice.com>
Date: Tue, 5 May 2009 08:42:46 +1000
Message-ID: <93D38F3A-EBED-4283-A8E9-6A7E703C78CA_at_multiservice.com>



I'm doing a test database recovery and here's what I'm seeing ...

RMAN> run {

2> restore database;
3> recover database;
4> }

Starting restore at 04-MAY-09
using channel ORA_DISK_1

channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to +DATA/rac01d/datafile/ 
system.259.685912417
channel ORA_DISK_1: restoring datafile 00002 to +DATA/rac01d/datafile/ sysaux.260.685912417
channel ORA_DISK_1: restoring datafile 00003 to +DATA/rac01d/datafile/ undotbs1.261.685912417
channel ORA_DISK_1: restoring datafile 00004 to +DATA/rac01d/datafile/ undotbs2.263.685912417
channel ORA_DISK_1: restoring datafile 00005 to +DATA/rac01d/datafile/ users.264.685912417
channel ORA_DISK_1: reading from backup piece /var/oracle/rman-backup/ nbke29ei_1_1
channel ORA_DISK_1: piece handle=/var/oracle/rman-backup/nbke29ei_1_1 tag=TAG20090503T001201
channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:55 Finished restore at 04-MAY-09

Starting recover at 04-MAY-09
using channel ORA_DISK_1

starting media recovery

archived log for thread 1 with sequence 827 is already on disk as file /var/oracle/archive-duplex/1_827_683508574.dbf archived log for thread 1 with sequence 864 is already on disk as file /var/oracle/archive-duplex/1_864_683508574.dbf archived log for thread 1 with sequence 865 is already on disk as file /var/oracle/archive-duplex/1_865_683508574.dbf archived log for thread 2 with sequence 797 is already on disk as file /var/oracle/archive-duplex/2_797_683508574.dbf archived log for thread 2 with sequence 834 is already on disk as file /var/oracle/archive-duplex/2_834_683508574.dbf archived log for thread 2 with sequence 835 is already on disk as file /var/oracle/archive-duplex/2_835_683508574.dbf archived log for thread 1 with sequence 1 is already on disk as file / var/oracle/archive-duplex/1_1_685912535.dbf archived log for thread 2 with sequence 1 is already on disk as file / var/oracle/archive-duplex/2_1_685912535.dbf archived log for thread 2 with sequence 2 is already on disk as file / var/oracle/archive-duplex/2_2_685912535.dbf archived log for thread 2 with sequence 3 is already on disk as file / var/oracle/archive-duplex/2_3_685912535.dbf

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 05/04/2009 17:10:50
RMAN-06053: unable to perform media recovery because of missing log RMAN-06025: no backup of archived log for thread 2 with sequence 833 and starting SCN of 17099297 found to restore RMAN-06025: no backup of archived log for thread 2 with sequence 832 and starting SCN of 17095946 found to restore :
RMAN-06025: no backup of archived log for thread 1 with sequence 829 and starting SCN of 16945318 found to restore RMAN-06025: no backup of archived log for thread 1 with sequence 828 and starting SCN of 16941751 found to restore

Yet it seems that the archived logs *are* present ...

[oracle_at_opbld05 archive-duplex]$ pwd
/var/oracle/archive-duplex
[oracle_at_opbld05 archive-duplex]$ ls -la *833* *832* *828* *829*
-rw-r----- 1 oracle oinstall 687104 May 3 00:42 1_828_683508574.dbf
-rw-r----- 1 oracle oinstall 1489920 May 3 01:12 1_829_683508574.dbf
-rw-r----- 1 oracle oinstall 941056 May 3 02:42 1_832_683508574.dbf
-rw-r----- 1 oracle oinstall 1254912 May 3 03:12 1_833_683508574.dbf
-rw-rw---- 1 oracle oinstall 572416 May 3 15:42 2_828_683508574.dbf
-rw-rw---- 1 oracle oinstall 1393664 May 3 16:12 2_829_683508574.dbf
-rw-rw---- 1 oracle oinstall 588800 May 3 17:42 2_832_683508574.dbf
-rw-rw---- 1 oracle oinstall 6379520 May 3 18:12 2_833_683508574.dbf

What have I missed?

Secondly, is there any way to tell RMAN where to backup its archived logs from? I have duplexed archive logs - I'm logging to FRA (on shared storage) and to local storage on each cluster node. I want RMAN to backup the archived logs from the FRA so that I get a full complement of logs, but it seems that it is instead choosing to backup from the other destination so is only backing up log files from one node.

My backup commands look like this :

RMAN> run {

2> _at__at_config.rman
3> configure controlfile autobackup on;
4> configure controlfile autobackup format for device type disk to '/ 
var/oracle/rman-backup/%F';
5> configure archivelog deletion policy to backed up 5 times to device type disk;
6> configure retention policy to recovery window of 10 days;
7> **end-of-file**
8> _at__at_alloc.rman
9> allocate channel c1 device type disk format '/var/oracle/rman- 
backup/%U';
10> **end-of-file**
11> backup as compressed backupset incremental level 0 database plus archivelog;
12> _at__at_crosscheck.rman
13> crosscheck backup;
14> crosscheck archivelog all;
15> **end-of-file**
16> _at__at_purge.rman
17> delete archivelog all;
18> delete expired backup;
19> delete obsolete;
20> **end-of-file**
21> }

Please let me know if I'm doing anything stupid here. I'm very new to rman. We've been running user-managed backups for years.

Thanks,

Steve

This email is intended solely for the use of the addressee and may contain information that is confidential, proprietary, or both. If you receive this email in error please immediately notify the sender and delete the email.

--

http://www.freelists.org/webpage/oracle-l Received on Mon May 04 2009 - 17:42:46 CDT

Original text of this message