How to Dynamically Switch the CM Loglevel and DM Debug Flags for the Current CM Process? [Video]
(Doc ID 1382172.1)
Last updated on JULY 16, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 6.0.3 to 7.5.0]
Information in this document applies to any platform.
***Checked for relevance on 10-Jul-2014***
Checked for relevance on 13-Feb-2017.
A presentation on How to dynamically switch the CM loglevel and DM debug flags for the current CM process.
On systems where the loglevel needs to be set to 1 in order to keep logs small, it is often difficult to troubleshoot problems when they arise as there is limited information.
This quick tutorial will show you how to dynamically change the loglevel of the CM and DM, within a context/session, to help trace a problem.
It can be used to limit the size of logs and only enable full logging on certain portions of your session.
For example, a scenario failed while calling the opcode PCM_OP_CUST_MODIFY_CUSTOMER with a custom input flist mod_account.flist.
nap(12336)> d 1
...< the content of mod_account.flist should be displayed here >...
nap(12336)> xop PCM_OP_CUST_MODIFY_CUSTOMER 0 1
xop: opcode 64, flags 0
XOP "64" failed:
...< some error messages from the failure >...
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