My Oracle Support Banner

Handling Lossy CC_NUMBER_HASH1 Data Reported In CSSCAN For Oracle Payments Tables (Doc ID 1132313.1)

Last updated on FEBRUARY 27, 2020

Applies to:

Oracle Payments - Version 12.1.3 to 12.1.3 [Release 12.1]
Oracle Payments - Version 11.5.10.2 to 12.1.2 [Release 11.5 to 12.1]
Oracle Payables - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms


We are currently on an eBusiness system with a Western European database character set (WE8ISO8859P9).  We intend to convert the character set to UTF8 / AL32UTF8 so that multibyte characters are supported.

As part of the conversion activity, we have run CSSCAN.
In CSSCAN we find that there's huge LOSSY data for iPayment/Payments module.


How do we avoid losing this masked credit card numbers in the columns CC_NUMBER_HASH1 & CC_NUMBER_HASH2 ?

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.