Oracle Files Administration Guide 9.0.3 Part Number A97358-01 |
|
| View PDF |
Oracle Files uses Oracle Text to facilitate full-text search and other advanced capabilities. The speed with which results are returned depends on several factors, including the quality of the Oracle Text index used with Oracle Files (IFS_TEXT), free space on the disk for objects required during the search, and other such details. In addition, the end user's experience of the "performance" of the search can depend on how much time you let elapse before an in-progress search times out.
This appendix provides information about how to maintain the Oracle Text index to ensure optimal Oracle Files performance, and includes these topics:
Previous names for Oracle Text include Oracle Context and Oracle interMedia Text. Many of the underlying indexes, views, tables, and various PL/SQL packages referred to in much of the administrator and application developer documentation still use Context or interMedia-related nomenclature. For example, the database schema that owns all Oracle Text objects, such as the indexes, is CTXSYS
.
For detailed information about Oracle Text, visit the Oracle Technology Network (http://otn.oracle.com/products/text/
).
Disk space for Oracle Text is divided among three distinct tablespaces:
Use this information to estimate and plan disk storage needs for your Oracle Files instance.
At the end of the configuration process for Oracle Files, the Configuration Assistant uses the SQL scripts shown in Table A-1 to create and populate the IFS_TEXT index.
These scripts are located in the \install\admin\sql
directory of the Oracle Collaboration Suite CD. If the installation process fails and you need to run these scripts manually, you should execute the scripts at a SQL*Plus prompt after logging on as the Oracle Files schema user (by default, IFSSYS
).
Oracle recommends using the PL/SQL packages provided with Oracle Text for maintaining the index. Unlike a regular database index, an Oracle Text index is not dynamically updated with each insert or update of information. Rather, you must refresh (or synchronize) the index periodically, using the Oracle Text stored procedure ctx_ddl.sync_index
.
The ctx_ddl.sync_index
procedure does not rebuild the entire index, but adds and delete records that have changed since the last synchronization. Since the changes are incremental, the more frequently you run this procedure, the faster it goes. However, over the course of time, the index can become fragmented, so a companion procedure (ctx_ddl.optimize_index
) is provided to optimize the index.
These two stored procedures to sync and optimize the IFS_TEXT index can be run automatically and simultaneously by configuring either the DBMS_JOB package or by using the job system of Oracle Enterprise Manager. See the Oracle9i Database Administrator's Guide for information.
ctx_ddl.sync_index(indexname);
ctx_ddl.optimize_index(indexname, 'FAST'|'FULL', maxtime );
Oracle Files provides some utility-type SQL scripts to facilitate interaction with Oracle Text (see Table A-2). Read each .sql
file for additional usage details. All scripts are available in:
$ORACLE_ HOME/9ifs/admin/sql
Oracle Files does not by default index every file that's moved into the system, but you can configure it to index any type of content you choose by designating the MIME type as "To Be Indexed" on the Create Format (or Format page, if it already exists).
For example, you may want to index all your .java source code files. To do so:
Enabling or disabling Oracle Text theme indexing causes all documents in Oracle Files to be re-indexed, which can take considerable time. To reduce the impact on your user community, be sure to perform either of these tasks after hours or when system usage is low.
Use SQL*Plus to connect as the Oracle Files schema user, and enter:
exec ctx_ddl.set_attribute('ifs_default_lexer', 'index_themes', 'yes'); exec ctx_ddl.set_attribute('ifs_default_lexer', 'theme_language','english'); alter index ifs_text rebuild parameters('replace lexer ifs_global_lexer');
In SQL*Plus, connect as the Oracle Files schema user, and enter:
exec ctx_ddl.set_attribute('ifs_default_lexer', 'index_themes', 'no'); alter index ifs_text rebuild parameters('replace lexer ifs_global_lexer');
The index is rebuilt and theme indexing is disabled.
For more information on themes, see Oracle Text Application Developer's Guide.
The IFS.SERVICE.SESSION.DefaultSearchTimeoutPeriod
service configuration parameter specifies the timeout period for a running search that has not yet returned results. The default setting for this parameter (in the default service configurations) is 60 seconds. Increase this value and users will wait longer than a minute before a search times out; decrease the value to shorten the time in which a running search will time out.
This section provides Oracle Text troubleshooting information.
Table A-3 Troubleshooting Oracle Text ProblemsProblem | Probable Cause | Corrective Action |
---|---|---|
Cannot search on document contents of any documents. |
Oracle Text server is not running. |
Start the database instance and make sure that Oracle Text is running. |
Server is slow only on content-based search activity. |
Probable cause #1: Oracle Text tablespaces are on the same disk as other database files. Probable cause #2: Oracle Text indexes have become fragmented. |
Move the Oracle Text tablespaces to other disks. See the Oracle Collaboration Suite Installation Guide. See the Oracle9i Administrator's Guide for more information on moving tablespaces. Regularly optimize the text Oracle index GLOBALINDEXEDBLOB_I (for new schemas). For more information, see "Optimize IFS_TEXT Index". |
Oracle Files rows never get processed and never leave the Oracle Text view ctx_user_pending. |
Oracle Files documents are corrupt or do not have the correct extension. |
|
Problem | Probable Cause | Corrective Action |
---|---|---|
Searching on the contents of new documents stops working. |
A recent document has caused Oracle Text server to fail. |
|
Oracle Files rows show up in the Oracle Text view ctx_user_index_errors. |
Oracle Files documents are corrupt or do not have the correct extension. |
|