Trace File Is Not Generating for Custom Program
(Doc ID 2250974.1)
Last updated on SEPTEMBER 23, 2023
Applies to:
Oracle Concurrent Processing - Version 12.0.0 to 12.1.3 [Release 12 to 12.1]Information in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
After following all steps mentioned in the note below in order to enable trace for a custom request, the trace file is not being generated:
Doc ID 453527.1 How To Trace a Concurrent Request And Generate TKPROF File
The below query shows that ORACLE_PROCESS_ID (Database process identifier) and ORACLE_SESSION_ID (Database session identifier) have NULL values.
ORACLE_PROCESS_ID and ORACLE_SESSION_ID do not get updated when these programs do not connect to the database as per Doc ID 1457799.1.
To check if the report is fetching data from the database i. e. establishing a connection with the database
Connect to SQLPLUS as APPS User :
Note : oracle_process_id is Unix PID and request_id is running concurrent program's request ID.
If "sid" and "serial#" values are returning values, then it means that process is running at database level.
Cause
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
| Symptoms |
| Cause |
| Solution |
| References |