Case insensitive searching for criteria "All metadata"

If I'm specifically searching in (for example) keywords, then the search is case insensitive. However, if I'm searching "All metadata" then the search is case sensitive. I don't know if this is a bug or a feature (seems like a bug to me), but I'd really prefer it to remain case insensitive for this search criterion as well.
While I'm at it, I'd like to be able to search the IPTC headline.
Bart

I'll second that request on both counts! In fact, I'd like to see the ability to search based on any XMP field.
-Andrew

Similar Messages

Case Insensitive Search for the Dashboard Prompt Filter

Hi,
Can anyone help me, how to make dashboard propmt filter to be case insensitive, as of now dashboard propmts are case sensitive by default. How can we achieve this? Any help on this will be appreciated. TIA

I wonder if it can be done. don't know if there's any work-around for it.
Generally, the data that is imported into the SOD system is case sensitive hence the field on which you base your prompt will also be case sensitive.

Case-insensitive Search with Search Form

I am using a Search Form with a UIX Page. One of the issue that need to be resolved is to be able to do case-insensitive search for text information stored in some database columns. Please advise me how to implement case_insensitive search with JDeveloper's Search Form.
Thanks in advance,

Hi Qian,
This article (below) by Steve Muench explains how you can customize Query by example behaviour of ADF BCs and if you really want, how to create your own ViewCriteriaAdapter (but you don't have to go quite that far - luckily :) ).
http://radio.weblogs.com/0118231/2005/02/10.html#a492
Here is what I did. I implemented the following method in my base view object class (MyBaseViewObject). Note that this code is based on a piece of code that Steve posted on his blog (http://radio.weblogs.com/0118231/stories/2003/07/11/implementingAViewCriteriaAdapterToCustomizeQueryByExampleFunctionality.html); originally an example about creating your own ViewCriteriaAdapter.
Since applyViewCriteria(oracle.jbo.ViewCriteria) is used by the query-by-example mechanism you're able to "intercept" the ViewCriteria on "it's way in". After that the standard ViewCriteria does it's job as ususal and generated the where clause when required.
public void applyViewCriteria(ViewCriteria vc)
     if( null == vc || vc.size() == 0 ) super.applyViewCriteria(vc);
     ViewCriteriaRow criteriaRow = (ViewCriteriaRow)vc.first();
     StructureDef def = criteriaRow.getStructureDef();
     AttributeDef[] attrs = def.getAttributeDefs();
     System.out.println(getClass().getName() + ": applyViewCriteria()");
     boolean bFirst = true;
     do{
       if(vc.hasNext() && !bFirst) criteriaRow = (ViewCriteriaRow)vc.next();
       criteriaRow.setUpperColumns(true);
       for (int j = 0, attrCt = attrs.length; j < attrCt; j++)
         String criteriaAttrVal = ((String)criteriaRow.getAttribute(j));
         if (criteriaAttrVal != null && !criteriaAttrVal.equals("") && !JboTypeMap.isNumericType(attrs[j].getSQLType()))
          criteriaRow.setAttribute(j,criteriaAttrVal.toUpperCase());
       bFirst=false;
     }while(vc.hasNext());
     super.applyViewCriteria(vc);
NOTE that doing this makes all your views case insensitive (to vc search) you may want to implement more functionality in your base view object to set whether a view is in case insensitive mode or not.
ALSO that flag will not be passivated (if I remember correctly - someone correct me if I'm wrong) so you'll have to add that flag to the passivated data.
Cheers!
Sacha

Case insensitive searching in Interactive Page

Hi all,
I am currently working on the interactive report, and wondering is it possible to perform case insensitive search for the data in the textbox besides the magnifying class.
By the default, the system uses "=" for searching. I tried the searching option using "contains", and it would be able to search the content in uppercase and lower case scenario. Is it possible to make "contains" as the default?
Thanks,
Thomas.

By the default, the system uses "=" for searching.I get "Row text contains..." as the filter when entering text directly into the default search box. Perhaps you are working with a saved report?
There's a way to make all IR comparisons case insensitive. See this <a ref="http://apex.oracle.com/pls/otn/f?p=34839:18">example of case/accent insensitive search</a> on a standard report.
That code can't be put in a Before Regions process as described to work with IRs as page processes are not executed by the AJAX call that refreshes the report. However, IR refreshes do run the Virtual Private Database PL/SQL call defined in the application security attributes, so putting the NLS modification code there will work.
Go to Application > Shared Components > Edit Security Attribute | Virtual Private Database (VPD), and make the call from there. Due to the specific requirements of the code that has to be called from here when used for security purposes, this is probably best done by setting this up to make separate calls to packages defined outside APEX, one to handle any actual VPD and other security-related details, and others to orchestrate any other code that has to be run. (For example, in this case it may not be desired to alter the NLS environment on every page, so the program could take a parameter specifying the current page and apply the ALTER SESSION conditionally on this.)

Support for Case Insensitive Search and IN Clause in Open SQL

Hi,
I have some doubts regarding Open SQL:
- Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
- Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
I have checked the [Open SQL Grammer |http://help.sap.com/saphelp_nwce711/helpdata/en/9b/f46cabaa874bc9a82234e8cf1d0696/frameset.htm]also, but nothing found there.
Thanks,
Piyush
P.S I didn't find any other appropriate place to post this thread, let me know the correct categorization of Open SQL in case its wrong.

No cross posting.
Read the "Rules of Engagement"
Regards
Juan

Case-Insensitive Searching on Content Server

Hello everyone,
I have a Content Server 10gr3 using an Oracle 11g DB. All of my searches are case sensitive, but we need case-insensitive searching. I've tried changing the DatabasePreserveCase variable in the config.cfg to 1, 0, true, and false, rebuilt the indexes in between each reboot (not sure if that's necessary or not), tried checking in new documents after making the changes and searching for those, but no matter, searches stay case sensitive.
We have another UCM install running on a 10.2.0.3.0 DB, and case insensitivity works on that Content Server with DatabasePreserveCase=1.
What could we be doing wrong? I've found several documents which have stated that case-insensitivity is impossible with an Oracle DB, but I think those are all old and from before Oracle's acquisition of the product (and obviously it is possible, since we have another install with it working).
Thanks in advance for any help you can give!

I'm not quite sure what you mean by Search Engine... we simply installed the Oracle 11g Database, then installed Content Server and configured it to run using that database. We haven't done anything with full-text search.
Edit: Do you mean the SearchIndexerEngineName value in the config file? It's DATABASE.METADATA, though at some point we also need to get full-text up and running which to my understanding requires it to be DATABASE.FULLTEXT.
As to the OracleCaseInsensitiveSearch component, where can I find it? Google shows up nothing, and MetaLink has one page saying that it exists but nothing more...
Message was edited by:
user573973

GetOrdinal of AseDataReader Class is not doing case-insensitive search

hi,
I am working on 12.5.4 version of sybase ASE.I am using 'Sybase.AdoNet2.AseClient.dll' to connect with database. I am using GetOrdinal method of ASEDatareader class (that as per documentation performs a case-sensitive lookup first. If it fails , a second search that is case-insensitive occurs) but in my case it is not performing case-insensitive search. I am attaching the document for your reference.
http://infocenter.sybase.com/help/index.jsp?topic=/com.infocenter.dc20066.1570100/doc/html/san1364409576274.html
Thanks,
Raman

Hi Monica,
Another thing you want to make sure is on your ASE that the oledb/adonet MDA scripts are up to snuff. Some of our fixes in the driver are in this.
If you login into the ASE and get the output of sp_version.
You should get something like this:
OLEDB MDA Scripts
         15.7.0.1250.1013/Wed Feb 19 UTC 00:28:47 2014
The ado.net driver and the older oledb driver use some specific MDA scripts on the ASE.
Read the coverletter of the SDK (Software Developers Kit for ASE). It explains how to update the MDA scripts. They are on the client side $sybase\ADONET\sp.
So where you downloaded the SDK you want to click Info then look for the README.
This is all the SDKs:
* Updating the metadata stored procedures required by ODBC, OLE DB and
jConnect Drivers on Adaptive Server Enterprise
Certain new features and bug fixes in ODBC, OLE DB and jConnect drivers
require you to modify the metadata stored procedures in Adaptive Server.
These stored procedures may not be up-to-date on your host ASE server due
to various reasons.
If the metadata stored procedures are outdated, you may not be able to use
some of the fixes that are implemented in this SP/ESD, so you will need to
manually install the updated metadata stored procedures.
To update the metadata stored procedures in Adaptive Server, first determine
the version of the meta-data scripts installed on the ASE. To do so, execute
the following command:
sp_version
go
The version number of the ODBC, OLE DB and jConnect meta-data scripts will
be displayed.
Review the version number column and compare it against the version of the
driver being used.
If the metadata scripts are outdated, the version installed will be older
than the driver build number or you will encounter one of the following:
- stored procedure sp_version is not found
- the stored procedure output does not print a row for the driver
The updated scripts are included with the drivers and can be installed as
follows:
For ODBC & OLE DB:
- Go the "sp" directory under the ODBC/OLE DB installation directory
- Execute the install_odbc_sprocs script for the ODBC Driver and
install_oledb_sprocs script for OLE DB Provider.
Syntax for using the script is:
        install_[odbc/olebd]_sprocs <ServerName> <username> [<password>]
         where <ServerName> is the name of the Adaptive Server
             <username> is the username to connect to the server
             [<password>] is the password the username
             (don’t supply this for null password)
For jConnect:
- Go to the "sp" directory under the jConnect installation directory. Based
on your host ASE server version, choose the appropriate SQL script.
- Use isql or another tool of your choice to execute the selected script.
This will install the current meta-data stored procedures.
Thanks,
Dawn

No case insensitive search in RAPID applications

Hey experts,
we have created a rapid application with non-key field "description". The rapid application is generating a search criteria "description", so far so good.
Now the issue is that only case sensitive search is possible for this field.
Any suggestions how to make the search case insensitive for this field or in general for all text fields?
Thanks,
Wladimir

Hello Wladimir.
Almost all of case insensitive searches in SAP CRM are done using dedicated "search" field (we're talking about classical DBs and not HANA and its capabilities). Which represents the desired field in uppercase in the same database table. Compare BUT000-NAME_LAST and BUT000-MC_NAME1, ADR6-SMTP_ADDR and ADR6-SMTP_SRCH fields pairs for example. So your description field should be programmatically converted to upper case and stored in another field. On which you should do the search.
Otherewise you should do a complete scan of database entries and compare pairs converted to the same case.

Error in a report after enabling case insensitive search in conn pool prop

Hi All,
I put the below code in connection pool's connection string to enable case insensitive search.
alter session set NLS_SORT=BINARY_CI
alter session set NLS_COMP=LINGUISTIC
After putting this code one of my report started giving the below error which was working fine otherwise.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. NQODBC SQL_STATE: HY000 nQSError: 10058 A general error has occurred. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16015 SQL statement execution failed. (HY000)
The report gives error for the below divide condition when I select a column from a different dimension (eg: region)
COUNT(DISTINCT RMA.RMA)/COUNT(DISTINCT User."User Name")
Can anyone please throw a light why this is happening.

Below is the SQL which is throwing error in OBIEE. It was working fine when I tried running it in toad:
select T1609.ATTRIB_05 as c1,
count(distinct T1609.ATTRIB_42) as c2,
TRUNC(T1159.FSCL_WEEK_START_DT) as c3
from
WC_DAY_D T1159 /* RMA_RECEIVED_DT(WC_DAY_D) */ ,
WC_RMA_D T571,
WC_FV_FA_D T1609,
WC_FV_FA_F T1679
where ( T571.ROW_WID = T1679.RMA_WID and T1159.ROW_WID = T1679.RMA_RECEIVED_WID and T1609.ROW_WID = T1679.FV_FA_WID and T1609.ATTRIB_39 <> 'FV' and (T571.STATUS_CD in ('2nd FA', '2nd FA Review', 'Closed')) and TRUNC(T1609.TODO_ACTL_END_DT) is not null and TRUNC(T1159.FSCL_WEEK_START_DT) between TIMESTAMP '2009-03-22 00:00:00' and TIMESTAMP '2009-04-12 00:00:00' )
group by T1609.ATTRIB_05, TRUNC(T1159.FSCL_WEEK_START_DT)
order by c3
-------------------- Query Status: Query Failed: [nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16015] SQL statement execution failed.

Case Insensitive Search coupled with "LIKE" operator.

Greetings All, I am running Oracle 11gR1 RAC patchet 25 on Windows X64.
This db supports and application that requires case insensitive searches.
Because there are a few entry points into the db I created an "after login" trigger:
CREATE OR REPLACE TRIGGER MyAppAfterLogon_TRGR
AFTER LOGON
ON DATABASE
DECLARE
vDDL VARCHAR2(200) := 'alter session set nls_comp=''linguistic''';
vDDL2 VARCHAR2(200) := 'alter session set nls_sort=''binary_ci''';
BEGIN
IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN
EXECUTE IMMEDIATE vDDL;
EXECUTE IMMEDIATE vDDL2;
END IF;
END MyAppAfterLogon_TRGR;
This ensures that everyone connecting to the DB via any mechanism will automatically have case insensitive searches.
Now, to optimize the know queries I created the standard index to support normal matching queries:
select * from MyTable where Name = 'STEVE';
The index looks like:
CREATE INDEX "CONTACT_IDX3 ON MYTABLE (NLSSORT("NAME",'nls_sort=''BINARY_CI'''))
This all works fine, no issues.
The problem is when I write a query that uses the "LIKE" operator:
select * from MyTable where Name like 'STEV%';
I get back the record set I expect. However, my index is not used? I can't for the life of me get this query to use an index.
The table has about 600,000 rows and I have run gather schema stats.
Does anyone know of any issues with case insensitive searches and the "LIKE" clause?
Any and all help would be appreciated.
L

I think there is issue with your logon trigger :
"IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN"
it should be :
IF UPPER(USER) = 'MYAPPUSER' OR UPPER(USER) = 'MYAPPREPORTINGUSER' THEN
because user name stored in Upper case. Check and try.
HTH
Girish Sharma

Case insensitive search in SE16

Hello Community,
We have a Z table which contains the field "filename," containing both upper & lowercase alphanumeric values.
I was surprised to find that it is not so easy to perform a case insensitive search against those field values using SE16.
It would be perfect if:
1. a search in SE16 for `file.txt` will find the results of all records related to the file "file.txt"
2. a search in SE16 for `FiLe.TxT` will also find all records related to the file "file.txt"
Can someone help me to accomplish this ?
Thanks!
Keith Helfrich

Hi everyone,
The goal is to perform a case insensitive search in SE16. Is there no way to do this ?
While there are a variety of work-arounds, for example : it is possible to store all the values in the table in UPPERCASE, these work-arounds do not solve our problem.
The values in the table need to be stored with the accurate case, exactly as the file is named at the UNIX level. Since UNIX is also case sensitive, we need to be accurate with the case when storing statistics data about the files.
Yet, when searching in SE16, it is problematic because we don't always know the correct case. For that reason, a case insensitive search is required.
This seems to be a very basic function that I am surprised SAP doesn't provide...

Case insensitive search and "IN" Clause in Open SQL

Hi,
I have some doubts regarding Open SQL:
- Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
- Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
I have checked the [Open SQL Grammer |http://help.sap.com/saphelp_nwce711/helpdata/en/9b/f46cabaa874bc9a82234e8cf1d0696/frameset.htm]also, but nothing found there.
Thanks,
Piyush
P.S I didn't find any other appropriate place to post this thread, let me know the correct categorization of Open SQL in case its wrong.

> I have some doubts regarding Open SQL:
I believe that you've questions and not doubts...
> - Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
Nope, there is nothing like that. By default all supported database use a bytewise equal operator - case insensitivness needs to be programmed by hand.
E.G. using UPPER(x)/LOWER(x) functions.
Be aware that this disables the possibilities of index usage.
> - Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
Yes, there is a restriction and it differes between the different DBMS.
Until recently you could have 2000 variables per statement with MaxDB.
The current versions of DBSL and MaxDB Kernel now support up to 10000 variables per statement.
Anyhow, in most cases, such a long in list can and should be avoided by using the FOR ALL ENTRIES construct. With this, the DBSL automatically splits the long IN list into smaller chunks and executes the statements several times.
This is invisible to the ABAP report - it just gets the result set as usual.
> P.S I didn't find any other appropriate place to post this thread, let me know the correct categorization of Open SQL in case its wrong.
I guess in anyone of the DB forums is Ok.
regards,
Lars

Case insensitive search working in dev but not in prod

Hello All,
I had set the CASE_SENSITIVE_CHARACTER_COMPARISON parameter as OFF in NQSConfig.ini file for enabling the case insensitive search in OBIEE.
This setup is letting me do the case insensitive search in Dev env but the same doesnt work in prod env. I tried pointing both prod and dev rpd to same prod db.
With same db also, case insensitive search doesnt work in prod env.
Any idea for which other configuration I can look for.
Thanks in advance.

Thanks Stijin. I had seen this post earlier. Case insensitive search works fine after setting the value for NLS_SORT and NLS_COMP in production RPD but the other report with distinct clause starts failing. Not sure about the reason.
Saw this comment from you in that post:
The only compromise solution we could find was to "cache" the column value we wanted to use in insensitive searches. These were mainly used in "show all choices" while setting prompts. Other than that there isn't much you can do in an Oracle database.
Can you please tell me how to implement the above.

WCC Case Insensitive Search

Hello everyone,
I am using OOTB DATABASE.METADATA as the search engine.
I wanted to know how to make it case insensitive search.
thanks

Hey Jiri,
thanks for the quick answer, I had to use Oracle Text Search.
to switch the search engine i added the following two entries in config.cfg
SearchIndexerEngineName=OracleTextSearch
MaxIndexableFileSize=0
bounce UCM and recreated indexes.
and i could make them case insensitive on WCC.
for WCCIMG i also had to make my applications full text before the searches were made case insensitive.
thanks

Possible to do case-insensitive searches?

G'day,
I was wondering if it's possible to do case-insensitive searches in oracle/HTMLDB?
I've tried what I thought would work
"select * from application where name like '%microsoft%'", this unfortunately doesn't return any records with a capital in it(eg "Microsoft").
If there is no way to do case-insensitive searches what is the best way around it?
Thanks
-Colin

Colin,
Yes it is possible to do case insensitive searches using SQL. Try, for example:
select * from application where upper(name) like '%ORACLE%'
The trick is to upper() both sides of the like operator.
Sergio

Case insensitive searching for criteria "All metadata"

Similar Messages

Maybe you are looking for