How to Move or Copy a Tablespace to Another Database【每日一译】--2012-11-03

To move or copy a set of tablespaces, you must make the tablespaces read only, copy

the datafiles of these tablespaces, and use export/import to move the database

information (metadata) stored in the data dictionary. Both the datafiles and the

metadata export file must be copied to the target database. The transport of these files

can be done using any facility for copying flat files, such as the operating system

copying facility, ftp, or publishing on CDs.

移动或者COPY表空间集合，你必须让表空间为只读，COPY表空间的数据文件，并且使用

EXP/IMP去移动存储在数据字典的的数据库元数据信息。数据文件和元数据导出文件必须COPY

到目标数据库。这些文件的传输的完成可以使用任何COPY平面文件的工具，就像OS的COPY工具

，FTP或者通过CD将数据出版。

After copying the datafiles and importing the metadata, you can optionally put the

tablespaces in read/write mode.

当你COPY数据文件并且导入元数据后，你可以将表空间设为READ/WRITE模式。

The first time a tablespace’s datafiles are opened under Oracle Database with the

COMPATIBLE initialization parameter set to 10 or higher, each file identifies the

platform to which it belongs. These files have identical on disk formats for file header

blocks, which are used for file identification and verification. Read only and offline

files get the compatibility advanced after they are made read/write or are brought

online. This implies that tablespaces that are read only prior to Oracle Database 10g

must be made read/write at least once before they can use the cross platform

transportable feature.

在数据库使用COMPATIBLE初始化参数设为10或更高版本中第一次表空间的数据文件

被打开的时候，每次文件识别它属于的平台。这些文件拥有在磁盘上相同格式对于文件头块来

说，它们用于文件的识别和验证。只读和离线获得的兼容性一致当它们被设为读/写或者

属于联机状态时。这也就意味着表空间对于10G来说在只读阶段必须被设为READ/WRITE至少

一次在它们可以在交错平台上使用传输功能时。

Note: In a database with a locally managed SYSTEM tablespace,

dictionary tablespaces cannot be created. It is possible to plug in a

dictionary managed tablespace using the transportable feature, but it

cannot be made writable.

备注：在一个使用本地管理的SYSTEM表空间，数据字典表空间不能被创建的，这可以

插入到一个数据字典管理的表空间使用传输功能，但它不能被设为可写；