This module will discuss the issues surrounding the interaction between Oracle data blocks and the database engine.
As we know,
- the size of the data blocks,
- the structure of the rows on the data blocks and
- the settings of the table storage parameters
all have an effect upon the contents of the data block and the performance of our database.
By the time you finish this module, you should be able to:
One of the most confusing issues surrounding storage space in an Oracle database is setting the proper data block size.
Decide on the best default database block size. The default block size defined by DB_BLOCK_SIZE cannot be changed later without reinstalling the database. Note that Oracle can support multiple block sizes within a single database. The default size for the database blocks is set via the DB_BLOCK_SIZE parameter specified in the parameter file during database creation. Managing the size of the database buffer cache is an important part of managing and tuning the database.
Oracle Databases can be deployed on up to 64,000 datafiles. Because a bigfiletablespace can contain a file that is 1,024 times larger than a smallfiletablespace, and bigfiletablespaces have 32 KB block sizes on 64-bit operating systems, the Oracle Database can grow
to up to 8 exabytes in size (an exabyte is equivalent to a million terabytes). The bigfiletablespace is designed for use with Oracle’s Automatic Storage Management (ASM), other logical volume managers that support striping, and RAID.
The next lesson reviews the db_block_size parameter setting.