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
oracle.sysman.emSDK.app.exception.EMSystemException
at oracle.sysman.emas.sdk.model.metric.ReposMetricProvider12.queryMultiMetricsByAssocOneQuery(ReposMetricProvider12.java:529)
at oracle.sysman.emas.model.as.ServerHomeDeploymentsModel.setupMetricBatchProvider(ServerHomeDeploymentsModel.java:198)at oracle.sysman.emas.model.as.ServerHomeDeploymentsModel.setDeployments(ServerHomeDeploymentsModel.java:517)
Caused by:
java.sql.SQLDataException: ORA-01882: timezone region not foundORA-06512: at "SYSMAN.MGMT_GLOBAL", line 8
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)
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