11G - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup-ID 1389592.1

徐卫

1445

25页

3次

2020-04-24

10墨值下载

2019/3/31 文档 1389592.1
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=18nizyfmfm_118&id=1389592.1 1/25
版权所有 (c) 2019，Oracle。保留所有权利。Oracle 机密。
11G - Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
(文档 ID 1389592.1)
In this Document
 
Purpose
  Traditional Cross Platform Transportable Tablespaces
  Reduce Downtime using Cross Platform Incremental Backup
Scope
Details
  Overview
  Cross Platform Incremental Backup Supporting Scripts
  Requirements and Recommendations
  Prerequisites
  Destination Database 11.2.0.3 or Earlier Requires a Separate Incremental Convert Home and Instance
  Troubleshooting
  Known Issues
  Transport Tablespaces with Reduced Downtime using Cross Platform Incremental Backup
  Conventions Used in This Document
  Phase 1 - Initial Setup
  Step 1.1 - Install the Destination Database Software and Create the Destination Database
  Step 1.2 - If necessary, Configure the Incremental Convert Home and Instance
  Step 1.3 - Identify Tablespaces to be Transported
 
Step 1.4 - If Using dbms_file_transfer Prepare Phase Method, then Configure Directory Objects and
Database Links
  Step 1.5 - Create Staging Areas
  Step 1.6 - Install xttconvert Scripts on the Source System
  Step 1.7 - Configure xtt.properties on the Source System
  Step 1.8 - Copy xttconvert Scripts and xtt.properties to the Destination System
  Step 1.9 - Set TMPDIR
  Phase 2 - Prepare Phase
  Phase 2A - Prepare Phase for dbms_file_transfer Method
  Step 2A.1 - Run the Prepare Step on the Source System
  Step 2A.2 - Transfer the Datafiles to the Destination System
  Phase 2B - Prepare Phase for RMAN Backup Method
  Step 2B.1 - Run the Prepare Step on the Source System
  Step 2B.2 - Transfer Datafile Copies to the Destination System
  Step 2B.3 - Convert the Datafile Copies on the Destination System
  Phase 3 - Roll Forward Phase
  Step 3.1 - Create an Incremental Backup of the Tablespaces being Transported on the Source System
  Step 3.2 - Transfer Incremental Backup to the Destination System
 
Step 3.3 - Convert the Incremental Backup and Apply to the Datafile Copies on the Destination
System
  Step 3.4 - Determine the FROM_SCN for the Next Incremental Backup
  Step 3.5 - Repeat the Roll Forward Phase (Phase 3) or Move to the Transport Phase (Phase 4)

2019/3/31 文档 1389592.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=18nizyfmfm_118&id=1389592.1 2/25

Phase 4 - Transport Phase

Step 4.1 - Make Source Tablespaces READ ONLY in the Source Database

Step 4.2 - Create the Final Incremental Backup, Transfer, Convert, and Apply It to the Destination

Datafiles

Step 4.3 - Import Object Metadata into Destination Database

Step 4.4 - Make the Tablespace(s) READ WRITE in the Destination Database

Step 4.5 - Validate the Transported Data

Phase 5 - Cleanup

Appendix

Description of Perl Script xttdriver.pl Options

Description of Parameters in Configuration File xtt.properties

Known Issue

Known Issues for Cross Platform Transportable Tablespaces XTTS Document 2311677.1

Change History

Discuss Oracle Backup and recovery Topics!

References

APPLIES TO:

Oracle Database Cloud Exadata Service - Version N/A and later

Oracle Database Cloud Service - Version N/A and later

Oracle Database - Enterprise Edition - Version 10.2.0.3 to 12.1.0.2 [Release 10.2 to 12.1]

Oracle Database Cloud Schema Service - Version N/A and later

Oracle Database Exadata Express Cloud Service - Version N/A and later

Linux x86-64

PURPOSE

Consider using the new release of this procedure, version 4. This version has drastically simplified the

steps and procedure. Before proceeding, review:

V4 Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup Note

2471245.1

When using Cross Platform Transportable Tablespaces (XTTS) to migrate data between systems that have

different endian formats, the amount of downtime required can be substantial because it is directly proportional

to the size of the data set being moved. However, combining XTTS with Cross Platform Incremental Backup can

significantly reduce the amount of downtime required to move data between platforms.

Traditional Cross Platform Transportable Tablespaces

The high-level steps in a typical XTTS scenario are the following:

1. Make tablespaces in source database READ ONLY

2. Transfer datafiles to destination system

3. Convert datafiles to destination system endian format

4. Export metadata of objects in the tablespaces from source database using Data Pump

5. Import metadata of objects in the tablespaces into destination database using Data Pump

6. Make tablespaces in destination database READ WRITE

Because the data transported must be made read only at the very start of the procedure, the application that

owns the data is effectively unavailable to users for the entire duration of the procedure. Due to the serial nature

of 25

10墨值下载

关注

评论