Oracle11新特性——DATA GUARD打开模式下应用归档

cainiao2

up

netbanker

when I create 3 standby logfiles, I noticed the status difference compared with the redo oracle creates by itself, anyone knows the difference?

in standby db:

SQL> select * from V$logfile;

    GROUP# STATUS  TYPE    MEMBER                                             IS_
---------- ------- ------- -------------------------------------------------- ---
         3         ONLINE  /u02/oradata/cat11gst/CAT11GSTredo03.log           NO
         2         ONLINE  /u02/oradata/cat11gst/CAT11GSTredo02.log           NO
         1         ONLINE  /u02/oradata/cat11gst/CAT11GSTredo01.log           NO
         4         STANDBY /u02/oradata/cat11gst/CAT11GST/stb_redo1.log       NO
         5         STANDBY /u02/oradata/cat11gst/CAT11GST/stb_redo2.log       NO
         6         STANDBY /u02/oradata/cat11gst/CAT11GST/stb_redo3.log       NO

6 rows selected.

SQL> select * from V$log;

    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIME
---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- -------------------
         1          1         16   52428800          1 YES CLEARING_CURRENT       1122302 2008-07-22:16:39:26
         2          1         15   52428800          1 YES CLEARING               1122203 2008-07-22:16:34:50
         3          1         16   52428800          1 YES CLEARING               1122302 2008-07-22:16:39:26


RFS[2]: Successfully opened standby log 4: '/u02/oradata/cat11gst/CAT11GST/stb_redo1.log'
Tue Jul 22 16:30:55 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 454692
RFS[3]: Identified database type as 'physical standby'
kcrrvslf: active RFS archival for log 4 thread 1 sequence 12
RFS[3]: Successfully opened standby log 5: '/u02/oradata/cat11gst/CAT11GST/stb_redo2.log'
Tue Jul 22 16:31:16 2008
Media Recovery Log /u02/oradata/cat11gst/arch2/1_11_660407962.dbf
Media Recovery Waiting for thread 1 sequence 12 (in transit)
Recovery of Online Redo Log: Thread 1 Group 4 Seq 12 Reading mem 0
  Mem# 0: /u02/oradata/cat11gst/CAT11GST/stb_redo1.log
Tue Jul 22 16:32:56 2008


seems only new created logfiles are used that status=STANDBY

[ 本帖最后由 netbanker 于 2008-7-23 07:44 编辑 ]

yangtingkun

没有看明白楼上的意思，你创建的不是STANDBY LOGFILE吗？状态当然是STANDBY了

bluemoon0083

yes of course,your standby db only use standby redo logfile,never use online redo logfile
it will be ok even you delete all the online redo logfiles from os

netbanker

when I switch logfile from primary, I can see status changed for:

'/u02/oradata/cat11gst/CAT11GST/stb_redo2.log' by alert log, but  from V$log, changed happens in group 1 ,2,3 which is
'/u02/oradata/cat11gst/CAT11GSTredo03.log' by V$logfile


SQL> select * from V$log; -- see STATUS column

    GROUP#    THREAD#  SEQUENCE#      BYTES    MEMBERS ARC STATUS           FIRST_CHANGE# FIRST_TIME
---------- ---------- ---------- ---------- ---------- --- ---------------- ------------- -------------------
         1          1         16   52428800          1 YES CLEARING_CURRENT       1122302 2008-07-22:16:39:26
         2          1         15   52428800          1 YES CLEARING               1122203 2008-07-22:16:34:50
         3          1         16   52428800          1 YES CLEARING               1122302 2008-07-22:16:39:26

netbanker

also by document, if using redo sync mode,

Synchronous

The synchronous redo transport mode transmits redo data synchronously with respect to transaction commitment. A transaction cannot commit until all redo generated by that transaction has been successfully sent to every enabled redo transport destination that uses the synchronous redo transport mode.

This transport mode is used by the Maximum Protection and Maximum Availability data protection modes


by testing primary still Maximum Performance


SQL> SELECT PROTECTION_MODE FROM V$DATABASE;

PROTECTION_MODE
--------------------
MAXIMUM PERFORMANCE


NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------

log_archive_dest_2   string      SERVICE=CAT11GST SYNC VALID_FO
                                                 R=(ONLINE_LOGFILES,PRIMARY_ROL
                                                 E) DB_UNIQUE_NAME=CAT11GST

javaever

With that feature in place, when a switchover happens, will the new standby in real time query standby mode?

If you want to go back to traditional recover managed mode, you cannot do it on-the-fly. The standby needs to be shutdown and recover managed mode needs to be reenabled

ddyg110

NinGoo 发表于 2007-9-29 09:31
SQL> select * from v$version
  2  ;

我在备库开启了 read only with apply 实时应用。但是重启备库，状态就变成了read only只读了。 这个是怎么回事？

streamsong

貌似12C的DG，好像可以 read write模式下应用日志，而且还支持修改操作，变态啊

Sunleth