BRM Cannot Install on Oracle Database That Has AL32UTF8 as Its Character Set
(Doc ID 737499.1)
Last updated on JUNE 24, 2022
Applies to:Oracle Communications Billing and Revenue Management - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 7.3.0 to 7.4.0]
Information in this document applies to any platform.
Attempting to install BRM using pin_setup.bat, those tables were able to be installed into the database (Oracle XE 10g); but when trying to start up DM, it failed due to incompatibility with the character set. It expected exactly the name "UTF8"; whereas, by default, the character set goes to AL32UTF8.
The documentation says to use UTF8, so the user tried to find a way to change an Oracle 10g or Oracle 18.104.22.168 DB to be UTF8. But the sys.props$ says it is AL32UTF8. What is the difference and/or how to change it? AL32UTF8 should be the standard, but it looked like the software was expecting and hardcoded UTF8 in BRM.
Env variable NLS_LANG=American_America.UTF8 was all the documentation stated as being required for setup.
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