| Goal |
| Solution |
| References |
APPLIES TO:
Oracle Supplier Lifecycle Management - Version 12.1.2 and laterOracle Contract Lifecycle Management for Public Sector - Version 12.1.3 and later
Oracle Sourcing - Version 11.5.10 and later
Oracle Purchasing - Version 12.0.6 to 12.2 [Release 12 to 12.2]
Oracle iProcurement - Version 11.5.9 to 12.2.4 [Release 11.5 to 12.2]
Information in this document applies to any platform.
iProcurement - Version: 11.5.9 to 12.0
GOAL
How to get log files in iProcurement according to the Procurement/Supply Chain Family Pack level or Oracle Applications release.
SOLUTION
A. For 12.0, 12.1 and 12.2 (except 2 and 3 for 12.2 which uses WebLogic)
===========================
1. OA Framework debug is similar to release 11.5.10.
For SQL Trace and About this page see 11.5.10 item 2 and 3.
To get the debug.log from the table:
1.1 Using System Administrator responsibility, set profile options at the user level:
FND: Debug Log Enabled : Yes
FND: Debug Log Filename for Middle-Tier : leave it as null
FND: Debug Log Level : Statement
FND: Debug Log Module : %
1.2. Truncate table APPLSYS.FND_LOG_MESSAGES
OR
run concurrent process "Purge Debug Log and System Alerts" under
System Administrator responsibility.
1.3. Bounce iAS/Apache
1.4. Reproduce the issue
1.5. Provide the table dump of fnd_log_messages in spreadsheet format.
If truncating the table is not an option:
1.6. Check the maximun log sequence from fnd_log_messages executing:
SQL> select max(log_sequence) from fnd_log_messages;
1.7. Reproduce the issue
1.8. Check the maximun log sequence again:
SQL> select max(log_sequence) from fnd_log_messages;
1.9. Retrieve the log messages executing the below statement. Upload the results in a spreadsheet
format.
SQL> select * from fnd_log_messages where log_sequence > &max_log_sequence_1_6 and log_sequence < &max_log_sequence_1_8 ;
Replace max_log_sequence from the results from 1.6 and 1.8.
OR
SQL> select * from fnd_log_messages
where user_id=(select user_id from fnd_user
where user_name='&user_name');
To generate the entries in the fnd_log_messages while running a concurrent request program set the following:
1. Enable the profile 'Concurrent: Allow Debugging'
2. Give the debug module as '%' (or the product of the program like 'po%')
3. Before running concurrent program, click 'Diagnostics' button and enable
logging there as well.
4. Collect the entries from fnd_log_messages.
5. Use the AUDSID from the request status log and collect it via SQL like:
SQL> select * from FND_LOG_MESSAGES where AUDSID = &audsid;
AFLOG_ENABLED=TRUE
AFLOG_LEVEL=STATEMENT
AFLOG_MODULE=
AFLOG_FILENAME=
The parameters above take precedence from the profile options. Bounce middle tier services.
For 12.2, backup file: $INST_TOP/appl/admin/oacore_wls.properties. Edit $INST_TOP/appl/admin/oacore_wls.properties and comment out the following lines:
AFLOG_ENABLED=
AFLOG_LEVEL=
AFLOG_MODULE=
AFLOG_FILENAME=
Re-start middle tier services
2. Apache log files:
In rel 12 there is an environment variable $LOG_HOME which is by default the directory under
$INST_TOP.
Log files can be generated in plain text (default) or XML - Oracle Diagnostics Logging (ODL)
2.1. Apache Plain Text Logs:
. Change $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
LogLevel debug
. Or update context variable s_apache_loglevel in the context file
$INST_TOP/appl/admin/<SID_HOSTNAME.xml to set Apache log level, then
run autoconfig
. Files are located at $LOG_HOME/ora/10.1.3/Apache
. There are 2 types of log files:
- Access Log (CustomLog)
Filename format should be like: access_log.<unique id>
- Error Log (ErrorLog) this includes ECID information
Filename format should be like: error_log.<unique id>
2.2. Apache ODL Logs - generates XML log files
. . Change $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
OraLogMode oracle
OraLogSeverity trace:32
. Files are located at $LOG_HOME/ora/10.1.3/Apache/oracle
3. OC4J logging
. In each OC4J instance change
$ORA_CONFIG_HOME/10.1.3/j2ee/<oacore, forms, oafm>/config/j2ee-logging.xml
<logger name='oracle' level='TRACE:1â
. To find the log file location:
. Check $ORA_CONFIG_HOME/10.1.3/j2ee/<oacore, forms, oafm>/application- deployments/<oacore,forms,oafm>/orion-application.xml
. Look for: <log> <file path=...> </log> to specify the log file name.
3.1 - Plain Text Log:
. Located at $LOG_HOME/ora/10.1.3/j2ee/<oacore, forms,
oafm>/<oacore,forms,oafm>_<default_group_1>/application.log
3.2 XML Log:
. Located at $LOG_HOME/ora/10.1.3/j2ee/<oacore, forms,
oafm>/<oacore,forms,oafm>_<default_group_1>/log.xml
4. Check the file version from the Applications (this can be done in 11.5.10 also):
4.1.Go to System Administration (not Administrator) responsibility
4.2. Go to Oracle Applications Manager > Patching and Utilities
4.3. Go to Site Map > Maintenance
4.4. Click Patch History
4.5. Enter in field File Name %<file name>%
Sample: File Name %ResponsePageLevelCO%
4.6. Provide the latest file version
5. Extracting Data Classifications and Items
There is no need to run the extract processes in release 12.0 and higher. The extraction is done
automatically. Enable profile FND: Debug Log Enabled to Yes and follow the steps
from 1.
6. Catalog Bulkload
In rel 12.0 and higher the bulkload file goes directly to the database and not to the concurrent server
like in 11.5.9 and 11.5.10.
Check the concurrent process log file for errors.
To check errors from the database:
SQL> SELECT job_number, job_type, job_status, user_file_name, role, po_header_id,
document_type_code, document_number, org_id, interface_header_id,
lines_processed, lines_failed, failure_message, system_failure_message,
session_id
FROM icx_cat_batch_jobs_all
WHERE job_number = &jobNumber
7. For Workflow debugging execute the steps:
7.1. Set profile PO: Set Debug Workflow ON : Yes
7.2. Bounce middle tier or clear the cache for the profile to take effect
7.3. Reproduce the issue
7.4. Collect the po_wf_debug.log:
. SQL> select wf_item_type, wf_item_key from po_requisition_headers_all where segment1 = ‘&req_number’;
Replace the requisition number
. SQL> select * from apps.po_wf_debug WHERE itemkey = &wf_item_key
and itemtype= 'REQAPPRV' ORDER BY EXECUTION_SEQUENCE;
8. For charge account issues:
8.1. Set Profile Account Generator:Run in Debug Mode to Yes.
8.2. Bounce middle tier or clear the cache for the profile to take effect
8.3. Reproduce the issue
8.4. Collect the file fdfsrvdbg.log in the directory specified by utl_file_dir.
SQL> select value from v$parameter where name = 'utl_file_dir';
8.5. Disable Profile Account Generator:Run in Debug Mode setting to No as the profile cause performance issues in iProcurement and core Purchasing.
B. For 11.5.10 or SC FP J
==================
In 11.5.10 iP is fully OA Framework based. The debug.log file is recorded in FND log files.
1.To enable FND log and get debug.log file execute the below steps. There are three ways to get the debug statements. The statements are generated by the code being executed and it help to troubleshoot the issue.
1.1. Using System Administrator responsibility, set profile option at the user level: FND: Diagnostics = Yes
1.2. Log in with user or responsibility with profile enabled.
1.3 To get the debug online on the page:
1.3.1 In the web page with the issue, append the following to the URL depending on the error:
&aflog_level=STATEMENT&aflog_module=icx*
&aflog_level=STATEMENT&aflog_module=fnd*
&aflog_level=STATEMENT&aflog_module=*
&aflog_level=STATEMENT&aflog_module=por*
The FND log will show up on the same page.OR
1.4 To get the debug in the navigated pages:
1.4.1 Once you enabled FND: Diagnostics to Yes, a link Diagnostics will show up at the top of the page.
1.4.2. Click Diagnostics link.
1.4.3. Use option Show Log on Screen.
1.4.4. Click Go.
1.4.5. Choose Log Level Statement (1).
1.4.6. Enter in Module *
1.4.7. Click Go to generate the log (debug.log).
1.4.8. Execute the steps to reproduce the issue
1.4.9. Copy and paste the entire message generated on the page in a text file
14.10. Click Diagnostics link > Show Log on Screen > Go
1.4.11. Check Turn off screen logging to stop showing the log on the screen
OR
1.5 To get the debug.log in file:
1.5.1.Using System Administrator responsibility, set profile options at the user level:
FND: Log Enabled = Yes
FND: Log Level = Statement
FND: Log Filename = /usr/tmp/debug.log (or any other directory with write privileges)
FND: Log Module = %
Reproduce the issue in the application. Go to /usr/tmp/ and get the debug.log.OR
1.6 To get the debug.log from the table:
1. 6.1 Using System Administrator responsibility, set profile options at the user level:
FND: Debug Log Enabled : Yes
FND: Debug Log Filename : leave it as null
FND: Debug Log Level : Statement
FND: Debug Log Module : icx%
1.6.2. Truncate table APPLSYS.FND_LOG_MESSAGES
1.6.3. Bounce iAS/Apache
1.6.4. Reproduce the issue
1.6.5. Provide the table dump of fnd_log_messages in spreadsheet format.
If truncating the table is not an option:
1.6.6. Check the maximum log sequence from fnd_log_messages executing:
SQL> select max(log_sequence) from fnd_log_messages;
1.6.7. Reproduce the issue
1.6.8. Retrieve the log messages executing the below statement. Upload the results in a spreadsheet format.
SQL> select * from fnd_log_messages where log_sequence > &max_log_sequence;
Replace max_log_sequence from the results from 1.6.6.
2. To get SQL Trace
2.1.Set profile FND: Diagnostics to Yes at user level.
2.2.Login as the above user
2.3. Click on Diagnostics icon.
2.4. Select 'Set Trace Level' and click Go
2.5. Select the desired trace level with binds and waits and click Save
2.6. Perform the activity to reproduce the issue
2.7. Click Diagnostics icon again
2.8. Select 'Set Trace Level' and click Go
2.9. Take note of the all trace file numbers on the left side of the page
2.10 Disable trace
2.11 Find the trace files with contains the number from 2.9.
2.12. Execute tkprof in the trace files
2.13. Upload raw and tkprof files
File is in user_dump_dest specified in init.ora. To check the directory through SQL execute:
SQL> select value from v$parameter where name = 'user_dump_dest';
. To execute tkprof:
$ tkprof (trace file name> <output file name>
. Upload raw and tkprofed files.
To find trace files in 11G and higher:
If using rdbms 11g or higher, the user_dump_dest parameter is ignored. The 11g uses ADR (Automatic Diagnostic Repository) which is a file-based repository for database diagnostic data like traces, core dumps, alert log, Health Monitor reports, etc. The location is set by DIAGNOSTIC_DEST initialization parameter.
Execute query below to find the directory where the trace files reside:
SQL> select value from v$parameter where name = 'diagnostic_dest';
Then, go to <DIAGNOSTIC_DEST>/diag/rdbms/<DB name>/<SID>/trace
to find the files. The directory path under <DIAGNOSTIC_DEST> may differ depending on
the directory set in <DIAGNOSTIC_DEST>. Look for trace directory under <DIAGNOSTIC_DEST>.
3. About This Page
This will list the main files with corresponding version from the page.This is useful to find the versions of files involved where the issue occurs.
At the user level change profile FND: Diagnostics to yes, then click About This Page, and provide the content to Support Services if creating a Service Request.
4. Extracting Data Classifications and Items log files
The log files are in Concurrent Requests View Log. Run extract with log level 100 to get
more details in extract process.
5. Catalog Bulkload log file
Starting in 11.5.9 Catalog Bulkload is a Java concurrent program.
The log file is in Concurrent Requests View Log.
6. To check if the instance is configured properly run the Diagnostics tests from System Administration (not Administrator) responsibility > Diagnostics
. PL/SQL Ping
. JSP Ping
. Servlet Ping
. AOL/J Database Connection Pool Status
. JSP Class Version Information - to check java file versions.
7. How to get BC4J log in 11.5.10
Steps for bc4j logging:
7.1. Edit $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.properties
7.2.Search for a line that reads
wrapper.bin.parameters=-Djava.awt.headless=true
7.3. Right below the above, add the following line:
wrapper.bin.parameters=-Djbo.debugoutput=console
7.4. Save the changes
7.5. Bounce apache ($INST_TOP/admin/scripts/$CONTEXT_NAME/adapcctl.sh stop |
start)
7.6. Reproduce your problem
7.7. Logging information is in the stdout/stderr files:
$IAS_ORACLE_HOME/Apache/Jserv/logs/jvm/OACore*.stdout|.stderr
C. For 11.5.9 (PRC FP I) Catalog and Receiving issues
======================================
Catalog and Receiving pages are OA Framework in 11.5.9.
The page is OA Framework if Personalize links are shown up after enabling profile option
Personalize Self-Service Defn to Yes
To create a log file in 11.5.9:
Using System Administrator responsibility, set profile options at the user or responsibility level: FND: Debug Log Enabled = Yes
FND: Debug Log Level = Statement
FND: Debug Log Filename = /tmp/debug.log
FND: Debug Log Module = %
Reproduce the issue in the application. Go to /tmp/ and get the debug.log.
D. For 11.5.9 (PRC FP I) and lower versions
==============================
1. To get log files in non-OA Framework version turn debug on in iP executing:
1.1 Add the following 3 lines to ssp_init.txt
DebugOutput= /Apache/Apache/logs/debug_log
DebugLevel=5
DebugSwitch=ON
1.2 Save the file ssp_init.txt
1.3 Set log=true in jserv.properties file.
1.4 Shut down apache
1.5 Empty out debug .log, error_log, jserv.log/mod_jserv.log files in /Apache/Apache/logs/
to get a clean file
1.6 Start up apache server
1.7 Reproduce the issue
1.8 Send debug, error_log, and jserv.log, mod_jserv.log files to Oracle Support Services if creating
a Service Request.
2. To get trace file at the database level, the steps are:
2.1. Enable trace parameter in init.ora file:
EVENT="10046 TRACE NAME CONTEXT FOREVER, LEVEL 4"
2.2. Delete all the trace files from where the trace files are been generated. To find the place see
parameter user_dump_dest in init.ora file.
2.3. Bounce database
2.4. Log as the sole user in the application
2.5. Reproduce the issue
2.6. Log off from application
2.7. Disable trace in init.ora file (comment out event parameter)
2.8. Bounce database
2.9. Execute tkprof in the trace files
2.10. Upload tkprofed and raw trace files through Metalink if creating Service Request
3. To get the trace file at the user level:
3.1. Log onto core Applications with the Application Developer responsibility.
3.2. Navigate to the Profile menu.
3.3. Query up the profile name "FND_INIT_SQL"
3.4. In the bottom block of the form, make sure that ALL checkboxes are checked.
Typically, you will have to enable the checkboxes under "User Access" to make
it "Visible" and "Updatable".
3.5. Save changes and exit this form.
3.6. Switch responsibility to System Administrator.
3.7. Navigate: Profile > System.
3.8. On the "Find System Profile Values" form, make sure the checkboxes for "User"
and "Profiles with no Values" are checked.
a. Beside the "User" checkbox use the LOV to select the user who's activity you
need to trace.
b. In the "Profile" field, type: %Initialization% Then click the "Find" button.
3.9. In the "System Profile Values" form, enter the following in the field for
the profile "Initialization SQL Statement - Custom" for the specific User:
begin FND_CTL.FND_SESS_CTL('','', '', 'TRUE','','ALTER SESSION SET
TRACEFILE_IDENTIFIER='||''''||'USERXXX' ||''''||' EVENTS ='||''''||' 10046 TRACE NAME CONTEXT
FOREVER, LEVEL 12 '||''''); end;
NOTE: It is all single quotes. if there is a typo, the user will not be able to login.
Optional to replace USERXXX by the user executing trace.
3.10. Save changes and exit the form.
3.11. Find where the trace files are created in the instance. Check table
v$parameter for user_dump_dest directory location. Delete all trace files from this directory.
3.12. Log onto applications as the user for whom turned on tracing,
and promptly recreate the problem, then log off.
3.13. Execute tkprof in the trace files. Upload the tkprofed trace file(s) created.
3.14. Make sure to clear the "Initialization SQL Statement - Custom" profile
option for the user who's activity you traced.
E. For 11.5.8 (PRC FP H) and lower versions
===============================
1. Extracting Data Classifications and Items log files
The log files are in Concurrent Requests View Log. Run extract with log level 100 to get
more details in extract process log files.
2. Catalog Bulkload log file
There is a tag called DEBUG_CHANNEL which enables
debugging of bulkloader process in the CatalogLoader.conf file. Set it to ON.
Note: Turn off after getting the log file to avoid performance issues.
REFERENCES
NOTE:418926.1 - How to Configure OTA For XML Gateway in Release 12.1NOTE:1340493.1 - How To Trace Performance Issues
NOTE:281530.1 - iProcurement Bulk Loader from an ATG/FND Perspective
NOTE:419839.1 - How to enable Apache, OC4J and OPMN logging in Oracle Applications R12
NOTE:1563168.1 - 12.2 E-Business Suite - How To Enable FND: Debug / AF Logging When Login Is Not Possible
NOTE:1563168.1 - 12.2 E-Business Suite - How To Enable FND: Debug / AF Logging When Login Is Not Possible
NOTE:1366187.1 - Oracle Applications E-Business Suite 12.2 Fusion Middleware Log Files: Locate,View, and Control
NOTE:1642431.1 - Oracle E-Business Suite Mobile Apps Administrator's Guide for Release 12.1 and Release 12.2
| Goal |
| Solution |
| References |
APPLIES TO:
Oracle Supplier Lifecycle Management - Version 12.1.2 and laterOracle Contract Lifecycle Management for Public Sector - Version 12.1.3 and later
Oracle Sourcing - Version 11.5.10 and later
Oracle Purchasing - Version 12.0.6 to 12.2 [Release 12 to 12.2]
Oracle iProcurement - Version 11.5.9 to 12.2.4 [Release 11.5 to 12.2]
Information in this document applies to any platform.
iProcurement - Version: 11.5.9 to 12.0
GOAL
How to get log files in iProcurement according to the Procurement/Supply Chain Family Pack level or Oracle Applications release.
SOLUTION
A. For 12.0, 12.1 and 12.2 (except 2 and 3 for 12.2 which uses WebLogic)
===========================
1. OA Framework debug is similar to release 11.5.10.
For SQL Trace and About this page see 11.5.10 item 2 and 3.
To get the debug.log from the table:
1.1 Using System Administrator responsibility, set profile options at the user level:
FND: Debug Log Enabled : Yes
FND: Debug Log Filename for Middle-Tier : leave it as null
FND: Debug Log Level : Statement
FND: Debug Log Module : %
1.2. Truncate table APPLSYS.FND_LOG_MESSAGES
OR
run concurrent process "Purge Debug Log and System Alerts" under
System Administrator responsibility.
1.3. Bounce iAS/Apache
1.4. Reproduce the issue
1.5. Provide the table dump of fnd_log_messages in spreadsheet format.
If truncating the table is not an option:
1.6. Check the maximun log sequence from fnd_log_messages executing:
SQL> select max(log_sequence) from fnd_log_messages;
1.7. Reproduce the issue
1.8. Check the maximun log sequence again:
SQL> select max(log_sequence) from fnd_log_messages;
1.9. Retrieve the log messages executing the below statement. Upload the results in a spreadsheet
format.
SQL> select * from fnd_log_messages where log_sequence > &max_log_sequence_1_6 and log_sequence < &max_log_sequence_1_8 ;
Replace max_log_sequence from the results from 1.6 and 1.8.
OR
SQL> select * from fnd_log_messages
where user_id=(select user_id from fnd_user
where user_name='&user_name');
To generate the entries in the fnd_log_messages while running a concurrent request program set the following:
1. Enable the profile 'Concurrent: Allow Debugging'
2. Give the debug module as '%' (or the product of the program like 'po%')
3. Before running concurrent program, click 'Diagnostics' button and enable
logging there as well.
4. Collect the entries from fnd_log_messages.
5. Use the AUDSID from the request status log and collect it via SQL like:
SQL> select * from FND_LOG_MESSAGES where AUDSID = &audsid;
AFLOG_ENABLED=TRUE
AFLOG_LEVEL=STATEMENT
AFLOG_MODULE=
AFLOG_FILENAME=
The parameters above take precedence from the profile options. Bounce middle tier services.
For 12.2, backup file: $INST_TOP/appl/admin/oacore_wls.properties. Edit $INST_TOP/appl/admin/oacore_wls.properties and comment out the following lines:
AFLOG_ENABLED=
AFLOG_LEVEL=
AFLOG_MODULE=
AFLOG_FILENAME=
Re-start middle tier services
2. Apache log files:
In rel 12 there is an environment variable $LOG_HOME which is by default the directory under
$INST_TOP.
Log files can be generated in plain text (default) or XML - Oracle Diagnostics Logging (ODL)
2.1. Apache Plain Text Logs:
. Change $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
LogLevel debug
. Or update context variable s_apache_loglevel in the context file
$INST_TOP/appl/admin/<SID_HOSTNAME.xml to set Apache log level, then
run autoconfig
. Files are located at $LOG_HOME/ora/10.1.3/Apache
. There are 2 types of log files:
- Access Log (CustomLog)
Filename format should be like: access_log.<unique id>
- Error Log (ErrorLog) this includes ECID information
Filename format should be like: error_log.<unique id>
2.2. Apache ODL Logs - generates XML log files
. . Change $ORA_CONFIG_HOME/10.1.3/Apache/Apache/conf/httpd.conf
OraLogMode oracle
OraLogSeverity trace:32
. Files are located at $LOG_HOME/ora/10.1.3/Apache/oracle
3. OC4J logging
. In each OC4J instance change
$ORA_CONFIG_HOME/10.1.3/j2ee/<oacore, forms, oafm>/config/j2ee-logging.xml
<logger name='oracle' level='TRACE:1â
. To find the log file location:
. Check $ORA_CONFIG_HOME/10.1.3/j2ee/<oacore, forms, oafm>/application- deployments/<oacore,forms,oafm>/orion-application.xml
. Look for: <log> <file path=...> </log> to specify the log file name.
3.1 - Plain Text Log:
. Located at $LOG_HOME/ora/10.1.3/j2ee/<oacore, forms,
oafm>/<oacore,forms,oafm>_<default_group_1>/application.log
3.2 XML Log:
. Located at $LOG_HOME/ora/10.1.3/j2ee/<oacore, forms,
oafm>/<oacore,forms,oafm>_<default_group_1>/log.xml
4. Check the file version from the Applications (this can be done in 11.5.10 also):
4.1.Go to System Administration (not Administrator) responsibility
4.2. Go to Oracle Applications Manager > Patching and Utilities
4.3. Go to Site Map > Maintenance
4.4. Click Patch History
4.5. Enter in field File Name %<file name>%
Sample: File Name %ResponsePageLevelCO%
4.6. Provide the latest file version
5. Extracting Data Classifications and Items
There is no need to run the extract processes in release 12.0 and higher. The extraction is done
automatically. Enable profile FND: Debug Log Enabled to Yes and follow the steps
from 1.
6. Catalog Bulkload
In rel 12.0 and higher the bulkload file goes directly to the database and not to the concurrent server
like in 11.5.9 and 11.5.10.
Check the concurrent process log file for errors.
To check errors from the database:
SQL> SELECT job_number, job_type, job_status, user_file_name, role, po_header_id,
document_type_code, document_number, org_id, interface_header_id,
lines_processed, lines_failed, failure_message, system_failure_message,
session_id
FROM icx_cat_batch_jobs_all
WHERE job_number = &jobNumber
7. For Workflow debugging execute the steps:
7.1. Set profile PO: Set Debug Workflow ON : Yes
7.2. Bounce middle tier or clear the cache for the profile to take effect
7.3. Reproduce the issue
7.4. Collect the po_wf_debug.log:
. SQL> select wf_item_type, wf_item_key from po_requisition_headers_all where segment1 = ‘&req_number’;
Replace the requisition number
. SQL> select * from apps.po_wf_debug WHERE itemkey = &wf_item_key
and itemtype= 'REQAPPRV' ORDER BY EXECUTION_SEQUENCE;
8. For charge account issues:
8.1. Set Profile Account Generator:Run in Debug Mode to Yes.
8.2. Bounce middle tier or clear the cache for the profile to take effect
8.3. Reproduce the issue
8.4. Collect the file fdfsrvdbg.log in the directory specified by utl_file_dir.
SQL> select value from v$parameter where name = 'utl_file_dir';
8.5. Disable Profile Account Generator:Run in Debug Mode setting to No as the profile cause performance issues in iProcurement and core Purchasing.
B. For 11.5.10 or SC FP J
==================
In 11.5.10 iP is fully OA Framework based. The debug.log file is recorded in FND log files.
1.To enable FND log and get debug.log file execute the below steps. There are three ways to get the debug statements. The statements are generated by the code being executed and it help to troubleshoot the issue.
1.1. Using System Administrator responsibility, set profile option at the user level: FND: Diagnostics = Yes
1.2. Log in with user or responsibility with profile enabled.
1.3 To get the debug online on the page:
1.3.1 In the web page with the issue, append the following to the URL depending on the error:
&aflog_level=STATEMENT&aflog_module=icx*
&aflog_level=STATEMENT&aflog_module=fnd*
&aflog_level=STATEMENT&aflog_module=*
&aflog_level=STATEMENT&aflog_module=por*
The FND log will show up on the same page.OR
1.4 To get the debug in the navigated pages:
1.4.1 Once you enabled FND: Diagnostics to Yes, a link Diagnostics will show up at the top of the page.
1.4.2. Click Diagnostics link.
1.4.3. Use option Show Log on Screen.
1.4.4. Click Go.
1.4.5. Choose Log Level Statement (1).
1.4.6. Enter in Module *
1.4.7. Click Go to generate the log (debug.log).
1.4.8. Execute the steps to reproduce the issue
1.4.9. Copy and paste the entire message generated on the page in a text file
14.10. Click Diagnostics link > Show Log on Screen > Go
1.4.11. Check Turn off screen logging to stop showing the log on the screen
OR
1.5 To get the debug.log in file:
1.5.1.Using System Administrator responsibility, set profile options at the user level:
FND: Log Enabled = Yes
FND: Log Level = Statement
FND: Log Filename = /usr/tmp/debug.log (or any other directory with write privileges)
FND: Log Module = %
Reproduce the issue in the application. Go to /usr/tmp/ and get the debug.log.OR
1.6 To get the debug.log from the table:
1. 6.1 Using System Administrator responsibility, set profile options at the user level:
FND: Debug Log Enabled : Yes
FND: Debug Log Filename : leave it as null
FND: Debug Log Level : Statement
FND: Debug Log Module : icx%
1.6.2. Truncate table APPLSYS.FND_LOG_MESSAGES
1.6.3. Bounce iAS/Apache
1.6.4. Reproduce the issue
1.6.5. Provide the table dump of fnd_log_messages in spreadsheet format.
If truncating the table is not an option:
1.6.6. Check the maximum log sequence from fnd_log_messages executing:
SQL> select max(log_sequence) from fnd_log_messages;
1.6.7. Reproduce the issue
1.6.8. Retrieve the log messages executing the below statement. Upload the results in a spreadsheet format.
SQL> select * from fnd_log_messages where log_sequence > &max_log_sequence;
Replace max_log_sequence from the results from 1.6.6.
2. To get SQL Trace
2.1.Set profile FND: Diagnostics to Yes at user level.
2.2.Login as the above user
2.3. Click on Diagnostics icon.
2.4. Select 'Set Trace Level' and click Go
2.5. Select the desired trace level with binds and waits and click Save
2.6. Perform the activity to reproduce the issue
2.7. Click Diagnostics icon again
2.8. Select 'Set Trace Level' and click Go
2.9. Take note of the all trace file numbers on the left side of the page
2.10 Disable trace
2.11 Find the trace files with contains the number from 2.9.
2.12. Execute tkprof in the trace files
2.13. Upload raw and tkprof files
File is in user_dump_dest specified in init.ora. To check the directory through SQL execute:
SQL> select value from v$parameter where name = 'user_dump_dest';
. To execute tkprof:
$ tkprof (trace file name> <output file name>
. Upload raw and tkprofed files.
To find trace files in 11G and higher:
If using rdbms 11g or higher, the user_dump_dest parameter is ignored. The 11g uses ADR (Automatic Diagnostic Repository) which is a file-based repository for database diagnostic data like traces, core dumps, alert log, Health Monitor reports, etc. The location is set by DIAGNOSTIC_DEST initialization parameter.
Execute query below to find the directory where the trace files reside:
SQL> select value from v$parameter where name = 'diagnostic_dest';
Then, go to <DIAGNOSTIC_DEST>/diag/rdbms/<DB name>/<SID>/trace
to find the files. The directory path under <DIAGNOSTIC_DEST> may differ depending on
the directory set in <DIAGNOSTIC_DEST>. Look for trace directory under <DIAGNOSTIC_DEST>.
3. About This Page
This will list the main files with corresponding version from the page.This is useful to find the versions of files involved where the issue occurs.
At the user level change profile FND: Diagnostics to yes, then click About This Page, and provide the content to Support Services if creating a Service Request.
4. Extracting Data Classifications and Items log files
The log files are in Concurrent Requests View Log. Run extract with log level 100 to get
more details in extract process.
5. Catalog Bulkload log file
Starting in 11.5.9 Catalog Bulkload is a Java concurrent program.
The log file is in Concurrent Requests View Log.
6. To check if the instance is configured properly run the Diagnostics tests from System Administration (not Administrator) responsibility > Diagnostics
. PL/SQL Ping
. JSP Ping
. Servlet Ping
. AOL/J Database Connection Pool Status
. JSP Class Version Information - to check java file versions.
7. How to get BC4J log in 11.5.10
Steps for bc4j logging:
7.1. Edit $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.properties
7.2.Search for a line that reads
wrapper.bin.parameters=-Djava.awt.headless=true
7.3. Right below the above, add the following line:
wrapper.bin.parameters=-Djbo.debugoutput=console
7.4. Save the changes
7.5. Bounce apache ($INST_TOP/admin/scripts/$CONTEXT_NAME/adapcctl.sh stop |
start)
7.6. Reproduce your problem
7.7. Logging information is in the stdout/stderr files:
$IAS_ORACLE_HOME/Apache/Jserv/logs/jvm/OACore*.stdout|.stderr
C. For 11.5.9 (PRC FP I) Catalog and Receiving issues
======================================
Catalog and Receiving pages are OA Framework in 11.5.9.
The page is OA Framework if Personalize links are shown up after enabling profile option
Personalize Self-Service Defn to Yes
To create a log file in 11.5.9:
Using System Administrator responsibility, set profile options at the user or responsibility level: FND: Debug Log Enabled = Yes
FND: Debug Log Level = Statement
FND: Debug Log Filename = /tmp/debug.log
FND: Debug Log Module = %
Reproduce the issue in the application. Go to /tmp/ and get the debug.log.
D. For 11.5.9 (PRC FP I) and lower versions
==============================
1. To get log files in non-OA Framework version turn debug on in iP executing:
1.1 Add the following 3 lines to ssp_init.txt
DebugOutput= /Apache/Apache/logs/debug_log
DebugLevel=5
DebugSwitch=ON
1.2 Save the file ssp_init.txt
1.3 Set log=true in jserv.properties file.
1.4 Shut down apache
1.5 Empty out debug .log, error_log, jserv.log/mod_jserv.log files in /Apache/Apache/logs/
to get a clean file
1.6 Start up apache server
1.7 Reproduce the issue
1.8 Send debug, error_log, and jserv.log, mod_jserv.log files to Oracle Support Services if creating
a Service Request.
2. To get trace file at the database level, the steps are:
2.1. Enable trace parameter in init.ora file:
EVENT="10046 TRACE NAME CONTEXT FOREVER, LEVEL 4"
2.2. Delete all the trace files from where the trace files are been generated. To find the place see
parameter user_dump_dest in init.ora file.
2.3. Bounce database
2.4. Log as the sole user in the application
2.5. Reproduce the issue
2.6. Log off from application
2.7. Disable trace in init.ora file (comment out event parameter)
2.8. Bounce database
2.9. Execute tkprof in the trace files
2.10. Upload tkprofed and raw trace files through Metalink if creating Service Request
3. To get the trace file at the user level:
3.1. Log onto core Applications with the Application Developer responsibility.
3.2. Navigate to the Profile menu.
3.3. Query up the profile name "FND_INIT_SQL"
3.4. In the bottom block of the form, make sure that ALL checkboxes are checked.
Typically, you will have to enable the checkboxes under "User Access" to make
it "Visible" and "Updatable".
3.5. Save changes and exit this form.
3.6. Switch responsibility to System Administrator.
3.7. Navigate: Profile > System.
3.8. On the "Find System Profile Values" form, make sure the checkboxes for "User"
and "Profiles with no Values" are checked.
a. Beside the "User" checkbox use the LOV to select the user who's activity you
need to trace.
b. In the "Profile" field, type: %Initialization% Then click the "Find" button.
3.9. In the "System Profile Values" form, enter the following in the field for
the profile "Initialization SQL Statement - Custom" for the specific User:
begin FND_CTL.FND_SESS_CTL('','', '', 'TRUE','','ALTER SESSION SET
TRACEFILE_IDENTIFIER='||''''||'USERXXX' ||''''||' EVENTS ='||''''||' 10046 TRACE NAME CONTEXT
FOREVER, LEVEL 12 '||''''); end;
NOTE: It is all single quotes. if there is a typo, the user will not be able to login.
Optional to replace USERXXX by the user executing trace.
3.10. Save changes and exit the form.
3.11. Find where the trace files are created in the instance. Check table
v$parameter for user_dump_dest directory location. Delete all trace files from this directory.
3.12. Log onto applications as the user for whom turned on tracing,
and promptly recreate the problem, then log off.
3.13. Execute tkprof in the trace files. Upload the tkprofed trace file(s) created.
3.14. Make sure to clear the "Initialization SQL Statement - Custom" profile
option for the user who's activity you traced.
E. For 11.5.8 (PRC FP H) and lower versions
===============================
1. Extracting Data Classifications and Items log files
The log files are in Concurrent Requests View Log. Run extract with log level 100 to get
more details in extract process log files.
2. Catalog Bulkload log file
There is a tag called DEBUG_CHANNEL which enables
debugging of bulkloader process in the CatalogLoader.conf file. Set it to ON.
Note: Turn off after getting the log file to avoid performance issues.
REFERENCES
NOTE:418926.1 - How to Configure OTA For XML Gateway in Release 12.1NOTE:1340493.1 - How To Trace Performance Issues
NOTE:281530.1 - iProcurement Bulk Loader from an ATG/FND Perspective
NOTE:419839.1 - How to enable Apache, OC4J and OPMN logging in Oracle Applications R12
NOTE:1563168.1 - 12.2 E-Business Suite - How To Enable FND: Debug / AF Logging When Login Is Not Possible
NOTE:1563168.1 - 12.2 E-Business Suite - How To Enable FND: Debug / AF Logging When Login Is Not Possible
NOTE:1366187.1 - Oracle Applications E-Business Suite 12.2 Fusion Middleware Log Files: Locate,View, and Control
NOTE:1642431.1 - Oracle E-Business Suite Mobile Apps Administrator's Guide for Release 12.1 and Release 12.2