4. 使用网络导出导入 network_link 的限制条件
Restrictions
-- When the NETWORK_LINK parameter is used in conjunction with the TABLES parameter, only whole tables can be imported (not partitions of tables).
--The Import NETWORK_LINK parameter is not supported for tables containing SecureFiles that have ContentType set or that are currently stored outside of the SecureFiles segment through Oracle Database File System Links.
--Network imports do not support the use of evolved types.
--Network imports do not support LONG columns.
--When operating across a network link, Data Pump requires that the source and target databases differ by no more than two versions. For example, if one database is Oracle Database 12c, then the other database must be 12c, 11g, or 10g. Note that Data Pump checks only the major version number (for example, 10g,11g, 12c), not specific release numbers (for example, 12.1,10.1, 10.2, 11.1, or 11.2).
--If the USERID that is executing the import job has the DATAPUMP_IMP_FULL_DATABASE role on the target database, then that user must also have the DATAPUMP_EXP_FULL_DATABASE role on the source database.
--The only types of database links supported by Data Pump Import are: public, fixed user, and connected user. Current-user database links are not supported.
--Network mode import does not use parallel query (PQ) slaves. See "Using PARALLEL During a Network Mode Import".
--When transporting a database over the network using full transportable import, tables with LONG or LONG RAW columns that reside in administrative tablespaces (such as SYSTEM or SYSAUX) are not supported.
--When transporting a database over the network using full transportable import, auditing cannot be enabled for tables stored in an administrative tablespace (such as SYSTEM and SYSAUX) if the audit trail information itself is stored in a user-defined tablespace.
5. 使用 @ 与使用 network_link 的区别 。
使用类似 expdp xxx/xxx@remote_tns 及使用 expdp xxx/xxx network_link= 方式的区别在于执行端不同，生成的文件所在位置不同。
Restrictions
-- When the NETWORK_LINK parameter is used in conjunction with the TABLES parameter, only whole tables can be imported (not partitions of tables).
--The Import NETWORK_LINK parameter is not supported for tables containing SecureFiles that have ContentType set or that are currently stored outside of the SecureFiles segment through Oracle Database File System Links.
--Network imports do not support the use of evolved types.
--Network imports do not support LONG columns.
--When operating across a network link, Data Pump requires that the source and target databases differ by no more than two versions. For example, if one database is Oracle Database 12c, then the other database must be 12c, 11g, or 10g. Note that Data Pump checks only the major version number (for example, 10g,11g, 12c), not specific release numbers (for example, 12.1,10.1, 10.2, 11.1, or 11.2).
--If the USERID that is executing the import job has the DATAPUMP_IMP_FULL_DATABASE role on the target database, then that user must also have the DATAPUMP_EXP_FULL_DATABASE role on the source database.
--The only types of database links supported by Data Pump Import are: public, fixed user, and connected user. Current-user database links are not supported.
--Network mode import does not use parallel query (PQ) slaves. See "Using PARALLEL During a Network Mode Import".
--When transporting a database over the network using full transportable import, tables with LONG or LONG RAW columns that reside in administrative tablespaces (such as SYSTEM or SYSAUX) are not supported.
--When transporting a database over the network using full transportable import, auditing cannot be enabled for tables stored in an administrative tablespace (such as SYSTEM and SYSAUX) if the audit trail information itself is stored in a user-defined tablespace.
5. 使用 @ 与使用 network_link 的区别 。
使用类似 expdp xxx/xxx@remote_tns 及使用 expdp xxx/xxx network_link= 方式的区别在于执行端不同，生成的文件所在位置不同。
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/35489/viewspace-1420537/，如需转载，请注明出处，否则将追究法律责任。
转载于:http://blog.itpub.net/35489/viewspace-1420537/
306
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
