You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Why does the ESS job for fa-hcm-person-results initial ingest to OSCS take 10+ hours after a P2T?

I’m looking for insight into why this Oracle indexing job is taking so long in our lower environments after a refresh/P2T.

We are running the ESS job to create index definition and perform initial ingest to OSCS with the parameter: fa-hcm-person-results

We've recently added this job to our list of other jobs to run after a refresh/P2T because we enabled the applicable Redwood pages. We've had a handful of refreshes now and this job is taking about 10+ hours to complete. As you can imagine, this is delaying the release of the environment to the system users by at least one business day.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!