OBIEE 10-12c: Steps To Generate Stack Trace Output To Debug Core Dump Or Hang On Linux / Unix (Doc ID 1382369.1)

Last updated on JUNE 30, 2017

Applies to:

Business Intelligence Suite Enterprise Edition - Version 10.1.3.4.2 [2405] to 12.2.1 Beta
Business Intelligence Server Enterprise Edition - Version 10.1.3.4.2 [2405] to 12.2.1 Beta
Generic UNIX
Generic Linux

Goal

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.

Note:

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 crashed create a file like javacore*.txt, these do not need to be analyzed by GDB or other 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

 

Solution

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms