12C - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup (Doc ID 2005729.1)
APPLIES TO:
Oracle Database - Enterprise Edition - Version 12.1.0.2 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Linux x86-64
Updated 05-Jun-2017 -- Version 3
PURPOSE
V4 Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup Note 2471245.1
This article covers the steps needed to use Cross Platform Transportable Tablespaces (XTTS) with RMAN incremental backups, in a 12c and higher environment, to migrate data between systems that have different endian formats, with the least amount of application down time. 本文介绍了在12c和更高版本的环境中将跨平台传输表空间（XTTS）与RMAN增量备份一起使用所需的步骤，以在具有不同字节序格式的系统之间迁移数据，并减少了应用程序停机时间。
The first step is to copy a full backup from the source to the destination. Then, by using a series of incremental backups, each smaller than the last, the data at the destination system can be brought nearly current with the source system, before any downtime is required. This procedure requires down time only during the final incremental backup, and the meta-data export/import. 第一步是将完整备份从源复制到目标。然后，通过使用一系列增量备份（每个备份增量都小于最后一个备份），可以在不需要任何停机时间之前，将源系统中的数据几乎与源系统中的数据同步。此过程仅在最终增量备份和元数据导出/导入期间需要停机时间。
This document describes the 12c procedures for Cross Platform Incremental Backup. For the 11g procedures, see Note:1389592.1. 本文档介绍了跨平台增量备份的12c步骤。有关11g的过程，请参见 Note:1389592.1
The high-level steps for Cross Platform Incremental Backup are: 跨平台增量备份的高级步骤是
1. Initial setup 初始设置
2. Prepare phase (source data remains online) 准备阶段（源数据保持在线）
- Backup (level=0) of tablespaces to be transported 备份(level=0)要传输的表空间
- Transfer backup and other necessary setup files to destination system 将备份和其他必要的设置文件传输到目标系统
- Restore datafiles on destination system endian format 恢复目标系统字节序格式的数据文件
3. Roll Forward phase (source data remains online - Repeat this phase as many times as necessary to catch destination datafile copies up to source database) 前滚阶段（源数据保持联机状态-重复此阶段多次以捕获目标数据文件副本直至源数据库）
- Create incremental backup on source system 在源系统上创建增量备份
- Transfer incremental backup and other necessary setup files to destination system 将增量备份和其他必要的设置文件传输到目标系统
- Convert incremental backup to destination system endian format and apply the backup to the destination datafile copies 将增量备份转换为目标系统字节序格式，并将备份应用于目标数据文件副本
- Determine next_scn for next incremental backup 确定next_scn用于下一次增量备份
- Repeat steps until ready to transport the tablespace. 重复步骤，直到准备传输表空间为止
4. Transport phase (source data is READ ONLY) 传输阶段（源数据为只读）
- Make tablespaces in source database READ ONLY 使源数据库中的表空间只读
- Repeat the Roll Forward phase one final time 最后一次重复前滚阶段
- This step makes destination datafile copies consistent with source database and generates necessary export. 此步骤使目标数据文件副本与源数据库一致，并生成必要的导出
- Time for this step is significantly shorter than traditional XTTS method when dealing with large data because the incremental backup size is smaller. 处理增量数据时，此步骤所需的时间明显少于传统XTTS方法，因为增量备份大小较小
- Import metadata of objects in the tablespaces into destination database using Data Pump 使用数据泵将表空间中对象的元数据导入到目标数据库中
- Make tablespaces in destination database READ WRITE 使目标数据库中的表空间读写
SCOPE
V4 Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup Note 2471245.1
The source system may be any platform provided the prerequisites referenced and listed below for both platform and database are met. 源系统可以是任何平台，只要满足以下针对平台和数据库所引用和列出的先决条件即可。
If you are migrating from a little endian platform to Oracle Linux, then the migration method that should receive first consideration is Data Guard. See Note 413484.1 for details about heterogeneous platform support for Data Guard between your current little endian platform and Oracle Linux. 如果从小端(little)平台迁移到Oracle Linux，则应首先考虑的迁移方法是Data Guard。 有关当前的小端(little)平台与Oracle Linux之间对Data Guard的异构平台支持的详细信息，请参见 Note 413484.1
DETAILS
V4 Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup Note 2471245.1
Overview 总览
This document provides a procedural example of transporting two tablespaces called TS1 and TS2 from an Oracle Solaris SPARC system to Oracle Linux, incorporating Oracle's Cross Platform Incremental Backup capability to reduce downtime.
本文档提供了一个示例，该示例将两个称为 TS1 和 TS2 的表空间从Oracle Solaris SPARC系统传输到Oracle Linux，并结合了Oracle跨平台增量备份功能以减少停机时间。
After performing the initial setup, moving the data is performed as follows: 执行初始设置后，按以下步骤移动数据：
Prepare 准备
During the prepare phase, a level =0 backup of the tablespaces' datafiles is taken on the source. The backups are transferred to the destination, datafiles are restored and converted to the destination endian format.
在准备阶段，在源上对表空间的数据文件进行 level =0 备份。备份将传输到目标，数据文件将还原并转换为目标字节序格式。
Roll Forward 前滚
During the roll forward phase, the datafiles restored during the prepare phase are rolled forward using incremental backups taken from the source database. By performing this phase multiple times, each successive incremental backup becomes smaller and faster to apply, allowing the data at the destination system to be brought almost current with the source system. The application being migrated is fully accessible during the Roll Forward phase.
在前滚阶段，使用从源数据库获取的增量备份来前滚在准备阶段还原的数据文件。通过多次执行此阶段，每个连续的增量备份将变得更小，更快地应用，从而使目标系统上的数据几乎与源系统保持最新。在前滚阶段，可以完全访问要迁移的应用程序。
Transport 传输
During the transport phase, the tablespaces being transported are put into READ ONLY mode, a final incremental backup is taken from the source database, backups are transferred to destination and applied to the destination datafiles. At this point, the destination datafile copies consistent with source database and the application being migrated cannot receive any further updates. The tablespaces then are TTS-exported from the source database and TTS-imported into the destination database. Finally, the tablespaces are made READ WRITE for full access on the destination database. 在传输阶段，将要传输的表空间置于“只读”模式，从源数据库获取最终的增量备份，将备份转移到目标并应用于目标数据文件。此时，目标数据文件副本与源数据库一致，并且正在迁移的应用程序无法接收任何进一步的更新。然后，将表空间从源数据库导出到TTS，并将TTS导入到目标数据库。最后，将表空间设置为READ WRITE以便对目标数据库进行完全访问
Cross Platform Incremental Backup Supporting Scripts 跨平台增量备份支持脚本
The Cross Platform Incremental Backup core functionality is delivered in Oracle Database 11.2.0.4 and later, for 11g use procedure outlined in Note 1389592.1. The procedures outlined in this note applies to Oracle 12c, 12.1 and later. See the Requirements and Recommendations section for details. In addition, a set of supporting scripts in the file rman_xttconvert_ver2.zip is attached to this document that are used to manage the procedure required to perform XTTS with Cross Platform Incremental Backup in 12c. Oracle Database 11.2.0.4及更高版本中提供了跨平台增量备份核心功能，用于Note 1389592.1中概述的11g使用过程。 本说明中概述的过程适用于Oracle 12c，12.1和更高版本。 有关详细信息，请参见“需求和建议”部分。 此外，此文档还附带了文件 rman_xttconvert_ver2.zip 中的一组支持脚本，这些脚本用于管理在12c中使用跨平台增量备份执行XTTS所需的过程。
The two primary supporting scripts files are the following: 以下是两个主要的支持脚本文件：
- Perl script xttdriver.pl script that is run to perform the main steps of the XTTS with Cross Platform Incremental Backup procedure. 运行Perl脚本xttdriver.pl脚本，以执行带有跨平台增量备份的XTTS的主要步骤
- Parameter file xtt.properties: the file which stores site-specific configuration. 参数文件xtt.properties：用于存储特定于站点的配置的文件。
Prerequisites 先决条件
The following prerequisites must be met before starting this procedure: 开始此过程之前，必须满足以下先决条件：
- The limitations and considerations for transportable tablespaces must still be followed. They are defined in the following manuals: 必须遵循传输表空间的限制和注意事项。它们在以下手册中定义：
- Oracle Database Administrator's Guide
- Oracle Database Utilities
- In addition to the limitations and considerations for transportable tablespaces, the following conditions must be met: 除了传输表空间的限制和注意事项之外，还必须满足以下条件
- The current version does NOT support Windows as either source or destination. 当前版本不支持Windows作为源或目标
- The source database must have its COMPATIBLE parameter set to 12.1.0 or higher. 源数据库必须将其COMPATIBLE参数设置为12.1.0或更高
- The source database's COMPATIBLE parameter must not be greater than the destination database's COMPATIBLE parameter. 源数据库的COMPATIBLE参数不得大于目标数据库的COMPATIBLE参数。
- The source database must be in ARCHIVELOG mode. 源数据库必须处于ARCHIVELOG模式
- RMAN on the source system must not have DEVICE TYPE DISK configured with COMPRESSED. 源系统上的RMAN 不得 将COMICEED配置为DEVICE TYPE DISK
- RMAN on the source system must not have BACKUP TYPE TO COPY. The source must have BACKUP TYPE TO BACKUPSET. 源系统上的RMAN 不得 具有 BACKUP TYPE TO COPY。源必须具有 BACKUP TYPE TO BACKUPSET
- The destination database must have its COMPATIBLE parameter set to 12.1.0 or higher. 目标数据库必须将其COMPATIBLE参数设置为12.1.0或更高
- The set of tablespaces being moved must all be online, and contain no offline data files. Tablespaces must be READ WRITE. Tablespaces that are READ ONLY may be moved with the normal XTTS method. There is no need to incorporate Cross Platform Incremental Backups to move tablespaces that are always READ ONLY. 要移动的表空间集必须全部在线，并且不包含任何离线数据文件。表空间必须是READ WRITE。只读的表空间可以使用普通的XTTS方法移动。无需合并跨平台增量备份来移动始终只读的表空间
- Although preferred destination system is Linux (either 64-bit Oracle Linux or a certified version of RedHat Linux), this procedure can be used with other Unix based operating systems. However, any non-Linux operating system must be on running 12.1.0.1 or higher in both destination and source. 尽管首选的目标系统是Linux（64位Oracle Linux或RedHat Linux的认证版本），但是此过程可以与其他基于Unix的操作系统一起使用。但是，任何非Linux操作系统都必须在目标和源上都运行12.1.0.1或更高版本。
- The Oracle version of source must be lower or equal to destination. Therefore, this procedure can be used as an upgrade method. Restrictions to transportable tablespace will apply. 源的Oracle版本必须低于或等于目标。因此，此过程可以用作升级方法。适用于可移动表空间的限制
- All steps in this procedure are run as the oracle user that is a member of the OSDBA group. OS authentication is used to connect to both the source and destination databases. 此过程中的所有步骤均以作为OSDBA组成员的oracle用户身份运行操作系统身份验证用于连接到源数据库和目标数据库
- It is not supported to execute this procedure against a standby or snapshot standby databases. 不支持对备用数据库或快照备用数据库执行此过程
- This process does not support multitenant databases. However, V4 of this procedure DOES support it, see Note 2471245.1 此过程不支持多租户数据库。但是，此过程的V4确实支持它，请参见 Note 2471245.1
Whole Database Migration 整个数据库迁移
If Cross Platform Incremental Backups will be used to reduce downtime for a whole database migration, then the steps in this document can be combined with the XTTS guidance provided in the MAA paper Platform Migration Using Transportable Tablespaces: Oracle Database. 如果将使用跨平台增量备份来减少整个数据库迁移的停机时间，则可以将本文档中的步骤与MAA论文《使用可迁移表空间的平台迁移：Oracle数据库》中提供的XTTS指导相结合。
Troubleshooting 故障排除
Debug mode enables additional screen output and causes all RMAN executions to be performed with the debug command line option. To enable debug mode, either run xttdriver.pl with the -d flag, or set environment variable XTTDEBUG=1 before running xttdriver.pl. This flag allows for 3 levels, -d [1/2/3] with 3 generating the most information. 调试模式可启用其他屏幕输出，并使用调试命令行选项执行所有RMAN命令。 要启用调试模式，请使用 -d 标志运行 xttdriver.pl ，或者在运行 xttdriver.pl 之前设置环境变量 XTTDEBUG = 1。 该标志允许3个级别，-d [1/2/3]，其中3级别生成最多的信息。
Known Issues 已知问题
- If the roll forward phase (xttdriver.pl -r) fails with the following errors, then verify RMAN DEVICE TYPE DISK is not configured COMPRESSED. 如果前滚阶段（xttdriver.pl -r）失败并出现以下错误，则请验证RMAN DEVICE TYPE DISK是否未配置为COMPRESSED。
Entering RollForward After applySetDataFile Done: applyDataFileTo Done: RestoreSetPiece DECLARE * ERROR at line 1: ORA-19624: operation failed, retry possible ORA-19870: error while restoring backup piece /dbfs_direct/FS1/xtts/incrementals/xtts_incr_backup ORA-19608: /dbfs_direct/FS1/xtts/incrementals/xtts_incr_backup is not a backup piece ORA-19837: invalid blocksize 0 in backup piece header ORA-06512: at "SYS.X$DBMS_BACKUP_RESTORE", line 2338 ORA-06512: at line 40
- If using ASM in both source and destination, see XTTS Creates Alias on Destination when Source and Destination use ASM (Note 2351123.1) 如果在源和目标中都使用ASM，请参阅当源和目标使用ASM时XTTS在目标上创建别名 (Note 2351123.1)
- The existence of a GLOGIN.sql, in either source or destination, can cause syntax errors. 源或目标中存在GLOGIN.sql可能会导致语法错误
Also refer Known Issues for Cross Platform Transportable Tablespaces XTTS Document 2311677.1 for other known issues. 另请参阅跨平台可移动表空间XTTS Document 2311677.1 的已知问题。
Transport Tablespaces with Reduced Downtime using Cross Platform Incremental Backup 使用跨平台增量备份减少停机时间的传输表空间
The XTTS with Cross Platform Incremental Backups procedure is divided into the following four phases: 具有跨平台增量备份的XTTS过程分为以下四个阶段
- Phase 1 - Initial Setup phase 初始设置阶段
- Phase 2 - Prepare phase 准备阶段
- Phase 3 - Roll Forward phase 前滚阶段
- Phase 4 - Final Incremental Backup 最终增量备份
- Phase 5 - Transport Phase: Import Metadata 传输阶段：导入元数据
- Phase 6 - Validate the Transported Data 验证传输的数据
- Phase 7 - Cleanup 清理
Conventions Used in This Document 本文档中使用的约定
- All command examples use bash shell syntax. 所有命令示例都使用bash shell语法
- Commands prefaced by the shell prompt string [oracle@source]$ indicate commands run as the oracle user on the source system. shell提示符字符串 [oracle@source]$ 开头的命令表示命令在源系统上以oracle用户身份运行
- Commands prefaced by the shell prompt string [oracle@dest]$ indicate commands run as the oracle user on the destination system. Shell提示符字符串 [oracle@dest]$ 开头的命令表示命令在目标系统上以oracle用户身份运行
Phase 1 - Initial Setup 初始设置
Perform the following steps to configure the environment to use Cross Platform Incremental Backups: 执行以下步骤以配置环境以使用跨平台增量式备份
Step 1.1 - Install the destination database software and create the destination database 步骤1.1-安装目标数据库软件并创建目标数据库
Install the desired Oracle Database software on the destination system that will run the destination database. This should be an Oracle 12c installation. 在将运行目标数据库的目标系统上安装所需的Oracle数据库软件。这应该是Oracle 12c安装
Identify (or create) a database on the destination system to transport the tablespace(s) into and create the schema users required for the tablespace transport. 在目标系统上标识（或创建）数据库以将表空间传输到表空间中，并创建表空间传输所需的模式用户
Step 1.2 - Identify tablespaces to be transported 步骤1.2-确定要传输的表空间
Identify the tablespace(s) in the source database that will be transported. Tablespaces TS1 and TS2 will be used in the examples in this document. As indicated above, the limitations and considerations for transportable tablespaces must still be followed. 在源数据库中标识将要传输的表空间。表空间TS1和TS2将在本文档的示例中使用。如上所述，对于可移动表空间的限制和注意事项仍然必须遵循
Step 1.3 - Install xttconvert scripts on the source system 步骤1.3-在源系统上安装 xttconvert 脚本
On the source system, as the oracle software owner, download and extract the supporting scripts attached as rman-xttconvert_2.0.zip to this document. 在源系统上，以oracle软件所有者的身份下载并提取作为rman-xttconvert_2.0.zip附加到此文档的支持脚本
[oracle@source]$ pwd /home/oracle/xtt [oracle@source]$ unzip rman_xttconvert_v3.zip Archive: rman_xttconvert_v3.zip inflating: xtt.properties inflating: xttcnvrtbkupdest.sql inflating: xttdbopen.sql inflating: xttdriver.pl inflating: xttprep.tmpl extracting: xttstartupnomount.sql
Step 1.4 - Create necessary directories 步骤1.4-建立必要的目录
- On source:
- Location of backups, as defined by backupformat parameter in the xtt.properties file. 备份的位置，所界定 backupformat 在 xtt.properties 文件参数
- On destination:
- staging areas on the destination systems as defined by the stageondest parameter in the xtt.properties file. 由 xtt.properties 文件中的 stageondest 参数定义的目标系统上的暂存区域
- location for datafiles on destination, as defined storageondest parameter in the xtt.properties file. 数据文件在目标位置的位置，如 xtt.properties 文件中定义的 storageondest 参数
Step 1.5 - Configure xtt.properties on the source system 步骤1.5-在源系统上配置 xtt.properties
Edit the xtt.properties file on the source system with your site-specific configuration. For more information about the parameters in the xtt.properties file, refer to the Description of Parameters in Configuration File xtt.properties section in the Appendix below. For this procedure, only the following parameters are mandatory. Others are optional and/or available for backup compatibility can be ignored. 使用特定于站点的配置在源系统上编辑 xtt.properties 文件。有关 xtt.properties 文件中的参数的更多信息，请参考下面附录中的配置文件xtt.properties中的参数说明。对于此过程，仅以下参数是必需的。其他是可选的和/或可用于备份兼容性，可以忽略
-
- tablespaces 表空间
- platformid 平台编号
- backupformat 备份格式
- stageondest
- storageondest
Step 1.6 - Copy xttconvert scripts and xtt.properties to the destination system< 步骤1.6-将 xttconvert 脚本和 xtt.properties 复制到目标系统
As the oracle software owner copy all xttconvert scripts and the modified xtt.properties file to the destination system. 作为oracle软件所有者，将所有 xttconvert 脚本和修改后的 xtt.properties 文件复制到目标系统
[oracle@source]$ scp -r /home/oracle/xtt oracle@dest:/home/oracle/xtt
Step 1.7 - Set TMPDIR environment variable 步骤1.7-设置 TMPDIR 环境变量
In the shell environment on both source and destination systems, set environment variable TMPDIR to the location where the supporting scripts exist. Use this shell to run the Perl script xttdriver.pl as shown in the steps below. If TMPDIR is not set, output files are created in and input files are expected to be in /tmp. 在源系统和目标系统上的Shell环境中，将环境变量TMPDIR设置为支持脚本所在的位置。使用shell运行Perl脚本 xttdriver.pl，如下步骤所示。如果未设置TMPDIR，则会在/ tmp中创建输出文件，并且输入文件应位于/ tmp中
[oracle@source]$ export TMPDIR=/home/oracle/xtt [oracle@dest]$ export TMPDIR=/home/oracle/xtt
Phase 2 - Prepare Phase 准备阶段
During the Prepare phase, datafiles of the tablespaces to be transported are backed up on source, backups transferred to the destination system and restored by the xttdriver.pl script. 在“准备”阶段，要传输的表空间的数据文件在源上备份，备份转移到目标系统，并由xttdriver.pl 脚本还原
11G - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup (Doc ID 1389592.1).
Step 2.1 - Run the backup on the source system 步骤2.1-在源系统上运行备份
On the source system, logged in as the oracle user with the environment (ORACLE_HOME and ORACLE_SID environment variables) pointing to the source database, run the backup as follows: 在源系统上，以oracle用户身份登录并使用指向源数据库的环境（ORACLE_HOME和ORACLE_SID环境变量），运行备份，如下所示
[oracle@source]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl --backup
Step 2.2 - Transfer the following files to the destination system: 步骤2.2-将以下文件传输到目标系统
- Backups created from source backupformat to destination stageondest 从源备份格式创建备份 到目标 阶段
In the example below, scp is used to transfer the level=0 backup created by the previous step from the source system to the destination system. 在下面的示例中， scp 用于将上一步创建的level = 0备份从源系统传输到目标系统
[oracle@source]$ scp /backupformat/* oracle@dest:/stageondest
The following from source $TMPDIR to destination $TMPDIR: 从源$ TMPDIR到目标$ TMPDIR的以下内容
tsbkupmap.txtxttnewdatafiles.txt
Step 2.3 - Restore the datafiles on the destination system 步骤2.3-在目标系统上还原数据文件
On the destination system, logged in as the oracle user with the environment (ORACLE_HOME and ORACLE_SID environment variables) pointing to the destination database, run the restore as follows: 在目标系统上，以oracle用户身份登录，并使用指向目标 数据库的环境（ORACLE_HOME和ORACLE_SID环境变量）来运行还原，如下所示
[oracle@dest]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl --restoreDatafiles will be placed on the destination system in the defined storageondest. 数据文件将以已定义的存储方式放置在目标系统上
Phase 3 - Roll Forward Phase 前滚阶段
During this phase an incremental backup is created from the source database, transferred to the destination system, converted to the destination system endian format, then applied to the converted destination datafile copies to roll them forward. This phase may be run multiple times. Each successive incremental backup should take less time than the prior incremental backup, and will bring the destination datafile copies more current with the source database. The data being transported (source) is fully accessible during this phase. 在此阶段，将从源数据库创建增量备份，将其备份到目标系统，转换为目标系统字节序格式，然后将其应用于转换后的目标数据文件副本以将其前滚。此阶段可以运行多次。每次连续的增量备份应该比以前的增量备份花费更少的时间，并且将使目标数据文件副本与源数据库的副本更新。在此阶段，可以完全访问要传输的数据（源）
Step 3.1 - Create an incremental backup of the tablespaces being transported on the source system 步骤3.1-创建源系统上正在传输的表空间的增量备份
On the source system, logged in as the oracle user with the environment (ORACLE_HOME and ORACLE_SID environment variables) pointing to the source database, run the create incremental step as follows: 在源系统上，以oracle用户身份登录并使用指向源数据库的环境（ORACLE_HOME和ORACLE_SID环境变量），运行创建增量步骤，如下所示
[oracle@source]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl --bkpincThis step will create an incremental backup for all tablespaces listed in xtt.properties. It creates the following files which must always be moved to the destination along with the backup files: 此步骤将为xtt.properties中列出的所有表空间创建增量备份。它创建以下文件，这些文件必须始终与备份文件一起移动到目标位置：
- xttplan.txt
- tsbkupmap.txt
- incrbackups.txt
Step 3.2 - Transfer incremental backup to the destination system 步骤3.2-将增量备份转移到目标系统
Transfer the incremental backup(s) along with other necessary setup files created during the previous step to the stageondest location on the destination system. The list of incremental backup files to copy are found in the incrbackups.txt file on the source system. 将增量备份以及在上一步中创建的其他必要的安装文件转移到目标系统上最重要的位置。在源系统上的incrbackups.txt文件中找到要复制的增量备份文件的列表
[oracle@source]$ scp `cat incrbackups.txt` oracle@dest:/stageondest [oracle@source]$ scp xttplan.txt oracle@dest:/home/oracle/xtt [oracle@source]$ scp tsbkupmap.txt oracle@dest:/home/oracle/xtt [oracle@source]$ scp incrbackups.txt oracle@dest:/home/oracle/xttIf the backupformat location on the source system and the stageondest location on the destination system refer to the same NFS storage location, then the backups do not need to be copied as they are available in the expected location on the destination system. 如果backupformat源系统和上位置stageondest在目标系统上的位置指的是同一NFS存储位置，则不需要备份，因为它们是在目标系统上的预期位置可被复制
However, the rest of the files (xttplan.txt, tsbkupmap.txt, incrbackups.txt) MUST be copied after EACH incremental backup as their contents change after step 3.4. 但是，其余文件（xttplan.txt，tsbkupmap.txt，incrbackups.txt）必须在每次增量备份后复制，因为它们的内容在步骤3.4之后会更改
Step 3.3 - Apply the incremental backup to the datafile copies on the destination system 步骤3.3-将增量备份应用于目标系统上的数据文件副本
On the destination system, logged in as the oracle user with the environment (ORACLE_HOME and ORACLE_SID environment variables) pointing to the destination database, run the roll forward datafiles step as follows: 在目标系统上，以oracle用户身份使用指向目标数据库的环境（ORACLE_HOME和ORACLE_SID环境变量）登录，运行前滚数据文件步骤，如下所示
[oracle@dest]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl --recoverThe roll forward step connects to destination database and applies the incremental backups on the tablespaces' datafiles for each tablespace being transported. 前滚步骤连接到目标数据库，并对要传输的每个表空间在表空间的数据文件上应用增量备份
Note that you must copy the xttplan.txt and tsbkupmap.txt files each time that this step is executed, because their content is different each iteration. 请注意，每次执行此步骤时，都必须复制xttplan.txt和tsbkupmap.txt文件，因为它们的内容在每次迭代中都是不同的
Step 3.4 - Determine the FROM_SCN for the next incremental backup 步骤3.4-确定下一个增量备份的FROM_SCN
For subsequent incremental backups, on the source system, logged in as the oracle user with the environment (ORACLE_HOME and ORACLE_SID environment variables) pointing to the source database, run the determine new FROM_SCN step as follows: 对于后续的增量备份，在源系统上以oracle用户身份使用指向源数据库的环境（ORACLE_HOME和ORACLE_SID环境变量）登录，然后运行确定新的FROM_SCN步骤
The determine new FROM_SCN step calculates the next FROM_SCN, records it in the file xttplan.txt, then uses that SCN when the next incremental backup is created in step 3.1. 确定新的FROM_SCN步骤将计算下一个FROM_SCN，将其记录在文件xttplan.txt中，然后在步骤3.1中创建下一个增量备份时使用该SCN[oracle@source]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl -s
Step 3.5 - Repeat the roll forward phase 3 (3.1 - 3.4) or proceed to phase 4, final incremental backup 步骤3.5-重复前滚阶段3（3.1-3.4）或进行到阶段4，最后进行增量备份
At this point there are two choices: 此时有两种选择
- If you need to bring the files at the destination database closer in sync with the production system, then repeat the Roll Forward phase, starting with step 3.1. 如果需要使目标数据库中的文件与生产系统更接近，请从步骤3.1开始重复前滚阶段
- If the files at the destination database are as close as desired to the source database, then proceed to the Transport phase. 如果目标数据库上的文件与源数据库尽可能接近，则进入传输阶段
NOTE: If a datafile is added to one a tablespace since last incremental backup and/or a new tablespace name is added to the xtt.properties, the following will appear: 注意：如果将数据文件自上次增量备份以来已添加到一个表空间中，并且/或者将新的表空间名称添加到了xtt.properties中，则会显示以下内容
Error:
------
The incremental backup was not taken as a datafile has been added to the tablespace:Please Do the following: 请执行以下操作
--------------------------
1. Copy fixnewdf.txt from source to destination temp dir 将fixnewdf.txt从源复制到目标temp目录2. Copy backups:
<backup list>
from <source location> to the <stage_dest> in destination3. On Destination（目标）, run $ORACLE_HOME/perl/bin/perl xttdriver.pl --fixnewdf
4. Re-execute the incremental backup in source: 在源段中重新执行增量备份
$ORACLE_HOME/perl/bin/perl xttdriver.pl --bkpincrNOTE: Before running incremental backup, delete FAILED in source temp dir or run xttdriver.pl with -L option:
注意：在运行增量备份之前，请在源临时目录中删除FAILED或使用-L选项运行xttdriver.pl：$ORACLE_HOME/perl/bin/perl xttdriver.pl -L --bkpincr
These instructions must be followed exactly as listed. The next incremental backup will include the new datafile. 必须严格按照列出的指示进行操作。下一个增量备份将包括新的数据文件
Phase 4 - Final Incremental Backup 最终增量备份
During this phase the source data is made READ ONLY and the destination datafiles are made consistent with the source database by creating and applying a final incremental backup. After the destination datafiles are made consistent, the normal transportable tablespace steps are performed to export object metadata from the source database and import it into the destination database. The data being transported is accessible only in READ ONLY mode until the end of this phase. 在此阶段，通过创建并应用最终增量备份，使源数据成为只读状态，并使目标数据文件与源数据库一致。在使目标数据文件一致之后，执行常规的可移动表空间步骤以从源数据库导出对象元数据并将其导入到目标数据库中。在此阶段结束之前，只能在“只读”模式下访问正在传输的数据
Step 4.1 - Alter source tablespace(s) READ ONLY in the source database 步骤4.1-更改源数据库中的源表空间（只读）
On the source system, logged in as the oracle user with the environment (ORACLE_HOME and ORACLE_SID environment variables) pointing to the source database, alter the tablespaces being transported to READ ONLY. 在源系统上，以oracle用户身份登录并使用指向源数据库的环境（ORACLE_HOME和ORACLE_SID环境变量），将要传输的表空间更改为“只读”
system@source/prod SQL> alter tablespace TS1 read only; Tablespace altered. system@source/prod SQL> alter tablespace TS2 read only; Tablespace altered.
Step 4.2 - Create the final incremental backup and export file for transfer to the destination 步骤4.2-创建最终的增量备份和导出文件以传输到目标
The final incremental backup is created with the "--bkpexport" option, then transferred to the destination. 使用“ --bkpexport”选项创建最终的增量备份，然后将其转移到目标位置。
[oracle@source]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl --bkpexport [oracle@source]$ scp `cat incrbackups.txt` oracle@dest:/stageondest [oracle@source]$ scp xttplan.txt oracle@dest:/home/oracle/xtt [oracle@source]$ scp tsbkupmap.txt oracle@dest:/home/oracle/xtt [oracle@source]$ scp incrbackups.txt oracle@dest:/home/oracle/xtt
Step 4.3 - Apply last incremental backup to destination datafiles 步骤4.3-将最后一个增量备份应用于目标数据文件
The final incremental backup must be applied to the destination datafiles using "--resincrdmp" 最终增量备份必须使用“ --resincrdmp”应用于目标数据文件
[oracle@dest]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl --resincrdmp
This step will apply the last incremental backup to the datafiles. In addition, it will restore the dump file for phase5A and a script file, xttplugin.txt, containing the syntax. 此步骤将最后一次增量备份应用于数据文件。另外，它将恢复phase5A的转储文件和包含语法的脚本文件xttplugin.txt
Phase 5 - Transport Phase: Import Object Metadata into Destination Database 阶段5-传输阶段：将对象元数据导入目标数据库
During this phase the tablespaces are plugged into the destination database. There are two options. The first is to import locally using the dump file created by step 4.3. The second would be to run the import with a network link between the two databases. 在此阶段，表空间被插入到目标数据库中。有两种选择。第一种是使用步骤4.3创建的转储文件在本地导入。第二种方法是使用两个数据库之间的网络链接运行导入。
Step 5A - Import existing dump file. 步骤5A-导入现有的转储文件
Step 5A.1 - Create datapump directory and grant privilege: 步骤5A.1-创建数据泵目录并授予特权
Datapump will look for the export file in the specified directory. Either copy the '.dmp' file in your existing data pump directory or create a new directory pointing to the or copy the '.dmp' in an existing datapump directory Datapump将在指定目录中查找导出文件。在现有数据泵目录中复制“ .dmp”文件，或者创建指向该目录的新目录，或者在现有数据泵目录中复制“ .dmp”
SYS@DESTDB> create directory dpump_tts as '/home/oracle/destination/convert';
The directory must be granted to use who will do the import: 必须授予目录使用谁来执行导入
SYS@DESTDB> GRANT READ, WRITE ON DIRECTORY dpump_tts TO system;
Step 5A.2 Modify and execute impdp command: 步骤5A.2修改并执行impdp命令
To perform the tablespace transport with this command, then you must edit the import command file xttplugin.txt (generated in step 4.3) and replace import parameters DIRECTORY with site-specific values. 要使用此命令执行表空间传输，则必须编辑导入命令文件xttplugin.txt（在步骤4.3中生成），并将导入参数DIRECTORY替换为特定于站点的值。
The following is an example transportable import command using existing dump file: 以下是使用现有转储文件的示例可移植导入命令
[oracle@dest]$ impdp system/<password> directory=dpump_tts > logfile=tts_imp.log > dumpfile=impdp3925_641.dmp > transport_datafiles='/u01/oradata/DESTDB/o1_mf_ts1_bngv18vm_.dbf','/u01/oradata/DESTDB/o1_mf_ts2_bngv229g_.dbf'
Step 5B - Import using network link. 步骤5B-使用网络链接导入
If you prefer, you can run the metadata import into destination using a network link to the source destination. This can be accomplished by executing the following steps: 如果愿意，可以使用到源目标的网络链接将元数据导入到目标。这可以通过执行以下步骤来完成
Step 5B.1 - Generate new xttplugin.txt for network import 步骤5B.1-生成新的xttplugin.txt以进行网络导入
On the destination system, logged in as the oracle user with the environment (ORACLE_HOME and ORACLE_SID environment variables) pointing to the destination database, run the generate Data Pump TTS command step as follows: 在目标系统上，以oracle用户身份使用指向目标数据库的环境（ORACLE_HOME和ORACLE_SID环境变量）登录，运行generate Data Pump TTS命令步骤，如下所示
[oracle@dest]$ $ORACLE_HOME/perl/bin/perl xttdriver.pl -e
This will generate a sample Data Pump network_link transportable import command in the file xttplugin.txt with the transportable tablespaces parameters TRANSPORT_TABLESPACES and TRANSPORT_DATAFILES correctly set. In addition, a datapump export file will also be created. 这将在文件xttplugin.txt中生成一个示例数据泵network_link transportable import命令，其中 正确设置了可传输表空间参数TRANSPORT_TABLESPACES和TRANSPORT_DATAFILES。此外，还将创建一个数据泵导出文件。
Step 5B.2 - Create a database link on destination database: 步骤5B.2-在目标数据库上创建数据库链接：
Connecting to the destination database, create a database link connecting to the source database. For example: 连接到目标数据库，创建一个连接到源数据库的数据库链接。例如
SQL@dest> create public database link ttslink connect to system identified by <password> using '<tns_to_source>';
Verify the database link can properly access the source system: 验证数据库链接可以正确访问源系统
SQL@dest> select name from v$database@ttslink;
Step 5B.3 - Modify and execute Impdp command: 步骤5B.3-修改并执行Impdp命令
A separate export or dump file is not required. To perform the tablespace transport with this command, then you must edit the import command file xttplugin.txt (generated in step 5B.1) and replace import parameters DIRECTORY, LOGFILE, and NETWORK_LINK with site-specific values. 不需要单独的导出或转储文件。要使用此命令执行表空间传输，则必须编辑导入命令文件xttplugin.txt（在步骤5B.1中生成），并将导入参数DIRECTORY，LOGFILE和NETWORK_LINK替换为特定于站点的值
The following is an example network mode transportable import command: 以下是示例网络模式可传输导入命令
[oracle@dest]$ impdp directory=DATA_PUMP_DIR logfile=tts_imp.log network_link=ttslink transport_full_check=no transport_tablespaces=TS1,TS2 transport_datafiles='+DATA/prod/datafile/ts1.285.771686721', '+DATA/prod/datafile/ts2.286.771686723', '+DATA/prod/datafile/ts2.287.771686743'
Resources:
Phase 6 - Validate the Transported Data 验证传输的数据
Step 6.1 Check tablespaces for corruption 步骤6.1检查表空间是否损坏
At this step, the transported data is READ ONLY in the destination database. Perform application specific validation to verify the transported data. 在此步骤中，已传输的数据在目标数据库中为只读。执行特定于应用程序的验证以验证传输的数据
Also, run RMAN to check for physical and logical block corruption by running VALIDATE TABLESPACE as follows: 另外，通过运行VALIDATE TABLESPACE，运行RMAN来检查物理和逻辑块损坏，如下所示
RMAN> validate tablespace TS1, TS2 check logical;
Step 6.2 - Alter the tablespace(s) READ WRITE in the destination database 步骤6.2-更改目标数据库中的表空间的READ WRITE
The final step is to make the destination tablespace(s) READ WRITE in the destination database. 最后一步是使目标表空间在目标数据库中为READ WRITE。
system@dest/prod SQL> alter tablespace TS1 read write; Tablespace altered. system@dest/prod SQL> alter tablespace TS2 read write; Tablespace altered.
Phase 7 - Cleanup 清理
If a separate incremental convert home and instance were created for the migration, then the instance may be shutdown and the software removed. 如果为迁移创建了单独的增量转换主目录和实例，则可以关闭该实例并删除软件。
Files created by this process are no longer required and may now be removed. They include the following: 通过此过程创建的文件不再需要，现在可以删除。其中包括：
- backupformat location on the source system backupformat在源系统上的位置
- stageondest location on the destination system 目标系统上最重要的位置
- $TMPDIR location in both source and destination systems $ TMPDIR在源系统和目标系统中的位置
Appendix 附录
Description of Perl Script xttdriver.pl Options Perl脚本xttdriver.pl选项的描述
The following table describes the options available for the main supporting script xttdriver.pl. 下表描述了主要支持脚本xttdriver.pl可用的选项。
| Option | Description |
|---|---|
| --backup |
Creates a level 0 backups of the datafiles belonging to the selected tablespaces. These backups will be written into the location pointed to by the xtt.properties variable “backupformat”. These backups need to be copied over to the destination to the location pointed to by the variable “stageondest”. Two more files, tsbkupmap.txt and xttnewdatafiles.txt, will be generated which also need to be copied over to the temporary directory in the destination, defined by TMPDIR. 创建属于所选表空间的数据文件的0级备份。这些备份将被写入xtt.properties变量“ backupformat”指向的位置。这些备份需要复制到目标变量“ stageondest”所指向的位置。 还将生成另外两个文件tsbkupmap.txt和xttnewdatafiles.txt，这些文件也需要复制到目标的临时目录中，该目录由TMPDIR定义。 |
| --restore |
Restores and converts the datafiles from the backups copied to the location “stageondest” in destination. The restored files will be placed in the path defined by the variable “storageondest”. 从复制到目标中“ stageondest”位置的备份还原并转换数据文件。恢复的文件将放置在变量“ storageondest”定义的路径中。 |
| --bkpincr |
Will take an incremental backup and place backups in the path defined by the variable “ backupformat” on the source. It will also create “incrbackups.txt” which contains a list of backups created. This file, along with “tsbkupmap.txt” must be copied to the destination’s “stageondest”. 将进行增量备份，并将备份放在源上变量“ backupformat”定义的路径中。它还将创建“ incrbackups.txt”， 其中包含创建的备份列表。该文件以及“ tsbkupmap.txt”必须复制到目标的“ stageondest”。 |
| --recover |
The –recover will apply the incremental backup on the already created datafiles on the destination. –recover将增量备份应用于目标上已创建的数据文件。 |
| -s |
Determine new FROM_SCN step is run one or more times with the environment (ORACLE_HOME and ORACLE_SID) set to the source database. 确定新的FROM_SCN步骤在环境（ORACLE_HOME和ORACLE_SID）设置为源数据库的情况下运行了一次或多次。 It reports the mapping of the new FROM_SCN to wall clock time to indicate how far behind the changes in the next incremental backup will be. 此步骤计算下一个FROM_SCN，将其记录在文件xttplan.txt中，然后在步骤3.1中创建下一个增量备份时使用该SCN。 它报告新的FROM_SCN到挂钟时间的映射，以指示下一个增量备份中的更改将落后多远。 |
| --bkpexport |
Will perform the last incremental backup and also create the dump file that can be used for importing the datafiles. The incremental backups will be present in “backupformat” location and can be obtained from the file “incrbackups.txt”. Also the file “tsbkupmap.txt” will be generated which needs to be copied over to the destination. 将执行最后的增量备份，并创建可用于导入数据文件的转储文件。增量备份将出现在“ backupformat”位置，并且可以从文件“ incrbackups.txt”获得。 另外，将生成文件“ tsbkupmap.txt”，需要将其复制到目标位置 |
| --resincrdmp |
Will recover the last incremental backup and apply it on the datafile. Also the dump file will be restored to the location pointed to by the temporary directory “TMPDIR” (passed through command line or set in the environment). This dump file can be used during the importing 将恢复上一个增量备份并将其应用于数据文件。另外，转储文件将还原到临时目录“ TMPDIR”指向的位置（通过命令行或在环境中设置）。此转储文件可以在导入期间使用 |
| -e |
Generates Data Pump TTS command step is run once on the destination system with the environment (ORACLE_HOME and ORACLE_SID) set to the destination database. 在将环境（ORACLE_HOME和ORACLE_SID）设置为目标数据库的目标系统上，一次运行Generates Data Pump TTS命令步骤。 network_link to import metadata of objects that are in the tablespaces being transported. 此步骤创建数据泵导入命令的模板，该命令使用network_link导入要传输的表空间中的对象的元数据。 |
| -d debug |
Enables debug mode for xttdriver.pl and RMAN commands it executes. Debug mode can also be enabled by setting environment variable XTTDEBUG=1. Debug allows for 1,2,3 levels of debug. I.e., xttdriver.pl -d 3 为xttdriver.pl及其执行的RMAN命令启用调试模式。也可以通过设置环境变量XTTDEBUG = 1来启用调试模式。调试允许进行1,2,3级调试。即xttdriver.pl -d 3 |
Description of Parameters in Configuration File xtt.properties 配置文件xtt.properties中的参数说明
The following table describes the parameters used by xttdriver.pl which must be defined in the xtt.properties file that are needed for this 12c procedure. Other parameters may exist which are needed for backward compatibility. 下表描述了xttdriver.pl使用的参数，此参数必须在xtt.properties文件中定义，此参数是12c过程所必需的。可能存在向后兼容所需的其他参数
| Parameter | Description | Example Setting |
|---|---|---|
| tablespaces |
Comma-separated list of tablespaces to transport from source database to destination database. Must be a single line, any subsequent lines will not be read. 从源数据库传输到目标数据库的表空间的逗号分隔列表。必须为一行，任何后续行都不会被读取。 |
tablespaces=TS1,TS2 |
| platformid |
Source database platform id, obtained from V$DATABASE.PLATFORM_ID. 从V $ DATABASE.PLATFORM_ID获得的源数据库平台ID。 |
platformid=2 |
| storageondest |
Directory object in the destination database that defines where the destination datafiles will be created. 目标数据库中的目录对象，用于定义将在何处创建目标数据文件 |
storageondest=DESTDIR i.e.: storageondest=+DATA |
| backupformat |
Location on the source system where backups are created. 在源系统上创建备份的位置 all subsequent incremental backups created for one iteration through the process documented above. 该位置必须有足够的可用空间来保存表空间数据文件的level = 0备份以及通过上述文档过程为一次迭代创建的所有后续增量备份。 in which case it should reference the same NFS location as the stageondest parameter for the destination system. 此位置可能是与目标系统共享的NFS挂载文件系统，在这种情况下，它应该引用与目标系统的stageondest参数相同的NFS位置 |
backupformat=/stage_source |
| stageondest |
Location on the destination system where backups are placed by the user when they are transferred manually from the source system. 从源系统手动传输备份时，用户放置备份的目标系统上的位置。 此位置必须有足够的可用空间来容纳级别= 0的备份以及从源传输的所有后续增量备份。 该位置可能是安装DBFS的文件系统。 in which case it should reference the same NFS location as the backupformat parameters for the source system. See Note 359515.1 for mount option guidelines. 该位置可能是与源系统共享的NFS挂载文件系统，在这种情况下，它应引用与源系统的backupformat参数相同的NFS位置。 有关安装选项的准则，请参见注释359515.1。 |
stageondest=/stage_dest |
| asm_home |
ORACLE_HOME for the ASM instance that runs on the destination system.在目标系统上运行的ASM实例的ORACLE_HOME。 注意：如果backupondest设置为文件系统位置，则注释掉asm_home和asm_sid。 |
asm_home=/u01/app/11.2.0.4/grid |
| asm_sid |
ORACLE_SID for the ASM instance that runs on the destination system. 在目标系统上运行的ASM实例的ORACLE_SID。 |
asm_sid=+ASM1 |
| parallel |
Defines the degree of parallelism used in the backup on the source (--backup). 定义源备份（--backup）中使用的并行度。 |
parallel=3 |
Change History
| Change | Date |
|---|---|
|
rman-xttconvert_2.0.zip released - add support for multiple source and destination directories 添加对多个源目录和目标目录的 添加对添加的数据文件的支持 |
20-May-2015 |
REFERENCES
NOTE:1389592.1 - 11G - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
BUG:18596700 - CHANGE TRACKING IS NOT USED DURING INCREMENTAL BACKUP FOR READ ONLY TBS
NOTE:2311677.1 - Known Issues for Cross Platform Transportable Tablespaces XTTS
BUG:17866999 - ORA-1499 FOR CLUSTER FOLLOWING RMAN CONVERT
NOTE:2013271.1 - 12c How Perform Cross-Platform Database Transport to different Endian Platform with RMAN Backup Sets
BUG:28309542 - LFI-00005 LFI-01007 XTTDRIVER.PL --RESTORE