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.  ILMT - Error on Import

    Posted Thu June 22, 2023 10:49 AM

    I have recently upgraded my ILMT Server to V31.  I am getting a failure error when attempting to perform an import.  Any ideas ?

    Below is a section of the import log with the associated error message.

    2023-06-22 01:00:25 (+0:00:15.959) INFO:  (ImportStep:CatalogMerger) IBM Catalog changes have been successfully transfered to SAM tables in 15959 milliseconds. No tables have been updated.
    2023-06-22 01:00:25 (+0:00:00.015) INFO: Moving IBM Software Catalog to SAM tables: Success
    2023-06-22 01:00:25 (+0:00:00.000) INFO: Calling SAM::PartNumber.before_snapshot: Start
    2023-06-22 01:00:25 (+0:00:00.518) INFO: Calling SAM::PartNumber.before_snapshot: Success
    2023-06-22 01:00:25 (+0:00:00.000) INFO: Calling SAM::CitSwConfigFile.before_snapshot: Start
    2023-06-22 01:00:25 (+0:00:00.125) INFO: Calling SAM::CitSwConfigFile.before_snapshot: Success
    2023-06-22 01:00:25 (+0:00:00.000) INFO: Check for computer_health_property_mappings: Start
    2023-06-22 01:00:25 (+0:00:00.031) INFO: Check for computer_health_property_mappings: Success
    2023-06-22 01:00:25 (+0:00:00.000) INFO: Cleaning Software Classification temporary user data if exists: Start
    2023-06-22 01:00:25 (+0:00:00.016) INFO: Cleaning Software Classification temporary user data if exists: Success
    2023-06-22 01:00:25 (+0:00:00.000) INFO: Determine models which need catalog update: Start
    2023-06-22 01:00:32 (+0:00:07.033) ERROR: SQL: {call [dbo].[etl_sam__software_title_versions](?,?,?,?,?,?,?,?,?,?,?,?,?,?)} Queue: 1000 Exception: #<Java::ComMicrosoftSqlserverJdbc::SQLServerException: Cannot insert the value NULL into column 'software_title_id', table 'temadb.sam.software_title_versions_scd'; column does not allow nulls. INSERT fails.>
    2023-06-22 01:00:32 (+0:00:00.000) ERROR: Batch execution error: 
    2023-06-22 01:00:32 (+0:00:00.015) INFO: Determine models which need catalog update: Failed
    2023-06-22 01:00:32 (+0:00:00.000) ERROR: Catalog import of type xml failed - will retry during next data import.
    2023-06-22 01:00:32 (+0:00:00.016) ERROR: RuntimeError: Catalog import of type xml failed - will retry during next data import.
        D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/domains/sam/app/models/sam/catalog_update.rb:170:in `latest_set_failed'
        D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/domains/sam/app/models/sam/catalog.rb:437:in `block in etl_before_datasources'
        org/jruby/RubyArray.java:1865:in `each'
        D:/Program Files/ibm/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-



    ------------------------------
    Paula Stewart
    ------------------------------


  • 2.  RE: ILMT - Error on Import

    Posted Fri June 23, 2023 02:38 AM

    Hi Paula,

    this might help:

    https://www.ibm.com/support/pages/after-upgrading-9231-some-cases-it-not-possible-update-license-metric-tool-database-schema

    Any suggestion from  the IBM support team?

    Michael



    ------------------------------
    Michael Köster
    ------------------------------



  • 3.  RE: ILMT - Error on Import

    Posted Fri June 23, 2023 03:30 AM

    Hi,

    What happens if you re-run the data import ? Is the same error thrown ?

    Thanks.



    ------------------------------
    Andrei Ionescu
    IBM
    Bucharest
    ------------------------------



  • 4.  RE: ILMT - Error on Import

    Posted Fri June 23, 2023 03:58 AM

    Hi Paula,

    The fundamental question is: is this the first import AFTER upgrade ?
    If it's the subsequent import please give us an output/log file from the first import process after upgrade...



    ------------------------------
    Thank you,
    Oktawian

    Oktawian Powązka, L3 Support
    IBM License Metric Tool
    ------------------------------



  • 5.  RE: ILMT - Error on Import

    Posted Mon June 26, 2023 09:19 AM
    Edited by Paula Stewart Mon June 26, 2023 09:21 AM

    Hi Oktawian -

    I am having issues uploading a file, so I am pasting the log below.  This is the log from the very first import after upgrade.  Thanks, Paula

    # Logfile created on 2023-06-19 17:29:27 +0000 by logger.rb/v1.5.1
    2023-06-19 17:29:27 (+0:00:00.000) INFO: ILMT version: 9.2.31.0-20230316-1027
    2023-06-19 17:29:27 (+0:00:00.001) INFO: All times in log are in UTC time zone!
    2023-06-19 17:29:27 (+0:00:00.001) INFO: Import created at (UTC): 2023-06-19 17:29:27 UTC
    2023-06-19 17:29:27 (+0:00:00.000) INFO: Import type: complete
    2023-06-19 17:29:27 (+0:00:00.001) INFO: Local server timezone: CurrentTimeZone=-300 (UTC-06:00) DaylightBias=-60
    2023-06-19 17:29:27 (+0:00:00.003) INFO: Detected License Metric Tool database version: 11.0.7001.0
    2023-06-19 17:29:27 (+0:00:00.028) INFO: [ILMTCore] (Import_ILMTCoreThread) ILMT Core version: 9.2.31.0-2023-03-16_09:38:46
    2023-06-19 17:29:27 (+0:00:00.025) INFO: Previously imported Catalog version: 9.2.14.0
    2023-06-19 17:29:28 (+0:00:00.133) INFO: Check datasources connectivity: Start
    2023-06-19 17:29:29 (+0:00:01.109) INFO: Trying another TLS version because of an error during TLSv1.2 connection with IEM nt7535.nml.com: Connection refused: connect
    2023-06-19 17:29:30 (+0:00:01.023) ERROR: TemServerAPI::TemServerAPIError: An error occured while preparing to send the request.
    Error during TLSv1 connection with IEM nt7535.nml.com: Connection refused: connect
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/tem_server_api.rb:52:in `send_request'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/tem_server_api.rb:203:in `test_connection'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/app/models/datasource_tem_server.rb:99:in `method_missing'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:236:in `block in check_datasources'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/dataset/actions.rb:137:in `block in each'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:825:in `process_result_set'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:754:in `block in fetch_rows'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:259:in `block in execute'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:672:in `statement'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:251:in `block in execute'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/connection_pool/threaded.rb:114:in `hold'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/database/connecting.rb:254:in `synchronize'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:250:in `execute'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/dataset/actions.rb:921:in `execute'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/adapters/jdbc.rb:754:in `fetch_rows'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/dataset/actions.rb:137:in `each'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/gems/gems/sequel-4.24.0.0fe2570236e05948c56727f2e00bdbedcf0b542d/lib/sequel/model/plugins.rb:28:in `each'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:233:in `check_datasources'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:50:in `block in run'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:193:in `block in within_import'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/dss/logger.rb:22:in `log_to'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:175:in `block in within_import'
        org/jruby/RubyKernel.java:1940:in `tap'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:164:in `within_import'
        D:/LMT/wlp/usr/servers/server1/apps/tema.war/WEB-INF/lib/etl/runner.rb:41:in `run'
        :1:in `'
        :1:in `block in '
    2023-06-19 17:29:30 (+0:00:00.052) INFO: Import failed in 0:00:03
    2023-06-19 17:29:30 (+0:00:00.001) INFO: Import contains 1 errors.



    ------------------------------
    Paula Stewart
    ------------------------------



  • 6.  RE: ILMT - Error on Import

    Posted Mon June 26, 2023 10:43 AM

    Hi Paula,

    Actually that first import error (connection with IEM nt7535.nml.com: Connection refused: connect) is completely unrelated with the subsequent catalog import problem.


    I can see two potential root causes which has driven that particular catalog import issue: 
    1) some intermittent catalog file's access problems,
    2) some previous catalog import errors reported AFTER that initial IEM Connection issue (there is three days gap between first and this 'last' run).

    To find out more I would need to verify ALL possible import logs captured after upgrade...

    You could try to re-run the data import but usually when import fails on catalog import step the subsequent import is doomed to fail.
    In such case bringing the temadb database snapshot taken right after an upgrade (or, if not available, repeating the whole upgrade process) is the only solution...

    As this whole issue is not trivial I'd say that opening support ticket to us would be the best solution... 



    ------------------------------
    Thank you,
    Oktawian

    Oktawian Powązka, L3 Support
    IBM License Metric Tool
    ------------------------------