There are available transactions to clear in the system that I confirmed in the forms interface, but no rows returned.
BEGIN mo_global.set_policy_context('S', 0); END; SELECT count(*) FROM CE_200_TRANSACTIONS_V T ------------------- BEGIN mo_global.set_policy_context('M', 0); END; SELECT count(*) FROM CE_200_TRANSACTIONS_V T
SQL> disc Disconnected from Oracle Database 11g Enterprise Edition Release 188.8.131.52.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options SQL> conn apps/apps@prod Connected. SQL> SQL> SQL> SQL> exec mo_global.set_policy_context('S', 0); PL/SQL procedure successfully completed. SQL> select count(*) from po_headers; COUNT(*) ---------- 14425 SQL> select count(*) from CE_200_TRANSACTIONS_V; COUNT(*) ---------- 0
stopuz wrote:From what responsibility you run this concurrent program?
That note helped. I am able to view the data in SQL Developer now, but the issue continues as we had sat the program as a concurrent program. Somehow the security context is getting overwritten when we run it from there. I tried setting the Operating unit mode for this program to "Single", "Multi",
and "None" but it did not make any difference.
Can you please advise? Where I may be making a mistake?
It is not set at application level either. I followed the document to enabled the debug options as described in there, but the concurrent request did not generate any logs. Am I supposed to write the debug messages myself within the custom code?If you enable debug/trace as per the docs and submit the request then you should get those debug messages in the table. You do not need to write any debug messages in your custom code.
Attention: If using Release 12 - the following patch is required for the trace to work properly using the steps below. Patch 8743459Please apply the patch.
Patch 8743459: 12.1.1: 'SQL TRACE' IN 'DEBUG OPTIONS' IS UNLIKELY WORKING.
We are on R12.1.3, but when search for this patch in OAM, it does not seem to be applied. Should I apply the patch? But, we are just after debug info not trace, I though it is irrelevant.
I deleted everything from fnd_log_messages table and enabled the profile option for the user. No one else is connecting to the system right now other than this account. There are no log entries in the table. Also, I tried to do the same thing for a built in program (a report which generates output), but it did not generate any log entries either.Please see profile options at the user level as per (How To Trace a Concurrent Request And Generate TKPROF File [ID 453527.1] -- 4. Debug based on fnd_log_messages), logout and login again for the table to get populated.