DBS, NR, Network Redundancy with Schema Difference

1 Alarm Description

The alarm is raised when one or more Persistent Object Types (POTs) known by a peer cluster has a different or no schema on the local cluster.

Table 1 DBS, NR, Network Redundancy with Schema Difference
Alarm Cause	Description	Fault Reason	Fault Location	Impact
One or more POTs have different or no schema between databases.	One or more POTs known by a peer cluster have different or no schema on the local cluster.	The local or the peer cluster have been upgraded to a new database schema.	Database	Changes to the value of unknown POT attributes are not replicated to the receiving cluster. The receiving cluster migrates all received POT instances to the known schema, which generates extra load.

Table 2 Alarm Attributes
Attribute Name	Attribute Value/Interpretation
Major Type	`193`
Minor Type	`918535`
MO Class	`DbsService`
Source	`DbsvDirector`
Specific Problem	`DBS, NR, Network Redundancy with Schema Difference`
Event Type	`QUALITYOFSERVICEALARM`
Probable Cause	`frequencyHoppingFailure` (74)
Perceived Severity	`MAJOR`
Additional Information	A list of the POT RTIDs with schema difference

2 Procedure

3 Handle Alarm DBS, NR, Network Redundancy with Schema Difference

Prerequisites

No documents are required.
No tools are required.
Before starting this procedure, ensure that the following condition is met:
- The alarm is raised.

Steps

Disable network redundancy by setting the isEnabled attribute of the NetsharedConfig class to false.
Perform the upgrade on the cluster with the old database schema.
Enable network redundancy by setting the isEnabled attribute of the NetsharedConfig class to true.
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.