My Oracle Support Banner

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 02, 2019

Applies to:

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


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 ( to have -resync flag.

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

    # su - <USER>
    $ 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




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
 Database and Environment Variable
Environment variables
 Deep Character-set Verification Using "csscan"
 Implication to Replication mechanism

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