Why do we need to use only AL32UTF8 character set while creating a database for CLM in oracle?
CLM help page on "setting up a Oracle db" I see IBM have specified that one should use AL32UTF8 character set while creating a database for CLM in oracle.
Is there any specific reason for this?
Thanks
Nicky C.J
One answer
Setting character set to Unicode (AL32UTF8) enables you to store multiple language groups.
See http://www-01.ibm.com/support/knowledgecenter/SSYMRC_4.0.6/com.ibm.jazz.install.doc/topics/t_s_server_installation_setup_oracle.html for more information about creating Oracle databases and tablespace.
Thanks,
Michael
Comments
Krzysztof Kaźmierczyk
May 29 '14, 12:02 p.m.Hi Nicky,
I am not sure about the answer, anyway this will be the first thing that support checks if you have any problem with database. Anyway what is the reason you are asking? Do you have already database set in different encoding?
Krzysztof Kaźmierczyk
May 29 '14, 12:03 p.m.Hi Nicky,
I am not sure about the answer, anyway this will be the first thing that support checks if you have any problem with database. Anyway what is the reason you are asking? Do you have already database set in different encoding?
nicky john
May 30 '14, 12:55 a.m.Hi Krzysztof,
Krzysztof Kaźmierczyk
May 30 '14, 2:29 a.m.Hi Nicky,
How you are going to integrate CQ with RRC? Do you use information from infocenter?
Also can you show us the error you have?
nicky john
May 30 '14, 5:51 a.m.i am not able to upload the snapshot.
anyways i am integrating using the OSLC method.
Please follow the below link to view the method i am using for the integration.
CQ_RRC_integration.
Krzysztof Kaźmierczyk
May 30 '14, 7:34 a.m.Hi Nicky,
It is really weird for me that wrong database encoding has caused issues with OSLC. It is potential candidate for a defect if it is true. What is exactly error message you see?
nicky john
May 30 '14, 7:50 a.m.Hi Krzysztof,
Given below is the error messsage that appears while trying to link CQ records to RRC requirements.
CRMMD1785E The field "oslcl_label" contains characters that are not supported by the data code page, "20127 (US-ASCII)". The following characters are invalid:
at 10
at 28
at 33
at 42
at 47
CRMMD1792E There are 2 additional invalid characters in this field.
nicky john
May 30 '14, 7:50 a.m.Details
CRVAP0075E After completion of the 'ServerPropPatch' operation, not all resources were delivered as requested. CRVSV0187E Record has invalid field values. CRVAP0290E CRMMD1785E The field "oslcl_label" contains characters that are not supported by the data code page, "20127 (US-ASCII)". The following characters are invalid: at 10 at 28 at 33 at 42 at 47 CRMMD1792E There are 2 additional invalid characters in this field.