.
\nI use transportable tablespaces a lot since 8i, here are just a few examples.
\nSame disclaimer here as in the first post of the series: don’t expect to get those posts close to what you will have at the exam, but they cover important points that matches the exam topics.
Information about the exam says: Create a plugged-in tablespace by using the transportable tablespace feature. this is the TTS feature we know for a long time. The ‘plugged-in’ term is how it was originally called (see patent: http://www.google.tl/patents/US5890167 from 1997). When 12c came with pluggable database, I said that it was just an extension of the TTS feature where the SYSTEM tablespace can be transported as well, thanks to multitenant architecture that separates application dictionary.
\nWhat’s new in 12c is the ability to transport a whole database, which means use TTS for all non-system tablespaces.
\nSo about documentation, open the Oracle® Database Administrator’s Guide, search for ‘transport’ and you have a whole chapter about transporting data. then go to: Transporting Database
I’ve a PDB pluggable database with some tablespaces and tables, and I set the user tablespace read-only;
\n\nsqlplus / as sysdba\ncreate pluggable database PDB admin user admin identified by admin file_name_convert=('/u01/app/oracle/oradata/pdbseed','/u02/app/oracle/oradata/PDB');\nalter pluggable database PDB open;\nalter session set container=PDB;\ngrant dba to DEMO identified by demo;\ncreate tablespace USERS datafile '/tmp/usersPDB.dbf' size 10M;\ncreate table DEMO.DEMO tablespace USERS as select current_timestamp ts from dual;\nalter tablespace USERS read only;\nquit\nThen I create a new pluggable database from seed and create a database link to transport the tablespace into it:
\n\nsqlplus / as sysdba\ncreate pluggable database PDBNEW admin user admin identified by admin file_name_convert=('/u01/app/oracle/oradata/pdbseed','/u02/app/oracle/oradata/PDBNEW');\nalter session set container=PDBNEW;\nstartup\ncreate database link DBL_PDB connect to system identified by oracle using '//localhost/PDB';\ncreate directory TMP as '/tmp';\nquit\ncp /tmp/usersPDB.dbf /tmp/usersPDBNEW.dbf\nimpdp '\"sys/oracle@//localhost/PDBNEW as sysdba\"' network_link=DBL_PDB directory=TMP FULL=Y TRANSPORTABLE=always transport_datafiles=/tmp/usersPDBNEW.dbf\nThis is database transport. It’s just the possibility to use both FULL=Y and TRANSPORTABLE. I don’t like FULL imports because they bring some mess with pseudo system schemas. But with multitenant, what is in a PDB is only user schemas.
\nIf I wanted to transport only the tablespace, I need to have the user created before:
\n\nsqlplus / as sysdba\nalter pluggable database PDBNEW close;\ndrop pluggable database PDBNEW including datafiles;\ncreate pluggable database PDBNEW admin user admin identified by admin file_name_convert=('/u01/app/oracle/oradata/pdbseed','/u02/app/oracle/oradata/PDBNEW');\nalter session set container=PDBNEW;\nstartup\ncreate database link DBL_PDB connect to system identified by oracle using '//localhost/PDB';\ncreate directory TMP as '/tmp';\ngrant dba to DEMO identified by demo;\nquit\nimpdp '\"sys/oracle@//localhost/PDBNEW as sysdba\"' network_link=DBL_PDB directory=TMP TRANSPORT_TABLESPACES=USERS transport_datafiles=/tmp/usersPDBNEW.dbf\nThis is the simple transport tablespace we know from a long time. Need to create the user, then all metadata is imported by data pump and data comes with the files. Here I used NETWORK_LINK because it’s the most simple, but everything is the same with a dumpfile. Need to copy datafiles with it to the target.
\nOn different endianness, RMAN can be used to convert. All is referenced in the ‘transporting data’ chapter of documentation.