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.

Missing clarity on 24D feature Automated re-ingestion of Oracle search indexes

Summary:


Missing clarity on 24D feature - Automated re-ingestion of Oracle search indexes

Content (please ensure you mask any confidential information):

Hi Team,

Greetings!

This is about the 24D feature Automated re-ingestion of Oracle search indexes :-

Automated Re-Ingestion of Oracle Search Indexes

As per the details -

  • The automated re-ingestion is smart and will only initiate re-ingestion if new attributes are added to an index.

—>

How do one know if there are any new attributes added to an index? There are multiple index.

  • Automated re-ingestion process is non-destructive, meaning it runs in the background while existing indexes are available.

—>
What does this mean? Is it about automatic run of ESS job in the background? Can those runs be tracked? Is there any specific activity to be performed post 24D upgrade?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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