No pending rows using triggers on Text indexed columns with MULTI_COLUMN_DATASTORE or USER_DATASTORE to bring in the various columns for indexing
(Doc ID 1613741.1)
Last updated on MARCH 03, 2019
Applies to:Oracle Text - Version 126.96.36.199 and later
Information in this document applies to any platform.
We have a Oracle Text CONTEXT index on multiple columns using a MULTI_COLUMN_DATASTORE or USER_DATASTORE to bring in the various columns for indexing with a BEFORE ROW trigger to propagate changes and update the Text index if any of the columns (other than the one on which the index is based) gets updated and add them to the pending table for indexing.
Although the trigger works and fires it does not add any entries in pending table or ctx_user_pending view.
This works well, but the kernel doesn't know which columns you've used in the index. As far as the kernel is concerned, you have created the index on a specific column, and it will only update the index when the contents of that column change.
- A fresh 12gR1 database with Text indexes using a MULTI_COLUMN_DATASTORE or USER_DATASTORE to bring in the various columns for indexing with a BEFORE ROW trigger
- Database has been upgraded from 188.8.131.52 to 184.108.40.206.0
- <Patch 14155722> has been applied on affected database
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document