How To Enable Tracing For Discoverer 10g (10.1) Portlet Issues [ID 370337.1]

		Modified 09-OCT-2008 Type TROUBLESHOOTING Status PUBLISHED

In this Document
Goal
Solution

---

Applies to:

Oracle Discoverer - Version: 10.1.2 to 10.1.2
Information in this document applies to any platform.

Goal

Explain in simple steps, how to create a diagnostic trace for Discoverer 10g (10.1.2) PortletProvider to diagnost portlet issues or provide to Oracle Support.

Solution

1. Stop the middle-tier (opmnctl stopall) or OC4J_BI_Forms and Discoverer at a minimum.
   
   
2. Delete (or rename and delete if you prefer to keep) the applicaion.log file:
   $ORACLE_HOME/j2ee/OC4J_BI_Forms/application-deployments/discoverer/OC4J_BI_Forms_default_island_1/application.log
   
   Note: you will have one applicaton.log for each JVM you have configured.
   For example:OC4J_BI_Forms_default_island_1, OC4J_BI_Forms_default_island_2
   
   Use the following command to find all the Discoverer application.log(s).
   
   cd $ORACLE_HOME
   find . -name 'application.log' | grep discoverer
   
   
3. Set the PortletProvider logLevel to "trace" and diagnostic framework logkey to "disco.portlet.debug".
   Edit: $ORACLE_HOME/discoverer/config/configuration.xml
   
   
   change line:
FROM:
<!-- Portlet Provider configuration. -->
<portlet logKey="disco.portlet.fatal" logLevel="error" pickerCompatibleVersions="10.1.2" maxDataRows="1000">

TO:
<!-- Portlet Provider configuration. -->
<portlet logKey="disco.portlet.debug" logLevel="trace" pickerCompatibleVersions="10.1.2" maxDataRows="1000">


4. Start the middle-tier (opmnctl startall) or stopped components.
   
   
5. Immediately reproduce the problem.
   
   
6. Review or upload the application.log
   

---