From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: Jeremiah Bauer <jbauer@agristats.com>
To: Alicja Kucharczyk <zaledwie10minut@gmail.com>
Cc: pgsql-admin@lists.postgresql.org <pgsql-admin@lists.postgresql.org>
Subject: Re: New Oracle system in our house, migration chances
Date: Thu, 13 Jan 2022 16:08:16 +0200
Message-ID: <8b47579e-0ac6-f813-2069-ea8475de755b@matrix.gatewaynet.com> (raw)
In-Reply-To: <CH2PR19MB35767EBDD32AA992ED9D3F85C2539@CH2PR19MB3576.namprd19.prod.outlook.com>
References: <d57a8b83-9ea4-97e7-4b72-720932d40fc1@matrix.gatewaynet.com>
<CAM=sWa6ydVoznn0EOpy1EhYQAuNgVf36gbUgHk9vijLxoTnOWQ@mail.gmail.com>
<CH2PR19MB35767EBDD32AA992ED9D3F85C2539@CH2PR19MB3576.namprd19.prod.outlook.com>
On 13/1/22 2:45 μ.μ., Jeremiah Bauer wrote:
> czw., 13 sty 2022 o 13:26 Achilleas Mantzios <achill@matrix.gatewaynet.com <mailto:achill@matrix.gatewaynet.com>> napisał(a):
>
> Hi All, HPNY 2022
>
> We acquired a new company, those guys run on Oracle 10, on AIX 5.2, both systems dating to around 2006 or so.
> We would like to increase our chances of recovery in case of disaster, since those are unsupported versions of Oracle/AIX AFAIK.
> The application is written on powerbuilder.
>
> The ppl in the respective IT dept claim they have no exotic SQL inside powerbuilder. I am almost 21 years into PostgreSQL, I have done some MS SQL integration with PostgreSQL but almost no Oracle
> experience since 90's. What are my options here?
>
> A)
> 1) use a tool like ora2pg and try to migrate the schema
> 2) try to load the data
> 3) migrate ORACLE code procedures and triggers (about 50 in total)
> 4) setup and test the app
> or
> B)
> 1) use a layer that provides DB code (procedures/triggers) compatibility and/or DDL compatibility
> 2) use a tool to move/migrate the schema and load data
> 3) setup and test the app
>
> Any hints where to start, technical options, help to evaluate/assess various solutions/costs would be welcome.
>
> I know this has been discussed extensively in PgSQL community, my intention is for this email to provide a platform along with my concurrent/parallel reading on the matter.
>
> Thank you
>
> --
> Achilleas Mantzios
> DBA, Analyst, IT Lead
> IT DEPT
> Dynacom Tankers Mgmt
>
>
> Hi Achilleas,
> I would go with version B - since as I understand it's ISV solution. Meaning the postgres ddl was tested and aligned with the application layer, otherwise you would need to fix app layer after
> the migration.
>
> I agree with Alicja, we have used EnterpriseDB's Oracle compatibility layer to migrate off Oracle in the past.
Thank you Jeremiah.
>
> CONFIDENTIALITY NOTICE: The information contained in this email (and any attachments) is privileged and confidential and protected from disclosure. If you are not the intended recipient of this
> email or the attachments, be aware that any disclosure, copying, distribution or use of this email or any attachment is strictly prohibited and you should not read the message or read or open any
> attachment. If you have received this email by mistake, please immediately notify the sender and delete it permanently from your system. Agri Stats, Inc. and its subsidiaries will not be held liable
> to any person or entity resulting from the unintended or unauthorized use of any information contained in this email.
--
Achilleas Mantzios
DBA, Analyst, IT Lead
IT DEPT
Dynacom Tankers Mgmt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: achill@matrix.gatewaynet.com, jbauer@agristats.com, zaledwie10minut@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: New Oracle system in our house, migration chances
In-Reply-To: <8b47579e-0ac6-f813-2069-ea8475de755b@matrix.gatewaynet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox