My Oracle Support Banner

CM Is Not Starting After Enabling The AES Key Encryption (Doc ID 2395972.1)

Last updated on MARCH 22, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version and later
Information in this document applies to any platform.


On : version, Infranet Install

Connection Manager(CM) is not getting started after enabling the AES (Advanced Encryption Standard) key encryption.

In order to migrate data from MD5 to AES Encryption, followed below steps;
1. Generated an AES key using the below command.
pin_crypt_app -genkey
2. Replace the AES key in the DM pin.conf
- crypt aes|${PIN_HOME}/lib/ "&aes|0D5E11BFDD97D2769D9B0DBFBD1BBF7EA82D797B052BA01C25BA4CC68417681C8B277F9229BCADC69E13B1230AAA0158"
- decrypt md5| "Abracadabra dabracaabrA"
3. Changed the login_pw in CM pin.conf
- cm infmgr_login_pw &aes|08|0D5E11BFDD97D2769D9B0DBFBD1BBF7E5D40C305EDF3D77DF111AAB8F781E92122

Data Manager (DM) started up , but CM is not starting up. CM is not making a connection to DM.

Error in cm.pinlog:





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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.