Handling Lossy CC_NUMBER_HASH1 Data Reported In CSSCAN (Doc ID 1132313.1)

Last updated on NOVEMBER 14, 2016

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.

USER.TABLE Convertible Truncation Lossy
-------------------------------------------------- ---------------- ---------------- ----------------
IBY.IBY_SECURITY_SEGMENTS|CC_NUMBER_HASH1 13,478 0 13,656
IBY.IBY_SECURITY_SEGMENTS|CC_NUMBER_HASH2 13,722 0 13,574
IBY.IBY_TRXN_SUMMARIES_ALL|INSTRNUM_HASH 36 0 11,830

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

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms