Job Queue / Message-Triggered Submission Queue: How to Stop, Start, Flush, Enable Them
Last updated on JANUARY 09, 2018
Applies to:Oracle Life Sciences Data Hub - Version 184.108.40.206 and later
Oracle Health Sciences Data Management Workbench - Version 2.4.6 and later
Information in this document applies to any platform.
Why we need sometimes to stop, start, flush, enable Job Queue and Message-Triggered Submission Queue? Below are some examples of cases when LSH or DMW were already working fine, and suddenly, jobs are not longer working:
1. When you need to disable LSH Debug option, and then, restart the job and message queues.
2. After Database or MiddleTier maintenance, randomly, the jobs that were working fine before, cannot longer be executed.
3. When the jobs are displayed in Pending status randomly and without apparent reason. The Jobs may stay in Pending Status, or LSH or WorkFlow Jobs cannot not be initiated anymore, when they were already working OK before.
4. LSH WorkFlow functionality is working fine standalone, but does not longer work when called in LSH. It is a symptom that let us know the root cause is on the LSH layer. You may hit errors as below ones:
java.sql.SQLException: ORA-04043: object PKG_CREATE_CONTAINER does not exist
java.sql.SQLException: ORA-04043: object PKG_DATALOAD_EXTENSION does not exist
java.sql.SQLException: ORA-06550: PACKAGE BODY, line 3507, column 11:
PLS-00201: identifier 'PKG_DATALOAD_EXTENSION.SP_UPGRADE' must be declared
This document applies to cases when LSH or DMW were already working fine, i.e, on production, and suddenly, stopped working as the examples indicated at the beginning of this KM Doc.
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