Re: ORA-04030: out of process memory errors

From: John Hurley <>
Date: Mon, 21 Oct 2013 16:35:47 -0700 (PDT)
Message-ID: <>

Sandra: remember that ORA 4030's are problems with programs chewing up too much PGA memory ( not SGA ).  Most of the time oracle bugs.

You should have trace files and/or entries in alert log that you can open an SR with Oracle against.

Last year we found a bad problem for us with a program that ran a bunch of updates on a text index.  Oracle had a fix already identified but decided apparently that it was not common enough to include in regular maintenance.  ( Heres my blog post on that one ).

Odds are very good that oracle support can identify a specific fix for you probably already on hand. ?  Really ?  Odds are even better than the fix is probably built into ( perhaps ) or almost certainly ... but you need to know what oracle bug ...

If you have something configured like OS Watcher and get it running every 60 seconds then you should be able to look at and correlate minute by minute os memory stats and process statistics against when the 4030's happen.  That will lead you directly to the suspects ...

 From: Sandra Becker <> To: oracle-l <> Sent: Monday, October 21, 2013 1:08 PM
Subject: ORA-04030: out of process memory errors   

Solaris 5.10,  128G RAM, 8G swap
Oracle EE
We've been getting the ORA-04030 errors several times a week since they did an OS patch in August.  The SE team says there isn't anything wrong with the server or configuration on their side, although they do see some swap messages in their logs.  Other than the OOM errors, we don't see any issues in the database.

What should we be looking at/for to determine the cause?  The databases and server they are running on have been in place for at least of couple of years.  Does anyone know of memory issues with this version of Solaris?

Thanks in advance for any suggestions or ideas.

Transzap, Inc.

Received on Tue Oct 22 2013 - 01:35:47 CEST

Original text of this message