My Oracle Support Banner

Terminate an instance by pmon in an out of memory situation (Doc ID 3026207.1)

Last updated on MAY 30, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 and later
Generic Linux

Symptoms

PMON terminating the instance due to error 502.

Instances are intermittently terminated by PMON in low memory situations.

 

DB Alert Log
2024-04-20T05:27:43.643512+09:00
Instance Critical Process (pid: 17, ospid: 21683, PMAN) died unexpectedly
PMON (ospid: 21643): terminating the instance due to error 502
2024-04-20T05:27:44.914850+09:00
System state dump requested by (instance=1, osid=21643 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file /oradump01/POBADBD/diag/rdbms/pobadbd/POBADBD/trace/POBADBD_diag_21671_20240420052744.trc
2024-04-20T05:27:55.430352+09:00
Instance terminated by PMON, pid = 21643

 

Changes

 N/A

 

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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