ORA-1578 Corrupt Block Found in Encrypted Database
(Doc ID 1329437.1)
Last updated on JULY 07, 2021
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 11.1 to 11.2]
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 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.
ORA-1578 Encrypted database cloned with RMAN and opened with incorrect wallet or other database wallet shows corruption.
DBV and RMAN do not show any corruption.
The dump of the corrupted blocks shows the blocks are soft-corrupted in memory: seq:0xff.
To make sure the blocks are good on disk run dbv for the associated datafile or block (dbv with START/END clauses).
DBVERIFY does not check for Logical Corruptions in encrypted blocks
(intrablock corruption where checksum is ok and block content is invalid)
DBVERIFY does check for physical corruption in encrypted blocks though (checksum,zero,fractured block, etc).
When an encrypted database is created using TDE, two files are created and used with the encryption process: cwallet.sso and ewallet.p12.
The location of these files is in the sqlnet.ora provided by ENCRYPTION_WALLET_LOCATION.
If by mistake an encrypted database is opened using incorrect wallet or other database wallet, ORA-1578 can be reported because of soft corupted blocks in memory.
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