Last updated on OCTOBER 18, 2016
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.
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:
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms