Re: Moving 10g database between platforms
Date: Tue, 2 Feb 2010 05:52:03 -0800 (PST)
Message-ID: <af7329c1-ba18-4cb6-b871-ee151c6b47eb_at_36g2000yqu.googlegroups.com>
On Feb 2, 5:19 am, "Bob Jones" <em..._at_me.not> wrote:
> "Vladimir M. Zakharychev" <vladimir.zakharyc..._at_gmail.com> wrote in messagenews:540b0b29-56c9-4091-97e3-d260a0f22315_at_m16g2000yqc.googlegroups.com...
> On Feb 1, 6:55 am, vsevolod afanassiev <vsevolod.afanass..._at_gmail.com>
> wrote:
>
>
>
> > In 10g Oracle introduced ability to use transportable tablespaces to
> > move
> > data between different platforms if endian format is the same:
>
> > PLATFORM_ID PLATFORM_NAME ENDIAN_FORMAT
> > ----------- ------------------------------ --------------
> > 1 Solaris[tm] OE (32-bit) Big
> > 2 Solaris[tm] OE (64-bit) Big
> > 7 Microsoft Windows IA (32-bit) Little
> > 10 Linux IA (32-bit) Little
> > 6 AIX-Based Systems (64-bit) Big
> > 3 HP-UX (64-bit) Big
> > 5 HP Tru64 UNIX Little
> > 4 HP-UX IA (64-bit) Big
> > 11 Linux IA (64-bit) Little
> > 15 HP Open VMS Little
> > 8 Microsoft Windows IA (64-bit) Little
> > 9 IBM zSeries Based Linux Big
> > 13 Linux x86 64-bit Little
> > 16 Apple Mac OS Big
> > 12 Microsoft Windows x86 64-bit Little
> > 17 Solaris Operating System (x86) Little
> > 18 IBM Power Based Linux Big
> > 20 Solaris Operating System (x86- Little
> > 64)
>
> > 19 HP IA Open VMS Little
>
> > So it should be possible to use transportable tablespaces to move data
> > from
> > Sun SPARC Solaris to AIX.
>
> > Question: is it possible to copy entire database including control
> > files,
> > redo logs, SYSTEM and SYSAUX tablespaces?
>
> < Not using TTS. Provided that the endianness is the same, should be no
> < problem simply copying the datafiles and redo logs (their format is
> < the same across all platforms with the same endianness,) but you will
> < most likely need to backup control file to trace on the source system
> < and recreate it on the target system (possibly editing paths to the
> < data files if you relocated them during copy.)
>
> No, even AIX and Solaris/SPARC have the same endianness, you cannot just
> copy the files and expect it to work.
>
Why not? The docs are clear on this:
"When transporting between platforms for which the ENDIAN_FORMAT column is the same, you do not need to use either CONVERT DATAFILE or CONVERT TABLESPACE command to convert the files. You can move or copy the file from the source to the destination with operating system utilities."
When copying the whole database, there are some further restrictions (see below,) but I think this statement applies to SYSTEM and SYSAUX, too. And UNDO is recreateable.
> < You can also try RMAN DUPLICATE command (TFM says that the platform
> < should be the same, but I am not sure if this restriction refers to
> < the hardware and OS platform and is somehow enforced by checking and
> < matching OS and CPU architecture, or duplicating to different hardware/
> < OS combination with the same endianness is actually supported - never
> < tried it myself.)
>
> The hardware and OS platform must be the same. The manual is quite clear on
> that.
The manual says exactly this (including the typo): "Duplication must be done to the same platform as the source datababse". Not quite clear what the term "platform" means in this context. Same OS? Same CPU architecture (but maybe different OS?) Both? The term is not defined anywhere, not even in the Master Glossary.
Anyway, you can CONVERT DATABASE, which allows to duplicate a database to a different platform with the same endianness. TFM says:
"In spite of the fact that the endian formats for the source and destination platform are the same, the datafiles for a transportable database must undergo a conversion process, on either the source or destination host. Unlike transporting tablespaces across platforms, where conversion is not necessary if the endian formats are the same, transporting an entire database requires that certain types of blocks, such as blocks in undo segments, be reformatted to ensure compatibility with the destination platform."
This means: in some cases dumb cold-copy duplication across platforms might not work, so you'd be better off with supported CONVERT DATABASE method if you can't afford extra time for testing if the db you just copied is not screwed up because of some platform-specific issue. So my initial "Not with TTS" was a bit off-base - the TTS mechanism is still used for cross-platform duplication, just in a different way.
Regards,
Vladimir M. Zakharychev
N-Networks, makers of Dynamic PSP(tm)
http://www.dynamicpsp.com
Received on Tue Feb 02 2010 - 07:52:03 CST