Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from
	<pgsql-admin-owner+M41011=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1UXuox-0000Ee-AD
	for pgsql-admin@arkaria.postgresql.org; Thu, 02 May 2013 14:49:19 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
	<pgsql-admin-owner+M41011=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
	id 1UXuow-0003V1-PP
	for pgsql-admin@arkaria.postgresql.org; Thu, 02 May 2013 14:49:18 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <vibhor.aim@gmail.com>) id 1UXuow-0003Uw-2B
	for pgsql-admin@postgresql.org; Thu, 02 May 2013 14:49:18 +0000
Received: from mail-qc0-x22e.google.com ([2607:f8b0:400d:c01::22e])
	by makus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <vibhor.aim@gmail.com>) id 1UXuos-0006tE-Tl
	for pgsql-admin@postgresql.org; Thu, 02 May 2013 14:49:17 +0000
Received: by mail-qc0-f174.google.com with SMTP id z24so292059qcq.5
	for <pgsql-admin@postgresql.org>; Thu, 02 May 2013 07:49:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=x-received:content-type:mime-version:subject:from:in-reply-to:date
	:cc:content-transfer-encoding:message-id:references:to:x-mailer;
	bh=sHv/wjBn4Xdft/+cqYPUxtJ+uKI1+Ov6X7SkLCSC80I=;
	b=yku+bOgUoaC4Knko4ADrL2MUSXejsT84PwTHXSiJGI/rqENqYfKYT7GhpnbgLp5gUN
	uFavQeIRamJl0Fro0seURUNawWV4fiI4alxHDrC7Gv8WsOBqBGbaQN/QDgWSUFm8Syvp
	MXHu0m8ML4izBcADdSH6ji2aeBdkA1P4aP2vWp1bn0/YSfUKwnRtTvrl25p5+M/vyAXK
	p03RhHy2U0nHO3AY9/k40bUxJcYQhMjQ3oVI5nyClmOIhJnAv3VtuKpIaPuNRxKZm5fQ
	3oZmyNKciaIEzfr808f6bmutekVI41g1rxEqQnWC7FpYpdOdYw109HPejxYu295xf2sa
	ANbg==
X-Received: by 10.49.28.4 with SMTP id x4mr8936925qeg.39.1367506153787;
	Thu, 02 May 2013 07:49:13 -0700 (PDT)
Received: from [172.24.38.110]
	(70-91-216-177-BusName-NewEngland.hfc.comcastbusiness.net.
	[70.91.216.177])
	by mx.google.com with ESMTPSA id c7sm8740713qel.2.2013.05.02.07.49.12
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Thu, 02 May 2013 07:49:13 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: Migration from Oracle 11g to Postgresql
From: Vibhor Kumar <vibhor.aim@gmail.com>
In-Reply-To: 
 <E8D40D92FF4F29479EA59F839673E63E04EC4D@AZ-US1EXMB02.global.avaya.com>
Date: Thu, 2 May 2013 10:49:15 -0400
Cc: "Paul B. Anderson" <paul.a@pnlassociates.com>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <2CC51A0B-1ED6-475F-BB25-CFDB0D15DF80@gmail.com>
References: 
 <CANwDVowrLpzvgizkz+ene1K21ttX3W_voqTVErt8vyDCnPyU6g@mail.gmail.com>
	<C202FD88-E84A-4DB6-99CB-60B89A4AE1B5@gmail.com>
	<CAP5xjbv8tncUfbx7o4ZCtQNa_RyYdOfAhJfFGM+94HZgV9XSWA@mail.gmail.com>
	<5182787F.1070501@pnlassociates.com>
	<E8D40D92FF4F29479EA59F839673E63E04EC4D@AZ-US1EXMB02.global.avaya.com>
To: "McKinzie, Alan (Alan)" <alanmck@avaya.com>
X-Mailer: Apple Mail (2.1503)
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org


On May 2, 2013, at 10:38 AM, "McKinzie, Alan (Alan)" <alanmck@avaya.com> wr=
ote:

> I used ora2pg a couple years ago.  I made a few minor changes to fit our =
specific requirements, but it worked well for our migration to Postgresql.

Ora2Pg is a good tool for one time migration.=20

However, when we come to crucial production databases where we have least d=
owntime window. Then replicating data from Oracle to PostgreSQL and later d=
oing switchover to postgreSQL (new database) in short window, is the effici=
ent way I have found and I have used xDB Replication most of time, since it=
s easy to configure and provides GUI mode to monitor your replication etc. =
I did many migration from Oracle Production database to PostgreSQL. Getting=
 long downtime window for Production is the main issue I have seen for cruc=
ial customer facing applications.

Thanks & Regards,
Vibhor Kumar
Blogs:http://vibhork.blogspot.com
http://vibhorkumar.wordpress.com



--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin