RE: Data Masking Pack
Date: Mon, 26 Oct 2009 14:13:57 -0400
One additional piece of info. He ran the data masking pack via OEM 10.2.0.5 to create the code which was deployed to a 10.2.0.4 database.
From: Kenneth Naim [mailto:kennaim_at_gmail.com]
Sent: Monday, October 26, 2009 2:13 PM
To: 'Oracle Discussion List'
Subject: Data Masking Pack
My colleague implemented data masking of credit cards, ssn's and bank accounts and ran into some errors, so I was asked to review the code generated by the pack. It seems a lot more complicated than it needs to be. I see constraints/triggers/tables being dropped, renamed and recreated, procedures being created and later dropped for every table being masked, hundreds of lines of null being concatenated together etc. Is this the way this pack should work? Does this logic make any sense to any one? How is this better that a simple procedure that disables constraints and triggers, and generates a random value for the column and then perform a mass update.
KenReceived on Mon Oct 26 2009 - 13:13:57 CDT