Tune DBMS_LOB.INSTR , or Overload to Support CTX Indexes?
We have a commercial app, BMC Remedy, which has forms with CLOB fields like one labeled "Details". Users like to search where details is like 'Switch' or something. Remedy builds the SQL and we have no control over such. One or 2 of these searches and the database is at its knees (about 100,000 rows). After some tracing, I see that Remedy is running where dbms_lob.instr(.....'Switch') > 0, so as I thought, a Context Index provides no relief. Basically BMC wants one to buy their Text Search engine, and we may, but not until next year. Users are used