Five tips for SAP R/3 ECC6 Upgrade
Tuesday, July 8th, 20081. The Cost of Logging
Some of you may already know that you can’t turn off [transaction] logging in db2 for z/os. Turning off transaction logging is an important part of the ECC upgrade process, and for good reason, since the upgrade process eats up a huge number of logs, and you seldom need to perform any kind of point in time recovery since the upgrade program can rerun each step.
In the SAP SERVICE MARKETPLACE you can find some information on the upgrade procedure’s requirements from the various servers and databases. Note 815203 will even tell you how much free space you require. But I haven’t found an official document that addresses the logins issue, so I guess there isn’t one. Anyway, what I’m trying to say is that my recent experience shows that upgrade from ECC5 to ECC6 generates around 500MB of transaction log data, and if you use dual logging it will add up to 1TB of data, so be prepared.
2. Profile Parameter Issues
a. Save your [old] instance and default profiles before the upgrade.
b. Save your [old] instance and default profiles before the upgrade.
c. Save your [old] instance and default profiles before the upgrade.
d. Save your [old] instance and default profiles before the upgrade.
e. Review the new profiles, make sure you haven’t lost important non-standard parameters, also note that some of the memory related parameters have changed, they are given default values , and this is probably not optimal for your system.
f. Review the shadow instance profile before the upgrade. At the very least consider adding the following parameters to it :
dbs/db2/use_wlm=1
dbs/db2/use_accounting = 1
(more…)
Popularity: 26% [?]