My Oracle Support Banner

How to Enable/Disable Debugging on NCC Processes (Doc ID 1277843.1)

Last updated on AUGUST 16, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 2.2.0 to 4.3.0 [Release 2.2 to 4.3]
Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.

Goal

This Document will help to enable and disable debug on certain processes.

It provides details to Oracle engineers on what a process is doing, and therefore allows to see if anything is being processed incorrectly.
Debug is usually enabled by adding the "DEBUG" variable to the process startup script.
This "DEBUG" variable can contain multiple parameters to limit the debug output into the log. It has to be kept in mind that enabling debug on a process usually needs a lot of disk space, and is only done when it is really necessary.
The most common debug parameter is "all", which corresponds to full debug. The following parameters are also often used to limit the amount of output into the log:
 

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
 1. Enabling debug on a process
 1.1 Where to find the startup script
 1.2 Enabling debug
 2. Deactivate debug
 2.1 Where to find the startup script
 3. Log cleaning
 4. Set a targeted debug level
 5. Restart the SLEE
 5.1 On an SLC
 5.2 On a VWS
References


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