Re: NLS_SORT different than BINARY_CI (604 Views)
Reply
Advisor
Posts: 31
Registered: ‎10-04-2007
Message 1 of 4 (627 Views)

NLS_SORT different than BINARY_CI

We are trying to support sort based on Turkish Character set. When we defined in ORACLE 11.2 parameters NLS_SORT= TURKISH_CI there is a phrase in log states that no other NLS_SORT is supported than BINARY_CI :

NLS_SORT = BINARY_CI

NLS_COMP = LINGUISTIC

 

Any help is depply appriciated.

 

sm.log db outputs:

  7861(  7919) 10/14/2011 12:39:59  RTE I Oracle server settings for language, territory and character set: AMERICAN_AMERICA.AL32UTF8 (AL16UTF16)

  7861(  7919) 10/14/2011 12:39:59  RTE I OCI Client settings for language, territory and character set: TURKISH_TURKEY.AL32UTF8 (UTF16)

  7861(  7919) 10/14/2011 12:39:59  RTE I Oracle instance setting for NLS_SORT is set to BINARY_CI

  7861(  7919) 10/14/2011 12:39:59  RTE I Oracle instance setting for NLS_COMP is set to LINGUISTIC

Honored Contributor
Posts: 989
Registered: ‎02-22-2011
Message 2 of 4 (624 Views)

Re: NLS_SORT different than BINARY_CI

This is likely due to the way that Service Manager implemented case-insensitivity support for Oracle.

 

Excerpt from the SM Case-Insensitive Oracle document:

You must meet the following requirements in order to use case-insensitive Oracle with Service Manager:

1.  NLS_SORT=BINARY_CI and NLS_COMP=LINGUISTIC must be set in the Oracle Instance level.

  –  If these values are set as given above, Service Manager will issue an ALTER SESSION statement
     to match the NLS_SORT and NLS_COMP session parameter with the NLS_SORT and NLS_COMP
     instance parameter.

  –  If these values are not set or are different from the given values, Service Manager will treat it as
     case-sensitive Oracle and issue an ALTER SESSION statement to modify those parameters to be
     NLS_SORT=BINARY and NLS_COMP=BINARY.

     This ensures that all Service Manager server processes within a horizontal or vertical scaling
     group have consistent Oracle case-sensitivity settings.

Advisor
Posts: 31
Registered: ‎10-04-2007
Message 3 of 4 (619 Views)

Re: NLS_SORT different than BINARY_CI

thanks m,

 

we achived incase sensivity but customer required sorting based on turkish character sequance which was not possible with steps in oracle incasensitive document.

 

Regards,

Sadun

Advisor
Posts: 31
Registered: ‎10-04-2007
Message 4 of 4 (604 Views)

Re: NLS_SORT different than BINARY_CI

Non-English language characters are not sorted correctly Customer symptom

Text fields with non-ASCII characters are not sorting according to the local language conventions.

Fix Version

Release Status
7.10    Closed-No Change
7.11    Closed-No Change
9.21    Closed-No Change
9.30    Investigation
In the queue for consideration in a future release, patch or hotfix

Internal Change Request

QCCR1E49699

Internal Legacy ID:

vfy553952

http://support.openview.hp.com/selfsolve/document/KM824012

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.