浅析控制文件的创建-Mysql Tutorial-php.cn

Home

Database

Mysql Tutorial

浅析控制文件的创建

WBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWBOYWB

Jun 07, 2016 pm 05:41 PM

oracle

当我们用不同方式创建控制文件的时候，可能会对控制文件中的信息产生不同的影响，下面分别介绍以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” 博客，网站空间，请务必保留此出处

Statement

The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn

Explain the InnoDB Buffer Pool and its importance for performance.Apr 19, 2025 am 12:24 AM

InnoDBBufferPool reduces disk I/O by caching data and indexing pages, improving database performance. Its working principle includes: 1. Data reading: Read data from BufferPool; 2. Data writing: After modifying the data, write to BufferPool and refresh it to disk regularly; 3. Cache management: Use the LRU algorithm to manage cache pages; 4. Reading mechanism: Load adjacent data pages in advance. By sizing the BufferPool and using multiple instances, database performance can be optimized.

MySQL vs. Other Programming Languages: A ComparisonApr 19, 2025 am 12:22 AM

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

Learning MySQL: A Step-by-Step Guide for New UsersApr 19, 2025 am 12:19 AM

MySQL is worth learning because it is a powerful open source database management system suitable for data storage, management and analysis. 1) MySQL is a relational database that uses SQL to operate data and is suitable for structured data management. 2) The SQL language is the key to interacting with MySQL and supports CRUD operations. 3) The working principle of MySQL includes client/server architecture, storage engine and query optimizer. 4) Basic usage includes creating databases and tables, and advanced usage involves joining tables using JOIN. 5) Common errors include syntax errors and permission issues, and debugging skills include checking syntax and using EXPLAIN commands. 6) Performance optimization involves the use of indexes, optimization of SQL statements and regular maintenance of databases.

MySQL: Essential Skills for Beginners to MasterApr 18, 2025 am 12:24 AM

MySQL is suitable for beginners to learn database skills. 1. Install MySQL server and client tools. 2. Understand basic SQL queries, such as SELECT. 3. Master data operations: create tables, insert, update, and delete data. 4. Learn advanced skills: subquery and window functions. 5. Debugging and optimization: Check syntax, use indexes, avoid SELECT*, and use LIMIT.

MySQL: Structured Data and Relational DatabasesApr 18, 2025 am 12:22 AM

MySQL efficiently manages structured data through table structure and SQL query, and implements inter-table relationships through foreign keys. 1. Define the data format and type when creating a table. 2. Use foreign keys to establish relationships between tables. 3. Improve performance through indexing and query optimization. 4. Regularly backup and monitor databases to ensure data security and performance optimization.

MySQL: Key Features and Capabilities ExplainedApr 18, 2025 am 12:17 AM

MySQL is an open source relational database management system that is widely used in Web development. Its key features include: 1. Supports multiple storage engines, such as InnoDB and MyISAM, suitable for different scenarios; 2. Provides master-slave replication functions to facilitate load balancing and data backup; 3. Improve query efficiency through query optimization and index use.

The Purpose of SQL: Interacting with MySQL DatabasesApr 18, 2025 am 12:12 AM

SQL is used to interact with MySQL database to realize data addition, deletion, modification, inspection and database design. 1) SQL performs data operations through SELECT, INSERT, UPDATE, DELETE statements; 2) Use CREATE, ALTER, DROP statements for database design and management; 3) Complex queries and data analysis are implemented through SQL to improve business decision-making efficiency.

MySQL for Beginners: Getting Started with Database ManagementApr 18, 2025 am 12:10 AM

The basic operations of MySQL include creating databases, tables, and using SQL to perform CRUD operations on data. 1. Create a database: CREATEDATABASEmy_first_db; 2. Create a table: CREATETABLEbooks(idINTAUTO_INCREMENTPRIMARYKEY, titleVARCHAR(100)NOTNULL, authorVARCHAR(100)NOTNULL, published_yearINT); 3. Insert data: INSERTINTObooks(title, author, published_year)VA

See all articles