My Oracle Support Banner

How to Dynamically Switch the CM Loglevel and DM Debug Flags for the Current CM Process? (Doc ID 1382172.1)

Last updated on DECEMBER 24, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.0.0.0.0 to 7.5.0.0.0 [Release 7.0.0 to 7.5.0]
Information in this document applies to any platform.

Goal

On Billing and Revenue Management (BRM) systems where the log level needs to be set to 1 in order to keep the size of log files to a small value, it is often difficult to troubleshoot problems when they arise as there is limited information in the log file.

This quick tutorial will show you how to dynamically change the log level of the CM (connection manager) and DM (data manager), 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, consider a scenario that failed while calling the opcode PCM_OP_CUST_MODIFY_CUSTOMER with a custom input flist mod_account.flist.

nap(12336)> r mod_account.flist 1
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 >...
...
nap(12336)>

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

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