Contents

1   Overview

This instruction concerns alarm handling for the Storage Engine, Memory Usage Too High In PLDB, Major alarm.

1.1   Alarm Description

The alarm is issued when the memory use of the Processing Layer Database (PLDB) reaches the level configured for the Full threshold (internal CUDB threshold). The alarm is cleared after the memory use drops below the level configured for the Full threshold, and the Storage Engine, Memory Usage Too High In PLDB, Warning, Reference [1] alarm is raised.

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
The memory use of the PLDB reached the Full threshold level.	The amount of subscriber data stored in the PLDB results in a level of memory use which reaches the level configured for the Full threshold.	The PLDB contains too much subscriber data, and is close to reaching its maximum capacity.	PLDB	The storage of newly provisioned subscriber data 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	9
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.8
Alarm Model Description	Memory usage at Full level, Storage Engine.
Alarm Active Description	Storage Engine (PLDB): memory usage at Full level.
ITU Alarm Event Type	processingErrorAlarm (4)
ITU Alarm Probable Cause	storageCapacityProblem (151)
ITU Alarm Perceived Severity	(4) – Major
Originating Source IP	Node IP where the alarm was raised.
Sequence Number	Number which indicates the order in which alarms were raised.

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

1.2   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.1   Documents

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

• The section on the cudbManageStore command in CUDB Node Commands and Parameters, Reference [2]
• CUDB Node Fault Management Configuration Guide, Reference [3], regarding alarm configuration
• The "Defragmenting a Database Cluster" section of CUDB System Administrator Guide, Reference [4]
• System Safety Information, Reference [6]
• Personal Health and Safety Information, Reference [7]

1.2.2   Tools

Not applicable.

1.2.3   Conditions

Not applicable.

2   Procedure

In case the alarm is raised, do the following:

1. Check if some of the subscriber data can be removed to free up space in the PLDB. If possible, then remove the data.
2. Perform a defragmentation in the PLDB. Refer to CUDB System Administrator Guide, Reference [4] for more information.
3. Confirm that the alarm has ceased. If the alarm remains, 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 [5].

Reference List

CUDB Documents
[1] Storage Engine, Memory Usage Too High In PLDB, Warning.
[2] CUDB Node Commands and Parameters.
[3] CUDB Node Fault Management Configuration Guide.
[4] CUDB System Administrator Guide.
[5] CUDB Glossary of Terms and Acronyms.

Other Ericsson Documents
[6] System Safety Information.
[7] Personal Health and Safety Information.