Patching Recover Catalog to Quarter 3 DB RU (39618711/39467003/39472050) & OJVM (39618711/39222882)
After applying these patch sets on our recovery catalog, single instance database host (19c, linux x86-64) using 'opatch apply -analyze', our sql version did not seem to change to 19.32. Additionally the RMAN command failed with the below error. This patch was applied to our passive oracle home. The active home that we rolled back to continues to run in 19.31 with no issues. Has anyone ran into a similar issue this week? I received no errors from datapatch or the opatch apply process. everything looked good until the final catalog upgrade.
Recovery Manager: Release 19.0.0.0.0 - Production on Thu Jul 23 14:25:12 2026
Version 19.30.0.0.0