I had a similar issue a few months back when a colleague was patching in
rolling maner a 3 node RAC and the configuration was in mixed mode (first
node with latest patch level and the other 2 with oldest patch level).
After patching was completed the error no longer appeared. So have you
completed the upgrade or you are still in an intermediate state?
Maybe uncatalog/catalog the DB might help.
În mar., 8 iun. 2021 la 01:02, David Barbour <david.barbour1@xxxxxxxxx> a
Anybody seen this with RMAN before? Just upgraded to 19c and the script
used to purge backups from Oracle Cloud is failing on catalog resync.
Pretty simple commands:
ALLOCATE CHANNEL for maintenance DEVICE TYPE 'SBT_TAPE' parms
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 14 DAYS;
delete noprompt obsolete recovery window of 14 days device type 'SBT_TAPE';
delete noprompt expired backup;
starting full resync of recovery catalog
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-03002: failure of delete command at 06/07/2021 16:57:47
RMAN-03014: implicit resync of recovery catalog failed
RMAN-03009: failure of full resync command on default channel at
ORA-12850: Could not allocate slaves on all specified instances: needed,