Srt

Sorry but I have some more information regarding the previous post.

I think that I have found where I have been going wrong.
When I ran the following command during the disaster recovery trial:
RMAN> list archivelog all;
I got the following output (which I saved in my notes):
List of
Key
------968579
969145
969146
969147
969148
969149
969150
969151
969152
969153
969154
969155
969156
969157
969158
969159
969160
969161
969162
969163
969164
969165
969166
969167
969168
969169
969170
969171
969172
969176
969179
969538
969539
969540
969541
969544

Archived Log
Thrd Seq
---- ------1
37662
1
37663
1
37664
1
37665
1
37666
1
37667
1
37668
1
37669
1
37670
1
37671
1
37672
1
37673
1
37674
1
37675
1
37676
1
37677
1
37678
1
37679
1
37680
1
37681
1
37682
1
37683
1
37684
1
37685
1
37686
1
37687
1
37688
1
37689
1
37690
1
37691
1
37692
1
37693
1
37694
1
37695
1
37696
1
37697

Copies
S Low Time
- --------A 11-SEP-08
A 11-SEP-08
A 11-SEP-08
A 11-SEP-08
A 11-SEP-08
A 11-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 12-SEP-08
A 13-SEP-08

Name
---/u02/oradata/JDE/arch/arch_1_37662.dbf
/u02/oradata/JDE/arch/arch_1_37663.dbf
/u02/oradata/JDE/arch/arch_1_37664.dbf
/u02/oradata/JDE/arch/arch_1_37665.dbf
/u02/oradata/JDE/arch/arch_1_37666.dbf
/u02/oradata/JDE/arch/arch_1_37667.dbf
/u02/oradata/JDE/arch/arch_1_37668.dbf
/u02/oradata/JDE/arch/arch_1_37669.dbf
/u02/oradata/JDE/arch/arch_1_37670.dbf
/u02/oradata/JDE/arch/arch_1_37671.dbf
/u02/oradata/JDE/arch/arch_1_37672.dbf
/u02/oradata/JDE/arch/arch_1_37673.dbf
/u02/oradata/JDE/arch/arch_1_37674.dbf
/u02/oradata/JDE/arch/arch_1_37675.dbf
/u02/oradata/JDE/arch/arch_1_37676.dbf
/u02/oradata/JDE/arch/arch_1_37677.dbf
/u02/oradata/JDE/arch/arch_1_37678.dbf
/u02/oradata/JDE/arch/arch_1_37679.dbf
/u02/oradata/JDE/arch/arch_1_37680.dbf
/u02/oradata/JDE/arch/arch_1_37681.dbf
/u02/oradata/JDE/arch/arch_1_37682.dbf
/u02/oradata/JDE/arch/arch_1_37683.dbf
/u02/oradata/JDE/arch/arch_1_37684.dbf
/u02/oradata/JDE/arch/arch_1_37685.dbf
/u02/oradata/JDE/arch/arch_1_37686.dbf
/u02/oradata/JDE/arch/arch_1_37687.dbf
/u02/oradata/JDE/arch/arch_1_37688.dbf
/u02/oradata/JDE/arch/arch_1_37689.dbf
/u02/oradata/JDE/arch/arch_1_37690.dbf
/u02/oradata/JDE/arch/arch_1_37691.dbf
/u02/oradata/JDE/arch/arch_1_37692.dbf
/u02/oradata/JDE/arch/arch_1_37693.dbf
/u02/oradata/JDE/arch/arch_1_37694.dbf
/u02/oradata/JDE/arch/arch_1_37695.dbf
/u02/oradata/JDE/arch/arch_1_37696.dbf
/u02/oradata/JDE/arch/arch_1_37697.dbf

I looked at this and thought that as 37697 was the last archivelog that RMAN
new about (when the
catalog was shut down and backed up at 23:00) then I would restore and
recover to this point (My
primary objective at this stage was to get a database back; applying later
archivelogs written
after the Saturday evening online backup was a secondary consideration).

-----------------11-Sep-2008 06:09:29 PM 11-Sep-2008 11-Sep-2008 06:09:13 PM 11-Sep-2008 11-Sep-2008 08:09:22 PM 11-Sep-2008 11-Sep-2008 09:09:06 PM 11-Sep-2008 11-Sep-2008 10:09:22 PM 11-Sep-2008 11-Sep-2008 11:09:39 PM 12-Sep-2008 12-Sep-2008 12:09:01 AM 12-Sep-2008 12-Sep-2008 01:09:51 AM 12-Sep-2008 12-Sep-2008 01:09:33 AM 12-Sep-2008 12-Sep-2008 01:09:24 AM 12-Sep-2008 12-Sep-2008 01:09:31 AM 12-Sep-2008 12-Sep-2008 01:09:24 AM 12-Sep-2008 12-Sep-2008 01:09:54 AM 12-Sep-2008 12-Sep-2008 02:09:34 AM 12-Sep-2008 12-Sep-2008 02:09:41 AM 12-Sep-2008 .to_char(next_time. I don't have many screen listings from the offsite trial because there was a lot of time pressure to get this working and my documentation of what I actually did was less than scientific.to_char(completion_time.'dd-Mon-yyyy hh:mm:ss PM')compl_time.'dd-M on-yyyy hh:mm:ss PM') next.'dd-Mon-yyyy hh:mm:ss PM') first.I incremented the number 37697 to 37698 (on the set until clause) in order to restore and recover up to and including 37697.--------------------------. I have.to_char(first_time. and found the following: just queried rc_backup_redolog on the live recovery catalog select sequence# seq#. however.---------37662 13-Sep-2008 08:09:13 PM 06:09:13 PM 9535 37663 13-Sep-2008 08:09:37 PM 08:09:22 PM 68615 37664 13-Sep-2008 08:09:38 PM 09:09:06 PM 204798 37665 13-Sep-2008 08:09:12 PM 10:09:22 PM 204798 37666 13-Sep-2008 08:09:12 PM 11:09:39 PM 204798 37667 13-Sep-2008 08:09:44 PM 12:09:01 AM 204798 37668 13-Sep-2008 08:09:43 PM 01:09:51 AM 204797 37669 13-Sep-2008 08:09:22 PM 01:09:33 AM 204798 37670 13-Sep-2008 08:09:21 PM 01:09:24 AM 204798 37671 13-Sep-2008 08:09:23 PM 01:09:31 AM 204798 37672 13-Sep-2008 08:09:07 PM 01:09:24 AM 204795 37673 13-Sep-2008 08:09:07 PM 01:09:54 AM 204793 37674 13-Sep-2008 08:09:08 PM 02:09:34 AM 204797 37675 13-Sep-2008 08:09:07 PM 02:09:41 AM 204798 37676 13-Sep-2008 08:09:58 PM 02:09:28 AM 204798 FIRST NEXT ----------------------.blocks from rc_backup_redolog where completion_time between '13-SEP-2008' and '14-SEP-2008' order by next_time SQL> / SEQ# COMPL_TIME BLOCKS ---------.

I think this means that the last complete archivelog file to actually to be backed up by Saturday evening's backup (18:30 13th September) was 37696. it did seem to know about 37697 (see previous 'LIST' command') and this would also have been available to it on disk from the file system backup restore.37677 13-Sep-2008 03:09:09 AM 204798 37678 13-Sep-2008 03:09:38 AM 204798 37679 13-Sep-2008 03:09:25 AM 204798 37680 13-Sep-2008 07:09:05 AM 204798 37681 13-Sep-2008 08:09:08 AM 204794 37682 13-Sep-2008 09:09:35 AM 204798 37683 13-Sep-2008 10:09:33 AM 204798 37684 13-Sep-2008 10:09:58 AM 204795 37685 13-Sep-2008 12:09:42 PM 204798 37686 13-Sep-2008 12:09:13 PM 204798 37687 13-Sep-2008 01:09:23 PM 204798 37688 13-Sep-2008 02:09:56 PM 204796 37689 13-Sep-2008 03:09:36 PM 204797 37690 13-Sep-2008 03:09:57 PM 204798 37691 13-Sep-2008 04:09:12 PM 204798 37692 13-Sep-2008 06:09:13 PM 194906 37693 13-Sep-2008 08:09:01 PM 96756 37694 13-Sep-2008 10:09:44 PM 204798 37695 13-Sep-2008 10:09:39 PM 204793 37696 13-Sep-2008 12:09:12 AM 204794 08:09:58 PM 12-Sep-2008 02:09:28 AM 12-Sep-2008 08:09:57 PM 12-Sep-2008 03:09:09 AM 12-Sep-2008 08:09:58 PM 12-Sep-2008 03:09:38 AM 12-Sep-2008 08:09:37 PM 12-Sep-2008 03:09:25 AM 12-Sep-2008 08:09:39 PM 12-Sep-2008 07:09:05 AM 12-Sep-2008 08:09:39 PM 12-Sep-2008 08:09:08 AM 12-Sep-2008 08:09:39 PM 12-Sep-2008 09:09:35 AM 12-Sep-2008 08:09:28 PM 12-Sep-2008 10:09:33 AM 12-Sep-2008 08:09:27 PM 12-Sep-2008 10:09:58 AM 12-Sep-2008 08:09:28 PM 12-Sep-2008 12:09:42 PM 12-Sep-2008 08:09:28 PM 12-Sep-2008 12:09:13 PM 12-Sep-2008 08:09:14 PM 12-Sep-2008 01:09:23 PM 12-Sep-2008 08:09:14 PM 12-Sep-2008 02:09:56 PM 12-Sep-2008 08:09:14 PM 12-Sep-2008 03:09:36 PM 12-Sep-2008 08:09:13 PM 12-Sep-2008 03:09:57 PM 12-Sep-2008 08:09:51 PM 12-Sep-2008 04:09:12 PM 12-Sep-2008 08:09:49 PM 12-Sep-2008 06:09:13 PM 12-Sep-2008 08:09:51 PM 12-Sep-2008 08:09:01 PM 12-Sep-2008 08:09:51 PM 12-Sep-2008 10:09:44 PM 12-Sep-2008 08:09:05 PM 12-Sep-2008 10:09:39 PM 13-Sep-2008 35 rows selected. Regardless of what rman actually backed up during the Saturday evening backup. . which was completed very early Saturday morning.

'dd-Mon-yyyy hh:mm:ss PM')compl_time.blocks from rc_backup_redolog where completion_time between '14-SEP-2008' and '15-SEP-2008' order by next_time SEQ# COMPL_TIME BLOCKS ---------.to_char(next_time.'dd-M on-yyyy hh:mm:ss PM') next.I extended the query on rc_backup_redolog to include the Sunday evening's backup in order to get details on 37697 and 37698 select sequence# seq#.'dd-Mon-yyyy hh:mm:ss PM') first.-----------------11-Sep-2008 06:09:29 PM 11-Sep-2008 11-Sep-2008 06:09:13 PM 11-Sep-2008 11-Sep-2008 08:09:22 PM 11-Sep-2008 11-Sep-2008 09:09:06 PM 11-Sep-2008 11-Sep-2008 10:09:22 PM 11-Sep-2008 11-Sep-2008 11:09:39 PM 12-Sep-2008 12-Sep-2008 12:09:01 AM 12-Sep-2008 12-Sep-2008 01:09:51 AM 12-Sep-2008 12-Sep-2008 01:09:33 AM 12-Sep-2008 12-Sep-2008 01:09:24 AM 12-Sep-2008 12-Sep-2008 01:09:31 AM 12-Sep-2008 12-Sep-2008 01:09:24 AM 12-Sep-2008 12-Sep-2008 01:09:54 AM 12-Sep-2008 12-Sep-2008 02:09:34 AM 12-Sep-2008 12-Sep-2008 02:09:41 AM 12-Sep-2008 12-Sep-2008 02:09:28 AM 12-Sep-2008 12-Sep-2008 03:09:09 AM 12-Sep-2008 12-Sep-2008 03:09:38 AM 12-Sep-2008 12-Sep-2008 03:09:25 AM 12-Sep-2008 .--------------------------.---------37662 14-Sep-2008 08:09:55 PM 06:09:13 PM 9535 37663 14-Sep-2008 08:09:15 PM 08:09:22 PM 68615 37664 14-Sep-2008 08:09:45 PM 09:09:06 PM 204798 37665 14-Sep-2008 08:09:44 PM 10:09:22 PM 204798 37666 14-Sep-2008 08:09:16 PM 11:09:39 PM 204798 37667 14-Sep-2008 08:09:17 PM 12:09:01 AM 204798 37668 14-Sep-2008 08:09:52 PM 01:09:51 AM 204797 37669 14-Sep-2008 08:09:53 PM 01:09:33 AM 204798 37670 14-Sep-2008 08:09:53 PM 01:09:24 AM 204798 37671 14-Sep-2008 08:09:27 PM 01:09:31 AM 204798 37672 14-Sep-2008 08:09:28 PM 01:09:24 AM 204795 37673 14-Sep-2008 08:09:27 PM 01:09:54 AM 204793 37674 14-Sep-2008 08:09:12 PM 02:09:34 AM 204797 37675 14-Sep-2008 08:09:12 PM 02:09:41 AM 204798 37676 14-Sep-2008 08:09:12 PM 02:09:28 AM 204798 37677 14-Sep-2008 08:09:13 PM 03:09:09 AM 204798 37678 14-Sep-2008 08:09:58 PM 03:09:38 AM 204798 37679 14-Sep-2008 08:09:58 PM 03:09:25 AM 204798 37680 14-Sep-2008 08:09:58 PM 07:09:05 AM 204798 FIRST NEXT ----------------------.to_char(completion_time.to_char(first_time.

This file was completed just before Satruday evening's backup and so the restore went back to Friday. I can now see that 37697 was the archive logfile that was terminated by the 'alter system switch logfile' command at the start of the Saturday's backup script and that 37698 was the new file that was written to immediately afterwards. I'm also guessing that because rman knew of the existence of 37697 (even if it had not backed it up as of 23:00 Saturday night) that it was able to recover until that point.37681 14-Sep-2008 08:09:08 AM 204794 37682 14-Sep-2008 09:09:35 AM 204798 37683 14-Sep-2008 10:09:33 AM 204798 37684 14-Sep-2008 10:09:58 AM 204795 37685 14-Sep-2008 12:09:42 PM 204798 37686 14-Sep-2008 12:09:13 PM 204798 37687 14-Sep-2008 01:09:23 PM 204798 37688 14-Sep-2008 02:09:56 PM 204796 37689 14-Sep-2008 03:09:36 PM 204797 37690 14-Sep-2008 03:09:57 PM 204798 37691 14-Sep-2008 04:09:12 PM 204798 37692 14-Sep-2008 06:09:13 PM 194906 37693 14-Sep-2008 08:09:01 PM 96756 37694 14-Sep-2008 10:09:44 PM 204798 37695 14-Sep-2008 10:09:39 PM 204793 37696 14-Sep-2008 12:09:12 AM 204794 37697 14-Sep-2008 06:09:15 PM 191972 37698 14-Sep-2008 08:09:13 PM 3681 08:09:58 PM 12-Sep-2008 07:09:05 AM 12-Sep-2008 08:09:43 PM 12-Sep-2008 08:09:08 AM 12-Sep-2008 08:09:43 PM 12-Sep-2008 09:09:35 AM 12-Sep-2008 08:09:44 PM 12-Sep-2008 10:09:33 AM 12-Sep-2008 08:09:43 PM 12-Sep-2008 10:09:58 AM 12-Sep-2008 08:09:28 PM 12-Sep-2008 12:09:42 PM 12-Sep-2008 08:09:28 PM 12-Sep-2008 12:09:13 PM 12-Sep-2008 08:09:29 PM 12-Sep-2008 01:09:23 PM 12-Sep-2008 08:09:28 PM 12-Sep-2008 02:09:56 PM 12-Sep-2008 08:09:08 PM 12-Sep-2008 03:09:36 PM 12-Sep-2008 08:09:08 PM 12-Sep-2008 03:09:57 PM 12-Sep-2008 08:09:08 PM 12-Sep-2008 04:09:12 PM 12-Sep-2008 08:09:06 PM 12-Sep-2008 06:09:13 PM 12-Sep-2008 08:09:49 PM 12-Sep-2008 08:09:01 PM 12-Sep-2008 08:09:49 PM 12-Sep-2008 10:09:44 PM 12-Sep-2008 08:09:49 PM 12-Sep-2008 10:09:39 PM 13-Sep-2008 08:09:49 PM 13-Sep-2008 12:09:12 AM 13-Sep-2008 08:09:02 PM 13-Sep-2008 06:09:15 PM 13-Sep-2008 37 rows selected. but no further. . I'm guessing when I kicked off the restore and recovery that rman decided to recover up to and including 37697.

Sign up to vote on this title
UsefulNot useful