Migration Query

Does one any having list of bottlenecks and workarounds while migrating data
from Oracle to Postgresql. like what are thing which we can migrate from Oracle database to Postgresql and what we can't?

Which is the best tool for migration from Oracle to Postgresql?

Hi,

I like this tool and have used it successfully in the past:

http://ora2pg.darold.net/

Bye,
Chris.

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

On Tue, May 9, 2017 at 1:13 AM, PAWAN SHARMA <er.pawanshr0963@gmail.com>
wrote:

Hi All,

Does one any having list of bottlenecks and workarounds while migrating
data
from Oracle to Postgresql. like what are thing which we can migrate from
Oracle database to Postgresql and what we can't?

In general you must be able to migrate pretty much any data type to
PostgreSQL. It would be good to understand the data-types specifically used
in the to-be-migrated Oracle database and how that would effect Application
functionality/performance after migrating to PostgreSQL.

If you can provide details on the specific data-types used by Oracle, then,
the required information can be provided. As per my experience as far as
data types are concerned, issues generally crop-up around when migrating
large object types. Having said that, PostgreSQL is rich in supporting side
range of data-types.

Which is the best tool for migration from Oracle to Postgresql?

As already suggested, ora2pg is the best open-source tool.

Regards,

Venkata B N
Database Consultant

PAWAN SHARMA schrieb am 08.05.2017 um 17:13:

Does one any having list of bottlenecks and workarounds while migrating data
from Oracle to Postgresql. like what are thing which we can migrate from Oracle database to Postgresql and what we can't?

One thing I have seen regularly is the wrong translation of Oracle's NUMBER data type to the corresponding Postgres type.

e.g. NUMBER(22) is very often translated to a numeric in Postgres but it should be translated to integer or bigint.

numeric is slightly slower and takes more space then integer or bigint.

You also need to think about how you used the DATE data type in Oracle.
If you rely on the time part, you have to translate that into a TIMESTMAP in Postgres.

Thomas

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