當前位置：首頁 > 编程资源 > 编程问答 >内容正文

编程问答

ORACLE 11G 搭建dataguard详细步骤（所有操作总结）

發布時間：2025/1/21 编程问答 34 豆豆

生活随笔收集整理的這篇文章主要介紹了 ORACLE 11G 搭建dataguard详细步骤（所有操作总结）小編覺得挺不錯的,現在分享給大家,幫大家做個參考.

序言：
DATAGUARD是通過建立一個PRIMARY和STANDBY組來確立其參照關系。
STANDBY一旦創建，DATAGUARD就會通過將主數據庫(PRIMARY)的REDO傳遞給STANDBY數據庫，然后在STANDBY中應用REDO實現數據庫的同步。

有兩種類型的STANDBY：物理STANDBY和邏輯STANDBY
物理STANDBY提供與主數據庫完全一樣的拷貝（塊到塊），數據庫SCHEMA，包括索引都是一樣的。它是直接應用REDO實現同步的。
邏輯STANDBY則不是這樣，在邏輯STANDBY中，邏輯信息是相同的，但物理組織和數據結構可以不同，它和主庫保持同步的方法是將接收的REDO轉換成SQL語句，然后在STANDBY上執行SQL語句。邏輯STANDBY除災難恢復外還有其它用途，比如用于用戶進行查詢和報表。

1、安裝環境
在primary搭建數據庫軟件，建立lsnrctl監聽，采用dbca搭建實例，在standby上搭建數據庫軟件，建立監聽，但是不需要采用dbca建立實例。
如何在linux上搭建oracle數據庫，請參考以前的blog實驗：http://blog.itpub.net/26230597/viewspace-1413242/
操作系統：都是centos6.4
oracle軟件版本： oracle 11.2.0.1.0
IP地址： primary庫（192.168.121.217）、standby庫（192.168.121.218）
db_unique_name： primary庫（pdunq）、standby庫（pdunq_dg）

2、準備工作在primary上操作
2.1、打開Forced Logging 模式
先確認primary庫處于歸檔模式
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 362
Next log sequence to archive 364
Current log sequence 364
SQL>

強制歸檔
SQL> alter database force logging;

Database altered.

SQL>
確認primary庫是歸檔模式

添加standby文件
alter database add standby logfile group 4 ('/home/oradata/powerdes/redo_dg_021.log') size 20M;
alter database add standby logfile group 5 ('/home/oradata/powerdes/redo_dg_022.log') size 20M;
alter database add standby logfile group 6 ('/home/oradata/powerdes/redo_dg_023.log') size 20M;
alter database drop standby logfile group 4;
alter database drop standby logfile group 5;
alter database drop standby logfile group 6;

select * from v$logfile order by 1;

2.3 準備參數文件
2.3.1 生成pfile
create pfile from spfile;
shutdown immediate

2.3.2 修改pfile
cp $ORACLE_HOME/dbs/initpowerdes.ora $ORACLE_HOME/dbs/initpowerdes.ora.bak
vim $ORACLE_HOME/dbs/initpowerdes.ora
*.db_unique_name=pdunq
*.diagnostic_dest='/oracle/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=powerdesXDB)'
*.fal_client='pdunq'
*.fal_server='pdunq_dg'
*.standby_file_management='AUTO'
*.db_file_name_convert='/home/oradata/powerdes','/home/oradata/pwerdes'
*.log_file_name_convert='/home/oradata/powerdes','/home/oradata/powerdes'
*.log_archive_config='DG_CONFIG=(pdunq,pdunq_dg)'
*.log_archive_dest_2='SERVICE=pdunq_dg lgwr sync affirm VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pdunq_dg'
*.log_archive_dest_state_2='ENABLE'

2.3.3 生成spfile
create spfile from pfile;
startup #這里可以啟動也可以不啟動，這里不啟動，后面就要記得startup;讓新的參數文件生效

2.4 修改監聽文件
[oracle@powerlong4 admin]$ vim listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = powerdes)
(ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1)
)
)

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.121.217)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
)

ADR_BASE_LISTENER = /oracle/app/oracle
INBOUND_CONNECT_TIMEOUT_listener=10

2.5，修改tns配置文件
[oracle@powerlong4 admin]$ vim tnsnames.ora
PD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.121.217)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = pdunq)
)
)

SC_SID =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.121.218)(PORT = 1521))
)
(CONNECT_DATA =
(SID = powerdes)
(SERVER = DEDICATED)
)
)

EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
)
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)
)

2.6 監聽服務重啟
lsnrctl stop
lsnrctl start

2.7 primary上配置最大可用模式：
SQL>startup
SQL>alter database set standby database to maximize availability;

2.8 備份數據庫
backup database plus archivelog;
backup current controlfile for standby;
exit;
備份結束后會在閃回區產生備份文件

3，數據庫配置 standby上
3.1 建立相應的文件目錄
包括dump文件目錄，數據文件目錄，通過show parameter dest;查看，保持和primary一樣的路徑地址

3.2 從primary上copy數據文件到standby上
在主庫上執行：
ps：在primary上執行
copy閃回區內容
copy閃回文件
cd /oracle/app/oracle/flash_recovery_area/
scp -r ./* 192.168.121.218:/oracle/app/oracle/flash_recovery_area/

copy參數文件
cd /oracle/app/oracle/product/11.2.0/dbhome_1/dbs
scp -r ./* 192.168.121.218:/oracle/app/oracle/product/11.2.0/dbhome_1/dbs

copy監聽文件
cd /oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/
scp -r ./* 192.168.121.218:/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/

3.3 在standby庫修改配置文件在standby上修改
[oracle@powerlong5 admin]$ vim listener.ora

# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1)
(PROGRAM = extproc)
)
(SID_DESC =
(SID_NAME = powerdes)
(ORACLE_HOME = /oracle/app/oracle/product/11.2.0/dbhome_1)
)
)

LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.121.218)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
)
)

在standby修改tns文件

3.4，修改參數文件
*.db_unique_name='pdunq_dg'
*.diagnostic_dest='/oracle/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=powerdes)'
*.fal_client='pdunq'
*.fal_server='pdunq_dg'
*.standby_file_management='AUTO'
*.db_file_name_convert='/home/oradata/powerdes','/home/oradata/powerdes'
*.log_file_name_convert='/home/oradata/powerdes','/home/oradata/powerdes'
*.log_archive_config='DG_CONFIG=(pdunq,pdunq_dg)'
*.log_archive_dest_2='SERVICE=pdunq_dg lgwr sync affirm VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pdunq_dg'
*.log_archive_dest_state_2='ENABLE'

PS:將*.log_archive_dest_2=后面的DB_UNIQUE_NAME改成primary的DB_UNIQUE_NAME值改為pdunq，這樣在做switchover的時候，新的primary能通過這個將redo日志傳到新的standby上面去。
log_archive_dest_N 目的是告訴數據庫，把歸檔放到那里去可選項，首先是本地，然后考慮遠程的從庫，所以，假設A是主庫，B是從庫，切換之后B是主庫，A是從庫，所以，log_archive_dest_N需要設置為對方

3.5，重啟監聽 standby
[oracle@powerlong5 dbs]$ lsnrctl stop

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 10-FEB-2015 15:41:36

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

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.121.218)(PORT=1521)))
The command completed successfully
[oracle@powerlong5 dbs]$ lsnrctl start

LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 10-FEB-2015 15:41:41

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

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

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

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.121.218)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date 10-FEB-2015 15:41:41
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/dbhome_1/network/admin/listener.ora
Listener Log File /oracle/app/oracle/diag/tnslsnr/powerlong5/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.121.218)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC0)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "powerdes" has 1 instance(s).
Instance "powerdes", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
[oracle@powerlong5 dbs]$

3.6，恢復數據庫
在standby庫上操作
[oracle@powerlong5 admin]$ rman target sys/syxxlxxxx58@PD1 auxiliary /

Argument Value Description
-----------------------------------------------------------------------------
target quoted-string connect-string for target database
catalog quoted-string connect-string for recovery catalog
nocatalog none if specified, then no recovery catalog
cmdfile quoted-string name of input command file
log quoted-string name of output message log file
trace quoted-string name of output debugging message log file
append none if specified, log is opened in append mode
debug optional-args activate debugging
msgno none show RMAN-nnnn prefix for all messages
send quoted-string send a command to the media manager
pipe string building block for pipe names
timeout integer number of seconds to wait for pipe input
checksyntax none check the command file for syntax errors
-----------------------------------------------------------------------------
Both single and double quotes (' or ") are accepted for a quoted-string.
Quotes are not required unless the string contains embedded white-space.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00552: syntax error in command line arguments
RMAN-01009: syntax error: found "end-of-file": expecting one of: "double-quoted-string, identifier, single-quoted-string, "
RMAN-01007: at line 0 column 0 file: command line arguments
[oracle@powerlong5 admin]$
[oracle@powerlong5 admin]$
[oracle@powerlong5 admin]$

報錯，看下是否standby沒有啟動導致？
SQL> startup

ORA-00845: MEMORY_TARGET not supported on this system
SQL> SQL> startup nomount
ORA-00845: MEMORY_TARGET not supported on this system
SQL>
[root@powerlong5 ~]# mount -t tmpfs shmfs -o size=12g /dev/shm
[root@powerlong5 ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 57G 45G 8.9G 84% /
tmpfs 12G 0 12G 0% /dev/shm
/dev/sda1 190M 51M 129M 29% /boot
/dev/sr0 4.1G 4.1G 0 100% /media/CentOS_6.4_Final
shmfs 12G 0 12G 0% /dev/shm
[root@powerlong5 ~]#

SQL> startup
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9925
SQL> startup nomount
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9925
ORA-09925: Unable to create audit trail file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 9925
SQL>
去primary庫上查詢下audit路徑
SQL> show parameter audit_file_dest

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
audit_file_dest string /oracle/app/oracle/admin/powerdes/adump
SQL>

然后在standby上操作
SQL> startup nomount
ORA-01081: cannot start already-running ORACLE - shut it down first
SQL> shutdown
ORA-01507: database not mounted

ORACLE instance shut down.
SQL> startup nomount
ORACLE instance started.

Total System Global Area 1.1358E+10 bytes
Fixed Size 2216744 bytes
Variable Size 8589937880 bytes
Database Buffers 2751463424 bytes
Redo Buffers 13946880 bytes
SQL>

去primary修改sys密碼：
SQL> alter user sys identified by "syxxlxxxx58";

User altered.

SQL>

在standby庫執行rman target sys/syspl1758@PD1 auxiliary /，如下所示：

[oracle@powerlong5 ~]$ rman target sys/syspl1758@PD1 auxiliary /

Recovery Manager: Release 11.2.0.1.0 - Production on Sat Feb 7 19:08:16 2015

connected to target database: POWERDES (DBID=3391761643)

connected to auxiliary database: POWERDES (not mounted)

RMAN> run {

allocate auxiliary channel c1 device type disk;

allocate auxiliary channel c2 device type disk;

duplicate target database for standby nofilenamecheck dorecover;

release channel c1;

release channel c2;

}

2> 3> 4> 5> 6> 7>

using target database control file instead of recovery catalog

allocated channel: c1

channel c1: SID=767 device type=DISK

allocated channel: c2

channel c2: SID=1150 device type=DISK

Starting Duplicate Db at 07-FEB-15

contents of Memory Script:

{

set until scn 10903678943;

restore clone standby controlfile;

}

executing Memory Script

executing command: SET until clause

Starting restore at 07-FEB-15

channel c1: starting datafile backup set restore

channel c1: restoring control file

channel c1: reading from backup piece /oracle/app/oracle/flash_recovery_area/PDUNQ/backupset/2015_02_07/o1_mf_ncsnf_TAG20150207T182252_bfct20tb_.bkp

channel c1: piece handle=/oracle/app/oracle/flash_recovery_area/PDUNQ/backupset/2015_02_07/o1_mf_ncsnf_TAG20150207T182252_bfct20tb_.bkp tag=TAG20150207T182252

channel c1: restored backup piece 1

channel c1: restore complete, elapsed time: 00:00:01

output file name=/oracle/data_ora/powerdes/control01.ctl

output file name=/oracle/app/oracle/flash_recovery_area/powerdes/control02.ctl

Finished restore at 07-FEB-15

contents of Memory Script:

{

sql clone \'alter database mount standby database\';

}

executing Memory Script

sql statement: alter database mount standby database

contents of Memory Script:

{

set until scn 10903678943;

set newname for datafile 1 to

\"/home/oradata/pwerdes/system01.dbf\";

set newname for datafile 2 to

\"/home/oradata/pwerdes/sysaux01.dbf\";

set newname for datafile 3 to

\"/home/oradata/pwerdes/undotbs01.dbf\";

set newname for datafile 4 to

\"/home/oradata/pwerdes/users01.dbf\";

set newname for datafile 6 to

\"/home/oradata/pwerdes/plas01.dbf\";

set newname for datafile 7 to

\"/home/oradata/pwerdes/pl01.dbf\";

set newname for datafile 8 to

\"/home/oradata/pwerdes/help01.dbf\";

set newname for datafile 9 to

\"/home/oradata/pwerdes/adobelc01.dbf\";

set newname for datafile 10 to

\"/home/oradata/pwerdes/sms01.dbf\";

restore

clone database

;

}

executing Memory Script

executing command: SET until clause

executing command: SET NEWNAME

Starting restore at 07-FEB-15

channel c1: starting datafile backup set restore

channel c1: specifying datafile(s) to restore from backup set

channel c1: restoring datafile 00001 to /home/oradata/pwerdes/system01.dbf

channel c1: restoring datafile 00002 to /home/oradata/pwerdes/sysaux01.dbf

channel c1: restoring datafile 00003 to /home/oradata/pwerdes/undotbs01.dbf

channel c1: restoring datafile 00004 to /home/oradata/pwerdes/users01.dbf

channel c1: restoring datafile 00006 to /home/oradata/pwerdes/plas01.dbf

channel c1: restoring datafile 00007 to /home/oradata/pwerdes/pl01.dbf

channel c1: restoring datafile 00008 to /home/oradata/pwerdes/help01.dbf

channel c1: restoring datafile 00009 to /home/oradata/pwerdes/adobelc01.dbf

channel c1: restoring datafile 00010 to /home/oradata/pwerdes/sms01.dbf

channel c1: reading from backup piece /oracle/app/oracle/flash_recovery_area/PDUNQ/backupset/2015_02_07/o1_mf_nnndf_TAG20150207T182252_bfcsvxoz_.bkp

channel c1: piece handle=/oracle/app/oracle/flash_recovery_area/PDUNQ/backupset/2015_02_07/o1_mf_nnndf_TAG20150207T182252_bfcsvxoz_.bkp tag=TAG20150207T182252

channel c1: restored backup piece 1

channel c1: restore complete, elapsed time: 00:04:05

Finished restore at 07-FEB-15

contents of Memory Script:

{

switch clone datafile all;

}

executing Memory Script

datafile 1 switched to datafile copy

input datafile copy RECID=3 STAMP=871067691 file name=/home/oradata/pwerdes/system01.dbf

datafile 2 switched to datafile copy

input datafile copy RECID=4 STAMP=871067691 file name=/home/oradata/pwerdes/sysaux01.dbf

datafile 3 switched to datafile copy

input datafile copy RECID=5 STAMP=871067691 file name=/home/oradata/pwerdes/undotbs01.dbf

datafile 4 switched to datafile copy

input datafile copy RECID=6 STAMP=871067691 file name=/home/oradata/pwerdes/users01.dbf

datafile 6 switched to datafile copy

input datafile copy RECID=7 STAMP=871067691 file name=/home/oradata/pwerdes/plas01.dbf

datafile 7 switched to datafile copy

input datafile copy RECID=8 STAMP=871067691 file name=/home/oradata/pwerdes/pl01.dbf

datafile 8 switched to datafile copy

input datafile copy RECID=9 STAMP=871067691 file name=/home/oradata/pwerdes/help01.dbf

datafile 9 switched to datafile copy

input datafile copy RECID=10 STAMP=871067692 file name=/home/oradata/pwerdes/adobelc01.dbf

datafile 10 switched to datafile copy

input datafile copy RECID=11 STAMP=871067692 file name=/home/oradata/pwerdes/sms01.dbf

contents of Memory Script:

{

set until scn 10903678943;

recover

standby

clone database

delete archivelog

;

}

executing Memory Script

executing command: SET until clause

Starting recover at 07-FEB-15

starting media recovery

archived log for thread 1 with sequence 302 is already on disk as file /oracle/app/oracle/flash_recovery_area/archivelog/1_302_870804216.dbf

archived log file name=/oracle/app/oracle/flash_recovery_area/archivelog/1_302_870804216.dbf thread=1 sequence=302

media recovery complete, elapsed time: 00:00:00

Finished recover at 07-FEB-15

Finished Duplicate Db at 07-FEB-15

released channel: c1

released channel: c2

RMAN> exit

3.7 standby上修改參數文件
先關閉oracle
shutdown immediate
然后開始修改參數文件
cd $ORACLE_HOME/dbs
vim initpowerdes.ora
# 主要是修改db_unique_name
*.db_unique_name='pdunq_dg'
*.diagnostic_dest='/oracle/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=powerdesXDB)'
*.fal_client='PD1'
*.fal_server='PD2'
*.global_names=FALSE
*.job_queue_processes=1000
*.log_archive_config='DG_CONFIG=(pdunq,pddgunq)'
重新創建參數文件
create spfile from pfile;

3.8 啟動數據庫
startup nomount;
alter database mount standby database;
alter database add standby logfile;
alter database add standby logfile;
alter database add standby logfile;
alter database recover managed standby database using current logfile disconnect from session;

4，檢查看到歸檔沒有過來
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination ?/dbs/arch
Oldest online log sequence 0
Next log sequence to archive 0
Current log sequence 0
SQL>
看到歸檔信息為0，說明primary上的redo日志沒有傳到standby上來。

4.1，查看alert日志
[oracle@powerlong5 trace]$ tail -f /oracle/app/oracle/diag/rdbms/pdunq_dg/powerdes/trace/alert_powerdes.log
MRP0 started with pid=41, OS id=21243
MRP0: Background Managed Standby Recovery process started (powerdes)
started logmerger process
Sat Feb 07 20:12:18 2015
Managed Standby Recovery not using Real Time Apply
Parallel Media Recovery started with 4 slaves
Waiting for all non-current ORLs to be archived...
All non-current ORLs have been archived.
Media Recovery Waiting for thread 1 sequence 303
Completed: alter database recover managed standby database disconnect from session

查看日志傳輸情況
select sequence#,first_time,next_time from v$archived_log;
SELECT sequence#,to_char(first_time,'yyyy-mm-dd hh24:mi:ss') first_time,to_char(next_time,'yyyy-mm-dd hh24:mi:ss') next_time from v$archived_log;
primary :

問題分析解決：
primary主庫上的alert日志有錯：
Error 12154 received logging on to the standby
Errors in file /oracle/app/oracle/diag/rdbms/pdunq/powerdes/trace/powerdes_arc2_22609.trc:
ORA-12154: TNS:could not resolve the connect identifier specified
PING[ARC2]: Heartbeat failed to connect to standby 'pdunq_dg'. Error is 12154.
錯誤很清晰了，主庫無法檢測到從庫存在
tns 12154 錯誤，主庫無法 tnsping pdunq_dg
tnsping standby庫報錯
[oracle@powerlong4 admin]$ tnsping pdunq_dg

TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 08-FEB-2015 21:42:26

Copyright (c) 1997, 2009, Oracle. All rights reserved.

Used parameter files:

TNS-03505: Failed to resolve name
[oracle@powerlong4 admin]$

參數文件里面
*.log_archive_dest_2='SERVICE=pdunq_dg lgwr sync affirm VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=pdunq_dg'
SERVICE=pdunq_dg 要和tnsnames.ora里面的保持一致。

4.2，去tnsnames.ora里面修改配置
去把tnsnames.ora里面的改成pdunq_dg即可。
重啟lsnrctl，然后查看從庫歸檔日志，有日志了，如下所示：
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 350
Next log sequence to archive 0
Current log sequence 351
SQL>

備庫切換到open狀態：
退出redo應用狀態
SQL> alter database recover managed standby database cancel;
Database altered.
PS：停止standby的redo應用 ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;注意，此時只是暫時redo 應用，并不是停止Standby 數據庫，standby 仍會保持接收只不過不會再應用接收到的歸檔，直到你再次啟動redo 應用為止。類似mysql里面的stop slave功能;

打開standby上的oracle庫
SQL> alter database open;
Database altered.
再應用redo日志
SQL> alter database recover managed standby database using current logfile disconnect ;
Database altered.
SQL>

去primary、standby庫上面執行檢查
SQL> select sequence#,applied from v$archived_log;

查看最新的scn：
SQL> select max(sequence#) from v$archived_log;

primary和standby都保持一致，OK，dataguard搭建完成。

轉載于:https://blog.51cto.com/liuhuanxin/1731327

總結

以上是生活随笔為你收集整理的ORACLE 11G 搭建dataguard详细步骤（所有操作总结）的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。

上一篇： C经典之14-双向链表存储1-10---
下一篇：算法导论5：基数排序和计数排序 2016