My Oracle Support Banner

Cloning DB with Different db_block_size Can Result in ORA-600 [17585] (Doc ID 172199.1)

Last updated on DECEMBER 11, 2023

Applies to:

Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database - Personal Edition - Version 10.1.0.2 and later
Oracle Database - Standard Edition - Version 10.1.0.2 and later
Information in this document applies to any platform.

Symptoms

When cloning a database from hot backups that for example has a db_block_size of 4k and the new init.ora has db_block_size of 8k you may get an ORA-600 [17585] when running a CREATE CONTROLFILE statement.

Call stack trace:

This can still occur even if you have the "*_IO_SLAVES" parameter commented out in the new init.ora as suggested in <Note 138621.1>.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.