DSR Upgrade Failed On SOAM Standby with inetmerge alarm 31107

Asset ID:	1-71-2195518.1
Update Date:	2017-03-21
Keywords:

Solution Type Technical Instruction Sure

Solution 2195518.1 : DSR Upgrade Failed On SOAM Standby with inetmerge alarm 31107

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 7.1.2 and later
Tekelec HLR Router - Version HLRR 4.0 to HLRR 4.0 [Release HLRR 4.0]
Information in this document applies to any platform.

Goal

The following was observed after an upgrade. How should this be addressed?

NETWORK_ELEMENT: SO_Element
  SERVER: adsrso0a
  SEQ_NUM: 1669101
  EVENT_NUMBER: 31107
  SEVERITY: MAJOR
  PRODUCT: Platform
  PROCESS: inetmerge
  TYPE: COLL
  INSTANCE: adsrso0b
  NAME: DB Merge From Child Failure
  DESCR: DB merging from a child Source Node has failed
  ERR_INFO:
  GN_DOWN: Child link not in active/standby/inhibit
  [7738:MergeReceiver.cxx:1793]

  SECS: 1476909800
  USECS: 27000
  CISECS: 1476909800
  CIUSECS: 27000
  ID: 0

[admusr@adsrso0a ~]$ inetmstat -m -w
  srcNode nodeId InetMerge State dir dSeq dTime updTime info

  adsrso0a adsrso0b ConnectedIncompat From 0 0.00 23:42:48

[admusr@adsrso0a ~]$

Solution

This issue is sometimes seen after an upgrade associated with the upgraded SOAM. The ConnectedIncompat implies the following:

ConnectedIncompat
Connected but the schema are incompatible and replication cannot run until
(1) the schema has the needed upgrade information or (2) problematic tables are excluded from replication.

However this is due to know bug and can be addressed by doing the following:

On the newly upgrade SOAM server
# pm.kill inetmerge

If the above does not clear the issue then execute the same command "pm.kill inetmerge" on the active SOAM.

Attachments

This solution has no attachment