Incrementally updating transportable tablespaces using rman Adultchat com au

19 Mar

It utiliuzes RMAN incremental backups to reduce the large amount of downtime it takes to copy and convert the datafiles cross Endianness.

This method is more suitable for smaller or low transaction rate applications.RMAN uses the configured settings, the records of previous backups, and the control file record of the database structure to determine an efficient set of steps for the backup. As explained in "RMAN File Management in a Data Guard Environment", you can run RMAN backups at any database in a Data Guard environment.Any backup of any database in the environment is usable for recovery of any other database if the backup is accessible.We are all aware of the issue surrounding cross platform database migrations.The endian difference between RISC Unix platforms (big endian) versus x86 platforms (little endian) causes a conversion of the data before it is usable by Oracle.When backing up to disk, however, you can specify a format to spread the backup across several drives for improved performance.In this case, allocate one CONFIGURE DEVICE TYPE DISK PARALLELISM 3; CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/disk1/%d_backups/%U'; CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/disk2/%d_backups/%U'; CONFIGURE CHANNEL 3 DEVICE TYPE DISK FORMAT '/disk3/%d_backups/%U'; BACKUP AS COPY DATABASE; User-specified tags are a useful way to indicate the purpose or usage of different classes of backups or copies.As it was POC I left source database working as main production database.For real migration time it's necessary to add time to recover last incremental backup and import TTS on new platform and also resolve issue with time necessary to gather statistics on new platform.As I described in my previous post I had to migrate database from HP-UX into Linux and also upgrade it from 10g into 12c.This time it was only Po C but my goal was to minimize downtime of production database.