Troubleshoot Record Mismatches

When setting up an Oracle Search-based feature for the first time in a pod, including the production pod, the user has to first turn on the feature before creating the required indexes by running the full ingestion process. It means that the feature is unavailable for a certain time (even hours).

Even a single excessively large document can make the entire full ingestion process to fail.

After the ingestion is completed, you need to run the HCM Journeys Oracle Search Diagnostics Report diagnostic report.

If there is a discrepancy between the number of records in the database versus in the index, you need to manually compare this difference with the assigned journeys visible on the Organization Journeys tab. Once you determine the missing journeys, you will need to run the Mass Ingest Journeys Data process with the Person Numbers parameter to re-ingest the data.

Users have to manually run the full ingestion process after upgrades. When a user upgrades their environment, including the production environment, the new code may require related index changes. Such an upgrade will only be fully functional for users when the full ingestion process completes successfully. It means that Oracle Search-based features in journeys may not work until that time.

Users have to manually run the full ingestion process after production to test (P2T).