Important Information to Consider When Stopping Elements of an OCNCC System (Doc ID 1290386.1)

Last updated on FEBRUARY 12, 2024

Applies to:

Oracle Communications Network Charging and Control - Version 2.2.0 and later
Information in this document applies to any platform.

Purpose

The aim of this document is to provide System Administrators important information to be considered when shutting down an Oracle Communication Network and Charging Control (OCNCC, or NCC for short) system.

It provides information to shut each type of NCC server down, assuming the other servers are still running.
It also provides information on how to completely shut the NCC network down, highlighting interactions between the servers

A few important remarks:

It is rarely needed to shut the whole OCNCC system down. Usually, only parts of it will be stopped and restarted. However, this procedure will highlight important aspects of the relations between the OCNCC nodes when stopping parts of the application on and may be used as a reference when consolidating one's own strategy.
This document does not provide the procedure to stop the processes on each server, another document covers that aspect

How To Stop the OCNCC Application
This document does not explain how to start the NCC application, that is covered in this document

Important Information to Consider When Starting Elements of an OCNCC System

How To Start the OCNCC Application
More information on the OCNCC System Administration can be found in the following document Oracle Communications Network Charging and Control System Administrator's Guide available as of version 4.4.0.0.0 of the OCNCC product

How to Download Oracle Communications Network Charging and Control (OCNCC/NCC) Documentation
Any and all IP addresses, which feature in this article are fictitious and are detailed for the benefit of the article and it’s usefulness.

Scope

This document can be used by any Oracle engineers and NCC System Administrators. It does however require a good understanding of:

NCC application principles
the specifics of the particular implementation it is used for

This procedure presented here will need to be adapted to the situation of a real NCC network.

Even if this document is structured as a procedure, it does not aim to provide a fully defined and static set of instructions to follow in each and every particular case.
It proposes a common methodology to shutting down nodes and outlines potential issues or important-to-remember aspects.
It should serve as a reference or guidelines and learning tool to set up your own shutdown strategy, depending on specifics from your network.
This KM is relevant for a network with a single node SMS. Other principles not discussed here apply to a network that uses a clustered SMS.