Event_Status Records In TBL_WO_EVENT_QUEUE Are Not Updated With Event_status = 303 (Doc ID 2017109.1)

Last updated on APRIL 16, 2024

Applies to:

Symptoms

erver version B.11.31 Matrix and we have migrated the  database from an ASAP 5.2 environment. Since then if the SARM process goes down, we are not able to start the system completely because there are many records in the tbl_wo_event_queue with event_status = 301.

The ASAP version is "ASAP Release R7_0_2_P6/B13/HP-UX/U/B.11.31/ia64/Dec 12 2013 14:05:12". The column 'event_status' in tbl_wo_event_quee (SARM db) is never updated to 303 (complete state) and permanently remains in state 301.

In order to start the SARM process we need to update the event_status from 301 to 303 in tbl_wo_event_queue as a  workaround. In our analysis, after enabling the log of the SARM to LOW, we observed that the call SSP_update_wo_event is not made by SARM.

On the other server, ASAP 7.0.2 patch1 environment (Where ASAP works fine without this issue) calls the procedure SSP_update_wo_event and appeared in the diagnostic file as below:

Command 'grep' executed:

$ASAP_BASE/DATA/logs/20150529 > tail -f SARMAS7.diag | grep SSP_update_wo_event
Executing RPC [SSP_update_wo_event]. Retry Count [0]
Created PL/SQL statement as follows : begin :retval :=SSP_update_wo_event(:wo_id,:event_unid,:event_status,:start_dts,:complete_dts); end;
RPC(SSP_update_wo_event) Complete in 3ms
Executing RPC [SSP_update_wo_event]. Retry Count [0]
Created PL/SQL statement as follows : begin :retval :=SSP_update_wo_event(:wo_id,:event_unid,:event_status,:start_dts,:complete_dts); end;
RPC(SSP_update_wo_event) Complete in 7ms

What are the possible causes and how we can fix it?

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.