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?
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
Related Q&A from Bert Vanstechelman
An SAP user wants to know the risks of changing time zones in ECC 6.0. Continue Reading
An SAP user wants to know how to access an SAP IDES 4.7 system via the Internet through SAP GUI. Continue Reading
A SearchSAP.com reader is upgrading from SAP ECC R/3 4.7 to ECC 6.0 and wants to know if there is a list that identifies which SAP ABAP code is ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.