After upgrading to FastDataMasker 4.10.114.0, we are not getting errors while masking on Azure DB2, but we also don't see the column getting masked. The values remain the same before and after FDM execution. Looking at the FDM debug logs, we see the following error reported, but the masking job shows as complete.
DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=TABLE, DRIVER=4.25.130
Release : 4.10
According to the FDM logs, FDM detected and used columns SYB_KEY_DSBL_CLM (Data Type INT) and TRD_CANC (Data Type DATE) as unique columns. Checking those columns in the database, we found that the TRD_CANC (DATE) column also contains NULL values. These NULL values are what's causing the issue.
Enabling the UPDATENULLINDEXCOLUMN options (UPDATENULLINDEXCOLUMN=Y) resolved the issue.