当前位置：首页 > news >正文

oracle 19c搭建dataguard(ADG)全过程

news 2025/11/2 7:12:23

oracle 19c搭建ADG全过程

在上一期文件中提到了Oracle 19c静默安装全过程

链接: Oracle 19c静默安装全过程

oracle 19c dataguard 搭建过程主备开启归档
select log_mode from v$database;LOG_MODE
------------
NOARCHIVELOGshutdown immediate;
startup mount;
alter database archivelog;
alter database open;alter database force logging;
-- Make sure at least one logfile is present.
alter system switch logfile;主库创建
-- If Oracle Managed Files (OMF) is used.
alter database add standby logfile thread 1 group 10 size 50m;
alter database add standby logfile thread 1 group 11 size 50m;
alter database add standby logfile thread 1 group 12 size 50m;
alter database add standby logfile thread 1 group 13 size 50m;-- If Oracle Managed Files (OMF) is not used.
alter database add standby logfile thread 1 group 4 ('/oradb/oradata/WOO/standby_redo01.log') size 200m;
alter database add standby logfile thread 1 group 5 ('/oradb/oradata/WOO/standby_redo02.log') size 200m;
alter database add standby logfile thread 1 group 6 ('/oradb/oradata/WOO/standby_redo03.log') size 200m;
alter database add standby logfile thread 1 group 7 ('/oradb/oradata/WOO/standby_redo04.log') size 200m;主库参数修改
--alter system set db_unique_name=woo scope=spfile sid='*';
alter system set DB_FILE_NAME_CONVERT='/oradb/oradata/WOO/','/oradb/oradata/WOO/' scope=spfile;
alter system set LOG_FILE_NAME_CONVERT='/oradb/oradata/WOO/','/oradb/oradata/WOO/' scope=spfile;alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG=(woo,woostd)';
alter system set LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=woo';
alter system set LOG_ARCHIVE_DEST_2='SERVICE=woostd LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=woostd';
alter system set FAL_SERVER=woostd;
alter system set FAL_CLIENT=woopri;
alter system set standby_file_management=auto;
alter system set db_recovery_file_dest='/oradb/oradata/archivelog';
alter system set db_recovery_file_dest_size='2G';备库参数修改
alter system set db_unique_name=woostd scope=spfile sid='*';
alter system set DB_FILE_NAME_CONVERT='/oradb/oradata/WOO/','/oradb/oradata/WOO/' scope=spfile;
alter system set LOG_FILE_NAME_CONVERT='/oradb/oradata/WOO/','/oradb/oradata/WOO/' scope=spfile;alter system set LOG_ARCHIVE_CONFIG='DG_CONFIG=(woo,woostd)';
alter system set LOG_ARCHIVE_DEST_1='LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=woostd';
alter system set LOG_ARCHIVE_DEST_2='SERVICE=woo LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=woo';
alter system set FAL_SERVER=woopri;
alter system set FAL_CLIENT=woostd;
alter system set standby_file_management=auto;
alter system set db_recovery_file_dest='/oradb/oradata/archivelog';
alter system set db_recovery_file_dest_size='2G';重启生效
startup force;检查确认参数
set linesize 500 pages 0
col value for a80
col name for a50select name, value from v$parameter
where name in ('db_name','db_unique_name','log_archive_config',    
'log_archive_dest_1','log_archive_dest_2','log_archive_dest_3','log_archive_dest_state_1','log_archive_dest_state_2','log_archive_dest_state_3', 'remote_login_passwordfile','log_archive_format','log_archive_max_processes','fal_server','fal_client','db_file_name_convert','log_file_name_convert', 'standby_file_management') order by 1;#vi $ORACLE_HOME/network/admin/tnsnames.orazoopri =(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = mgrser1)(PORT = 1521)))(CONNECT_DATA =(SID = zoo)))zoostd =(DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = mgrser2)(PORT = 1521)))(CONNECT_DATA =(SID = zoo)))静态监听vi $ORACLE_HOME/network/admin/listener.oraSID_LIST_LISTENER =(SID_LIST =(SID_DESC =(GLOBAL_DBNAME = woo)(ORACLE_HOME = /oradb/oracle/product/19.3/dbhome_1)(SID_NAME = zoo)(ENVS="TNS_ADMIN=/oradb/oracle/product/19.3/dbhome_1/network/admin")))ADR_BASE_LISTENER = /oradb/oraclelsnrctl reload#
开始启动搭建DG备库启动到 nomount 状态
shutdown immediate;
startup nomount;rman target sys/q1w2e3r4@woopri auxiliary sys/q1w2e3r4@woostdduplicate target databasefor standbyfrom active databasedorecovernofilenamecheck;--关闭备库：
alter database recover managed standby database cancel;
--启动备库
alter database recover managed standby database using current logfile disconnect from session;--查看进程：
select process,status,sequence# from v$managed_standby;--查看归档进程配置状态
col error for a30
col DEST_NAME for a20
select DEST_NAME,STATUS,ERROR from v$archive_dest;--主库切换日志
alter system switch logfile;
archive log list;alter system set LOG_ARCHIVE_DEST_STATE_2=DEFER;
alter system set LOG_ARCHIVE_DEST_STATE_2=ENABLE;

遇到的问题：

sql statement: alter system archive log current
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 11/01/2025 05:03:14
RMAN-05501: aborting duplication of target database
RMAN-03015: error occurred in stored script Memory Script
RMAN-03009: failure of sql command on default channel at 11/01/2025 05:03:14
RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current
ORA-16014: log 3 sequence# 6 not archived, no available destinations
ORA-00312: online log 3 thread 1: '/oradb/oradata/WOO/redo03.log'解决方法
没有设置归档大小和归档路径，创建归档路径，设置归档参数即可。Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.RMAN-05535: warning: All redo log files were not defined properly.
Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.RMAN-05535: warning: All redo log files were not defined properly.
Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.RMAN-05535: warning: All redo log files were not defined properly.
Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.RMAN-05535: warning: All redo log files were not defined properly.
Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.RMAN-05535: warning: All redo log files were not defined properly.
Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.RMAN-05535: warning: All redo log files were not defined properly.
Oracle error from auxiliary database: ORA-01275: Operation RENAME is not allowed if standby file management is automatic.RMAN-05535: warning: All redo log files were not defined properly.
Finished Duplicate Db at 01-NOV-25解决方法：
把备库参数文件管理设置为手动，但是出现了如下新的提示RMAN-05535: warning: All redo log files were not defined properly.
RMAN-05535: warning: All redo log files were not defined properly.
RMAN-05535: warning: All redo log files were not defined properly.
RMAN-05535: warning: All redo log files were not defined properly.
RMAN-05535: warning: All redo log files were not defined properly.
RMAN-05535: warning: All redo log files were not defined properly.
RMAN-05535: warning: All redo log files were not defined properly.
Finished Duplicate Db at 01-NOV-25SQL> select DEST_NAME,STATUS,ERROR from v$archive_dest;DEST_NAME            STATUS    ERROR
-------------------- --------- ------------------------------
LOG_ARCHIVE_DEST_1   VALID
LOG_ARCHIVE_DEST_2   ERROR     ORA-16047: DGID mismatchbetween destination settingand target database#
问题：备库的唯一名字设置不对导致
原命令为：alter system set db_unique_name=woostd
准确是：alter system set db_unique_name=woostd scope=spfile sid='*'; 重启数据库生效。备库进程一致是 WAIT_FOR_LOG ，与预期的实时应用不一致。
SQL> --查看进程：
SQL> select process,status,sequence# from v$managed_standby;
ARCH      CONNECTED             0
DGRD      ALLOCATED             0
DGRD      ALLOCATED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
RFS       IDLE                  0
RFS       IDLE                 24
RFS       IDLE                  0
RFS       IDLE                  0
RFS       IDLE                  0
MRP0      WAIT_FOR_LOG         24解决方法：
排查到是由于redo日志和standby日志文件大小不一致导致的。
主备库重建standby 日志。备库取消同步：
alter database recover managed standby database cancel;主备库设置手动文件处理
alter system set standby_file_management='manual';主备库删除日志组
alter database drop standby logfile group 10 ;
alter database drop standby logfile group 11 ;
alter database drop standby logfile group 12 ;
alter database drop standby logfile group 13 ;主备库重建日志组alter database add standby logfile thread 1 group 4 ('/oradb/oradata/WOO/standby_redo01.log') size 200m;
alter database add standby logfile thread 1 group 5 ('/oradb/oradata/WOO/standby_redo02.log') size 200m;
alter database add standby logfile thread 1 group 6 ('/oradb/oradata/WOO/standby_redo03.log') size 200m;
alter database add standby logfile thread 1 group 7 ('/oradb/oradata/WOO/standby_redo04.log') size 200m;主备库设置自动文件处理
alter system set standby_file_management=auto;重新启动备库同步进程，主库刷新日子，再次查看正常。
SQL> set pages 200
SQL> select process,status,sequence# from v$managed_standby;PROCESS   STATUS        SEQUENCE#
--------- ------------ ----------
ARCH      CONNECTED             0
DGRD      ALLOCATED             0
DGRD      ALLOCATED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
ARCH      CONNECTED             0
RFS       IDLE                  0
RFS       IDLE                  0
RFS       IDLE                  0
RFS       IDLE                  0
MRP0      APPLYING_LOG         25
RFS       IDLE                 2512 rows selected.SQL>

查看全文

http://www.dtcms.com/a/557004.html