Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
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
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Running Ingestion process after quarterly upgrade and P2T

Summary:


Content (please ensure you mask any confidential information):

Should not these below be done by Oracle Admin team as part of their Post processing after upgrade/P2T? Why it should be a task for the customer?

Refresh Indexes After Upgrade - You must run the initial data ingestion process for every created index after upgrading to a new release.
Refresh Indexes After P2T - You must run the initial data ingestion process for every created index after P2T (production-to-test) process.

Version (include the version you are using, if applicable):
24B

Code Snippet (add any code snippets that support your topic, if applicable):

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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