oracle checkpoint 说明 -凯发app官方网站

凯发app官方网站-凯发k8官网下载客户端中心 | | 凯发app官方网站-凯发k8官网下载客户端中心
  • 博客访问: 2090504
  • 博文数量: 195
  • 博客积分: 4378
  • 博客等级: 上校
  • 技术积分: 4046
  • 用 户 组: 普通用户
  • 注册时间: 2007-09-09 11:37
个人简介

白天和黑夜只交替没交换无法想像对方的世界

文章分类

全部博文(195)

文章存档

2014年(3)

2013年(20)

2012年(18)

2011年(107)

2010年(17)

2009年(5)

2008年(20)

2007年(5)

相关博文
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·
  • ·

分类: oracle

2013-06-19 16:07:12

 

 

一. oracle checkpoint 说明

 1.1  checkpoint

(1)a synchronization event at aspecific point in time

(2)causes some or all dirty blockimages to be written to the database thereby guaranteeing that blocks dirtiedprior to that point in time get written

(3)brings administration up to date

(4)several types of checkpoint exist

 

 

 

1.2  the point of oracle checkpoints

       the point of oracle checkpoints is to synchronize all datafiles, some datafiles orsome objects to a point in time for consistency, performance and recoverabilitypurposes.

  

1.3 buffer cache

       checkpoint与buffer cache 的关系很大,有关buffer cache,之前整理的相关文章如下:

 

 

 

1.3.1 buffer cache 组成

the buffer cache component structures are:

(1)buffers

       eachbuffer may hold an image of one data block at any one time

(2)buffer headers

       =>storemetadata about contents of the buffers

       =>actas cache management structures

(3)buffer pools

       collectionof buffers used for the same purpose and managed accordingly

(4)working set

       =>allor part of a buffer pool

       =>assigned to a dbwn process

 

1.3.2 buffer management

(1) cached buffers managed by doublylinked lists:

(2) repl

              =>bufferscontaining block images being used

(3) repl-aux

             =>buffersready to be used for i/o or cr build

              关于cr 参考:

             

             

(4) write and ckpt-q

             =>dirtybuffers requiring i/o

(5) write-aux

             =>dirtybuffers with i/o in progress

(6) touch count is used to decide theinitial insertion location in the repl chain

(7) aux lists avoid wasteful scanning

 

1.3.3 redo and the buffer cache

(1) block modification dirties thebuffer containing the block image and generates redo

(2) a buffer becomes dirty at aparticular rba which is a point in the redo stream

       关于rba,参考我的blog:

      

      

(3) redo written by lgwr makes thecorresponding part of the redo log file “active”

(4) dirty block images written by dbwnmakes the corresponding part of the redo log file “inactive”

(5) redo is always written priorto the corresponding block images

(6) size of active redo in the logfile influences instance and crash recovery time

(7) trade-off between performance andrecovery time

 

1.3.4 buffer cache i/o

(1)servers look for an availablebuffer on repl-aux then read a data block into selected buffer

      

link url:

阅读(1380) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~
")); function link(t){ var href= $(t).attr('href'); href ="?url=" encodeuricomponent(location.href); $(t).attr('href',href); //setcookie("returnouturl", location.href, 60, "/"); }
网站地图