OracleDG deployment: Windows– >Oracle

OracleDG deployment: Windows– >Oracle

Director of sprout

• The cloud community
• Data storage and databases
• Oracle
• The log
• LOG
• windows
• The database
• configuration
• ADD
• Cloud disk
• database
• disk
• type
• Group

Abstract: There is an Oracle11G stand-alone environment running under Windows, with 1.3T of tablespace allocation and 700-800G of actual data. For server stability and database performance, the customer needs to migrate the database to a Linux environment and cut it when appropriate.

There is an Oracle11G standalone environment running under Windows, with 1.3T of tablespace allocation and 700-800G of actual data. For server stability and database performance, the customer needs to migrate the database to a Linux environment and cut it when appropriate. (1) The current server environment

Database environment

(2)

Open the file

After communicating with the developer, we learned that the reason for not opening archiving is that the database is updated frequently. During the activity, a large number of archiving will be generated, sometimes reaching 1T, which requires high read and write performance of the disk. Therefore, archiving is closed.

After the database access permission is obtained, the switchover frequency of the current online logs is queried. It is found that the log volume is controllable. During the Double 12 event, the online log volume is switched 4205 times, and the estimated archiving volume is about 4205*50M/1024M ~ 210G. And Double 12 is the biggest event of the year.



According to the obtained situation, feedback to the developer, suggest the customer to buy and mount enough disks (more than 1T) to store archive logs; You are advised to add a log file group (500 MB), set an archive deletion policy, and a RMAN backup policy.

After the disk is mounted, the developer applies for a maintenance window and starts archiving. According to recent observation, the daily production of archiving is about 100G.

(3)

Planning standby database resources

935G/ORabackup A local backup set is used to store 935G/ORalog online and archived logs 467G /oradata/ Oradata04 data file 467G/Oradata03 data file 467G Oradata /oradata02 Data file 467G /oradata/oradata01 data fileCopy the code

(5) The configuration of the DG environment of the master database is operated by the developer

Alter database force logging; alter system set log_archive_config = 'dg_config=(ccc,ccc_dg)'; alter system set log_archive_dest_2 = 'SERVICE=ccc_dg COMPRESSION=ENABLE LGWR ASYNC AFFIRM VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=ccc_dg'; alter system set log_archive_dest_state_2 = ENABLE; Ora change CCC = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = XXXX)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = ccc) ) ) CCC_DG = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST = zzzz)(PORT = 1521)) CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = CCC) (UR = A)Copy the code

(6) Standby DG environment configuration

Alter system set log_ARCHIve_config = 'dg_config=(CCC, ccC_dg)'; alter system set log_archive_dest_1 = 'location=/oralog/archive'; alter system set db_file_name_convert = 'D:\ORADB\CCC','/oradata/oradata01','F:\ORADB\CCC','/oradata/oradata02','G:\ORADB\CCC','/oradata/oradata02','H:\ORADB\CC C','/oradata/oradata03','I:\ORADB\CCC','/oradata/oradata03','J:\ORADB\CCC','/oradata/oradata04' scope=spfile; alter system set log_file_name_convert = 'D:\ORADB\CCC','/oralog/log' scope=spfile; The # tnsnames.ora configuration is omitted from the main library # listen configurationCopy the code

After the configuration is complete, use TNsname to connect the active and standby databases. (7) Start database initialization

nohup sh ccc_dg_par.sh > /dev/null 2>&1 &Copy the code

ccc_dg_par.sh

#! /bin/bash set -o pipefail set -o errexit if [ -f ~/.bashrc ]; then . ~/.bashrc fi export ORACLE_SID=ccc $ORACLE_HOME/bin/rman target sys/xxxxxxx@xxx auxiliary sys/xxxxxxxxx@xxx_dg cmdfile 'ccc_dg.par' log 'ccc_dg.log' <<EOF exit EOF exitCopy the code

ccc_dg.par

run{ allocate channel prmy1 type disk; allocate channel prmy2 type disk; allocate auxiliary channel standby1 type disk; allocate auxiliary channel standby2 type disk; set newname for datafile 5 to '/oradata/oradata01/BACKUP01.DBF'; set newname for datafile 63 to '/oradata/oradata01/BACKUP07.DBF'; set newname for datafile 11 to '/oradata/oradata01/system01.DBF'; ..................... set newname for tempfile 5 to '/oradata/oradata03/TEMP03.DBF'; set newname for tempfile 6 to '/oradata/oradata04/TEMP02.DBF'; duplicate target database for standby from active database nofilenamecheck dorecover; release channel prmy1; release channel prmy2; }Copy the code

(8) Enable real-time synchronization

Alter database add standby logfile group 11 '/oralog/log/standby_11.log 'size 1024m; Alter database add standby logfile group 12 '/oralog/log/standby_12.log 'size 1024m; Alter database add standby logfile group 13 '/oralog/log/standby_13.log 'size 1024m; Alter database add standby logfile group 14 '/oralog/log/standby_14.log 'size 1024m; Alter database add standby logfile group 14 '/oralog/log/standby_14.log' size 1024m; Alter database add standby logfile group 15 '/oralog/log/standby_15.log 'size 1024m; Alter database add standby logfile group 16 '/oralog/log/standby_16.log 'size 1024m; Alter database add standby logfile group 17 '/oralog/log/standby_17.log 'size 1024m; alter database recover managed standby database disconnect from session; alter database recover managed standby database cancel; Alter database open; alter database recover managed standby database disconnect from session using current logfile;Copy the code

(IX) Verify and access EasyDB monitoring platform

For details, please click
Comments (0)

To:

• Oracle Executions=0 but Executions=0