RE: strategies for optimizing 'like' operations
Date: Mon, 10 Mar 2008 20:47:24 +0900
Message-ID: <007201c882a4$8479c780$0a00a8c0@dell600m>
Oracle 10 alleviates that restriction (ie you can refresh "on commit" in
effect, or even as part of the same transaction I think), but the same old
issue of: more frequent refresh = bigger text index can still rear its head.
Cheers
Connor
-----Original Message-----
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org]
On Behalf Of Rich Jesse
Sent: Saturday, 8 March 2008 4:36 AM
To: oracle-l_at_freelists.org
Subject: RE: strategies for optimizing 'like' operations
The index must indeed be maintained, but this can be done with a DBMS job (or Scheduler job). If memory serves, the maintenance job was created automagically as a DBMS job in 9iR2 under the CTXSYS account.
[snip]
Enjoy!
Rich
> The problem with oracle text as I understand it is that the index must
> be manually maintained.
>
> Our users have an expectation of immediate availability through the
> search.
>
> Thanks for the suggestion!
-- http://www.freelists.org/webpage/oracle-l -- http://www.freelists.org/webpage/oracle-lReceived on Mon Mar 10 2008 - 06:47:24 CDT