Job Queue / Message-Triggered Submission Queue: How to Stop, Start, Flush, Enable Them (Doc ID 2055811.1)

Last updated on FEBRUARY 20, 2023

Applies to:

Symptoms

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 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. It may happen the workload was very heavy at once, and the jobs are waiting to be processed. This KM Note applies if you prefer to cancel and start fresh.

2. When you need to disable LSH Debug option, and then, restart the job and message queues. For example, after applying the steps from <NOTE:2250628.1> ""How To Restart LSW Successfully (DMW + LSH)".

3. After Database or MiddleTier maintenance, i.e., restarting DMW and LSH Tech Stack. Randomly, the jobs that were working fine before, cannot longer be executed.

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

Changes

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.

Cause

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