My Oracle Support Banner

Instance Crash Or ORA-04030 Errors When Pagefile Is Full (Doc ID 1358570.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 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)


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.:

Memory (Avail/Total): Ph:25261M/30709M, Ph+PgF:38M/80709M

The Windows Event Viewer may also show a warning indicating that the low system resource was due to the ORAVSSW.EXE process, e.g.:

Log Name: System
Source: Microsoft-Windows-Resource-Exhaustion-Detector
Date: 29/08/2011 19:26:39
Event ID: 2004
Task Category: Resource Exhaustion Diagnosis Events
Level: Warning
Keywords: Events related to exhaustion of system commit limit (virtual memory).
Computer: myserver
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

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