Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..
103 views

CMDB10.x error after upgrade to 10.22 CUP1

UCMDB 10.22 CUP1

CP 19

After upgrading our environment to 10.22 cup1, we ran the ucmdb to ucmdb integration with the cmdb10.x adapter. We were able to start the integration and test connection successfully.But when we tried to run a job, it failed right away and in the probe log we saw the following error:

jvm 3    | <2016-06-13 21:35:21,045> 524680 [ERROR] [JobExecuterWorker-0:DS_Population DM to PM_Level 1 Netdevice Pop] (JobExecuter.java:985) - Discovery failure in job DS_Population DM to PM_Level 1 Netdevice Pop on destination: null (02d22d02bcf64cc8ca6f59546bf1d303)
jvm 3    | java.lang.IncompatibleClassChangeError: Class com.hp.ucmdb.api.client.topology.TopologyQueryServiceImpl does not implement the requested interface com.hp.ucmdb.api.topology.TopologyQueryService
jvm 3    | 	at com.hp.ucmdb.adapters.cmdb10xAdapter.Cmdb10xAdapter.getQueryByName(Cmdb10xAdapter.java:816)
jvm 3    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.retrieveQueryDefinitionByRootType(AdapterService.java:269)
jvm 3    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.runDiscovery(AdapterService.java:196)
jvm 3    | 	at com.hp.ucmdb.discovery.probe.services.dynamic.core.AdapterService.discover(AdapterService.java:149)
jvm 3    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter.launchTask(JobExecuter.java:1206)
jvm 3    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.launchAndIsProbeRestarting(JobExecuter.java:953)
jvm 3    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.executeTask(JobExecuter.java:869)
jvm 3    | 	at com.hp.ucmdb.discovery.probe.agents.probemgr.taskexecuter.JobExecuter$JobExecuterWorker.run(JobExecuter.java:729)
jvm 3    | <2016-06-13 21:35:21,070> 524705 [INFO ] [JobExecuterWorker-0:DS_Population DM to PM_Level 1 Netdevice Pop] (ProbeMgrProgressHandler.java:247) - Progress handler for job [DS_Population DM to PM_Level 1 Netdevice Pop] for trigger [02d22d02bcf64cc8ca6f59546bf1d303] - received total 1 Messages, 1 new (reported) and 0 errors cleared
jvm 3    | <2016-06-13 21:35:21,082> 524717 [INFO ] [JobExecuterWorker-0:DS_Population DM to PM_Level 1 Netdevice Pop] (TaskResultsDistributer.java:79) - Start to send task result
jvm 3    | <2016-06-13 21:35:21,082> 524717 [INFO ] [JobExecuterWorker-0:DS_Population DM to PM_Level 1 Netdevice Pop] (LocalTaskResultsDistributer.java:83) - Start store new Task result to the Probe manager database
jvm 3    | <2016-06-13 21:35:21,092> 524727 [INFO ] [JobExecuterWorker-0:DS_Population DM to PM_Level 1 Netdevice Pop] (LocalTaskResultsDistributer.java:85) - Finish store new Task result to the Probe manager database
jvm 3    | <2016-06-13 21:35:21,093> 524728 [INFO ] [JobExecuterWorker-0:DS_Population DM to PM_Level 1 Netdevice Pop] (TaskResultsDistributer.java:81) - Finish to send task result
jvm 3    | <2016-06-13 21:35:21,093> 524728 [INFO ] [JobExecuterWorker-0:DS_Population DM to PM_Level 1 Netdevice Pop] (ProbeMgrProgressHandler.java:158) - Execution state of trigger 02d22d02bcf64cc8ca6f59546bf1d303 for job DS_Population DM to PM_Level 1 Netdevice Pop was set to EXECUTION_END, message was sent to the Gateway

Any idea what can cause this?

 

Thank you,

0 Likes
4 Replies
Highlighted
Super Contributor.
Super Contributor.

Re: CMDB10.x error after upgrade to 10.22 CUP1

Hello

Have you tried to recreate the TQL and integration point?

BR
don-xu

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: CMDB10.x error after upgrade to 10.22 CUP1

Yes, I did. But still got the same error

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: CMDB10.x error after upgrade to 10.22 CUP1

Hello Ctruong,

That exception can be found in case you are using integration UCMDB to OMi with patch IP5.
The following five jars reside on the OMi Probe under probemanager/Discoveryresources/ and probegateway/Discoveryresources/ should be manually replaced with the same name jars from IP5 in order to fix that issue:
api-integration.jar
api-interfaces.jar
api-internal.jar
Cmdb10xAdapter.jar
cmdb-adapter.jar

Best Regards,
Nikola

------------------------
Nikola Todorov
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: CMDB10.x error after upgrade to 10.22 CUP1

Hello,

The integration is to another UCMDB on the same version 10.22 CUP1 with CP19.

I tested integration with another UCMDB on version 10.21 and it work fine.

Any thought or advice is appreciated.

Thanks,

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.