1. To Enable Level 12 Trace:
Navigate Responsibility: System Administrator > Profile=> System
A. Find the profile option 'Initialization SQL Statement - Custom' for User who is submitting the process to trace.
User: User submitting the process
Profile: Initialization SQL Statement - Custom
B. Click on User column - Edit Field and enter
begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SET EVENTS='||''''||'10046 TRACE NAME CONTEXT FOREVER,LEVEL 12'||''''); end;
c. Save.
2. To Enable FND debug:
Navigate Responsibility: System Administrator > Profile => System
a. Find the FND profile options for User who is submitting the process to debug.
User: User submitting the process
Profile: FND:%Debug%
b. Set the following Profile values at the user level
FND: Debug Log Enabled :Yes
FND: Debug Log Filename : NULL
FND: Debug Log Level : STATEMENT
FND: Debug Log Module : %
c. Save.
3. Run the process to reproduce the issue. Note: Avoid any extra steps as we want to trace just the process that is failing.
4. Disable Trace and FND Debug by resetting the above profiles.
5. Spool the output of the following query to an excel file which gives FND debug log:
SELECT LOG.MESSAGE_TEXT, LOG.MODULE
FROM FND_LOG_MESSAGES LOG,
FND_LOG_TRANSACTION_CONTEXT CON
WHERE CON.TRANSACTION_ID = &request_id
AND CON.TRANSACTION_TYPE = 'REQUEST'
AND CON.TRANSACTION_CONTEXT_ID = LOG.TRANSACTION_CONTEXT_ID
ORDER BY LOG.LOG_SEQUENCE;
6. To pull the trace:
a. Run the following query, this gives the directory where the trace file is stored.
SELECT name, value
FROM v$parameter
WHERE name = 'user_dump_dest';
b. Go to the directory returned by USER_DUMP_DEST and use this command to find the trace, use the concurrent request id for the process that is failing.
grep -i 'CONC_REQUEST_ID=<enter conc req id>' *
Ex: grep -i 'CONC_REQUEST_ID=1499133' *
c. Upload both:
- RAW trace file
- Tkprofed output file:
To tkprof:
begin fnd_ctl.fnd_sess_ctl('','','TRUE','TRUE','LOG','ALTER SESSION SET EVENTS='||''''||'10046 TRACE NAME CONTEXT FOREVER,LEVEL 12'||''''); end;
c. Save.
2. To Enable FND debug:
Navigate Responsibility: System Administrator > Profile => System
a. Find the FND profile options for User who is submitting the process to debug.
User: User submitting the process
Profile: FND:%Debug%
b. Set the following Profile values at the user level
FND: Debug Log Enabled :Yes
FND: Debug Log Filename : NULL
FND: Debug Log Level : STATEMENT
FND: Debug Log Module : %
c. Save.
3. Run the process to reproduce the issue. Note: Avoid any extra steps as we want to trace just the process that is failing.
4. Disable Trace and FND Debug by resetting the above profiles.
5. Spool the output of the following query to an excel file which gives FND debug log:
SELECT LOG.MESSAGE_TEXT, LOG.MODULE
FROM FND_LOG_MESSAGES LOG,
FND_LOG_TRANSACTION_CONTEXT CON
WHERE CON.TRANSACTION_ID = &request_id
AND CON.TRANSACTION_TYPE = 'REQUEST'
AND CON.TRANSACTION_CONTEXT_ID = LOG.TRANSACTION_CONTEXT_ID
ORDER BY LOG.LOG_SEQUENCE;
6. To pull the trace:
a. Run the following query, this gives the directory where the trace file is stored.
SELECT name, value
FROM v$parameter
WHERE name = 'user_dump_dest';
b. Go to the directory returned by USER_DUMP_DEST and use this command to find the trace, use the concurrent request id for the process that is failing.
grep -i 'CONC_REQUEST_ID=<enter conc req id>' *
Ex: grep -i 'CONC_REQUEST_ID=1499133' *
c. Upload both:
- RAW trace file
- Tkprofed output file:
To tkprof:
tkprof <RAW trace> <output> explain=apps/uname/apps_pwd sys=no
0 comments:
Post a Comment