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

Managing DB2 transaction logs when upgrading to SAP ECC 6.0

A SearchSAP.com reader wants to know how an increase of indexes and tables after upgrade to SAP ECC 6.0 will affect the memory requirements of a DB2 version 8.x system.

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?

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.

Dig Deeper on SAP Basis

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.