Dm Cannot Be Started In Debug Mode
(Doc ID 1131994.1)
Last updated on MARCH 20, 2023
Applies to:
Oracle Communications Billing and Revenue Management - Version 7.3.0.0.0 to 7.3.0.0.0 [Release 7.3.0]Information in this document applies to any platform.
Goal
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?
Replication steps:
1) Stop all chain processes (cm, dm, eai_js).
2) Setup debug mode for DM.
export DM_DEBUG3=0xFFFFFF
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.
Solution
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
| Goal |
| Solution |
| References |