xtts 迁移注意

简介: xtts 迁移注意

1,NOTE: Only those database objects that are physically located in the tablespace(s) being transported will be copied to the destination system. Other objects, such as users, pl/sql objects, sequences, views etc., located in the SYSTEM tablespace will not be transported. You will need to pre-create the users and copy such objects to the destination system, possibly using data pump.

Metadata Residing in the SYSTEM or SYSAUX Tablespaces
Database metadata includes views, synonyms, type definitions, database links,
PL/SQL packages, roles, Java classes, privileges, sequences, and other objects.
Running a full database, metadata-only import creates database metadata that is not
automatically created in the target database by the transport process. This will be
accomplished with two separate import processes, as detailed in the following
steps.
SYSTEM-Owned Objects Residing in the SYSTEM or SYSAUX Tablespaces
Some applications create tables and indexes owned by the SYSTEM user that are
required for proper application functionality. To properly identify these objects
requires application-specific knowledge. You must move these objects to the target
database manually with Data Pump, or manually re-create the objects after
performing the platform migration.
User-Owned Tables Residing in the SYSTEM or SYSAUX Tablespaces
Run the following script (provided in the Appendix) to identify user objects that
reside in SYSTEM or SYSAUX:
Handle Objects in the SYSTEM or SYSAUX Tablespaces
Because XTTS does not move objects that reside in the SYSTEM or SYSAUX
tablespaces of the source database, the following conditions warrant special
consideration when transporting a whole database:

NOTE: Only those database objects that are physically located in the tablespace(s) being transported will be copied to the destination system. Other objects, such as users, pl/sql objects, sequences, views etc., located in the SYSTEM tablespace will not be transported. You will need to pre-create the users and copy such objects to the destination system, possibly using data pump.

The following may help:

Oracle Database 12c: Full Transportable Export/Import

and/or

MAA paper Platform Migration Using Transportable Tablespaces: Oracle Database.

目录
打赏
0
9
9
0
104
分享
相关文章
MySQL数据库DTS迁移上云
利用DTS数据迁移工具完成RDS实例间的数据迁移。
【迁移】Mysql数据库备份 迁移
备份数据,新建库,导入数据,恢复备份
94 0
【迁移】Mysql数据库备份 迁移
系统迁移
系统迁移
147 0
数据迁移问题
数据迁移问题
233 0
服务器迁移
本实践以小微客户为例,提供两个场景的迁移验证实践。采用 SMC 模式,一个以阿里云内部迁移举例;一个以他云服务器为例,迁移到华东2(上海)。
服务器迁移
MongoShake全量迁移功能
从v1.5版本开始,MongoShake新增了全量迁移功能,该功能可以让用户更快地对数据量较大的MongoDB数据库做数据复制。MongoShake不再需要源数据库保留全部的oplog,只要依赖当前的oplog就能做数据同步复制。
3561 0
系统迁移基本法
社区评论系统在完成了基础功能建设后,开始逐步将老系统业务迁移到新系统,实现整体架构统一、新系统功能赋能老业务、节省系统维护成本;迁移过程本身虽然枯燥无味,但并不妨碍通用解决方案的沉淀,本文以评论新老系统迁移为背景,聊聊系统迁移的基本方法,同时也希望能抛砖引玉,探索更多迁移方案的可能性。
DTS增量/同步支持DDL迁移的说明
    DTS目前并不支持所有数据库类型时间的DDL迁移,特别是异构数据库之间的迁移.不得不承认DDL的迁移是非常的,因为这涉及到DDL的解析(DDL的过滤)及转换(库表列映射及异构数据库).毕竟DDL是一个高危操作,稍有不慎就肯能造成不可恢复的故障.
3422 0