So today I tried to apply Windows Bundle Patch 30445947 and the OJVM patch 30445947 on top of a 19.5 Data Guard environment in Windows x64
I went about things the way i normally would.. i shutdown standby and rolled back patch 30128191 (OJVM 19.5 patch) as it conflicts with the new patches. Then I applied the DB and OJVM patches (3048491 and 30445947).
At this point i restarted the standby and once DGMGRL reported everything was successful, I performed a switchover to the Standby. Once DGMGRL was happy again, I repeated the process on the Primary (now a standby).
Once this was completed, I swtiched the database back so the original primary was primary again.
After that, I shutdown and restarted the primary in upgrade mode and ran datapatch -verbose. All patches were rolled back and applied successfully as I would expect. After all patches were applied to the CDB adn PDB successfully, I restarted the primary DB in 'normal' mode.
Then I check in DGMGRL and noticed the configuration was successful for a few minutes and the redo apply to the standby stopped. I could not get it to restart. After checking all relevant files/logs, I noticed in the alert log of the standby these messages:
PL/SQL package SYS.DBMS_BACKUP_RESTORE version is not current
PL/SQL package SYS.DBMS_RCVMAN version 19.05.00.00 is too old
2020-02-06T19:12:26.160127-05:00
PL/SQL package SYS.DBMS_BACKUP_RESTORE version is not current
PL/SQL package SYS.DBMS_RCVMAN version 19.05.00.00 is too old
2020-02-06T19:24:25.361206-05:00
Could this be why my redo apply stopped? If it is how can i correct this issue?
thanks for any help.
steve