RDBMS -- EBS - Exadata Cloud at Customer (ECC) migration -- ignorable errors during 11.2.0.4 upgrade

This blog post will be in 2 parts.

In the first part , I will give some useful info about "EBS - ECC migrations" and then, I will share some ignorable errors that we have seen during our EBS database upgrade.

Let's start with the first part;

As a prereq for an Exadata Cloud at Customer (ECC) migration project, we were upgrading the database tier of an EBS R12 instance.

The upgrade was done for making the database of this EBS instance aligned with the ECC's minimum database software version requirements. ( currently, ECC requires 11.2.0.4 as the minimum RDBMS version)

So our plan was to upgrade this EBS's database and then migrate it to ECC using dataguard..

With this migration, we also planned to convert this EBS's database from single instance to RAC.
Note that, the source database version was 11.2.0.3.

Anyways, although it sounds complicated , there are 3 documents to follow for this approach.

The MOS document for the database upgrade -> Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 (Doc ID 1058763.1)

The MOS document for dataguard switchover -- migration -> Business Continuity for Oracle E-Business Release 12.1 Using Oracle 11g Release 2 Physical Standby Database (Doc ID 1070033.1)

The MOS document for converting Using RAC 11gR2 with EBS R12 ->  Using Oracle Real Application Clusters 11g Release 2 with Oracle E-Business Suite Release 12 (Doc ID 823587.1)

Now, let's check what we have seen during 11.2.0.3 to 11.2.0.4 upgrade (using dbua)

Well.. Although we have did everything documented in "Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 (Doc ID 1058763.1)", during the upgdade we have seen unexpected errors like the following;

When we check the upgrade log (we must check the log to see the details of the failing command), we ended up with the following;

drop procedure sys.drop_aw_elist_all

*

ERROR at line 1:

ORA-04043: object DROP_AW_ELIST_ALL does not exist

create or replace type SYSTEM.LOGMNR$TAB_GG_REC wrapped

*

ERROR at line 1:

ORA-02303: cannot drop or replace a type with type or table dependents 

create or replace type SYSTEM.LOGMNR$COL_GG_REC wrapped

*

ERROR at line 1:

ORA-02303: cannot drop or replace a type with type or table

create or replace type SYSTEM.LOGMNR$SEQ_GG_REC wrapped

*

ERROR at line 1:

ORA-02303: cannot drop or replace a type with type or table

  

create or replace type SYSTEM.LOGMNR$KEY_GG_REC wrapped

*

ERROR at line 1:

ORA-02303: cannot drop or replace a type with type or table

CREATE TYPE SYSTEM.LOGMNR$TAB_GG_RECS AS TABLE OF  SYSTEM.LOGMNR$TAB_GG_REC;

*

ERROR at line 1:

ORA-00955: name is already used by an existing object

Good news -> After some researches, we have concluded that all of these errors were ignorable.

The ORA-04043 which was encountered for dropping DROP_AW_ELIST_ALL was ignorable. My comment on this was -> this object seems not secure (maybe there was a SQL/DML injection bug there) and maybe that's why upgrade was trying to drop it. (ref: http://www.davidlitchfield.com/OLAPDMLInjection.pdf)

But, as far as I can see, this procedure normally comes with patch 9968263.. So if this patch was not applied, then it is normal to not to have this procedure inside the database and then "object doesn't exist error" is normal as well. So it was just ignorable :)

The ORA-02303 and ORA-00955 errors were encountered for Logminer-specific objects. These errors were completely addressed/documented in Oracle Support, so they were directly ignorable.This was a bug actually. These objects were actually affecting the Goldengate, since we didn't have Goldengate in this customer, we just ignored them..  However, if you have Goldengate, then check the following document:

ORA-02303 & ORA-00955 Errors on SYSTEM.LOGMNR$ Types During PSU Updates (Doc ID 2008146.1)

That's it :) Just wanted to share.