(9.2.15) The Import of data might fail on SAM::AppUsage or UsageManager import step

Abstract
After upgrade to BigFix Inventory 9.2.15.0, the import of data might fail on SAM::AppUsage or UsageManager import step.

Content
BigFix Inventory 9.2.15 - import might fail on SAM::AppUsage or UsageManager import step.
The issue does not apply to License Metric Tool 9.2.15. Only BigFix Inventory 9.2.15 is affected.

Symptoms

  1. SAM::AppUsage step - java.lang.NullPointerException exception
    INFO: ETL from - SAM::AppUsage (0x0000000000000000 - N/A): Start
    INFO: (ImportThread) com.ibm.license.mgmt.etl.core.actions.bigfix.usage.ImportAppUsageForDatasourceAction::doAction: Uploading Application Usage data from BigFix.
    ERROR: (ImportThread) execute failed - unexpected exception java.lang.NullPointerException
    at com.ibm.license.mgmt.etl.core.actions.bigfix.usage.UploadAppUsageToTempAction.parseAppUsageAnalysisRecord(UploadAppUsageToTempAction.java:124)

  2. SAM::AppUsage step - Error converting data type datetime2 to datetime
    ERROR: (ImportThread) SQLException -> Message : mainException
    -> SQL Message : Error converting data type datetime2 to datetime.
    -> SQL ErrorCode : 8114
    -> SQL State : S0001
    java.sql.BatchUpdateException: Error converting data type datetime2 to datetime.

  3. UsageManager - Duplicate key com.ibm.license.mgmt.usage.bean.UsePathBean
    INFO: ETL from UsageManager: Start
    INFO: (ImportThread) com.ibm.license.mgmt.etl.core.actions.RunUsageManagerAction::doAction::Measuring usage by matching process and discovery paths…
    ERROR: (ImportThread) execute failed - unexpected exception java.lang.IllegalStateException: Duplicate key com.ibm.license.mgmt.usage.bean.UsePathBean@<…>

  4. UsageManager - java.lang.StringIndexOutOfBoundsException exception
    INFO: ETL from UsageManager: Start
    INFO: (ImportThread) com.ibm.license.mgmt.etl.core.actions.RunUsageManagerAction::doAction::Measuring usage by matching process and discovery paths…
    ERROR: (ImportThread) execute failed - unexpected exception java.lang.StringIndexOutOfBoundsException

Workaround
To complete the import without any errors, disable the step that fails. It refers to the new discovery method of software usage for Java (distinguished by path).
As a workaround you can temporarily disable the new function:

  1. Use the REST API call and set the parameter e nable_signature_less_usage to false. For more information about how to change the parameter value, see: Configuration of advanced server settings.
  2. Send a PUT request to the following URL:
    http(s)://:/api/sam/configs?token=&name=enable_signature_less_usage&value=false
  3. Restart the BigFix Inventory server.

Once the BigFix Inventory server is up and running, the next import of data should not invoke the failing step.

3 Likes

Hi Michal,
I encountered the error, and set the parameter to false.
Does it mean that this method is disabled for ever, and I will not be able to use it to discover Java process distinguished by path ?
Thanks to answer

No, we are working to fix the issue and bring back this feature.