Incorrect Character-Set on Table ACS_NOTIF_TMPL Breaks Full Replication with Error "smsCompareResyncClient(2825) CRITICAL: Data Length XYZ Exceeds Maximum Size Of Data Column 256"

(Doc ID 1414393.1)

Last updated on OCTOBER 18, 2016

Applies to:

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

Symptoms

When attempting to do Replication Full-Resync, the following error occurs in updateLoader log.

smsCompareResyncClient(2825) CRITICAL: Data Length 263 Exceeds Maximum Size Of Data Column 256



The issue can be reproduced at will with the following steps:

  1. in SLC, change startup script of updateLoader (updateLoaderStartup.sh) to have -resync flag.

    # cat /IN/service_packages/SMS/bin/updateLoaderStartup.sh
    exec /IN/service_packages/SMS/bin/updateLoader -nodeid <node_id> -resync
  2. restart updateLoader process, by killing it.

    # su - smf_oper
    $ pkill updateLoader
  3. monitor Full-Resync progress in /IN/service_packages/SMS/tmp/updateLoader.log.

 

SLC : Service Logic Controller
SMS : Service Management Server
VWS : Voucher Wallet Server

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms