R12 AP: Change The Database Character Set Generates Invalid IBY Objects
Last updated on SEPTEMBER 22, 2016
Applies to:Oracle Payments - Version 12.2.3 and later
Information in this document applies to any platform.
On : 12.2.3 version, Upgrade
Using Oracle Database Migration Assistant for Unicode (DMU) to scan the data in the database prior to doing a character set conversion to AL32UTF8 from US7ASCII ,encrypted columns are flagged as invalid.
Running DMU flags data in the following tables/columns as 'Invalid Data':
IBY_EXT_BANK_ACCOUNTS BANK_ACCOUNT_NUM_HASH1 BANK_ACCOUNT_NUM_HASH2
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