I thought it would be useful to have a consolidated list of issues we have run into, some of which I have already blogged about, some of which I haven’t. I will try to keep this page up-to-date moving forwards. Note we are not really using 12cR2 extensively, we have just upgraded OEM Repository and AWR Warehouse instances so far.
Oracle have now published a document about this issue:
UPGRADE CATALOG command from 12.1 to 12.2 Fails With RMAN-6004 and ORA-1422 (Doc ID 2252894.1)
Bug 26115103 – REPORT OBSOLETE NOT SHOWING OLD DATAFILE COPY IN 12.2
Control File autobackups are never marked as obsolete
Bug 25943271: RMAN REPORT OBSOLETE DOES NOT REPORT CONTROLFILE BACKUP AS OBSOLETE
After upgrading catalog to 12.2, resync failing with “ORA-20110: set stamp set count conflict”
Bug 26385473 : REGISTER TARGET DATABASE WITH 12.2 CATALOG FAILS WITH RMAN-03008 ORA-20110
This seems to be a problem that is specific to 12.1 multi-tenant instance on 12.2 catalog. It appears that rman is attempting to catalog the same backupset once for each PDB
Trace on the target system reveals problem seems to be caused by SQL like the following, which seem to ‘forget’ to provide the join conditions between the two tables queried:
SELECT BS.RECID , BS.STAMP , BS.SET_STAMP , BS.SET_COUNT , BS.BACKUP_TYPE , BS.INCREMENTAL_LEVEL , BS.PIECES , START_TIME , COMPLETION_TIME , CONTROLFILE_INCLUDED , BS.INPUT_FILE_SCAN_ONLY , KEEP_UNTIL , DECODE(BS.KEEP_OPTIONS , ‘LOGS’ , :b1 , ‘NOLOGS’ , :b2 , ‘BACKUP_LOGS’ , :b3 , 0 ) KEEP_OPTIONS , BS.BLOCK_SIZE , BS.MULTI_SECTION , BS.GUID , DECODE(BS.CON_ID , :b4 , 1 , 0 ) DROPPED_PDB FROM V$BACKUP_SET BS , V$CONTAINERS PDB WHERE BS.RECID BETWEEN :b5 AND :b6 AND ( BS.STAMP >= :b7 OR BS.RECID = :b6 ) AND BS.STAMP >= :b8 AND BS.FOR_XTTS != ‘YES’ ORDER BY BS.RECID
AWR and AWR Warehouse
AWR Warehouse load process failing with ORA-600 after upgrading repository
The error message is [kewrspbr_2: wrong last partition]. Doc ID 2020227.1 describes the fix for a similar issue. I found partitioning was wrong on some on some new 12.2 AWR tables so I recreated them, added a partition for each database contributing to AWR Warehouse. I have been unable to reproduce this issue on a test system.
Only affects database upgraded from 184.108.40.206, workaround is to re-create the index.
BUG 25954054 – WRH$_SGASTAT_U BECOMING UNUSABLE STATE IN UPGRADED DB
A patch is now available for this issue.
Set SQLNET.ALLOWED_LOGON_VERSION_SERVER to 11
TNS-12599: TNS:cryptographic checksum mismatch in alert log of 12.2 database from connections from OEM
No functional impact. Bug number 25915038 created. Setting the following in sqlnet.ora of target database suppresses the message:
This is a bug on calculation of database version from db plugin. Simplest solution is to upgrade db plugin to 13.2.2 or later on database host.
ORA-20001: Statistics Advisor: Invalid task name for the current user
Seems to be on fresh created database. Solution per Doc ID 2127675.1 is to run dbms_stats.init_package.
Bug 26035911 : AUDIT RECORDS GENERATED EVEN WHEN THE SYSTEM PRIVILEGE IS NOT EXERCISED IN 12.2