DBS, Memory Limit Reached

Contents


1   Alarm Description

The alarm is raised when DBN memory use exceeds a threshold.

Table 1    DBS Memory Limit Reached Alarm Causes

Alarm Cause

Description

Fault Reason

Fault Location

Impact

Reconfiguration ongoing

DBN is redistributing data either because a node being locked or unlocked or because a node failed.

N/A

N/A

Node lock, node unlock, and scaling operations must not be initiated until the alarm clears, as these can temporarily increase memory usage even more.

Overload

The system is overloaded.

Dimensioning

Note:  
The alarm can be raised during a reconfiguration operation.

Table 2    Alarm Attributes

Attribute Name

Attribute Value/Interpretation

Major Type

193

Minor Type

917505

MO Class

DbsPU

Source

Format:(1)


ManagedElement=1,SystemFunctions=1,Pm=1, PmJob=<threshold_job_name>, MeasurementReader=<measurement_reader_name>:PU=<Node_name>, EE=DBN

Specific Problem

DBS, Memory Limit Reached

Event Type

PROCESSINGERRORALARM

Probable Cause

outOfMemory (162)

Perceived Severity

Critical

Additional Text

Measurement type: Mem.RecordHeap.PUsed

(1)  This attribute is filled by other CBA components, for example: CoreMW, COM SA. Therefore, the described format is only an example and can be different on the node.


2   Procedure

2.1   Handle Alarm DBS, Memory Limit Reached

Prerequisites

Steps

  1. Is the system overloaded?

    Yes: Decrease load on the cluster, if possible.

    No: Continue with the next step.

  2. Is data redistribution (reconfiguration) in progress?

    Yes: Wait for the reconfiguration to finish, then continue with the next step.

    No: Consult the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.

  3. Is the alarm cleared?

    Yes: Job is completed.

    No: Consult the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.