Row Chaining and Migration
Row Chaining and Migration
Overview
If you notice poor performance in your Oracle database Row Chaining and Migration may be one of several reasons, but
prevent some of them by properly designing and/or diagnosing the database.
Row Migration & Row Chaining are two potential problems that can be prevented. By suitably diagnosing, we can impr
database performance. The main considerations are:
Migrated rows affect OLTP systems which use indexed reads to read singleton rows. In the worst case, you can add an e
to all reads which would be really bad. Truly chained rows affect index reads and full table scans.
Oracle Block
The Operating System Block size is the minimum unit of operation (read /write) by the OS and is a property of the OS fi
system. While creating an Oracle database we have to choose the «Data Base Block Size» as a multiple of the Operating
Block size. The minimum unit of operation (read /write) by the Oracle database would be this «Oracle block», and not t
block. Once set, the «Data Base Block Size» cannot be changed during the life of the database (except in case of Oracle
decide on a suitable block size for the database, we take into consideration factors like the size of the database and the co
number of transactions expected.
The database block has the following structure (within the whole database structure)