Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eTeOc-0007Mn-8h for pgsql-admin@arkaria.postgresql.org; Tue, 26 Dec 2017 01:51:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eTeOb-0000HH-LL for pgsql-admin@arkaria.postgresql.org; Tue, 26 Dec 2017 01:51:09 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eTeOb-0000Gy-7w; Tue, 26 Dec 2017 01:51:09 +0000 Received: from mail-qt0-x235.google.com ([2607:f8b0:400d:c0d::235]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eTeOY-0007qe-VZ; Tue, 26 Dec 2017 01:51:08 +0000 Received: by mail-qt0-x235.google.com with SMTP id d4so43738956qtj.5; Mon, 25 Dec 2017 17:51:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ga2KxNT5PueIW9KpkwAQbN7s2JHfgjCDdjafc0CIFbw=; b=s1pPNMjICtQ0LdPn4ajCRDZIRnhiRDjn7Ik1EIJ8OPQdyylnsSaeNGKGti5t1fV0uU xIOhfHM/8+EPZkpb3+TxEdZazSyajAxXTyXuyL+MGII8F36BTsFFnKOM+kCac13MKqeb rpwMgNhHdYFEl2xnuONvWcDE6HgLPixr05CVXmTeZDpnrnGHOiX0tdzm6MbeQAUP1jnN FUOd75ZsRSDrAgRZMD2YTTSg7IEQ9xyDY6XAmO52sa9AKOnmgQLorpQt3xN4dgybPlRv mNOI5y94ztg50RAIsM2v0Qm0DyiqVt+DJQ2DTeRJGWJB0AiRIvuwbuy4WkC5tcUdXtle Z87A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Ga2KxNT5PueIW9KpkwAQbN7s2JHfgjCDdjafc0CIFbw=; b=k2D/WQRtCE4lgYZs0rf/p4xmDmERXbYNjgDMWzo0ispLraMe1yAazG9AZHHYn6OgJB n/Gn+Q0VrlD7aA/mVsTQuUCRRmsD2QQJ+0tvmQc+Lt5+VhfIi0rl4sRbMo0bkO+Hh7tK ik6gzS6pLhpx9eSH17t27ccmQEYV6+hjBwzppdSDW0nHfJP1Q+wHiT+9tncDs6+jmfEs BMUq0JDYUeUopETLqFvsXalvcoC2QwdYrWlLza+TqXOm4Fqr9o2H2NKcDwceoWqTFgAR Jh4DMdP19wpC7CUTduA7HxvZUez10fYIzGkMCfjMy9JyBOZ5UQ/hYnH01Z8djfHShO4G RnoQ== X-Gm-Message-State: AKGB3mKkqPzc2eOlUD9I7xYCDi4afX4cghQeoz9kk/jBoCS80ZD3xkeB udvB37NrCKkRmRVzkxqS5A3m9RHc X-Google-Smtp-Source: ACJfBovoTypWIsC8+QxqOoGn6SjpKt06fUELsiEtbJLaMFFBx05fBvk1rjfud86LQA7d6QqbHK4dGg== X-Received: by 10.200.19.11 with SMTP id e11mr32029727qtj.62.1514253065630; Mon, 25 Dec 2017 17:51:05 -0800 (PST) Received: from [192.168.1.152] (pool-71-179-177-60.bltmmd.fios.verizon.net. [71.179.177.60]) by smtp.gmail.com with ESMTPSA id p65sm18707282qkb.29.2017.12.25.17.51.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 25 Dec 2017 17:51:04 -0800 (PST) Content-Type: multipart/alternative; boundary=Apple-Mail-D6D5CE7A-0471-4764-9DE7-478DDD55D9C0 Mime-Version: 1.0 (1.0) Subject: Re: Oracle to postgres migration From: John Scalia X-Mailer: iPad Mail (15C153) In-Reply-To: Date: Mon, 25 Dec 2017 20:51:04 -0500 Cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org, pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit Message-Id: <7BD67AC6-F903-4A85-8636-2A642537C825@gmail.com> References: To: Azimuddin Mohammed List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Apple-Mail-D6D5CE7A-0471-4764-9DE7-478DDD55D9C0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi, =20 May I first suggest that you first look at some of EnterpriseDB=E2=80=99s te= chnical literature. They have some documents which list what their products a= dd to PostgreSQL to make it more like Oracle. If your firm isn=E2=80=99t doi= ng this just to get out of licensing fees, they would probably be a good opt= ion for you. The basics of a migration is to look at the Oracle schema in or= der to determine which data types you=E2=80=99ll need to convert. Then, you=E2= =80=99ll need to check which stored procedures you already have, and then wh= at you=E2=80=99ll need to turn into PostgreSQL functions. Offhand, I=E2=80=99= d say this isn=E2=80=99t difficult, but it may get very involved. =E2=80=94 Jay Sent from my iPad > On Dec 25, 2017, at 7:30 PM, Azimuddin Mohammed wrote:= >=20 > Hello, > Can anyone guide me through the steps for migration from oracle to postgre= s with config changes required, keeping in mind that neither I am a oracle D= BA not postgres admin >=20 > --=20 >=20 > Regards, > Azim >=20 >=20 > Virus-free. www.avast.com --Apple-Mail-D6D5CE7A-0471-4764-9DE7-478DDD55D9C0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi,
 
May I first sugges= t that you first look at some of EnterpriseDB=E2=80=99s technical literature= . They have some documents which list what their products add to PostgreSQL t= o make it more like Oracle. If your firm isn=E2=80=99t doing this just to ge= t out of licensing fees, they would probably be a good option for you. The b= asics of a migration is to look at the Oracle schema in order to determine w= hich data types you=E2=80=99ll need to convert. Then, you=E2=80=99ll need to= check which stored procedures you already have, and then what you=E2=80=99l= l need to turn into PostgreSQL functions. Offhand, I=E2=80=99d say this isn=E2= =80=99t difficult, but it may get very involved.
=E2=80=94
Jay

Sent from my iPad
On Dec 25, 2017, at 7:30 PM, Azimuddin Mohammed <azimeiu@gmail.com> wrote:

Hello,
Can anyone guide me through the s= teps for migration from oracle to postgres with config changes required, kee= ping in mind that neither I am a oracle DBA not postgres admin

--

Regards,
Azim

= --Apple-Mail-D6D5CE7A-0471-4764-9DE7-478DDD55D9C0--