Oracle accesses blocks in one of two modes, current or consistent.
A 'db block get' is a current mode get. That is, it's the most up-to-date
copy of the data in that block, as it is right now, or currently. There
can only be one current copy of a block in the buffer cache at any time.
Db block gets generally are used when DML changes data in the database.
In that case, row-level locks are implicitly taken on the updated rows.
There is also at least one well-known case where a select statement does
a db block get, and does not take a lock. That is, when it does a full
table scan or fast full index scan, Oracle will read the segment header
in current mode (multiple times, the number varies based on Oracle version).
A 'consistent get' is when Oracle gets the data in a block which is consistent
with a given point in time, or SCN. The consistent get is at the heart of
Oracle's read consistency mechanism. When blocks are fetched in order to
satisfy a query result set, they are fetched in consistent mode. If no
block in the buffer cache is consistent to the correct point in time, Oracle
will (attempt to) reconstruct that block using the information in the rollback
segments. If it fails to do so, that's when a query errors out with the
much dreaded, much feared, and much misunderstood ORA-1555 "snapshot too old".
A 'db block get' is a current mode get. That is, it's the most up-to-date
copy of the data in that block, as it is right now, or currently. There
can only be one current copy of a block in the buffer cache at any time.
Db block gets generally are used when DML changes data in the database.
In that case, row-level locks are implicitly taken on the updated rows.
There is also at least one well-known case where a select statement does
a db block get, and does not take a lock. That is, when it does a full
table scan or fast full index scan, Oracle will read the segment header
in current mode (multiple times, the number varies based on Oracle version).
A 'consistent get' is when Oracle gets the data in a block which is consistent
with a given point in time, or SCN. The consistent get is at the heart of
Oracle's read consistency mechanism. When blocks are fetched in order to
satisfy a query result set, they are fetched in consistent mode. If no
block in the buffer cache is consistent to the correct point in time, Oracle
will (attempt to) reconstruct that block using the information in the rollback
segments. If it fails to do so, that's when a query errors out with the
much dreaded, much feared, and much misunderstood ORA-1555 "snapshot too old".
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/21993926/viewspace-659692/ ，如需转载，请注明出处，否则将追究法律责任。
上一篇：
Analytic Functions
下一篇：
命名规范
请登录后发表评论
登录
全部评论
最新文章
- PARALLEL_EXECUTION_MESSAGE_SIZE
- some suggestions for rac performance
- ORA-01931: cannot grant UNLIMITED TABLESPACE to a role on 10g
- RMAN-06094 Datafile does not exist
- MRP0: Background Media Recovery terminated with error 1274
- set up a standby quickly by duplicate.
- how to mount diskgroup automatically
- alias doesn't work on solaris
- ORA-00600 [Kfgfinalize_2] While Mounting Diskgroups In Rac [ID 418063.1]
- rac installation on Solaris10 x86-64
