11i Logs

2,244 views
2,130 views

Published on

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.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,244
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
83
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

11i Logs

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

×