Both V41 & V29 run the same SQL query on dbo.DBINFO to check BigFix server version.
The only difference between V41 & V29 is the JDBC driver version being used to run that SQL statement.
The most obvious root cause would be a different collation, but, as you stated both use the same Data Source connection setup.
As I wrote before,
I'd first verify if you are able to pass Data Source verification using 'Management: Data Sources' panel.
Please check tema log for any potential errors upon this check.
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
------------------------------
Original Message:
Sent: Tue October 28, 2025 05:49 PM
From: Bruce Connelly
Subject: Invalid object name 'dbo.dbinfo'
Perhaps you missed my summary that there are 2 ILMTs and BOTH have the same credentials and V29 has no issues at all. This means that in both cases the source info appears the same and the passwords are the same..
Its interesting that the V41 (now) still plots sub capacity data but vmman data from the central bigfix is absent in V41 but not in V29.
So in order to plot subcap database access must be occurring.
Strange isnt it, any suggestions knowing this, I will have to lodge an APAR I think.
Bruce
------------------------------
Bruce Connelly
Original Message:
Sent: Tue October 28, 2025 06:39 AM
From: Oktawian Powązka
Subject: Invalid object name 'dbo.dbinfo'
Import process checks the table dbo.DBINFO existence using BFEnterprise database not reports database (BESReporting).
BESReporting database is not being checked/used by ILMT for pretty long time...
I'd first verify if you are able to pass Data Source verification using 'Management: Data Sources' panel.
Just fill in missing fields like password and click Save.
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Mon October 27, 2025 12:00 AM
From: Bruce Connelly
Subject: Invalid object name 'dbo.dbinfo'
When using a single BigFix Source at version 10.0.14 level to multiple ILMT instances each using the same BigFix database source and credentials the following error is encountered at ILMT 39/40 and 41 but NOT 29.
2025-10-27 02:50:53:728 (+0:00:00.000) INFO: Computer Reconciliation: Start2025-10-27 02:50:53:743 (+0:00:00.015) ERROR: (Importcom.ibm.license.mgmt.etl.core.actions.ComputerReconciliationImportStep) Invalid object name 'dbo.dbinfo'.2025-10-27 02:50:53:743 (+0:00:00.000) ERROR: (Importcom.ibm.license.mgmt.etl.core.actions.ComputerReconciliationImportStep) SQLException -> Message : mainException -> SQL Message : Invalid object name 'dbo.dbinfo'. -> SQL ErrorCode : 208 -> SQL State : S0002 com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'dbo.dbinfo'.
The table dbo.DBINFO exists in the reports database, the user and credentials are the same.
There are no issues from the reconciliation step in v29.
The recommended collations are used and the id is the owner.
Any clues?
Bruce
------------------------------
Bruce Connelly
------------------------------