![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 2242964.1 : Diameter Signaling Router (DSR): Event_Number - 31100 - DB Replication Fault
In this Document
Created from <SR 3-14462627311> Applies to:Oracle Communications Diameter Signaling Router (DSR) - Version DSR 5.0 and laterInformation in this document applies to any platform. SymptomsDatabase replication alarm (Event 31100) on both MP Server. TIMESTAMP: 2017-03-12 05:38:32.113 GMT SECS: 1489297112 TIMESTAMP: 2017-03-12 05:37:45.039 GMT SECS: 1489297065
CauseThere was a ntp daemon not synchronized alarm (Event 32509) on MP1 server causing incorrect time on the server. This in turn was causing the Database replication alarm 31100 on MP servers. TIMESTAMP: 2017-03-11 17:09:56.262 GMT
NETWORK_ELEMENT: NOAM SERVER: mp1 SEQ_NUM: 19480753 EVENT_NUMBER: 32509 SEVERITY: MINOR PRODUCT: TPD PROCESS: cmplatalarm TYPE: PLAT INSTANCE: NAME: Server NTP Daemon Not Synchronized DESCR: Server NTP Daemon Not Synchronized ERR_INFO: GN_WARNING/WRN Platform detected an error condition [cmplatalarm.cxx:319] ^^ Additional details captured in /var/TKLC/log/syscheck/fail_log (timestamp: 1489252196) [cmplatalarm.cxx:323] ^^ [5441:cmplatalarm.cxx:325] SECS: 1489252196 USECS: 262000 CISECS: 1489252196 CIUSECS: 262000 ID: 7 SolutionDo the following on the server reporting the ntp alarm to clear both NTP issue and database replication alarms # ntpq -pn
# sudo service ntpd status # sudo service ntpd stop # sudo ntpdate <IP from remote column of ntpq command> --> do the ntpdate command 3 times, until offset is/or is close to zero # sudo service ntpd start # sudo service ntpd status # ntpq -pn Warning:Sudden database timestamp jump may temporarily affect the system, so it is best that given server is take out of service (Active NOAM GUI: Main Menu--> Status & Mange --> HA-->Edit)
Attachments This solution has no attachment |
||||||||||||||||
|