About Auditing Oracle Text DR$ Index Tables

You can audit actions on Oracle Text index tables (DR$index), which can contain sensitive data.

The audit can capture actions that a user will perform on the index table. You should create a unified audit policy for the table that contains the sensitive data, as well as the Oracle Text index table for the column containing the sensitive data. Oracle Text index table names start with a prefix of DR$.

Index tables that do not contain customer data do not need audit policies. Tables that you should consider creating audit policies for include the following:

• DR$index_name$I (the main table that all users should protect)

• DR$index_name$G (if present, stage_itab preference)

• DR$index_name$P (if present, prefix index preference)

• DR$index_name$O (if present, forward index preference)

• DR$index_name$D (if present, save copy preference)

• DR$index_name$KG (if present, wildcard index preference)

• DR$index_name$SN, $ST, $SD, $SV, $STZ (if present, optimize_for_search SDATA preference )

• DR$index_name$S (if present, optimize_for_sort SDATA preference)

You can find associated indexes with a particular table by querying the OBJECT_TYPE column of the ALL_OBJECTS data dictionary view. To find a list of internal Oracle Text tables, query the USER_TABLES table, in the schema where index was created. For example, for an index named my_index:

SELECT TABLE_NAME FROM USER_TABLES WHERE TABLE_NAME LIKE 'DR$my_index%';