Upgrade and migrate options

From: Tony Adolph <tony.adolph.dba_at_gmail.com>
Date: Fri, 26 Jun 2009 11:17:51 +1200
Message-ID: <4a38d9060906251617q4467a7a1m22f4d1d3a4c339b2_at_mail.gmail.com>

Hi Folks,

Environment, VM guests:


Oracle: ** with APEX 3.2 using Embedded PL/SQL Gateway (EPG). No ASM, no RAC
32-bit OS: Suse Linux 10.1 i686 i686 i386 GNU/Linux


Oracle: ** - installed - nothing else 32-bit OS: openSuse 11.1 SMP i686 i686 i386 GNU/Linux


Get the database that's running on source, running on target. Its only small (~500M) and there are no downtime issues as this is a sandpit environment and the exercise purely for training.

I have a couple of ideas for the "best" way to go with this:

Exp/imp (traditional or datapump):

  1. Build empty database on target
  2. [on target] exp or expdb from source (full = y)
  3. copy exp to target (not req'd if exp done on target)
  4. imp full=y
  5. run upgrade scripts or DBUA
  6. configure EPG

This seems the simplest approach (I have seen the recent discussion full=y vs separate schemas)


Not sure about this one.

  1. on source "backup copy copy of database" 1a - hypothetical) IF in production then stop app
  2. copy to target inc archive redo, controlfiles, pfile
  3. on target: set SID and recover database
  4. run upgrade scripts or DBUA
  5. configure EPG


  1. dont have to pre-create empty database on target
  2. possibly quicker than imp / exp (not an issue right now, but always worth investigating for real-world scenarios)

What are you're thoughts list?



http://www.freelists.org/webpage/oracle-l Received on Thu Jun 25 2009 - 18:17:51 CDT

Original text of this message