Re: Case insensitive searches

    We did the same thing as Martin, and it worked OK.

    The only issue we had was with our logical standby DB. Since many of the indexes were converted to FBI on the primary DB, it caused tables scans on the LSB, and performance was unacceptable. After trying a few things, we replaced the LSB with an Active dataguard database, and the queries worked as expected. It was a costly solution to the problem though.

• Original Message ----- From: "Martin Klier" <usn_at_usn-it.de> To: <rjjanuary_at_multiservice.com> Cc: "oracle-l" <oracle-l_at_freelists.org> Sent: Tuesday, March 18, 2014 8:28 AM Subject: Re: Case insensitive searches

> Hi Ryan,
>
> we are running more than 50 projects on 11.2.x with NLS_SORT set to
> BINARY_CI and NLS_COMP to LINGUISTIC.
>
> We do two things:
> * both parameters are only set on session level for the app users and
> NOT for SYSTEM or the dictionary owner.
> * all VARCHAR field indexes are changed to function based:
> NLSSORT(MY_TEXT_FIELD, 'NLS_SORT=BINARY_CI')
> Because this function is what Oracle wraps around any string search when
> the mentioned parameters are set.
>
> Hope this helps
> Martin Klier
>
> Am 17.03.2014 23:02, schrieb Ryan January:
>> to set NLS_SORT to BINARY_CI and NLS_COMP to LINGUISTIC
>
> --
> Usn's IT Blog for Oracle and Linux
> http://www.usn-it.de
>
> performing databases
> Your reliability. Our concern.
> http://www.performing-databases.com
>
> --
> http://www.freelists.org/webpage/oracle-l
>
>

--
http://www.freelists.org/webpage/oracle-l