For some records, WF_NOTIFICATION_OUT table shows the message state 3, which means such messages are expired. Should I rebuild the queue to bring these messages back to normal state?
Some messages could expire and move to exception queue after certain retries. Following select statement can be executed to check the retry count and message status. Select corr_id, msg_state, retry_count, count(msg_id) from applsys.aq$wf_notification_out group by corr_id, msg_state, retry_count; Instead of rebuilding the queue, use the concurrent program “Move messages from Exception to Normal Queue of Workflow Agent” to move messages from exception queue to normal queue for agent WF_NOTIFICATION_OUT.
Related Questions
- For some records, WF_NOTIFICATION_OUT table shows the message state 3, which means such messages are expired. Should I rebuild the queue to bring these messages back to normal state?
- What does iWise use to prevent message storms - multiple messages for the same event - from creating multiple incident records during automatic logging of alerts/exception incidents?
- What does the message "No primary key defined on table name; you are unable to update records after migration." mean?
