Slow/Poor Performance While Performing Rman Convert on Source HP Tru64 Platform (Doc ID 1442798.1)

Last updated on OCTOBER 11, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
HP Tru64 UNIX

Symptoms

For a database having to be migrated from HP Tru64 platform , if Automatic Segment Space Management (ASSM) is used then EVERY file containing ASSM segment headers has to be converted , even if the endian format from source to target platform does not change.  This is because the format of ASSM segment headers on Tru64 platforms differs from other unix platforms.    As ASSM is enabled by default from 10G , in practice this means that every datafile has to be converted.

It has been found that running the conversion of the datafiles on the source HP Tru64 platform performs very poorly.  Using an RMAN 10.2.0.5 client,  conversion of 4 datafiles totaling  36GB  took 2 hours and 15 minutes.  Based on this result, it was estimated that a database of 1.6TB would take about 102 hours to convert.

An RMAN COPY of the same 4 files to the same convert location took just 20 mins.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms