BRIEF DESCRIPTION of LOG FILES

As a part of understanding Oracle Apps all the beginner must understand this ".req",".log","rti" and log files.
As we know that, when ever any Concurrent Request is submitted, log and output files are stored in $APPLCSF/$APPLOG and $APPLCSF/$APPLOUT directories respectively.

Apart from concurrent request files, some other files are also getting stored in the same directory.

Those brief description  in this  blog.

1.       l<Request ID>.req                      example “l1420978.req”

This is the Concurrent Request log file. When any concurrent request is submitted, request log file is created in this directory with file name as l<Request ID>.req

Inside of this Request File
+---------------------------------------------------------------------------+
Application Object Library: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

FNDWFLSC module: Synchronize WF LOCAL tables

+---------------------------------------------------------------------------+

Current system time is 11-MAR-2011 00:31:11

+---------------------------------------------------------------------------+

**Starts**11-MAR-2011 00:31:11

**Ends**11-MAR-2011 00:31:13

+---------------------------------------------------------------------------+

Start of log messages from FND_FILE

+---------------------------------------------------------------------------+

+---------------------------------------------------------------------------+

End of log messages from FND_FILE

+---------------------------------------------------------------------------+

+---------------------------------------------------------------------------+

Executing request completion options...

+------------- 1) PRINT   -------------+

Printing output file.

               Request ID : 1418182

         Number of copies : 0

                  Printer : noprint

+--------------------------------------+

Finished executing request completion options.

+---------------------------------------------------------------------------+

Concurrent request completed successfully

Current system time is 11-MAR-2011 00:31:13

+---------------------------------------------------------------------------+

"l1418182.req" 43L, 1510C                                       

2.      Events####.log                           example “Events117.log”

This Events####.log contains information of log written by adstrtal.sh when any problem with starting of middle tier applications (sh adstrtall.sh is  a shell script to start all the middle tier application , remember the script locations in R12 and 11i  )

 3.   Error####.log                             example “Errors118.log”

It contains the Java Exception Errors.

4.      #####.log                                     example “03111123.log”

This file keeps the information of starting of Apache Listener.

Inside of this Apache Listener file follows



Setting service Oracle Apache Server TEST_ibm to mode 3

Executing service control script:

/ebiz/testappl/testcomn/admin/scripts/TEST_ibm/adapcctl.sh stop

Timeout specified in context file: 100 second(s)

script returned:

****************************************************

adapcctl.sh version 115.54

Apache Web Server Listener :httpd ( pid 27449 ) is running.

Stopping Apache Web Server Listener (dedicated HTTP) ...

Apache Web Server Listener (PLSQL) :httpd ( pid 27557 ) is running.

Stopping Apache Web Server Listener (dedicated PLSQL) ...

adapcctl.sh: exiting with status 0

.end std out.

.end err out.

5.      f60webmx_dump_<PID>                       example “f60webmx_dump_11299”

This file is created when ever any Client Forms Session ends Unexpectedly. When user forms session got crash or terminated abruptly that diagnostics information is written into this dump file.  



Inside of this file if unexpected close of Client forms session looks like this:

[Tue Mar  8 13:24:34 2011 IST]::Client Status [ConnId=83, PID=11299]

        >> Network connection to client failed: timeout on connection

Possible causes include a network failure or client termination

~

6.       em_<PID>.rti                                          example “em_10984.rti”

This file contains Client run time process information. These files are used by Oracle Application Manager and Enterprise Manager for Forms Monitoring Services and are generated by Forms runtime processes. For each f60webmx session, there is one .rti file is created. These files are written to the directory set by parameter $FORMS60_RTI_DIR.


 By default these are written into $APPLCSF/$APPLLOG directory. RTI files should be automatically cleaned up when user logs out of the forms session, in case user logs out of the forms sessions abruptly. Then these files are not cleaned up properly. So then you may need to clear these files manually. We can delete the files, but we should not delete these files when users are active.


em –> enterprise manager
<PID> –> Process ID of Client
rti –< Run time information In some cases


.rti file contains:

listener = ibm_9001_TEST

pid = 10984

connect = Thu Mar 10 19:20:01 2011 IST

ip = 172.16.1.105:51423

user = APPLSYSPUB

 ****Note:

                  This above details are for basic understanding of log files, kindly follow search more documents in metalink, that will be more useful than any other.