Contents

1   Overview

This instruction concerns alarm handling for the Storage Engine, Out Of Memory In PLDB alarm.

1.1   Alarm Description

The alarm is issued when the Processing Layer Database (PLDB) Storage Engine runs out of memory.

The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
No free space in the PLDB.	The PLDB has run out of available memory.	The PLDB contains too much subscriber data, and has reached its maximum capacity.	PLDB	Subscriber data that is newly added (through provisioning or otherwise) may be rejected.

The alarm attributes are listed and explained in Table 2:

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Auto Cease	Yes
Module	STORAGE-ENGINE
Error Code	4
Timestamp First	Date and time when the alarm was raised for the first time.
Repeated Counter	Number which indicates how many times the alarm was raised.
Timestamp Last	Date and time of the most recent alarm raised.
Resource ID	.1.3.6.1.4.1.193.169.1.1.4
Alarm Model Description	Out of memory, Storage Engine.
Alarm Active Description	Storage Engine (PLDB): out of memory (<DET>).
ITU Alarm Event Type	processingErrorAlarm (4)
ITU Alarm Probable Cause	outOfMemory (162)
ITU Alarm Perceived Severity	(4) – Major
Originating Source IP	Node ID where the alarm was raised.
Sequence Number	Number which indicates the order in which alarms were raised.

In Table 2, the indicated variable is as follows:

• <DET> is a text string providing further details on the out-of-memory error, if available.

For further information about attribute descriptions, refer to CUDB Node Fault Management Configuration Guide, Reference [1].

1.2   Prerequisites

This section lists the prerequisites to meet before performing the below procedure.

1.2.1   Documents

Before starting this procedure, ensure that you have read the following documents:

• CUDB Node Fault Management Configuration Guide, Reference [1], regarding alarm configuration.
• CUDB System Administrator Guide, Reference [2], regarding defragmentation.
• System Safety Information, Reference [4]
• Personal Health and Safety Information, Reference [5]

1.2.2   Tools

Not applicable.

1.2.3   Conditions

Not applicable.

2   Procedure

In case the alarm is raised, do the following:

1. Perform a defragmentation in the PLDB to free up space. Refer to CUDB System Administrator Guide, Reference [2] for more information.
2. Check if the alarm is cleared. If it is cleared, no further actions must be taken. If it is not cleared, then consult the next level of maintenance support. Further actions are outside the scope of this instruction.

Glossary

For the terms, definitions, acronyms, and abbreviations used in this document, refer to CUDB Glossary of Terms and Acronyms, Reference [3].

Reference List

CUDB Documents
[1] CUDB Node Fault Management Configuration Guide.
[2] CUDB System Administrator Guide.
[3] CUDB Glossary of Terms and Acronyms.

Other Ericsson Documents
[4] System Safety Information.
[5] Personal Health and Safety Information.