What are the Ramifications of using a Non-AL32UTF8 Character set in the database, when installing WebCenter Content 11g/12c?
(Doc ID 1515287.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle WebCenter Content - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Note that this answer corresponds to the WebCenter Content Product 184.108.40.206.0 and above.
Example: When installing Oracle WebCenter Content 11g (220.127.116.11.0), According to Oracle documentation the database must meet the following requirements:
The version should be equal or superior than Database version 18.104.22.168.0.
The character set must be AL32UTF8. If you do not meet this requirement a warning appear.
The database instance being used for the installation is using the character set WE8ISO8859P15.
This is a consolidation database with many products, so it's not used just for Webcenter Content. IN this case, creating another instance is not an option.
The note "RCU Fails With Non-AL32UTF8 Character Set (Doc ID 1063712.1)" mentions that we could ignore the warning.
The question is: Is there any problem in ignoring the warning? What implications or impact might there be?
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