Values This column is Idoc scriptable. This column can only be defined when AllowMultiple This column indicates whether the defined index is used with

4-24 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server For example, if the WHERE clause contains the following condition using the PK_ Revisions index would be a very valuable hint to include in an optimized query: Revisions.dID = 3 However, if the WHERE clause contains the following condition then using the PK_ Revisions index would not be useful: Revisions.dID 3

4.2.5.8.5 Index This column identifies the specific index to use in the optimized query

if the condition meets the hint rule requirements.

4.2.5.8.6 Order This column contains the preferred order to use when the rule is

included in the Hint Rules Table. The highest ordered rules in a query are given precedence when deciding which hint to use. The order values include: ■ 5 : This value indicates that the specified index is unique or does not match more than 50 rows for any value. For example, specifying dID with the Revisions, Documents, or DocMeta tables. ■

4: This value indicates that the specified index should be somewhat less selective.

The specified value should typically match a few rows and, at the very most, several hundred rows. For example, specifying dDocTitle with the Revisions table. ■

3: This value indicates that the specified index matches less than a thousand rows.

For example, specifying dInDate or dOutDate. ■

2: This value indicates that the specified index matches less than ten thousand

rows. ■

1: This value indicates that the specified index matches more than ten thousand

rows.

4.2.5.8.7 Values This column is Idoc scriptable. This column can only be defined when

the Operators column value is one of the following: ■ in or notIn: When you use either of these operators, the value should be a comma-delimited list enclosed in parenthesis. ■ range : When you use this operator, the value must use one of the following formats: – Format 1: [lowValue],range[,highDateValue] Examples of acceptable values include: Y, O ,7d {ts 2004-12-11 12:03:23.000}, 2d, dateCurrent – Format 2: [d|h] For example, a range of five days is 5d and seven hours is 7h. Managing System Settings 4-25 The following use cases demonstrate how this column provides additional flexibility to the hint rules: ■ Use Case 1: State or Status Table Columns Table columns that indicate a state or status such as dReleaseState or dStatus are biased regarding the finished states. For example, dReleaseState is predisposed for Y released or O old version. Likewise, dStatus is predisposed for RELEASED. Therefore, in WHERE clauses, conditions such as dReleaseState = Y or dStatus = RELEASED match the majority of rows in the Revisions table. Thus, indexes for these two columns are almost useless. Conversely, the condition dReleaseState = N new, not yet indexed matches only a few rows. Consequently, indexes on this column would be very helpful. ■ Use Case 2: Date or Number Table Columns Table columns that indicate a date or number exhibit similar behavior to state or status. For example, the condition dInDate dateCurrent matches most of the table rows and makes indexes on this field irrelevant. However, the combined conditions dInDate dateCurrent AND dInDate dateCurrent-1 usually match only a small set of rows and would benefit from using the corresponding index as a hint.

4.2.5.8.8 AllowMultiple This column indicates whether the defined index is used with

other indexes. In Oracle, only the bitmap index can be combined.

4.2.5.8.9 Disabled This column indicates whether a hint rule has been disabled. Any