how to interpret the following lines and how can i make sure that the memory availability if it in case server throughs out of memory error
OS Available: 29400K, Working Set: 24680K, Cache Target: 89110K
The OS Available says that the OS is reporting only 29MB of free memory and that's pretty tight for most OSs. Do you have any other processes running with high memory demand? If there's only 29MB of memory free in the system and if the current cache size is the same as the target cache size (~29MB) I'd think you were running on a handheld device or that something else is using up lots of memory in your system.
The Working Set shows that the OS thinks that the database server has referenced about 25MB or memory "recently" and/or "frequently".
The Cache Target shows that the server thinks that 89MB would be a reasonable cache size given the state of the OS, the size of the databases, etc. Usually, the Cache Target is approximately OS Available + Working Set but limited to database sizes and the cache size lower & upper bounds (-cl, -ch). Since Cache Target is a fair bit larger than osavail+workingset, I'd guess that your min cache size is 89MB or so? Look at the startup messages: the min & max cache sizes are displayed there.
What command line switches were used to start the database and what is the size of the database? What OS are you using and how much memory is installed in the system?
answered 26 Aug '13, 21:51