标签：备份 Incident sign uil stc 强制 rem thread for
Creating a Physical Standby database using DBCA duplicate (Doc ID 2283697.1)
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure: 出于本文档的目的，以以下虚拟环境为例来描述该过程
Primary Database: DB_NAME: Chicago Primary host name : exa503 Standby Database: DB_UNIQUE_NAME: boston standby hostname : exa504 Diskgroups used for both :- +DATAC1 and +RECOC1 --两者均使用的磁盘组
Maximum Availability Architecture 最高可用性架构
The Maximum Availability Architecture (MAA) defines Oracle’s most comprehensive architecture for reducing downtime for scheduled outages as well as preventing, detecting and recovering from unscheduled outages. Real Application Clusters (RAC) and Oracle Data Guard are integral components of the Database MAA reference architectures and solutions. 最大可用性体系结构（MAA）定义了Oracle最全面的体系结构，以减少计划内停机的停机时间，并防止，检测和从计划外停机中恢复。实际应用集群（RAC）和Oracle Data Guard是数据库MAA参考体系结构和解决方案的组成部分。
More detailed information, such as a discussion of the purpose of MAA and the benefits it provides, can be found on the Oracle Technology Network (OTN) at http://www.oracle.com/technetwork/database/features/availability/maa-096107.html
Purpose of this Document 本文目的
The purpose of this document is to provide a step-by-step guide for creating a standby database using DBCA in an Oracle Database 12.2 environment integrating the MAA Oracle Data Guard configuration best practices. This paper assumes that the following conditions exist:
本文档的目的是提供逐步指南，以在集成了MAA Oracle Data Guard配置最佳实践的Oracle Database 12.2环境中使用DBCA创建备用数据库。本文假定存在以下条件
Supported Versions 支持的版本
Multiple Channels Consideration: 多渠道注意事项
Performing a DBCA duplicate and using multiple channels on the primary node can significantly improve performance. If the Primary database is a RAC use multiple RMAN channels spread across the primary nodes. This utilizes more network interfaces for the data transfer. 执行DBCA duplicate并在主节点上使用多个通道可以显着提高性能。如果主数据库是RAC，请使用分布在主节点上的多个RMAN通道。这利用更多的网络接口进行数据传输
Parallelize backups across all primary database nodes leveraging disk and network bandwidth as available. MAA best practice recommend using 8 channels minimum or 2 channels per node. 利用可用的磁盘和网络带宽在所有主数据库节点上并行备份。MAA最佳实践建议每个节点至少使用8个通道或2个通道
Use automatic load balancing to distribute RMAN channels among the allocated nodes. Analyze the impact on existing production databases and reduce the RMAN parallelism if necessary. 使用自动负载平衡在分配的节点之间分配RMAN通道。分析对现有生产数据库的影响，并在必要时减少RMAN并行性
Make the following RMAN configuration changes at the primary database. Our example uses 4 preconfigured channels for RMAN to use during the standby creation step. These 4 channels will suffice for single node but can be increased if the server has additional capacity. 在主数据库上进行以下RMAN配置更改。我们的示例使用4个预配置的通道供RMAN在备用创建步骤中使用。这四个通道对于单个节点就足够了，但是如果服务器具有附加容量，则可以增加这四个通道。
[oracle@exa503]$ rman target / RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK; RMAN> CONFIGURE DEVICE TYPE DISK PARALLELISM 4;
All of the examples illustrated in this document use the following naming: 本文档中说明的所有示例均使用以下命名
|
Databases and Hosts Used in this example |
||
|
|
Primary |
Standby |
|
Hosts |
exa503 |
exa504 |
|
Database Unique Name |
chicago |
boston |
|
Instance names |
chicago |
boston |
PRIMARY DATABASE
[oracle@exa503]$ sqlplus / as sysdba SQL> alter database force logging;
Create standby redo logs on the primary database that are the same size of the online redo logs. This will ensure that standby redo log files are automatically created at the standby during the DBCA duplication process and that standby redo log files are available on the current Primary after a role transition occurs in the future and the Primary becomes a standby. 在主数据库上创建与在线重做日志大小相同的备用重做日志。这将确保在DBCA复制过程中在备用数据库上自动创建备用数据库重做日志文件，并且在将来发生角色转换且主数据库成为备用数据库之后，当前主数据库上的备用数据库重做日志文件可用。
Oracle recommends having the same number of standby redo log files as there are online redo log files plus 1 extra for each thread. Our primary database has 3 online redo log files for single thread. We therefore need 4 Standby Redo Log per thread for total of 4 standby Redo logs files. As per MAA Best Practice we recommend to create only one member for standby redo log. For example: Oracle建议使用与在线重做日志文件相同数量的备用重做日志文件，并为每个线程额外增加1个备用重做日志文件。我们的主数据库有3个单线程在线重做日志文件。因此，每个线程我们需要4个备用重做日志，以便总共有4个备用重做日志文件。根据MAA最佳实践，我们建议仅创建一个成员作为备用重做日志。例如：
[oracle@exa503]$ sqlplus / as sysdba SQL> select thread#,group#,bytes/1024/1024/1024 SIZE_IN_GB, status from v$log; THREAD# GROUP# SIZE_IN_GB STATUS ---------- ---------- -------------- ---------------- 1 1 4 CURRENT 1 2 4 UNUSED 1 3 4 UNUSED
[oracle@exa503]$ sqlplus / as sysdba SQL> alter database add standby logfile thread 1 group 4 (‘+DATAC1’) size 4G, group 5 (‘+DATAC1’) size 4G, group 6 (‘+DATAC1’) size 4G; group 7 (‘+DATAC1’) size 4G;
[oracle@exa503]$ sqlplus / as sysdba SQL> alter system set log_archive_dest_1=‘location=USE_DB_RECOVERY_FILE_DEST valid_for=(ALL_LOGFILES,ALL_ROLES) db_unique_name=chicago‘
|
In tnsnames.ora file on the primary node |
In tnsnames.ora file on the standby node |
|
chicago = boston = (CONNECT_DATA = chicago_local_listener = |
chicago = boston = boston_local_listener = |
[oracle@exa504 ~]$ dbca -silent -createDuplicateDB -gdbName chicago -sid boston -sysPassword welcome1 -primaryDBConnectionString exa503:1521/chicago -createAsStandby -dbUniqueName boston –initParams db_create_file_dest=+DATAC1,db_recovery_file_dest=+RECOC1,local_listener=”boston_local_listener”
Modify the script below to your environment and save as PostCR.sql 将以下脚本修改为您的环境，然后另存为PostCR.sql
注意：故障转移角色转换后，需要闪回数据库才能恢复发生故障的主数据库。（可选）在主数据库和备用数据库上启用闪回。备用数据库可以在执行PostCR脚本时开始使用闪回。
[oracle@exa504 ~]$ cat PostCR.sql connect sys/welcome1 as sysdba alter system set LOG_ARCHIVE_DEST_1=‘LOCATION=USE_DB_RECOVERY_FILE_DEST VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=boston‘ scope=spfile; alter system set db_file_name_convert=‘+DATAC1/chicago‘,‘+DATAC1/boston‘ scope=spfile; alter system set log_file_name_convert=‘+RECOC1/chicago‘,‘+RECOC1/boston‘ scope=spfile; alter system set standby_file_management=auto scope=spfile; alter system set dg_broker_config_file1=‘+DATAC1/boston/dr1.dat‘ scope=spfile; alter system set dg_broker_config_file2=‘+RECOC1/boston/dr2.dat‘ scope=spfile; alter system set db_flashback_retention_target=120 scope=spfile; alter database flashback on; alter system set dg_broker_start=true scope=spfile; alter system set remote_listener=‘prmy-scan:1521‘ scope=spfile; shutdown immediate startup alter system register; connect sys/welcome1@chicago as sysdba alter system set standby_file_management=auto scope=both; alter system set dg_broker_config_file1=‘+DATAC1/chicago/dr1.dat‘ scope=both;= alter system set dg_broker_config_file2=‘+RECOC1/chicago/dr2.dat‘ scope=both; alter system set dg_broker_start=TRUE; host sleep 30 host dgmgrl sys/welcome1@chicago "CREATE CONFIGURATION dgconfig AS PRIMARY DATABASE IS CHICAGO CONNECT IDENTIFIER IS CHICAGO"; host sleep 30 host dgmgrl sys/welcome1@chicago "ADD DATABASE BOSTON AS CONNECT IDENTIFIER IS BOSTON" ; host dgmgrl sys/welcome1@chicago "ENABLE CONFIGURATION" exit
[oracle@exa504 ~]$ export ORACLE_HOME=/u01/app/12.2.0.1/dbhome_1 [oracle@exa504 ~]$ export ORACLE_SID=boston [oracle@exa504 ~]$ export PATH=$ORACLE_HOME/bin:$PATH [oracle@exa504]$ sqlplus / as sysdba SQL> @PostCR.sql
[oracle@exa504 ~]$dgmgrl sys/<password> DGMGRL> show configuration Configuration - dgconfig Protection Mode: MaxPerformance Members: chicago - Primary database boston - Physical standby database Fast-Start Failover: DISABLED Configuration Status: SUCCESS (status updated 58 seconds ago)
[oracle@exa504 ~]$ export ORACLE_SID=+ASM1 [oracle@exa504]$ export ORACLE_HOME=/u01/app/12.2.0.1/grid [oracle@exa504 ~]$ export PATH=$ORACLE_HOME/bin:$PATH [oracle@exa503]$asmcmd –p ASMCMD [+] > mkdir DATAC1/BOSTON/PASSWORD ASMCMD [+] > pwcopy /u01/app/oracle/product/12.2.0.1/dbhome_1/dbs/orapwboston +DATAC1/BOSTON/PASSWORD/pwboston [oracle@exa504]$ rm /u01/app/oracle/product/12.2.0.1/dbhome_1/dbs/orapwboston [oracle@exa504 ~]$ export ORACLE_HOME=/u01/app/12.2.0.1/dbhome_1 [oracle@exa504 ~]$ export ORACLE_SID=boston [oracle@exa504 ~]$ export PATH=$ORACLE_HOME/bin:$PATH oracle@exa504]$ sqlplus / as sysdba SQL> create pfile=‘/tmp/b.ora‘ from spfile; SQL> create spfile=‘+DATAC1/BOSTON/spfileboston.ora‘ from pfile=‘/tmp/b.ora‘; [oracle@exa504]$ rm /u01/app/oracle/product/12.2.0.1/dbhome_1/dbs/spfileboston.ora
[oracle@exa504]$ echo “spfile=‘+DATAC1/BOSTON/spfileboston.ora‘” > /u01/app/oracle/product/12.2.0.1/dbhome_1/dbs/initboston.ora SQL> shutdown immediate SQL>exit
[oracle@exa504]$ srvctl add database -db boston -oraclehome /u01/app/oracle/product/12.2.0.1/dbhome_1 -dbtype Single -instance boston -node exa504-dbname chicago -diskgroup RECOC1,DATAC1 -role physical_standby -spfile ‘+DATAC1/BOSTON/spfileboston.ora‘ -pwfile ‘+DATAC1/BOSTON/PASSWORD/pwboston‘ [oracle@exa504]$ srvctl start database -db boston
This concludes building a single instance standby database from single instance primary database using DBCA. 至此，使用DBCA从单实例主数据库构建了一个单实例备用数据库
12.2新特性 使用DBCA duplicate创建物理备用数据库 (Doc ID 2283697.1)
标签：备份 Incident sign uil stc 强制 rem thread for
原文地址：https://www.cnblogs.com/zylong-sys/p/12042980.html
