D2-IDEWT Batch Job Runs Continuously When Running Daily Consumption Extract Jobs (DataConnect)
(Doc ID 2410134.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Utilities Meter Data Management - Version 220.127.116.11 and later
Information in this document applies to any platform.
When running daily consumption extract jobs (DataConnect), the D2-IDEWT job normally runs continuously each minute from the time F1-SUBRQ starts until the last consumption extract job completes.
Under some condition(s), the D2-IDEWT job runs continuously and does not stop when the consumption extract jobs complete. This happened when one of the historical correction consumption extracts threw an exception (which may or may not have been a coincidence). When the exception was thrown, the bo_status_cd on the f1_req record for the request did not transition to a status of 'COMPLETE', but instead stayed in a status of 'WAIT_FOR_RUN' in one case or 'ERROR' in another case. In both cases, setting the BO_STATUS_CD to 'COMPLETE' caused the D2-IDEWT process to stop, although it did not stop until after nightly batch when the batch business day is updated and threadpool workers are restarted.
Please provide detailed information regarding the functionality of D2-IDEWT with respect to DataConnect consumption extracts so that we may more effectively troubleshoot this issue.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document