Saturday, June 14, 2014

EM12c: How to upgrade JVMD Engine and JVMD agents in EM12cR4?

To upgrade JVMD Engine and JVMD agents. Pls. follow steps as given:

1.    Goto Setup->Middleware Management-> Application Performance Management

 2.    Select on triangle next to JVM Diagnostics Engines

3.    This page will show already installed JVM Diagnostics Engines.  Provide credentials for the host where JVMD Engine is running and also provide credential for the Weblogic Domain (EMGC Domain), of which JVMD manager is part of. Then click on Apply button in lower panel.

4.    One all credential have been applied. Click on Upgrade button on top panel.


 5.    It will ask for confirmation if you want to upgrade JVMD engine to newer version. Click OK.

6.    That will submit an EM Job to upgrade the JVMD Engine as shown below:


7.    JVMD Engine is up and running


8.    Similar way, we can upgrade JVMD agents using given steps. Select triangle icon against JVMD Agents Count:


9.    This will show agent Upgrade Wizard. Select Upgrade option. Select agents to be upgraded.


10.    Provide credentials for the Target weblogic domain where JVMD agents are deployed. And click on Apply button in lower panel.

11.    Then select Next button on top panel.


12.     Do a final review of all input and click on Upgrade button.


13.    It will submit following EM job

14.    Once the job is successful. You will see like given screenshot.


15.     Now you can go to JVMD UI and verify that JVMD Agents have started reporting to JVMD Engine and JVMD data is there.

Tuesday, June 03, 2014

EM12c Release 4 ( or 12c PS3 Release with plugin and connector version info

Oracle Enterprise Manager 12c Release 4 has been announced today. It has lot of new capabilities for:
  • Cloud Mgmt
  • FMW mgmt
  • DB Mgmt etc.

EM12cR4 has following plugin versions:
  • Plugins added newly in PS3

  • Plugins that were shipped with PS2 or later

EM12cR4 has following connector versions:

For more details, pls refer here.

    Wednesday, May 14, 2014

    EM12c: Unable to delete Database System target successfully

    Problem: Tried removing Database System target from UI, but it fails with following error in emoms.trc :

     2014-04-23 17:06:28,234 [EMUI_17_06_28_/console/rac/conf/racTargetDelete] ERROR svlt.PageHandler

    handleRequest.674 - java.lang.IndexOutOfBoundsException: Index: 1, Size: 0
    java.lang.IndexOutOfBoundsException: Index: 1, Size: 0
        at java.util.ArrayList.get(

    Action: If the error continues while removing the Database system target, drop it via command line as given below:

    $ cd $OMS_HOME/bin

    $ ./emcli login -username=SYSMAN -password=<sysman_passwd>

    $ ./emcli sync

    $ ./emcli delete_target -name="<dbsys_name>" -type="oracle_dbsys"
    replace <dbsys_name> with the database system target name, as shown in the All targets list.

    It should remove database system target properly.

    Thursday, March 20, 2014


    In EM, when trying to upload a J2ee Application Component to software library, it shows status as incomplete and can be seen on UI.

    emoms.log shows following associated exception:
    Caused by: java.sql.SQLException: ORA-20406: The following targets are invalid:
    ORA-06512: at "SYSMAN.EM_JOB_OPS", line 290
    ORA-06512: at "SYSMAN.GC_JOB", line 29
    ORA-06512: at line 1
    at oracle.jdbc.driver.T4CTTIoer.processError(  
    at oracle.jdbc.driver.T4CTTIoer.processError(
    at oracle.jdbc.driver.T4C8Oall.processError(


    Cause: It turns out that if the OMS virtual host name is different from physical host name, that caused this issue.

    Solution: This is a product bug, there is no fix AS OF NOW. But there is a workaround, not the best solution but to proceed further, it helps.

    To workaround the issue, one can push another agent on oms host with same physical name. This will resolve the virtual host vs physical host conflict.
    Now upload the J2ee Application Component to software library, it will be successful.

    Once the J2ee App has been uploaded. One may stop the agent and bring it up only when its needed again. Else it can add some overhead to existing resources.

    Tuesday, February 11, 2014

    EM12c: Weblogic host is up, but EM doesn't show metric data (ORA-01882)

    Issue: On EM12c, Weblogic Server is discovered successfully. On EM12c UI, one can see various middleware targets and their respective availbility status. But when one wants to see the details metrics like Servlets and JSPs metrics or Work Manager etc. It shows 'Unavailable' as shown in screenshot below:

    Also  when one looks at emoms.log with DEBUG level on, one see following error:

    2014-01-25 18:53:04,015 [53::[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'] DEBUG as.ServerHomeDeploymentsModel logp.251 - Error getting metrics for the application deployments table
    at oracle.sysman.emas.sdk.model.metric.ReposMetricProvider12.queryMultiMetricsByAssocOneQuery(

    Caused by:
    java.sql.SQLDataException: ORA-01882: timezone region not found
    ORA-06512: at "SYSMAN.MGMT_GLOBAL", line 8

    at oracle.jdbc.driver.T4CTTIoer.processError(
    at oracle.jdbc.driver.T4CTTIoer.processError(
    at oracle.jdbc.driver.T4C8Oall.processError(
    at oracle.jdbc.driver.T4CTTIfun.receive(
    at oracle.jdbc.driver.T4CTTIfun.doRPC(

    In this case, agent is working fine and collecting all data, passign to OMS. Where entire metric data is getting collected in EM repository. However, this is an OMS UI side issue, where due to difference in Timezone of agent and host, OMS is not showing the metric data.

    Solution: Set the TimeZone before starting OMS server.
    One can set timezone at OMS host at host/user level .At host level would be ideal.
    Use following example to start the timezone:

    %$OMS_HOME/bin/emctl stop oms

    %export TZ=PST8PDT

    %$OMS_HOME/bin/emctl start oms

    Friday, January 31, 2014

    EM12c: How to deploy JVMD agent on EBiz 12.1 (oc4j based instance) ?

    E-Business 12.1 has Oracle iAS based tech stack. It has oc4j as its application server.
    EM12c doesn't have any automated UI flow for deploying JVMD agent on oc4j server.
    That deployment has to be manual.

    Manual JVMD deployment is referred in this doc

    Download JVMD agent file from EM12c UI as given here

    1. In EM Cloud Control, Select Setup menu-> Middleware Management-> Application Performance Management.

    2. On the Application Performance Management page, select JVM Diagnostics Engine.

    3. Click Configure. The 'JVM Diagnostics Setup' page appears.

    4. On the 'JVM Diagnostics Setup' page, click JVMs and Pools, then click Download.

    5. From the JVMD Component menu, to download jamagent.war. From the JVMD Component menu, select JVMD Agent, then click OK. The JVM Diagnostics Agent web.xml parameters dialog box appears.

    6. From the Available Engines menu, select a JVMD engine from the list, then click Download.
    7. Click Download to download jamagent.war.

    Due to some changes in EBiz 12.1 iAS, it requires some additional steps for JVMD agent deployment. EBiz12.1 oc4j doesn't have its own admin web console, so one needs to deploy JVMD agent using command line utility like admin_client.jar.  That requires resetting oc4jadmin password for oafm and oacore  etc.

    Given steps can be used as workaround for JVMD agent deployment on oc4j. Not sure if one would like to use these steps in a Production env. Take your call.

    a. To reset oc4jadmin password for oafm and oacore
    edit the following files:

    look for the <credentials> section under OC4J Administrator
    replace the encrypted password e.g. {903}xxxxxxxxxx with a new plaintext e.g. !welcome1
    (new plaintext must begin with a !)

    Also modify the opmn config file, to disable SSL and allow remote connections
    change the <notification-server> section so it looks something like this
       <notification-server interface="ipv4">
          <ipaddr remote="" request=""/>
          <port local="17006" remote="17007" request="17005"/>
          <ssl enabled="false" wallet-file="$ORACLE_HOME/opmn/conf/ssl.wlt/default"/>
    (add the line with <ipaddr...> and change <ssl enabled="true"...> to false)

    b.  Use following command to deploy JVMD agent
    java  -jar /oracle/r12/VIS12/apps/tech_st/10.1.3/j2ee/home/admin_client.jar
     deployer:oc4j:opmn:// oc4jadmin welcome1
    -deploy -file /tmp/jamagent.war -deploymentName jamagent -bindAllWebApps

    java   -jar
     deployer:oc4j:opmn:// oc4jadmin welcome1 -deploy -file /tmp/jamagent.war -deploymentName jamagent -bindAllWebApps

    Friday, October 18, 2013

    EM12c: Service Management (Synthetic Monitoring) White Paper

    Oracle EM12c cloud control provides a comprehensive monitoring solution for IT organizations to achieve high availability, performance and optimized service levels for their business services. EM's service management solution allows you to actively monitor and report on the availability and performance of a wide variety of services, including end users business functions (mail infrastructure, network and database services), web applications, Oracle Apps etc.. Using synthetic transactions one can monitor services from end users perspective.

    To understand Service management, Service Definition, Service Test (using ATS), System, Service Level Agreement, Service Dashboard etc., pl refer the Service Management White Paper