EM 13c installation fails with "Check the db edition - DB should be enterprise edition"

Those days, when trying to install EM 13c on my ExaCC database, the installation was failing with a "Check the db edition - DB should be enterprise edition" error..

Searching on My Oracle Support for this error, the closest I could find was "Bug 29492182 : Installing OMS fails: Check the db edition DB should be enterprise edition". However there was no patch associated with that bug.

Apparently, there was a check for "Enterprise Edition" string running on my database that could not match with the "Enterprise Edition Extreme Performance" version I had.

So, first I tried to search for any pre-patch file.. note I had to run the installation with the "SHOW_PROXY=true" as the machine had no access to the internet:

[oracle@ocosoemprdap01 install]$ ./em13400_linux64.bin -J-Djava.io.tmpdir=/u01/app/tmp/ SHOW_PROXY=true

Looking on the temporary installation folder, I noted that the following patch was downloaded:

Patch 31205199: Support EE Extreme Performance and EE Extreme High Performance DB editions as an OMR for EM Install

And checking on patch README.txt:

Oracle Management Service 13c Release 4 (13.4.0.0.0)
Patch for Bug# 31205199

Released: April 21, 2020

Bugs Fixed
----------
31205199 - Support EE Extreme Performance and EE Extreme High Performance DB editions as an OMR for EM Install.

This patch should not be applied manually. It is intended to be applied as auto download patch during Install or Upgrade.

So there is also this Bug 31205199 which seems to be the same issue. This should only be applied with the auto-download feature. However you can also apply it manually and that's what I did, as I was having some issues with the auto-download.

So first I installed the EM 13c with the "Software Only" option.

Then I applied the patch on the installed Middleware Home:

[oracle@ocosoemprdap01 install]$ unzip p31205199_134000_Generic.zip
Archive:  p31205199_134000_Generic.zip
   creating: 31205199/
   creating: 31205199/files/
   creating: 31205199/files/oracle.sysman.em.installer/
   creating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/
   creating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/oracle.sysman.em.installer.symbol/
   creating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/oracle.sysman.em.installer.symbol/oui/
   creating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/oracle.sysman.em.installer.symbol/oui/em/
  inflating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/oracle.sysman.em.installer.symbol/oui/em/emInstaller.jar
   creating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/oracle.sysman.em.installer.symbol/install/
   creating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/oracle.sysman.em.installer.symbol/install/requisites/
   creating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/oracle.sysman.em.installer.symbol/install/requisites/properties/
  inflating: 31205199/files/oracle.sysman.em.installer/13.4.0.0.0/oracle.sysman.em.installer.symbol/install/requisites/properties/stopPrereqOnDemand.properties
  inflating: 31205199/README.txt
   creating: 31205199/etc/
   creating: 31205199/etc/config/
  inflating: 31205199/etc/config/inventory.xml
  inflating: 31205199/etc/config/actions.xml
  inflating: PatchSearch.xml
[oracle@ocosoemprdap01 install]$ cd 31205199/
[oracle@ocosoemprdap01 31205199]$ opatch apply
Oracle Interim Patch Installer version 13.9.4.2.2
Copyright (c) 2020, Oracle Corporation.  All rights reserved.


Oracle Home       : /u01/app/oracle/em13c/middleware
Central Inventory : /u01/app/oraInventory
   from           : /u01/app/oracle/em13c/middleware/oraInst.loc
OPatch version    : 13.9.4.2.2
OUI version       : 13.9.4.0.0
Log file location : /u01/app/oracle/em13c/middleware/cfgtoollogs/opatch/opatch2020-06-04_19-43-21PM_1.log


OPatch detects the Middleware Home as "/u01/app/oracle/em13c/middleware"

Verifying environment and performing prerequisite checks...
OPatch continues with these patches:   31205199

Do you want to proceed? [y|n]
y
User Responded with: Y
All checks passed.
Backing up files...
Applying interim patch '31205199' to OH '/u01/app/oracle/em13c/middleware'

Patching component oracle.sysman.em.installer, 13.4.0.0.0...
Patch 31205199 successfully applied.
Log file location: /u01/app/oracle/em13c/middleware/cfgtoollogs/opatch/opatch2020-06-04_19-43-21PM_1.log

OPatch succeeded.
[oracle@ocosoemprdap01 31205199]$

Finally, after Middleware was installed and patched, I called the Configuration UI:

[oracle@ocosoemprdap01 install]$ pwd
/u01/app/oracle/em13c/middleware/sysman/install
[oracle@ocosoemprdap01 install]$ ./ConfigureGC.sh

And now no more errors =]

UPDATE 2020-06-06:

Jon Adams commented in this post about this MOS Doc ID:

With a terrible title but that indeed gives a much easier solution:

If the DB product is Enterprise Edition, still query is reporting 0 rows it might be because 'Product' value reports 'EE' instead of 'Enterprise Edition'

As a workaround follow below, Once installation is finished, back up and revert back the changes.

a.) When the error is encountered, look for "stopPrereqOnDemand.properties" file under <tmp_folder>/OraInstallAAAA-MM-DD_TIMESTMAP/install/requisites/properties/

b.) Edit and change id_check_db_is_enterprise_edition and id_check_optimizer_adaptive_features_param to TRUE

c.) Click OK in the error pop-up and then do a Retry from the OUI.

Thanks Jon!

Have you enjoyed? Please leave a comment or give a 👍!

2 comments

    • Jon Adams on June 4, 2020 at 20:13
    • Reply

    Rodrigo, check MOS 2365190.1 for the work around for this error. It will recommend altering the file OMS uses allowing you to skip certain prerequisite checks. I used the work around successfully when I encountered the same error installing a single node OMS and repository database configuration on an OCI compute node. Reach out to me for more details.

    1. Thanks Jon! This Doc ID would indeed solve my issue in a easier way.. but with this name ("OEM Installation - Bug Fix Required") it was impossible to find it using MOS search box.. there is no reference even to the error on the title! (I will update this blog post with this info.)

Leave a Reply

Your email address will not be published.