DM_MALLOC Error When MD5 Crupt Entry Missing In DM_FUSA (Doc ID 979381.1)

Last updated on SEPTEMBER 24, 2016

Applies to:

Oracle Communications Billing and Revenue Management - Version: 7.3.1.0.0 and later   [Release: 7.3.1 and later ]
Information in this document applies to any platform.

Symptoms


 If MD5 encryption is disabled by commenting out the "crypt md5|" entry, 
errors are reported in the dm_fusa.pinlog file and also dm_malloc errors in dm_fusa.log.

DM_FUSA will start if MD5 encryption is enabled but an encryption key is not provided or a wrong key is provided.

Actually results
---------------
DM_FUSA starts even if the MD5 encryption key is missing or incorrect (MD5 encryption being enabled)

Expected results
----------------
DM_FUSA should not start when MD5 encryption is enabled but the key is missing or incorrect.


Changes

Applying Patch 8916625

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