Dm Cannot Be Started In Debug Mode
(Doc ID 1131994.1)
Last updated on APRIL 28, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.3.0]
Information in this document applies to any platform.
It is not possible to start DM in debug mode. Are there any limitations (e.g. product catalogue size, etc.) that have to be kept in order to retain possibility to start DM in debug level mode or this possibility relates to setup of particular system parameters?
1) Stop all chain processes (cm, dm, eai_js).
2) Setup debug mode for DM.
3) Start all chain processes in following order 1.dm_ifw_sync, 2. dmo_db1, 3. dmo_db2, 4. cm, 5. eai_js.
4) DM cannot be started.
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