IBM License Metric Tool (ILMT)

IBM License Metric Tool (ILMT)

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only

  • 1.  Issue With Initial Import: dbo.Computers Not Found

    Posted Mon October 11, 2021 12:55 AM

    Hi all ...

    I tried to install ILMT 9.2.25. Installation appeared to be fine. Then I ran the initial import. It got about 90% of the way through and then failed because it could not find dbo.computers. I opened the ILMT database and saw the view dbo.computers with one record in it, probably that of the IBM server. We tried dropping the database and letting the ILMT installer recreate it but still ran into the same issue. The id running the Import was the Administrator and it has sysadmin on the database. Any idea what else I can check? Here's the relevant part of the import log:

    2021-10-08 16:58:17 (+0:00:00.000) INFO: ETL from Reaggregation: Start 2021-10-08 16:58:17 (+0:00:00.344) INFO: ETL from Reaggregation: Success 2021-10-08 16:58:17 (+0:00:00.000) INFO: ETL from Aggregation: Start 2021-10-08 16:58:18 (+0:00:00.422) INFO: (ImportThread) com.ibm.license.mgmt.etl.core.actions.RunAggregationAction::execute::STATISTICS: IBM Aggregation is completed for group All Computers : PVU from 2021-10-08 to 2021-10-08 - 1 day processed, RVU from 2021-10-08 to 2021-10-08 - 1 day processed, VPC from 2021-10-08 to 2021-10-08 - 1 day processed, INSTALL_INSTANCES from 2021-10-08 to 2021-10-08 - 1 day processed, OTHER from 2021-10-08 to 2021-10-08 - 1 day processed, FLEXPOINT from 2021-10-08 to 2021-10-08 - 1 day processed 2021-10-08 16:58:18 (+0:00:00.016) INFO: ETL from Aggregation: Success 2021-10-08 16:58:18 (+0:00:00.000) INFO: ETL from UpdateComputerSystems: Start 2021-10-08 16:58:21 (+0:00:02.828) INFO: ETL from UpdateComputerSystems: Success 2021-10-08 16:58:21 (+0:00:00.000) INFO: ETL from UpdateComputerHealthStatus: Start 2021-10-08 16:58:21 (+0:00:00.312) ERROR: (ImportThread) Invalid object name 'dbo.computers'. 2021-10-08 16:58:21 (+0:00:00.000) ERROR: (ImportThread) SQLException -> Message : mainException -> SQL Message : Invalid object name 'dbo.computers'. -> SQL ErrorCode : 208 -> SQL State : S0002 com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'dbo.computers'.

    ... followed by a Java dump that is really long, followed by:

    2021-10-08 16:58:21 (+0:00:00.015) ERROR: LMT ETL step failed, response code: 500 2021-10-08 16:58:21 (+0:00:00.000) INFO: ETL from UpdateComputerHealthStatus: Failed 2021-10-08 16:58:21 (+0:00:00.000) ERROR: RuntimeError: LMT ETL step failed D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/domains/sam/lib/sam/lmt.rb:126:in `send_request' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/domains/sam/lib/sam/lmt.rb:58:in `run' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/domains/sam/domain.rb:630:in `block in Domain' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/task.rb:12:in `run' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/tasks.rb:81:in `run_task' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/tasks.rb:120:in `block in run_multi_txn' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/database/transactions.rb:134:in `_transaction' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/database/transactions.rb:108:in `block in transaction' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/connection_pool/threaded.rb:110:in `hold' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/database/connecting.rb:254:in `synchronize' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/database/transactions.rb:97:in `transaction' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/database/transactions.rb:83:in `transaction' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/tasks.rb:119:in `block in run_multi_txn' org/jruby/RubyArray.java:1809:in `each' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/tasks.rb:115:in `run_multi_txn' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/tasks.rb:24:in `run' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:77:in `block in run' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/sequel/extensions/isolation_level.rb:18:in `block in with_isolation_level' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/connection_pool/threaded.rb:110:in `hold' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/database/connecting.rb:254:in `synchronize' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/sequel/extensions/isolation_level.rb:14:in `with_isolation_level' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:76:in `block in run' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/sequel/extensions/date_utils.rb:22:in `block in freeze_date' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/connection_pool/threaded.rb:114:in `hold' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.9d792a04e8ef0cea89ab8b94522b4942/lib/sequel/database/connecting.rb:254:in `synchronize' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/sequel/extensions/date_utils.rb:17:in `freeze_date' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:74:in `block in run' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:186:in `block in within_import' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/dss/logger.rb:22:in `log_to' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:168:in `block in within_import' org/jruby/RubyKernel.java:1897:in `tap' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:158:in `within_import' D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:41:in `run' :1:in `' :1:in `block in '

    A case can be opened if necessary.



    #AIX
    #Support
    #SupportMigration


  • 2.  RE: Issue With Initial Import: dbo.Computers Not Found
    Best Answer

    Posted Mon October 11, 2021 12:57 AM

    I guess you can't edit once submitted ... forgot to mention, this is ILM on Windows, where BigFix 10.0.0.4 was installed separately on the same machine.



    #AIX
    #Support
    #SupportMigration


  • 3.  RE: Issue With Initial Import: dbo.Computers Not Found
    Best Answer

    Posted Wed October 13, 2021 01:57 AM

    Hi

    Sorry for the delay.

    Can you check in your MS SQL Management Studio if you can locate

    dbo.computers table

    in database instance TEMADB or BFENT DB?

    Thanks



    #AIX
    #Support
    #SupportMigration


  • 4.  RE: Issue With Initial Import: dbo.Computers Not Found
    Best Answer

    Posted Thu October 21, 2021 05:36 PM

    Hi ...


    We determined that the database collation was set incorrectly for BigFix. We reinstalled SQL Server and are now starting all over with the BigFix installation followed by the ILMT install. Hopefully that corrects this issue. The reinstall is currently underway.


    --Mark



    #AIX
    #Support
    #SupportMigration


  • 5.  RE: Issue With Initial Import: dbo.Computers Not Found
    Best Answer

    Posted Thu October 28, 2021 10:21 PM

    I also have the same error when installing ILMT 9.2.25. Installation was fine. and the initial import failed because it could not find dbo.computers.

    Reviewed the ILMT database and the object was not there.

    There is conflicting information the document on this link Performing

    initial configuration on Windows (BigFix scenario) - IBM Documentation mentions when manually creating the database, it should have SQL_Latin1_General_CP1_CS_AS Collation (this is CS-Case Sensitive) However the document in this Database

    requirements (hcltechsw.com) link states the Server, database and column level collation must be CI-Case insensitive which is SQL_Latin1_General_CP1_CI_AS Collation.



    #AIX
    #Support
    #SupportMigration


  • 6.  RE: Issue With Initial Import: dbo.Computers Not Found
    Best Answer

    Posted Fri October 29, 2021 03:08 PM

    We determined that the database collation was set incorrectly for BigFix. We reinstalled SQL Server with the correct collation followed by the ILMT install. The initial import ran successfully.



    #AIX
    #Support
    #SupportMigration


  • 7.  RE: Issue With Initial Import: dbo.Computers Not Found
    Best Answer

    Posted Fri October 29, 2021 03:16 PM

    It would be nice if the BigFix installer could detect that the SQL server collation was wrong and simply stop the install process at that point. Or maybe have the ILMT installer fail if the default database collation is wrong for it. That assumes the database collation could be checked programmatically through the installers. I don't understand why BigFix requires the database collation of CI while ILMT requires CS - why couldn't they be consistent? Backward compatibility maybe? (rhetorical questions)



    #AIX
    #Support
    #SupportMigration