如何确认备库的状态word始终显示最终状态跟随主库

来源：蜘蛛抓取(WebSpider) 时间：2016-09-06 06:05 标签： 战网始终保持登录状态
博客访问： 296788
博文数量： 260
注册时间：
IT168企业级官微
微信号：IT168qiye
系统架构师大会
微信号：SACC2013
分类： Linux
主备库切换原因：
1. switch：用户主动切换；
2. failover：主库出现故障，强行切换；
switch切换过程：先主库再备库
1. 查看switchover_status：select database_role, switchover_status from v$
如果switchover_status为：to standby 则：
ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY
否则用：ALTER DATABASE COMMIT TO SWITCHOVER TO PHYSICAL STANDBY WITH SESSION SHUTDOWN;
2. 重启数据库：
3. 以备库mount
alter database mo
1. 应用redo：alter database recover managed standby database dis
2. 查看switchover_status：select database_role, switchover_status from v$
如果switchover_status为：to primary 则：ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY
否则用：ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY WITH SESSION SHUTDOWN;
3. &重启数据库
failover 主备库切换
1.. 停止日志应用 alter database recover managed sta&
2. 关闭standby日志传输 alter database recover managed standby d&
3. 切换到primary alter database commit to switchover to primary w&
做这一步的时候，若存在gap，则会报ORA-16139:Switchover: Media recovery required - standby not in limbo 错误。
做测试的时候，若先起主库再起备库，且未等待备库相关日志传输完毕，就会出现这个问题。此时需要强制切换 alter database activate physi&
4. 重启数据库到open状态
阅读(2627) | 评论(0) | 转发(0) |
相关热门文章
给主人留下些什么吧！~~
请登录后评论。如何配置dataguard一主库 一物理备库 一逻辑备库的相关推荐_百度知道DateGarde主备数据库如何判断哪个是主数据库_百度知道数据库环境
物理备库：
主库　　SHDB
备库　　BJDB
1、查看当前主备库角色、状态信息
主库(SHDB)
10:48:37 SYS@ SHDB&col name for a10
10:54:03 SYS@ SHDB&col database_role for a20
10:54:03 SYS@ SHDB&col protection_mode for a20
10:54:04 SYS@ SHDB&col switchover_status for a20
10:54:04 SYS@ SHDB&select name,protection_mode,database_role,switchover_status from v$database;
PROTECTION_MODE
DATABASE_ROLE
SWITCHOVER_STATUS
---------- -------------------- -------------------- --------------------
MAXIMUM PERFORMANCE
TO STANDBY
备库(BJDB)
01:12:20 SYS@ BJDB&col name for a10
01:16:50 SYS@ BJDB&col database_role for a20
01:16:50 SYS@ BJDB&col protection_mode for a20
01:16:51 SYS@ BJDB&col switchover_status for a20
01:16:51 SYS@ BJDB&select name,protection_mode,database_role,switchover_status from v$database;
PROTECTION_MODE
DATABASE_ROLE
SWITCHOVER_STATUS
---------- -------------------- -------------------- --------------------
MAXIMUM PERFORMANCE
PHYSICAL STANDBY
NOT ALLOWED
2、主库切换成物理备库
10:54:04 SYS@ SHDB&alter database commit to switchover to
Database altered.
注意：如果执行上述SQL命令失败，如下述现象，说明有其他的SESSION(除当前的SYS用户之外)在登陆ORACLE；当然如果直接执行成功，下面的情况就可以不用再执行了.
23:25:58 SYS@ BJDB&alter database commit to switchover to
alter database commit to switchover to standby
ERROR at line 1:
ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected
23:32:38 SYS@ BJDB&alter database commit to switchover to standby with session shutdown;
Database altered.
23:35:10 SYS@ BJDB&
2.1、执行完成切换之后，数据库处于关闭状态，需要手工启动到mount状态；
11:03:06 SYS@ SHDB&select open_mode from v$database;
select open_mode from v$database
ERROR at line 1:
ORA-01507: database not mounted
11:03:25 SYS@ SHDB&shutdown
ORA-01507: database not mounted
ORACLE instance shut down.
11:04:05 SYS@ SHDB&
ORACLE instance started.
Total System Global Area
Fixed Size
1339824 bytes
Variable Size
Database Buffers
Redo Buffers
5132288 bytes
Database mounted.
11:04:17 SYS@ SHDB&select open_mode from v$database;
------------------------------------------------------------
11:04:26 SYS@ SHDB&
2.2、查看当前数据库(SHDB)角色为PHYSICAL STANDBY
11:04:17 SYS@ SHDB&select open_mode from v$database;
------------------------------------------------------------
11:04:26 SYS@ SHDB&col name for a10
11:05:45 SYS@ SHDB&col database_role for a20
11:05:45 SYS@ SHDB&col protection_mode for a20
11:05:45 SYS@ SHDB&col switchover_status for a20
11:05:45 SYS@ SHDB&select name,protection_mode,database_role,switchover_status from v$database;
PROTECTION_MODE
DATABASE_ROLE
SWITCHOVER_STATUS
---------- -------------------- -------------------- --------------------
MAXIMUM PERFORMANCE
PHYSICAL STANDBY
TO PRIMARY
3、备库(BJDB)切换为主库
01:16:51 SYS@ BJDB&col name for a10
01:30:48 SYS@ BJDB&col database_role for a20
01:30:48 SYS@ BJDB&col protection_mode for a20
01:30:48 SYS@ BJDB&col switchover_status for a20
01:30:48 SYS@ BJDB&select name,protection_mode,database_role,switchover_status from v$database;
PROTECTION_MODE
DATABASE_ROLE
SWITCHOVER_STATUS
---------- -------------------- -------------------- --------------------
MAXIMUM PERFORMANCE
PHYSICAL STANDBY
SESSIONS ACTIVE
此时我们注意到一个奇怪的现象，主库(SHDB)与备库(BJDB)此时此刻都处于PHYSICAL STANDBY状态。实际上这是一个中间状态.
3.1、执行备库(BJDB)切换为主库
01:30:48 SYS@ BJDB&alter database commit to switchover to primary;
alter database commit to switchover to primary
ERROR at line 1:
ORA-01093: ALTER DATABASE CLOSE only permitted with no sessions connected
01:32:42 SYS@ BJDB&alter database commit to switchover to primary with session shutdown;
Database altered.
3.2、查看备库(BJDB)已经处于PRIMARY状态，也就是说备库切换为主库成功了
01:32:42 SYS@ BJDB&alter database commit to switchover to primary with session shutdown;
Database altered.
01:33:22 SYS@ BJDB&col name for a10
01:33:55 SYS@ BJDB&col database_role for a20
01:33:55 SYS@ BJDB&col protection_mode for a20
01:33:55 SYS@ BJDB&col switchover_status for a20
01:33:56 SYS@ BJDB&select name,protection_mode,database_role,switchover_status from v$database;
PROTECTION_MODE
DATABASE_ROLE
SWITCHOVER_STATUS
---------- -------------------- -------------------- --------------------
MAXIMUM PERFORMANCE
NOT ALLOWED
3.3、切换完成数据库(SHDB)之后，数据库处于mounted状态，需要手工切换至open
01:35:33 SYS@ BJDB&select status from v$
------------------------------------
01:35:41 SYS@ BJDB&alter database open;
Database altered.
01:35:50 SYS@ BJDB&select status from v$
------------------------------------
4、监控主库(BJDB)启动进程
01:36:03 SYS@ BJDB&select process,status from v$managed_
--------------------------- ------------------------------------
5、监控备库(SHDB)启动进程.
11:05:46 SYS@ SHDB&select process,status from v$managed_
--------------------------- ------------------------------------
6 rows selected.
注意：备库上才有RFS进程的
6、至此主库与备库的角色已经成功切换完成.接下来可以在监控主库与备库的告警日志、归档日志信息的同时，主库产生一些新数据，备库接收并应用归档日志.
##############################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&& 华丽的分割线 &&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
#################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################试验：验证备库接收应用归档日志
1、主库产生新数据
01:38:36 SYS@ BJDB&conn test/test
Connected.
01:49:49 TEST@ BJDB&select count(*) from
----------
01:49:56 TEST@ BJDB&insert into emp select * from
54784 rows created.
01:50:24 TEST@ BJDB&commit;
Commit complete.
01:50:28 TEST@ BJDB&select count(*) from
----------
01:50:33 TEST@ BJDB&
2、主库发生日志切换
01:50:59 TEST@ BJDB&conn / as sysdba
Connected.
01:51:04 SYS@ BJDB&alter s
System altered.
3、备库应用归档日志(备库库处于mount状态)
11:29:57 SYS@ SHDB&select open_mode from v$database;
------------------------------------------------------------
11:30:48 SYS@ SHDB&select sequence#,name,applied from v$archived_
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
119 /dsk4/arch_shdb/arch_1_119_.log
120 /dsk4/arch_shdb/arch_1_120_.log
121 /dsk4/arch_shdb/arch_1_121_.log
122 /dsk4/arch_shdb/arch_1_122_.log
123 /dsk4/arch_shdb/arch_1_123_.log
124 /dsk4/arch_shdb/arch_1_124_.log
125 /dsk4/arch_shdb/arch_1_125_.log
126 /dsk4/arch_shdb/arch_1_126_.log
127 /dsk4/arch_shdb/arch_1_127_.log
128 /dsk4/arch_shdb/arch_1_128_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
129 /dsk4/arch_shdb/arch_1_129_.log
130 /dsk4/arch_shdb/arch_1_130_.log
131 /dsk4/arch_shdb/arch_1_131_.log
132 /dsk4/arch_shdb/arch_1_132_.log
133 /dsk4/arch_shdb/arch_1_133_.log
134 /dsk4/arch_shdb/arch_1_134_.log
135 /dsk4/arch_shdb/arch_1_135_.log
136 /dsk4/arch_shdb/arch_1_136_.log
137 /dsk4/arch_shdb/arch_1_137_.log
138 /dsk4/arch_shdb/arch_1_138_.log
139 /dsk4/arch_shdb/arch_1_139_.log
140 /dsk4/arch_shdb/arch_1_140_.log
141 /dsk4/arch_shdb/arch_1_141_.log
142 /dsk4/arch_shdb/arch_1_142_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
143 /dsk4/arch_shdb/arch_1_143_.log
144 /dsk4/arch_shdb/arch_1_144_.log
145 /dsk4/arch_shdb/arch_1_145_.log
146 /dsk4/arch_shdb/arch_1_146_.log
148 /dsk4/arch_shdb/arch_1_148_.log
147 /dsk4/arch_shdb/arch_1_147_.log
166 /dsk4/arch_shdb/arch_1_166_.log
149 /dsk4/arch_shdb/arch_1_149_.log
150 /dsk4/arch_shdb/arch_1_150_.log
151 /dsk4/arch_shdb/arch_1_151_.log
152 /dsk4/arch_shdb/arch_1_152_.log
154 /dsk4/arch_shdb/arch_1_154_.log
153 /dsk4/arch_shdb/arch_1_153_.log
155 /dsk4/arch_shdb/arch_1_155_.log
156 /dsk4/arch_shdb/arch_1_156_.log
157 /dsk4/arch_shdb/arch_1_157_.log
158 /dsk4/arch_shdb/arch_1_158_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
159 /dsk4/arch_shdb/arch_1_159_.log
160 /dsk4/arch_shdb/arch_1_160_.log
161 /dsk4/arch_shdb/arch_1_161_.log
162 /dsk4/arch_shdb/arch_1_162_.log
163 /dsk4/arch_shdb/arch_1_163_.log
165 /dsk4/arch_shdb/arch_1_165_.log
164 /dsk4/arch_shdb/arch_1_164_.log
167 /dsk4/arch_shdb/arch_1_167_.log
168 /dsk4/arch_shdb/arch_1_168_.log
169 /dsk4/arch_shdb/arch_1_169_.log
170 /dsk4/arch_shdb/arch_1_170_.log
171 /dsk4/arch_shdb/arch_1_171_.log
172 /dsk4/arch_shdb/arch_1_172_.log
173 /dsk4/arch_shdb/arch_1_173_.log
174 /dsk4/arch_shdb/arch_1_174_.log
175 /dsk4/arch_shdb/arch_1_175_.log
176 /dsk4/arch_shdb/arch_1_176_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
177 /dsk4/arch_shdb/arch_1_177_.log
178 /dsk4/arch_shdb/arch_1_178_.log
179 /dsk4/arch_shdb/arch_1_179_.log
180 /dsk4/arch_shdb/arch_1_180_.log
181 /dsk4/arch_shdb/arch_1_181_.log
182 /dsk4/arch_shdb/arch_1_182_.log
183 /dsk4/arch_shdb/arch_1_183_.log
184 /dsk4/arch_shdb/arch_1_184_.log
185 /dsk4/arch_shdb/arch_1_185_.log
186 /dsk4/arch_shdb/arch_1_186_.log
187 /dsk4/arch_shdb/arch_1_187_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
188 /dsk4/arch_shdb/arch_1_188_.log
86 rows selected.
11:32:35 SYS@ SHDB&alter database recover managed standby database disconnect from
Database altered.
再次查看v$archived_log已经归开始陆续应用
11:34:31 SYS@ SHDB&select sequence#,name,applied from v$archived_
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
119 /dsk4/arch_shdb/arch_1_119_.log
120 /dsk4/arch_shdb/arch_1_120_.log
121 /dsk4/arch_shdb/arch_1_121_.log
122 /dsk4/arch_shdb/arch_1_122_.log
123 /dsk4/arch_shdb/arch_1_123_.log
124 /dsk4/arch_shdb/arch_1_124_.log
125 /dsk4/arch_shdb/arch_1_125_.log
126 /dsk4/arch_shdb/arch_1_126_.log
127 /dsk4/arch_shdb/arch_1_127_.log
128 /dsk4/arch_shdb/arch_1_128_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
129 /dsk4/arch_shdb/arch_1_129_.log
130 /dsk4/arch_shdb/arch_1_130_.log
131 /dsk4/arch_shdb/arch_1_131_.log
132 /dsk4/arch_shdb/arch_1_132_.log
133 /dsk4/arch_shdb/arch_1_133_.log
134 /dsk4/arch_shdb/arch_1_134_.log
135 /dsk4/arch_shdb/arch_1_135_.log
136 /dsk4/arch_shdb/arch_1_136_.log
137 /dsk4/arch_shdb/arch_1_137_.log
138 /dsk4/arch_shdb/arch_1_138_.log
139 /dsk4/arch_shdb/arch_1_139_.log
140 /dsk4/arch_shdb/arch_1_140_.log
141 /dsk4/arch_shdb/arch_1_141_.log
142 /dsk4/arch_shdb/arch_1_142_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
143 /dsk4/arch_shdb/arch_1_143_.log
144 /dsk4/arch_shdb/arch_1_144_.log
145 /dsk4/arch_shdb/arch_1_145_.log
146 /dsk4/arch_shdb/arch_1_146_.log
148 /dsk4/arch_shdb/arch_1_148_.log
147 /dsk4/arch_shdb/arch_1_147_.log
166 /dsk4/arch_shdb/arch_1_166_.log
149 /dsk4/arch_shdb/arch_1_149_.log
150 /dsk4/arch_shdb/arch_1_150_.log
151 /dsk4/arch_shdb/arch_1_151_.log
152 /dsk4/arch_shdb/arch_1_152_.log
154 /dsk4/arch_shdb/arch_1_154_.log
153 /dsk4/arch_shdb/arch_1_153_.log
155 /dsk4/arch_shdb/arch_1_155_.log
156 /dsk4/arch_shdb/arch_1_156_.log
157 /dsk4/arch_shdb/arch_1_157_.log
158 /dsk4/arch_shdb/arch_1_158_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
159 /dsk4/arch_shdb/arch_1_159_.log
160 /dsk4/arch_shdb/arch_1_160_.log
161 /dsk4/arch_shdb/arch_1_161_.log
162 /dsk4/arch_shdb/arch_1_162_.log
163 /dsk4/arch_shdb/arch_1_163_.log
165 /dsk4/arch_shdb/arch_1_165_.log
164 /dsk4/arch_shdb/arch_1_164_.log
167 /dsk4/arch_shdb/arch_1_167_.log
168 /dsk4/arch_shdb/arch_1_168_.log
169 /dsk4/arch_shdb/arch_1_169_.log
170 /dsk4/arch_shdb/arch_1_170_.log
171 /dsk4/arch_shdb/arch_1_171_.log
172 /dsk4/arch_shdb/arch_1_172_.log
173 /dsk4/arch_shdb/arch_1_173_.log
174 /dsk4/arch_shdb/arch_1_174_.log
175 /dsk4/arch_shdb/arch_1_175_.log
176 /dsk4/arch_shdb/arch_1_176_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
177 /dsk4/arch_shdb/arch_1_177_.log
178 /dsk4/arch_shdb/arch_1_178_.log
179 /dsk4/arch_shdb/arch_1_179_.log
180 /dsk4/arch_shdb/arch_1_180_.log
181 /dsk4/arch_shdb/arch_1_181_.log
182 /dsk4/arch_shdb/arch_1_182_.log
183 /dsk4/arch_shdb/arch_1_183_.log
184 /dsk4/arch_shdb/arch_1_184_.log
185 /dsk4/arch_shdb/arch_1_185_.log
186 /dsk4/arch_shdb/arch_1_186_.log
187 /dsk4/arch_shdb/arch_1_187_.log
SEQUENCE# NAME
---------- ------------------------------------------------------------ ---------------------------
188 /dsk4/arch_shdb/arch_1_188_.log
86 rows selected.
4、备库取消应用归档日志
11:34:32 SYS@ SHDB&alter database recover managed standby database
Database altered.
5、备库开启到open(read only)状态
11:35:58 SYS@ SHDB&alter database open;
Database altered.
11:36:18 SYS@ SHDB&select open_mode from v$database;
------------------------------------------------------------
6、备库应用归档日志
11:36:27 SYS@ SHDB&alter database recover managed standby database disconnect from
Database altered.
7、备库查看产生的新数据
11:37:27 SYS@ SHDB&select count(*) from test.
----------
8、在主库与备库都处于open状态下，模拟生产数据，备库应用归档日志同时对外提供查询服务
主库truncate掉test.emp表中的10万多条数据，并发生一次切换日志
01:51:11 SYS@ BJDB&conn test/test
Connected.
02:01:27 TEST@ BJDB&truncate table
Table truncated.
02:01:38 TEST@ BJDB&select count(*) from
----------
02:01:49 TEST@ BJDB&conn / as sysdba
Connected.
02:01:54 SYS@ BJDB&alter s
System altered.
备库查看test.emp表中的数据
11:37:57 SYS@ SHDB&select count(*) from test.
----------
阅读(...) 评论()股票/基金&
散户跟随主力操作必须知道的
　　市场操作一般以下列法则为依据：　　1、市场人气状态决定拒绝股价的涨跌　　2、供求关系的变化是股价变动的依据　　3、股价的操作必须灵活，不能一味的做多或做空　　4、必须有能力控制筹码　　5、操作必须理性，对散户心理了解必须透彻　　市场主力操作股价并不是件轻松的事，因为资金大，又需要考虑散户的心态，大势的走向等等。而散户的行动比主力灵活得多，这就为散户赚钱创造了条件。散户的最佳选股策略是选择那些主力吸货完成刚刚开始拉升的股票，然后在主力出货之前或刚出货时卖出。要做到这些，必须注意跟随主力的策略。　　散户捕捉主力行踪的方法不外乎两种，其一是从成交量分析，从走势看出主力意图。要做到这一点，必须加强看盘功夫的锻炼，全面掌握各种技术分析方法。关于如何从盘面看出庄家的行动，说起来是十分丰富的话题，但无论如何，散户先应该掌握基本的技术分析方法，在此基础上，再练些套路，这些套路可以是庄家主力操盘的常见手法，比如洗盘，拉抬等等。练好了套路并非就天下无敌了，应该再向更高的境界冲击。有时你会被庄家的花招陷阱所迷惑，或者，你明明知道壮举在洗盘，却还是因为害怕而抛出股票，这是你面对的问题已不是技术上的了，而是心理上的问题，关键在于功力不够，信心不够。这时即使你掌握了花拳绣腿，仍然敌不过凶悍庄家的简单招术。这时你面对战胜庄家的第二个境界：即如何加强自己的内功修炼。　　散户捕捉主力行踪的另一种方法，是从主力制造的种种市场气氛中看出主力的真实意图，即从市场气氛与庄股实际走势的反差之中发现问题。在主力吸货时，常常会有利空消息传出来，如果你看到家极力唱空，但这只股票的走势分明显示有庄家吸货的痕迹，那还有什么疑问呢？在主力出货的时候，往往当天各种股评都会推出该股，似乎一定要在今天买入才能甘心.,但该股当天竟冲高回落，成交量巨大，那不是主力出货又是什么呢？　　散户平时要加强的基本分析及炒作题材分析，借以找出可以被主力介入的个股。除了注意关注上市公司的各种报导之外，更需多注意筹码归向分析，追踪盘面浮码多少。如果发现浮码日益减少，应密切注意。　　散户介入每只股票之前，必须考虑风险与报酬的比例，必须注意到介入该股的价位与长期底部的距离，乖离率的大小登因素。散户跟随主力时选择理想的底部介入才是最佳和最安全的策略。毕竟股价要大涨，必须要有健全而完整的底部图形，筹码安全性高，将来上升的阻力才会小。底部结构不理想的个股，很难有好的表现。投资着千万不要忽视一个完整的底部图形，更不要无视它的威力，嘲弄或不信任完美图形的人，无异与市场作对，逆的操作是会受到重创的。　　几乎所有的坚实底部，在它的低点或是平台部位都会出现成交量剧减的局面，这种现象表示卖压已经消竭，持股者不再愿意杀低。如果此后，成交量再一路放大，且股价收涨，那就表示有一股新的力量介入，主力进场做多的意图表现无遗，投资者可以大胆跟进，利润必远大于风险。　　【财富至尊】今天，笔者为大家挖掘一只集成电路龙头+智能穿戴第一股+半导体领军者+爆发性超强+政策红利=翻倍的黑马股，透露四大方向扶持集成电路，政策红利迅速释放，消息面利好不断，各路资金疯狂抢筹，成长空间十分惊人，暴涨姿势即将开拔！
03/14 15:2603/14 15:2503/03 08:5402/28 08:24
暂无专家推荐本文
同时转发到我的微博
将自动提交到和讯看点，
请输入您的观点并提交。
请输入您的观点 168字以内
同时转发到我的微博置顶我的观点
每日要闻推荐
社区精华推荐
精彩专题图鉴
网上投洽会
　　【独家稿件声明】凡注明“和讯”来源之作品（文字、图片、图表），未经和讯网授权，任何媒体和个人不得全部或者部分转载。如需转载，请与010-联系；经许可后转载务必请注明出处，并添加源链接，违者本网将依法追究责任。

我要回帖

更多关于 战网始终保持登录状态 的文章

 

随机推荐