This documentation supports the 21.3 version of BMC Helix CMDB.To view an earlier version, select the version from the Product version menu.

Troubleshooting data decompression issue in CMDBDriver

You might encounter data decompression issues when the data that you are processing is large. The following table provides information about symptoms and the resolution to troubleshoot the issue:

Symptom

Resolution

The Decompression has failed error occurs when a resultset returned from the BMC Helix CMDB database to the AR System server is too large. If you are using the cmdbdriver program to retrieve data in bulk and it returns a large chunk of data, you might receive the error message that states, Decompression has failed. You might receive this error with cmdbdriver commands such as impdt and gli. 

  1. Open the %TEMP% and %TMP% directories.
  2. Check the space available for AR System server.
    Ensure there is enough space available for the AR System server.

You might get the following error when you use CMDBDriver to import a large XML file from a pod that is located outside the cluster. For example, from an exposed pod such as platform-fts-ext service.

Example

CMDBImportData  results
  ReturnCode:  ERROR
  Status List : 1 items
  Status Struct :
    Message type : ERROR
    Message number :  160
  Message:  Data Decompression has failed.
    Appended:  checksum does not match
  Total items Processed        :  0

Perform one of the following steps to resolve this issue: 

  • Use Atrium Integrator Spoon to create a job to export and import the CI data across environments.
    For information about creating a job in Atrium Integrator Spoon, see Creating a job in Atrium Integrator Spoon.
  • Create a case with BMC Support to import the required data.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*