My Oracle Support Banner

ConfigLab Process Does Not Produce Log With Non-ascii Characters (Doc ID 1636712.1)

Last updated on MAY 04, 2022

Applies to:

Oracle Utilities Customer Care and Billing - Version 2.3.1 and later
Information in this document applies to any platform.


When running ConfigLab processes with trace options selected, process fails if the debug information contains non-ascii utf-8 characters (eg. in object descriptions). Perl script cobol/source/dm/CLBDSYNC.plx fails with error "Wide character in print". The workaround is to explicitly set encoding of log file in cobol/source/dm/CLBDSYNC.plx - in mymain() function after:


add line:

binmode($LogFH, ":utf8");

Error in batch run tree is:

Compare utility error 0000065280
Compare module error
Message number: 29, 18134

This problem exists for environments with SP17/SP7 installed, it used to work in past. In the meantime we also upgrade Oracle database from to, which could cause perl version upgrade.


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

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