Comments (5)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 localhost commented Permalink

Hi, first time I ran into this problem with and Oracle database. However, it seemed it was not the Oracle database problem.Starting a few UNIX processes, we got this type of error:0403-031 The fork function failed. There is not enough memory available.<div>&nbsp;</div> The problem started to appear on a new server installed, where the old application and database was moved. Oracle doc's mentioned this parameter, this way I got here. <div>&nbsp;</div> Regards,Ryszard<div>&nbsp;</div>

2 localhost commented Permalink

Hi Ryszard.<div>&nbsp;</div> Pls check your swap setting default ,the setting is small than you phymemory ,you have to increase it by manual.

3 localhost commented Permalink

Yeah that message is related to page "thrashing". Your server is swapping too much and can't handle allocating memory to your OS or apps. Add more physical memory. We went from 5GB to 12GB and now Oracle is happy!

4 localhost commented Permalink

question about this parameter... does it mean the application can never be swapped? So if the system is running out of memory, it keeps taking memory from the file cache until it is gone... what happens after that?<div>&nbsp;</div>

5 localhost commented Permalink

bladesofsteele: The application can be swapped but your goal is for applications never to swap. But due to fiscal reasons or some other excuse, some shops cannot add more physical RAM to accommodate let's say an Oracle DB Server. To alleviate this issue, one needs to allocate enough paging space for the application to still work properly, albeit a little more slowly since it's now using Persistant storage. If there is not a leak and the application still requires more RAM pages than its allotted amount of Paging Space, yes the application will tend to crash, hence the message: "0403-031 The fork function failed. There is not enough memory available" as stated in the first post.