Escolar Documentos
Profissional Documentos
Cultura Documentos
Public
The term "upgrade" is used for a major release change, and "update"
is used when applying EHPs over an existing product, when applying
Support Packages or when installing an Add-On.
Preparation
Reviewing database, operating system and SAP system for the upcoming changes
Proactive actions
A considerable number of incidents are worked reactively by customer alongside SAP Support, when software-related errors take place during
the maintenance of SAP systems. We were able to track down and classify these interactions, and the outcome showed an impressive 80% of
all UPG cases that were already documented or were consulting (how-to) requests. Had customers reached the properly knowledge channels of
SAP, most of the incidents would have never existed.
Based on that, SAP Support has developed a series of proactive solutions. This Customer Facing Training focus on examining customer systems
in all relevant aspects for upgrade scenarios, aiming to eliminate know gaps, problems and limitations.
Because the upgrade procedure is such a complex set of tasks that involves almost all ABAP and SAP Java technologies aspects, a direct result
of this investigation will be an optimized and tuned system. Going from the operating system level, through the database and ending up on the
SAP product, we’ll review and suggest on the most common settings
In the end customers might have a considerable gain in SAP technology knowledge that can side effect to all Application areas, fostering
knowledge and ecosystem accountability
2. Setup and configure your database accordingly before starting the upgrade
a) Oracle
b) MSSQL
o 1314750 DB6: DBA Cockpit Correction Collection SAP Basis 7.00 / 7.10
o 1456402 DB6: DBA Cockpit Corrections for SAP Basis 7.02/7.30/7.31
o 1309424 DB6: DBA Cockpit Correction Collection SAP Basis 7.01 / 7.11
o 1312006 DB6: Database Performance Warehouse Master Note
o SAP DB2 document in SCN listing the important notes and documents
d) HANA
Solution Manager
The SUM tool uses a stack XML file generated in MOPZ to determine all dependent packages according to the target version and Support
Package levels. This stack file is mandatory.
1887979: Requirements before opening an incident for MOPZ (update your SolMan following this note before generating the XML file)
1600302: MOpz: Copy stack xml with a report (copy the XML file using this report or generate a new stack file for your next upgrade system)
Oficial SAP MOPZ guide
1981278: Software Update Manager 1.0 SP12 [lmt_008] (last SUM version)
Old SAPup for other upgrade paths: check for the target NW version. 701 (like EhP4), 702 (EhP5) and 711 (PI/XI).
2 or even 3 steps-upgrade is OK
OS level
o Mount the medias on the local directory, avoid network /NFS drives;
o Consider the architecture of your OS: 32 or 64bit and the impact this has on ACT_UPG phase: note #1630256
ABAP checks
o Update SAP kernel to latest patch level stack (not the kernel version!)
o Check if STMS and the background jobs are correctly configured: note #1541076
o Data class missing or misconfigured (KBA #1805195 – tablespaces handling during upgrade)
ABAP checks
Make sure you run this SM65 check when the system is quiet and no other batch jobs are running. You'll have to cancel the
current batch activities as this would put a lock on the TBTCO table till it finishes. This table may be needed by any other batch
job that is running or scheduled to run at the time SM65 checks are running. Customers should also do the TEMSE and spool
consistency checks as per note #48400. Remove inconsistencies if any found.
Introduction
Overview
Import of the substitution set into the shadow tables during production
operation (2nd shadow) enables the following in uptime
SCN-Blog: http://scn.sap.com/docs/DOC-32544
Ramp down
UPG/EHPi
Validation
Ramp up
Backup
Backup
Technical Customer SGEN
Installation Shadow transports
Preparation operation Downtime Add on,...
nZDM:
obsolete
technical
downtime
savings:
Additional runtime: 20-30 % 50 - 60%
Uptime Business Downtime Uptime
nZDM/SUM
Ramp down
Validation
NEW 2nd
Ramp up
Backup
Technical Cust.
Backup
Installation Shadow
shadow Downtime Trsp.
Preparation operation Add on
operation ,...
1:00
18:15 11:15 9:15
2:30 1:00
9:00
2:15
4:00
2:15
schedules
logfiles in
DIR_PUT/log database
datafile
SAPup start
read
tp
start
R3trans
read & write
write import
write
logfiles in database
DIR_PUT/log
logfiles in
DIR_PUT/log
database
© 2015 SAP SE or an SAP affiliate company. All rights reserved. Public 29
Technical overview – bulk import phases control flow
datafile from CD
SAPup start
read
R3load
read & write
import
write
logfiles in database
DIR_PUT/log
2. Could SAPup logon to the SAP system? (Check the .LOG file)
Yes: check #3
No (ie. error during logon): check if DDIC could logon in 000 with the given password.
Did a tool write a error message into its logfile ? (Check the .ELG file)
XPRA or "Report after Put" is an ABAP program or Function Module that is executed during a transport request import sequence,
the import of a Support Package and during Upgrades/Enhancement Package installations.
The reports that are executed during XPRA are application-related conversions, adjustments, data mergers or alignments for the
conversion of release-specific SAP-shipped customizing that need to be adjusted during the upgrade. The runtime of the XPRA phase differs
from one application component to another - however XPRAs are used by all SAP modules and applications.
The XPRA phase reports are run as one of the last steps of the upgrade. However, due to the fact that table content is adjusted,
the XPRA phase needs to behttp://wiki.scn.sap.com/wiki/display/TechTSG/XPRAS+phases
done at application downtime. XPRA can also run as part of the activation of extension sets and IS add-ons.
XPRAs use jobs RDDEXECL, seen in SM37
• SPAU
• Must be run after the 1st system upgrade of the
landscape (usually DEV)
http://wiki.scn.sap.com/wiki/display/TechTSG/XPRAS+phases
• 14-day expire period
Contact information:
Tomas Black
Upgrade Support Engineer
SAP Labs Latin America, São Leopoldo. Brazil
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.
Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche
Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.
SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der
SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Ländern weltweit.
Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://global.sap.com/corporate-de/legal/copyright/index.epx.
Die von SAP SE oder deren Vertriebsfirmen angebotenen Softwareprodukte können Softwarekomponenten auch anderer Softwarehersteller enthalten.
Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschließlich zu Informationszwecken.
Die SAP SE oder ihre Konzernunternehmen übernehmen keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation.
Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen
Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren.
Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehörigen Präsentation dargestellte
Geschäftsabläufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu veröffentlichen. Diese Publikation oder eine zugehörige Präsentation,
die Strategie und etwaige künftige Entwicklungen, Produkte und/oder Plattformen der SAP SE oder ihrer Konzernunternehmen können von der SAP SE oder ihren
Konzernunternehmen jederzeit und ohne Angabe von Gründen unangekündigt geändert werden.
Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder
Funktionen dar. Sämtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatsächlichen Ergebnisse von den
Erwartungen abweichen können. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie getätigt wurden. Dem Leser wird empfohlen,
diesen Aussagen kein übertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen nicht auf sie zu stützen.