Also upgraded to 10.0.2.0 this week and am seeing the same error causing failure in our import logs. We have a support case opened for this. Should be getting attention on it soon.
Had the same problem and it seems HCL are aware and working on the issue. The workaround is to change the following Advance Settings and then the import seems to work:
@ageorgiev I see an ALL CAPS warning when attempting to modify the “split_ms_merge” value.
_Split SQL query for inserting software facts_
_Splits the SQL query that is used for inserting software facts into multiple queries to reduce usage of TEMPDB in a large-scale environment. Splitting the query lengthens the import. The parameter is applicable only on Windows. WARNING: USE THIS PARAMETER ONLY WHEN YOU ARE REQUESTED BY HCL SUPPORT_
Is there a simple process to reverse this if I enable the setting. Any cause for concern any than longer than normal imports?
This setting switches between two implementation. When set to “true” is causes to use the sample pattern on MS SQL as on the DB2 all the time.
There is possible to switch back. But I would not advice this per the known issue. Reversal might work when you will keep raw_data_api_history_keep_days to 0 (no history of the File Facts).
We are recommending using this option on large MS SQL deployments and also receive positive feedback that duration if also shorten. Please compare your result taking into account processed computers in Full Scan result once you switch to it.
The settings are always in Management -> Advanced Server Settings, so yes, you can change them back - the only limitation is that you can’t change those settings if the import is currently running. You need to wait for it to finish/fail, change them back.
If you want to be on the safe side open a Support case and work through it. I just shared a workaround I got off HCL since we run our environment MS SQL but of course it comes with a risk, so decide for yourself whether you are willing to try them.