NCC 12 Does Not Allow For Zero-downtime Upgrade 32- To 64-bits (Doc ID 2708768.1)

Last updated on SEPTEMBER 15, 2020

Applies to:

Goal

In the context of an upgrade from an older Oracle Communications Network Charging and Control (OC-NCC/NCC) version (which is running in 32-bit mode) to a recent version running in 64-bit mode, it seems beClient and beVWARs does not support a backward compatibility mode allowing to implement compatible32bit = false node-by-node.
Current design assumes that whole platform is shut down and in *all* nodes compatible32bit is set to false (or the flag is removed).

This is not realistic in case of real-life production platform which has to be upgraded without stopping traffic processing.

Proposed 64-bit enablement strategy:

- Step 1: Turn VWS2 into 64-bit mode. SMS, SLC1, SLC2, VWS1 in 32-bit. VWS2 in 64-bit mode.
- Step 2: Turn VWS1 into 64-bit mode. SMS, SLC1, SLC2 in 32-bit. VWS1, VWS2 in 64-bit mode.
- Step 3: Turn SLC1 into 64-bit mode. SMS, SLC2 in 32-bit. VWS1, VWS2, SLC1 in 64-bit mode.
- Step 4: Turn SLC2 into 64-bit mode. SMS in 32-bit. VWS1, VWS2, SLC1, SLC2 in 64-bit mode.
- Step 5: Turn SMS into 64-bit mode. All nodes: VWS1, VWS2, SLC1, SLC2, SMS in 64-bit mode.

Is it possible to adapt further versions of NCC so the proposed upgrade strategy will be possible?

Solution

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