How to upgrade DB2 on SAP R/3 4.7
We have SAP R/3 4.7 with IBM DB2 Fix Pack 6 and the database administrator wants to upgrade the database version to Fix Pack 16. This is going to be done in our DEV and QAS environment before the PRD environment.

Could I do a transport change request from DEV to PRD during the test stage even though the database version of both environments are different? While the change is taking place, I'm also investigating to see if our SAP R/3 4.7 is compatible with DB2 Fix Pack 16.

    Requires Free Membership to View

    Login

    When you register, you will start receiving targeted emails from my award-winning team of editorial writers. Our goal is to keep you informed on the hottest topics and biggest challenges faced by SAP professionals today.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchSAP.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSAP.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

SAP code is database- and OS-independent. It is perfectly possible to do this, and is supported to run your development and quality assurance system on SQL Server/Windows and your production system on Oracle/AIX. This is inevitable during an OS/DB migration in which the development and quality assurance has already been migrated, and production not.

As such, upgrading DB2 on the development and quality assurance system, while leaving DB2 on the production system in the old version, should be no problem.

One exception: You should be careful if you use EXEC SQL in your own ABAP code. EXEC SQL can be used to call SQL code directly. SQL code is always database-dependent, although, different database versions might respond slightly differently.

This was first published in January 2009