Shulou(Shulou.com)05/31 Report--

This article introduces the relevant knowledge of "how to deploy Oracle19c dataguard". In the operation of actual cases, many people will encounter such a dilemma, so let the editor lead you to learn how to deal with these situations. I hope you can read it carefully and be able to achieve something!

New features

Oracle19c

By automatically copying the restore point from the primary node to the standby node, the process of flashing the physical standby node back to the point in time captured on the primary node is simplified.

When performing a flashback or point-in-time recovery on the primary database, the standby database in mount mode can automatically follow the same recovery procedure performed on the primary database

You can enable both Oracle database memory column storage and data protection multi-instance redo applications on the active data protection standby database.

The DML operation can be performed on the active data protection standby instance. When you run an invalid PL/SQL object on the ADG standby database, the object is automatically recompiled.

New features of Fast-Start-Failover (FSFO). The main library is dead. The standby library starts quickly.

Oracle18c

During role changes, the database buffer cache state is now maintained on the Oracle active data protection standby server

You can now dynamically create global temporary tables on the Oracle Active Data Guard standby database.

A new initialization parameter ADG_ACCOUNT_INFO_TRACKING extends control of user account security to prevent login attacks to protect standby databases across production databases and all Oracle active data. See Oracle database reference

A new view V$DATAGUARD_PROCESS (instead of V$MANAGED_STANDBY) provides queryable information to verify that redo is transferred from the primary database and applied to the standby database.

Metadata for private temporary tables (also known as local temporary tables) can be stored in memory. This allows dedicated temporary tables to be enabled on a read-only database, allowing reporting applications to run on Oracle active data protection standby databases.

Database unlogging has been extended to two new modes: standby Nologging for load performance and Standby Nologging for data availability. These patterns provide better support for use in Oracle active data protection environments without significantly increasing the amount of redo generated.

You can now refresh the standby database over the network using a RMAN command, RECOVER standby database.

Enhanced Data Guard agent support for upgrades performed using the DBMS_ROLLING PL/SQL package.

Multi-instance redo applications now support block change tracking

Deployment enables archiving select name,log_mode,force_logging from gv$database;alter database force logging

Starting with Oracle Database 18c, the following two new nologging clauses are introduced, which can perform non-logging operations while making the Active Data Guard standby database receive all the data, thus preventing performance degradation caused by generating a large number of redo logs in FORCE mode.

ALTER DATABASE SET STANDBY NOLOGGING FOR DATA AVAILABILITY;-mode allows the bulk load operation to send loaded data to each standby database through its own connection to the standby database. The submission is delayed until all Active Data Guard standby databases apply the data through recover.

ALTER DATABASE SET STANDBY NOLOGGING FOR LOAD PERFORMANCE

-the pattern is similar to the previous pattern, except that if the network cannot keep up with the speed at which the data is loaded into the primary database, the loading process can stop sending data to the standby database. In this mode, the standby database may lack data, but each Active Data Guard standby database automatically extracts data from the primary database during the recover process.

Primary parameter show parameter db_unique_nameALTER SYSTEM SET LOG_ARCHIVE_CONFIG='DG_CONFIG= (mydb19c,mydbdg) 'SID='*';ALTER SYSTEM SET LOG_ARCHIVE_DEST_1='LOCATION=/arch VALID_FOR= (ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=mydb19c' SID='*';ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=mydbdg LGWR ASYNC REOPEN NET_TIMEOUT=300 VALID_FOR= (ONLINE_LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=mydbdg' SID='*';alter system set LOG_ARCHIVE_DEST_STATE_1=enable Alter system set LOG_ARCHIVE_DEST_STATE_2=enable;ALTER SYSTEM SET STANDBY_FILE_MANAGEMENT = AUTO SID='*';ALTER SYSTEM SET FAL_SERVER='MYDBDG' SID='*';alter system set DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/MYDBDG','/u01/app/oracle/oradata/MYDB19C','/u01/app/oracle/oradata/MYDBDG','/u01/app/oracle/oradata/mypdb' scope=spfile Alter system set LOG_FILE_NAME_CONVERT='/u01/app/oracle/oradata/MYDBDG','/u01/app/oracle/oradata/MYDB19C' scope=spfile; ALTER SYSTEM SET LOG_ARCHIVE_FORMAT='%t_%s_%r.arc' SCOPE=SPFILE;ALTER SYSTEM SET LOG_ARCHIVE_MAX_PROCESSES=30; adds standby logselect group#,thread#,bytes/1024/1024,members from vault logtioncol member for a50select group#,member from v$logfilealter database add standby logfile group 4 ('/ u01Accord oradata) size 200m Alter database add standby logfile group 5 ('/ u01 size database add standby logfile group) size 200m alter database add standby logfile group 6 ('/ u01) size size-view ordbredo7 ('/ u01 tag) Configure listener/tnsnames--primary and standby--vi $ORACLE_HOME/network/admin/tnsnames.oraMYDB19C = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.80.216) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = mydb19c) (UR = A)) MYDBDG = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.80.217) (PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = mydbdg) (UR = A))-- standby vi $ORACLE_HOME/network/admin/listener.oraSID_LIST_LISTENER = (SID_LIST = (SID_DESC = (GLOBAL_DBNAME = mydbdg) (ORACLE_HOME = / u01/app/oracle/product/19.0.0/dbhome_1) (SID_NAME = mydbdg) create authentication user create user c##dgmima identified by dgmima2019 Grant sysoper to caching dgmima _ alter system set redo_transport_user=c##dgmima sid='*'; copy the related file create pfile='/home/oracle/pfile2020.ora' from spfile Scp / home/oracle/pfile2020.ora 192.168.80.217:/home/oraclescp $ORACLE_HOME/dbs/orapwmydb19c 192.168.80.217:/u01/app/oracle/product/19.0.0/dbhome_1/dbs/orapwmydbdgstandby pfile, note the database unique name * .audit _ file_dest='/u01/app/oracle/admin/mydbdg/adump'*.audit_trail='none'*.compatible='19.0.0'*.control_files='/u01/app/oracle/oradata/MYDBDG/control01.ctl' '/ u01ApplictionoracleUniverse oradataUniverse MYDBDGUniverse control02.ctlharmless. Dbstores blocksizecoat 8192. DbappThree fileholders nameplate convertablespact U01applicationoraclelemoradataplicMYDB19C labeled oradataUniplicationu01plains oracleoradataMypdb' '/ u01 apprenticeship oraclegrey oradataapMYDBDGrouption.dbdatabase filesystems 2000.dbaccountnamewords MYDB19Cand.dbdatabases uniquenamewords MYDBDGmail packages. Stickies destinations destinations archive_dest_1='LOCATION=/arch VALID_FOR= U01 apprenticeships apprenticeships. Chersmakers' (SERVICE=mydbdgXDB)'(SERVICE=mydbdgXDB)'* .enable _ pluggable_database=true*.fal_server='MYDB19C'*.local_listener=''*.log_archive_config='DG_CONFIG= (mydb19c,mydbdg)'* .log _ archive_dest_1='LOCATION=/arch VALID_FOR= (ALL_LOGFILES) ALL_ROLES) DB_UNIQUE_NAME=mydbdg'*.log_archive_dest_2='SERVICE=mydb19c LGWR ASYNC REOPEN NET_TIMEOUT=300 VALID_FOR= (ONLINE_LOGFILE,PRIMARY_ROLE) DB_UNIQUE_NAME=mydb19c'*.log_archive_dest_state_1='ENABLE'*.log_archive_dest_state_2='ENABLE'*.log_archive_format='%t_%s_%r.arc'*.log_archive_max_processes=30*.log_file_name_convert='/u01/app/oracle/oradata/MYDB19C' '/ u01According to an oracleback or oradata, or MYDBDGmail, or MYDBDGATA, or MYDBDGGATA, or MYDBDGGATA, or MYDBDGATA, or MYDBDGGATA, or MYDBDGARATA, or MYDBDGGATA, or MYDBDGATA, or MYDBDGGATA, or MYDBDGATA, or MYDBDGARATA, or MYDBDGARATA, or MYDBDGARADATA. NLSABUDGATA. Nlscharacters territorycharacters, AMERICANG.openings, cursorss.pgaits, targets, passwordfileholders, ex Startup nomount; starts replicating database rman target sys/oracle@mydb19c auxiliary sys/oracle@mydbdgrun {allocate channel prmy1 type disk;allocate channel prmy2 type disk;allocate channel prmy3 type disk;allocate channel prmy4 type disk;allocate auxiliary channel stby1 type disk;allocate auxiliary channel stby2 type disk;allocate auxiliary channel stby3 type disk;allocate auxiliary channel stby4 type disk; duplicate target database for standby from active database nofilenamecheck;} start recovery process-- backup starts recovery process mrp0alter database recover managed standby database using current logfile disconnect from session -- the slave queries whether there is a mrp0 process, select name,pid,role,action,group#,thread#,sequence#,delay_mins from vaindataguardprocessor:: switch the main database archive, and observe whether the synchronization of the slave database archive log is normal. How to disable media recovery by alter system archive log current;--: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;-- starts the database alter database open;alter pluggable database all open; to enable DML redirection-Note: if the slave database is not submitted, the master database and other slave databases cannot be viewed, and the slave database can be checked. After submission, you can view the ALTER SESSION ENABLE ADG_REDIRECT_DML;-- system-level alter system ENABLE ADG_REDIRECT_DML;DG environment clone database

Clone database must be in read-only mode

Remote clone reference: create database link connect to system identified by xxxxxxxx using''; alter systm set STANDBY_PDB_SOURCE_FILE_DBLINK='db_link';alter pluggable database open read only;create pluggable database from @; Mount database-mount. Parameters take effect only if xml method is used-- uninstall alter pluggable database unplug into'/ home/oracle//.xml';backup as copy pluggable database format'/ backup/' from other libraries -- prepare the library, set the following parameters, and the setting path of the backup end is the same as the original file on the master end. Alter system set standby_pdb_source_file_directory='/backup/';-- main library create pluggable database as clone using'/ / .xml 'copy;--or create pluggable database as clone using' / home/oracle//.xml' copy source_file_directory='+sparse//DATAFILE'; "how to deploy Oracle19c dataguard" ends here. Thank you for reading. If you want to know more about the industry, you can follow the website, the editor will output more high-quality practical articles for you!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.