Batch Status Is Successful When ALM Engine Fails With Shared Memory Issue
(Doc ID 3043554.1)
Last updated on OCTOBER 04, 2024
Applies to:
Oracle Financial Services Asset Liability Management - Version 8.1.2 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA) 8.1.2
Oracle Financial Services Asset Liability Management (ALM) 8.1.2
Symptoms
With Oracle Financial Services Asset Liability Management (ALM) 8.1.2, when running an ALM Process via a Batch, the Batch Task ends with a status of Successful when the ALM Process fails as a result of running out of shared memory.
The Task is successful but, when you select the Task, there is no "Execution Successful" message:
Checking the ALM Cash Flow engine log for the Task, you find the following errors:
Module Logging OFS errors: semget failed, errno = 28, file ipcmutex.cpp, line 197
Module Logging OFS errors: semget failed, errno = 28, file ipcmutex.cpp, line 244
Module Logging OFS errors: Out of Shared Memory
You expect the Batch Task for this ALM Process to end in a status of Failed.
Cause
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
Symptoms |
Cause |
Solution |
References |