Oracle Database - (Data|Db|Logical|Oracle) Block or Page

Card Puncher Data Processing

About

Articles which talk about:

At the finest level of granularity in the logical structure of an Oracle Database, the data is stored in data blocks.

The data block sizes should be a multiple of the operating system's block size.

One data block corresponds to a specific number of bytes of physical database space on disk.

The standard block size is specified by the DB_BLOCK_SIZE initialization parameter. A common block size is 8k. In addition, you can specify up to four other block sizes. A database uses and allocates free database space in Oracle Database data blocks.

Oracle Segment Extent Data Block

A block is also see as:

  1. the individual rows,
  2. the set of rows for each possible transaction on the block,
  3. the entire set of rows in the block.

If you had 200,000 rows in a table, deleted half of them, then the table would still 'own' the same number of blocks. See Oracle Database - High Water Mark (HWM) - boundary between used and unused space

Retrieval of block

Blocks may be retrieved and used by the database in one of two ways :

  • current
  • or consistent

A query will generally perform “Oracle Database - Consistent (Read get|Buffer Mode) (CR)” and the term logical I/O refer often to it.

Current get

A current mode get is a retrieval of a block as it exists right now. You will see these most frequently during modification statement, which must update only the latest copy of the block.

Statistic : Oracle Database - (Db Block Get|Current Get) Buffer Mode (CU)

Consistent get

Consistent gets are the retrieval of blocks from the buffer_cache in “read consistent” mode and may include read asides to UNDO (rollback segments).

Statistic : Oracle Database - Consistent (Read get|Buffer Mode) (CR)

Reference





Discover More
Card Puncher Data Processing
IO - Block (Batch on device)

A block is a unit of storage representing a fix number of bytes called the block size. It's also known as the minimum unit of transfer. It implements the concept of batch where data is organized into...
Oracle Segment Extent Data Block
Oracle Database - (Logical) Extent (Unit of Storage)

An extent is a group of contiguous data blocks. An extent can contain data from only one data file. An extent is a logical unit of database storage space allocation made up of a number of (contiguous|ordered)...
Card Puncher Data Processing
Oracle Database - Buffer cache

For many types of operations, Oracle Database uses the buffer cache to store data blocks read from disk. Oracle Database bypasses the buffer cache for particular operations, such as sorting and parallel...
Card Puncher Data Processing
Oracle Database - Compression

By using a data compression algorithm specifically designed for relational data, Oracle is able to compress data much more effectively than standard compression techniques. More significantly, unlike other...
Card Puncher Data Processing
Oracle Database - DB_FILE_MULTIBLOCK_READ_COUNT Parameter

This parameter determines how many database blocks are read in a single I/O (with a single operating system READ call) during a: full table scan or index fast full scan. SQL parallel execution is...
Card Puncher Data Processing
Oracle Database - Database Writer Process (DBWn)

Database writer process (DBWn) is a background process that writes buffers in the database buffer cache to data files. Modified or new data is not necessarily written to a datafile immediately. To reduce...
Card Puncher Data Processing
Oracle Database - High Water Mark (HWM) - boundary between used and unused space

The High water mark is the boundary between used and unused space: for a data file. See or for a segment You can think at the high-water mark (HWM) as the rightmost block that ever contained data...
Card Puncher Data Processing
Oracle Database - Logical Structure

The physical structures of the database contain logical structures: data blocks, extents, segments. tablespaces, and schema objects, Because the physical and logical structures are separate,...
Card Puncher Data Processing
Oracle Database - Physical I/O

A physical read, I/O of table or index data places the block into the buffer cache. Then we perform a logical io to retrieve the block. Hence, most physical read are immediately followed by a logical io....
Card Puncher Data Processing
Oracle Database - Physical Read

The physical read statistic from the autotrace statistics is a measure of how much real I/O, or physical i/o, your query performed. A physical read of table or index data places the block into the buffer...



Share this page:
Follow us:
Task Runner