How To Get Log, Trace Files In OA Framework Pages And Concurrent Request Programs

Goal

Solution

References

---

APPLIES TO:

Oracle Supplier Lifecycle Management - Version 12.1.2 and later
Oracle 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; 

            

If the log is not generating or it is showing only plsql but not java class entries check the file $ORA_CONFIG_HOME/10.1.3/j2ee/oacore/config/oc4j.properties and comment out the following entries:
                       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