Understanding RTI Switch

High volume batch updates (for search definitions enabled for RTI) can cause a sudden spike in the number of entries to process in the RTI staging table added by the database trigger. This can cause the database table fragmentation to go high and potentially slow down overall system performance.

If you have large volumes of batch updates, the RTI process should be temporarily turned off and when the batch is complete, perform catch-up updates to indexed data using incremental indexing before resuming RTI.

RTI switch enables the application to turn OFF RTI before initializing high volume batch programs. It turns ON RTI during the incremental indexing time for a specific search definition.

Note:

If your updates are not available in the search results or analytics after the batch is complete, you have to manually run the incremental index to enable RTI.

Batch Process Minimum PeopleTools Release HCM Update Image

HRS_BTCH_LET

8.59.09

Image 45

HRS_CRJOB

8.59.09

Image 45

HRS_DUPE_MERGE

8.59.09

Image 45

HRS_RESLOAD

8.59.09

Image 45

HRS_JO_SCR

8.59.09

Image 45

HRS_PRI_PLCM

8.59.09

Image 45

HR_MASS_UPD

8.59.10

Image 46

TRW_EXT_STMT

8.59.09

Image 47

WCS_CYCLOAD

8.59.09

Image 47

BAS_BARUN_RT

8.59.09

Image 48

BAS_BAS04_RT

8.59.09

Image 48

BAS_BAS05_RT

8.59.09

Image 48

BAS_CONFSTMT

8.59.09

Image 48

Note:

Oracle's PeopleSoft recommend that you do not change the Configure Batch switch without a complete understanding of how it works, because batch processes must be specifically coded to reference the RTI Switch.

For additional information about RTI Switch, see PeopleTools: Search Technology, "Administering Real-Time Indexing" documentation.