Skip to main content

Everything a DBA Need to Know About Oracle Data Block


<<Back to DB Administration Main Page

What is Oracle Database Block

An oracle data block (DB Block) is a logical unit of data storage. And is the smallest unit of IO for oracle database. The data is physically stored in datafiles (disk files) made up of operating system blocks (OS Blocks). The size of OS blocks can be different than the Oracle DB Block. The OS handles IO in OS blocks while oracle always reads, write data in multiple of DB blocks. The size of oracle DB block can be defined using DB_BLOCK_SIZE init parameter (default 8k ) at the time of database creation and can not be changed later.

You can configure multiple database block size in a database. To be specific you can define block size
for each tablespace (except SYSTEM, SYSAUX).

Oracle Data Block Structure

Now that you know what is oracle data block, Lets have a look how does it looks like. As you can see in the picture above the oracle DB block got a header (also known as block overhead) on top and data on bottom and  the free space lies in between . Database uses the header information to track the data and free space in the block.
An Oracle block overhead consists of header, table directory and row directory and oracle needs this information to manage the block itself.
Block header  => Block header holds general information about the block  eg address of the block on disk, segment type, Transaction information etc.
Table directory => This directory holds information like table metadata whose rows are stored in this block.
Row directory =>  In the form of row address, this holds the information to locate the rows in the block.
The block overhead totals between 84 to 107 bytes.
Like DB Block header every row in the block has its own header, we can call it row header. The row header of each row contains the information about the data stored in that particular row. Before going deep into Oracle DB Block lets have a look at Oracle ROW format as well.

Oracle Database ROW Format

Each row in a block is called row piece. Each row piece has a row header and column data as stated above.

Column Data => This hold the actual data in the row.
ROW Header => Row header contains information like
  • Number of columns in the row.
  • Information about chained and migrated rows.
  • Cluster key for table cluster (if applicable) etc.

Oracle database usages ROWID to uniquely identify a row in the database. The row id is not physically stored in the database, but computed using the file id and block id.
To know more about oracle ROW ID READ HERE

That's said lets get back to our original topic for this Blog ie Oracle Database Block,  And examine the facts little more in detail.  And to do so I have to dump a block and walk you through the dumpfile.
Steps to dump an oracle DB block is provided  HERE

Start dump data blocks tsn: 11 file#:64 minblk 132 maxblk 132
tsn: 11 => v$tablespace.TS#
file#:64 =>  v$datafile.FILE#
minblk & maxblk => dba_extents.BLOCK_ID (range of block ids dumped)
So from this line you can find the rage of blocks dumped (ie 132 to 132- just 1 block) from datafile#64 and Tablespace#11

Block dump from disk: <= self explanatory 

buffer tsn: 11 rdba: 0x10000084 (64/132)
buffer tsn: 11 => Tablespace Number
rdba 0x10000084 (64/132)  => Relative database Block Address.

RDBA is computed using datafile# and block_id and we can verify this as shown below. I got 268435588, decimal equivalent of rdba: 0x10000084. You can find the converter below to convert hex to decimal and vice versa
How to Convert from Hex to Decimal and Vice Versa

Lets compute the RDBA using file# (64) and block id (132)
SQL> select DBMS_UTILITY.MAKE_DATA_BLOCK_ADDRESS(64,132) from dual;
DBMS_UTILITY.MAKE_DATA_BLOCK_ADDRESS(64,132)
--------------------------------------------
                                   268435588

And we got the same number.  We can even extract the file# and Block id from the decimal equivalent of RDBA

SQL> select DBMS_UTILITY.DATA_BLOCK_ADDRESS_FILE(268435588) from dual;
DBMS_UTILITY.DATA_BLOCK_ADDRESS_FILE(268435588)
-----------------------------------------------
                                             64
1 row selected.
SQL> select DBMS_UTILITY.DATA_BLOCK_ADDRESS_BLOCK(268435588) from dual;
DBMS_UTILITY.DATA_BLOCK_ADDRESS_BLOCK(268435588)
------------------------------------------------
                                             132
1 row selected.
And therefore we concluded that the RDBA is calculated using file# and Block id

scn: 0x0.3f1c831 seq: 0x01 flg: 0x06 tail: 0xc8310601
scn: 0x0.3f1c831 => scn the block last modified at
seq: 0x01 => block sequence on this scn ( this tells, how many times a block is modified at this scn)
flg: 0x06=> some kind of flag
tail: 0xc8310601=> SCN + block type + SCN sequence number used to ensure the block consistency
frmt: 0x02 chkval: 0xf684 type: 0x06=trans datafrmt: 0x02 => Oracle7 formated or >=Oracle8 formated block
chkval: 0xf684  => block integrity checking and configured using db_block_checksum init parameter
type: 0x06=trans data => block types 

Object id on Block? Y => object id present on block.

 seg/obj: 0x182ed  csc: 0x00.3f1c577  itc: 2  flg: E  typ: 1 - DATA
 seg/obj: 0x182ed => segment/object number
 SQL>select to_number('182ed', 'xxxxxxxxxx') from dual;   
 SQL> select OWNER,OBJECT_NAME,OBJECT_ID from dba_objects where OBJECT_ID='132877586';

csc: 0x00.3f1c577 => Cleanout System Change number
itc: 2 => interested transaction list count. There are 2 transactions interested  in this block. defaults to 1 and is maintained by storage parameters INITRANS and MAXTRANS.flg: E => Free list flag
 


 Itl           Xid                  Uba         Flag  Lck        Scn/Fsc
0x01   0x0007.020.00007dd6  0x014004e0.2d71.0a  --U-    1  fsc 0x0000.03f1c831
0x02   0x0000.000.00000000  0x00000000.0000.00  ----    0  fsc 0x0000.00000000
Itl => The array index for the list, This value is used in the lock byte (lb:) for a row to show
which transaction has locked the row
Xid => The transaction id of a recent transaction that has modified this block. undo segment . undo slot . undo sequence number
Uba => The undo record address. Absolute block address . block sequence number . record within block
Flag=> flag identifying transaction state
----: active (or “never existed” if every field in the Xid is zero).
--U-: Upper bound commit (also set during “fast commit”).
C---: Committed and cleaned out (all associated lock bytes have been reset to zero).
-B--: May be relevant to the recursive transactions for index block splits.
Lck=> Number of rows locked by this transaction in this block.
Scn/Fsc =>  Depending on the Flag, the commit SCN or the number of bytes of free space that would become available if this transaction committed

tsiz: 0x1f98  => total available space in the block
hsiz: 0x14 => current header size
pbl: 0x7f4533ccf264
     76543210
flag=--------
ntab=1  => number of tables in this block. Unless this block belongs to a cluster, the value is 1
nrow=1  => number of rows stored in this block.
frre=-1
fsbo=0x14  => Beginning Of Free Space
fseo=0x1f8c => End Of Free Space
avsp=0x1f78 => Available Space
tosp=0x1f78 => Total space
0xe:pti[0]      nrow=1  offs=0 => There are 1 rows in table 0, starting at row 0
0x12:pri[0]     offs=0x1f8c =>  Pointer to the row of table 0
block_row_dump:
tab 0, row 0, @0x1f8c => table 0 , row 0, starting byte position 0x1f8c
tl: 12 fb: --H-FL-- lb: 0x1  cc: 2
tl: 12 => total number of bytes for this row. 
fb: --H-FL-- => row flag value
H=> head of the row
F=> First piece of the row
L=> Last piece of the row
means we have the complete row in the block.
lb: 0x1 => lock byte, coming from Itl
cc: 2 => column count
col  0: [ 2]  c1 02           =>  column number and their values in Hexadecimal format
col  1: [ 5]  54 45 53 54 31  =>  column number and their values in Hexadecimal format
end_of_block_dump

Using Hex to ASCII converter you can read the content of table from this code.
Hex to ASCII Convertor

NOTE:- There are too many things and its nearly impossible to reverse engineer the oracle DB block.
depending the type of block you dump and the status of the block at the moment you are dumping etc you will find more or less information in the dump file.
The overall objective of the post is to provide you an idea, about the oracle database block & row format and how oracle manages them

I hope you like the content. Please feel free to write your comment , feedback , suggestion in the comment section below.

Related Posts
How to Convert from Hex to Decimal and Vice Versa
Oracle ROWID Explained
Oracle Database Architecture


Comments

  1. AnonymousApril 6, 2022 at 9:43 PM

    Everything A Dba Need To Know About Oracle Data Block >>>>> Download Now

    >>>>> Download Full

    Everything A Dba Need To Know About Oracle Data Block >>>>> Download LINK

    >>>>> Download Now

    Everything A Dba Need To Know About Oracle Data Block >>>>> Download Full

    >>>>> Download LINK 6V

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Power On/off Oracle Exadata Machine

<<Back to Exadata Main Page How to Power On/off Oracle Exadata Machine Oracle Exadata machines can be powered on/off either by pressing the power button on front of the server or by logging in to the ILOM interface. Powering on servers using  button on front of the server The power on sequence is as follows. 1. Start Rack, including switches  Note:- Ensure the switches have had power applied for a few minutes to complete power on  configuration before starting Exadata Storage Servers 2.Start Exadata Storage Servers  Note:- Ensure all Exadata Storage Servers complete the boot process before starting the   database servers 3. Start Database Servers Powering On Servers Remotely using ILOM The ILOM can be accessed using the Web console, the command-line interface (CLI), IPMI, or SNMP. For example, to apply power to server dm01cel01 using IPMI, where dm01cel01-ilom is the host name of the ILOM for the serve...
Post a Comment
Read more

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...
7 comments
Read more

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:
1 comment
Read more

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.
Post a Comment
Read more

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container
Post a Comment
Read more

ORA-16905: The member was not enabled yet

<<Back to Oracle DataGuard Main Page ORA-16905 Physical Standby Database is disabled DGMGRL> show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database (disabled)       ORA-16905: The member was not enabled yet. Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 58 seconds ago) DGMGRL> DGMGRL> enable database 'ORCL1PS'; Enabled. DGMGRL>  show configuration; Configuration - DG_ORCL1P   Protection Mode: MaxPerformance   Members:   ORCL1PP - Primary database     ORCL1PS - Physical standby database Fast-Start Failover:  Disabled Configuration Status: SUCCESS   (status updated 38 seconds ago)
Post a Comment
Read more

How to Switch Log File from All Instances in RAC

<<Back to Oracle RAC Main Page Switch The Log File of All Instances in Oracle RAC. In many cases you need to switch the logfile of the database. You can switch logfile using alter system switch logfile command but if you want to switch the logfile from all the instances you need to execute the command on all the instances individually and therefore you must login on all the instances. You can avoid this and switch logfile of all instances by just running the below command from any of the instance in RAC database SQL> ALTER SYSTEM SWITCH ALL LOGFILE;   System altered.
Post a Comment
Read more

Starting RMAN and connecting to Database

  <<Back to Oracle Backup & Recovery Main Page Starting RMAN and connecting to Database Starting RMAN and connecting to Database To start RMAN you need to set the environment and type rman and press enter. You can connect to database either using connect command or using command line option. using command line option localhost:$ export ORACLE_HOME=/ora_app/product/18c/dbd2 localhost:$ export PATH=$ORACLE_HOME/bin:$PATH localhost:$ export ORACLE_SID=ORCL1P localhost:$ rman target / Recovery Manager: Release 18.0.0.0.0 - Production on Sun Apr 4 08:11:01 2021 Version 18.11.0.0.0 Copyright (c) 1982, 2018, Oracle and/or its affiliates.  All rights reserved. connected to target database: ORCL1P (DBID=4215484517) RMAN> using connect option localhost:$ rman RMAN> connect target sys@ORCL1P  target database Password:******** connected to target database: ORCL1P (DBID=4215484517) NOTE: To use connect command you need to ensure that  you have proper TNS sentry...
Post a Comment
Read more

How to Attach to a Datapump Job and Check Status of Export or Import

<<Back to Oracle DATAPUMP Main Page How to check the progress of  export or import Jobs You can attach to the export/import  job using ATTACH parameter of oracle datapump utility. Once you are attached to the job you check its status by typing STATUS command. Let us see how Step1>  Find the Export/Import Job Name You can find the datapump job information from  DBA_DATAPUMP_JOBS or  USER_DATAPUMP_JOBS view. SQL> SELECT OWNER_NAME,JOB_NAME,OPERATION,JOB_MODE,STATE from DBA_DATAPUMP_JOBS; OWNER_NAME JOB_NAME                       OPERATION            JOB_MODE   STATE ---------- ------------------------------ -------------------- ---------- ---------- SYSTEM     SYS_EXPORT_FULL_02          ...
7 comments
Read more

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...
Post a Comment
Read more