IBM User Guide for Java V7 on Windows > Troubleshooting and support > Using diagnostic tools > Using system dumps and the dump viewer > Using the dump viewer

Using jextract

Use the jextract utility to process system dumps.

For an analysis of core dumps from Linux and AIX platforms, copies of executable files and libraries are required along with the system dump. You must run the jextract utility provided in the SDK to collect these files. You must run jextract using the same SDK level, on the same system that produced the system dump. The jextract utility compresses the dump, executable files, and libraries into a single .zip file for use in subsequent problem diagnosis.

For Java™ 7 SDKs on Windows and z/OS platforms, you do not need to run the jextract utility.

For Java 6 and Java 5.0 SDKs, containing versions of the IBM J9 virtual machine before V2.6, you must still run the jextract utility for all platforms.

When a core file is generated, run the jextract utility against the core file with the following syntax:

jextract <core file name> [<zip_file>]

to generate a compressed file in the current directory, containing the dump and the required executable file and libraries. The jextract utility is in the directory sdk/jre/bin. If you run jextract on a JVM level that is different from the one on which the dump was produced you see the following messages:

J9RAS.buildID is incorrect (found e8801ed67d21c6be, expecting eb4173107d21c673). 
This version of jextract is incompatible with this dump. 
Failure detected during jextract, see previous message(s).

Remember: If you are analyzing a dump from a JVM that used -Xcompressedrefs, use -J-Xcompressedrefs to run jextract using compressed references. See Compressed references for more information about compressed references.

The contents of the .zip file produced and the contents of the XML are subject to change. You are advised not to design tools based on the contents of these files.

Parent: Using the dump viewer

Error 404 - Not Found

The document you are looking for may have been removed or re-named. Please contact the web site owner for further assistance.