BRM start_all Script Initially Fails to Start cm with Error "PIN_ERR_DM_CONNECT_FAILED"
(Doc ID 2661859.1)
Last updated on OCTOBER 23, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.5.0.22.0 and laterInformation in this document applies to any platform.
Symptoms
On Oracle Communications Billing and Revenue Management (BRM), when using the start_all script to start BRM, the Connection Manager (cm) process may fail to start. If start_cm is executed afterwards, cm starts successfully.
The error reported by cm is:
This issue primarily affects the start_all script shipped with default BRM installations, however it may also affect custom startup scripts depending on how the startup is done.
Essentially this affects cm if an attempt is made to start cm immediately after attempting to start dm_oracle.
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 |