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

This article focuses on "Oracle19c rman use simple test analysis", interested friends may wish to take a look. The method introduced in this paper is simple, fast and practical. Now let the editor to take you to learn "Oracle19c rman use simple test analysis" it!

19c new features

PDB support database

-- connection example connect target "sbu@prod AS SYSBACKUP"

Automatically delete flashback log

By default, 1440 minutes / day, 19c begins to surpass the new features of automatic cleaning db_flashback_retention_target18C.

Copy one pdb to another existing cdb

Copy database to Oracle cloud

Roll forward the physical repository to simplify use

RMAN backup can be migrated, switched between pdb and cdb

Enhanced write protection for block loss

Partial functional test

Fully prepared

Connect target / run {allocate channel ch2 type disk; allocate channel ch3 type disk; alter system archivelog current; alter system archivelog current; backup format'/ backup/mypdb_full_%T_%s_%p' database plus archivelog delete all input; backup format'/ backup/mypdb_controlfile_%T_%s_%p' current controlfile; alter system archivelog current; backup format'/ backup/mypdb_arch_%Y%M%D_%s_%p' archivelog all; release channel ch2 Release channel ch3;}

Data file reference for full backup

-- where the data file 2, 5, 5, 6 is the pdb template col file_name for a50select file_id,file_name,tablespace_name from cdb_data_files order by file_id.

Back up the pdb database

For more confidence in commands, refer to the full BACKUP PLUGGABLE DATABASE mypdb;--or [oracle@node216 ~] $rman target sys/oracle@mypdbRecovery Manager: Release 19.0.0.0.0-Production on Fri Feb 14 21:57:32 2020Version 19.3.0.0.0Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved.connected to target database: MYDB19C:MYPDB (DBID=2219134196) RMAN > backup database

Backup cdb,pdbseed

Backup root+pdbseed recommends backing up run {allocate channel ch2 type disk; allocate channel ch3 type disk; alter system archivelog current; alter system archivelog current; backup format'/ backup/root_full_%T_%s_%p' database root plus archivelog delete all input; backup format'/ backup/pdbseed_full_%T_%s_%p' database 'PDB$SEED'; backup format' / backup/root_controlfile_%T_%s_%p' current controlfile; alter system archivelog current together Backup format'/ backup/root_arch_%Y%M%D_%s_%p' archivelog all; release channel ch2; release channel ch3;} recovery test-restore root+pdbseed, or restore restore controlfile from'/ backup/root_controlfile_20200215_62_1'; alter database mount; run {restore database root; restore database 'pdb$seed'; recover database root; recover database' pdb$seed';} separately-skip pdb database, openalter session set container=mypdb Col name for a50select file#,name,status from venerable datafile alter database datafile 9 online;alter database open;--oralter session set container= 10 CDB$ROOT 11 12 offline;alter database open resetlogs;-- restore pdbcol pdb_name for a20select pdb_name,status from dba_pdbs;restore pluggable database mypdb;recover pluggable database mypdb;alter session set container=mypdb;alter database datafile 9 Tokyo 11 lemon 13 online;alter database open;--oralter session set container= "CDB$ROOT";

Pdb Migration, no-cdb pdb

-- backup BACKUP format'/ backup/testpdb_full_%T_%s_%p' PLUGGABLE DATABASE testpdb PLUS ARCHIVELOG;-- uninstall / export pdbsqlplus / as sysdbaalter pluggable database testpdb unplug into'/ home/oracle/testpdb.xml';-- delete pdb, migration can not be deleted, note that the data file drop pluggable database testpdb keep datafiles cannot be deleted -- check whether the target cdb is suitable for backup pdbSET SERVEROUTPUT ON DECLARE compatible CONSTANT VARCHAR2 (3): = CASE DBMS_PDB.CHECK_PLUG_COMPATIBILITY (pdb_descr_file = >'/ home/oracle/testpdb.xml') WHEN TRUE THEN 'YES' ELSE' NO' END; BEGIN DBMS_OUTPUT.PUT_LINE (compatible); END; /-- create pdbcreate pluggable database testpdb using'/ home/oracle/testpdb.xml'-- nocopy tempfile reuse FILE_NAME_CONVERT= ('/ u01 open alter pluggable database testpdb open; open alter pluggable database testpdb open;, manually delete the original data file, but not delete it, directly restore the oradata-restore the original data file directly Catalog preplugin archivelog'/ u01 open RECOVER PLUGGABLE DATABASE testpdb; ALTER PLUGGABLE DATABASE testpdb open; or rman target sys/oracle@testpdb recover database;Duplicating pdb or rman target sys/oracle@testpdb recover database;Duplicating pdb copy to another existing cdb

Limit

Only active database duplication is supported.

Only the following clauses of the DUPLICATE command are supported: NORESUME

DB_FILE_NAME_CONVERT, SECTION SIZE, and USING COMPRESSED BACKUPSET

The following clauses of the DUPLICATE command are not supported: SPFILE, NO

STANDBY, FARSYNC STANDBY, and LOG_FILE_NAME_CONVERT.

Duplicating a PDB to a CDB that is a standby database is not supported

Only one PDB can be duplicated at a time.

Partial PDB duplication is not supported, only complete PDB duplication is

Supported. For example, you cannot include or exclude specific tablespaces while

Duplicating a PDB

Duplicating a non-CDB as a PDB in an existing CDB is not supported.

Duplicating PDBs that contain TDE-encrypted tablespaces is not supported.

Steps

-- configure network MYDB19C = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = node216) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = mydb19c) TESTCDB = (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = node217) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = testcdb))-- create relevant directories Target end mkdir-p / u01 mkdir mkdir-p / backup/mystpdbalter system set remote_recovery_file_dest='/backup/mystpdb' etc. -- connecting to rman target sys/oracle@mydb19c auxiliary sys/oracle@testcdb-- and starting replication DUPLICATE PLUGGABLE DATABASE mypdb AS mystpdb TO testcdb FROM ACTIVE DATABASEDB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/mypdb','/u01/app/oracle/oradata/TESTCDB/mystpdb';-- will automatically import the relevant metadata replication process

Restore data file: restore complete of datafile 14 to datafile copy

Create pdb

CREATE PLUGGABLE DATABASE mystpdb AS CLONE USING'/ u01apposable oracleUniverse product CREATE PLUGGABLE DATABASE mystpdb AS CLONE USING'/ u01ActionActionoracleandproductAction19.0 / u01ActionoracleandproductAction19.0. / u01applash oraclebyoracleandproduct SOURCE_FILE_NAME_CONVERT = ('/ u01Actionoracleandoradatadbmypdb','/ u01backbackoracleoradata system01.dbf','/ u01aphoracleoradataandTESTCDB _ mystpdbBypmpdbsystem01.dbf') NOCOPY REFRESH MODE MANUAL

Copy and archive to the target side and apply, incremental / incomplete recovery complete

Adjust the data file number: organize the new file_id according to the new environment before deletion

Open pdb

Remote cloning mode

-- set user rights on the source side and create dblink create database link clonePdb connect to mypdb identified by mypdb using'on the target side of alter session set container=mypdb;grant create pluggable database to mypdb;-- (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.80.216) (PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = mypdb)' -- start to create create pluggable database pdb8 from mypdb@clonePdb FILE_NAME_CONVERT=, which is similar to the Duplicating process. ('/ u01AccessorActionoradata hand create pluggable database pdb8 from mypdb@clonePdb FILE_NAME_CONVERT=). At this point, I believe you have a deeper understanding of "simple test analysis of Oracle19c rman usage". You might as well do it in practice! Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

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.