Re: Workflow background process errors after 19c upgrade

Posted by ErmanArslansOracleBlog on Feb 07, 2023; 6:58am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Workflow-background-process-errors-after-19c-upgrade-tp11563p11565.html

We have that event instructed to be set in "Using UTL_FILE_DIR or Database Directories for PL/SQL File I/O in Oracle E-Business Suite Releases 12.1 and 12.2 (Doc ID 2525754.1)" --> To enable the UTL_FILE functionality on which the supplemental UTL_FILE_DIR parameter depends, ensure that you have set the following event at the CDB level in your database initialization parameters: event='10946 trace name context forever, level 8454144'

According to what you have sent, you have that event set in your PROD instance, which is the instance having the issues. What about that other event (10995), why is it there?  -- it is already removed from the EBS 12- 19C interoperability document --> Removed setting event 10995 trace name context forever, level 16.

and there is no ref. for 12.2, it was there for 12.1 and it was removed then..

Additional info:

ORA-10995: general event for materialized views

Cause: N/A
Action: This internal event is used to enable various actions associated with MVs. The event level is interpreted as a bitmap of actions to enable.//*Comment: Not for general purpose use.LEVEL ACTION//---------------------------------------------------------------------------0x0001 enable callback-based refresh0x0002 invalidate dependents for online redef0x0004 allow PCT fast refresh after CONSIDER FRESH


1)---> so this  10995 is set in your PROD, but not set in your TEST.. so what about removing it ? -- Workflow background process is a process that can encounter ORA-01555.. So that means it uses the Materialized views in the backend.. So that event set for the MW access may affect it.

2)Also sent me the workflow background process log, if the issue persists.

3)Also see -> 11.i - 12 How to Resolve the Most Common Workflow Background Engine Problems (Doc ID 466535.1) -- finding the cause / the table /query related with that ORA-06502 can help..

Some other refs.

How to Monitor the FNDWFBG Workflow Background Program? (Doc ID 369537.1)
How To Generate Performance Trace for Workflow Background Process? (Doc ID 734425.1) -- that is for performance but can also be used for getting the trace and capturing the SQLs(to get the problematic SQL )