Idea ID 1674048
Some users choose an external Java for iSPI Metrics (NPS) during installation. Later on Linux admin may update
Linux stuff including Java. This changes the path to the current Java and older java is typically getting deleted. When a user starts iSPI it reports errors about connection to CS DB and BI server fails to start. Analysis shows CS DB is running and it is even possible to connect and run queries using isql. However, the tools cssize.ovpl and statusCS.ovpl say CS DB is not running. This is because the wrong (older) Java path in NNMPerformanceSPI.cfg. NPS admin may not know about Linux updates which sometimes happen centrally and automatically. It makes it very difficult to find the root cause because there are no relevant errors in ASE and other log files. This is a request to display a message about wrong Java when starting iSPI with startALL.ovpl, startCS.ovpl, or startBI.ovpl.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.