Concurrent Manager issue ( Actual 0, Target 1 ) in R12

Dear Reader,

Today, One of my application user reported that the workflow services were down on TEST instance.

When I checked through OAM ( System Administrator --> OAM --> Workflow Manager ), I saw all service components are down.

Then, I checked in Concurrent Administrator window, I saw all Workflow managers ( ie. Workflow Notification Mailer, Workflow Agent Listener,Workflow Document Web Services Service ) were having their actul value as 0 and target value as 1.

I have tried with Restarting Workflow managers one by one, Activating and Deactivating the managers. But still issue was persist. So, many of the notes suggested to run cmclean.sql and bounce entire CM services.

Finally, I have decided to fix this issue without bouncing any services. I have completely reviewed the CMCLEAN.sql and execute the following update statements manually for all the WF Managers,


-- Updating process value as Zero

UPDATE  fnd_concurrent_queues
SET     running_processes = 0, max_processes = 0
where    concurrent_queue_name in ('WFWSSVC','WFALSNRSVC','WFMLRSVC');

-- Updating Control code with NULL

UPDATE  fnd_concurrent_queues
SET     control_code = NULL
WHERE   concurrent_queue_name in ('WFWSSVC','WFALSNRSVC','WFMLRSVC')
AND    control_code not in ('E', 'R', 'X')
AND     control_code IS NOT NULL;

-- Making Target node as Null

UPDATE  fnd_concurrent_queues
SET     target_node = null
where   concurrent_queue_name in ('WFWSSVC','WFALSNRSVC','WFMLRSVC');

commit;

After making these updates statements, Immediately Internal manager brought up all Workflow managers with actual and target value as 1 and all service components showed as UP in OAM.

Same update statements I have performed for "Output Post Processor" concurrent manager and this also fixed.

Finally I have ignored the bouncing of ICM Services. :)

You can also do the same and update your comments here.

Thanks once again for visiting our blog !!!