RMAN Resync Fails With ORA-00904 after applying 22.214.171.124.161018 Bundle Patch (24340679)
(Doc ID 2201135.1)
Last updated on DECEMBER 31, 2020
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
RMAN backups of 126.96.36.199 target database start failing after applying 188.8.131.52.161018 Bundle Patch (24340679) to Oracle Home of RMAN executable used to trigger backups. Typically, all operations fail when connected to catalog during resync phase:
In this particular setup, RMAN backups are triggered from RMAN executable of a common Oracle home (i.e. RMAN executable of target database Oracle Home is not used to trigger the backup). The error is seen when 184.108.40.206.161018 Bundle Patch is applied to the common Oracle Home (whose RMAN executable is used to trigger backup) but not the target database Oracle Home.
We verified that patch is properly applied (and relevant datapatch is executed against patched databases as pert of post install steps). Also we ran UPGRADE CATALOG from the patched RMAN executable to update the recovery catalog schema, still the error is not fixed.
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