How to Troubleshoot when the Workflow Services Go Down
(Doc ID 564394.1)
Last updated on DECEMBER 03, 2019
Applies to:Oracle Workflow - Version 220.127.116.11 to 12.2.2 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
Checked for relevance on 26FEB2012
This article is created in order to help you to solve the most common problems with the Workflow Services. This article is intended to be used when the Workflow Services go down. It is written for Oracle Applications Administrators and Database Administrators.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|A. How to determine if the workflow services are up and running?|
B. What to do when the workflow services go down?
|1. Make sure the Service Component Containers are started from OAM|
|2. Make sure Concurrent GSM Enable profile option is set to Yes|
|3. When the workflow services are down, this is usually solved by running the Concurrent Manager Recovery|
4. Make sure the Service Service Manager:<NODE> is up and running in the concurrent manager tier otherwise the workflow services won't start:
|5. Run the CP Java Regression Test concurrent program to identify if there are dbc problems|
|6. Run the following to confirm that the required jar files exist or will exist in appsborg2.zip.|
|7. Reviewing the output of $FND_TOP/sql/wfver.sql in the Service Component Control Event Subscriptions section|
|8. Increase the Workflow Mailer's Log Level to Statement in order to get additional diagnostic information for the Workflow Mailer|
|9. After trying to start the Workflow Services, the mailer log files show the following error:|
|10. WF Mailer Service cannot be started, mailer log file is not created and there are no errors in the ICM and FNDSM log files.|
|Workflow Information Center, Diagnostics, & Community|