EM13c: SQL Monitoring Raises ORA-06553

After I have installed the EM13c R2, I noticed that I couldn’t access the SQL Monitoring page. I tested the SQL monitoring page for 11g to 12c database targets, and it gave the same error: ORA-06553: PLS-306: wrong number or types of arguments in call to ‘REPORT_SQL_MONITOR_LIST’. As you can guess I hit a bug, good thing is someone else already raised a service request and Oracle released Patch 24914115 to fix the bug. When I examined the patch, I saw that it’s also released for DB Plugin (OMS) Bundle. So if you applied this 161031 bundle for EM13 R1, you probably have the same bug, and you need to apply the patch.

I was planning to say a few words about the poor testing of EM13c releases, but I’m sure everyone already knows it, so I’ll just tell how I applied the Patch 24914115.

First of all, we need to update OPatch (in the Middleware Home) and OMSPatcher. To update OPatch, go to the Patch 6880880, and pick 13.9 release. It’s the OPatch for Enterprise Manager. I don’t think that Oracle Database will have 13.9 release so it seems 13.9 is reserved for Enterprise Manager 13c.

OPatch 13.9 is a different than previous OPatch releases. It comes with an installer. Download “p6880880_139000_Generic.zip”, unzip it to a temporary directory. You’ll see a file named “opatch_generic.jar”. Using JDK of Oracle Middleware Home, run the jar file:

According to the readme file, the jar file requires two parameters. First one is “-slient” (I didn’t tested what happens if I don’t give -slient parameter), and second one is oracle_home. The oracle_home parameter should point to the Oracle Middleware Home.


To update OMSPatcher, go to the Patch 19999993, and pick the correct Enterprise Manager release. Download the patch file, rename the old OMSPatcher folder and unzip the new OMSPatcher:

After you update them, check the releases of the OMSPatcher and OPatch:

So we upgraded both the OMSPatcher and the OPatch. Now we can download the patch and apply it to our system.


Go to the Patch 24914115, download the patch for EM13c R2, unzip the file for a temporary folder, switch that folder, set ORACLE_HOME variable to your Oracle Middleware Home, and run the omspatcher. I’ll run it with analyze parameter to be sure that the patch has no conflicts and all prerequisites are already met:

Enter the weblogic admin server, username and password. OMSPatcher will detect the admin server and username, so you probably just accept them with pressing enter. All you need is to enter the admin server password.

If you see a message similar to above, you’re ready to apply the patch. Issue “omspatcher apply” command (without -analzye parameter) to apply the patch. After applying the patch, you need to restart OMS to make changes take effect. That’s all, so we can access the SQL Monitoring page!

Please share

AWS Big Data Specialist. Oracle Certified Professional (OCP) for EBS R12, Oracle 10g and 11g. Co-author of "Expert Oracle Enterprise Manager 12c" book published by Apress. Awarded as Oracle ACE (in 2011) and Oracle ACE Director (in 2016) for the continuous contributions to the Oracle users community. Founding member, and vice president of Turkish Oracle User Group (TROUG). Presented at various international conferences including Oracle Open World.


  1. J

    It took Oracle Support about 1.5 months to release the fix, which is frustrating. We’re on 13.2, and were going to roll back to 13.1, but turned out Oracle broke that functionality on older versions as well (even 12c). I can’t even imagine how they test it.

  2. Paul Hubbert

    When I try and do this patch, both the omspatcher apply -analyze and omspatcher apply give the error: “OMSPatcher cannot establish JMX connection to weblogic server”. I have checked the 3 inputs that  are requested (URL, weblogic name, and password) and they are all correct. The oms is supposed to be down at this time and it is, but we still get this error. Have you seen this before? The patch we are trying is the same one you discuss in this article.

    • Gokhan Atil

      Hello Paul,

      It might be a certification problem. Are you using demo certification or a custom certificate?

    • J.P. Boileau

      It appears that the OMS but be UP before doing the patching analyze or apply. I ran into the same situation. Starting the OMS fixed it.

      Thanks for positing this, Gokhan!

  3. Yusuf Eyidogan

    Detaylı anlatımınız ve paylaşımınız için teşekkürler.

Leave Comment

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.