InForm Data Load Jobs are Moving to 'Aborted' Status after DMW Upgrade to Version 3.1.1 (Doc ID 2849767.1)

Last updated on JULY 13, 2023

Applies to:

Symptoms

On Oracle Life Sciences Data Management Workbench (DMW) 3.1.1 version,

When attempting to perform an InForm Data Load job after upgrade from DMW 2.5.3 to 3.1.1,
the following error occurs:

Associated scheduler for this job is not running.
Scheduler is in STOPPED status with errors: REASON="Job slave process was terminated"
This job won't able to continue its execution and will be stuck in same status.
Hence, Application will abort this job.

Abort operation is invoked from following session:
Session id: <SESSION_ID>
Serial#= <SERIAL_ID>
Instance Id: <INSTANCE_ID>
User name: <USER_NAME>
Machine= <HOST_NAME>
Program= <PROGRAM_NAME>
OS user= <USER_NAME>

***************ABORT REQUESTED**********************
Abort operation is started for this job at  :: 02-04-2022 06:48:07
Job Status : Started :: Execution Status: Pendinglogon
Service instance Id:<SERVICE_INSTANCE_ID> is associated for this job.
OWB Operator Type:CdrPLSQLImmediate_1
Technology Type:$TECHTYPES$INFORMDATA

It was observed that:

When the jobs pre-processing phase is done on Database node 1 and execution phase on node 2, then the jobs are failing/going to abort state.
When the jobs pre-processing phase is done on Database node 2 and execution phase on node 1, then the jobs are completed successfully.

STEPS
-----------------------
The issue can be reproduced with the following steps:
1. Upgrade DMW 2.5.3 to 3.1.1.
2. Attempt to execute an InForm Data Load job.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.