1 Description
When a pluggable database (PDB) is unplugged, all data files associated with a PDB along with the PDB manifest need to be copied or moved individually over to the remote server where it is plugged into another multitenant container database (CDB). With this new feature, a you can choose to create a single PDB archive file, a compressed file with the .pdb extension, that contains the PDB manifest and all of the data files when unplugging a PDB. When plugging in a PDB, the presence of a .pdb file is interpreted and the PDB is plugged into the CDB. You can choose to run the PDB plug-in compatibility test directly on the PDB archive without extracting the PDB manifest file from the archive.
From 12.2 With this new feature, you can choose to create a single PDB archive file, a compressed file with a .pdb extension, which contains all the data files and the PDB PDB metadata.
This function is very useful, greatly reducing the complexity of the migration of the PDB.
FIG pull PDB 1
Experiment 2
2.1 Unplug PDB
Corresponding PDB must be closed, in the MOUNT state.
SQL> show pdbs;
CON_ID CON_NAME OPEN MODE RESTRICTED
---------- ------------------------------ ---------- ----------
2 PDB$SEED READ ONLY NO
3 LEI1 MOUNTED
4 LEI2 MOUNTED
5 SIHONG MOUNTED
6 CNDBA_PDB_REF MOUNTED
- Imported into the archive file (.pdb)
SQL> alter pluggable database sihong unplug into '/software/backup/sihong.pdb';
Pluggable database altered.
- Take a look at the file size
[oracle@db12CR2 backup]$ ll -h
total 440M
-rw-r--r-- 1 oracle oinstall 440M Aug 8 11:40 sihong.pdb
pdb file can be used to quickly package migrating PDB, backup and so on.