Skip to main content

Workflow Services are not Running or Starting in R12 Oracle Apps

Oracle Workflow Services in Oracle Applications are encountering problems.The workflow components are not starting when I was trying to start up the services from front end web-form using system administrator responsibility.These services appear with a Target value of 1 and an Actual value of 0. Even I tried from Concurrent>Manager>Administer form but still these were not starting.

 Workflow components was not coming  Up and  showing as below


 Target - 1 Actual - 0


Workflow service Components and there shotnames.

Workflow Agent Listener Service - WFALSNRSVC
Workflow Mailer Service - WFMLRSVC
Workflow Document Web Services Service - WFWSSVC

 We can find the same using below query as well.

Workflow Agent Listener Service:

SQL> select CONCURRENT_QUEUE_NAME from  apps.fnd_concurrent_queues_tl where USER_CONCURRENT_QUEUE_NAME='Workflow Agent Listener Service';

CONCURRENT_QUEUE_NAME
------------------------------
WFALSNRSVC


Workflow Mailer Service:

SQL> select CONCURRENT_QUEUE_NAME from  apps.fnd_concurrent_queues_tl where USER_CONCURRENT_QUEUE_NAME='Workflow Mailer Service';

CONCURRENT_QUEUE_NAME
------------------------------
WFMLRSVC


Workflow Document Web Services Service:

SQL> select CONCURRENT_QUEUE_NAME from  apps.fnd_concurrent_queues_tl where USER_CONCURRENT_QUEUE_NAME='Workflow Document Web Services Service';

CONCURRENT_QUEUE_NAME
------------------------------
WFWSSVC



Now to fix the issue we will follow below steps

1) Make the the processes value zero for these services.

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

3 rows updated.

2) Update Control codes 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; 

0 rows updated.

3) Make Target node as Null option

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

3 rows updated.

4) Commit

SQL>commit;

Commit complete.

5) Check Workflow Concurrent Managers

Wait for few minutes, the Internal concurrent manager will bring up services automatically.
We can check the components status using following SQL statements.

SQL> select control_code,running_processes,MAX_PROCESSES from fnd_concurrent_queues where concurrent_queue_name='WFALSNRSVC';

C RUNNING_PROCESSES MAX_PROCESSES
- ----------------- -------------
                  1             1

SQL> select control_code,running_processes,MAX_PROCESSES from fnd_concurrent_queues where concurrent_queue_name='WFALSNRSVC';

C RUNNING_PROCESSES MAX_PROCESSES
- ----------------- -------------
                  1             1

SQL> select control_code,running_processes,MAX_PROCESSES from fnd_concurrent_queues where concurrent_queue_name='WFWSSVC';

C RUNNING_PROCESSES MAX_PROCESSES
- ----------------- -------------
                  1             1

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...