Technology Stack - EBS (MOSC)

MOSC Banner

ADOP Cutover - Best practise on scheduled requests/alerts

edited Nov 12, 2018 6:41AM in Technology Stack - EBS (MOSC) 12 commentsAnswered ✓

We are on EBS 12.2 and an issue came up recently during technology stack patching in anticipation of HRMS patching.  Staff reported that a scheduled alert did not run as it was scheduled to run while the application was down during adop cutover.  Staff are requesting that when we patch, we check to see if any scheduled concurrent requests or alerts were in the timeframe causing them to be missed.

Has anyone else addressed this issue?  What is the best practice for those patching to ensure scheduled jobs don't get skipped or fail because of the patching timeframe?

Lydia

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

EBS TechStack Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center