My Oracle Support Banner

Discrepancy In MDM DBA Admin Guide And Post Upgrade Scenario - MDM 2.2 SP2, FMW 4.3.0.5 (Doc ID 2438295.1)

Last updated on MARCH 13, 2019

Applies to:

Oracle Utilities Meter Data Management - Version 2.2.0.2.0 and later
Information in this document applies to any platform.

Goal


Discrepancy in Oracle Utilities Meter Data Management (MDM) Database Administrator (DBA) Guide and post upgrade scenario - MDM 2.2 SP2, Oracle Utilities Application Framework (FW) 4.3.0.5

We have currently upgrade our MDM Application from 2.2 SP1 to 2.2 SP2 and FW from 4.3.0.3 to 4.3.0.4

As per the Admin Guide, Oracle Utilities Meter Data Management Database Administrator Guide Release 2.2.0 Service Pack 2 E91714-01, we see an update in Appendix G (Upgrades to the Oracle Utilities Application Framework Database), Upgrading from Oracle Utilities Application Framework v4.3.0.4.0 to v4.3.0.5.0, "Index Changes Index S1C675S1 for table F1_EXT_LOOKUP_VAL_CHAR has been renamed to F1C675S1"

You have compared the database and you see after the upgrade, the index still reads as S1C675S1 .

Could you please let us know what is the issue and the reason for the above discrepancy?
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.