SARM Stops Processing And Terminates With Critical Error Memory Allocation Error (Doc ID 1274610.1)

Last updated on JUNE 20, 2012

Applies to:

Oracle Communications ASAP - Version 5.2.4 and later
Information in this document applies to any platform.
***Checked for relevance on 20-JUN-2012***

Symptoms

The SARM exited - Critical Memory Allocation error:

Memory Pool 'CS_BYTE[128] (Base)' used up, Resizing by 512 blocks to 179712 blocks
> /> 235653.636:28:PROG:System Event :2375:sarm/sarm/sarm/provision.c
ASAP System Event: SYS_INFO
Memory Pool 'CS_BYTE[16] (Base)' used up, Resizing by 1024 blocks to 123904 blocks
> /> 235653.636:28:PROG:System Event :2375:sarm/sarm/sarm/provision.c
ASAP System Event: SYS_INFO
Memory Pool 'CS_BYTE[32] (Base)' used up, Resizing by 1024 blocks to 58368 blocks
> /> 235655.094:160:PROG:Fatal Thread Error :1691:control/libcontrol/main.c
SARMPROD Server: Fatal Thread Error:
Open Server Error # [16008] Severity [15] State [0] Error Text [Could not build error string
]
> /> 235655.094:160:PROG:System Event :203 :control/libcontrol/asc_memory.c
ASAP System Event: SYS_TERM
Critical Error: Memory Allocation Error for [1032] Bytes
> /> 235655.094:160:PROG:System Event :203 :control/libcontrol/asc_memory.c
ASAP System Event: SYS_TERM
Critical Error: Memory Allocation Error for [1032] Bytes
> /> 235655.094:160:PROG:System Event :203 :control/libcontrol/asc_memory.c
ASAP System Event: SYS_TERM
Critical Error: Memory Allocation Error for [1032] Bytes
> /> 235655.094:160:PROG:System Event :203 :control/libcontrol/asc_memory.c
ASAP System Event: SYS_TERM
Critical Error: Memory Allocation Error for [1032] Bytes

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms