My Oracle Support Banner

How to Diagnose a Signal 11 Memory Error When Running an RM Process (Doc ID 565692.1)

Last updated on MAY 18, 2017

Applies to:

Oracle Risk Manager - Version 4.5 and later
Information in this document applies to any platform.
Oracle Financial Services Applications (OFSA) 4.5

Purpose

This document addresses how to diagnose and address memory related issues for Oracle Risk Manager (RM).  When running a Risk Manager process on the server, the process fails / dies due to a lack of memory.  A return code of -11 is returned to the server status update window.  In the Request Queue (rq) log, there is a signal 11 message and a core dump file is created on the server.  The signal 11 message may be preceded by an "Out of Memory" error with a return code of 1008.  There may be an additional message in the ofsrm.xxxx file (where xxxx is the job number).

If running a stochastic RM process with multiprocessing on, the process may also hang while waiting for resources rather than fail with a signal 11 or signal 6 error.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
References

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