ORA-19837: INVALID BLOCKSIZE 0 IN BACKUP PIECE HEADER USING RMAN TTS BACKUPS DOING RECOVER
(Doc ID 1486655.1)
Last updated on FEBRUARY 14, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud 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
Information in this document applies to any platform.
Symptoms
You have taken RMAN backups using "BACKUP FROM SCN" syntax. The backup is using channels configured for automatic channel allocation.
The command "BACKUP INCREMENTAL FROM SCN 123456789 DATABASE".
You convert the backup from platform A to platform B to use to roll forward the database.
During convert you see some warning but the message completed successful is given.
The backup is copied to the new platform and during apply give an ORA-19994 error.
-- The recovery fails with:
Entering RollForward
<path>/ap_data.1752.78906945329
Done: applyDataFileTo
Done: RestoreSetPiece
DECLARE
*
ERROR at line 1:
ORA-19624: operation failed, retry possible
ORA-19870: error while restoring backup piece <path>/g2ne6gh5_1_1
ORA-19608:<path>/g2ne6gh5_1_1 is not a backup piece
ORA-19837: invalid blocksize 0 in backup piece header
ORA-6512: at "SYS.DBMS_BACKUP_RESTORE", line 2365
ORA-6512: at line 76
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! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |