Roadmap—Investigating, Reporting, and Resolving a Problem

13-18 Oracle Fusion Middleware Administrators Guide

13.4.3.2 Viewing a Description of a Diagnostic Dump

You can view a description of a particular dump, including the syntax for executing the dump by using the WLST describeDump command. You specify the name of the dump in which you are interested. For example, to view a description of the dms.metrics dump, use the following command: describeDumpname=dms.metrics Name: dms.metrics Description: Dumps DMS Dynamic Monitoring Service metrics. Mandatory Arguments: Optional Arguments: Name Type Description format STRING Format of the dump output; raw or xml

13.4.3.3 Executing Dumps

If you detect a problem and want to gather additional diagnostic data, you can invoke the executeDump command for a specified dump. Each dump may have mandatory or optional arguments, or both. To view the arguments for a particular dump and how to specify them, use the describeDump command, as described in Section 13.4.3.2 . The following example executes the dump with the name dms.metrics and the incident ID 1 and writes it to the file dumpout.txt: executeDumpname=dms.metrics, outputFile=tmpdumpout.txt, id=1 Dump file dms_metrics1_i1.dmp added to incident 1 The command writes the dump output to the information about incident 1. If you execute the showIncident command for incident 1, the output includes dms_metrics1_ i1.dmp.

13.4.4 Managing Incidents

The Diagnostic Framework stores incidents, whether they are created automatically or manually, and Oracle Fusion Middleware provides tools to help you process incident reports and to package those incidents to send to Oracle Support. The following sections describe: ■ Creating an Incident Manually ■ Packaging an Incident ■ Generating an RDA Report ■ Purging Incidents jvm.classhistogram A JVM class histogram, the output of which varies depending on the JVM vendor. jvm.threads Summary statistics about the threads running in a JVM as well as performing a full thread dump. odl.activeLogConfig The active Java logging configuration. odl.logs Contents of diagnostic logs, correlated by ECID or time range. odl.quicktrace Quick trace messages. wls.image The WLDF server image dump. Table 13–2 Cont. Diagnostic Dump Actions Dump Action Description Diagnosing Problems 13-19

13.4.4.1 Creating an Incident Manually

System-generated problems—critical errors generated internally—are automatically added to the Automatic Diagnostic Repository ADR. You can gather additional diagnostic data on these problems, upload diagnostic data to Oracle Support, and in some cases, resolve the problems, all with the workflow that is explained in Section 13.4 . Consider creating an incident manually when you encounter an issue, such as software failure or performance problem and you want to gather more diagnostic data, but the Diagnostic Framework has not automatically created an incident. You use the WLST command createIncident to create an incident manually. You can specify an incident based on time, a message ID, an impact area, or an ECID. Then, you can inspect the content of the incident or send it to Oracle Support for further analysis. The following describes how to manually create an incident based on a message ID: 1. Search the log files, as described in Section 12.3.2 . If you find a message that you suspect is related to the issue you are seeing, you can use the message ID when you create the incident. 2. Use the following commands to invoke WLST, connect to the Managed Server and navigate to the Managed Server instance: java weblogic.WLST connectweblogic, password, localhost:7001 cdserversserver_name 3. Create the incident, using the createIncident command, with the following format: createIncident[adrHome] [,incidentTime] [,messageId] [,ecid] [,appName] [,description] [,server] For example, to create an incident based on the error with the message ID MDS-50500, use the following command, specifying the message ID, and provide a description of the incident to help you and Oracle support track the incident: createIncidentmessageId=MDS-50500, description=sample incident Incident Id: 55 Problem Id: 4 Problem Key: MDS-50500 [MANUAL] Incident Time: 23rd February 2010 11:55:45 GMT Error Message Id: MDS-50500 Flood Controlled: false If you do not specify a server, the incident collects information from the server to which you are connected. To specify a server, use the server option, as shown in the following example: createIncidentmessageId=MDS-50500, description=sample incident, server=soa_server1 If you do not specify the adrHome option, the incident is created in the server to which you are connected. For example, if you are connected to the Administration Server, the incident is created in the adrHome for the Administration Server. The Diagnostic Framework evaluates the command and invokes the appropriate diagnostic dumps. The incident and the diagnostic dumps are written to the ADR. Each diagnostic dump writes its output to the incident. 13-20 Oracle Fusion Middleware Administrators Guide You can view the information about the incident, as described in Section 13.4.2.2 . You can view the information in the dumps, as described in Section 13.4.3 .

13.4.4.2 Packaging an Incident

You can package the incident to facilitate sending the information to Oracle Support by using the ADR Command Interpreter ADRCI. The ADRCI utility enables you to investigate and report problems in a command-line environment. With ADRCI, you can package incident and problem information into a zip file for transmission to Oracle Support. The ADRCI command-line utility is located in the following directory: UNIX MW_HOMEwlserver_10.3serveradr Windows MW_HOME\wlserver_10.3\server\adr Packaging an incident involves a three-step process: 1. Create a logical package. The package is denoted as logical because it exists only as metadata in the ADR. It has no content until you generate a physical package from the logical package. The logical package is assigned a package number, and you refer to it by that number in subsequent commands. You can create the logical package as an empty package, or as a package based on an incident number, a problem number, a problem key, or a time interval. If you create the package as an empty package, you can add diagnostic information to it in step 2. Creating a package based on an incident means including diagnostic data, such as dumps, for that incident. Creating a package based on a problem number or problem key means including in the package diagnostic data for incidents that reference that problem number or problem key. Creating a package based on a time interval means including diagnostic data on incidents that occurred in the time interval. 2. Add diagnostic information to the package. If you created a logical package based on an incident number, a problem number, a problem key, or a time interval, this step is optional. You can add additional incidents to the package or you can add any file within the ADR to the package. If you created an empty package, you must use ADRCI commands to add incidents or files to the package. 3. Generate the physical package. When you submit the command to generate the physical package, ADRCI gathers all required diagnostic files and adds them to a zip file in a designated directory. You can generate a complete zip file or an incremental zip file. An incremental file contains all the diagnostic files that were added or changed since the last zip file was created for the same logical package. You can create incremental files only after you create a complete file, and you can create as many incremental files as you want. Each zip file is assigned a sequence number so that the files can be analyzed in the correct order. Zip files are named according to the following format: packageName_mode_sequence.zip In the format: