Issue with testnap for OZT encryption
(Doc ID 2592984.1)
Last updated on MAY 20, 2022
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
Starting with Billing and Revenue Manger (BRM) 12.0, the old MD5 encryption method was moved to OZT encryption.
In case of an upgrade from BRM 7.5 PSxx to BRM 12.0, pin_crypt_upgrade script is responsible for moving from MD5 encryption to OZT.
Sometime, this script might fail and customer should enable OZT by-hand, using pin_crypt_app utility:
$pin_crypt_app -useZT -genkey [-key <key>] [-update_dm_conf] ---> to set it in dm pin_conf
After this change and a restart of CM and DM_ORACLE, it was observed that testnap fails to start anymore. The following error messages was printed on cm.pinlog file:
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |