root cause analysis concurrent scheduling
DESCRIPTION
concurrentTRANSCRIPT
![Page 1: Root Cause Analysis Concurrent Scheduling](https://reader036.vdocuments.site/reader036/viewer/2022081807/55cf9985550346d0339dcc99/html5/thumbnails/1.jpg)
Root Cause Analysis
Primary Fault ROOT CAUSE
Corrective Action & Responsibility Date
Area: Oracle Applications Product/Process:Concurrent Schedule
Problem Description:Scheduled concurrent requests failed to run as per schedule post restart
![Page 2: Root Cause Analysis Concurrent Scheduling](https://reader036.vdocuments.site/reader036/viewer/2022081807/55cf9985550346d0339dcc99/html5/thumbnails/2.jpg)
Use this route to specify the nonconformity that is being investigated.
Why?
Use this route to investigate why the problem wasn’t detected
Therefore B
Why?
Use this route to investigate the root cause of the system.
Why?
Why?
"It looks like a bunch of UK related programs running under WEB use didn’t start back up"
A1. Post restart sanity check should include checking against a list of concurrent requests provided by Philosophy and not based on "pending Requests"
Normally terminated scheduled programs will have the schedules intact. This is taken care of by the system itself.If there is an abrupt termination as it happened on 14th scheduling becomes corrupt.
2. An enhancement for an alert needs to be placed with the logic in (1) so that stakeholders are informed in advance
Why?
Sanity check done on 14-Aug-13 post restart but scheduling problem for 2
conc. Programs not detected.
Sanity check did not reveal for requests that got abruptly terminated and was not re-scheduled
Why?
Oracle does not retain schedule for abruptly terminated programs
Post Restart, add sanity check for scheduled requests based on new query
Schedules that have had abrupt terminations need to be rescheduled manually
![Page 3: Root Cause Analysis Concurrent Scheduling](https://reader036.vdocuments.site/reader036/viewer/2022081807/55cf9985550346d0339dcc99/html5/thumbnails/3.jpg)
Root Cause Analysis
Date
Product/Process:Concurrent Schedule
Scheduled concurrent requests failed to run as per schedule post restart
![Page 4: Root Cause Analysis Concurrent Scheduling](https://reader036.vdocuments.site/reader036/viewer/2022081807/55cf9985550346d0339dcc99/html5/thumbnails/4.jpg)
Use this route to specify the nonconformity that is being investigated.
Use this route to investigate why the problem wasn’t detected
Use this route to investigate the root cause of the system.
![Page 5: Root Cause Analysis Concurrent Scheduling](https://reader036.vdocuments.site/reader036/viewer/2022081807/55cf9985550346d0339dcc99/html5/thumbnails/5.jpg)
PROGRAM StatePhilosophy Web UK Inventory Handler Abnormally TerminatedOutbound Triggering Process (Triggering Process Outbound) Abnormally TerminatedIN: Purchase Orders (850/ORDERS) Abnormally TerminatedPhilosophy - Demandware Inventory Handler Abnormally TerminatedResponsys File Upload Abnormally TerminatedOUT: Invoice (810/INVOIC) Abnormally TerminatedPhilosophy - Demandware Price Export Handler Abnormally TerminatedPhilosophy Process Wave Planning Abnormally TerminatedPhilosophy Order Extract to Coty UK Abnormally TerminatedPhilosophy Generate Misc Label Abnormally Terminated
![Page 6: Root Cause Analysis Concurrent Scheduling](https://reader036.vdocuments.site/reader036/viewer/2022081807/55cf9985550346d0339dcc99/html5/thumbnails/6.jpg)
Schedule Status CurrentScheduled later manually by DevonRequired for schedule?Scheduled Manually laterNot scheduledNot scheduledScheduled ManuallyNot scheduledIs this neededto be scheduled?Manually scheduled laterNot a scheduled request