Forum Discussion
Mick_O_Rourke_6
Nimbostratus
NimbostratusMonitoring ASM memory usage
Hi DevCentral,
- We hit a major issue recently where our ASM ran out of memory;
- The result was a major Sev1 where the whole boxed slowed to a crawl, during the event CPU and mem...
Torti_93733Nimbostratus
Nimbostratusdo you know, why is running out of memory? Is it the ASM itself or i.e. the xml enforcer? we have experience with that, too ;-)
if it is the ASM, you could change the provisioning by a custom memory setting. if it is a sub process like xml enforcer, it can be changed by the internal parameter "total_xml_memory".
The bd process is the main process for the ASM. There should be a possibility, to get the memory allocation of every process via snmp. For this, you need the process id and hrSWRunPerfMem
i.e. 1.3.6.1.2.1.25.5.1.1.2.$PID - if your PID is 9002 --> snmpget 1.3.6.1.2.1.25.5.1.1.2.9002
the problem is, the pid isn't static. So you have to change the snmpget with every restart of the process. for a main process, it should only happen with a system restart.
- Torti_93733process name: .1.3.6.1.2.1.25.4.2.1.2.$PID