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 DirectorTransaction 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