This article explains How to change COSO references when updating Java client version on Network Automation. For instance, COSO reference and Java client update on NA 2019-05 and newer versions.

Environment
Network Automation
Linux

Situation

Network Automation - NA and Network Node Management NNMi got implemented into Network 
Object Management – NOM as a suit, still the clients can decide to keep separated the applications. 
NOM introduced COSO Reporting in 2020-08 version as an alternative to NPS with NNMi installation and 
as an alternative to OBR with NA installation.

NA 2019-05 comes with initial tool implementation not yet full implemented on the product due the 
object release, NA 2019-05 is a Bridge release between legacy versions (facility to skip upgrade versions 
on the product).

COSO functionality is active on version 2019-05 but not functional, still there are references internally on 
NA application to work with future versions; for some features support will need to modify those 
references depending on the client environment. Those references cannot/should not be removed, just 
updated properly in order to prevent additional issues when connecting with databases.

NA & COSO tool works with Java client 7, additional updates on the OS versions might need Java client 
to be updated to the latest version.

Make sure only one client is installed:

[root@naserver]# find /[NA_HOME]/ -name ojdbc*.jar -print
…/[NA_HOME]/server/ext/jboss/server/default/lib/ojdbc8.jar
Note: the number on the file will dictate the java client version installed.

[root@naserver]# ps -ef | grep -i jdbc
….
/opt/NA/server/ext/wrapper/lib/wrapper.jar:/opt/NA/server/ext/coso/lib/cososervice.jar:/opt/NA/client/tc_tools.jar:/opt/NA/server/ext/jboss/server/default/lib/ojdbc7.jar
…

For resolution, please read the complete knowledge article