Release 2.4
A63820-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 ConText Cartridge Administrator's Guide Release 2.4 A63820-01 |
|
This appendix contains detailed information about the database tables and Oracle indexes that are created by ConText when a text or theme index is created for a column.
The following topics are covered in this appendix:
ConText index tables are created automatically by ConText during text and theme indexing. The five digit number nnnnn is the identifier for the policy that owns the index. Each of the ConText index tables for a policy has the same five digit identifier.
This is the main table of a ConText index. It stores each indexed token from the text column, as well as a reference to the documents in which the word occurs and the location of each occurrence.
The n appended to the end of the table name is an internal identifier (value of 1 or 2) which ConText uses to prevent table name collisions when two-table compaction or two-table combined real deletion and compaction are used to optimize the ConText index for a table.
|
Note: The appended n is transparent to users because a synonym called DR_nnnnn_I1T, which points to DR_nnnnn_I1Tn, is automatically created/updated after two-table index optimization. For more information about two-table index optimization, see "Index Optimization" in Chapter 6, "Text Concepts". |
This internal table maps the textkey for each indexed document to a document identifier (DOCID). ConText indexes use DOCIDs internally to identify the documents in which indexed words occur. ConText indexes also use DOCIDs to track documents for which DML has occurred (i.e. deletion or modification).
| Name | Type | Description |
|---|---|---|
|
TEXTKEY |
VARCHAR2(256) |
ID for document in text table |
|
DOCID |
NUMBER(38) |
ID for document in index |
This internal table generates the unique document IDs (DOCID) used in a ConText index. It also stores the next available DOCID for use in the index.
This internal table is used to optimize DOCID resolution during queries. It stores the DOCIDs of documents that have been modified or deleted from the text table.
| Name | Type | Description |
|---|---|---|
|
FIRST_DOC |
NUMBER(38) |
Internal use only |
|
IDLIST |
LONG RAW |
Internal use only |
This internal table stores each word identified by the Soundex function and the groups to which the word belongs. This table is only created when you index a table with a policy that includes Soundex (soundex_at_index attribute enabled for the GENERIC WORD LIST Tile).
The Oracle indexes for a ConText index are created automatically by ConText after the index tables have been populated with the ConText index information.
ConText creates a total of five Oracle indexes for the three ConText index tables created during indexing. The Oracle indexes follow the naming conventions used to name the index tables, where the five digit number nnnnn is the internal identifier for the policy that owns the ConText index.
| ConText Index Table | Oracle Index |
|---|---|
|
DR_nnnnn_I1Tn |
DR_nnnnn_I1In |
|
DR_nnnnn_KTB |
DR_nnnnn_KID |
|
|
DR_nnnnn_KIK |
|
|
DR_nnnnn_KSQ |
|
DR_nnnnn_LST |
DR_nnnnn_LIX |
The SQR table is created automatically by ConText during text and theme indexing of a text column; however, the table is not populated until a stored query expression (SQE) is created (stored) for the policy of the text column.
The five digit number nnnnn is the identifier for the policy that owns the SQE.
|
Note: The SQR table is an internal table and should not be accessed directly. To perform administration tasks on an SQE, use the CTX_QUERY package or the System Administration tool. For more information about creating SQEs and using the CTX_QUERY package, see Oracle8 ConText Cartridge Application Developer's Guide. |
This internal table stores the results of an SQE. The definition of the SQE is stored in an internal table owned by CTXSYS.
During creation of the SQR table, an Oracle index, DR_nnnnn_SRI, is created on the table.
