UA.bat fails to Connect to FDMEE

The upgrade of EPM versions to 11.2.8 is a little dated now, but there are still some customers who are on earlier versions of EPM 11.2.x.  Depending on which of those versions you are running, you may face this interesting issue when applying a maintenance release to get to 11.2.8, so you can proceed to a later patch.

If you are on a version before 11.2.5, when moving to 11.2.8 you need to run the file \Oracle\Middleware\oracle_common\upgrade\bin\ua.bat (or .sh for Linux). 

 The first part of this process requires you to connect as a SYSDBA user to the Oracle database, and then select to FDMEE schema.  This process is required to upgrade the system from ODI 12.2.1.3.0 to ODI 12.2.1.4.0.   The very first part of this connection checks the SYSTEM.schema_version_registry table.  If that table is lacking an ODI entry, then you will get an error that there is no ODI instance valid for updating.

The way to resolve this is to edit the table for schema_version_registry.  In this case you add a new row, and set the values as follows:

·      COMP_ID:  ODI

·      COMP_NAME:  Master and Work Repository

·      MRC_NAME: EPM

·      MR_NAME: ODI_REPO

·      MR_TYPE: ODI_REPO

·      OWNER: FDMEE (or whatever your FDMEE schema is named)

·      VERSION:  12.2.1.3.0

·      STATUS: Valid

·      UPGRADED: N

·      TIME:  Copy the time field from any other entry in this table…it’s the easiest way.

Once the above is completed, you can now connect with the UA.bat utility and proceed with the ODI upgrade.  When it’s complete you can recheck the above table and see the following changes:

 ·      VERSION:  12.2.1.4.0

·      UPGRADED: Y

And that’s all there is to it.  It’s a pretty easy change, but can be frustrating when you’re connecting as a SYSDBA level user, but still seeing errors that something can’t be upgraded.

If you’re looking for Cloud or EPM assistance, the team here at iArch Solutions is here to help.  Reach out to us, we’d love to hear from you.