db_block_size

Oracle 11.1.0:

Oracle 10.2.0:

Oracle 10.1.0:

Oracle 9.2.0:

Oracle 8.1.7:

Oracle 8.0.6:

Oracle 7.3.4:

Related Error Messages:

Cause: DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.

Action: Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.

ORA-00209: control file blocksize mismatch, check alert log for more info

Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.

Action: Look at the alert log for more information.

ORA-00218: block size %s of control file '%s' does not match DB_BLOCK_SIZE (%s)

Cause: The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database.

Action: Restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.

ORA-00374: parameter db_block_size = %s invalid ; must be a multiple of %s in the range [%s..%s]

Cause: invalid value for db_block_size parameter

Action: adjust parameter and restart

ORA-06580: Hash Join ran out of memory while keeping large rows in memory

Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised.

Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increaed.

ORA-07303: ksmcsg: illegal database buffer size.

Cause: The database buffer size must be a multiple of the database block size, and less than the maximum block size.

Action: Verify that the db_block_size parameter is correct in INIT.ORA.

ORA-07305: ksmcsg: illegal database buffer size.

Cause: The database buffer size must be a multiple of the extended cache mapping size for indirect data buffers to be used.

Action: Verify that the db_block_size parameter is correct in INIT.ORA, or disable the use_indirect_data_buffers parameter.

ORA-07620: smscre: illegal database block size

Cause: An illegal database block size was specified in the parameter file. It must be positive, a multiple of 512, and less than the maximum physical i/o data size.

Action: Change db_block_size in the parameter file to conform to these limits.

ORA-09202: sfifi: error identifying file

Cause: db_block_size specified in init.ora could be incorrect

Action: See OSD error accompanying this message

ORA-31004: Length %s of the BLOB in XDB$H_INDEX is below the minimum %s

Cause: In the XDB$H_INDEX table, the CHILDREN column, a BLOB, must have a certain minimum length without being chained. The calculated length of the LOB was less than the stated minimum.

Action: Set the value of the init.ora parameter db_block_size to at least 2K. For XDB to run at its fastest, set db_block_size to 8K.

This parameter is documented in the Oracle Server Reference Guide. Search for more info about [ db_block_size ] on the Oracle FAQ.