Incrementally updating transportable tablespaces using rman dating marriage countries submissive women

In, the incremental backup method was introduced which reduces the tablespace read-only downtime.As users can reduce down time using this feature it is suitable for large databases.Probably copy existing stats using PL/SQL will be solution there but it has to be check in next phase.

incrementally updating transportable tablespaces using rman-44

Incrementally updating transportable tablespaces using rman dating asp id

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.

Lets see how this works by transporting a tablespace from Oracle Linux to Oracle Solaris.

select banner from v$version; BANNER -------------------------------------------------------------------------------- Oracle Database 12c Enterprise Edition Release - 64bit Production PL/SQL Release - Production CORE Production TNS for Linux: Version - Production NLSRTL Version - Production select platform_id, platform_name, endian_format 2 from v$transportable_platform order by platform_id; PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT ----------- -------------------------------------------------- -------------- 1 Solaris[tm] OE (32-bit) Big 2 Solaris[tm] OE (64-bit) Big 3 HP-UX (64-bit) Big 4 HP-UX IA (64-bit) Big 5 HP Tru64 UNIX Little 6 AIX-Based Systems (64-bit) Big 7 Microsoft Windows IA (32-bit) Little 8 Microsoft Windows IA (64-bit) Little 9 IBM z Series Based Linux Big 10 Linux IA (32-bit) Little 11 Linux IA (64-bit) Little 12 Microsoft Windows x86 64-bit Little 13 Linux x86 64-bit Little 15 HP Open VMS Little 16 Apple Mac OS Big 17 Solaris Operating System (x86) Little 18 IBM Power Based Linux Big 19 HP IA Open VMS Little 20 Solaris Operating System (x86-64) Little 21 Apple Mac OS (x86-64) Little All we have to do to transport tablespace(s) using the new functionality is create a so called transportable backupset on the source database and restore it on the destination database.

The tablespace should be in read-only mode during the process and only image copies are used.

This method is more suitable for smaller or low transaction rate applications.

The advantage of the RMAN statements is that backupsets are used instead of datafile copies.

Just a quick note to point a MOS note which I found out yesterday .

All of the restrictions that apply to transportable tablespaces apply here also, such as the need to ensure that all of the objects being transported are completely contained within the set of tablespaces being transported.

Cross-platform transportable tablespace can be performed between platforms that have the same, or different, endian format.

See new features around SYSBACKUP, pluggable databases, and the SQL interface covered in Part 1 – Oracle Database 12c – RMAN New Features: Part 1 See new features around backups, file recovery, snapshots, and duplication covered in Part 2 – Oracle Database 12c – RMAN New Features: Part 2 In this article I will cover: Cross-platform transportable tablespace and database were introduced in Oracle 10g.

Tags: , ,