Process Hangs After Issuing Oradebug Short_Stack on HP Platforms
(Doc ID 1271173.1)
Last updated on MARCH 28, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.1 to 22.214.171.124.0 [Release 10.2 to 11.2]
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
HP-UX PA-RISC (64-bit)
In a rare race condition on HP platforms, an "oradebug short_stack" on a process could cause that process to get stuck on a "malloc" OS call. From that point on, the process becomes unresponsive. The following symptoms could occur:
- Oracle process (background or foreground process) is hung. This can result in a wide variety of symptoms.
- A GDB stack trace of the process shows a stack trace that includes ...malloc...ksdxfstk...<signal handler called>...malloc. Note that the last call in the list (first one executed) could be either malloc(), realloc(), calloc(), or free().
- If using Procwatcher ( <Note: 459694.1> ) you could see the following in the Procwatcher log: "WARNING: There was a problem with oradebug shortstack".
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