My Oracle Support Banner

Terminating the Instance Due to Error 471 Out-Of-Memory(OOM) Killer Crashes Oracle Database (Doc ID 1622379.1)

Last updated on JANUARY 21, 2020

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Generic Linux
***Checked for relevance on 22-Mar-2016***


Symptoms

Instance terminated due to death of background process. In this case, it was DBWR.

No more information in alert / traces why DBWR process dead.

Tue Feb 04 13:00:03 2014
LNS: Standby redo logfile selected for thread 1 sequence 6206 for destination LOG_ARCHIVE_DEST_2
Archived Log entry 10547 added for thread 1 sequence 6205 ID 0x77e10623 dest 1:
Tue Feb 04 13:05:09 2014
LGWR waiting for instance termination
Tue Feb 04 13:05:15 2014
System state dump requested by (instance=1, osid=13406 (PMON)), summary=[abnormal instance termination].
System State dumped to trace file /opt/oracle/diag/rdbms/<SID>/<SID>/trace/<SID>_diag_13429.trc
Tue Feb 04 13:05:21 2014
PMON (ospid: 13406): terminating the instance due to error 471
Tue Feb 04 13:05:21 2014

Changes

 

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.