Skip to main content
NetApp Knowledge Base

During archive log pruning with SMO, RMAN complains that the Oracle Version is mismatched

Views:
148
Visibility:
Public
Votes:
0
Category:
snapmanager-for-oracle
Specialty:
snapx
Last Updated:

Applies to

  • SnapManager for Oracle (SMO) for Windows 3.4.x
  • SnapManager for SAP (SMSAP) for Windows 3.4.x
  • Oracle 12.1.0.2, 12.2.0.1

Issue

After upgrading a database from (e.g.) Oracle 12.1 to Oracle 12.2, during the Archive Log Pruning SnapManager job, the following error sometimes (*) occurs:

[Execution Monitor Thread [[LIST ARCHIVELOG UNTIL TIME "TO_DATE(' 2020-01-01:08:00:00 ','yyyy-MM-dd:HH24:MI:SS ' )" LIKE 'M:\_<ORASID>_ARCHLOGS\FLASH_RECOVERY_AREA\<ORASID>%';]]] [DEBUG]:
EXE-00001: Shell result [0:00:00.641] (Exit Value: 1):

Recovery Manager: Release 12.1.0.2.0 - Production on Tue Sep 15 11:05:34 2020
Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-06429: TARGET database is not compatible with this version of RMAN
RMAN-06618: RMAN client and database release mismatch; indicated database release is 12.2.0.1

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device