11i Logs
Upcoming SlideShare
Loading in...5
×
 

11i Logs

on

  • 3,133 views

This is a presentation that identifies the various components of the 11i technology stack and how to generate log files for them for troubleshooting and debugging.

This is a presentation that identifies the various components of the 11i technology stack and how to generate log files for them for troubleshooting and debugging.

Statistics

Views

Total Views
3,133
Views on SlideShare
3,125
Embed Views
8

Actions

Likes
0
Downloads
78
Comments
0

2 Embeds 8

http://www.slideshare.net 7
http://www.linkedin.com 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

11i Logs 11i Logs Presentation Transcript

  • Mahesh Vallampati
    • 100% Internet Based.
    • Eliminates Barriers for running “single instance” for applications.
    • Three Tiered Distributed Computing.
    • Frontend Complexity Eliminated.
    • Backend Complexity Increased.
    • Install the Oracle Applications suite with all the desired modules to be implemented.
    • Maximize the use of available functionality within the application by modifying business processes whenever efficient.
    • Customize the Oracle Application suite for business processes that cannot be modified keeping in mind that customizations impact the ability to upgrade and support by the vendor.
    • Deploy the applications and be able to meet business, performance and operational requirements.
    • Database Tier running Oracle 8i
    • Application Tier running Oracle Applications and other tools.
    • Desktop Tier for the user interface from a Java Enabled Internet Browser.
    • Database Tier Logs
    • Application Tier Logs
    • Desktop Tier Logs
    • Database Logs defined in init<DBNAME>.ora
      • User Dump Destination (user_dump_dest)
      • Core Dump Destination (core_dump_dest)
      • Background Dump Destination (background_dump_dest)
      • Control size of trace files using the parameter “max_dump_file_size”
      • Monitor alert_<DBNAME>.log for significant database events.
    • Database Listener log files specified in listener.ora
      • LOG_DIRECTORY_<DBNAME> specifies the log directory.
      • LOG_FILE_<DBNAME> specifies the log file name.
      • TRACE_DIRECTORY_<DBNAME> specifies the log directory.
      • TRACE_FILE_<DBNAME> specifies the log file name.
      • TRACE_LEVEL_<DBNAME> for tracing levels.
    • Monitor alert_<DBNAME>.log to proactively find out issues with the database.
    • Check bdump,udump and cdump for too many files which could hint at problems ahead.
    • To do network tracing set the appropriate level for tracing and use trcasst to get detailed information on network traffic and other relevant information.
    • Periodically, backup and recycle the alert_<DBNAME>.log and other log and trace files.
    • Concurrent Manager
    • Forms Listener
    • Apache Listener
    • Forms Metrics Server Listener
    • Forms Metrics Client Listener
    • Reports Server
    • Applications Listener
    • Thin Client Framework Server
    • APPLCSF determines the logging approach
      • Null specifies that log files get directed to the product/module top’s log and out file directory.
      • A specific directory implies that all out and log files get stored in that directory.
      • Some modules like manufacturing generate a lot of log and out files for processes which run every few minutes.
      • APPLLOG and APPLOUT determines the name of the log and out directories. (log and out are default).
    • Internal manager logs are available in $FND_TOP/$APPLLOG or in $APPLCSF/$APPLLOG directories in the format <mgrname>.mgr
    • Concurrent Program logs are available in $MODULE_TOP/$APPLLOG or in $APPLCSF/$APPLLOG directories in the format l<Conc.Req.Id>.req
    • Concurrent Manager logs are available in $FND_TOP/$APPLLOG or in $APPLCSF/$APPLLOG directories in the format w<conc.proc.id>.mgr.
    • Log files can be accessed from application also.
    • Purge Concurrent Manager program and log files from the server in concert with purging concurrent request information from the database tables.
    • Monitor the internal manager log file for information about various concurrent managers and their statuses.
    • Purge output files from the server the same way you purge concurrent program files.
    • Monitor disk usage of concurrent log and out files.
    • Forms Listener has three components
      • Forms Metrics Server Listener
      • Forms Metrics Clients Listener
      • Forms Listener
    • The forms metrics client listener is invoked by running the script adfmcctl.sh.
    • The log file for the listener is determined by the FRMLOG parameter in the file.
    • Modify this parameter for the file to be generated in a custom directory.
    • The file is d2lc60.txt
    • The forms metrics Server listener is invoked by running the script adfmsctl.sh.
    • The log file for the listener is determined by the FRMLOG parameter in the file.
    • Modify this parameter for the file to be generated in a custom directory.
    • The file is d2ls60.txt
    • The forms metrics Server listener is invoked by running the script adfrmctl.sh.
    • The log file for the listener is determined by the FRMLOG parameter in the file.
    • Modify this parameter for the file to be generated in a custom directory.
    • The file is f60svrm.txt
    • Set debug_mode=1 to generate logs for startup.
    • appsweb.cfg in the $OA_HTML/bin directory contains entries for tracing and logging.
    • Set the value for the parameter “record” to one of the following.
      • Performance : Records server events timings into log file
      • Collect : Records Runtime Diagnostic data into log file
      • All : Records Diagnostic and Performance data
      • Names : Adds UI names to messeges, no log generated
      • PECS : Old performance data saved into log file
    • Use “log” parameter to define location and name of log file.
    • Apache Errors are written to the log file specified by the ErrorLog parameter in the httpd(s).conf file.
    • The various log levels are: debug, info, notice, warn, error, crit (for critical),alert, emerg.
    • Other logs for access, referer, agent or combined can be specified in the httpd(s).conf file.
    • We recommend that we leave the httpds.pid and the ssl_mutex files to be left in the default location.
    • Jserv info which is also served by the Apache server has logs which is specified by jserv.conf.
    • The parameter is specified in the jserv.conf file by the ApJServLogFile parameter. This is the mod_jserv.log file.
    • The ApJServLogLevel parameter specifies the kind of logging which can be one of: [debug|info|notice|warn|error|crit|alert|emerg]
    • The jserv.properties file contains wrapper-bin parameters which contains jserv logging. Set them to point to the custom directory.
    • Also set log=true and the log.file parameter to point to the custom directory. There are several log.* parameter which can be set to trigger various kinds of logging events.
    • The configurator use the jserv cartridge and the files are dumped here.
    • iProcurement logs can be specified in the ssp_init.txt file in the Jserv/etc/ directory.
    • The following parameters need to be set.
      • DebugOutput=<Directory/File name>
      • DebugLevel=5
      • DebugSwitch=ON
    • These debug files are useful in troubleshooting iProcurement files.
    • Thin Client Framework logs can be obtained by using parameters when starting up the TCF Listener process.
    • The parameters are
      • DEBUG (True or False)
      • OUTPUT_FILE (Path to Output File)
      • LOGLEVEL (One of [ERROR|EXCEPTION|EVENT|PROCEDURE|STATEMENT]
      • LOGMODULE*=[<product name>|<oracle.apps>]
    • The script adtcfctl.sh script which starts up needs to be customized with these options to log information to be debugged.
    • The information in the output file can be used to debug issues with processes using the TCF Server.
    • The script adrepctl.sh starts up the Reports Listener.
    • The LOGFILE in the startup script can be used to setup the logging.
    • The applications listener serves the FNDFS process.
      • LOG_DIRECTORY_<DBNAME> specifies the log directory.
      • LOG_FILE_<DBNAME> specifies the log file name.
      • TRACE_DIRECTORY_<DBNAME> specifies the log directory.
      • TRACE_FILE_<DBNAME> specifies the log file name.
      • TRACE_LEVEL_<DBNAME> for tracing levels.
    • All the Logs mentioned above in the document can be stored in a directory separate from the other main directories and organized for fast access of the logs which will aid in troubleshooting.
    • A preliminary directory structure is given below.
    • This should be used as a starting point for the various logs.
    • Scripts could be written to backup and recycle the logs and trace files stored in these directories.
    • Database
      • Listener
      • Oracle
        • Bdump
        • Cdump
        • Udump
    • Application
      • Concman
        • Log
        • Out
      • Forms
        • Listener
        • MetricsServer
        • MetricsClient
      • Apache
        • Apache
        • Jserv
        • Jdk
        • ssp5
      • TCF
      • ApplicationsListener
      • ReportsServer
    • This is a recommended directory structure to hold all the log files. These directories can be backed up every time there is a startup/shutdown sequence for the applications. The log files should also be purged so they don’t grow in size out of proportion.
    • On the desktop, Oracle use the Jinitiator program to run several e-business modules.
    • The jinitiator has a control panel. On the Basic pane of the jinitiator, there is a check box for “Show Java Console”. Enabling this checkbox will help in troubleshooting issues with Oracle Applications.
    • On the advanced Pane, there is a checkbox for debug settings which could be used for the same purpose.
    • Sometimes, clearing the Jcache directory under the Jinitiator directory could help in solving issues with logging into Oracle Applications.
  • Q & Q U E S T I O N S A N S W E R S