Hi,
We've managed to replicate the problem:
1. TABLE1. Only one row. FIELD1(
PK,bigint, not null), FIELD2 (
nvarchar(max), null)
2. TABLE2. Same row as above. FIELD1(
PK,bigint, not null), FIELD2 (varchar(max), null).
3. TABLE3. Same row as above. FIELD1(bigint, not null), FIELD2 (
nvarchar(max), null)
FDM is not masking TABLE1. Other two tables are being masked. Not getting errors in log file. Job is completed succesfully.
Test made using FDM 4.8 version.
It looks like FDM is not masking nvarchar fields if table has a primary key.
I guess we need to open an issue anyway but just to share some more info about the problem in case it has a quick solution condering it's easy to reproduce.
Regards,
Jessica.
Original Message:
Sent: 01-17-2020 04:40 AM
From: Abderrahmane Zahrir
Subject: Masking job successfully completed but data is not being masked in DB.
Please use the latest FDM version as the current version 4.7.xxx.0 will not wor k against nvarchar type
Regsrds, Dahman
Original Message:
Sent: 01-17-2020 04:35 AM
From: Klaas-Jan Lute
Subject: Masking job successfully completed but data is not being masked in DB.
Hi Jessica,
I see that you got the filename wrong. Don't know if this is of any influence but maybe it confuses the system.
DBUPDATES=Y
LOGDIR=D:\MASKING\GMPH\DESA\PRUEBA3
LOGFILENAME=D:\MASKING\GMPH\DESA\PRUEBA3\log
The logfile name should be something like:
LOGFILENAME=log.txt
Best regards,
Klaas-Jan Lute
Original Message:
Sent: 01-17-2020 04:05 AM
From: Jessica Astorga
Subject: Masking job successfully completed but data is not being masked in DB.
Hi Klaas-Jan,
I've made the test suggested. Getting the same result. See log attached please.
I've tried a second round setting the commit to 1 since the table has only 70 rows. It didn't work either.
Thanks again for your help @Klaas-Jan Lute!
Regards,
Jessica.
Original Message:
Sent: 01-16-2020 07:24 AM
From: Klaas-Jan Lute
Subject: Masking job successfully completed but data is not being masked in DB.
Hi Jessica,
In the logfile I see that you have only set the LOGDIR and did not set the LOGFILENAME.
You could try to add the COMMIT=1000 and DBUPDATES=Y options. Although the default should be fine, it might help.
Best regards,
Klaas-Jan
Original Message:
Sent: 01-16-2020 03:56 AM
From: Jessica Astorga
Subject: Masking job successfully completed but data is not being masked in DB.
Hi Klaas-Jan,
I've tried to set TB15_IDDOCUMENTO as "unique column" in the masking rule. Same result. No errors but no updated in DB.
Please, see attached .csv and .log in case you find something wrong.
Thanks for your help.
Jessica.
Original Message:
Sent: 01-16-2020 01:24 AM
From: Klaas-Jan Lute
Subject: Masking job successfully completed but data is not being masked in DB.
Hi Jessica,
That is strange indeed. Is TB15_IDDOCUMENTO a unique column? If so, indicate this in the masking rule as Unique Column. That would help FDM to register the progress.
Best regards,
Klaas-Jan
Original Message:
Sent: 01-15-2020 08:39 AM
From: Jessica Astorga
Subject: Masking job successfully completed but data is not being masked in DB.
Hello Keith,
We're using FDM 4.7.3229.0 version.
In order to simplify the research, I've executed same job again applying the FIXED clause instead of our own masking rules.
Added also a WHERE clause to only update one record.
I'm getting the same result. Job is complete without errors but DB is not updated.
Please see attached log for more detail.
Any other suggested test will be welcomed.
Thanks again and regards,
Jessica.
Original Message:
Sent: 01-14-2020 09:11 AM
From: Keith Puzey
Subject: Masking job successfully completed but data is not being masked in DB.
Hi,
Do you have some more details on the issue you are seeing?
What version of FDM are you using?
Can you share the masking rules you are using?
Can you share the FDM logs?
------------------------------
Regards
Keith Puzey
Client Services Consultant | Enterprise Software Division
Broadcom
Original Message:
Sent: 01-14-2020 05:41 AM
From: Jessica Astorga
Subject: Masking job successfully completed but data is not being masked in DB.
Hi,
We're facing some issues with a masking job. The job is completed successfully but data is not being masked in Data Base.
We made sure DBUPDATES option is "Y".
The SQLFUNCTION we're using is working fine when we update the same DB using SqlServer Management Studio.
Same credentials are being used to launch the FDM marking job and updating through with SqlServer Management Studio.
Could you please help on this?
Thanks in advanced,
Jessica.