We are evaluating a possibility of migrating customer database from ORACLE to POSTGRESQL
Customer is using Visual Cobol - PROCobol (Not only (also java, .NET) - but we have around 100000 lines of COBOL).
Is it practicable (reasonable) to migrate it from Oracle ProCOBOL to OpenESQL POSTGRES?
Has anyone tried it, also with other databases?
Any hints?
We are evaluating a possibility of migrating customer database from ORACLE to POSTGRESQL
Customer is using Visual Cobol - PROCobol (Not only (also java, .NET) - but we have around 100000 lines of COBOL).
Is it practicable (reasonable) to migrate it from Oracle ProCOBOL to OpenESQL POSTGRES?
Has anyone tried it, also with other databases?
Any hints?
Nothing is impossible!
Sure, it is possible to migrate database ORACLE to Postgres or other as MSSQL.
There are minimal changes to do on sqlcode, Oracle have allways a Primary key that must not be declared, the access is a little bit others.
What is the reason to change? a) from Oracle
b) to Postgres
only Cost or other?
On wich OS run your application?
100000 code of lines are not heavy, but without see a example from the coding, i can't give more experience.
I have good experience since 20 years with mssql on Windows and now also running on Linux Server !
Nothing is impossible!
Sure, it is possible to migrate database ORACLE to Postgres or other as MSSQL.
There are minimal changes to do on sqlcode, Oracle have allways a Primary key that must not be declared, the access is a little bit others.
What is the reason to change? a) from Oracle
b) to Postgres
only Cost or other?
On wich OS run your application?
100000 code of lines are not heavy, but without see a example from the coding, i can't give more experience.
I have good experience since 20 years with mssql on Windows and now also running on Linux Server !
Thanks for this answer. I know this is "it depends".
I do not know much - it is my customer situation. The reason for postgres migration is cost of oracle (licenses operations).
I am java developer and ... At the moment I look how to "not rewrite" those COBOL programs customer has to java (they just work, risks are high and to avoid cost).
This is linux (on production) as far as I know (I can confirm if it matters).
From my "unexperienced" perspective it looked like possible task. I am now scanning sources for potentially oracle specific features that may not work on postgresql . Actually, I do not know what can that be - just checking while reading sources.
+2Thanks for this answer. I know this is "it depends".
I do not know much - it is my customer situation. The reason for postgres migration is cost of oracle (licenses operations).
I am java developer and ... At the moment I look how to "not rewrite" those COBOL programs customer has to java (they just work, risks are high and to avoid cost).
This is linux (on production) as far as I know (I can confirm if it matters).
From my "unexperienced" perspective it looked like possible task. I am now scanning sources for potentially oracle specific features that may not work on postgresql . Actually, I do not know what can that be - just checking while reading sources.
OpenESQL is based on the ANSI SQL standards and Pro*COBOL contains many Oracle extensions to the standard.
The best way to find out the problem areas is to compile your Pro*COBOL apps using the Pro*COBOL FIPS flag so that it will flag code that does not adhere to the ANSI standard. This normally indicates areas where code changes may be required.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
