RMAN BACKUP & RECOVERY. Recovery Manager. Veeratteshwaran Sridhar

Transcription

1 RMAN Recovery Manager BACKUP & RECOVERY Veeratteshwaran Sridhar

2 Why Backup & Recovery? The purpose of a backup and recovery strategy is to protect the database against data loss and reconstruct the database after data loss. RMAN Backup Hello Boss, Hello Database Boss..!!!Database is Recovering Recovered!!! Crash

3 Oracle Backup and Recovery Techniques RMAN Recovery Manager User Managed Backup EXP / EXPDP and IMP / IMPDP Export Backup

4 What is RMAN Recovery Manager It is an Oracle Utility that performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files. It is a feature of the Oracle database server and does not require separate installation.

5 Question? In Which version of Oracle RMAN Introduced? Oracle 7 Oracle 8 Oracle 9 RMAN (Recovery Manager) is a backup and recovery manager supplied for Oracle databases (from version 8) created by the Oracle Corporation. It provides database backup, restore, and recovery capabilities addressing high availability and disaster recovery concerns.

6 RMAN - Evolution RMAN (Recovery Manager) is a backup and recovery manager supplied for Oracle databases (from version 8) created by the Oracle Corporation. It provides database backup, restore, and recovery capabilities addressing high availability and disaster recovery concerns.

7 Support for Multitenancy Data Recovery Advisor Recover Table & Table Partitions Multisection Backup Better Catalog Management Image Parallel Copies Backup of NEWLY Same BORN DatafileALL Restartable Backup SHOW Cross-Platform Backup & Restore Improvements Duplicate Enhancements Proactive Health Check Automatic Channel Failover Backup of Archivelogs Block Change Tracking SQL Interface Archivelog Deletion Policy Automatic Block Repair SHOW ALL Enhancement Drop Virtual Database SYSBACKUP Private Catalog thru RMAN

8 Components of RMAN RMAN TARGET DATABASE RMAN CLIENT FAST RECOVERY AREA MEDIA MANAGER RECOVERY CATALOG RECOVERY CATALOG SCHEMA

9 Components of RMAN TAPE DRIVE TAPE DRIVE TARGET DATABASE STANDBY DATABASE RECOVERY CATALOG CONTROL FILE AUXILIARY INSTANCE RECOVER CATALOG SCHEMA RMAN CLIENT

10 Benefits of RMAN Corrupted Blocks are detected and reported. Backs up and restores DATABASES, TABLESPACES, DATAFILES, CONTROLFILES and SPFILES. Can create a single Backup of all archive logs since the last backup. Can delete archive logs after they are backed up. Can backup the Control File and SPFILE automatically. Used for Cloning Databases and creating Standby Databases.

11 RMAN Terminology Image Copy Full copy of a Single File Backup Set Oracle format for a package of Objects backed up Channel A server process on the target database DB Incarnation Incremented each resetlogs Tag A logical name assigned by a user to a backup set or image copy. Tag=< name >

12 FEATURES Closed Database Backups Open Database Backups RECOVERY MANAGER USER MANAGED EXPORT BACKUP Supported Supported Not Supported Supported Supported Requires Rollback or Undo segments to generate consistent backups Incremental Backups Supported Not Supported Not Supported Corrupt Block Detection Supported Automatic Specification of Files to Supported include in the backup Backup Repository Backups to Media Manager (Tapes) Backup of Initialization Parameter Backup of Password and Networking Files Supported. Catalog / NoCatalog Not Supported Not Supported. Files to be backed up should be copied manually. Not Supported. DBA should maintain the backup records. Supported. But Identifies corrupt blocks in the Export Log. Not Supported Not Supported Supported Supported Not Supported Supported Supported Not Supported Not Supported Supported Not Supported

13 RMAN 12c Some New Features SHOW ALL RMAN Configuration Settings SQL Interface Improvements SYSBACKUP Privilege Multisection Backup Improvements Recovering Tables and Table Partitions using RMAN Backups Support for Multitenant Architecture Duplicate Enhancements

14 RMAN 12c RMAN Configuration Settings SHOW ALL;

15 In RMAN 11g RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name PRODDB are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/ /db_1/dbs/snapcf_proddb.f'; # default

16 In RMAN 12c Non CDB RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name RMANDB are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/oracle/product/12.1.0/db_1/dbs/snapcf_rmandb.f'; # default

17 In RMAN 12c CDB RMAN> show all; using target database control file instead of recovery catalog RMAN configuration parameters for database with db_unique_name TEST12C are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default CONFIGURE RMAN OUTPUT TO KEEP FOR 7 DAYS; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/localfs/orasrc/product/db/ /dbs/snapcf_test12c.f'; # default

18 Question? How can you RESET all the configuration settings of RMAN to DEFAULT using a single command? execute dbms_backup_restore.resetconfig; SQL> conn / as sysdba SQL> execute dbms_backup_restore.resetconfig; PL/SQL procedure successfully completed.

19 RMAN 12c SQL Interface Improvements

20 SQL Interface Improvements Till Oracle 11g, to run the SQL commands in the RMAN prompt we need to use SQL Keyword. SQL keyword is required preceding any SQL statements when used in RMAN. RMAN> sql sql statement ; In Oracle 12c RMAN, to run the SQL commands in the RMAN prompt, the use of SQL keyword has been eliminated. Now RMAN has been more friendly to SQL commands. RMAN> sql statement;

21 In RMAN 11g RMAN> sql "alter database datafile '+DATA_GRP/proddb/datafile/users '' offline"; sql statement: alter database datafile ''+DATA_GRP/proddb/datafile/users '' offline Below we can see the datafile belonging to USERS tablespace is OFFLINE. SQL> select file#,name,status from v$datafile; FILE# NAME STATUS DATA_GRP/proddb/datafile/system SYSTEM 2 +DATA_GRP/proddb/datafile/sysaux ONLINE 3 +DATA_GRP/proddb/datafile/undotbs ONLINE 4 +DATA_GRP/proddb/datafile/users OFFLINE 5 +DATA_GRP/proddb/datafile/example ONLINE 6 +DATA_GRP/proddb/datafile/tbsrman ONLINE

22 In RMAN 12c We can use the common SQL syntax without starting the command with the keyword SQL or the necessity to include double or single quotes. It's the same SQL command we use on a SqlPlus session. RMAN> alter database datafile '/vol1/oradata/rmandb/users01.dbf' offline; Statement processed SQL> select name,status from v$datafile; NAME STATUS /vol1/oradata/rmandb/system01.dbf SYSTEM /vol1/oradata/rmandb/example01.dbf ONLINE /vol1/oradata/rmandb/sysaux01.dbf ONLINE /vol1/oradata/rmandb/undotbs01.dbf ONLINE /vol2/tbsrman01.dbf ONLINE /vol1/oradata/rmandb/users01.dbf OFFLINE

23 In RMAN 11g Insert Statements RMAN> sql "insert into scott.dept values (50, ''IT'',''INDIA'')"; sql statement: insert into scott.dept values (50, ''IT'',''INDIA'') RMAN> sql "commit"; sql statement: commit SQL> select * from scott.dept; DEPTNO DNAME LOC IT INDIA 10 ACCOUNTING NEW YORK 20 RESEARCH DALLAS 30 SALES CHICAGO 40 OPERATIONS BOSTON

24 In RMAN 12c Insert Statements RMAN> insert into scott.dept values (50, IT, INDIA ); Statement processed RMAN> commit; Statement processed SQL> select * from scott.dept; DEPTNO DNAME LOC IT INDIA 10 ACCOUNTING NEW YORK 20 RESEARCH DALLAS 30 SALES CHICAGO 40 OPERATIONS BOSTON

25 In a similar way we can also issue create table statements, update statements etc., in RMAN Prompt without any trouble of quotations like single quotes or double quotes and also without the Preceding SQL keyword. What About SELECT and DES[CRIBE] Statements?

26 In RMAN 11g In Oracle 11g, It will not allow us to run SELECT and DESC[RIBE] commands in RMAN Prompt. RMAN> sql "select instance_name,status from v$instance"; sql statement: select instance_name,status from v$instance RMAN> sql 'desc v$instance'; sql statement: desc v$instance RMAN00571:================================================ RMAN-00569: ===============ERROR MESSAGE STACK FOLLOWS===== RMAN00571:================================================ RMAN-03009: failure of sql command on default channel at 02/22/ :11:53 RMAN-11003: failure during parse/execution of SQL statement: desc v$instance ORA-00900: invalid SQL statement

27 In RMAN 12c In Oracle 12c, We can also run SELECT and DESC[RIBE] commands in RMAN Prompt. RMAN> select instance_name,status from v$instance; INSTANCE_NAME STATUS RMANDB OPEN RMAN> desc dual Name Null? Type DUMMY VARCHAR2(1)

28 Question? When was Transportable Tablespace Feature introduced? Oracle 7 Oracle 8 Oracle 9 Transportable Tablespace was introduced in Oracle 8i. Database s source and destination must match the Block Size. OS must be same across the Source and Target.

29 RMAN 12c SYSBACKUP Privilege

30 In RMAN 11g Till Oracle 11g, users required SYSDBA privilege to backup the database. There were no separate roles given to the user who does the Backup and Recovery Operations. ~]$ rman Recovery Manager: Release Production on Sun Feb 22 17:00: Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. RMAN> connect target / connected to target database: PRODDB (DBID= ) RMAN connects you to the target Database or Auxiliary database with the SYSDBA privilege. If you do not have this privilege, then the connection fails. You can connect as SYSDBA using a password file or using operating system authentication. You do not need to specify the SYSDBA option because RMAN uses this option implicitly and automatically. You must only have the SYSDBA privilege to connect to the target database.

31 In RMAN 12c In Oracle 12c a new Predefined role exclusively for Backup and Recovery has been introduced. SYSBACKUP This role is created with the database creation. The SYSBACKUP privilege allows the DBA to perform RMAN backup commands without additional privileges. With RMAN you have same authentication options that are available with SQL*Plus, which are Operating system authentication and password file authentication. RMAN> connect target "/ as sysbackup" connected to target database: RMANDB (DBID= ) SYSBACKUP does not include data access privilege, such as SELECT ANY TABLE. When you don t specify the role explicitly then the default used is as SYSDBA.

32 RMAN 12c Multisection Backup Improvements

33 In RMAN 11g Multi-Section option was introduced in Oracle 11g to handle large Datafiles backups. Using this option RMAN can split up or break up a large file into sections during the backup and recovery. This improves the performance of backup and recovery of a large Datafiles. Multi-Section option can be used in Oracle 11g for the below, 1. Backup using Backup sets. 2. Full Backups using Backup sets. 3. Incremental level 0 backups using Backup sets. SECTION SIZE is the keyword used and each channel will create separate files within the backup sets and backup the database in parallel. This option can only be used to backup the Datafiles. We can not use this option to backup the Control Files.

34 In RMAN 11g SQL> select file_id,file_name,bytes/1024/1024 size_mb from dba_data_files;where file_id=5; FILE_ID FILE_NAME SIZE_MB DATA_GRP/proddb/datafile/example When trying to backup as copy the datafile 5 using SECTION SIZE option, RMAN> backup as copy section size 100M datafile 5; Starting backup at 22-FEB-15 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=52 device type=disk RMAN-00571: ================================================= RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS====== RMAN-00571:================================================= RMAN-03002: failure of backup command at 02/22/ :08:14 RMAN-06580: the SECBYTES option cannot be used with AS COPY

35 In RMAN 12c From Oracle 12c RMAN, Multisection Backups are supported for the below., 1. Backup using Backup sets and Image Copies 2. Full Backups using Backup sets and Image Copies 3. Incremental level 0 backups and higher than level 0 If we specify the SECTION SIZE larger than the actual Datafile size, then RMAN does not use the Multisection option. The following example creates a multisection backup of the database using image copies, BACKUP AS COPY SECTION SIZE 500M DATABASE; The following example creates Multisection level 1 incremental backup, BACKUP INCREMENTAL LEVEL 1 SECTION SIZE 500M DATABASE;

36 In RMAN 12c SQL> select file_id,file_name,bytes/1024/1024 Size_MB from dba_data_files where file_id=2; FILE_ID FILE_NAME SIZE_MB /vol1/oradata/rmandb/example01.dbf RMAN> backup as copy section size 100M datafile 2; Starting backup at 22-FEB-15 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=44 device type=disk channel ORA_DISK_1: starting datafile copy input datafile file number=00002 name=/vol1/oradata/rmandb/example01.dbf backing up blocks 1 through output file name=/oracle/fast_recovery_area/rmandb/datafile/o1_mf_example_bgmoq5kt_.dbf tag=tag t channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03 channel ORA_DISK_1: starting datafile copy input datafile file number=00002 name=/vol1/oradata/rmandb/example01.dbf backing up blocks through output file name=/oracle/fast_recovery_area/rmandb/datafile/o1_mf_example_bgmoq5kt_.dbf tag=tag t channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:07 channel ORA_DISK_1: starting datafile copy input datafile file number=00002 name=/vol1/oradata/rmandb/example01.dbf backing up blocks through output file name=/oracle/fast_recovery_area/rmandb/datafile/o1_mf_example_bgmoq5kt_.dbf tag=tag t channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:04 channel ORA_DISK_1: starting datafile copy input datafile file number=00002 name=/vol1/oradata/rmandb/example01.dbf backing up blocks through output file name=/oracle/fast_recovery_area/rmandb/datafile/o1_mf_example_bgmoq5kt_.dbf tag=tag t channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:03 Finished backup at 22-FEB-15

37 In RMAN 12c RMAN> configure device type disk parallelism 4 backup type to backupset; new RMAN configuration parameters: CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO BACKUPSET; new RMAN configuration parameters are successfully stored released channel: ORA_DISK_1 RMAN> backup as copy section size 100M datafile 2; Starting backup at 22-FEB-15 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=44 device type=disk allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=40 device type=disk allocated channel: ORA_DISK_3 channel ORA_DISK_3: SID=43 device type=disk allocated channel: ORA_DISK_4 channel ORA_DISK_4: SID=58 device type=disk channel ORA_DISK_1: starting datafile copy input datafile file number=00002 name=/vol1/oradata/rmandb/example01.dbf backing up blocks 1 through channel ORA_DISK_2: starting datafile copy input datafile file number=00002 name=/vol1/oradata/rmandb/example01.dbf backing up blocks through channel ORA_DISK_3: starting datafile copy input datafile file number=00002 name=/vol1/oradata/rmandb/example01.dbf backing up blocks through channel ORA_DISK_4: starting datafile copy input datafile file number=00002 name=/vol1/oradata/rmandb/example01.dbf backing up blocks through output file name=/oracle/fast_recovery_area/rmandb/datafile/o1_mf_example_bgmp0psq_.dbf tag=tag t channel ORA_DISK_1: datafile copy complete, elapsed time: 00:00:08 output file name=/oracle/fast_recovery_area/rmandb/datafile/o1_mf_example_bgmp0psq_.dbf tag=tag t channel ORA_DISK_2: datafile copy complete, elapsed time: 00:00:07 output file name=/oracle/fast_recovery_area/rmandb/datafile/o1_mf_example_bgmp0psq_.dbf tag=tag t channel ORA_DISK_3: datafile copy complete, elapsed time: 00:00:07 output file name=/oracle/fast_recovery_area/rmandb/datafile/o1_mf_example_bgmp0psq_.dbf tag=tag t channel ORA_DISK_4: datafile copy complete, elapsed time: 00:00:07 Finished backup at 22-FEB-15

38 RMAN 12c Table and Table Partition Recovery

39 In RMAN 11g Using Database Point-in-Time Recovery (DBPITR). Using Tablespace Point-in-Time Recovery (TSPITR). Using Recycle Bin. Using Flashback Table command.

40 In RMAN 12c From 12c, RMAN enables us to recover tables and table partitions at a point-in-time without affecting other objects in the database. RECOVER TABLE is the command used to recover table and table partitions from an RMAN Backup. Uses Database Backups and Archived Redo Logs for Recovery. The Recovery happens at an Auxiliary location. Uses an automatically created and maintained Auxiliary instance. User need to specify the auxiliary database location using AUXILIARY DESTINATION clause in the RECOVERY command. The database remains online. During Recovery other objects are not disturbed.

41 Table Recovery Useful in below Scenarios When the object has Logical corruption or dropped. When there is no sufficient undo to perform Flashback table. When DDL operation modified the structure and you want to recover the data (Flashback cannot rewind the structural changes). If you need to recover a small number of tables to a point-intime.

42 Table Recovery Pre-Requisites Database must be in ARCHIVELOG mode and read-write mode. At least one full backup is available along with archived logs. Enough disk space is available on the database server for auxiliary instance. If present, any dependent objects to include in recovery. COMPATIBLE parameter must be set to or higher to recover table partition.

43 Table Recovery Steps Determine the backup which has the tables or table partitions that needs to recover to specified point-in-time. Create auxiliary database and recover the tables or table partitions until specified point-in-time. Take a data dump export with recovered tables or table partitions. Import the dump into target database. Rename the recovered tables or table partitions in the target database. Clean-up the Auxiliary Instance. 1

44 Table Recovery RMAN> backup as backupset incremental level 0 database plus archivelog; Backup the Database SQL> select to_char(sysdate, 'DD-MON-YYYY HH24:MI:SS am'),current_scn from v$database; Check the current SCN / Time SYSDATE CURRENT_SCN FEB :51:12 am SQL> drop table TEST; Drop the Table Table dropped. SQL> desc TEST ERROR: ORA-04043: object TEST does not exist Check if the Table Exists

45 Table Recovery ~]$ rman target / Connect to RMAN Recovery Manager: Release Production on Tue Feb 24 00:52: Copyright (c) 1982, 2013, Oracle and/or its affiliates. All rights reserved. connected to target database: RMANDB (DBID= ) Recover Table RMAN> RECOVER TABLE SCOTT."TEST" UNTIL TIME "to_date('24-feb :51:12','DD-MON-YYYY:HH24:MI:SS')" AUXILIARY DESTINATION '/backup' DATAPUMP DESTINATION '/backup' DUMP FILE 'testdump.dmp';

46 Table Recovery How it Works? 1. Creating automatic instance, with SID='axEy' initialization parameters used for automatic instance: db_name=rmandb db_unique_name=axey_pitr_rmandb compatible= db_block_size=8192 db_files=200 sga_target=1g processes=80 diagnostic_dest=/oracle db_create_file_dest=/backup log_archive_dest_1='location=/backup' #No auxiliary parameter file used

47 Table Recovery How it Works? 2. Restore of the Control File for the Auxiliary Instance contents of Memory Script: { # set requested point in time set until time "to_date('24-feb :51:12','DD-MON- YYYY:HH24:MI:SS')"; # restore the controlfile restore clone controlfile; # mount the controlfile sql clone 'alter database mount clone database'; # archive current online log sql 'alter system archive log current'; }

48 Table Recovery How it Works? 3. A list of Datafiles that will be restored, followed by their restore and recovery in the auxiliary instance. contents of Memory Script: { # set requested point in time set until time "to_date('24-feb :51:12','DD-MON-YYYY:HH24:MI:SS')"; # set destinations for recovery set and auxiliary set datafiles set newname for clone datafile 1 to new; set newname for clone datafile 4 to new; set newname for clone datafile 3 to new; set newname for clone tempfile 1 to new; # switch all tempfiles switch clone tempfile all; # restore the tablespaces in the recovery set and the auxiliary set restore clone datafile 1, 4, 3; switch clone datafile all; } contents of Memory Script: { # set requested point in time set until time "to_date('24-feb :51:12','DD-MON-YYYY:HH24:MI:SS')"; # online the datafiles restored or switched sql clone "alter database datafile 6 online"; # recover and open resetlogs recover clone database tablespace "USERS", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog; alter clone database open resetlogs; }

49 Table Recovery How it Works? 4. Export of tables from the auxiliary instance via Oracle Data Pump. contents of Memory Script: { # create directory for datapump import sql "create or replace directory TSPITR_DIROBJ_DPDIR as '' /backup''"; # create directory for datapump export sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as '' /backup''"; } executing Memory Script sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/backup' sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/backup' Performing export of tables... EXPDP> Starting "SYS"."TSPITR_EXP_axEy_ugii": EXPDP> Estimate in progress using BLOCKS method... EXPDP> Processing object type TABLE_EXPORT/TABLE/TABLE_DATA EXPDP> Total estimation using BLOCKS method: 64 KB EXPDP> Processing object type TABLE_EXPORT/TABLE/TABLE EXPDP> Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT EXPDP> Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS EXPDP> Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS EXPDP> Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER EXPDP>.. exported "SCOTT"."TEST" KB 3 rows EXPDP> Master table "SYS"."TSPITR_EXP_axEy_ugii" successfully loaded/unloaded EXPDP> ****************************************************************************** EXPDP> Dump file set for SYS.TSPITR_EXP_axEy_ugii is: EXPDP> /backup/testdump.dmp EXPDP> Job "SYS"."TSPITR_EXP_axEy_ugii" successfully completed at Tue Feb 24 00:54: elapsed 0 00:00:31 Export completed

50 Table Recovery How it Works? 5. Import of tables, constraints, indexes, and other dependent objects into the target database from the Data Pump export file. contents of Memory Script: { # shutdown clone before import shutdown clone abort } executing Memory Script Oracle instance shut down Performing import of tables... IMPDP> Master table "SYS"."TSPITR_IMP_axEy_Ewrg" successfully loaded/unloaded IMPDP> Starting "SYS"."TSPITR_IMP_axEy_Ewrg": IMPDP> Processing object type TABLE_EXPORT/TABLE/TABLE IMPDP> Processing object type TABLE_EXPORT/TABLE/TABLE_DATA IMPDP>.. imported "SCOTT"."TEST" KB 3 rows IMPDP> Processing object type TABLE_EXPORT/TABLE/CONSTRAINT/CONSTRAINT IMPDP> Processing object type TABLE_EXPORT/TABLE/INDEX/STATISTICS/INDEX_STATISTICS IMPDP> Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS IMPDP> Processing object type TABLE_EXPORT/TABLE/STATISTICS/MARKER IMPDP> Job "SYS"."TSPITR_IMP_axEy_Ewrg" successfully completed at Tue Feb 24 00:54: elapsed 0 00:00:02 Import completed

51 Table Recovery How it Works? 6. Clean-up of the Auxiliary Instance. Removing automatic instance Automatic instance removed auxiliary instance file /backup/rmandb/datafile/o1_mf_temp_bgpzkdmn_.tmp deleted auxiliary instance file /backup/axey_pitr_rmandb/onlinelog/o1_mf_3_bgpzl21n_.log deleted auxiliary instance file /backup/axey_pitr_rmandb/onlinelog/o1_mf_2_bgpzl0q8_.log deleted auxiliary instance file /backup/axey_pitr_rmandb/onlinelog/o1_mf_1_bgpzkzlr_.log deleted auxiliary instance file /backup/axey_pitr_rmandb/datafile/o1_mf_users_bgpzky0x_.dbf deleted auxiliary instance file /backup/rmandb/datafile/o1_mf_sysaux_bgpzhy1m_.dbf deleted auxiliary instance file /backup/rmandb/datafile/o1_mf_undotbs1_bgpzhy13_.dbf deleted auxiliary instance file /backup/rmandb/datafile/o1_mf_system_bgpzhy16_.dbf deleted auxiliary instance file /backup/rmandb/controlfile/o1_mf_bgpzhq7j_.ctl deleted auxiliary instance file testdump.dmp deleted Finished recover at 24-FEB-15

52 RMAN 12c Support for Multitenant Architecture

53 Oracle 12c Multitenant Architecture Multitenant Architecture was introduced in Oracle 12c. The Architecture consists of Container Database and Pluggable Databases. RMAN 12c provides full support for backup and recovery of these Container and Pluggable databases. You can backup the Entire Container Database. It is similar to a Full Backup of a Non-CDB database. Backing up a Container Database includes all the Pluggable Databases and Archive Logs.

54 Oracle 12c Multitenancy

55 RMAN 12c in Multitenant Architecture BACKUP COMMANDS Backing up the Whole CDB or Non-CDB Database RMAN> BACKUP DATABASE; Backing up a Pluggable Database(s) RMAN> BACKUP PLUGGABLE DATABASE PDB1; RMAN> BACKUP PLUGGABLE DATABASE PDB1, PDB2; Backing up a ROOT Container Database RMAN> BACKUP PLUGGABLE DATABASE ROOT; Backing up a Tablespace of a Pluggable Database RMAN> BACKUP TABLESPACE PDB1:TEST_TBS;

56 RMAN 12c in Multitenant Architecture RECOVER COMMANDS Recover the Whole CDB or Non-CDB Database RMAN> RECOVER DATABASE; Recover a Pluggable Database(s) RMAN> RECOVER PLUGGABLE DATABASE PDB1; RMAN> RECOVER PLUGGABLE DATABASE PDB1, PDB2; Recover a ROOT Container Database RMAN> RECOVER PLUGGABLE DATABASE ROOT; Recover a Tablespace of a Pluggable Database RMAN> RECOVER TABLESPACE PDB1:TEST_TBS;

57 RMAN 12c DUPLICATE Enhancements

58 RMAN 12c Duplicate Enhancements On using DUPLICATE command Database is Created and Opened with RESETLOGS. In 12c a Clause has been introduced NOOPEN. The Database will be created and will not be Opened. NOOPEN clause is used as below., RMAN> DUPLICATE TARGET DATABASE TO DUPDB FROM ACTIVE DATABASE NOOPEN;

59 RMAN 12c Duplicate Enhancements NOOPEN Clause is used in the below Situations., If any modifications needed to the Initialization Parameters before opening the database. If you plan to create a database for Upgrade or open with the Upgrade mode (Startup Upgrade).

60 Thank You..!!!