Configuring Diagnostic Framework Settings

13-14 Oracle Fusion Middleware Administrators Guide Figure 13–4 Flow for Investigating a Problem The following describes the workflow illustrated in Figure 13–4 : 1. You notice that the system, component, or application is not functioning as expected. For example, you notice that there is a performance problem or users have reported that the application that they are trying to access is reporting errors. Suspect a Problem Incident Created? Yes No Manually Create an Incident View Problems View Incidents View Details of Specific Incident Able to Resolve the Problem? No Execute Additonal Dumps View Contents of Incident Files 1 Able to Resolve the Problem? No Package Incident and Send to Oracle Support 2 3 4 5 6 7 Problem Resolved Yes Yes 8 Diagnosing Problems 13-15 2. Check to see if a problem and an incident have been created that may be related to the symptoms you are observing: a. View the set of problems by using the WLST listProblems command, as described in Section 13.4.2.1 . b. If a problem has been created, list the incidents related to the specific problem using the listIncidents command, as described in Section 13.4.2.2 . 3. If an incident has not been created, go to Step 4. If an incident has been created, go to Step 5. 4. If you do not see any incidents listed that are related to your problem, you can create an incident manually using the createIncident command to capture diagnostics for the problem. Consider creating an incident when you encounter an issue, such as software failure or performance problem, and you want to gather more diagnostic data. You can view the log files and the messages in the files. If there is a specific message that you believe is related to the issue you are seeing, you can use the message ID in the createIncident command. See Section 13.4.4.1 for more information about creating an incident. 5. View the details of the specific incident using the showIncident command, as described in Section 13.4.2.2 . This command lists information about the incident, including the related message ID, the time of the incident, the ECID, and the files generated by the incident. 6. Use the getIncidentFile command to view the contents of files for the incident, as described in Section 13.4.2.2 . The contents may provide information to guide you to the source of the problem and help in resolving it. 7. If the contents of the files for the incident do not help you to resolve the problem, you can execute additional dumps to view detailed diagnostics. For example, if you are experiencing performance problems, execute the dms.metrics dump. See Section 13.4.3 for information about the dumps available and how to execute them. 8. If you still cannot resolve the problem, package the incident, along with the RDA report, and send them to Oracle Support. See Section 13.4.4.2 and Section 13.4.4.3 for information about packaging incidents and generating RDA reports.

13.4.2 Viewing Problems and Incidents

You can view the set of problems, the list of incidents, and the details of a particular incident using the WLST command-line utility, as described in the following topics: ■ Viewing Problems ■ Viewing Incidents

13.4.2.1 Viewing Problems

You can view the set of problems by executing the WLST listProblems command, using the following format: listProblems[adrHome] [,server] The listProblems command lists the problems in the ADR home. Each problem has a unique ID: listProblems 13-16 Oracle Fusion Middleware Administrators Guide Problem Id Problem Key 1 BEA-101020 [HTTP]

13.4.2.2 Viewing Incidents

You can list of all available incidents or the incidents related to a specific problem by executing the WLST listIncidents command, using the following format: listIncidents[id], [ADRHome] For example, to see the list of all incidents, use the following command: listIncidents Incident Id Problem Key Incident Time 2 BEA-101020 [HTTP] Fri Feb 26 13:42:01 PDT 2010 1 BEA-101020 [HTTP] Tue Feb 23 06:17:39 PDT 2010 To view the incidents related to a specific problem, use the following command: listIncidentsid=1 Incident Id Problem Key Incident Time 2 BEA-101020 [HTTP] Fri Feb 26 13:42:01 PDT 2010 1 BEA-101020 [HTTP] Tue Feb 23 06:17:39 PDT 2010 To view the details of a particular incident, use the WLST showIncident command, using the following format: showIncidentid, [adrHome] [,server] For example, to see the details of incident 1, use the following command: showIncidentid=1 Incident Id: 1 Problem Id: 1 Problem Key: BEA-101020 [HTTP] Incident Time: Tue Feb 23 06:17:39 PDT 2010 Error Message Id: BEA-101020 Execution Context: 0000IExqUvyAhKB5JZ4Eyf1Afdj600009i Flood Controlled: false Dump Files : dms_ecidctx1_i1.dmp jvm_threads2_i1.dmp dms_metrics3_i1.dmp odl_logs4_i1.dmp odl_logs5_i1.dmp diagnostic_image_AdminServer_2010_02_23_06_17_42.zip readme.txt To view the contents of a file in the incident, use the WLST getIncidentFile command, using the following format: getIncidentFileid, name [,outputFile] [,adrHome] [,server] For example, to view the contents for the file odl_logs4_i1.dmp use the following command: getIncidentFileid=1, name=odl_logs4_i1.dmp, outputFile=tmpodl_logs4_i1_ dmp.output The command writes the output to the file odl_logs4_i1_dmp.output.