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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Do we need to run steps for maintaining oracle search in production after every patch?
Summary:
Oracle Fusion Recruiting Cloud: Maintaining Oracle Search for Oracle Recruiting (Doc ID 2637638.1) talks about running steps for oracle search after an upgrade/patch. I'm trying to understand better, does that mean we have to re-run some steps or schedule processes after every patch in production? that doesn't make sense to me. in a test pod, I'm aware we need to re-run the index, but doing it in production after every patch seems odd. looking for some clarification. Thank you
Content (please ensure you mask any confidential information):
Version (include the version you are using, if applicable):
24B
Code Snippet (add any code snippets that support your topic, if applicable):
Tagged:
0