RAC归档日志还原一例

最新推荐文章于 2021-04-04 11:36:57 发布
最新推荐文章于 2021-04-04 11:36:57 发布
阅读量282 收藏
点赞数
文章标签： 数据库
系统环境是10.2.0.5，RAC，归档日志在node1上建立了nfs共享，而node2上没有建立nfs共享。另有一套查询库，通过DSG的同步软件将数据从生产库上同步到查询库上。软件原理是通过传输分析归档日志然后加以应用，总体感觉有点像DG。由于生产库上使用的是增量备份，每天都进行备份。且备份完后会自动删除归档日志。恢复生产库的归档日志的原因是，同步到查询库时失败(采用DSG的备份软件时，当遇到大量DML操作时经常遇到同步失败的情况)，需要重新同步，但归档日志已经被删除，故需要还原归档日志。查询库昨日17:00后的数据同步失败，故需要还原从昨日至今的归档日志。系统环境交代到这，下面是具体的实施步骤。
在node1上进行操作
通过v$archived_log找到17:00以后的归档日志序列号
select sequence#,completion_time from v$archived_log where completion_time > to_date('2012-02-15','hh24:mi:ss');
查询得出从sequence#为16147开始的归档日志为2012-02-17 17:00以后的归档日志
执行
$ rman target /
Recovery Manager: Release 10.2.0.5.0 - Production on Thu Feb 16 13:07:12 2012
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: ZGSCDB (DBID=3629726729)
RMAN> run{
2> allocate channel c1 type disk;
3> allocate channel c2 type disk;
4> allocate channel c3 type disk;
5> allocate channel c4 type disk;
6> set archivelog destination to '/arch_log/restore';
7> restore archivelog from logseq 16147;
8> release channel c1 ;
9> release channel c2;
10> release channel c3;
11> release channel c4;
12> }
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: sid=4834 instance=zgscdb1 devtype=DISK
allocated channel: c2
channel c2: sid=5333 instance=zgscdb1 devtype=DISK
allocated channel: c3
channel c3: sid=4879 instance=zgscdb1 devtype=DISK
allocated channel: c4
channel c4: sid=5317 instance=zgscdb1 devtype=DISK
executing command: SET ARCHIVELOG DESTINATION
Starting restore at 16-FEB-12
released channel: c1
released channel: c2
released channel: c3
released channel: c4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/16/2012 13:10:53
RMAN-20242: specification does not match any archive log in the recovery catalog
RMAN> list archivelog from logseq 16147;
没有任何输出，郁闷。。。。。。。。。
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5115 169.62M DISK 00:00:09 12-FEB-12
        BP Key: 12219 Status: AVAILABLE Compressed: NO Tag: TAG20120212T014331
        Piece Name: /rman_data/zgscdb_rman/ZGSCDB_arch_20120212_0tn33hqa_s5149_p1_C1
  List of Archived Logs in backup set 5115
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  1 13769 12663219622525 11-FEB-12 12663220068092 11-FEB-12
  1 13770 12663220068092 11-FEB-12 12663220426071 11-FEB-12
  1 13771 12663220426071 11-FEB-12 12663220887716 11-FEB-12
  1 13772 12663220887716 11-FEB-12 12663222831310 12-FEB-12
省略部分输出
  List of Archived Logs in backup set 5197
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  2 16176 12670019198216 15-FEB-12 12670023192712 15-FEB-12
  2 16177 12670023192712 15-FEB-12 12670025565356 16-FEB-12
  2 16178 12670025565356 16-FEB-12 12670026143737 16-FEB-12
  2 16179 12670026143737 16-FEB-12 12670026897385 16-FEB-12
  2 16180 12670026897385 16-FEB-12 12670027305649 16-FEB-12
  2 16181 12670027305649 16-FEB-12 12670027693987 16-FEB-12
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5198 13.00G DISK 00:01:07 16-FEB-12
 List of Archived Logs in backup set 5193
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  2 16148 12670010177819 15-FEB-12 12670011207570 15-FEB-12
  2 16149 12670011207570 15-FEB-12 12670012283915 15-FEB-12
  2 16150 12670012283915 15-FEB-12 12670012754302 15-FEB-12
  2 16151 12670012754302 15-FEB-12 12670012969887 15-FEB-12
  2 16152 12670012969887 15-FEB-12 12670013212670 15-FEB-12
  2 16153 12670013212670 15-FEB-12 12670013780868 15-FEB-12
  2 16154 12670013780868 15-FEB-12 12670013976009 15-FEB-12
  2 16155 12670013976009 15-FEB-12 12670015183858 15-FEB-12
  2 16156 12670015183858 15-FEB-12 12670015441965 15-FEB-12
  2 16157 12670015441965 15-FEB-12 12670015599451 15-FEB-12
  2 16158 12670015599451 15-FEB-12 12670015722094 15-FEB-12
  2 16159 12670015722094 15-FEB-12 12670015785593 15-FEB-12
  2 16160 12670015785593 15-FEB-12 12670015847887 15-FEB-12
  2 16161 12670015847887 15-FEB-12 12670016000750 15-FEB-12
  Backup Set Copy #1 of backup set 5193
  Device Type Elapsed Time Completion Time Compressed Tag
  ----------- ------------ --------------- ---------- ---
  DISK 00:03:55 16-FEB-12 NO TAG20120216T010430
    List of Backup Pieces for backup set 5193 Copy #1
    BP Key Pc# Status Piece Name
    ------- --- ----------- ----------
    12560 1 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_39n3e111_s5225_p1_C1
    12561 2 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_39n3e111_s5225_p2_C1
    12562 3 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_39n3e111_s5225_p3_C1
  List of Archived Logs in backup set 5198
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  2 16134 12668052207072 15-FEB-12 12668052339209 15-FEB-12
  2 16135 12668052339209 15-FEB-12 12668052456743 15-FEB-12
  2 16136 12668052456743 15-FEB-12 12668052579080 15-FEB-12
  2 16137 12668052579080 15-FEB-12 12668052695760 15-FEB-12
  2 16138 12668052695760 15-FEB-12 12668056672468 15-FEB-12
  2 16139 12668056672468 15-FEB-12 12668060445745 15-FEB-12
  2 16140 12668060445745 15-FEB-12 12668062444755 15-FEB-12
  2 16141 12668062444755 15-FEB-12 12668660576479 15-FEB-12
  2 16142 12668660576479 15-FEB-12 12668660718987 15-FEB-12
  2 16143 12668660718987 15-FEB-12 12668660871830 15-FEB-12
  2 16144 12668660871830 15-FEB-12 12668661303733 15-FEB-12
  2 16145 12668661303733 15-FEB-12 12668661585953 15-FEB-12
  2 16146 12668661585953 15-FEB-12 12668662079217 15-FEB-12
  2 16147 12668662079217 15-FEB-12 12670010177819 15-FEB-12
  Backup Set Copy #1 of backup set 5198
  Device Type Elapsed Time Completion Time Compressed Tag
  ----------- ------------ --------------- ---------- ---
  DISK 00:01:07 16-FEB-12 NO TAG20120216T010430
    List of Backup Pieces for backup set 5198 Copy #1
    BP Key Pc# Status Piece Name
    ------- --- ----------- ----------
    12573 1 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_3an3e18j_s5226_p1_C1
    12574 2 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_3an3e18j_s5226_p2_C1
    12575 3 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_3an3e18j_s5226_p3_C1
  List of Archived Logs in backup set 5195
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  2 16162 12670016000750 15-FEB-12 12670016088204 15-FEB-12
  2 16163 12670016088204 15-FEB-12 12670016308969 15-FEB-12
  2 16164 12670016308969 15-FEB-12 12670016653192 15-FEB-12
  2 16165 12670016653192 15-FEB-12 12670017027396 15-FEB-12
  2 16166 12670017027396 15-FEB-12 12670017225549 15-FEB-12
  2 16167 12670017225549 15-FEB-12 12670017317060 15-FEB-12
  2 16168 12670017317060 15-FEB-12 12670017393441 15-FEB-12
  2 16169 12670017393441 15-FEB-12 12670017462567 15-FEB-12
  2 16170 12670017462567 15-FEB-12 12670017541021 15-FEB-12
  2 16171 12670017541021 15-FEB-12 12670017654244 15-FEB-12
  2 16172 12670017654244 15-FEB-12 12670017735163 15-FEB-12
  2 16173 12670017735163 15-FEB-12 12670017811611 15-FEB-12
  2 16174 12670017811611 15-FEB-12 12670017888323 15-FEB-12
  2 16175 12670017888323 15-FEB-12 12670019198216 15-FEB-12
  Backup Set Copy #1 of backup set 5195
  Device Type Elapsed Time Completion Time Compressed Tag
  ----------- ------------ --------------- ---------- ---
  DISK 00:03:56 16-FEB-12 NO TAG20120216T010430
    List of Backup Pieces for backup set 5195 Copy #1
    BP Key Pc# Status Piece Name
    ------- --- ----------- ----------
    12566 1 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_38n3e111_s5224_p1_C1
    12567 2 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_38n3e111_s5224_p2_C1
    12568 3 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_38n3e111_s5224_p3_C1
可以看到从日志序列号为16147到16181的归档日志备份全部存。那为什么执行list backup of archivelog from logseq 16147;时没有输出呢？
查了下rman的list语法，执行如下命令
RMAN>list backup of archivelog from time "to_date('2012-02-15 17:00:00','yyyy-mm-dd hh24:mi:ss')";
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5189 287.12M DISK 00:00:04 16-FEB-12
        BP Key: 12552 Status: AVAILABLE Compressed: NO Tag: TAG20120216T010430
        Piece Name: /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_37n3e111_s5223_p1_C1
  List of Archived Logs in backup set 5189
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  1  14153 12670027303388 16-FEB-12 12670027694268 16-FEB-12
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5190 9.98G DISK 00:02:45 16-FEB-12
  List of Archived Logs in backup set 5190
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  1  14131 12668662080221 15-FEB-12 12670012207947 15-FEB-12
  1 14132 12670012207947 15-FEB-12 12670012971251 15-FEB-12
  1 14133 12670012971251 15-FEB-12 12670013978444 15-FEB-12
  1 14134 12670013978444 15-FEB-12 12670015440149 15-FEB-12
  1 14135 12670015440149 15-FEB-12 12670015722540 15-FEB-12
  1 14136 12670015722540 15-FEB-12 12670016001416 15-FEB-12
  Backup Set Copy #1 of backup set 5190
  Device Type Elapsed Time Completion Time Compressed Tag
  ----------- ------------ --------------- ---------- ---
  DISK 00:02:45 16-FEB-12 NO TAG20120216T010430
    List of Backup Pieces for backup set 5190 Copy #1
    BP Key Pc# Status Piece Name
    ------- --- ----------- ----------
    12553 1 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_35n3e111_s5221_p1_C1
    12554 2 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_35n3e111_s5221_p2_C1
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5192 12.30G DISK 00:03:09 16-FEB-12
  List of Archived Logs in backup set 5192
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  1 14137 12670016001416 15-FEB-12 12670016653312 15-FEB-12
  1 14138 12670016653312 15-FEB-12 12670017030219 15-FEB-12
  1 14139 12670017030219 15-FEB-12 12670017394454 15-FEB-12
  1 14140 12670017394454 15-FEB-12 12670017657280 15-FEB-12
  1 14141 12670017657280 15-FEB-12 12670017890908 15-FEB-12
  1 14142 12670017890908 15-FEB-12 12670018260012 15-FEB-12
  1 14143 12670018260012 15-FEB-12 12670020257257 15-FEB-12
  1 14144 12670020257257 15-FEB-12 12670022421290 15-FEB-12
  1 14145 12670022421290 15-FEB-12 12670023190650 15-FEB-12
  1 14146 12670023190650 15-FEB-12 12670024544870 15-FEB-12
  1 14147 12670024544870 15-FEB-12 12670026609312 16-FEB-12
  1 14148 12670026609312 16-FEB-12 12670026743414 16-FEB-12
  1 14149 12670026743414 16-FEB-12 12670026894479 16-FEB-12
  1 14150 12670026894479 16-FEB-12 12670027048502 16-FEB-12
  1 14151 12670027048502 16-FEB-12 12670027176883 16-FEB-12
  1 14152 12670027176883 16-FEB-12 12670027303388 16-FEB-12
  Backup Set Copy #1 of backup set 5192
  Device Type Elapsed Time Completion Time Compressed Tag
  ----------- ------------ --------------- ---------- ---
  DISK 00:03:09 16-FEB-12 NO TAG20120216T010430
    List of Backup Pieces for backup set 5192 Copy #1
    BP Key Pc# Status Piece Name
    ------- --- ----------- ----------
    12557 1 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_32n3e111_s5218_p1_C1
    12558 2 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_32n3e111_s5218_p2_C1
    12559 3 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_32n3e111_s5218_p3_C1
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5193 13.27G DISK 00:03:55 16-FEB-12
  List of Archived Logs in backup set 5193
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  2  16148 12670010177819 15-FEB-12 12670011207570 15-FEB-12
  2 16149 12670011207570 15-FEB-12 12670012283915 15-FEB-12
  2 16150 12670012283915 15-FEB-12 12670012754302 15-FEB-12
  2 16151 12670012754302 15-FEB-12 12670012969887 15-FEB-12
  2 16152 12670012969887 15-FEB-12 12670013212670 15-FEB-12
  2 16153 12670013212670 15-FEB-12 12670013780868 15-FEB-12
  2 16154 12670013780868 15-FEB-12 12670013976009 15-FEB-12
  2 16155 12670013976009 15-FEB-12 12670015183858 15-FEB-12
  2 16156 12670015183858 15-FEB-12 12670015441965 15-FEB-12
  2 16157 12670015441965 15-FEB-12 12670015599451 15-FEB-12
  2 16158 12670015599451 15-FEB-12 12670015722094 15-FEB-12
  2 16159 12670015722094 15-FEB-12 12670015785593 15-FEB-12
  2 16160 12670015785593 15-FEB-12 12670015847887 15-FEB-12
  2 16161 12670015847887 15-FEB-12 12670016000750 15-FEB-12
  Backup Set Copy #1 of backup set 5193
  Device Type Elapsed Time Completion Time Compressed Tag
  ----------- ------------ --------------- ---------- ---
  DISK 00:03:55 16-FEB-12 NO TAG20120216T010430
    List of Backup Pieces for backup set 5193 Copy #1
    BP Key Pc# Status Piece Name
    ------- --- ----------- ----------
    12560 1 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_39n3e111_s5225_p1_C1
    12561 2 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_39n3e111_s5225_p2_C1
    12562 3 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_39n3e111_s5225_p3_C1
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5195 13.28G DISK 00:03:56 16-FEB-12
  List of Archived Logs in backup set 5195
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  2 16162 12670016000750 15-FEB-12 12670016088204 15-FEB-12
  2 16163 12670016088204 15-FEB-12 12670016308969 15-FEB-12
  2 16164 12670016308969 15-FEB-12 12670016653192 15-FEB-12
  2 16165 12670016653192 15-FEB-12 12670017027396 15-FEB-12
  2 16166 12670017027396 15-FEB-12 12670017225549 15-FEB-12
  2 16167 12670017225549 15-FEB-12 12670017317060 15-FEB-12
  2 16168 12670017317060 15-FEB-12 12670017393441 15-FEB-12
  2 16169 12670017393441 15-FEB-12 12670017462567 15-FEB-12
  2 16170 12670017462567 15-FEB-12 12670017541021 15-FEB-12
  2 16171 12670017541021 15-FEB-12 12670017654244 15-FEB-12
  2 16172 12670017654244 15-FEB-12 12670017735163 15-FEB-12
  2 16173 12670017735163 15-FEB-12 12670017811611 15-FEB-12
  2 16174 12670017811611 15-FEB-12 12670017888323 15-FEB-12
  2 16175 12670017888323 15-FEB-12 12670019198216 15-FEB-12
  Backup Set Copy #1 of backup set 5195
  Device Type Elapsed Time Completion Time Compressed Tag
  ----------- ------------ --------------- ---------- ---
  DISK 00:03:56 16-FEB-12 NO TAG20120216T010430
    List of Backup Pieces for backup set 5195 Copy #1
    BP Key Pc# Status Piece Name
    ------- --- ----------- ----------
    12566 1 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_38n3e111_s5224_p1_C1
    12567 2 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_38n3e111_s5224_p2_C1
    12568 3 AVAILABLE /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_38n3e111_s5224_p3_C1
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
5197 3.02G DISK 00:00:26 16-FEB-12
        BP Key: 12572 Status: AVAILABLE Compressed: NO Tag: TAG20120216T010430
        Piece Name: /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_3bn3e18n_s5227_p1_C1
  List of Archived Logs in backup set 5197
  Thrd Seq Low SCN Low Time Next SCN Next Time
  ---- ------- ---------- --------- ---------- ---------
  2 16176 12670019198216 15-FEB-12 12670023192712 15-FEB-12
  2 16177 12670023192712 15-FEB-12 12670025565356 16-FEB-12
  2 16178 12670025565356 16-FEB-12 12670026143737 16-FEB-12
  2 16179 12670026143737 16-FEB-12 12670026897385 16-FEB-12
  2 16180 12670026897385 16-FEB-12 12670027305649 16-FEB-12
  2  16181 12670027305649 16-FEB-12 12670027693987 16-FEB-12
看到都需要的归档日志都包含进去了，满心欢喜的执行如下命令
RMAN> run{
2> allocate channel c1 type disk;
3> allocate channel c2 type disk;
4> allocate channel c3 type disk;
5> allocate channel c4 type disk;
6> set archivelog destination to '/arch_log/restore';
7> restore archivelog from time "to_date('2012-02-15 17:00:00','yyyy-mm-dd hh24:mi:ss')";
8> release channel c1;
9> release channel c2;
10> release channel c3;
11> release channel c4;
12> }
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: sid=4849 instance=zgscdb1 devtype=DISK
allocated channel: c2
channel c2: sid=5326 instance=zgscdb1 devtype=DISK
allocated channel: c3
channel c3: sid=4946 instance=zgscdb1 devtype=DISK
allocated channel: c4
channel c4: sid=4879 instance=zgscdb1 devtype=DISK
executing command: SET ARCHIVELOG DESTINATION
Starting restore at 16-FEB-12
archive log thread 1 sequence 14155 is already on disk as file /arch_log/zgsc_db01_arch/1_14155_743864713.dbf
archive log thread 1 sequence 14156 is already on disk as file /arch_log/zgsc_db01_arch/1_14156_743864713.dbf
archive log thread 1 sequence 14157 is already on disk as file /arch_log/zgsc_db01_arch/1_14157_743864713.dbf
archive log thread 1 sequence 14158 is already on disk as file /arch_log/zgsc_db01_arch/1_14158_743864713.dbf
archive log thread 1 sequence 14159 is already on disk as file /arch_log/zgsc_db01_arch/1_14159_743864713.dbf
archive log thread 1 sequence 14160 is already on disk as file /arch_log/zgsc_db01_arch/1_14160_743864713.dbf
archive log thread 1 sequence 14161 is already on disk as file /arch_log/zgsc_db01_arch/1_14161_743864713.dbf
archive log thread 1 sequence 14162 is already on disk as file /arch_log/zgsc_db01_arch/1_14162_743864713.dbf
archive log thread 1 sequence 14163 is already on disk as file /arch_log/zgsc_db01_arch/1_14163_743864713.dbf
archive log thread 1 sequence 14164 is already on disk as file /arch_log/zgsc_db01_arch/1_14164_743864713.dbf
archive log thread 1 sequence 14165 is already on disk as file /arch_log/zgsc_db01_arch/1_14165_743864713.dbf
released channel: c1
released channel: c2
released channel: c3
released channel: c4
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/16/2012 13:47:51
RMAN-06026: some targets not found - aborting restore
RMAN-06025: no backup of log thread 2 seq 16209 lowscn 12670043591603 found to restore
RMAN-06025: no backup of log thread 2 seq 16208 lowscn 12670043181908 found to restore
RMAN-06025: no backup of log thread 2 seq 16207 lowscn 12670043081120 found to restore
RMAN-06025: no backup of log thread 2 seq 16206 lowscn 12670042973201 found to restore
RMAN-06025: no backup of log thread 2 seq 16205 lowscn 12670042654302 found to restore
RMAN-06025: no backup of log thread 2 seq 16204 lowscn 12670041610965 found to restore
RMAN-06025: no backup of log thread 2 seq 16203 lowscn 12670040751853 found to restore
RMAN-06025: no backup of log thread 2 seq 16202 lowscn 12670040584982 found to restore
RMAN-06025: no backup of log thread 2 seq 16201 lowscn 12670040305341 found to restore
RMAN-06025: no backup of log thread 2 seq 16200 lowscn 12670039987074 found to restore
RMAN-06025: no backup of log thread 2 seq 16199 lowscn 12670039745774 found to restore
RMAN-06025: no backup of log thread 2 seq 16198 lowscn 12670039250107 found to restore
RMAN-06025: no backup of log thread 2 seq 16197 lowscn 12670038751777 found to restore
RMAN-06025: no backup of log thread 2 seq 16196 lowscn 12670038122926 found to restore
RMAN-06025: no backup of log thread 2 seq 16195 lowscn 12670037110291 found to restore
RMAN-06025: no backup of log thread 2 seq 16194 lowscn 12670036384317 found to restore
RMAN-06025: no backup of log thread 2 seq 16193 lowscn 12670036130529 found to restore
RMAN-06025: no backup of log thread 2 seq 16192 lowscn 12670035930022 found to restore
RMAN-06025: no backup of log thread 2 seq 16191 lowscn 12670035736951 found to restore
RMAN-06025: no backup of log thread 2 seq 16190 lowscn 12670034378583 found to restore
RMAN-06025: no backup of log thread 2 seq 16189 lowscn 12670033507562 found to restore
RMAN-06025: no backup of log thread 2 seq 16188 lowscn 12670032888750 found to restore
RMAN-06025: no backup of log thread 2 seq 16187 lowscn 12670031934562 found to restore
RMAN-06025: no backup of log thread 2 seq 16186 lowscn 12670031295273 found to restore
RMAN-06025: no backup of log thread 2 seq 16185 lowscn 12670029669200 found to restore
RMAN-06025: no backup of log thread 2 seq 16184 lowscn 12670029122812 found to restore
RMAN-06025: no backup of log thread 2 seq 16183 lowscn 12670027774997 found to restore
RMAN-06025: no backup of log thread 2 seq 16182 lowscn 12670027693987 found to restore
报错，郁闷，超级郁闷
$ ls /arch_log/zgsc_01_arch
1_14155_743864713.dbf 1_14158_743864713.dbf 1_14161_743864713.dbf 1_14164_743864713.dbf 1_14167_743864713.dbf
1_14156_743864713.dbf 1_14159_743864713.dbf 1_14162_743864713.dbf 1_14165_743864713.dbf
1_14157_743864713.dbf 1_14160_743864713.dbf 1_14163_743864713.dbf 1_14166_743864713.dbf
观察报错发现没有找到的备份信息主要都是thread 2的备份信息，结合上面ls命令的输出分析得出，线程为1日志序列号从14155至14166的归档日志虽然为2012-02-15 17:00之后的归档日志，但却仍再使用。使用restore archivelog from time "to_date('2012-02-15 17:00:00','yyyy-mm-dd hh24:mi:ss')";命令恢复时会提示already on disk。结合list backup of archivelog from time "to_date('2012-02-15 17:00:00','yyyy-mm-dd hh24:mi:ss')";和
node1
$ ls /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_39n3e111_s5225_p1_C1
ls: 0653-341 The file /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_39n3e111_s5225_p1_C1 does not exist
node2
$ ls /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_35n3e111_s5221_p1_C1
ls: 0653-341 The file /rman_data/zgscdb_rman/ZGSCDB_arch_20120216_35n3e111_s5221_p1_C1 does not exist.
发现双节点都只有各自的备份文件，备份文件没有进行存储共享的配置(出于安全考虑，确实不应该把备份配置成共享的，不过设置成nfs挂载应该是没问题)。呵呵，犯了个低级错误。
经过以上分析得出，restore archivelog from time "to_date('2012-02-15 17:00:00','yyyy-mm-dd hh24:mi:ss')";命令会自动查找所需的备份文件进行还原，但是由于双节点无法同时访问所有需要备份文件，故需在特定节点还原指定的日志序列号，进行逐个还原，即 需要在相应的实例上还原相应thread对应的归档日志。
thread的意义： RAC环境下，多台主机同时访问位于共有的磁盘阵列的共同的数据库结构。每台主机上的数据库例程分别写自己的日志文件，不同的例程通过thread来区分。
于是根据list backup of archivelog from time "to_date('2012-02-15 17:00:00','yyyy-mm-dd hh24:mi:ss')"
命令得出的归档日志和备份信息，执行如下命令恢复
在RAC节点node 1上执行
run{
allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
allocate channel c4 type disk;
set archivelog destination to '/arch_log/restore';
restore archivelog from logseq 14131 until logseq 14153 thread 1;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
}
在RAC节点node 2上执行
run{
allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
allocate channel c4 type disk;
set archivelog destination to '/arch_log/restore';
restore archivelog from logseq 16148 until logseq 16181 thread 2;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
}
还原成功。
这里顺带说一句，如果需要进行数据库恢复，那么必须在能够访问所有归档日志的节点上进行，这里是node1

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/29337971/viewspace-1853854/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/29337971/viewspace-1853854/

congbaifu8214
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
RAC开启归档日志
qq_39111199的博客
04-08 469
···············开启归档日志 1.在节点1上用grid用户，关闭数据库集群 [root@rac1 ~]$ su - grid [grid@rac1 ~]$ srvctl stop database -d orcl 2.将一个节点启动到mount状态，在该节点进行以下操作 [grid@rac1 ~]$ srvctl start instance -d orcl -i orcl1 -o mount 3.连接到数据库 [root@rac1 ~]# su - oracle [oracle@rac1
oracle RAC集群开启归档日志.docx
09-23
Oracle RAC 集群开启归档日志 Oracle RAC 集群开启归档日志是指在 Oracle RAC 集群环境中启用归档日志功能，以便提高数据库的可靠性和可维护性。为了实现这一功能，需要修改集群参数文件，重启数据库。 在开启归档...
记一次Oracle 生产库还原归档日志经历(原创)
czmmiao的专栏
02-17 403
中午刚去吃饭，就接到同事电话说急着要恢复生产库上的归档日志。系统环境是10.2.0.5，RAC，归档日志在node1上建立了nfs共享，而node2上没有建立nfs共享。另有一套查询库，通过DSG的同步软件将数据从生产库上同步到查询库上。软件原理是通过传说分析归档日志然后加以应用，总体感觉有点像DG。由于生产库上使用的是增量备份，每天都进行备份。且备份完后会自动删除归档日志。恢复生产库的归档日志的...
RAC环境备份归档日志和恢复数据库方法
congrang4031的博客
02-11 347
环境linuxOracle10.2.0.1归档日志在ASM磁盘组恢复到原来的RAC节点根据Oracle的RAC环境的不同，RMAN备份、恢复操作也是不同的。如果RAC环境是建立在CLUSTER文件系统上的，或者是建立在ASM上的...
RAC环境备份归档日志和RMAN恢复启动数据库
congyan3522的博客
02-01 189
环境linuxOracle10.2.0.1归档日志在ASM磁盘组恢复到原来的RAC节点 根据Oracle的RAC环境的不同，RMAN备份、恢复操作也是不同的。如果RAC环境是建立在CLUSTER文...
rac下的rman的归档日志备份和恢复问题
clx00001的博客
08-16 182
os:aix5.2 oracle:9205 当初安装的时候归档都是在本地做的，现在想用ＲＭＡＮ做归档的备份，我感觉备份的时候应该备份到一个共享空间上去的，但发现备份还是备份到的本地硬盘． 这样的话，恢复的时候会不会出现...
oracle RAC集群修改归档日志路径.docx
09-23
Oracle RAC（Real Application Clusters）...总之，Oracle RAC集群中修改归档日志路径是一项关键任务，它涉及到数据库的稳定运行和灾难恢复能力。遵循正确的步骤和最佳实践，可以确保数据的安全性和系统的高效运行。
关闭11gRAC自动归档日志
10-19
关闭11gRAC自动归档日志
解决Oracle RMAN删除归档日志不释放问题的方法
12-16
Oracle数据库在运行过程中会产生大量的归档日志（Archived Logs），这些日志是数据库恢复的重要组成部分，特别是对于那些需要满足严格数据完整性和法规遵从性的系统。然而，当归档日志空间耗尽时，可能会导致数据库...
解决Oracle数据库归档日志占满磁盘空间问题
09-09
Oracle数据库的归档日志（Archived Logs）是数据库运行过程中不可或缺的一部分，它们记录了数据库事务的更改历史，用于在发生故障时进行恢复。然而，当归档日志占满磁盘空间时，可能导致数据库性能下降甚至无法正常...
Oracle RAC恢复到单机方案-仅有一个全备
05-04
目标：Oracle RAC只有一个历史全备（热备），无增量备份和归档备份，现需恢复到单机上。文档给出具体步骤和可能遇到的错误。
rac 简单归档设置下备份恢复理解
01-11 25
理解最简单的备份方法，理解rman是如何备份与恢复的。集群环境下对归档日志的备份注意事项： 必须保证备份实例上能够访问所有实例的归档日志，否则会报错，除非为各个实例分配通道。 集群环境下恢复注意事项： 进行restore时，为每个实例配置通道，以正确的转储。 进行recover时，当前操作实例必须能够访问所有的归档日志文件，否则可能恢复失败。 以上注意事项在任何归档日志设置情况下成立，只...
RAC启用归档日志
数据之路-忆梦前程
11-26 1097
1.关闭实例 [oracle@RAC1 dbs]$ crsctl status resource -t -------------------------------------------------------------------------------- Name Target State Server State
RAC环境一个实例何时会归档另一个实例的日志
ckawt40802的专栏
03-05 119
有人在我的BLOG上提出问题，为什么有的时候发现一个实例所在的服务器上包含了另一个服务器的归档日志。 其实很多中情况都可能造成这个问题的产生。 最简单的情况，一个节点执行了ALTER SYSTEM ARCHIVE...
RMAN_RAC归档日志备份包恢复到单机
cjh81378066的博客
07-29 256
RAC是ASM的存储且是OMF创建的格式，所以RAC的日志名为如下+ARCH/mioa/archive/1_73554_875548170.dbf、+ARCH/mioa/archive/2_57012_875548170....
oracle rac的归档日志,oracle 11g rac开启归档日志和闪回
weixin_42466331的博客
04-04 552
oracle 11g rac开启归档日志和闪回发布时间：2020-07-01 06:21:14来源：51CTO阅读：2084作者：z597011036栏目：数据库1.查看数据库是否开启归档(查看两个节点rac1和rac2是否开归档日志)SQL> archiveloglistSP2-0734: unknown command beginning "archivelog..." - rest o...
oracle rac的归档日志,oracle RAC－－归档日志的开启方法
weixin_42361635的博客
04-04 227
oracle RAC－－归档日志的开启方法＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝10g R1 要修改cluster_database参数 ，10G R2和以后的版本就不需要了1. 例子(10g R1或之前)：srvctl stop database -d RAC节点1sql>startup mountSQL> alter system set log_ar...
RAC－－归档日志的开启方法
cnqc11810的博客
10-09 125
oracle RAC－－归档日志的开启方法 ＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝＝ 10g R1 要修改cluster_database参数 ，10G R2和...
oracle rac如何删除归档日志
最新发布
05-31
在Oracle RAC中删除归档日志有两种方法： 1. 使用RMAN命令来删除归档日志。在RMAN命令行下，使用delete archivelog命令来删除指定的归档日志。例如： ``` RMAN> delete archivelog all backed up 1 times to ...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值