| Asset ID: |
1-71-2213698.1 |
| Update Date: | 2017-10-12 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2213698.1
:
DB Replication To Slave Failure On Standby NO
| Related Items |
- Oracle Communications User Data Repository
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Broadband Network Solutions>SN-SND: Tekelec UDR
|
In this Document
Created from <SR 3-13830166151>
Applies to:
Oracle Communications User Data Repository - Version UDR 10.0.1 and later
Information in this document applies to any platform.
Goal
We are seeing Critical Alarms: Replication failure from Primary to Spare site NOs
71796374 31101 2016-12-12 11:07:04.262
CRITICAL
Platform inetrep NO_UDR NO-1B REPL NO-1A
DB Replication To Slave Failure GN_WARNING/WRN child link auditing ^^ [8269:RepChannelGroup.cxx:2199]
71796375 31101 2016-12-12 11:07:04.262
CRITICAL
Platform inetrep NO_UDR NO-1B REPL NO-1B
DB Replication To Slave Failure GN_WARNING/WRN child link auditing ^^ [8269:RepChannelGroup.cxx:2199]
How can we fix this?
Solution
Verify the replication state between the Primary NO and the Standby.
run the following commands on the Primary NO and the servers having the issues.
Execute the commands as a root user and submit them as part of a Service Request.
# procshm -o
# ithrottle
# irepstat -w
Attachments
This solution has no attachment
