资讯

精准传达 • 有效沟通

从品牌网站建设到网络营销策划,从策略到执行的一站式服务

OracleDataguard报错怎么办

这篇文章主要为大家展示了“Oracle Dataguard报错怎么办”,内容简而易懂,条理清晰,希望能够帮助大家解决疑惑,下面让小编带领大家一起研究并学习一下“Oracle Dataguard报错怎么办”这篇文章吧。

成都创新互联公司从2013年成立,是专业互联网技术服务公司,拥有项目网站制作、成都网站制作网站策划,项目实施与项目整合能力。我们以让每一个梦想脱颖而出为使命,1280元五华做网站,已为上家服务,为五华各地企业和个人服务,联系电话:028-86922220

环境:RAC+单机 Dataguard
问题:启动DG备库到mount阶段,启动MRP进程后,发现后台日志不打印归档传输信息,另外备库日志打开ARC1: Becoming the 'no FAL' ARC

1、启动DG备库到mount阶段,启动MRP进程后,发现后台日志不打印归档传输信息,
,发现备库中的日志有报错现象,报:ARC1: Becoming the 'no FAL' ARC错误,告警中日志如下
MMON started with pid=15, OS id=10552
ORACLE_BASE from environment = /oracle/app/oracle
Sun Mar 04 15:44:47 2018
MMNL started with pid=16, OS id=10554
Sun Mar 04 15:44:47 2018
ALTER DATABASE   MOUNT
ARCH: STARTING ARCH PROCESSES
Sun Mar 04 15:44:52 2018
ARC0 started with pid=18, OS id=10561
ARC0: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
ARC0: STARTING ARCH PROCESSES
Successful mount of redo thread 1, with mount id 2557884335
Physical Standby Database mounted.
Lost write protection disabled
Sun Mar 04 15:44:53 2018
ARC1 started with pid=19, OS id=10564
Sun Mar 04 15:44:53 2018
ARC2 started with pid=20, OS id=10566
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
Sun Mar 04 15:44:53 2018
ARC3 started with pid=21, OS id=10568
Completed: ALTER DATABASE   MOUNT
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Sun Mar 04 15:51:20 2018
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (strac)

2、在备库中查询查询状态如下,其中有后台日志报错信息

SQL> SELECT MESSAGE FROM V$DATAGUARD_STATUS;

MESSAGE

ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
ARC3: Archival started

7 rows selected.

3、此时通过第2步是发现备库中有报归档日志错误信息,可以先到主库是查询是否报错
查询结果如下:
SQL> SELECT MESSAGE FROM V$DATAGUARD_STATUS;

MESSAGE

Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby

MESSAGE

PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.

MESSAGE

Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby

MESSAGE

PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.

MESSAGE

Error 12154 received logging on to the standby
PING[ARC2]: Heartbeat failed to connect to standby 'strac'. Error is 12154.
Error 12154 received logging on to the standby

4、通过第三步发现主库中无法连接备库,导致报12154错误,通过分析,由于我们在备库中采集的是静态监听方式来同步数据,在服务器启动时,并不会自动启动静态监听,从而导致RAC和备库不是属于连接状态,

5、解决方法先在备库中手动启动静态监听,观察备库是否报错

[oracle@racdg trace]$ lsnrctl status--查询当前监听状态

LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 04-MAR-2018 15:52:15

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=racdg)(PORT=1521)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux Error: 111: Connection refused
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
TNS-12541: TNS:no listener
TNS-12560: TNS:protocol adapter error
TNS-00511: No listener
Linux Error: 111: Connection refused
[oracle@racdg trace]$ lsnrctl start --启动监听

LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 04-MAR-2018 15:52:24

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Starting /oracle/app/oracle/product/11.2.0/bin/tnslsnr: please wait...

TNSLSNR for Linux: Version 11.2.0.4.0 - Production
System parameter file is /oracle/app/oracle/product/11.2.0/network/admin/listener.ora
Log messages written to /oracle/app/oracle/diag/tnslsnr/racdg/listener/alert/log.xml
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=racdg)(PORT=1521)))
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=racdg)(PORT=1521)))
STATUS of the LISTENER

Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date                04-MAR-2018 15:52:26
Uptime                    0 days 0 hr. 0 min. 0 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /oracle/app/oracle/product/11.2.0/network/admin/listener.ora
Listener Log File         /oracle/app/oracle/diag/tnslsnr/racdg/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=racdg)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "strac" has 1 instance(s).
Instance "strac", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@racdg trace]$ lsnrctl status

LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 04-MAR-2018 15:52:47

Copyright (c) 1991, 2013, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=racdg)(PORT=1521)))
STATUS of the LISTENER

Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.4.0 - Production
Start Date                04-MAR-2018 15:52:26
Uptime                    0 days 0 hr. 0 min. 21 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /oracle/app/oracle/product/11.2.0/network/admin/listener.ora
Listener Log File         /oracle/app/oracle/diag/tnslsnr/racdg/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=racdg)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
Services Summary...
Service "strac" has 1 instance(s).
Instance "strac", status UNKNOWN, has 1 handler(s) for this service...--显示为静态监听
The command completed successfully

6、此时再次查询DG的状态,发现有归档日志传输过到DG库中

SQL> SELECT MESSAGE FROM V$DATAGUARD_STATUS;

MESSAGE

ARC0: Archival started
ARC1: Archival started
ARC2: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC2: Becoming the heartbeat ARCH
ARC2: Becoming the active heartbeat ARCH
ARC3: Archival started
Attempt to start background Managed Standby Recovery process
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Media Recovery Waiting for thread 1 sequence 161

MESSAGE

Fetching gap sequence in thread 1, gap sequence 161-161
RFS[1]: Assigned to RFS process 10600
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_161f9q9gtp0.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_99f9kzzhq2.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_100f9l00mnz.ar
c

Media Recovery Waiting for thread 1 sequence 162
Fetching gap sequence in thread 1, gap sequence 162-162

MESSAGE

RFS[2]: Assigned to RFS process 10604
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_162f9q9h4vb.ar
c

Media Recovery Waiting for thread 1 sequence 163
Fetching gap sequence in thread 1, gap sequence 163-163
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_163f9q9hdxv.ar
c

Media Recovery Waiting for thread 1 sequence 164
Fetching gap sequence in thread 1, gap sequence 164-164

MESSAGE

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_164f9q9hr44.ar
c

Media Recovery Waiting for thread 1 sequence 165
Fetching gap sequence in thread 1, gap sequence 165-165
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_165f9q9j27p.ar
c

Media Recovery Waiting for thread 1 sequence 166
Fetching gap sequence in thread 1, gap sequence 166-166
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_166f9q9jdoq.ar

MESSAGE

c

Media Recovery Waiting for thread 1 sequence 167
Fetching gap sequence in thread 1, gap sequence 167-167
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_167f9q9jotm.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_101f9l02sv8.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_102f9l02wrc.ar

MESSAGE

c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_103f9l8x8b8.ar
c

Media Recovery Waiting for thread 1 sequence 168
Fetching gap sequence in thread 1, gap sequence 168-168
ARC0: Beginning to archive thread 1 sequence 168 (3679660-3724468)
ARC0: Completed archiving thread 1 sequence 168 (0-0)
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_168f9q9lxgy.ar
c

MESSAGE

Media Recovery Waiting for thread 1 sequence 169
Fetching gap sequence in thread 1, gap sequence 169-169
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_169f9q9n23p.ar
c

Media Recovery Waiting for thread 2 sequence 104
ARC1: Beginning to archive thread 2 sequence 104 (3724490-3744517)
ARC1: Completed archiving thread 2 sequence 104 (0-0)
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_104f9q9nc85.ar
c

MESSAGE

Media Recovery Waiting for thread 2 sequence 105
Fetching gap sequence in thread 2, gap sequence 105-105
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_105f9q9no3z.ar
c

Media Recovery Waiting for thread 2 sequence 106
Fetching gap sequence in thread 2, gap sequence 106-106
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_106f9q9o0j5.ar
c

MESSAGE

Media Recovery Waiting for thread 1 sequence 170
Fetching gap sequence in thread 1, gap sequence 170-170
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_170f9q9pcpl.ar
c

Media Recovery Waiting for thread 1 sequence 171
Fetching gap sequence in thread 1, gap sequence 171-171
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_171f9q9pqkc.ar
c

Media Recovery Waiting for thread 1 sequence 172

MESSAGE

Fetching gap sequence in thread 1, gap sequence 172-172
RFS[3]: Assigned to RFS process 10616
RFS[4]: Assigned to RFS process 10614
Primary database is in MAXIMUM PERFORMANCE mode
RFS[5]: Assigned to RFS process 10618
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_172f9q9q3pz.ar
c

Media Recovery Waiting for thread 2 sequence 107 (in transit)
RFS[6]: Assigned to RFS process 10620
RFS[7]: Assigned to RFS process 10622

MESSAGE

RFS[8]: Assigned to RFS process 10624
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_107f9q9q7lr.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_108f9q9q7lv.ar
c

Media Recovery Waiting for thread 1 sequence 173
Fetching gap sequence in thread 1, gap sequence 173-173
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_173f9q9sq3g.ar
c

MESSAGE

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_109f9q9q7z6.ar
c

Media Recovery Waiting for thread 1 sequence 174
Fetching gap sequence in thread 1, gap sequence 174-174
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_174f9q9tz7q.ar
c

Media Recovery Waiting for thread 1 sequence 175
Fetching gap sequence in thread 1, gap sequence 175-175

MESSAGE

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_175f9q9vwo0.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_110f9q9qlco.ar
c

Media Recovery Waiting for thread 1 sequence 176
Fetching gap sequence in thread 1, gap sequence 176-176
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_176f9q9w9h6.ar
c

MESSAGE

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_111f9q9qmng.ar
c

Media Recovery Waiting for thread 1 sequence 177
Fetching gap sequence in thread 1, gap sequence 177-177
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_177f9q9x92z.ar
c

Media Recovery Waiting for thread 1 sequence 178
Fetching gap sequence in thread 1, gap sequence 178-178
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_178f9q9xmc8.ar

MESSAGE

c

Media Recovery Waiting for thread 1 sequence 179
Fetching gap sequence in thread 1, gap sequence 179-179
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_179f9q9xxgx.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_112f9q9qmwy.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_113f9q9qmyd.ar

MESSAGE

c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_114f9q9qncn.ar
c

Media Recovery Waiting for thread 1 sequence 180
Fetching gap sequence in thread 1, gap sequence 180-180
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_180f9q9y7sn.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_115f9q9qncr.ar

MESSAGE

c

Media Recovery Waiting for thread 1 sequence 181
Fetching gap sequence in thread 1, gap sequence 181-181
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_181f9q9ykrr.ar
c

Media Recovery Waiting for thread 1 sequence 182
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_182f9q9ywg8.ar
c

MESSAGE

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_116f9q9qnl3.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_117f9q9qnl7.ar
c

Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_118f9q9qnt2.ar
c

Media Recovery Waiting for thread 1 sequence 183

115 rows selected.

SQL>

7、查看日志中发现有大量的归档日志传输过来,详细的内容如下:
alter database recover managed standby database disconnect from session
Attempt to start background Managed Standby Recovery process (strac)
Sun Mar 04 15:51:20 2018
MRP0 started with pid=22, OS id=10584
MRP0: Background Managed Standby Recovery process started (strac)
Serial Media Recovery started
Managed Standby Recovery not using Real Time Apply
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 161
Fetching gap sequence in thread 1, gap sequence 161-161
Completed: alter database recover managed standby database disconnect from session
Sun Mar 04 15:52:58 2018
Using STANDBY_ARCHIVE_DEST parameter default value as USE_DB_RECOVERY_FILE_DEST
RFS[1]: Assigned to RFS process 10600
RFS[1]: Opened log for thread 1 sequence 161 dbid -1759711868 branch 947273412
Archived Log entry 48 added for thread 1 sequence 161 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:53:06 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_161f9q9gtp0.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_99f9kzzhq2.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_100f9l00mnz.arc
Media Recovery Waiting for thread 1 sequence 162
Fetching gap sequence in thread 1, gap sequence 162-162
Sun Mar 04 15:53:07 2018
RFS[2]: Assigned to RFS process 10604
RFS[2]: Opened log for thread 1 sequence 162 dbid -1759711868 branch 947273412
Archived Log entry 49 added for thread 1 sequence 162 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:53:16 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_162f9q9h4vb.arc
Media Recovery Waiting for thread 1 sequence 163
Fetching gap sequence in thread 1, gap sequence 163-163
RFS[2]: Opened log for thread 1 sequence 163 dbid -1759711868 branch 947273412
Archived Log entry 50 added for thread 1 sequence 163 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:53:26 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_163f9q9hdxv.arc
Media Recovery Waiting for thread 1 sequence 164
Fetching gap sequence in thread 1, gap sequence 164-164
Sun Mar 04 15:53:28 2018
RFS[2]: Opened log for thread 1 sequence 164 dbid -1759711868 branch 947273412
Archived Log entry 51 added for thread 1 sequence 164 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:53:37 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_164f9q9hr44.arc
Media Recovery Waiting for thread 1 sequence 165
Fetching gap sequence in thread 1, gap sequence 165-165
Sun Mar 04 15:53:38 2018
RFS[2]: Opened log for thread 1 sequence 165 dbid -1759711868 branch 947273412
Archived Log entry 52 added for thread 1 sequence 165 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:53:47 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_165f9q9j27p.arc
Media Recovery Waiting for thread 1 sequence 166
Fetching gap sequence in thread 1, gap sequence 166-166
Sun Mar 04 15:53:48 2018
RFS[2]: Opened log for thread 1 sequence 166 dbid -1759711868 branch 947273412
Archived Log entry 53 added for thread 1 sequence 166 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:53:57 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_166f9q9jdoq.arc
Media Recovery Waiting for thread 1 sequence 167
Fetching gap sequence in thread 1, gap sequence 167-167
RFS[2]: Opened log for thread 1 sequence 167 dbid -1759711868 branch 947273412
Archived Log entry 54 added for thread 1 sequence 167 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:54:07 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_167f9q9jotm.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_101f9l02sv8.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_102f9l02wrc.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_02/o1_mf_2_103f9l8x8b8.arc
Media Recovery Waiting for thread 1 sequence 168
Fetching gap sequence in thread 1, gap sequence 168-168
Sun Mar 04 15:55:08 2018
RFS[2]: Selected log 7 for thread 1 sequence 168 dbid -1759711868 branch 947273412
Sun Mar 04 15:55:10 2018
Archived Log entry 55 added for thread 1 sequence 168 ID 0x971d6184 dest 1:
Sun Mar 04 15:55:17 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_168f9q9lxgy.arc
Sun Mar 04 15:55:43 2018
Media Recovery Waiting for thread 1 sequence 169
Fetching gap sequence in thread 1, gap sequence 169-169
Sun Mar 04 15:55:46 2018
RFS[2]: Opened log for thread 1 sequence 169 dbid -1759711868 branch 947273412
Archived Log entry 56 added for thread 1 sequence 169 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:55:54 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_169f9q9n23p.arc
Media Recovery Waiting for thread 2 sequence 104
Sun Mar 04 15:55:55 2018
RFS[1]: Selected log 12 for thread 2 sequence 104 dbid -1759711868 branch 947273412
Sun Mar 04 15:55:55 2018
Archived Log entry 57 added for thread 2 sequence 104 ID 0x971d6184 dest 1:
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_104f9q9nc85.arc
Media Recovery Waiting for thread 2 sequence 105
Fetching gap sequence in thread 2, gap sequence 105-105
Sun Mar 04 15:56:05 2018
RFS[2]: Opened log for thread 2 sequence 105 dbid -1759711868 branch 947273412
Archived Log entry 58 added for thread 2 sequence 105 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:56:14 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_105f9q9no3z.arc
Media Recovery Waiting for thread 2 sequence 106
Fetching gap sequence in thread 2, gap sequence 106-106
Sun Mar 04 15:56:16 2018
RFS[2]: Opened log for thread 2 sequence 106 dbid -1759711868 branch 947273412
Archived Log entry 59 added for thread 2 sequence 106 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:56:24 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_106f9q9o0j5.arc
Sun Mar 04 15:56:49 2018
Media Recovery Waiting for thread 1 sequence 170
Fetching gap sequence in thread 1, gap sequence 170-170
Sun Mar 04 15:56:59 2018
RFS[2]: Opened log for thread 1 sequence 170 dbid -1759711868 branch 947273412
Archived Log entry 60 added for thread 1 sequence 170 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:57:09 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_170f9q9pcpl.arc
Media Recovery Waiting for thread 1 sequence 171
Fetching gap sequence in thread 1, gap sequence 171-171
Sun Mar 04 15:57:11 2018
RFS[2]: Opened log for thread 1 sequence 171 dbid -1759711868 branch 947273412
Archived Log entry 61 added for thread 1 sequence 171 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:57:20 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_171f9q9pqkc.arc
Media Recovery Waiting for thread 1 sequence 172
Fetching gap sequence in thread 1, gap sequence 172-172
Sun Mar 04 15:57:23 2018
RFS[2]: Opened log for thread 1 sequence 172 dbid -1759711868 branch 947273412
Archived Log entry 62 added for thread 1 sequence 172 rlc 947273412 ID 0x971d6184 dest 2:
RFS[2]: Opened log for thread 2 sequence 107 dbid -1759711868 branch 947273412
Sun Mar 04 15:57:28 2018
RFS[3]: Assigned to RFS process 10616
RFS[3]: Opened log for thread 2 sequence 108 dbid -1759711868 branch 947273412
Sun Mar 04 15:57:28 2018
RFS[4]: Assigned to RFS process 10614
RFS[4]: Opened log for thread 2 sequence 109 dbid -1759711868 branch 947273412
Sun Mar 04 15:57:31 2018
Primary database is in MAXIMUM PERFORMANCE mode
RFS[5]: Assigned to RFS process 10618
RFS[5]: Selected log 11 for thread 2 sequence 119 dbid -1759711868 branch 947273412
Sun Mar 04 15:57:34 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_172f9q9q3pz.arc
Media Recovery Waiting for thread 2 sequence 107 (in transit)
Sun Mar 04 15:57:36 2018
Archived Log entry 63 added for thread 2 sequence 107 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:57:38 2018
RFS[6]: Assigned to RFS process 10620
RFS[6]: Opened log for thread 2 sequence 110 dbid -1759711868 branch 947273412
Sun Mar 04 15:57:38 2018
Archived Log entry 64 added for thread 2 sequence 109 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:57:39 2018
Archived Log entry 65 added for thread 2 sequence 108 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:57:39 2018
RFS[7]: Assigned to RFS process 10622
RFS[7]: Opened log for thread 2 sequence 111 dbid -1759711868 branch 947273412
Archived Log entry 66 added for thread 2 sequence 111 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:57:39 2018
RFS[8]: Assigned to RFS process 10624
RFS[8]: Opened log for thread 2 sequence 112 dbid -1759711868 branch 947273412
RFS[7]: Opened log for thread 2 sequence 113 dbid -1759711868 branch 947273412
Archived Log entry 67 added for thread 2 sequence 113 rlc 947273412 ID 0x971d6184 dest 2:
Archived Log entry 68 added for thread 2 sequence 112 rlc 947273412 ID 0x971d6184 dest 2:
RFS[7]: Opened log for thread 2 sequence 114 dbid -1759711868 branch 947273412
RFS[8]: Opened log for thread 2 sequence 115 dbid -1759711868 branch 947273412
Archived Log entry 69 added for thread 2 sequence 114 rlc 947273412 ID 0x971d6184 dest 2:
Archived Log entry 70 added for thread 2 sequence 115 rlc 947273412 ID 0x971d6184 dest 2:
RFS[7]: Opened log for thread 2 sequence 116 dbid -1759711868 branch 947273412
RFS[8]: Opened log for thread 2 sequence 117 dbid -1759711868 branch 947273412
Archived Log entry 71 added for thread 2 sequence 116 rlc 947273412 ID 0x971d6184 dest 2:
Archived Log entry 72 added for thread 2 sequence 117 rlc 947273412 ID 0x971d6184 dest 2:
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_107f9q9q7lr.arc
RFS[7]: Opened log for thread 2 sequence 118 dbid -1759711868 branch 947273412
Archived Log entry 73 added for thread 2 sequence 118 rlc 947273412 ID 0x971d6184 dest 2:
Archived Log entry 74 added for thread 2 sequence 110 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:58:38 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_108f9q9q7lv.arc
Media Recovery Waiting for thread 1 sequence 173
Fetching gap sequence in thread 1, gap sequence 173-173
Sun Mar 04 15:58:47 2018
RFS[6]: Opened log for thread 1 sequence 173 dbid -1759711868 branch 947273412
Archived Log entry 75 added for thread 1 sequence 173 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:58:59 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_173f9q9sq3g.arc
Sun Mar 04 15:59:22 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_109f9q9q7z6.arc
Media Recovery Waiting for thread 1 sequence 174
Fetching gap sequence in thread 1, gap sequence 174-174
Sun Mar 04 15:59:27 2018
RFS[6]: Opened log for thread 1 sequence 174 dbid -1759711868 branch 947273412
Archived Log entry 76 added for thread 1 sequence 174 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 15:59:36 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_174f9q9tz7q.arc
Sun Mar 04 15:59:52 2018
Media Recovery Waiting for thread 1 sequence 175
Fetching gap sequence in thread 1, gap sequence 175-175
Sun Mar 04 15:59:53 2018
db_recovery_file_dest_size of 10240 MB is 4.63% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Sun Mar 04 15:59:56 2018
RFS[6]: Opened log for thread 1 sequence 175 dbid -1759711868 branch 947273412
Archived Log entry 77 added for thread 1 sequence 175 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 16:00:04 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_175f9q9vwo0.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_110f9q9qlco.arc
Media Recovery Waiting for thread 1 sequence 176
Fetching gap sequence in thread 1, gap sequence 176-176
Sun Mar 04 16:00:09 2018
RFS[6]: Opened log for thread 1 sequence 176 dbid -1759711868 branch 947273412
Archived Log entry 78 added for thread 1 sequence 176 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 16:00:21 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_176f9q9w9h6.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_111f9q9qmng.arc
Media Recovery Waiting for thread 1 sequence 177
Fetching gap sequence in thread 1, gap sequence 177-177
Sun Mar 04 16:00:41 2018
RFS[6]: Opened log for thread 1 sequence 177 dbid -1759711868 branch 947273412
Archived Log entry 79 added for thread 1 sequence 177 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 16:00:51 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_177f9q9x92z.arc
Media Recovery Waiting for thread 1 sequence 178
Fetching gap sequence in thread 1, gap sequence 178-178
Sun Mar 04 16:00:51 2018
RFS[6]: Opened log for thread 1 sequence 178 dbid -1759711868 branch 947273412
Archived Log entry 80 added for thread 1 sequence 178 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 16:01:01 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_178f9q9xmc8.arc
Media Recovery Waiting for thread 1 sequence 179
Fetching gap sequence in thread 1, gap sequence 179-179
Sun Mar 04 16:01:01 2018
RFS[6]: Opened log for thread 1 sequence 179 dbid -1759711868 branch 947273412
Archived Log entry 81 added for thread 1 sequence 179 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 16:01:11 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_179f9q9xxgx.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_112f9q9qmwy.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_113f9q9qmyd.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_114f9q9qncn.arc
Media Recovery Waiting for thread 1 sequence 180
Fetching gap sequence in thread 1, gap sequence 180-180
Sun Mar 04 16:01:11 2018
RFS[6]: Opened log for thread 1 sequence 180 dbid -1759711868 branch 947273412
Archived Log entry 82 added for thread 1 sequence 180 rlc 947273412 ID 0x971d6184 dest 2:
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_180f9q9y7sn.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_115f9q9qncr.arc
Media Recovery Waiting for thread 1 sequence 181
Fetching gap sequence in thread 1, gap sequence 181-181
RFS[6]: Opened log for thread 1 sequence 181 dbid -1759711868 branch 947273412
Archived Log entry 83 added for thread 1 sequence 181 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 16:01:31 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_181f9q9ykrr.arc
Media Recovery Waiting for thread 1 sequence 182
Sun Mar 04 16:01:32 2018
RFS[6]: Opened log for thread 1 sequence 182 dbid -1759711868 branch 947273412
Archived Log entry 84 added for thread 1 sequence 182 rlc 947273412 ID 0x971d6184 dest 2:
Sun Mar 04 16:01:42 2018
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_1_182f9q9ywg8.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_116f9q9qnl3.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_117f9q9qnl7.arc
Media Recovery Log /archlog/STRAC/archivelog/2018_03_04/o1_mf_2_118f9q9qnt2.arc
Media Recovery Waiting for thread 1 sequence 183

8、通过日志发现DG库中是正常的,可以通过在主库中做日志切换观察备库中的日志是否打印,若能正常打印则是正常的
在主库中做日志切换:
SQL> archive log list;
Database log mode          Archive Mode
Automatic archival         Enabled
Archive destination        USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     115
Next log sequence to archive   117
Current log sequence           117

SQL> alter system switch logfile;
SQL> /

System altered.

SQL> /

System altered.

SQL> archive log list;
Database log mode          Archive Mode
Automatic archival         Enabled
Archive destination        USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     119
Next log sequence to archive   121
Current log sequence           121
SQL>

9、在备库中日志打印信息,可以判断归档日志是可以正常传输

Sun Mar 04 16:16:04 2018
RFS[5]: Selected log 12 for thread 2 sequence 120 dbid -1759711868 branch 947273412
Sun Mar 04 16:16:05 2018
Archived Log entry 85 added for thread 2 sequence 119 ID 0x971d6184 dest 1:
Sun Mar 04 16:16:13 2018
Archived Log entry 86 added for thread 2 sequence 120 ID 0x971d6184 dest 1:
RFS[5]: Selected log 11 for thread 2 sequence 121 dbid -1759711868 branch 947273412

以上是“Oracle Dataguard报错怎么办”这篇文章的所有内容,感谢各位的阅读!相信大家都有了一定的了解,希望分享的内容对大家有所帮助,如果还想学习更多知识,欢迎关注创新互联行业资讯频道!


本文题目:OracleDataguard报错怎么办
分享路径:http://cdkjz.cn/article/pghhhi.html
多年建站经验

多一份参考,总有益处

联系快上网,免费获得专属《策划方案》及报价

咨询相关问题或预约面谈,可以通过以下方式与我们联系

大客户专线   成都:13518219792   座机:028-86922220