RMAN function failing in Backup process of SCO due to weak Oracle client security
Applies to
- SnapCenter Plug-in for Oracle (SCO) up to 4.7P1
- Oracle version 11.2, 12.1, 12.2, 18c, 19c and 21c with July 2021 Patches
Issue
During the retention run on Archive log backups, the following errors appear during the RMAN deletion request:
ORACLE-00101: Error executing RMAN command: [DELETE NOPROMPT ARCHIVELOG UNTIL TIME 'SYSDATE-4.0' LIKE 'ARCHIVE_LOG_PATH/%';]. The command returned:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12269: client uses weak encryption/crypto-checksumming version
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at DATE TIME
RMAN-06171: not connected to target database
or (note different placement of the weak crypto message):
ORACLE-00101: Error executing RMAN command: [DELETE NOPROMPT ARCHIVELOG UNTIL TIME 'SYSDATE-4.0' LIKE 'ARCHIVE_LOG_PATH/%';]. The command returned:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at DATE TIME
RMAN-12001: could not open channel ORA_DISK_1
RMAN-10008: could not create channel context
RMAN-10003: unable to connect to the target database
ORA-12269: client uses weak encryption/crypto-checksumming version