Instance Crash Or ORA-04030 Errors When Pagefile Is Full
(Doc ID 1358570.1)
Last updated on AUGUST 18, 2020
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
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
Microsoft Windows (32-bit)
Microsoft Windows x64 (64-bit)
***Checked for relevance on 30-Jan-2015***
Various ORA-7445 and ORA-4030 errors occur due to all the Windows pagefile space having been used up despite physical memory being free on the server. Checking the Oracle trace files will show free memory is available but there is insufficient free pagefile space, e.g.:
The Windows Event Viewer may also show a warning indicating that the low system resource was due to the ORAVSSW.EXE process, e.g.:
Date: 29/08/2011 19:26:39
Event ID: 2004
Task Category: Resource Exhaustion Diagnosis Events
Keywords: Events related to exhaustion of system commit limit (virtual memory).
Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: oravssw.exe (1936) consumed 29900058624 bytes, oravssw.exe (1964) consumed 22195634176 bytes, and oravssw.exe (1992) consumed 12582133760 bytes.
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