Last updated on SEPTEMBER 24, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Checked for relevance on 29-Dec-2011
Checked for relevance on 27-May-2016
Oracle Database defines by default the parameter NLS_LENGTH_SEMANTICS as BYTE.
This definition generates errors when you define, for example, a VARCHAR2(10) field and you load more
than 5 multibyte characters (UTF-8) such as "�������".
This problem can be solved if you define the parameter as CHAR (specifying LS_LENGTH_SEMANTICS=CHAR) and after that you define the field as VARCHAR2(10).
How would this change (BYTE to CHAR) impact BRM?
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