Siebel Target Discovery Stuck/Hang/Fails With OEM Agent 13.5.1 RU16 with JDK 1.8.0_361 Or Later and Siebel 23.x
(Doc ID 2984723.1)
Last updated on NOVEMBER 03, 2023
Applies to:
Enterprise Manager for Siebel - Version 13.5.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
Siebel Target discovery fails with OEM agent 13.5.1 RU16 with JDK 1.8.0_361 on Siebel 23.x
Error in gcagent.log
oracle.sysman.emSDK.agent.fetchlet.exception.FetchletException: Throwable: java.lang.NoClassDefFoundError: Could not initialize class oracle.sysman.siebel.management.serveraccess.SrvrMgrInvoke
Error Message
Error in communicating with Agent: server.abc.com.
Exception thrown : Error in communicating with Agent: Server.abc.com
The issue can be reproduced at will with the following steps:
1. Applied RU16 on OEM server and agent
2. Updated OEM agent JDK to 1.8.0_361 and above
3. Target discovery fails even after following the steps in below documents:
EM 13.5: How to Use the Latest Certified JDK 8 Update with OMS 13.5 (Doc ID 2776765.1)
EM 13.5: How to Use the Latest Certified JDK 8 Update with 13.5 Agents (Doc ID 2777094.1)
4. Target discovery is successful when using OEM agent with JDK 1.8.0_261
Changes
Updated RU15 and applied JDK 1.8.0_361 on OEM agent
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |