BRM15 Upgrade Fails As MD5 Encryption Returns A Different Value With BRM15
(Doc ID 3000788.1)
Last updated on FEBRUARY 06, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 15.0.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
While running the BRM15 upgrade script, ie pin_upgrade_15.pl, it fails near the end while try to connect to the cm with “invalid password” error.
pin_upgrade_15.pl output:
STEPS
-----------------------
Way to reproduce the issue:
sample_md5.c => contains the OOB make_digest function frm fm_cust_pol.
Makefile_32 => makefile to build 32 bits sample_md5
Makefile_64 => makefile to build 64 bits sample_md5
When executing 32 bits (as in BRM12):
sample_md5 password
md5: md5|5f4dcc3b5aa765d61d8327deb882cf99
When executing 64 bits (as in BRM15):
sample_md5 password
md5: md5|81060ad3da98104399e49ffa7db55172
Same code produces a different result depending on compiler option.
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 |