Unable to Execute Pin_crypt_upgrade In Secondary Schemas when Encryptable Flag is Set to 1
(Doc ID 2104223.1)
Last updated on FEBRUARY 20, 2019
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On : 188.8.131.52.0 version, DM
As per business requirement Customer needs to encrypt certain fields in BRM DB. For encrypting historic data and migrated data, pin_crypt_upgrade utility is used.
The utility is throwing error only when the encryptable flag is set to 1 in the dd_object_field tables for field ‘PIN_FLD_PASSWD’ in class config/pricing_admin and 'PIN_FLD_BIC', 'PIN_FLD_IBAN' in class /config/creditor.
Analyzed further and found these config classes have tables on primary and views on other schemas as result pin_crypt_upgrade utility is failing to update data present on schemas other than primary.
1. The utility, pin_crypt_upgrade is working fine when the encryptable flag in dd_object_field_t is set to 0 for fields in config class
(namely for field ‘PIN_FLD_PASSWD’ in class config/pricing_admin and 'PIN_FLD_BIC', 'PIN_FLD_IBAN' in class /config/creditor.)
2. Executed the utility from Primary schema and verified that it is updating/encrypting data across all the schemas.
3. Found that above mentioned config classes has config tables on PRIMARY schema and views on other schemas.
4. Tried executing the utility by setting the encryptable flag as 1 on the table dd_object_field_t for config classes on schema 1 and set encryptable flag as 0 on other schemas. Checked that it is working, but data present of other schemas were not updated/encrypted.
Qn: How to resolve this issue?
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