EBS R12的11g库从AIX迁移到Linux不能采用 Cross Platform Incremental Backup 的原因-阿里云开发者社区

开发者社区> 数据库> 正文
登录阅读全文

EBS R12的11g库从AIX迁移到Linux不能采用 Cross Platform Incremental Backup 的原因

简介:

详见红色字体部分,估计是EBS中一些特殊的object不适用这种方式,普通数据库可以采用。所以目前EBS还只能是传统的XTTS (跨平台传输表空间) 及 EXPDP/IMPDP+OGG两种方法 。 

Known Issues and Limitations of XTTS    

  1. Built-in Limitations 
    Built-in limitations are documented in the Oracle Database Administrator's Guide, 11g Release 2 (11.2). One important limitation outlined in this document that is relevant for EBS is that the source and target databases must have the same character set and national character set.
  2. Column Encryption Using TDE 
    Transportable Tablespaces migration is not supported for tables that have columns encrypted using the Transparent Data Encryption (TDE) functionality of Oracle Database 11g (see My Oracle Support Document 732764.1). Tables that have encrypted columns must be de-crypted prior to following the transportable tablespaces migration and then encrypted in the target database after migration.
  3. Mixing RDBMS and EBS Schemas in the same Tablespace 
    The use of RDBMS and EBS Schemas in the same tablespace is not supported as tablespaces with RDBMS schemas are disregarded in the creation of the transportable set. It is recommended that RDBMS schemas (such as CTXSYS) be in separate tablespaces (for example, SYSAUX).
  4. Cross Platform Incremental Backup (跨平台增量备份方式)
    Cross Platform Incremental Backup is not certified to work with an EBS database.

参考Oracle文档   Using Transportable Tablespaces for EBS Release 12.0 or 12.1 Using Database 11gR2 (文档 ID 1311487.1)  

本文转自ITPUB博客tolywang的博客,原文链接:EBS R12的11g库从AIX迁移到Linux不能采用 Cross Platform Incremental Backup 的原因,如需转载请自行联系原博主。

版权声明:本文内容由阿里云实名注册用户自发贡献,版权归原作者所有,阿里云开发者社区不拥有其著作权,亦不承担相应法律责任。具体规则请查看《阿里云开发者社区用户服务协议》和《阿里云开发者社区知识产权保护指引》。如果您发现本社区中有涉嫌抄袭的内容,填写侵权投诉表单进行举报,一经查实,本社区将立刻删除涉嫌侵权内容。

分享:
数据库
使用钉钉扫一扫加入圈子
+ 订阅

分享数据库前沿,解构实战干货,推动数据库技术变革

其他文章