This illustration shows that the inst1.example.com database and the inst3.example.com database do not share a computer file system. The inst1.example.com database contains two tablespaces: sales_tbs1 and sales_tbs2. The illustration shows a tablespace repository with two versions of this tablespace set: v_q1fy2005 and v_q2fy2005. Other versions can also be added to the tablespace repository. The illustration also shows the directory objects that store the data files, export dump file, and export log file in each version on the computer file system for the inst1.example.com database. The q1fy2005 directory object stores the files for version v_q1fy2005, and the q2fy2005 directory object stores the files for version v_q2fy2005.

Before a version of the tablespace set can be attached to the inst3.example.com database, the data files and export dump file in the version are copied to a directory on the inst3.example.com database's computer file system using the DBMS_FILE_TRANSFER package. The illustration shows the data files and export dump file in the q1fy2005 directory object on inst1.example.com being copied to the q1fy2005 directory object on inst3.example.com. After the tablespace set is attached, the inst3.example.com database contains the sales_tbs1 and sales_tbs2 tablespaces. Also, an import log file generated during the attach is added to the q1fy2005 directory object on inst3.example.com.