| From: | Vibhor Kumar <vibhor(dot)aim(at)gmail(dot)com> |
|---|---|
| To: | "McKinzie, Alan (Alan)" <alanmck(at)avaya(dot)com> |
| Cc: | "Paul B(dot) Anderson" <paul(dot)a(at)pnlassociates(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Migration from Oracle 11g to Postgresql |
| Date: | 2013-05-02 14:49:15 |
| Message-ID: | 2CC51A0B-1ED6-475F-BB25-CFDB0D15DF80@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On May 2, 2013, at 10:38 AM, "McKinzie, Alan (Alan)" <alanmck(at)avaya(dot)com> wrote:
> 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.
However, when we come to crucial production databases where we have least downtime window. Then replicating data from Oracle to PostgreSQL and later doing switchover to postgreSQL (new database) in short window, is the efficient way I have found and I have used xDB Replication most of time, since its 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 crucial customer facing applications.
Thanks & Regards,
Vibhor Kumar
Blogs:http://vibhork.blogspot.com
http://vibhorkumar.wordpress.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dev Kumkar | 2013-05-02 17:32:13 | Re: Migration from Sybase to Postgresql |
| Previous Message | Dev Kumkar | 2013-05-02 14:42:19 | Migration from Sybase to Postgresql |