If you encounter such error on Windows system, please don't just look at physical memory usage but also committed memory usage which includes physical memory and page file. You could be in such situation where there is still free physical memory but running out of pagefile.
To check on the metrics, you can go to Task Manager - Performance tab - Memory. Look at the value under Committed. In this screenshot below, the system commit limit is 50.3GB and current committed usage is 9.3GB.
To find out more on what processes that consume the committed memory, you can go to Details tab. By default Commit size column is not shown in this tab. To make it visible, you need to right click on any of column title and click Select columns.
Select Commit size
You can see the Commit size column now. Among all the processes, you can see that oravssw.exe actually has much larger Commit Size compare to Memory. And this is possible the culprit for this our-of-memory issue.
So what is oravssw.exe? It is Oracle VSS Writer and it is used by a lot of backup software to perform Oracle backup. Unfortunately, there is a bug for this software that cause memory leaking according to this note (Doc ID 1358570.1) from Oracle. There is no fix for this yet but only workaround which is to disable this service or perform service restart after backup. Although is not pretty but at least you don't need to bother with ORA-04030 issue again.
No comments:
Post a Comment