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.

What is the purpose of ORA_PER_CHECKLIST_MANUAL_ASYNC_ALLOCATION profile

edited Feb 6, 2025 9:57PM in Journeys 1 comment

We'd like to understand what the profile option ORA_PER_CHECKLIST_MANUAL_ASYNC_ALLOCATION does and also why the value in our Production environment (RUX,REST) is different to the Oracle documentation default value (RUI,REST) as we did not modify this value ourselves (to our recollection). The Oracle documentation does provide a brief description but does not explain what it means to allocate checklists asynchronously vs synchronously i.e. what is the change in the system behaviour that we will see and also, it makes no reference of what 'RUX, Rest' means vs 'RUI, Rest'. Also, is this still relevant if we're using Redwood?

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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