Oracle EBS Workflow ( Requisition , PO and Others) status wait for background process

Oracle EBS Workflow ( Requisition , PO and Others) Status Wait for background process

     * If the workflow status stuck in Waiting Background Process: 

Solution1 : Oracle Note : 2012189.1

SOLUTION

Please implement the following solution in TEST instance:

1. Download and review the readme and pre-requisites for Patch 20368337:R12.PO.D

2. Ensure that you have taken a backup of your system before applying the recommended patch.

3. Apply the patch in a test environment.

4. Confirm the following file versions:

POXWPA1B.pls 120.141.12020000.39

5. Retest the issue.

6. Migrate the solution as appropriate to other environments.

Solution2: Oracle Note : 2288816.1

SOLUTION

To implement the solution, please execute the following steps:

1.Clear the cache via below navigation:
Functional Administrator responsibility-> Core Services-> Caching Framwork-> Global Configuration-> Clear All Cache.

2.Logout and re-login.

3.Retest the issue.

Solution 3 : 

1. Shutdown Application and wait all concurrent processes to be kill. 

2. Shutdown Database 

3. Start Application and Database then  run Workflow Background Process Request.

Hope this Helpful,

 

Step by Step SOA 12c Installation guide

Step by Step SOA 12c Installation guide

Useful link :

https://apps2fusion.com/training_demo/SOA-12c/SOA-12c-Installation-Guide.pdf

Thanks, 

Oracle APPS Query to get Instance cloned Date

 Query to get Instance cloned Date

select  to_char(CREATION_DATE,'DD/MM/RRRR HH24:MI') from fnd_nodes a ;

OR 

select to_char(resetlogs_time,'DD/MM/RRRR HH24:MI') from v$database ; 

Best Regards,

ORA-01000 maximum open cursors exceeded

When youo get this error: "ora-01000 maximum open cursors exceeded " error during the database operation.

Then check open_cursor parameter 

From Oracle Document:

OPEN_CURSORS

Property	Description
Parameter type	Integer
Default value	50
Modifiable	ALTER SYSTEM
Range of values	0 to 65535
Basic	Yes

OPEN_CURSORS specifies the maximum number of open cursors (handles to private SQL areas) a session can have at once. You can use this parameter to prevent a session from opening an excessive number of cursors.

It is important to set the value of OPEN_CURSORS high enough to prevent your application from running out of open cursors. The number will vary from one application to another. Assuming that a session does not open the number of cursors specified by OPEN_CURSORS, there is no added overhead to setting this value higher than actually needed.

SQL> show parameter open_cursors ; 

NAME         TYPE     VALUE
------ ---- -----    --------

open_cursors integer     200 

SQ>

* Change current value of open_cursor parameter, you can change the value according to your resource and database.