My Oracle Support Banner

OBI: Steps To Generate Stack Trace Output To Debug Core Dump Or Hang On Linux|Unix (Doc ID 1382369.1)

Last updated on JANUARY 07, 2020

Applies to:

Business Intelligence Suite Enterprise Edition - Version and later
Business Intelligence Server Enterprise Edition - Version and later
Generic Linux
Generic UNIX


This document provides guidelines on how to generate a stack trace using GDB for the OBIEE System Components.  GDB is preferred for the detailed output it provides if available on your platform.

A stack trace debug output on a core file may be requested by Oracle Support / Development to troubleshoot OBIEE  crashes and / or hangs.


Windows crashes should be debugged with ADPlus, see: <Document 958101.1> OBIEE 10g-12c: Steps To Generate An ADPlus Stack Trace To Debug A Crash OR Hang On Windows

Java crashes create a file like javacore*.txt, these do not need to be analyzed by GDB or another debugger.  Please see: E-WL: <Document 659452.1> How to Create a Thread Dump with WebLogic Server 9.2 and 10.3
For OBIEE, the three potential components to produce javacore*.txt are:  Weblogic AdminServer JVM, Weblogic Managed Server (bi_serverX) JVM, JavaHost



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

Ensuring a core file can be generated
 Determining the location of the core file:
 Determining which executable produced the core file:
 Generating a stack trace:
 Preferred method:
 Manual method:
 OBIEE 11g

 OBIEE 10g
 Generating a stack trace against an executable that is hanging, not crashing:

Using GDB:
 Strace alternative:

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