Managing DB2 transaction logs when upgrading to SAP ECC 6.0

Managing DB2 transaction logs when upgrading to SAP ECC 6.0

Our company is currently running IBM DB2 version 8.x on Z/OS operating system. Our SAP system is SAP R/3 4.7 x 200 and we are upgrading to SAP ECC 6.0. I have looked in ECC 6.0, and there is an increase of about 80% of DB2 transaction logs.

How will this affect the memory requirements of our DB2 version 8.x system? Will the number of cache statements grow? Are there database buffering requirements?

    Requires Free Membership to View

    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.

The database increases with approximately 50GB to 60GB. SAP strongly recommends using Short Message Service (SMS) to simplify disk space handling. If you do not, make sure that the VTOC and the indexed VTOC are large enough, as many small files are created during the import phases.

Transaction logging cannot be turned off in DB2 for Z/OS. This is unfortunate, as the upgrade generates a huge number of DB2 transaction logs. You seldom need to perform any point-in-time recovery, as the upgrade steps can be repeated or the upgrade can be undone and restarted from scratch without the need of a database recovery. You might therefore consider increasing the number of LOG datasets. Customer experiences show up to 500MB of transaction logging generated during the upgrade.

For performance reasons, change the Workload Manager (WLM) settings so that the SAPGEN and SAP Batch enclaves get high priority. Usually, the SAPGEN and or SAP Batch enclaves are given lower priority than the SAPdiag and/or SAPupdate. Keep in mind that the upgrade does most of the work using the R3trans/R3load process, which creates SAPGEN enclaves.

This was first published in March 2010

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.