MIME-Version: 1.0
From: Sandra Becker <sbecker6925@gmail.com>
Date: Mon, 13 Jan 2020 12:31:51 -0700
Message-ID: <CAJzM94Asfw1TDOSpiBeuAtPZ2DtCNFehY_TxuYVSf_AcbBHUtA@mail.gmail.com>
Subject: OOM killer terminating database on AWS EC2
To: oracle-l <oracle-l@freelists.org>
Content-Type: multipart/alternative; boundary="00000000000099b091059c0a87e3"
Sender: oracle-l-bounce@freelists.org
Errors-to: oracle-l-bounce@freelists.org
Precedence: normal
Reply-To: sbecker6925@gmail.com
--00000000000099b091059c0a87e3
Content-Type: text/plain; charset="UTF-8"

Server:   AWS EC2
RHEL:   7.6
Oracle:  12.1.0.2

We have a database on an AWS EC2 server that the OOM killer has terminated
twice in the last 5 days, both times it was the ora_dbw0_dwprod process.
On 1/8 postfix was enabled to allow us to email the DBA team through an AWS
relay server when a backup failed.  We stopped running daily backups and
cronjobs that did a quick check for expired accounts.  We've left postfix
enabled for sending emails.  We are searching for answers but have none yet
as to why this is happening.  We also no longer have Oracle support
available to us.  (management saving money again).

Questions:

   1. Could postfix be related to the memory issues even though we haven't
   sent any emails since the first crash 5 days ago?
   2. How can we monitor the memory usage of  an EC2 instance?
   3. How do you disable the OOM killer in EC2 should we decide to go that
   route?  (we have it disabled on our on-prem servers)  The docs I've found
   so far have not been helpful.

I appreciate any help you can give us or pointing us in the right direction.

Thank you,
-- 
Sandy B.

--00000000000099b091059c0a87e3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Server:=C2=A0=C2=A0 AWS EC2</div><div>RHEL:=C2=A0=C2=
=A0 7.6</div><div>Oracle:=C2=A0 12.1.0.2</div><div><br></div><div>We have a=
 database on an AWS EC2 server that the OOM killer has terminated twice in =
the last 5 days, both times it was the ora_dbw0_dwprod process.=C2=A0 On 1/=
8 postfix was enabled to allow us to email the DBA team through an AWS rela=
y server when a backup failed.=C2=A0 We stopped running daily backups and c=
ronjobs that did a quick check for expired accounts.=C2=A0 We&#39;ve left p=
ostfix enabled for sending emails.=C2=A0 We are searching for answers but h=
ave none yet as to why this is happening.=C2=A0 We also no longer have Orac=
le support available to us.=C2=A0 (management saving money again).=C2=A0=C2=
=A0 <br></div><div><br></div><div>Questions:</div><div></div><div><ol><li>C=
ould postfix be related to the memory issues even though we haven&#39;t sen=
t any emails since the first crash 5 days ago?</li><li>How can we monitor t=
he memory usage of=C2=A0 an EC2 instance?</li><li>How do you disable the OO=
M killer in EC2 should we decide to go that route?=C2=A0 (we have it disabl=
ed on our on-prem servers)=C2=A0 The docs I&#39;ve found so far have not be=
en helpful.<br></li></ol></div><div>I appreciate any help you can give us o=
r pointing us in the right direction.</div><div><br></div><div>Thank you,<b=
r></div><div>-- <br><div dir=3D"ltr" class=3D"gmail_signature" data-smartma=
il=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr">Sandy B.<br><=
br></div></div></div></div></div></div>

--00000000000099b091059c0a87e3--
--
http://www.freelists.org/webpage/oracle-l