正常的步骤关闭数据库
Alter system checkpoint；
Alter system switch logfile；
Shutdown immediate；
Shutdown命令執行中在alert log中報錯 如附件
之後shutdown 命令異常終止
sys@sfc12db> shutdown immediate;
ORA-00448: normal completion of background process
Alert.log
Job queue slave processes stopped
Tue Aug 9 17:58:05 2011
Error 1017 received logging on to the standby
------------------------------------------------------------
Check that the primary and standby are using a password file
and remote_login_passwordfile is set to SHARED or EXCLUSIVE,
and that the SYS password is same in the password files.
returning error ORA-16191
------------------------------------------------------------
Tue Aug 9 17:58:05 2011
Errors in file /apps/oracle/admin/sfc12db/bdump/sfc12db3_arc9_28977.trc:
ORA-16191: Primary log shipping client not logged on standby
PING[ARC9]: Heartbeat failed to connect to standby 'sfc12stb'. Error is 16191.
alter database recover managed standby database using current logfile
Tue Aug 9 23:30:52 2011
Media Recovery Start: Managed Standby Recovery (sfc12db1)
Tue Aug 9 23:30:52 2011
Managed Standby Recovery starting Real Time Apply
Tue Aug 9 23:30:53 2011
parallel recovery started with 3 processes
Media Recovery Log +STANDBY_ARCH/sfc12stb/archivelog/2011_08_09/thread_3_seq_75093.748.758760043
Media Recovery Log +STANDBY_ARCH/sfc12stb/archivelog/2011_08_09/thread_1_seq_74711.1087.758758331
Media Recovery Waiting for thread 2 sequence 46805
Fetching gap sequence in thread 2, gap sequence 46805-46904
Tue Aug 9 23:31:08 2011
Using STANDBY_ARCHIVE_DEST parameter default value as +STANDBY_ARCH
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 5332
RFS[1]: Identified database type as 'physical standby'
Tue Aug 9 23:31:08 2011
RFS LogMiner: Client disabled from further notification
Tue Aug 9 23:31:15 2011
FAL[client]: Failed to request gap sequence
GAP - thread 2 sequence 46805-46904
DBID 1192333070 branch 679867280
FAL[client]: All defined FAL servers have been attempted.
报了一堆如上面稀奇古怪的问题，密码不对，不需要的archived log都出来了。先把密码改回以前的密码，开始也不行，后来不知道自己就可以做了，也没有报错了，神奇的Oracle！
步骤大致如下：
1、在Primary 3个节点用orapwd修改密码为原来的，以后修改sys密码都用orapwd去做：
orapwd file=orapwsfc12db1 password=oracleracdb entries=10 force=y
orapwd file=orapwsfc12db2 password=oracleracdb entries=10 force=y
orapwd file=orapwsfc12db3 password=oracleracdb entries=10 force=y
2. 在 standby 2个节点上也修改：
orapwd file=orapwsfc12db1 password=oracleracdb entries=10 force=y
orapwd file=orapwsfc12db2 password=oracleracdb entries=10 force=y
3. 重启standby db去recover log，检查alert log发现开始同步：
alter database recover managed standby database cancel;
shutdown immediate
startup mount
alter database recover managed standby database using current logfile disconnect;
4. 然后重复步骤1去修改primary上sys密码：
orapwd file=orapwsfc12db1 password=sfcs12pass entries=10 force=y
orapwd file=orapwsfc12db2 password=sfcs12pass entries=10 force=y
orapwd file=orapwsfc12db3 password=sfcs12pass entries=10 force=y
5. 重复步骤2去修改standby 上sys密码：
orapwd file=orapwsfc12db1 password=sfcs12pass entries=10 force=y
orapwd file=orapwsfc12db2 password=sfcs12pass entries=10 force=y
6. 重复步骤3重启standby db观察修改密码是否可以同步，结果正常：
alter database recover managed standby database cancel;
shutdown immediate
startup mount
alter database recover managed standby database using current logfile disconnect;
7. 在DP的SFC12DB的备份中check configuration没有问题。
要点就是修改sys密码用orapwd，并且在所有Primary&standby 节点上都要做，并修改检查DP上备份的密码。
当前位置：
论坛首页 »
自由讨论区 »
MySQL, Oracle及数据库讨论区
»
[转帖]修改sys密码导致节点关闭失败及standby db无法同步-处理过程
发起投票
技术讨论
加好友
发消息
2019-9-19 11:11:25 |
赞(
操作
