DG-duplicate 操作注意事项

 

1、duplicate时用户必须使用sys用户

2、to standby的脚本

#!/bin/bash

LOG=duplicate_`date +%Y%m%d`.log

export TMP=/tmp

export TMPDIR=$TMP

export ORACLE_BASE=/u01/oracle/app

export ORACLE_HOME=$ORACLE_BASE/11.2.0

export ORACLE_TERM=xterm

export PATH=/usr/sbin:$PATH

export PATH=$ORACLE_HOME/bin:$PATH

export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib64:/usr/lib64:/usr/local/lib64:/usr/x11R6/lib64

export CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib

export ORACLE_SID=orcl

/u01/oracle/app/11.2.0/bin/rman target sys/password@orcldb auxiliary sys/password@orcldb_dg log=/home/oracle/$LOG append <<eof</eof<>

run{

duplicate target database for standby from active database dorecover;

}

exit;

EOF

在RAC端任意节点通过RMAN连接到目标实例和辅助实例，执行duplicate命令复制数据库

3、备库是nomount状态

4、必须将密码文件进行同步

（注意密码要以字母开头数字结尾）

[oracle@OADB1 ~]$ /u01/oracle/app/11.2.0/bin/rman target sys/passwd@orcldb

Recovery Manager: Release 11.2.0.4.0 - Production on Tue Mar 20 09:51:16 2018

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-00554: initialization of internal recovery manager package failed

RMAN-04005: error from target database:

ORA-01017: invalid username/password; logon denied

或者

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-00554: initialization of internal recovery manager package failed

RMAN-04006: error from auxiliary database: ORA-01017: invalid username/password; logon denied

遇到这种报错，需重置sys密码

Alter user sys identified by passwd;

再将密码文件拷贝到备库

或者直接在备库手动设置密码文件，如下

orapwd file=$ORACLE_HOME/dbs/orapwCPDR password=change_on_install

5、是否要删除备库的所有数据文件？

(如果DBF文件没损坏就不需要删除)

6、修改主库的tnsname.ora

主库：

vi tnsname.ora

orcldb_dg=

  (DESCRIPTION =

    (ADDRESS = (PROTOCOL = TCP)(HOST = IP地址)(PORT = 1521))

    (CONNECT_DATA =

      (SERVER = DEDICATED)

      (SERVICE_NAME = orcldb_dg)

    )

  )

7、参数文件的log_file_name_convert参数需要修改成对应的目录（备库）

可以参考主库的目录设置成一模一样

8、控制文件路径control_files需要修改成对应的目录（备库）

可以参考主库的目录设置成一模一样

9、设置log_file_name_convert为空或者和主库一样

设置为空即与主库路径一致

alter system set log_file_name_convert='' scope=spfile;

或者在参数文件中设置和主库一致的路径

log_file_name_convert='+orcl_DATA/orcldb','+orcl_data/orcldb_dg2'

10、备库的参数文件要使用spfile

11、备库监听不定时重启或自动关闭

如果备库监听总是不定时重启或者自动关闭，修改LISTEN.ora文件

如下

LISTENER =

  (DESCRIPTION_LIST =

    (DESCRIPTION =

      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))

      (ADDRESS = (PROTOCOL = TCP)(HOST = orcldb-dg)(PORT = 1521))

    )

  )

ADR_BASE_LISTENER = /u01/app/grid

ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON  

SID_LIST_LISTENER = 

  (SID_LIST =  

    (SID_DESC = 

      (SID_NAME = orcl1db) 

      (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1) 

      (GLOBAL_DBNAME=orcl1db_dg) 

    ) 

    (SID_DESC = 

      (SID_NAME = orcl2db) 

      (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1) 

      (GLOBAL_DBNAME=orcl2db_dg) 

    )

    (SID_DESC = 

      (SID_NAME = orcl3db) 

      (ORACLE_HOME = /u01/app/oracle/product/11.2.0/dbhome_1) 

      (GLOBAL_DBNAME=orcl3db_dg) 

    )

  )

如果备库安装的是单节点ASM，使用grid用户执行以下命令重启监听

srvctl stop listener

srvctl start listener

12、备库采用字符界面命令模式挂载ASM的裸设备

查看ASM磁盘的详细信息及状态

select group_number,disk_number,header_status,mode_status,state,total_mb,name,failgroup,path from  v$asm_disk;

select name,state from v$asm_diskgroup;

-- 添加 ASM磁盘组

Create diskgroup  orcl1_DATA  external  redundancy  disk '/dev/asm_vdd';

Create diskgroup  orcl2_DATA  external  redundancy  disk '/dev/asm_vdb';

Create diskgroup  orcl3_DATA  external  redundancy  disk '/dev/asm_vdi';

给磁盘组添加磁盘

alter diskgroup data add disk '/dev/asm_vde';

alter diskgroup data add disk '/dev/asm_vdf';

alter diskgroup data add disk '/dev/asm_vdg';

alter diskgroup data add disk '/dev/asm_vdh';

alter diskgroup data add disk '/dev/asm_vdj';

--加载磁盘组

ALTER DISKGROUP DATA MOUNT;

13、备库注意配置/etc/hosts

ip地址 orcldb-dg

14、duplicate后，同步日志无法成功，主库查询出现报错

SQL> select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2';

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS        ERROR

--------- -----------------------------------------------------------------

        1

LOG_ARCHIVE_DEST_2

ERROR   ORA-16191: ??????????????????

        2

LOG_ARCHIVE_DEST_2

ERROR   ORA-16191: ??????????????????

或者

        2

LOG_ARCHIVE_DEST_2

ERROR   ORA-16058: ??????????

        1

LOG_ARCHIVE_DEST_2

ERROR   ORA-16058: ??????????

这个时候需要去备库重启数据库实例

Shutdown immediate

startup

15、duplicate时出现报错

RMAN-00571: ===========================================================

RMAN-03002: failure of Duplicate Db command at 03/28/2018 19:36:20

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/28/2018 19:36:20

ORA-00245: ????????; ?????????????

尝试手动执行命令，不用脚本

16、安装备库单节点ASM后，需要手动启动CRS服务

crsctl start resource ora.diskmon

crsctl status resource -t

crs_stat -p ora.cssd

crsctl modify resource "ora.cssd" -attr "AUTO_START=1"   --设置自动启动

crs_stat -p ora.diskmon

crsctl modify resource "ora.diskmon" -attr "AUTO_START=1"   --设置自动启动

注意：这里采用图形界面安装GRID软件，要选择第二项安装

如果选择的是最后一项安装软件，可能会漏掉一些CRS服务，导致无法使用asmca命令打开图形界面

17、记得把备份停止了

18、duplicate后，同步日志无法成功，主库查询出现报错

SQL> select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2';

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

2

LOG_ARCHIVE_DEST_2

ERROR   ORA-01033: ORACLE initialization or shutdown in progress

1

LOG_ARCHIVE_DEST_2

ERROR   ORA-01033: ORACLE initialization or shutdown in progress

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

解决方法：

1、检查RAC节点的密码文件是否同步，可以直接拷贝覆盖一下

2、检查DG节点的密码文件是否同步， 可以直接拷贝RAC的密码文件到DG覆盖

3、在主节点alter system set log_archive_dest_state_2=enable;

4、再次查询状态变成VALID正常

SQL>  select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2';

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

2

LOG_ARCHIVE_DEST_2

VALID

1

LOG_ARCHIVE_DEST_2

VALID

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

注意：检验是否因密码问题导致DG日志不同步，也可以在alter.log里面查找验证（主库和备库都看）

19、如果遇到下面的报错，哈哈，可能你设置的路径并不是LOG_ARCHIVE_DEST_2

也可能是LOG_ARCHIVE_DEST_3，所以要看清楚了。  select * from V$ARCHIVE_DEST_STATUS

SQL> select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2';

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

2

LOG_ARCHIVE_DEST_2

BAD PARAM

1

LOG_ARCHIVE_DEST_2

BAD PARAM

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

20、在DG库上设置同步后，发现日志并没有同步

SQL> select thread#,process,client_process,sequence#,status from v$managed_standby;

   THREAD# PROCESS   CLIENT_P  SEQUENCE# STATUS

---------- --------- -------- ---------- ------------

0 ARCH      ARCH        0 CONNECTED

0 ARCH      ARCH        0 CONNECTED

0 ARCH      ARCH        0 CONNECTED

0 ARCH      ARCH        0 CONNECTED

2 MRP0      N/A     2880 APPLYING_LOG

这个时候，查看主库状态

SQL> select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2';

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

1

LOG_ARCHIVE_DEST_2

ERROR   ORA-03135: connection lost contact

2

LOG_ARCHIVE_DEST_2

ERROR   ORA-03135: connection lost contact

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

在主库重新enable也没用

alter system set log_archive_dest_state_2=ENABLE;

检查DG备库监听，发现监听没启动

su - oracle

lsnrctl start

然后再次检查，发现还是不同步

主库查状态

SQL> select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2';

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

1

LOG_ARCHIVE_DEST_2

ERROR   ORA-12543: TNS:destination host unreachable

2

LOG_ARCHIVE_DEST_2

ERROR   ORA-12543: TNS:destination host unreachable

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

这个时候，检查DG备库，发现，iptables -L  发现防火墙阻拦了

iptables -F清除

问题解决

21、 在DG库上设置同步后，发现日志并没有同步

SQL> select thread#,process,client_process,sequence#,status from v$managed_standby;

   THREAD# PROCESS   CLIENT_P  SEQUENCE# STATUS

---------- --------- -------- ---------- ------------

0 ARCH      ARCH        0 CONNECTED

0 ARCH      ARCH        0 CONNECTED

0 ARCH      ARCH        0 CONNECTED

0 ARCH      ARCH        0 CONNECTED

2 MRP0      N/A     2880 APPLYING_LOG

这个时候，查看主库状态

SQL> select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_2';

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

2

LOG_ARCHIVE_DEST_2

DISABLED  ORA-16057: server not in Data Guard configuration

1

LOG_ARCHIVE_DEST_2

DISABLED  ORA-16057: server not in Data Guard configuration

   INST_ID

----------

DEST_NAME

--------------------------------------------------------------------------------

STATUS   ERROR

--------- -----------------------------------------------------------------

看到这个报错，就要去检查log_archive_config了

主备库两个都要检查，因为他们要一致

主库查看

SQL> show parameter log_archive_config

NAME      TYPE VALUE

------------------------------------ ----------- ------------------------------

log_archive_config      string DG_CONFIG=orcldb,orcldbdg3)

备库查看

SQL> show parameter log_archive_config

NAME      TYPE VALUE

------------------------------------ ----------- ------------------------------

log_archive_config      string DG_CONFIG=(orcldbdg3,orcldbdg)

果然不一致，修改它

SQL> alter system set log_archive_config='DG_CONFIG=(orcldbdg3,orcldb)';

去主库重新enable一下

alter system set log_archive_dest_state_2=ENABLE;

回到备库，发现已经开通同步日志了

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/28371090/viewspace-2152437/，如需转载，请注明出处，否则将追究法律责任。