当我们用不同方式创建控制文件的时候，可能会对控制文件中的信息产生不同的影响，下面分别介绍以noresetlogs方式、resetlogs方式创建控制文件，以查看控制文件中
当我们用不同方式创建控制文件的时候，可能会对控制文件中的信息产生不同的影响，下面分别介绍以noresetlogs方式、resetlogs方式创建控制文件，以查看控制文件中信息的变化。
一：以noresetlogs方式创建控制文件
1 重建控制文件语句如下
startup nomount
create controlfile reuse database crm noresetlogs archivelog
maxlogfiles 16
maxlogmembers 3
maxdatafiles 100
maxinstances 8
maxloghistory 292
logfile
group 1 (
'/oracle/app/db1/dbs/log1crm.dbf',
'/oracle/crm2/crm/redo01b.log'
) size 200m,
group 2 (
'/oracle/app/db1/dbs/log2crm.dbf',
'/oracle/crm2/crm/redo02b.log'
) size 50m,
group 3 (
'/oracle/crm2/crm/redo03.log',
'/oracle/crm2/crm/redo03b.log'
) size 200m,
group 4 (
'/oracle/crm2/crm/redo04.log',
'/oracle/crm2/crm/redo04b.log'
) size 200m,
group 5 (
'/oracle/crm2/crm/redo05.log',
'/oracle/crm2/crm/redo05b.log'
) size 200m,
group 6 (
'/oracle/crm2/crm/redo06.log',
'/oracle/crm2/crm/redo06b.log'
) size 200m
datafile
'/oracle/test/system1.dbf',
'/oracle/test/zxb.dbf',
'/oracle/test/sysaux01.dbf',
'/oracle/test/users01.dbf',
'/oracle/test/zxa.dbf',
'/oracle/test/test1.dbf',
'/oracle/test/zxc.dbf',
'/oracle/test/undotbs1.dbf',
'/oracle/test/zxbig.dbf'
character set zhs16gbk
;
2转储 数据文件头部信息如下：
v10 style file header:
compatibility vsn = 169869568=0xa200100
db id=3601019238=0xd6a33166, db
activation id=0=0x0
control seq=9739=0x260b, file size=640=0x280
file number=4, blksiz=8192, file type=3 data
tablespace #4 - users rel_fn:4
creation at scn: 0x0000.000027b9 10/22/2005 21:45:00
backup taken at scn: 0x0000.00000000 01/01/1988 00:00:00 thread:0
reset logs count:0x2fac7053 scn: 0x0000.802c8c23 reset logs terminal rcv data:0x0 scn: 0x0000.00000000
prev reset logs count:0x2fac6f51 scn: 0x0000.802c3dfd prev reset logs terminal rcv data:0x0 scn: 0x0000.00000000
recovered at 12/05/2012 05:28:04
status:0x0 root dba:0x00000000 chkpt cnt: 1183 ctl cnt:1182
begin-hot-backup file size: 0
checkpointed at scn: 0x0000.8031da6a（2150750826） 11/22/2012 19:25:50
thread:1 rba:(0x1e.c8f.10)
3 转储新控制文件信息如下：
----------------------------------------------------------------------------------------------------
database entry
----------------------------------------------------------------------------------------------------
(size = 316, compat size = 316, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 1, numrecs = 1)
12/05/2012 05:47:51
db name crm
database flags = 0x00400103 0x00001000
controlfile creation timestamp 12/05/2012 05:47:52
incmplt recovery scn: 0x0000.00000000
resetlogs scn: 0x0000.802c8c23 resetlogs timestamp 11/20/2012 07:01:39
prior resetlogs scn: 0x0000.802c3dfd prior resetlogs timestamp 11/20/2012 06:57:21
redo version: compatible=0xa200100
#data files = 9, #online files = 9
database checkpoint: thread=1 scn: 0x0000.a5aaadfd
threads: #enabled=1, #open=0, head=0, tail=0
--------------------------------------------------------------------------------
checkpoint progress records
-------------------------------------------------------------------------------
(size = 8180, compat size = 8180, section max = 11, section in-use = 0,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 2, numrecs = 11)
thread #1 - status:0x0 flags:0x0 dirty:0
low cache rba:(0x0.0.0) on disk rba:(0x0.0.0)
on disk scn: 0x0000.00000000 01/01/1988 00:00:00
resetlogs scn: 0x0000.00000000 01/01/1988 00:00:00
heartbeat: 801186341 mount id: 3609678535
-------------------------------------------------------------------------------------
data file #4:
(name #18) /oracle/test/users01.dbf
creation size=0 block size=8192 status=0x12 head=18 tail=18 dup=1
tablespace 4, index=4 krfil=4 prev_file=0
unrecoverable scn: 0x0000.00000000 01/01/1988 00:00:00
checkpoint cnt:1183 scn: 0x0000.a5aaadfd 01/01/1988 00:00:00
stop scn: 0x0000.a5aaadfd （2779426301）12/05/2012 05:47:52
creation checkpointed at scn: 0x0000.000027b9 10/22/2005 21:45:00
thread:0 rba:(0x0.0.0)
4 转储当前联机日志其最后一个记录如下
redo record - thread:1 rba: 0x000040.0000e490.0160 len: 0x0064 vld: 0x02
scn: 0x0000.a5aaadfb subscn: 1 12/05/2012 04:52:27
change #1 media recovery marker scn:0x0000.00000000 seq: 0 op:23.1
block written - afn: 1 rdba: 0x0040edc8 bft:(1024,4255176) non-bft:(1,60872)
scn: 0x0000.a5aaadf9 seq: 0x07 flg:0x04
block written - afn: 1 rdba: 0x0040006a bft:(1024,4194410) non-bft:(1,106)
scn: 0x0000.a5aaadfa seq: 0x01 flg:0x06
block written - afn: 1 rdba: 0x00400009 bft:(1024,4194313) non-bft:(1,9)
scn: 0x0000.a5aaadfa seq: 0x01 flg:0x04
end of redo dump
----- redo read statistics for thread 1 -----
read rate (async): 29255kb in 41.53s => 0.69 mb/sec
total physical reads: 29255kb
longest record: 10kb, moves: 0/92501 (0%)
change moves: 41327/182885 (22%), moved: 10mb
longest lwn: 1537kb, moves: 7/364 (1%), moved: 6mb
last redo scn: 0x0000.a5aaadfb (2779426299)
5总结：
noresetlogs方式创建控制文件
数据文件头部情况
控制文件中记录数据文件信息
检查点计数值
chkpt cnt: 1183
检查点计数值
checkpoint cnt:1183
检查点scn值
0x8031da6a
检查点scn值
scn: 0xa5aaadfd
redo 块地址
rba:(0x1e.c8f.10)
stop scn
stop scn: 0xa5aaadfd
database checkpoint: thread=1 scn: 0x0000.a5aaadfd
checkpoint cnt:1183 scn: 0x0000.a5aaadfd 01/01/1988 00:00:00
stop scn: 0x0000.a5aaadfd （2779426301）12/05/2012 05:47:52
1 控制文件中记录数据文件检查点计数值信息来自于数据文件头部。
2 控制文件中记录数据文件检查点 scn以及stop scn 值来自于当前日志文件。
3 数据库检查点scn值也来自于当前日志文件。
4 重建控制文件后数据文件头部的rba地址决定了应用归档的开始（0x1e转换为10进制为30）
6 介质恢复过程：（注意红色部分）
执行recover database后按提示输入auto，香港服务器，网站空间，从踪过程可看到恢复的应用归档和联机日志的过程。
parsing in cursor #1 len=34 dep=0 uid=0 oct=35 lid=0 tim=1322909211242292 hv=1214106442 ad='72e77150'
alter database recover database 真正后台恢复语句
end of stmt
parse #1:c=1000,e=1470,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1322909211242288
recovery target incarnation = 1, activation id = 0
influx buffer limit = 12870 (50% x 25740)
successfully allocated 3 recovery slaves
using 367 overflow buffers per recovery slave
start recovery at thread 1 ckpt scn 2150750826 logseq 30 block 3215
*** 2012-12-05 06:10:32.542
media recovery add redo thread 1
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_30_799830099.dbf （从30号归档开始应用）
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_31_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_32_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_33_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_34_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_35_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_36_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_37_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_38_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_39_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_40_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_41_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_42_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_43_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_44_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_45_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_46_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_47_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_48_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_49_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_50_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_51_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_52_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_53_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_54_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_55_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_56_799830099.dbf
=====================
alter database recover continue default
media recovery log /oracle/archive/1_57_799830099.dbf
=====================
alter database recover continue default
end of stmt
media recovery log /oracle/archive/1_58_799830099.dbf
*** 2012-12-05 06:12:59.378
recovery of online redo log: thread 1 group 5 seq 59 reading mem 0
*** 2012-12-05 06:12:59.906
recovery of online redo log: thread 1 group 6 seq 60 reading mem 0
*** 2012-12-05 06:13:00.147
recovery of online redo log: thread 1 group 1 seq 61 reading mem 0
*** 2012-12-05 06:13:00.330
recovery of online redo log: thread 1 group 2 seq 62 reading mem 0
*** 2012-12-05 06:13:00.538
recovery of online redo log: thread 1 group 3 seq 63 reading mem 0
*** 2012-12-05 06:13:03.523
recovery of online redo log: thread 1 group 4 seq 64 reading mem 0
----- redo read statistics for thread 1 -----
read rate (async): 110780kb in 152.42s => 0.71 mb/sec
total physical reads: 110780kb
longest record: 23kb, moves: 0/292927 (0%)
change moves: 113261/562625 (20%), moved: 45mb
longest lwn: 2004kb, moves: 23/4514 (0%), moved: 15mb
last redo scn: 0x0000.a5aaadfb (2779426299)
----------------------------------------------
*** 2012-12-05 06:13:04.986
media recovery drop redo thread 1
file 1 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
file 2 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
file 3 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
file 4 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
file 5 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
file 6 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
file 7 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
file 8 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
file 9 (stop scn 2779426300) completed recovery at checkpoint scn 2779426300
-------------------------------------介质恢复到此处完成-----------------------------------------
二 resetlogs 方式创建控制文件
1 resetlogs方式创建控制文件语句如下：
startup nomount
create controlfile reuse database crm resetlogs archivelog
maxlogfiles 16
maxlogmembers 3
maxdatafiles 100
maxinstances 8
maxloghistory 292
logfile
group 1 (
'/oracle/app/db1/dbs/log1crm.dbf',
'/oracle/crm2/crm/redo01b.log'
) size 200m,
group 2 (
'/oracle/app/db1/dbs/log2crm.dbf',
'/oracle/crm2/crm/redo02b.log'
) size 50m,
group 3 (
'/oracle/crm2/crm/redo03.log',
'/oracle/crm2/crm/redo03b.log'
) size 200m,
group 4 (
'/oracle/crm2/crm/redo04.log',
'/oracle/crm2/crm/redo04b.log'
) size 200m,
group 5 (
'/oracle/crm2/crm/redo05.log',
'/oracle/crm2/crm/redo05b.log'
) size 200m,
group 6 (
'/oracle/crm2/crm/redo06.log',
'/oracle/crm2/crm/redo06b.log'
) size 200m
datafile
'/oracle/test/system1.dbf',
'/oracle/test/zxb.dbf',
'/oracle/test/sysaux01.dbf',
'/oracle/test/users01.dbf',
'/oracle/test/zxa.dbf',
'/oracle/test/test1.dbf',
'/oracle/test/zxc.dbf',
'/oracle/test/undotbs1.dbf',
'/oracle/test/zxbig.dbf'
character set zhs16gbk
;
2 转储数据文件头部信息如下：
v10 style file header:
compatibility vsn = 169869568=0xa200100
db id=3601019238=0xd6a33166, db
activation id=0=0x0
control seq=11044=0x2b24, file size=640=0x280
file number=4, blksiz=8192, file type=3 data
tablespace #4 - users rel_fn:4
creation at scn: 0x0000.000027b9 10/22/2005 21:45:00
backup taken at scn: 0x0000.00000000 01/01/1988 00:00:00 thread:0
reset logs count:0x2fc8ca2a scn: 0x0000.a5ac8ab7 reset logs terminal rcv data:0x0 scn: 0x0000.00000000
prev reset logs count:0x2fc60dc2 scn: 0x0000.a5abe48a prev reset logs terminal rcv data:0x0 scn: 0x0000.00000000
recovered at 12/12/2012 01:00:31
status:0x0 root dba:0x00000000 chkpt cnt: 1285 ctl cnt:1284
begin-hot-backup file size: 0
checkpointed at scn: 0x0000.a5ad6cd4 12/11/2012 23:00:27
thread:1 rba:(0xc.a2df.10)
3 转储控制文件信息如下：
----------------------------------------------------------------------------------------------
database entry
-----------------------------------------------------------------------------------------------
(size = 316, compat size = 316, section max = 1, section in-use = 1,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 1, numrecs = 1)
12/12/2012 01:20:14
db name crm
database flags = 0x00400147 0x00001000
controlfile creation timestamp 12/12/2012 01:20:14
incmplt recovery scn: 0x0000.a5ad6cd4
resetlogs scn: 0x0000.a5ac8ab7 resetlogs timestamp 12/10/2012 19:08:26
prior resetlogs scn: 0x0000.a5abe48a prior resetlogs timestamp 12/08/2012 17:20:02
redo version: compatible=0xa200100
#data files = 9, #online files = 9
database checkpoint: thread=0 scn: 0x0000.00000000
threads: #enabled=1, #open=0, head=0, tail=0
---------------------------------------------------------------------------------------------------
checkpoint progress records
---------------------------------------------------------------------------------------------------
(size = 8180, compat size = 8180, section max = 11, section in-use = 0,
last-recid= 0, old-recno = 0, last-recno = 0)
(extent = 1, blkno = 2, numrecs = 11)
thread #1 - status:0x0 flags:0x0 dirty:0
low cache rba:(0x0.0.0) on disk rba:(0x0.0.0)
on disk scn: 0x0000.00000000 01/01/1988 00:00:00
resetlogs scn: 0x0000.00000000 01/01/1988 00:00:00
heartbeat: 801780265 mount id: 3610283405
---------------------------------------------------------------------------------------------------
data file #4:
----------------------------------------------------------------------------------------------------
(name #18) /oracle/test/users01.dbf
creation size=0 block size=8192 status=0x12 head=18 tail=18 dup=1
tablespace 4, index=4 krfil=4 prev_file=0
unrecoverable scn: 0x0000.00000000 01/01/1988 00:00:00
checkpoint cnt:1285 scn: 0x0000.a5ad6cd4 12/11/2012 23:00:27
stop scn: 0xffff.ffffffff 12/12/2012 01:20:15
creation checkpointed at scn: 0x0000.000027b9 10/22/2005 21:45:00
thread:0 rba:(0x0.0.0)
4总结：
resetlogs方式创建控制文件
数据文件头部情况
控制文件中记录数据文件信息
检查点计数值
chkpt cnt: 1285
检查点计数值
checkpoint cnt:1285
检查点scn值
0x a5ad6cd4
检查点scn值
scn: 0xa5ad6cd4
redo 块地址
rba:( 0xc.a2df.10)
stop scn
stop scn: 0xffff.ffffffff
database checkpoint: thread=0 scn: 0x0000.00000000
low cache rba:(0x0.0.0) on disk rba:(0x0.0.0)
on disk scn: 0x0000.00000000 01/01/1988 00:00:00
1 控制文件中记录数据文件的检查点计数值取自于数据文件头部
2 控制文件中记录的数据文件检查点scn值取自于数据文件头部
3 控制文件中记录数据文件stop scn 为空
4 数据文件头部的rba地址决定了应用归档的开始。
5 介质恢复过程：（注意红色部分）
执行recover database using backup controlfile 按提示先输入auto执行完后在输入cancel。具体跟踪步骤如下：
=====================
parsing in cursor #1 len=60 dep=0 uid=0 oct=35 lid=0 tim=1323483294217660 hv=4023293076 ad='72ee3548'
alter database recover database using backup controlfile 后台执行的恢复语句
end of stmt
parse #1:c=2000,e=75902,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483294217651
recovery target incarnation = 1, activation id = 0
influx buffer limit = 12870 (50% x 25740)
successfully allocated 3 recovery slaves
using 367 overflow buffers per recovery slave
start recovery at thread 1 ckpt scn 2779606228 logseq 12 block 41695
*** 2012-12-12 01:28:13.478
media recovery add redo thread 1
exec #1:c=26995,e=202134,p=9,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=1323483294419926
error #1:err=279 tim=431688214
xctend rlbk=0, rd_only=1
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483298441740 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=829,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483298441733
*** 2012-12-12 01:28:17.604
media recovery log /oracle/archive/1_12_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483299535222 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=433,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483299535218
*** 2012-12-12 01:28:18.724
media recovery log /oracle/archive/1_13_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483299695183 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=1000,e=725,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483299695179
*** 2012-12-12 01:28:18.888
media recovery log /oracle/archive/1_14_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483299740282 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=419,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483299740278
*** 2012-12-12 01:28:18.934
media recovery log /oracle/archive/1_15_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483299786570 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=336,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483299786566
*** 2012-12-12 01:28:18.981
media recovery log /oracle/archive/1_16_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483299832254 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=399,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483299832250
*** 2012-12-12 01:28:19.028
media recovery log /oracle/archive/1_17_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483299876112 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=345,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483299876094
*** 2012-12-12 01:28:19.073
media recovery log /oracle/archive/1_18_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483299926303 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=278,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483299926300
*** 2012-12-12 01:28:19.124
media recovery log /oracle/archive/1_19_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483300165398 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=488,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483300165393
*** 2012-12-12 01:28:19.369
media recovery log /oracle/archive/1_20_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483300227290 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=368,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483300227285
*** 2012-12-12 01:28:19.432
media recovery log /oracle/archive/1_21_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483300279420 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=423,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483300279416
*** 2012-12-12 01:28:19.486
media recovery log /oracle/archive/1_22_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483300352148 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=1000,e=326,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483300352145
*** 2012-12-12 01:28:19.560
media recovery log /oracle/archive/1_23_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483300395658 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=306,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483300395655
*** 2012-12-12 01:28:19.605
media recovery log /oracle/archive/1_24_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483300445677 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=354,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483300445674
*** 2012-12-12 01:28:19.656
media recovery log /oracle/archive/1_25_801688106.dbf
=====================
parsing in cursor #1 len=44 dep=0 uid=0 oct=35 lid=0 tim=1323483300496386 hv=2522010750 ad='72dc70e8'
alter database recover continue default
end of stmt
parse #1:c=0,e=343,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483300496382
*** 2012-12-12 01:28:19.708
media recovery log /oracle/archive/1_26_801688106.dbf
=====================
parsing in cursor #1 len=30 dep=0 uid=0 oct=35 lid=0 tim=1323483300520620 hv=426209255 ad='72dc65c0'
alter database recover cancel 由于seq号为26的归档不存在所以执行此处恢复退出
end of stmt
parse #1:c=0,e=362,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483300520616
----- redo read statistics for thread 1 -----
read rate (async): 501kb in 6.26s => 0.08 mb/sec
total physical reads: 501kb
longest record: 11kb, moves: 0/323 (0%)
change moves: 198/757 (26%), moved: 0mb
longest lwn: 333kb, moves: 0/12 (0%), moved: 0mb
last redo scn: 0x0000.a5ad6da9 (2779606441)
----------------------------------------------
*** 2012-12-12 01:28:19.733
media recovery drop redo thread 1
xctend rlbk=0, rd_only=1
exec #1:c=2999,e=2842075,p=76,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=1323483303362733
*** 2012-12-12 01:31:10.671
---------------------------------------到此处auto执行完成下面为cancel-------------------------------
parse error #1:len=62 dep=0 uid=0 oct=35 lid=0 tim=1323483467452187 err=905
alter database recover database usbing backup controlfile
*** 2012-12-12 01:31:21.663
xctend rlbk=0, rd_only=1
=====================
parsing in cursor #1 len=59 dep=0 uid=0 oct=35 lid=0 tim=1323483478188160 hv=4034011427 ad='72eddf60'
alter database recover database using backup controlfile
end of stmt
parse #1:c=1000,e=1252,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483478188152
recovery target incarnation = 1, activation id = 0
influx buffer limit = 12870 (50% x 25740)
successfully allocated 3 recovery slaves
using 367 overflow buffers per recovery slave
start recovery at thread 1 ckpt scn 2779606446 logseq 26 block 2
*** 2012-12-12 01:31:21.731
media recovery add redo thread 1
exec #1:c=15997,e=67432,p=9,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=1323483478255663
error #1:err=279 tim=431707036
xctend rlbk=0, rd_only=1
=====================
parsing in cursor #1 len=34 dep=0 uid=0 oct=35 lid=0 tim=1323483482042870 hv=3965620631 ad='72dcaa20'
alter database recover cancel
end of stmt
parse #1:c=1000,e=719,p=0,cr=0,cu=0,mis=1,r=0,dep=0,og=1,tim=1323483482042864
*** 2012-12-12 01:31:25.612
media recovery drop redo thread 1
xctend rlbk=0, rd_only=1
exec #1:c=3000,e=2929112,p=0,cr=0,cu=0,mis=0,r=0,dep=0,og=1,tim=1323483484972040
*** 2012-12-12 01:31:38.300
---------------------------------------cancel恢复完成--------------------------------------------------
本文出自 “myblog” 博客，网站空间，请务必保留此出处