当我们用不同方式创建控制文件的时候，可能会对控制文件中的信息产生不同的影响，下面分别介绍以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” 博客，网站空间，请务必保留此出处
MySQL与Sqlite有何不同？Apr 24, 2025 am 12:12 AMMySQL和SQLite的主要区别在于设计理念和使用场景：1.MySQL适用于大型应用和企业级解决方案，支持高性能和高并发；2.SQLite适合移动应用和桌面软件，轻量级且易于嵌入。
MySQL中的索引是什么？它们如何提高性能？Apr 24, 2025 am 12:09 AMMySQL中的索引是数据库表中一列或多列的有序结构，用于加速数据检索。1）索引通过减少扫描数据量提升查询速度。2）B-Tree索引利用平衡树结构，适合范围查询和排序。3）创建索引使用CREATEINDEX语句，如CREATEINDEXidx_customer_idONorders(customer_id)。4）复合索引可优化多列查询，如CREATEINDEXidx_customer_orderONorders(customer_id,order_date)。5）使用EXPLAIN分析查询计划，避
说明如何使用MySQL中的交易来确保数据一致性。Apr 24, 2025 am 12:09 AM在MySQL中使用事务可以确保数据一致性。1)通过STARTTRANSACTION开始事务，执行SQL操作后用COMMIT提交或ROLLBACK回滚。2)使用SAVEPOINT可以设置保存点，允许部分回滚。3)性能优化建议包括缩短事务时间、避免大规模查询和合理使用隔离级别。
在哪些情况下，您可以选择PostgreSQL而不是MySQL？Apr 24, 2025 am 12:07 AM选择PostgreSQL而非MySQL的场景包括：1)需要复杂查询和高级SQL功能，2)要求严格的数据完整性和ACID遵从性，3)需要高级空间功能，4)处理大数据集时需要高性能。PostgreSQL在这些方面表现出色，适合需要复杂数据处理和高数据完整性的项目。
如何保护MySQL数据库？Apr 24, 2025 am 12:04 AMMySQL数据库的安全可以通过以下措施实现：1.用户权限管理：通过CREATEUSER和GRANT命令严格控制访问权限。2.加密传输：配置SSL/TLS确保数据传输安全。3.数据库备份和恢复：使用mysqldump或mysqlpump定期备份数据。4.高级安全策略：使用防火墙限制访问，并启用审计日志记录操作。5.性能优化与最佳实践：通过索引和查询优化以及定期维护兼顾安全和性能。
您可以使用哪些工具来监视MySQL性能？Apr 23, 2025 am 12:21 AM如何有效监控MySQL性能？使用mysqladmin、SHOWGLOBALSTATUS、PerconaMonitoringandManagement(PMM)和MySQLEnterpriseMonitor等工具。1.使用mysqladmin查看连接数。2.用SHOWGLOBALSTATUS查看查询数。3.PMM提供详细性能数据和图形化界面。4.MySQLEnterpriseMonitor提供丰富的监控功能和报警机制。
MySQL与SQL Server有何不同？Apr 23, 2025 am 12:20 AMMySQL和SQLServer的区别在于：1)MySQL是开源的，适用于Web和嵌入式系统，2)SQLServer是微软的商业产品，适用于企业级应用。两者在存储引擎、性能优化和应用场景上有显着差异，选择时需考虑项目规模和未来扩展性。
在哪些情况下，您可以选择SQL Server而不是MySQL？Apr 23, 2025 am 12:20 AM在需要高可用性、高级安全性和良好集成性的企业级应用场景下，应选择SQLServer而不是MySQL。1)SQLServer提供企业级功能，如高可用性和高级安全性。2)它与微软生态系统如VisualStudio和PowerBI紧密集成。3)SQLServer在性能优化方面表现出色，支持内存优化表和列存储索引。
热AI工具
Undresser.AI Undress
人工智能驱动的应用程序，用于创建逼真的裸体照片
AI Clothes Remover
用于从照片中去除衣服的在线人工智能工具。
Undress AI Tool
免费脱衣服图片
Clothoff.io
AI脱衣机
Video Face Swap
使用我们完全免费的人工智能换脸工具轻松在任何视频中换脸！
热门文章
热工具
Dreamweaver CS6
视觉化网页开发工具
螳螂BT
Mantis是一个易于部署的基于Web的缺陷跟踪工具，用于帮助产品缺陷跟踪。它需要PHP、MySQL和一个Web服务器。请查看我们的演示和托管服务。
SublimeText3 Mac版
神级代码编辑软件(SublimeText3)
VSCode Windows 64位 下载
微软推出的免费、功能强大的一款IDE编辑器
SublimeText3汉化版
中文版，非常好用
