- On the source machine:
- Export the tablespace meta data using export
- % expdp system/<password> DUMPFILE=expdat.dmp DIRECTORY = dpump_dir TRANSPORT_TABLESPACES = <list of tablespaces separated by commas> TRANSPORT_FULL_CHECK=Y
- If the dumpdir is not set up, you will get an ‘invalid’ directory error:
- SQL> CREATE DIRECTORY dmpdir as ‘/somedir’;
- SQL> GRANT read,write on DIRECTORY to system;
- Export the data converting on the fly:
- Determine the platform name for the destination machine:
- SQL> SELECT PLATFORM_ID, PLATFORM_NAME, ENDIAN_FORMAT FROM V$TRANSPORTABLE_PLATFORM
- % rman TARGET /
- RMAN> CONVERT TABLESPACE <list of tablespaces separated by commas> to PLATFORM ‘<platform name from previous step>’ FORMAT=’/somedir/%U’;
- Determine the platform name for the destination machine:
- Put the tablespaces into read/write mode
- SQL> alter tablespace <tablespace> READ WRITE;
- Transfer the files to the destination machine (Setup the dumpdir if you haven’t already)
- Create the oracle user(s) with the same names as on the source oracle (if you don’t you will need to remap the ownership using the REMAP_SCHEMA for the impdb )
- Import the tablespace schema and data (repeat for each tablespace)
- % impdp system/<password> DUMPFILE=expdat.dmp DIRECTORY = dpump_dir TRANSPORT_DATAFILES = <Full path to each tablespace datafile separated by commas>
- Put the tablespaces in to read/write mode
- SQL> alter tablespace <tablespace> READ WRITE;
« How to disable the “uninstall password” to uninstall Symantec Antivirus VMware 2.0.2 running on Win2k3 -> VMware ESX 4.0 .. done :) »



