Contents
1 Alarm Description
The alarm is raised when Database Service (DBS) memory use exceeds a threshold.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
Out of memory |
All available memory is allocated |
One or more Database Network (DBN) instances consume all their record heap. |
Heap memory |
If a DBN instance runs out of record heap, database operations fail with retry status until memory becomes available |
|
Uneven memory consumption |
The memory consumption is uneven |
Faulty allocation of persistent object to logical container (DU) |
Memory |
Service downtime or reduced service capacity when the problem is too often detected or when it persists |
|
Faulty pool allocation | ||||
|
System overload |
The system is overloaded |
The system is overloaded |
System dimensioning | |
|
One or more processes of DBS leak memory |
Memory leak in one or more DBS processes. The memory consumption increases. |
A software component has a defective implementation and cannot, for example, clear data (Persistent Object Type instances) that is no longer used |
Software component |
Software crash leading to service downtime or reduced service capacity depending on redundancy |
- Note:
- This alarm can appear as a result of a maintenance activity.
2 Procedure
2.1 Handle Alarm DBS Memory Limit Reached
Prerequisites
- This instruction references the following document:
- No tools are required.
- Before starting this procedure, ensure that the following
condition is met:
- The alarm is raised.
Steps
- Is there is a reconfiguration operation in progress?
Yes: Wait for completion.
No: Decrease load on the cluster.
- Is the alarm cleared?
Yes: Proceed with Step 5.
No: Continue with the next step.
- Perform data collection, refer to Data Collection Guideline.
- Consult the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.
- Job is completed.