APPLIES TO

Oracle Database - Enterprise Edition - Version 11.2.0.4 to 12.2 BETA1 [Release 11.2 to 12.2]

Oracle Database Cloud Schema Service - Version N/A and later

Oracle Database Exadata Cloud Machine - Version N/A and later

Oracle Cloud Infrastructure - Database Service - Version N/A and later

Oracle Database Backup Service - Version N/A and later

Information in this document applies to any platform.

SYMPTOMS

Using RMAN to backup/restore datafiles from one server to another (same OS, same endianness) fails

RMAN-07517: Reason: The file header is corrupted

CAUSE

The source Production database, has a 32KB tablespace and an initialisation parameter defined for db_32k_cache_size,

But the target pfile didn't have the parameter db_32k_cache_size defined.

SOLUTION

Set in the pfile/spfile of the target db_32k_cache_size.

DBRECOVER Recovery Options

For Oracle incidents, start with the DBRECOVER for Oracle trial to verify table visibility, row previews, and export readiness on copied datafiles. For MySQL and InnoDB incidents, DBRECOVER for MySQL is free software and can inspect.ibd files, ibdata1, and database directories locally.

When the case is urgent, preserve the original files first, work from copies, and contact paid emergency support with the database version, platform, error messages, file list, and recovery objective.

Archive ParnassusData Blog Migration Archive