Part of my Oracle Fusion HCM Fix of the Day series: real issues from implementations and a Redwood rollout I led without a Systems Integrator, and how I fixed each one.
This is Fix #25. Start from Fix #1 to follow the series in order.
Moving Recruiting to Redwood is not just a switch you turn on. The Redwood pages read much of their data from Oracle Search (OSCS, Oracle Search Cloud Service), and that search data has to be built by a set of scheduled processes. During our Recruiting Redwood setup, the lesson was simple and strict: every one of those ESS jobs has to finish with Succeeded. If even one ends in Warning or Error, the data does not load, and the Redwood pages show an incomplete picture.
The symptom
We submitted the ESS jobs for the Recruiting Redwood setup. Some completed. Some ended in Warning or Error. Others sat in Wait or Hold and never really started.
From the outside it looked like the setup had run. But the data was not there in Redwood: requisitions, candidates and lists of values were missing or incomplete. It is easy to look at a list of processes, see mostly green, and move on. That is the trap. A partial run is not a successful run.
Why it happens
These jobs depend on each other. One job builds or loads index data that the next one needs. If a job ends in Warning or Error, the index it was meant to build is incomplete, and anything that runs after it works from that gap.
Jobs stuck in Wait or Hold cause a different problem. Recurring indexing jobs and old duplicate requests keep running in the background. They compete with the full reload you are trying to do, or run on top of it at the wrong moment.
So a clean result needs two things: a clear queue before you start, and every job ending in Succeeded.
Before you start
- You need the FND_MANAGE_SCHEDULED_JOB_DEFINITION_PRIV privilege to submit the OSCS ingest job. It comes with the Application Administrator and Application Developer job roles.
- If you use the Redwood requisition and offer lists of values backed by Oracle Search, enable their profile options first: ORA_PER_ORACLE_SEARCH_WORKERSLOV_ENABLED, ORA_PER_ORACLE_SEARCH_POSITIONSLOV_ENABLED, ORA_PER_ORACLE_SEARCH_DEPARTMENTSLOV_ENABLED, ORA_PER_ORACLE_SEARCH_LOCATIONSLOV_ENABLED and ORA_PER_ORACLE_SEARCH_JOBSLOV_ENABLED.
- If you use advanced job application filters, enable ORA_IRC_JA_ORACLE_SEARCH_ENABLED. Without it, the fa-hcm-jobapplication ingest fails with "Index not enabled".
The ESS jobs we ran, in order
Step 1: Stop and clear the queue
- In Scheduled Processes, stop anything still Running for Recruiting search.
- Cancel the recurring jobs Maintain Candidates and Job Requisitions for Search and Index Candidate Attachments.
- Search by status for Hold and for Wait, and cancel every request you find.
- Search once more and confirm nothing is left running, waiting or on hold.
Step 2: Reload the Recruiting search data (one at a time, each must succeed)
- Load and Index Master Geography Hierarchy, with no parameters.
- Load and Index Job Requisitions, indexing mode Drop and Recreate Index.
- Load and Index Candidates, indexing mode Drop and Recreate Index.
- Index Job Summary for Each Requisition, Full mode (needed for Smart Search and Career Coach search).
Step 3: OSCS index ingest
Job name: ESS job to create index definition and perform initial ingest to OSCS. Submit it once for each index, entering the index in the Index Name to Reingest field. Submit them one by one, and wait for each to succeed before the next. Never leave the field blank, or it runs for every predefined index.
- fa-hcm-savedsearch
- fa-hcm-requisition
- fa-hcm-jobapplication (only if advanced job application filters are enabled)
- fa-hcm-irc-hiring-events (if you use hiring events)
- fa-hcm-irc-messages (if you use the Redwood Message Center; run once, do not schedule it)
- For the Redwood requisition and offer lists of values: fa-hcm-person, fa-hcm-position, fa-hcm-organization, fa-hcm-location and fa-hcm-job
Step 4: Restart the incremental jobs
- Maintain Candidates and Job Requisitions for Search, every 15 minutes.
- Index Candidate Attachments, every 15 minutes.
- Index Job Summary for Each Requisition, Incremental mode.
How I fixed it
- I stopped all running Recruiting search jobs and cancelled every request in Hold or Wait.
- I confirmed the queue was clear before submitting anything.
- I ran the jobs above one at a time, in order.
- After each job, I checked the status. If it ended in Warning or Error, I opened the log, fixed the cause, and reran it before submitting the next one.
- When every job showed Succeeded, I restarted the recurring jobs.
- I checked the Redwood Recruiting pages, the requisition and candidate searches and the lists of values, and confirmed the data had loaded.
How to avoid it next time
- Clear the queue first. Stop anything running, and cancel everything in Hold or Wait.
- Treat Warning as a failure for setup jobs. Read the log every time.
- Run the initial OSCS ingest by hand, once per index. Oracle advises against scheduling it.
- Keep a checklist of the jobs with a status column, and tick each one only when it shows Succeeded.
- Rerun the relevant jobs after quarterly updates and after a production-to-test refresh, following Oracle's guidance for your release.
- After the last job, check the data in the Redwood pages, not just the job statuses.
Recruiting data depends on search indexes more than most people expect. In Fix #7, jobs were missing from the career site until the search index was rebuilt. Different symptom, same lesson: check the processes behind the page.
Key takeaway
For a Recruiting Redwood setup, every ESS and OSCS ingest job must end in Succeeded. Stop running jobs, cancel anything in Hold or Wait, then run the jobs one at a time in order and fix every warning or error before moving on.
Meeramaheswari Annadurai, Oracle HCM & Enterprise AI. More at meera2k10.github.io/enterprise-ai
```