This won't be much help to you (except from an informational sharing
perspective) but we ran into similar performance issues as part of a
Sybase -> Oracle conversion.  Never did get a resolution after working
with both Oracle and Remedy.  In the end we posponed our db conversion
to coincide with our apps upgrade (5.5 -> 7.0).  We will be deploying
the new apps case sensitive. 


-- 

Chris Danaceau
703-833-2459

The electronic mail message you have received and any files transmitted
with it are confidential and solely for the intended addressee(s)'s
attention. Do not divulge, copy, forward, or use the contents,
attachments, or information without permission of Fannie Mae.
Information contained in this message is provided solely for the purpose
stated in the message or its attachment(s) and must not be disclosed to
any third party or used for any other purpose without consent of Fannie
Mae. If you have received this message and/or any files transmitted with
it in error, please delete them from your system, destroy any hard
copies of them, and contact the sender.     



-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Albert Bihler
Sent: Friday, February 09, 2007 11:10 AM
To: [email protected]
Subject: Oracle case insensitivity features and ARS 7

Hi list,

we are currently migrating a ARS application from Sybase to Oracle
10gR2. A big problem is that Oracle by default is case sensitive and
users are used to execute searches without caring about the case.

We applied KM-000000012018 without great success.

We also played around with the following Oracle options:
ALTER SESSION SET NLS_COMP=LINGUISTIC;
ALTER SESSION SET NLS_SORT=BINARY_CI;
and function based indexes to get Oracle to work case insensitive. The
problem is that the indexes created by ARS won't work and performance
would be very poor.

Does anybody have a performant real live environment with ARS using
Oracle case insensitivity options and would like to share the details?

Remedy support says this is a limitation from Oracle.

Oracle support states that everything works great if you use
nlssort-funcion in the where clause of your SQL statement. Unfortunately
ARS doesn't issue SQL commands of that style.

ARS 7.0.0
Oracle 10gR2
Solaris 10


Kind regards,
Albert

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to