1 Introduction

This instruction concerns alarm handling for the Storage Engine, Deleted Data Due to Reconciliation alarm.

1.1 Alarm Description

The alarm is issued if data has been deleted from the Data Store (DS) data partition due to a data reconciliation process.

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 automated reconciliation process has deleted data to achieve consistency.	Data was deleted from the Data Store (DS) data partition due to a data reconciliation process to achieve consistency.	No fault, a data reconciliation task is ongoing or pending.	DS Unit Group (DSG)	No impact, the reconciliation task must be finished.

The alarm attributes are listed and explained in Table 2.

Table 2 Alarm Attributes
Attribute Name	Attribute Value
Auto Cease	`No`
Module	`STORAGE-ENGINE`
Error Code	`12`
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.2.12.` `<DG>`
Alarm Model Description	`Deleted data due to reconciliation, Storage Engine`
Alarm Active Description	`Storage Engine (DS-group #` `<DG>` `):` `Deleted data due to reconciliation.`
ITU Alarm Event Type	`communicationsAlarm (2)`
ITU Alarm Probable Cause	`databaseInconsistency (160)`
ITU Alarm Perceived Severity	`(5) – Minor`
Originating Source IP	Node IP where the alarm was raised.
Sequence Number	Number which indicates the order in which alarms were raised.

In Table 2, the indicated variables are as follows:

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

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

This instruction references the following documents:

Not applicable.

Not applicable.

If the alarm is raised, do the following:

Steps

Establish an admin "CUDB CLI" session towards the target CUDB node:
ssh <admin_user>@<CUDB_Node_OAM_IP_Address>
Run the following command to check if there are any pending or ongoing reconciliation tasks:
sudo cudbReconciliationMgr -l

This command returns the DSG in affirmative case. Otherwise, it returns nothing. In affirmative case, wait for the task to be completed.

Refer to CUDB Node Commands and Parameters for further information about this command.
Check the log information about reconciliation to see the distributed data involved in the process. For more information, refer to CUDB Node Logging Events.
Clear the alarm manually as described in CUDB Node Fault Management Configuration Guide.
If the alarm does not cease, contact the next level of maintenance support. Further actions are outside the scope of this Operating Instruction.

Copyright	© Ericsson AB 2016, 2018. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.
Disclaimer	The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.
Trademarks	All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.