Exadata non-virtual database server (X3 through X8) running Exadata 19.3/20.1 may kernel panic after database process crash and incident dump creation (Doc ID 2724585.1)

Last updated on NOVEMBER 04, 2020

Applies to:

Symptoms

Following a database process crash (e.g. ORA-7445) and corresponding incident dump creation, the database server may experience a kernel panic, with messages similar to the following in /var/log/messages or dmesg(1) output:

When this issue occurs, it is always preceded by a database process crash or event (e.g. ORA-7445) that creates an incident dump containing a memory dump of a specific address associated with the InfiniBand HCA. However, not all database process crashes and events cause this issue. A kernel panic will not occur when an incident dump does not have a memory dump, or has a memory dump that does not access the specific address associated with the InfiniBand HCA.

The following conditions must exist for this issue to occur:

• Database server is X4, X5, X6, X7, or X8 hardware generation, 2-socket or 8-socket.  
  • X8M database servers are not affected.  X3 and earlier database servers are not affected.
• Database server is configured physical (non-VM).
  • Database servers configured virtual are not affected.
• Database server is running one of the following Exadata versions
  • 20.1.0 through 20.1.2
  • 19.3.0 through 19.3.12

Cause

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