The Oracle Multitenant architecture came with Oracle 12c a few years ago. For people usually working with traditional Non-CDB database it might be confusing the first time to do Backup and Recovery with pluggable databases (PDBs)
In this document we are trying to explain how to use RMAN backup and recovery in a multitenant environment for an oracle 19c database with 2 pluggable databases.
Below the configuration we are using.
SQL> show pdbs
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB1 READ WRITE NO
4 PDB2 READ WRITE NO
We will not use a recovery catalog, but the use of recovery is the same than in a non-CDB environment.
Note that starting with Oracle 19c, we can now connect to a recovery catalog when the target database is a PDB.
Whole CDB Backups
Backin up a whole CDB is like backing up non-CDB database. We have to backup
-root pdb
-all pluggable databases
-archived logs
The steps are:
1- Connect to the root container with a common user having SYSBACKUP or SYSDBA privileges
RMAN> connect target / connected to target database: ORCL (DBID=1546409981) RMAN>
2- Launch the backup
RMAN> BACKUP DATABASE PLUS ARCHIVELOG; Starting backup at 11-SEP-19 current log archived using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=279 device type=DISK channel ORA_DISK_1: starting archived log backup set channel ORA_DISK_1: specifying archived log(s) in backup set input archived log thread=1 sequence=6 RECID=1 STAMP=1018632767 input archived log thread=1 sequence=7 RECID=2 STAMP=1018690452 input archived log thread=1 sequence=8 RECID=3 STAMP=1018691169 input archived log thread=1 sequence=9 RECID=4 STAMP=1018693343 channel ORA_DISK_1: starting piece 1 at 11-SEP-19 channel ORA_DISK_1: finished piece 1 at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2019_09_11/o1_mf_annnn ... ... Finished backup at 11-SEP-19 Starting Control File and SPFILE Autobackup at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2019_09_11/o1_mf_s_1018693411_gqkcr46z_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 11-SEP-19
Oracle also recommends to backup sometimes the root container.
Once connected to the root container with a common user, run the backup command
RMAN> BACKUP DATABASE ROOT; Starting backup at 11-SEP-19 using channel ORA_DISK_1 channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00001 name=/u01/app/oracle/oradata/ORCL/system01.dbf input datafile file number=00003 name=/u01/app/oracle/oradata/ORCL/sysaux01.dbf input datafile file number=00004 name=/u01/app/oracle/oradata/ORCL/undotbs01.dbf input datafile file number=00007 name=/u01/app/oracle/oradata/ORCL/users01.dbf channel ORA_DISK_1: starting piece 1 at 11-SEP-19 channel ORA_DISK_1: finished piece 1 at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T103019_gqkd4vxb_.bkp tag=TAG20190911T103019 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:16 Finished backup at 11-SEP-19 Starting Control File and SPFILE Autobackup at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2019_09_11/o1_mf_s_1018693836_gqkd5d65_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 11-SEP-19 RMAN>
PDBSs Backups
Backing up PDBs is not difficult, there are just some mechanisms to know. When connecting with RMAN to the root container, we can back up one or more PDBs while directly connecting to a PDB, we can only back up this PDB.
1- Connect to the root container with a common user having SYSBACKUP or SYSDBA privileges
RMAN> connect target / connected to target database: ORCL (DBID=1546409981) RMAN>
And backup individual PDBs
RMAN> BACKUP PLUGGABLE DATABASE PDB1,PDB2; Starting backup at 11-SEP-19 using channel ORA_DISK_1 channel ORA_DISK_1: starting full datafile backup set ... ... Starting Control File and SPFILE Autobackup at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2019_09_11/o1_mf_s_1018695111_gqkff85l_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 11-SEP-19 RMAN>
2- Connecting to the PDBs with a local user having SYSBACKUP or SYSDBA privileges
PDB1
RMAN> connect target sys/root@pdb1 connected to target database: ORCL:PDB1 (DBID=4178439423) RMAN> BACKUP DATABASE; Starting backup at 11-SEP-19 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=279 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00010 name=/u01/app/oracle/oradata/ORCL/pdb1/sysaux01.dbf input datafile file number=00009 name=/u01/app/oracle/oradata/ORCL/pdb1/system01.dbf input datafile file number=00011 name=/u01/app/oracle/oradata/ORCL/pdb1/undotbs01.dbf input datafile file number=00012 name=/u01/app/oracle/oradata/ORCL/pdb1/users01.dbf channel ORA_DISK_1: starting piece 1 at 11-SEP-19 channel ORA_DISK_1: finished piece 1 at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/92359B0BEC8B4545E0531502A8C0F64E/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T110707_gqkg9w5n_.bkp tag=TAG20190911T110707 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07 Finished backup at 11-SEP-19 RMAN>
PDB2
RMAN> connect target sys/root@pdb2 connected to target database: ORCL:PDB2 (DBID=3996013191) RMAN> BACKUP DATABASE; Starting backup at 11-SEP-19 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=279 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00014 name=/u01/app/oracle/oradata/ORCL/pdb2/sysaux01.dbf input datafile file number=00013 name=/u01/app/oracle/oradata/ORCL/pdb2/system01.dbf input datafile file number=00015 name=/u01/app/oracle/oradata/ORCL/pdb2/undotbs01.dbf input datafile file number=00016 name=/u01/app/oracle/oradata/ORCL/pdb2/users01.dbf channel ORA_DISK_1: starting piece 1 at 11-SEP-19 channel ORA_DISK_1: finished piece 1 at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/92359E387C754644E0531502A8C02C00/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T110844_gqkgdwmm_.bkp tag=TAG20190911T110844 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:07 Finished backup at 11-SEP-19 RMAN>
Tablespace Backup in a PDB
Tablespaces in different PDBs can have the same name. So to eliminate ambiguity always connect to the PDB you want to back up tablespaces.
1- Connect to the PDB with a local user having SYSBACKUP or SYSDBA privilege
[oracle@oraadserver ~]$ rman target sys/root@pdb1 Recovery Manager: Release 19.0.0.0.0 - Production on Wed Sep 11 11:35:53 2019 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL:PDB1 (DBID=4178439423)
2- Issue the BACKUP TABLESPACE command
RMAN> BACKUP TABLESPACE USERS; Starting backup at 11-SEP-19 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=290 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00012 name=/u01/app/oracle/oradata/ORCL/pdb1/users01.dbf channel ORA_DISK_1: starting piece 1 at 11-SEP-19 channel ORA_DISK_1: finished piece 1 at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/92359B0BEC8B4545E0531502A8C0F64E/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T113623_gqkj0qxl_.bkp tag=TAG20190911T113623 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01 Finished backup at 11-SEP-19 RMAN>
Data File Backup in a PDB
Data Files are identified by a unique number across the CDB. So for the Backup we can connect either to the root container or directly to the PDB.
Note that while directly connecting to the PDB, we can only backup files belonging to this PDB.
1- Connect to the root container with a common user having SYSBACKUP or SYSDBA privileges
[oracle@oraadserver admin]$ rman target / Recovery Manager: Release 19.0.0.0.0 - Production on Wed Sep 11 11:54:42 2019 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL (DBID=1546409981)
2- Backup the Data File
RMAN> BACKUP DATAFILE 10; Starting backup at 11-SEP-19 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=274 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00010 name=/u01/app/oracle/oradata/ORCL/pdb1/sysaux01.dbf channel ORA_DISK_1: starting piece 1 at 11-SEP-19 channel ORA_DISK_1: finished piece 1 at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/92359B0BEC8B4545E0531502A8C0F64E/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T115504_gqkk3s44_.bkp tag=TAG20190911T115504 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03 Finished backup at 11-SEP-19 Starting Control File and SPFILE Autobackup at 11-SEP-19 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2019_09_11/o1_mf_s_1018698908_gqkk3wwt_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 11-SEP-19 RMAN>
Whole CDB Complete Recovery
Suppose we lose all Data Files, Control Files and Redo Log Files of the whole container. We can restore with the following steps
1- Restore Control Files while connecting to the root container
[oracle@oraadserver ORCL]$ rman target / Recovery Manager: Release 19.0.0.0.0 - Production on Wed Sep 11 14:25:25 2019 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database (not started) RMAN> startup nomount Oracle instance started Total System Global Area 872413680 bytes Fixed Size 9140720 bytes Variable Size 297795584 bytes Database Buffers 557842432 bytes Redo Buffers 7634944 bytes RMAN> RMAN> restore controlfile FROM AUTOBACKUP; Starting restore at 11-SEP-19 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=21 device type=DISK recovery area destination: /u01/app/oracle/fast_recovery_area database name (or database unique name) used for search: ORCL channel ORA_DISK_1: AUTOBACKUP /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2019_09_11/o1_mf_s_1018698908_gqkk3wwt_.bkp found in the recovery area AUTOBACKUP search with format "%F" not attempted because DBID was not set channel ORA_DISK_1: restoring control file from AUTOBACKUP /u01/app/oracle/fast_recovery_area/ORCL/autobackup/2019_09_11/o1_mf_s_1018698908_gqkk3wwt_.bkp channel ORA_DISK_1: control file restore from AUTOBACKUP complete output file name=/u01/app/oracle/oradata/ORCL/control01.ctl output file name=/u01/app/oracle/fast_recovery_area/ORCL/control02.ctl Finished restore at 11-SEP-19 RMAN>
2- Mount the CDB
RMAN> alter database mount; released channel: ORA_DISK_1 Statement processed
3- List Backup of archived logs
RMAN> list backup of archivelog all;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
2 397.52M DISK 00:00:04 11-SEP-19
BP Key: 2 Status: AVAILABLE Compressed: NO Tag: TAG20190911T102225
Piece Name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2019_09_11/o1_mf_annnn_TAG20190911T102225_gqkcp1k9_.bkp
List of Archived Logs in backup set 2
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 6 2120330 10-SEP-19 2155559 10-SEP-19
1 7 2155559 10-SEP-19 2257139 11-SEP-19
1 8 2257139 11-SEP-19 2327294 11-SEP-19
1 9 2327294 11-SEP-19 2342937 11-SEP-19
BS Key Size Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
7 5.00K DISK 00:00:00 11-SEP-19
BP Key: 7 Status: AVAILABLE Compressed: NO Tag: TAG20190911T102330
Piece Name: /u01/app/oracle/fast_recovery_area/ORCL/backupset/2019_09_11/o1_mf_annnn_TAG20190911T102330_gqkcr2n1_.bkp
List of Archived Logs in backup set 7
Thrd Seq Low SCN Low Time Next SCN Next Time
---- ------- ---------- --------- ---------- ---------
1 10 2342937 11-SEP-19 2342996 11-SEP-19
RMAN>
4- Restore the database according to the sequence
RMAN> restore database until sequence 11; Starting restore at 11-SEP-19 Starting implicit crosscheck backup at 11-SEP-19 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=24 device type=DISK Crosschecked 18 objects ... ... channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:07 Finished restore at 11-SEP-19 RMAN>
5- Recover the database
RMAN> recover database until sequence 11; Starting recover at 11-SEP-19 using channel ORA_DISK_1 starting media recovery archived log for thread 1 with sequence 10 is already on disk as file /u01/app/oracle/fast_recovery_area/ORCL/archivelog/2019_09_11/o1_mf_1_10_gqkcr27d_.arc archived log file name=/u01/app/oracle/fast_recovery_area/ORCL/archivelog/2019_09_11/o1_mf_1_10_gqkcr27d_.arc thread=1 sequence=10 media recovery complete, elapsed time: 00:00:00 Finished recover at 11-SEP-19 RMAN>
6- Open database in Resetlogs mode
RMAN> alter database open resetlogs; Statement processed RMAN>
PDBs Complete Recovery
To recover a PDB we can :
– Connect to the root and then use the RESTORE PLUGGABLE DATABASE and RECOVER PLUGGABLE DATABASE commands.
1- Close the PDB to recover
SQL> alter pluggable database pdb1 close;
Pluggable database altered.
SQL> show pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB1 MOUNTED
4 PDB2 READ WRITE NO
SQL>
2- Connect to rman on the root container and issue the restore command
RMAN> RESTORE PLUGGABLE DATABASE PDB1; Starting restore at 11-SEP-19 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=56 device type=DISK channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00009 to /u01/app/oracle/oradata/ORCL/pdb1/system01.dbf channel ORA_DISK_1: restoring datafile 00010 to /u01/app/oracle/oradata/ORCL/pdb1/sysaux01.dbf channel ORA_DISK_1: restoring datafile 00011 to /u01/app/oracle/oradata/ORCL/pdb1/undotbs01.dbf channel ORA_DISK_1: restoring datafile 00012 to /u01/app/oracle/oradata/ORCL/pdb1/users01.dbf channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fast_recovery_area/ORCL/92359B0BEC8B4545E0531502A8C0F64E/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T144816_gqkv9btm_.bkp channel ORA_DISK_1: piece handle=/u01/app/oracle/fast_recovery_area/ORCL/92359B0BEC8B4545E0531502A8C0F64E/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T144816_gqkv9btm_.bkp tag=TAG20190911T144816 channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:07 Finished restore at 11-SEP-19
3- Recover the pluggable database
RMAN> RECOVER PLUGGABLE DATABASE PDB1; Starting recover at 11-SEP-19 using channel ORA_DISK_1 starting media recovery media recovery complete, elapsed time: 00:00:01 Finished recover at 11-SEP-19
4- Open the pluggable database
RMAN> alter pluggable database PDB1 open; Statement processed RMAN>
– Connect to the PDB and use the RESTORE DATABASE and RECOVER DATABASE commands.
1- Close the PDB to recover
SQL> show pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 PDB1 READ WRITE NO
4 PDB2 MOUNTED
SQL>
2- Connect to the PDB and issue the RESTORE DATABASE command
[oracle@oraadserver pdb1]$ rman target sys/root@pdb2 Recovery Manager: Release 19.0.0.0.0 - Production on Wed Sep 11 15:19:03 2019 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL:PDB2 (DBID=3996013191, not open) RMAN> RESTORE DATABASE; Starting restore at 11-SEP-19 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=45 device type=DISK channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00013 to /u01/app/oracle/oradata/ORCL/pdb2/system01.dbf channel ORA_DISK_1: restoring datafile 00014 to /u01/app/oracle/oradata/ORCL/pdb2/sysaux01.dbf channel ORA_DISK_1: restoring datafile 00015 to /u01/app/oracle/oradata/ORCL/pdb2/undotbs01.dbf channel ORA_DISK_1: restoring datafile 00016 to /u01/app/oracle/oradata/ORCL/pdb2/users01.dbf channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fast_recovery_area/ORCL/92359E387C754644E0531502A8C02C00/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T144816_gqkv9tfq_.bkp channel ORA_DISK_1: piece handle=/u01/app/oracle/fast_recovery_area/ORCL/92359E387C754644E0531502A8C02C00/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T144816_gqkv9tfq_.bkp tag=TAG20190911T144816 channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:07 Finished restore at 11-SEP-19 RMAN>
3- Recover the pluggable database
RMAN> recover database; Starting recover at 11-SEP-19 using channel ORA_DISK_1 starting media recovery media recovery complete, elapsed time: 00:00:01 Finished recover at 11-SEP-19
4- Open the database
RMAN> alter database open ; Statement processed RMAN>
Complete Tablespace Recovery in a PDB
-Non-SYSTEM Tablespace
To recover a Non-SYSTEM Tablespace in a PDB we can do next steps
1-Put the tablespace offline while connecting to the PDB
SQL> ALTER TABLESPACE MYTAB OFFLINE; Tablespace altered. SQL>
2- Connect to the PDB with RMAN and issue the RESTORE TABLESPACE command
[oracle@oraadserver pdb2]$ rman target sys/root@pdb2 Recovery Manager: Release 19.0.0.0.0 - Production on Wed Sep 11 16:52:37 2019 Version 19.3.0.0.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL:PDB2 (DBID=3996013191) RMAN> RESTORE TABLESPACE MYTAB; Starting restore at 11-SEP-19 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=274 device type=DISK channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00017 to /u01/app/oracle/oradata/ORCL/pdb2/mytab01.dbf channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fast_recovery_area/ORCL/92359E387C754644E0531502A8C02C00/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T163708_gql1o4gx_.bkp channel ORA_DISK_1: piece handle=/u01/app/oracle/fast_recovery_area/ORCL/92359E387C754644E0531502A8C02C00/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T163708_gql1o4gx_.bkp tag=TAG20190911T163708 channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:01 Finished restore at 11-SEP-19
3- Issue the RECOVER TABLESPACE command
RMAN> RECOVER TABLESPACE MYTAB; Starting recover at 11-SEP-19 using channel ORA_DISK_1 starting media recovery media recovery complete, elapsed time: 00:00:01 Finished recover at 11-SEP-19 RMAN>
4- Put back the tablespace ONLINE
RMAN> ALTER TABLESPACE MYTAB ONLINE; Statement processed RMAN>
-SYSTEM Tablespace
To recover a SYSTEM Tablespace in a PDB
1- Shutdown the entire CDB and Mount it
[oracle@oraadserver pdb2]$ sqlplus / as sysdba
SQL*Plus: Release 19.0.0.0.0 - Production on Wed Sep 11 17:09:33 2019
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle. All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0
SQL> shut immediate
ORA-01116: error in opening database file 13
ORA-01110: data file 13: '/u01/app/oracle/oradata/ORCL/pdb2/system01.dbf'
ORA-27041: unable to open file
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
SQL> shut abort;
ORACLE instance shut down.
SQL>
SQL> startup mount
ORACLE instance started.
Total System Global Area 872413680 bytes
Fixed Size 9140720 bytes
Variable Size 310378496 bytes
Database Buffers 545259520 bytes
Redo Buffers 7634944 bytes
Database mounted.
SQL> show pdbs
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED MOUNTED
3 PDB1 MOUNTED
4 PDB2 MOUNTED
SQL>
2- Connect to root container and restore the corresponding files (Files can be identified using command REPORT SCHEMA for example)
RMAN> RESTORE DATAFILE 13; Starting restore at 11-SEP-19 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=26 device type=DISK channel ORA_DISK_1: starting datafile backup set restore channel ORA_DISK_1: specifying datafile(s) to restore from backup set channel ORA_DISK_1: restoring datafile 00013 to /u01/app/oracle/oradata/ORCL/pdb2/system01.dbf channel ORA_DISK_1: reading from backup piece /u01/app/oracle/fast_recovery_area/ORCL/92359E387C754644E0531502A8C02C00/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T163708_gql1o4gx_.bkp channel ORA_DISK_1: piece handle=/u01/app/oracle/fast_recovery_area/ORCL/92359E387C754644E0531502A8C02C00/backupset/2019_09_11/o1_mf_nnndf_TAG20190911T163708_gql1o4gx_.bkp tag=TAG20190911T163708 channel ORA_DISK_1: restored backup piece 1 channel ORA_DISK_1: restore complete, elapsed time: 00:00:03 Finished restore at 11-SEP-19 RMAN>
3- Recover the Data File
RMAN> RECOVER DATAFILE 13; Starting recover at 11-SEP-19 using channel ORA_DISK_1 starting media recovery media recovery complete, elapsed time: 00:00:00 Finished recover at 11-SEP-19
4- Open all containers
RMAN> alter database open; Statement processed RMAN> ALTER PLUGGABLE DATABASE ALL OPEN READ WRITE; Statement processed RMAN>
Conclusion
In this blog we basically explain how to use RMAN in a multitenant environment. We did not talked about PITR recovery, we will do it in a coming blog.
Note also that we did not use RMAN commands like LIST FAILURE, ADVISE FAILURE and REPAIR FAILURE. But these commands also work.
Cet article RMAN in a Multitenant Environment est apparu en premier sur Blog dbi services.