当前位置:网站首页>Simulate not all endpoints registered exceptions and Solutions
Simulate not all endpoints registered exceptions and Solutions
2022-07-23 07:54:00 【51CTO】
database :oracle 11.2.0.4
System :CentOS 7.9
Environmental Science :rac (2 node )
The goal of the experiment : simulation not all endpoints registered abnormal , And providing solutions .
1、 database information
1.1、IP Information
explain :192.168.133.162 The vip Later as a test IP, Particular attention .
1.2、 Login authentication
explain : Two nodes use hisdb1-vip Can log into the database .
1.3、 State of the cluster
explain : Note here scan ip stay hisdb2 On .
1.4、vip state
see vip 192.168.133.162 state
2、 Simulate anomalies
2.1、 close vip
Now shut down vip 192.168.133.162.
explain : close hisdb1 Of vip after ,ifconfig Will not show ens33:1 Information .
2.2、 State of the cluster
close hisdb1-vip Then view the cluster status .
explain : Now the node 1 Monitoring status and vip Turn into OFFLINE. And through nodes 1 Of public ownership IP、VIP Cannot log into the database . Through node 2 Of public ownership ip、vip、scan ip The connection is normal .
2.3、 Solution
2.3.1、 Trial and error scheme
It is found that the listening status is off,rac Environment with oracle The user starts listening . explain :scan ip At the node 2, The following will happen .
scan ip At the node 1 The author did not save the data after the test , But you can also test it yourself and leave a message in the comment area .
A few minutes later, no service was found , Even if alter system register Re register to listen , Still no service .
grid The user views the monitoring situation as follows , Abnormal listening .
Use at this time grid The user starts listening .
View the cluster status , Found Not All Endpoints Registered Report errors , As shown below , This error is successfully simulated .
This error report was also encountered by the author during a patrol inspection , Presumably, the customer used oracle The user found that the status was wrong after starting monitoring , And then use grid The user starts listening , Check the monitoring status as above and think it is normal , Here, the author reproduces the problem and tests the use node 1 Of public ownership IP and VIP You can still connect to the database , So this leads to customers thinking that database monitoring has returned to normal .
The solution of this trial and error solution :
explain : Find out hisdb1 There are two listeners , Database ORACLE_HOME There is also a , Cause the port 1521 Occupy ,kill process 10097, After that, the monitoring returned to normal .
2.3.2、 Correct scheme
As you can see , The monitor didn't get up , It should be in hisdb1 use grid The user starts listening , The above exception will not appear , and vip Also open with monitoring .
边栏推荐
猜你喜欢

File upload, server file name Chinese garbled file upload, server file name Chinese garbled

Implementation of remove function

自定义flink es source

Graduation project ----- Internet of things environment detection system based on stm32

驱动页面性能优化的3个有效策略

【翻译】宣布Krius--加速你对Kubernetes的监控采用

Mysql A left(right) join B on A.id=B.id and A.age=1与A left(right) join B on A.id=B.id where A.age=1

延伸联接边界,扩展业务范围,全面迈向智能云网2.0时代

信息系统项目管理师必背核心考点(四十九)合同法

1.10 API 和字符串
随机推荐
File upload, server file name Chinese garbled file upload, server file name Chinese garbled
BGP笔记(二)
Information system project managers must recite the core examination points (49) contract law
Customize flick es source
大厂底层必修:“应用程序与 AMS 的通讯实现”
用Stanford Parse(智能语言处理)去实现分词器
程序员最想干的三件事 |漫画
pny 文件转图片
真人踩过的坑,告诉你避免自动化测试常犯的10个错误
Patrick McHardy事件对开源社区的影响
LAN SDN hard core technology insider 18 beautiful new world
Scala when used Performance problems of contains().Exists()
With 130 new services and functions a year, this storage "family bucket" has grown again
记一次线上SQL死锁事故:如何避免死锁?
Flick batch reading es
How to use the order flow analysis tool (Part 2)
船舶测试/ IMO A.799 (19)船用结构材料不燃性试验
RN底层原理 -- 1. Component和PureComponent解析
我为OpenHarmony 写代码,战“码”先锋第二期正式开启!
CPU/GPU(CUDA)版本的 YOLOv5后处理代码