This content has been marked as final. Show 6 replies
here are a number of issues to consider when installing Content Server for international use. How you go about setting up your configuration depends on the database you will be using and the database character set.
During the installation of Content Server, if you select to have the installation create your database tables you are given a choice for "Unicode". Selecting Unicode will branch the installation to create database tables that use the "Unicode database scripts" and create NVARCHAR2/NVARCHAR fields, whereas the "standard database scripts" are used to create tables with VARCHAR2/VARCHAR fields. This difference can lead to post installation errors if your database encoding is not properly matched.
You should not select the "Unicode" option when running the installation scripts and using an Oracle database.
To setup an international environment, instead of using "Unicode", you will want to create an Oracle database that uses AL32UTF8 (the standard UTF-8 character encoding) and use the "standard database scripts" to create the tables.
To do this you will need to set your Oracle database encoding in advance of the Content Server installation. When you have an AL32UTF8 database you can install Content Server using the "standard database scripts" (not Unicode database scripts). See below in this article for more information on how to identify the encoding of your database.
Thanks for the reply.
Can you please provide me with link of Article.
while searching the characters for language in Oracle UCM CS other than English for metadata and full text search, it does not show the results.
So is there issue with Unicode being set to false in Oracle UCM or there is something else that i need to look into for?
I got to know that to update encoding in Oracle DB the following command is executed to set encoding to AL32UTF8:
ALTER DATABASE CHARACTER SET AL32UTF8
But since currently we have WE8MSWIN1252 encoding set for Oracle DB, it gives me the below error:
ORA-12712: new character set must be a superset of old character set
What could be the way to update the Encoding for Oracle to AL32UTF8?