Q
Problem solve Get help with specific problems with your technologies, process and projects.

Risks in porting an application

We are porting an application that was originally written using DB2 to Oracle 9i. The timeline is aggressive such that the vendor did not do functional testing on the apllication. Assuming that standard DB2 calls were made in the application, what risks do we face in porting?

We are porting an application that was originally written using DB2 to Oracle 9i. The timeline is aggressive such that the vendor did not do functional testing on the apllication, maintaining that porting affects performance generally and that any errors should surface during the UAT.

Assuming that standard DB2 calls were made in the application, what risks do we face in porting?

The biggest risk in porting between databases is differences in the "dialects" of SQL. Both Oracle and DB2 have non-ANSI extensions to SQL, and if your DB2 application contains SQL extensions that are not recognized by Oracle SQL, you may have to re-write that SQL.

Remember, while both DB2 and Oracle offer "100% ANSI-compliant" SQL, they have a vested interest in making their SQL better than the competition and they both offer non-ANSI features. An excellent example is the Oracle "decode" statement, an extremely useful features not found in DB2 SQL.

I would recommend extracting all SQL from the DB2 application and running it against the Oracle schema. Any syntax errors will point to any troublesome SQL.

Dig Deeper on Oracle and SQL

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close