Batches Going Into Pending Status When Database Connection Down (Doc ID 3035443.1)

Last updated on JULY 19, 2024

Applies to:

Symptoms

On RMB v2.9.0.1.0 against FW v4.4.0.2.0, Batches are going into Pending status due to an unavailable DB (database) link.

We understand the reason for failure with a batch run when DB is unavailable during batch execution (for any internal network issue). But once DB is available, all batches next in queue go into pending state including F1-FLUSH.
It only works after restarting of TPW (Threadpoolworker). We expect the process should work even without restarting TPW - once DB becomes available, it should be able to execute the batches in the queue.

ACTUAL BEHAVIOR
-----------------------------
TPW is stuck and no batches are processed and show them in Pending status.

EXPECTED BEHAVIOR
----------------------------------
Once the DB is up, TPW should work as usual and pending batches should get processed as per below scenarios:
1. Batches that were in-progress when DB went down, move to Error status
2. Batches in pending state get picked up and get executed

STEPS
-----------
1. Get the TPW up.
2. Get the DB down.
3. Schedule multiple batch jobs with online submissions.
4. Get the DB up.

Cause

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