Page History
In OracleText, a full-text index can be configured to synchronize manually, at regular intervals or on commit. By default, the Blueriq full-text index on aggregates and documents is synchronized every hour. To change this behavior, the index needs to be rebuilt with different parameters.
| UI Text Box | type |
|---|
| Note |
Always consult the documentation of your particular Oracle database version. The following examples illustrate how to change the synchronization behavior without setting additional options such as whether the index is rebuilt online or offline, whether it is rebuilt in parallel, etc. |
| UI Text Box |
| Note |
|---|
Please note that each index synchronization increases the index fragmentation, degrading search performance over time. Consult the the How to maintain full-text search performance article article to learn more about index fragmentation and how to maintain the full-text index. |
| Tip | |||||
|---|---|---|---|---|---|
We advice to rebuild the index after every change. This can be done using the following script:
|
Changing index synchronization to manual
...
The "1/24" expression represents one twentyfourth of a day (one hour). The expression uses Oracle's job scheduling syntax.
| UI Text Box | type | note
|---|
| Info |
When using this synchronization method, the database user needs to have the the |
Changing index synchronization to on commit
...
When this synchronization method is used, the index is updated every time an aggregate or document is created, modified or deleted.
| UI Expand | ||
|---|---|---|
| showLabels | false | |
| max | 5 | |
| spaces | BKB |
|
| Content by Label | modified | |
| showSpace | false | |
| reverse | true | |
| type | page | |
| labels | search | |
| UI Expand | ||
| ||
...
Overview
Content Tools