• Find us:
    +1-669-900-5138   |   +44-203-372-5553
  • Free Newsletter

    Get Latest Updates

  • Make Training Enquiry


  • Categories

  • Archive

  • Log files in $APPLCSF/$APPLLOG directory

    Posted by "" in "11i" on 2008-01-12

    Share on FacebookTweet about this on TwitterShare on Google+Share on LinkedInEmail this to someone

                                    I would like to share some important things here. You all might know these, but Oracle Apps newbie will get benefited. 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 *.req files, some other files are also getting stored in $APPLCSF/$APPLOG directory. I would like to give brief description about these files. These are the following files which are getting stored in that directory.

     (a) l<Request ID>.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

    (b) Events####.log

    adstrtal.sh script writes the log information in to this file, when ever there is any problem with starting of any Application Service.

    (c) Error####.log

    This file contains the Java Exception Errors.

    (d) #####.log

    This file keeps the information of starting of Apache Listener.

     (e) f60webmx_dump_<PID>

    This file is created when ever any Client Forms Session ends abruptly. When user forms session got crash or terminated abruptly that diagnostics information is written into this dump file.  If you want to get rid out of this dump files. Please execute the following stepsSet the FORMS60_CATCHTERM = 0 in Registry (NT) or Environment Variable (Unix/Linux) and bounce the Forms Services

    (f) em_<PID>.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,

    we need to delete the FNDCPPUR program log files and output files manually to free up the disk space. Here I am giving UNIX commands to find out and deleting the old files. If your FNDCPPUR program is scheduled to run daily and given AGE Mode value as 7, purge Program has to delete the files which are older than 7 days. But if program did not delete the files, use this command to find out those files.

     Find the Concurrent Request Log and Output files which are not deleted

     find $APPLCSF/$APPLLOG -mtime +7 -name “*.req”

     find $APPLCSF/$APPLOUT -mtime +7 -name “*.out

    Delete the Concurrent Request log and output files which are older than 7 Days

     find $APPLCSF/$APPLLOG -mtime +7 -name “*.req” -exec rm “{}” “;”

     find $APPLCSF/$APPLOUT -mtime +7 -name “*.out” -exec rm “{}” “;”

    Delete other files in $APPLCSF/$APPLLOG directory

    find $APPLCSF/$APPLLOG -mtime +7 -name “*.log” -exec rm “{}” “;”

    find $APPLCSF/$APPLLOG -mtime +7 -name “*.mgr” -exec rm “{}” “;”

    find $APPLCSF/$APPLLOG -mtime +7 -name “f60webmx*” -exec rm “{}” “;”

    find $APPLCSF/$APPLLOG -mtime +7 -name “*.rti” -exec rm “{}” “;”


     (1) What Are .RTI and .FLI Files? Doc ID: Note: 470850.1

     (2) Oracle Forms in Applications FAQ Doc ID: Note: 177610.1

    27 Responses to “Log files in $APPLCSF/$APPLLOG directory”

    1. Atul says:

      Nice Post Subbu, Hope to see some more posts from you in near future

    2. SubbaRao says:

      Thank you Atul,

      Its a great honour to write articles in this site.

      Thanks alot.


    3. arvind says:

      I just wanted to know the location for $APPLCSF; what is the default location.

    4. Atul says:

      For R12 its


      For 11i its in $COMMON_TOP/admin or $INSTALL_BASE/comn/admin

    5. SubbaRao says:

      Hi Aravind,

      As Atul Said, for the default location you can check in Autoconfig Context File (XML File). XML file will be in $INST_TOP/appl/admin directory.

      Default Location for APPLCSF is

      $INST_TOP/logs/appl/conc directory. If you want to change it, you can edit your location in XML file and run the autoconfig. now you are done.


    6. arvind says:

      Thanks Atul and Subba for this information.

    7. arvind says:


      Can you please tell me step by step procedure for Rapid cloning. One more thing in which scenario we don’t require preclone? What is the purpose of preclone?


    8. Amit says:

      Hi Arvind,

      Preclone basically collect the conf files and templated of source and stores in a Staged Clone directory. This is used when you run adcfgclone.pl on target. Also Step by step procedure for cloning is mentioned in “Back to Basics of Cloning ” Post that is in details of Cloning.

      Also there are scenerios where customization of Rapid clone methos is required and we need not run the preclone but that is not supported by Oracle.

      Let me know if you have any confusion.


    9. arvind says:


      Can some one please tell me how to recover my context file (for both db and apps tier), if removed?
      Is adadmin utility will help here?


    10. Atul says:

      You can recreate them by using adbldxml script (Rebuild XML file)

    11. Hi all. I would like to know if deleting the .req files manually(without any purge script) could cause the apps to behave erratically?

    12. SubbaRao says:


      You can delete the requests files manually. But always recommended is to use the “Purge Concurrent Requests/Manager Data” to delete the concurrent requests information from tables and operating system.

      Hope it helps,


    13. Mike says:

      Thanks for the post .It was a great place to start and very encouraging too .
      There are a few changes to the contents of the original post

      ***.log is not an apache log file .It actually logs information about middle tier servers and services during and recycle.This information was culled by reading the contents of the log file.

      Events####.log is related to the logging in the fulfillment server not adstrtal.sh.
      ML 601375.1 .
      Again thanks for your help


    14. laksha says:

      In my $APPLCSF/$APPLOUT directory there are many files with ctl and dat extension of the format
      what are these files and it it safe to delete these files?
      I have scheduled “Purge Concurrent Request and/or Manager Data” on daily basis but this does not delete the ctl and dat files.

    15. SubbaRao says:

      Hi Laksha,

      I am not sure about those.

      the following metalink notes might be helpful

      Why are .dat .ctl Temp Files being Created by the Memory Based Planner? Doc ID: 152056.1

      MRP MPS ASCP .DAT and .CTL Files Left Over From Memory Based Planner Doc ID: 112851.1

      Memory Based Planner FAQ Doc ID: 111691.1


    16. Ash says:

      where does adworker log files are stored

    17. SubbaRao says:

      Hi Ash,

      for adworker log files, please check the below location


      Note: PROD is the Database Instance Name. Substitue this value according to your Database Instanance Name

      and look for adworker*.log files

      Hope it helps,


    18. Abuzaid says:

      Dear ALL;
      Thanks for the good Article.
      I configure concurrent Manager for “Purge ..or .. ” and Age is 50 days..and ALL.
      but I find 70GB files from 2007,2008 still exists, ..
      please advise.

    19. Avu says:


      I just want to know the effect on performance of deleting Concurrent logs from the Production server, Secondly I tried the “Purge Concurrent Requests/Manager Data” on a Test server but it took a very long time to finish, why this and what is the effect on performance? Lastly how often should this be done?

    20. Atul Kumar says:

      @ Avu,
      Yes, purging Concurrent Requests/Manager Data will improve performance specially around view output and logs for concurrent request.

      Frequency : depeneds on number of concurrent request you generate . On an average scheduling this every 2 weeks is good enough .

      Why Purge was slow on test server ? : Well this depends on number of factors like
      a) Number of concurrent request eligible to be purged
      b) size of server
      c) load on server
      d) Any locks/hangs in database

    21. chandru says:


      We have migrated the forms application server from forms6i to forms10g and we want to retain the rti files for a specified period of time. There are some rti related parameters like 1. RTI_KEEP_DAYS am not sure where to set this. Kindly help me on this issue.

    22. Atul Kumar says:

      @ chandru,

      RTI files are generated by the forms runtime processes.

      Set them in to Form Server Configuration Files at

      This file is replacement of formservlet.ini in 11i

    23. wajid iqbal says:

      hy atul bhiya
      what a gr8 knowldge u have, i m realy gr8 fan of u , whould that u b here kiss ur forehead,
      may u live long, love u dear,amoooah,tc

    24. mrmuds says:

      Where do the files which we upload from OAF gets stored. For example we upload a .rtf file for xml outputs. where does this rtf file gets stored?

      thank you

    25. anil singh says:




    26. anil singh says:


    27. Atul Kumar says:

      @ Anil Singh,
      You should not directly delete files but use purge concurrent program which should delete tmp/out files and old requests.

      If files are deleted restore from backup in order to view output/log

    Leave a Reply

  • K21 Technologies is among the most experienced Oracle Gold Partner for Identity Access Management service providers. We work with application development companies and in-house technology division to help achieve significant returns on their IT security investment. Our clientele includes some of the globally renowned corporate, which speaks of our expertise in our field.

    We have the most talented and experienced team that can swiftly deploy security solutions even in complex IT ecosystem. Our clients highly appreciate our timely implementation, interactive training, on-demand support and community resources.

    K21 Technologies
    8 Magnolia Place, Harrow,
    London, HA2 6DS

    UK: +44(0)7476444481
    USA: +1-888-414-1821

  • 2014, K21 Technologies. All rights reserved DMCA.com
  • TOP