IBM License Metric Tool (ILMT)

 View Only
Expand all | Collapse all

ILMT import error (disconnected scanner)

  • 1.  ILMT import error (disconnected scanner)

    Posted Mon March 20, 2023 08:57 AM

    Hi,

    The log for scheduled data import (disconnected scan files) reliably shows these errors, each followed by a java dump

    ERROR: [ILMTCore] (ImportAggregation-Thread:0) com.ibm.ilmt.core.aggregation.cache.CacheLoader::load:com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name '##temp_pre_inv_event_pvu_gr_0'.

    ERROR: [ILMTCore] (ImportAggregation-Thread:0) SQLException -> Message       : mainException
                 -> SQL Message   : Invalid object name '##temp_pre_inv_event_pvu_gr_0'.
                 -> SQL ErrorCode : 208
                 -> SQL State     : S0002
     com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name '##temp_pre_inv_event_pvu_gr_0'.

    although data seems to get imported, the Metric Quantity History chart on the PVU Subcapacity report has gaps in it.

    However, if I run the data import manually the error does not appear in the logs and it fills the gaps in the Metric Quantity History chart.

    More info that may be relevant:

    The ILMT server service is running as local system account. (windows)

    SQL server is on a different machine

    ILMT db collation is SQL_Latin1_General_CP1_CS_AS

    Would really appreciate any ideas!

    Thanks



    ------------------------------
    Simon Phillips
    ------------------------------


  • 2.  RE: ILMT import error (disconnected scanner)

    Posted Tue March 21, 2023 02:16 AM

    Hello there,


    The table names from both presented exceptions :
    Invalid object name '##temp_pre_inv_event_pvu_gr_0'.
    Invalid object name '##temp_node_aggr_event_pvu_gr_0'.


    show one common denominator: usage of SQL Server temporary tables.
    All temporary tables are created in the dedicated tempdb database...perhaps, some issues with tempdb database access.

    You've mentioned that if the data import is run manually the error does not appear...
    I reckon that this failing scheduled data import was always tried at the same time, correct ?
    If so, perhaps some database maintenance jobs (database backup, reindex, update) are conducted exactly at the time when ILMT tries to access tempdb database.
    To verify that theory please change the data import schedule to some other period...

    At last, I'd check the output of following SQL statements for any tempdb database access/locks run right after that particular import problem shows up :
    EXEC sp_who2
    EXEC sp_lock



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

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

    Original Message