Maintaining Oracle Search Indexes
Capabilities such as Global Search and Connections use Oracle Search indexes to expedite responses to your queries.
While loading data, HCM Data Loader captures the Fusion surrogate ID of all the records successfully created, updated, and deleted by your data set.
After which, it automatically submits the Update Oracle Search with HCM Data Loader Changes process to maintain the Oracle Search indexes with the changes made.
You can review the status of this process by clicking Review Processes for your data set in the Import and Load Data task.
Disabling Oracle Search Bulk Ingestion
To disable the Update Oracle Search with HCM Data Loader Changes process include the following instruction at the top of your file:
SET DISABLE_POST_PROCESS_TASKS OracleSearchBulkIngestion
HCM Data Loader will continue to capture the details needed for the bulk ingestion of Oracle Search indexes despite disabling the Update Oracle Search with HCM Data Loader Changes process.
You must manually submit the Update Oracle Search with HCM Data Loader Changes process to keep the Oracle Search Indexes updated.
Initial Ingestion of Oracle Search Index
If the update you’re making impacts the vast majority of records for an Oracle Search index, you may want to consider disabling bulk ingestion and reinitializing the Oracle Search index instead.
To disable bulk-ingestion include the following instruction at the top of your file:
SET ORACLE_SEARCH_UPDATE_MODE INITIAL
It disables the capture of the Fusion surrogate IDs for Oracle Search bulk-ingestion and the automated submission of the Update Oracle Search with HCM Data Loader Changes process.