Indexing the Text
Once your text is loaded in a text column, you can create a Text index.
General Defaults for All Languages
When you create an index and accept all the default values for options, the
system does the following for all languages:
- Assumes that the text to be indexed is stored directly in a text column. The
text column can be of type CLOB, BLOB, BFILE, VARCHAR2, or CHAR. The columns
types LONG and LONG RAW are supported for migrating Oracle7 systems to Oracle8i.
The column types NCLOB, DATE and NUMBER cannot be indexed
- Detects the column type and uses filtering for binary column types. Most
document formats are supported for filtering. If your column is plain text, the
system does not use filtering.
Note: For document filtering to work correctly in your system, you must ensure
that your environment is set up correctly to support the Inso filter. To learn
more about configuring your environment to use the Inso filter, see the Oracle interMedia Text User's Guide and Reference.
- Assumes the language of text to index is the language you specify in your
database setup.
- Uses the default stoplist for the language you specify in your database setup.
Stoplists identify the words (stop words) that the system ignores during indexing.
- Enables fuzzy and stemming queries for your language, if this feature is
available for your language.
Of course, you can change the default indexing behavior by creating your own
preferences and specifying these custom preferences when you create the index.
Language-Specific Defaults
English:
In addition to the general defaults, the system enables the following option
for English language text:
- Indexes document theme information. When theme information is indexed, ABOUT
queries are more precise.
Languages other than English:
- By default, the following features are enabled:
- Case-sensitive indexing is enabled for German.
- Composite indexing is enabled for German and Dutch.
- Alternate spelling is enabled for German, Dutch, and Swedish
See also the Lexer options.
Index Maintenance
Index maintenance is necessary after your application inserts, updates, or
deletes documents in your base table.
If the base table is static (that is, you do no updating, inserting or
deleting of documents after your initial index), you do not need to maintain the
index. However, if you perform DML (inserts, updates, or deletes) on the base table,
you must update the index.
You can synchronize the index manually with ALTER INDEX. You can also run the
ctxsrv server in the background, which synchronizes the index automatically at
regular intervals.
See also: Main topics (outline), Getting started with interMedia Text