My Oracle Support Banner

How To Collect/Enable Java Tracing in ODI, Such as Thread Dump, Heap Dump, Core Dump or Stack Trace ? (Doc ID 2248749.1)

Last updated on OCTOBER 04, 2022

Applies to:

Oracle Data Integrator - Version 11.1.1.3.0 and later
Information in this document applies to any platform.

Purpose

 To describe the difference between Thread dump, Heap dump, Core dump and Stack Trace and advise on the circumstances in which dump or trace should be collected and how to do it.

Scope

 This article is intended for Oracle Data Integrator (ODI) Administrators.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 I. Thread Dump:
 What is a Thread dump?
 How to collect Thread dumps in Windows/Unix?
 How to collect Thread dumps in Unix?
 Common GUI Methodology to Collect Thread dumps:
 II. Heap Dump
 What is a Heap dump?
 How to collect Heap Dumps?

    1. To collect the information present in the memory when the **out of memory** arises, one can have the Java process automatically generate a Heap dump when the   error is received.
 III. Core Dump
 What is a Core dump?
 Core dump in Windows:
 
Core dump in Unix:
 How to generate Heap dump from Core dump and analyze it?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.