XTTS_V4.1.pdf - 墨天轮文档

XTTS_V4.1.pdf

dm3052

797

16页

41次

2021-08-20

免费下载

2021/8/19
Document 2471245.1
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=156g335fya_187&id=2471245.1
1/16
Copyright (c) 2021, Oracle. All rights reserved. Oracle Confidential.
V4 Reduce Transportable Tablespace Downtime using Cross Platform Incremental Backup
(Doc ID 2471245.1)
In this Document
Purpose
Scope
Details
    
 
NOTE:  Before proceeding with this procedure, review the following notes to understand all the
restrictions and issues associated with the transportable tablespace feature (TTS). All such
restrictions/limitations of TTS apply.
  Overview
  Cross Platform Incremental Backup Supporting Scripts
  Prerequisites
  Troubleshooting
  Known Issues
  V4 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 - Identify tablespaces to be transported
  Step 1.3 - Install xttconvert scripts on the source system
  Step 1.4 - Create necessary directories
  Step 1.5 - Configure xtt.properties on the source system
  Step 1.6 - Copy xttconvert scripts and xtt.properties to the destination system<
  Step 1.7 - Set TMPDIR environment variable
  Phase 2 - Prepare Phase
  Step 2.1 - Run the backup on the source system
  Step 2.2 - Transfer the following files to the destination system:
  Step 2.3 - Restore the datafiles 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 backups and res.txt to the destination system
  Step 3.3 - Apply the incremental backup to the datafile copies on the destination system
  Step 3.4 - Repeat the roll forward phase 3 (3.1 - 3.3) or proceed to phase 4, final incremental backup
 
Phase 4 - Final Incremental Backup  -- If you are running 12c or higher, this step can be replaced by Phase 4 in
Note 2005729.1:
  Step 4.1 - Alter source tablespace(s) to READ ONLY in the source database
  Step 4.2 - Create the final incremental backup of the tablespaces being transported on the source system:
  Step 4.3- Transfer incremental backups and res.txt to the destination system
  Step 4.4 - Apply last incremental backup to destination datafiles
  Phase 5 - Transport Phase:  Import Object Metadata into Destination Database
  OPTION #1.  Manually running export and import command.
  Option1.A:  Run datapump export on source database:
 
Option1.B:  Transfer the export file to destination directory used by datapump
Option1.C:  Run datapump import on destination to plug in the tablespaces.  For example:

2021/8/19

Document 2471245.1

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=156g335fya_187&id=2471245.1

2/16

OPTION #2. Import across sqlnet.

Option2.A: Create datapump directory and grant privilege:

Option2.B: Generate new xttplugin.txt for network import

Option2.C: Create a database link on destination database:

Option2.D: Modify and execute Impdp command:

Step 6.1 Check tablespaces for corruption

Step 6.2 - Alter the tablespace(s) READ WRITE in the destination database

Phase 7 - Cleanup

Appendix

Description of Perl Script xttdriver.pl Options

Description of Parameters in Configuration File xtt.properties

Change History

References

APPLIES TO:

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

Oracle Database Backup Service - Version N/A and later

Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later

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

Oracle Database Cloud Service - Version N/A and later

Linux x86-64

Updated 09-Nov-2018 -- Version 4

PURPOSE

This article covers the steps needed to use V4 Cross Platform Transportable Tablespaces (XTTS) with RMAN incremental

backups to migrate data between systems that have different endian formats, with the least amount of application down

time.

The first step will be 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 V4 procedures for Cross Platform Incremental Backup which can be used with 11.2.0.4 and

higher. This new procedure is simplified version of previous XTTs versions. This version has the following differences:

this procedure uses simplified commands. One command (--backup) for the source and one command (--restore)

for the destination.

this procedure works for multi-tenant environment, including transporting tablespace from non-CDB to CDB or visa

versa. TTS restrictions may apply.

this procedure requires only one file to be copied between the source's and destination's $TMPDIR (res.txt).

this procedure will automatically resolve added datafiles with no additional intervention.

this procedure allows for multiple incremental backups taken off the source without running the recovery. After

which, recovery will be of all the incremental backups in the destination at once.

NOTE: There are a reported issues with multiple incremental backup recovery and large number of datafiles. The

recover command creation may cause backups to not be found (ORA-19625) and/or the recovery attempts to apply

the backups in the wrong order resulting in:

ORA-19638: file /<path>/<datafile name> is not current enough to apply this incremental backup

ORA-19642: start SCN of incremental backup is <scn>

ORA-19641: backup datafile checkpoint is SCN <scn> time MM/DD/YYYY HH:MM:SS

ORA-19640: datafile checkpoint is SCN <scn> time MM/DD/YYYY HH:MM:SS

of 16

免费下载

跨平台xtts_v4

关注

评论