Hi!

This parameter changes the search behavior when using an Oracle DB. If you set this parameter to ‘N’ all the search fields become case-sensitive (only the exact matches will be returned). By that you could gain a bit more performance when searching because you will receive a smaller result set. However, your system users should be made aware how to correctly search.

Best regards
Roman

Thanks for the quick response ​@roklde  . Now I got it. so, this App param will be useful only when FSM Application installed with Oracle database. 

Correct.  Also whilst using Oracle with the flag not set correct you will likely see some performance issues from the UI screen in particular as the use of indexes changes, and forces the search to ‘UPPER’ to avoid the case sensitivity.

Thanks ​@nickz. could you please help me here. So currently we are using Oracle database as backend. what value needs to be set on this app param
ORACLE_MIXED_CASE_SEARCH_ENABLED to improve the performance?

You want it set to ‘N’.  If you are changing the setting then you need to do some tests 1st, as the way the system will work with searches with lowercase letters will have changed.  Mostly the codes you have will be uppercase anyway….but if you have any lowercase or users that search with lowercase assuming the system will match to uppercase will see a change as it will no longer do it…..BUT the search should improve immediately.  So don’t just change it in a production environment.