thank you for this clarification.
I would appreciate, if the doc would be more precise here and stress contradiction between BigFix and ILMT databases collation.
Original Message:
Sent: Fri March 20, 2026 03:58 AM
From: Oktawian Powązka
Subject: Invalid object name 'dbo.dbinfo'
Does it mean that the ILMT database require different collation than the BigFix database ?
That is exactly the point.
Let me ask the team to improve ILMT doc on this subject.
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Thu March 19, 2026 07:04 AM
From: JAN FLEGR
Subject: Invalid object name 'dbo.dbinfo'
Hello Oktawian,
thank you for this hint.
I've used the SQL_Latin1_General_CP1_CS_AS, as it is stated as a required collation for the ILMT database:
https://www.ibm.com/docs/en/license-metric-tool/9.2.0?topic=ir-software-requirements#system_requirements__ms_sql
so I set this up for the whole database instance and then any new database is created with SQL_Latin1_General_CP1_CS_AS.
Does it mean that the ILMT database require different collation than the BigFix database ?
------------------------------
JAN FLEGR
Original Message:
Sent: Thu March 19, 2026 05:56 AM
From: Oktawian Powązka
Subject: Invalid object name 'dbo.dbinfo'
Hello,
SQL_Latin1_General_CP1_CS_AS is a wrong collation for BFEnterprise database.
For BFEnterprise (and BESReporting) the collation must be case insensitive, as it is stated in BigFix documentation:
https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Installation/c_database_requirements.html?hl=collation
so e.g. collation SQL_Latin1_General_CP1_CI_AS would be correct for those two databases....
The only way to go further is to recreate the Bigfix database.
There is no workaround for incorrect collation as far as ILMT is concerned.
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Tue March 17, 2026 09:46 AM
From: JAN FLEGR
Subject: Invalid object name 'dbo.dbinfo'
Hello Oktawian,
Yes, same 'Invalid object name 'dbo.dbinfo' thrown by ComputerReconciliationImportStep
The Import log is reporting as follows:
Data Source: MSSQL database collation: SQL_Latin1_General_CP1_CS_AS
------------------------------
JAN FLEGR
Original Message:
Sent: Tue March 17, 2026 09:13 AM
From: Oktawian Powązka
Subject: Invalid object name 'dbo.dbinfo'
Hello,
Owner of the BFEnterprise database is not relevant.
By the same problem you mean 'Invalid object name 'dbo.dbinfo' thrown by ComputerReconciliationImportStep ?
As I wrote before, the most obvious root cause would be a incorrect collation.
Verifying collation can be tricky (database level vs server level).
So, what collation is reported by import log :
INFO: Data Source: MSSQL database collation: xxxx
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Mon March 16, 2026 12:29 PM
From: JAN FLEGR
Subject: Invalid object name 'dbo.dbinfo'
Hello Oktawian,
I have the same problem. My versions are BF 11.0.5 and ILMT 9.2.42.
I verified datasources login, and verified the table dbo.dbinfo exists in the BFEnterprise database.
Only unusal thing is the owner of the BFEnterprise database is my account, not the NT Authority\SYSTEM which operates all BES Services. I tried to grant dbo to NT Authority\System to BFEnterprise but no luck. Do I need to set the NT Authority\System as the owner of BFEnterprise database ? Or is it any other way how to make sure table dbo.dbinfo would be accessible / visible for the Import process ?
------------------------------
JAN FLEGR
Original Message:
Sent: Wed October 29, 2025 05:28 AM
From: Oktawian Powązka
Subject: Invalid object name 'dbo.dbinfo'
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
------------------------------