Using the new 12.2 PDB archive feature documented here: https://docs.oracle.com/database/122/NEWFT/new_features.htm#GUID-F7D4B5DF-1DEE-4488-B093-3F73677E5D18
"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. "
If the data files are all on the file system (/u01, /u02, etc) this command works fine:
alter pluggable database dev05 unplug into '/u01/app/oracle/pdbarch/dev05.pdb';
And dev05.pdb is really big, but compressed quite a bit.
HOWEVER, if the CDB containing DEV05 is stored in ASM (e.g., "+DATA"), then all I get is a PDB archive file with only the manifest, and no other compressed PDB archive to be found!!!
[oracle@db122dev /u01/app/oracle/pdbarch]$ ls -l
total 4
-rw-r--r--. 1 oracle dba 1739 Mar 30 22:35 dev05.pdb
[oracle@db122dev /u01/app/oracle/pdbarch]$ unzip dev05.pdb
Archive: dev05.pdb
warning: stripped absolute path spec from /u01/app/oracle/pdbarch/dev05.xml
inflating: u01/app/oracle/pdbarch/dev05.xml
[oracle@db122dev /u01/app/oracle/pdbarch]$ more dev05.xml
. . .
<file>
<path>+DATA/REL2017/4BFF16765EAF4E42E0550A0027E39010/DATAFILE/lclusers.319.940025507</path>
. . .
The documentation is a bit thin, but I can't find anywhere where it says there are any limitations if you use ASM for your data files, control files, wallets, etc.
Thanks. Using a PDB archive file with ASM is not very useful since it's not putting everything into one file!