My Oracle Support Banner

Database Instance on VWS Nodes Created with Incorrect Character Set After OCNCC 5.0 Installation (Doc ID 1522076.1)

Last updated on AUGUST 21, 2019

Applies to:

Oracle Communications Network Charging and Control - Version 5.0.0 to 5.0.0 [Release 5.0]
Information in this document applies to any platform.

Symptoms

All database instances on OCNCC (Oracle Communication Network Charging & Control) nodes should be created with the AL32UTF8 character set. An issue in the beBe package installation results in the database instance on VWS (Vouchers & Wallets Server) nodes to be created with the US7ASCII character set instead. Other node types are not affected.

On the USMS and SLC: 

 

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
 Pre-installation workaround
 Post-installation workaround
 Create a backup of the VWS database
 Isolate both VWS’s from one Pair
 Start the migration-procedure for VWS
 Startup the VWS's
References

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