Skip to Main Content

Enterprise Manager

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

WARN - Can't connect to OMS

ClaudiamarJan 14 2019 — edited Jan 14 2019

I installed the agent 13.2 from a gold image onto 5 database servers. I am having problems with just one. The agent runs but it does not upload data to the oms. The errors are as follows:

1. . From emctl status agent

Started at         : 2019-01-03 09:23:42
Started by user    : oracle
Operating System   : Linux version 3.10.0-327.el7.x86_64 (amd64)
Number of Targets  : (none)
Last Reload        : 2019-01-14 12:43:04
Last successful upload                   : (none)
Last attempted upload                    : (none)

Total Megabytes of XML files uploaded so far : 0

Number of XML files pending upload       : 4
Size of XML files pending upload(MB)     : 0
Available disk space on upload filesystem: 93.48%
Collection Status                        : Collections enabled
Heartbeat Status                         : OMS is unreachable
Last attempted heartbeat to OMS          : 2019-01-14 12:44:47
Last successful heartbeat to OMS         : (none)
Next scheduled heartbeat to OMS          : 2019-01-14 12:45:17

2. [oracle@betatest bin]$ ./emctl pingOMS

Oracle Enterprise Manager Cloud Control 13c Release 2 

Copyright (c) 1996, 2016 Oracle Corporation.  All rights reserved.

---------------------------------------------------------------

EMD pingOMS error: An internal error has occurred at the agent: "java.lang.NullPointerException". Check the agent's error logs for details.

3. more ../../agent_instance/sysman/log/gcagent.log

2019-01-14 12:01:55,366 [12841:933821C7] INFO - Critical error is report by

java.lang.Exception: Critical error

    at oracle.sysman.gcagent.tmmain.diag.DiagManager.handleException(DiagManager.java:1019)

    at oracle.sysman.gcagent.tmmain.diag.DiagManager.handleException(DiagManager.java:935)

    at oracle.sysman.gcagent.tmmain.diag.DiagManager.handleException(DiagManager.java:707)

    at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:138)

    at oracle.sysman.gcagent.dispatch.DispatchRequestsAction.call(DispatchRequestsAction.java:51)

    at oracle.sysman.gcagent.task.DiagWrappedAction.call(DiagWrappedAction.java:52)

and the list of errors goes on.

Any suggestions as to what I can do to resolve this problem?

Thanks,

Claudia

Comments
Post Details
Added on Jan 14 2019
1 comment
505 views