After an upgrade the opr-clis log file start to filling rapidly

Document ID:KM03287431
Creation Date:14-Nov-2018
Modified Date:14-Nov-2018
- Micro Focus Products:
  operations bridge manager 2018.05

Summary

The opr-clis log start to filling rapidly and continuously with error messages.

Question

The opr-clis log file is filling rapidly and continually.

2018-10-03 15:28:09,429 [main] ERROR DBPropertiesManager.propertiesTableInit(112) - Failed to initialize IDGen

com.mercury.jdbc.sqlserverbase.dden: [Mercury][SQLServer JDBC Driver]A username was not specified and the driver could not establish a connection using Kerberos (type 4) integrated security: java.io.IOException: D:/HPBSM/lib/JDBCDriverLogin.conf (No such file or directory)

rethrown as com.mercury.infra.utils.exceptions.MNoSuchElementException: Failed to create a connection for pool: dbType=(SQL Server); hostName=OH01POBS03VAGL; dbName=mgmt; userName=; server=OH01POBS03VAGL; port=1433: [Mercury][SQLServer JDBC Driver]A username was not specified and the driver could not establish a connection using Kerberos (type 4) integrated security: java.io.IOException: D:/HPBSM/lib/JDBCDriverLogin.conf (No such file or directory)

at com.mercury.infra.utils.db.pools.ConnectionFactory.makeObject(ConnectionFactory.java:204)

Caused by: com.mercury.jdbc.sqlserverbase.dden: [Mercury][SQLServer JDBC Driver]A username was not specified and the driver could not establish a connection using Kerberos (type 4) integrated security: java.io.IOException: D:/HPBSM/lib/JDBCDriverLogin.conf (No such file or directory)

Answer

Based on the errors and previos case on lab, we found that the issue is related to the policy OMi_BusMonitor

Customer was using Windows authentication for sql server.
In order to solve the issue we will need to added the following at line 53 of OMiSmBusMonitoring.pl
hdir "$omihome/bin"

Note: If the customer is not using the policy he can also disable the policy and the message error will not longer appears.