This site is currently read-only as we are migrating to Oracle Forums for an improved community experience. You will not be able to initiate activity until January 30th, when you will be able to use this site as normal.

    Forum Stats

  • 3,890,147 Users
  • 2,269,775 Discussions


Data masking algorithm in OEM needs change.

Mahesh Pednekar
Mahesh Pednekar MrMember Posts: 34
edited May 13, 2016 11:17AM in Database Ideas - Ideas

I tried to use OEM to mask the SSN numbers. But the issue is, OEM uses a function/algorithm to generate a random masked SSN number that maches with some existing SSN number. There is a need to change the algorithm that generates a unique SSN number.

Mahesh Pednekar
4 votes

Active · Last Updated


  • top.gun
    top.gun Member Posts: 3,666 Gold Crown

    The problem is an algorithm that generates unique numbers, when the original numbers are not unique, will change the cardinality of the table.

    This affects the testing because you want the size of the result sets to be close to what's in production.

    You also want the execution plans to be the same as production.

    Everything changes when you change the cardinality of the data, and your testing becomes less meaningful.