Disclaimer

Wednesday, 18 December 2024

xtt.properties - file in rman_xttconvert_VER4.5.zip - Explanation



The file you shared is the xtt.properties file template from Doc ID 2471245.1, designed for configuring the XTTS (Cross-Platform Transportable Tablespace) utility with xttdriver.pl

Below is an explanation of key properties and their usage:


Detailed Explanation of Parameters

Tablespace Configuration

  • tablespaces
    • List the tablespaces to migrate, separated by commas.
    • Use uppercase names, without spaces, and do not include quotes.
    • Example:

tablespaces=USERS,EXAMPLE,MY_DATA_TS



Platform ID

  • platformid
    • arget platform ID obtained from the source database using the query:

SELECT PLATFORM_NAME, PLATFORM_ID FROM V$TRANSPORTABLE_PLATFORM;
platformid=6  # AIX-Based Systems (64-bit)


File Locations

  1. src_scratch_location

    • Temporary directory on the source for incremental backups and datafile copies.
Example:
src_scratch_location=/src_backups/


dest_datafile_location

  • Final location for the converted datafiles in the destination database.
  • Use ASM (e.g., +DATA) if the destination is ASM, or a filesystem path otherwise.
dest_datafile_location=+DATA


dest_scratch_location

  • Temporary directory on the destination for receiving files copied from the source.
dest_scratch_location=/dest_backups/




ASM Configuration (if applicable)

  • asm_home and asm_sid
    • Specify the ASM instance home and SID for the destination.
    • Uncomment and update if the destination uses ASM.
asm_home=/u01/app/19.0.0/grid
asm_sid=+ASM



Parallelism

  1. parallel

    • Number of RMAN channels for the prepare phase and conversion.
    • Default: 8. Example:
parallel=4


rollparallel

  • Parallelism for the roll forward phase during incremental backups.
  • Default: 0 (serial). Example:
rollparallel=2



getfileparallel

  • Parallelism for the -G operation (getting incremental backups).
  • Default: 1. Example
getfileparallel=4



Automatic File Transfer

  • metatransfer

    • Enable automated file transfer between source and destination (requires passwordless SSH).
    • Default: 0. Enable by setting:
metatransfer=1


destuser and desthost

  • Credentials and hostname for the destination when using metatransfer.
destuser=oracle
desthost=target-server

desttmpdir

  • Temporary directory for intermediate files on the destination.
desttmpdir=/tmp


allowstandby

  • Set to 1 if you want to execute the script from a standby database.
allowstandby=1


usermantransport

Mandatory for databases using Oracle 12c or higher.
usermantransport=1



Connection Strings (CDB/PDB Only)

  • srcconnstr and destconnstr
    • Used for migrating pluggable databases (PDBs).
srcconnstr=sys/oracle@cdb1_pdb1
destconnstr=sys/oracle@cdb2_pdb1



Example Configuration
# Tablespaces to transport
tablespaces=USERS,EXAMPLE,MY_DATA_TS

# Source database platform ID
platformid=13

# Source and Destination Scratch Locations
src_scratch_location=/src_backups/
dest_scratch_location=/dest_backups/

# Destination Datafile Location
dest_datafile_location=+DATA

# ASM Configuration
asm_home=/u01/app/19.0.0/grid
asm_sid=+ASM

# Parallelism Configuration
parallel=4
rollparallel=2
getfileparallel=4

# Automatic File Transfer
metatransfer=1
destuser=oracle
desthost=target-server
desttmpdir=/tmp

# Optional Settings
allowstandby=1
usermantransport=1


Checklist for Running XTTS:

  1. Set Up Passwordless SSH (if using metatransfer=1).
  2. Verify Disk Space in src_scratch_location and dest_scratch_location.
  3. Validate Tablespaces with:

EXEC DBMS_TTS.TRANSPORT_SET_CHECK('USERS,EXAMPLE,MY_DATA_TS', TRUE);
SELECT * FROM TRANSPORT_SET_VIOLATIONS;

   4. Perform a Test Run with a small tablespace before migrating all.












No comments:

Post a Comment

How to recovery PDB when PDB database is dropped in Oracle

  How to recovery PDB when PDB database is dropped :) [oracle@rac01 ~]$ sqlplus '/as sysdba' SQL*Plus: Release 21.0.0.0.0 - Product...