Creating SecureFile LOBs on Import

You are now enabled to specify a LOB storage method to be used during a Data Pump
Import process regardless of the settings in the source database when the Data Pump
Export was made. This provides a straightforward method that allows users to easily
migrate from the BasicFile LOBs to SecureFile LOBs
Once again, this new feature is only possible due to the introduction of a new metadata
TRANSFORM parameter called LOB_STORAGE (as you can see, Oracle has introduced
many enhancements to the TRANSFORM parameter on Data Pump).
Now let's take a look at an example of how to use this new TRANSFORM parameter in
real life:
$ impdp test/test DIRECTORY=datapump DUMPFILE=test.dmp
TRANSFORM=LOB_STORAGE:SECUREFILE
Note: When setting the parameter to SECUREFILE or BASICFILE, you are specifying
the LOB storage method that will be applied to all the LOBs during the import session. If
default is set, then the LOB clause is omitted and all the imported tables will use the
DEFAULT mode associated with the destination tablespace. Finally, if you set the
parameter to NO_CHANGE, the import process will use the LOB storage clauses that were
created in the export dump file.