ITPub博客

首页 > 数据库 > Oracle > DG-duplicate操作注意事项(各种报错应对方法)

DG-duplicate操作注意事项(各种报错应对方法)

原创 Oracle 作者:germany006 时间:2018-03-30 15:40:51 1 删除 编辑



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时出现报错

(1)

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: ????????; ?????????????


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



(2)

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

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

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

RMAN-03002: failure of Duplicate Db command at 10/22/2020 14:22:24

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-03009: failure of sql command on clone_default channel at 10/22/2020 14:22:24

RMAN-11003: failure during parse/execution of SQL statement: alter database mount standby database

ORA-01103: database name 'ORCLDB' in control file is not 'ORCLDG'


检查备库的参数文件, db_name 必须设置为 limsdb ,重新使用该参数文件 spfile 启动即可



(3)

出现以下报错:

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

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

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

RMAN-03002: failure of Duplicate Db command at 10/23/2020 10:53:16

RMAN-05501: aborting duplication of target database

RMAN-05001: auxiliary file name +DATA/orcldb/datafile/undotbs3.352.1052653543 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/cpwms_data.344.1052653263 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/cpwms_data.348.1052653077 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/cpwms_data.350.1052652903 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/cpwms_data.342.1052652717 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/cpwms_data.358.1052652541 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/cpwms_data.357.1052652357 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/cpwms_data.260.1052652161 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/undotbs2.346.1052653483 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/users.343.1052653585 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/undotbs1.351.1052653519 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/sysaux.345.1052653439 conflicts with a file used by the target database

RMAN-05001: auxiliary file name +DATA/ orcldb/datafile/system.353.1052653569 conflicts with a file used by the target database


检查参数文件

*.db_file_name_convert='+DATA/ orcldb/datafile','/home/orcldg/','+DATA/ orcldb/tempfile','/home/orcldg/'

*.log_file_name_convert='+DATA/ orcldb/onlinelog','/home/orcldg/'


 

遇到以下报错,是因为在主库执行 rman target sys/**** auxiliary sys/****@orcldg时,没export ORACLE_SID

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

RMAN-03002: failure of Duplicate Db command at 10/23/2020 10:00:59

RMAN-05501: aborting duplication of target database

RMAN-06403: could not obtain a fully authorized session

ORA-01034: ORACLE not available

ORA-27101: shared memory realm does not exist

Linux-x86_64 Error: 2: No such file or directory





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清除


问题解决


主库报错ORA-12541

   INST_ID

----------

DEST_NAME

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

STATUS    ERROR

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

         1

LOG_ARCHIVE_DEST_3

ERROR     ORA-12541: TNS:no listener


         2

LOG_ARCHIVE_DEST_3

ERROR     ORA-12541: TNS:no listener


这个时候,检查DG备库,发现,备库监听没启动,lsnrctl start启动监听后问题解决


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;



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


22、发现以下报错,有可能设置的log_archive_dest不是这个,检查是否是其他的,可以在PLSQL检查

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

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

         1

LOG_ARCHIVE_DEST_2

BAD PARAM ORA-16053: DB_UNIQUE_NAME  is not in the Data Guard Configuration


         2

LOG_ARCHIVE_DEST_2

BAD PARAM


   INST_ID

----------

DEST_NAME

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

STATUS    ERROR

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


#########2022-11-08更新##############

23、配置log_archive_dest_*报错

select inst_id,dest_name,status,error from gv$archive_dest_status where dest_name='LOG_ARCHIVE_DEST_4';

  INST_ID    DEST_NAME                  STATUS        ERROR

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

1      LOG_ARCHIVE_DEST_4   DISABLED      ORA-12154: TNS:could not resolve the connect identifier specified


解决方法:

1、检查tnsnames.ora,主备库都要配置互相的tns连接,且测试网络连接

2、检查/etc/hosts,主备库都要互相添加hosts

主库IP地址   主库主机名

备库IP地址   备库主机名

3、主库备库都要修改

alter system set log_archive_config='DG_CONFIG=(utest,ksdb)';

                                                                                  (主库SID,备库SID)


24、网络登录测试报错

sqlplus sys/*****@utest as sysdba


SQL*Plus: Release 19.0.0.0.0 - Production on Wed Oct 26 13:21:13 2022

Version 19.3.0.0.0


Copyright (c) 1982, 2019, Oracle.  All rights reserved.


ERROR:

ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA


出现这个报错时,tnsping也是不正常的,SERVICE_NAME是空的。且出现Used EZCONNECT或者Used HOSTNAME,正常的情况应该是Used TNSNAMES

Used EZCONNECT adapter to resolve the alias

Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=tcp)(HOST=10.32.213.40)(PORT=1521)))

OK (10 msec)

Used HOSTNAME adapter to resolve the alias

Attempting to contact (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=tcp)(HOST=10.32.213.40)(PORT=1521)))

OK (0 msec)


解决方法:

vi /home/oracle/.bash_profile

export TNS_ADMIN=$ORACLE_HOME/network/admin


25、数据库启动报错:

ORA-01103: database name 'UTEST' in control file is not 'KSDB'


解决方法:

主备primary,standby库的instance name不一致引起的

把备库的db_name要和主库一致,但*.db_unique_name='standby'应为备库的SID




26、主库查询LOG_ARCHIVE_DEST报错ORA-12504

报错:

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


   INST_ID     DEST_NAME STATUS ERROR

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

       1              LOG_ARCHIVE_DEST_4               DISABLED              ORA-12504: TNS:listener was not given the SERVICE_NAME in  CONNECT_DATA



解决方法:

检查主备库tnsping两边都是通的,如果还是报错,就要检查两边数据库的版本是否一致,注意!!!!小版本也必须一致,我这边尝试过主库是19.0.0.0.0,备库是19.17.0.0.0(打了最新补丁),就会出现该报错,将主库打上一样的补丁后,问题解决



27、遇到报错:(开启主备同步alert.log)

2022-10-31T16:12:50.947025+08:00

ARC1 (PID:1531): Error 1017 received logging on to the standby

ARC1 (PID:1531): -------------------------------------------------------------------------

ARC1 (PID:1531): Check that the source and target databases are using a password file

ARC1 (PID:1531): and remote_login_passwordfile is set to SHARED or EXCLUSIVE,

ARC1 (PID:1531): and that the SYS password is same in the password files,

ARC1 (PID:1531): returning error ORA-16191

ARC1 (PID:1531): -------------------------------------------------------------------------

ARC1 (PID:1531): FAL: Error 16191 connecting to utest for fetching gap sequence

2022-10-31T16:12:50.978660+08:00



解决方法:

将主库的密码文件拷贝到备库,注意权限,oracle.oinstall





28、在配置duplicate连通过程中报错

主库:

 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
DISABLED  ORA-16009: invalid redo transport destination

     2
LOG_ARCHIVE_DEST_2
DISABLED  ORA-16009: invalid redo transport destination


解决方法:

检查备库的spfile是否修改生效

 cat rptdgpfile.ora
rptvmdg.__data_transfer_cache_size=0
rptvmdg.__db_cache_size=18723373056
rptvmdg.__inmemory_ext_roarea=0
rptvmdg.__inmemory_ext_rwarea=0
rptvmdg.__java_pool_size=0
rptvmdg.__large_pool_size=134217728
rptvmdg.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
rptvmdg.__pga_aggregate_target=21474836480
rptvmdg.__sga_target=21474836480
rptvmdg.__shared_io_pool_size=134217728
rptvmdg.__shared_pool_size=2415919104
rptvmdg.__streams_pool_size=0
rptvmdg.__unified_pga_pool_size=0
*.audit_file_dest='/u01/app/oracle/admin/rptvmdg/adump'
*.audit_trail='db'
*.compatible='19.0.0'
*.control_files='/u01/app/oracle/oradata/RPTVMDG/control01.ctl','/u01/app/oracle/oradata/RPTVMDG/control02.ctl'
*.db_block_size=8192
*.db_name='rptdb'
*.diagnostic_dest='/u01/app/oracle'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=rptvmdgXDB)'
*.local_listener='LISTENER_RPTVMDG'
*.nls_language='AMERICAN'
*.nls_territory='AMERICA'
*.open_cursors=300
*.pga_aggregate_target=20480m
*.processes=5000
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=20480m
*.undo_tablespace='UNDOTBS1'
*.DB_UNIQUE_NAME='rptvmdg'
*.log_archive_config='DG_CONFIG=(rptdb,rptvmdg)'
*.log_archive_dest_1='location=/oradata/rptvmdg/archivelog/ VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=rptvmdg'
*.log_archive_dest_2='SERVICE=rptvmdg lgwr ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=rptvmdg'
*.fal_server='rptdb'
*.fal_client='rptvmdg'
*.log_archive_format='%t_%s_%r.arc'
*.standby_file_management=auto
*.db_file_name_convert='+DATA/RPTDB/DATAFILE/','/oradata/rptvmdg/','+DATA/RPTDB/TEMPFILE/','/oradata/rptvmdg/'

*.log_file_name_convert='+DATA/ RPTDB/ONLINELOG/','/oradata/rptvmdg/'

shut immediate

startup noumoutn pfile='';

create spfile from pfile='';

shut immediate

startup nomount;


29、 在配置duplicate连通过程中报错


主库:
export ORACLE_SID=主库sid
rman target sys/***@ 主库db_name auxiliary sys/***@备库 db_name

run{
duplicate target database for standby from active database dorecover;
}


出现以下报错:
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/29/2023 14:22:22
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: Oracle error from auxiliary database: ORA-17629: Cannot connect to the remote database server
ORA-17627: ORA-12154: TNS:could not resolve the connect identifier specified
ORA-17629: Cannot connect to the remote database server


解决方法:
 在备库上的tnsnames.ora添加主库RAC的scan地址和tns别名
主库db_name =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = IP地址)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = 主库db_name)
    )
  )


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

请登录后发表评论 登录
全部评论
ORACLE,MYSQL,POSTGRESQL,SQLSERVER,MONGODB,TIDB,DB2,REDIS,本博客只为记录自己学习总结,不代表完全准确。

注册时间:2013-03-06

  • 博文量
    776
  • 访问量
    1038300