Aborted Job Goes Into 'Aborted/Not Rolledback' Status With Execution Status As 'Executing' And Same Program Can't Be Submitted Again (Doc ID 2066124.1)

Last updated on OCTOBER 14, 2015

Applies to:

Oracle Life Sciences Data Hub - Version 2.2.2 and later
Information in this document applies to any platform.

Goal

 On :  2.2.2 version, Execution Component

ACTUAL BEHAVIOR  
----------------
When cancelling a high load PLSQL job, it goes to 'Aborted/Not Rolledback' status with Execution Status as 'Executing'.

If resubmit the same program, afferent job goes to Serializing status until first job reach 'Execution Status: Aborted'

EXPECTED BEHAVIOR
-----------------------
LSH job should be killed by Cancel Job command.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create and submit a high load PLSQL job
2. Go to job page and click Cancel job
It goes to 'Aborted/Not Rolledback' status with Execution Status as 'Executing'
3. Resubmit the program - it goes to Serializing status

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms