ORA-19870, ORA-19599 while RESTORING COMPRESSED BACKUP OF DUMPFILE
(Doc ID 2620719.1)
Last updated on JUNE 17, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 12.2.0.1 and later Information in this document applies to any platform.
Symptoms
NOTE: In the images and/or the document content below, the user information and environment data used represents
fictitious data from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other
training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Database Name: DB122C
Instance Name: DB122CP
Tablespace Name: TESTTBS
Path and all it's sub-directories: /export/home/oracle/orabase
During cross platform transportable tablespace from AIX to Linux using the steps described in this Doc ID -
12c How Perform Cross-Platform Database Transport to different Endian Platform with RMAN Backup Sets (Doc ID 2013271.1)
returns the following error at step #6
RMAN-571: ===========================================================
RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-571: ===========================================================
RMAN-3002: failure of restore command at 08/06/2019 14:26:35
ORA-19870: error while restoring backup piece
/oradba/app/oracle/acfsmounts/global/global/backup/XXXX/TS_BAAN_675_metadata.dmp
ORA-19599: block number 257 is corrupt in backup piece
/oradba/app/oracle/acfsmounts/global/global/backup/XXXX/TS_BAAN_675_metadata.dmp
The error happens only when using the compression option during backup which may be necessary for very large databases.
ALERT LOG:
=========
<SID>:Compressed piece hard block mismatch, expected 1, got 4 (257) for file 0
<SID>:Corrupt block 257 found during reading backup piece,
file=/oradba/app/oracle/acfsmounts/global/global/backup/XXXX/TS_BAAN_675_metadata.dmp, corr_type=4
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!