Escolar Documentos
Profissional Documentos
Cultura Documentos
Public
Public
Agenda
Customer Facing Trainer introduction
Brief description of the new services and scope of the upgrade preparation
Preparation
Reviewing database, operating system and SAP system for the upcoming changes
Public
Introduction
Introduction
Benefits
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.
Public
Preparation
Preparation
1.
2.
Setup and configure your database accordingly before starting the upgrade
a)
o
o
o
o
o
o
Oracle
1919276:
1171650:
830576:
1431798:
592393:
1738989:
Public
Preparation
b) MSSQL
o
o
o
o
o
o
o
o
o
1744217:
1237682:
1702408:
1986775:
987961:
363018:
1725220:
1558087:
1054852:
Public
Preparation
c) DB6 (DB2 on Unix/Windows)
o
o
o
o
1314750
1456402
1309424
1312006
o SAP DB2 document in SCN listing the important notes and documents
Public
Preparation
d) HANA
o 1732157:
Public
10
Preparation
Solution Manager
Maintenance Optimizer (MOPZ)
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
Public
11
Preparation
SUM upgrade paths
1981278: Software Update Manager 1.0 SP12 [lmt_008] (last SUM version)
2 or even 3 steps-upgrade is OK
Public
12
Preparation
OS level
o Check for space availability on the OS level, especially in /SUM directory;
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
o Set up parallelism in SUM according to note #1616401
o Check note #927637, specially the owners of file sapuxuserchk
o If possible, set the user limits on Unix-like Oss to unlimited
Public
13
Preparation
ABAP checks
o Check for inactive objects in SE80
o Check SM21 and ST22
o Update if SPAM/SAINT tools to the very last version available
o Update SAP kernel to latest patch level stack (not the kernel version!)
o Update the transport tools individually (R3trans and tp)
o Check if STMS and the background jobs are correctly configured: note #1541076
o Check for orphan update processes as per note #1280546
o Data class missing or misconfigured (KBA #1805195 tablespaces handling during upgrade)
Public
14
Preparation
ABAP checks
o Perform consistency checks in SM65:
1.
2.
3.
4.
5.
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.
Public
15
Public
17
Public
18
Import of the substitution set into the shadow tables during production
operation (2nd shadow) enables the following in uptime
Public
19
Ongoing improvements based on customer feedback, e.g. reduction of preprocessing and post-processing phase
SCN-Blog: http://scn.sap.com/docs/DOC-32544
2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
20
Public
21
Business Downtime
SGEN
50 - 60%
Uptime
SGEN
selected AIMs
Customer transports
Main import & conversions
Ramp up
Add on
,...
Uptime
Validation
Technical Cust.
Downtime Trsp.
Backup
NEW 2nd
shadow
operation
Backup
Shadow system
instance is created
in the background
Shadow
operation
Business Downtime
Ramp down
nZDM/SUM
Installation
Preparation
obsolete
nZDM:
technical
downtime
savings:
Ramp up
Customer
transports
Add on,...
Technical
Downtime
Validation
Shadow
operation
Backup
Installation
Preparation
Backup
Ramp down
UPG/EHPi
Uptime
Public
22
4:30
1:00
18:15
11:15
9:00
2:30
4:00
9:15
1:00
2:15
2:15
Public
23
Technical Overview
Technical overview
SUM initiates 4 different actions during an upgrade:
1.
2.
3.
4.
Public
25
main programs
ABAP programs
UI
(admin)
SAPup
tp
starts
R3load
DB
SLC
SAP system
Public
26
SAPup
function module
schedules
job
write
logfiles in
DIR_PUT/log
database
Public
27
datafile
SAPup
start
read
tp
start
R3trans
read & write
import
write
write
logfiles in
DIR_PUT/log
2015 SAP SE or an SAP affiliate company. All rights reserved.
database
Public
28
external programs
SAPup
start
tp
start
sapevt
trigger
RDDIMPDP
write
schedules
logfiles in
DIR_PUT/log
2015 SAP SE or an SAP affiliate company. All rights reserved.
RDD*
database
Public
29
datafile from CD
SAPup
start
read
R3load
read & write
import
write
logfiles in
DIR_PUT/log
2015 SAP SE or an SAP affiliate company. All rights reserved.
database
Public
30
Public
31
Public
32
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.
3. Did the RFC call return successful?
Yes: check #4
No (ie. RFC error):
Check the authorisations for DDIC in 000.
Check the SAP system (SM21, ST11 rfc traces, ST22).
Public
33
Public
34
stdout of tp,
collected error lines from transport logs.
Logfiles of tp :
ULOG...
ALOG<rel>
SLOG<rel>
Logfiles of R3trans :
SAPI*
SAPH*
Public
35
Public
36
Post processing
Public
38
http://wiki.scn.sap.com/wiki/display/TechTSG/XPRAS+phases
14-day expire period
Public
39
Public
40
Public
41
Thank you
Contact information:
Tomas Black
Upgrade Support Engineer
SAP Labs Latin America, So Leopoldo. Brazil
2015 SAP SE or an SAP affiliate company. All rights reserved.
Public
43
Die von SAP SE oder deren Vertriebsfirmen angebotenen Softwareprodukte knnen Softwarekomponenten auch anderer Softwarehersteller enthalten.
Produkte knnen lnderspezifische Unterschiede aufweisen.
Die vorliegenden Unterlagen werden von der SAP SE oder einem SAP-Konzernunternehmen bereitgestellt und dienen ausschlielich zu Informationszwecken.
Die SAP SE oder ihre Konzernunternehmen bernehmen keinerlei Haftung oder Gewhrleistung fr Fehler oder Unvollstndigkeiten in dieser Publikation.
Die SAP SE oder ein SAP-Konzernunternehmen steht lediglich fr Produkte und Dienstleistungen nach der Magabe ein, die in der Vereinbarung ber die jeweiligen
Produkte und Dienstleistungen ausdrcklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zustzliche Garantie zu interpretieren.
Insbesondere sind die SAP SE oder ihre Konzernunternehmen in keiner Weise verpflichtet, in dieser Publikation oder einer zugehrigen Prsentation dargestellte
Geschftsablufe zu verfolgen oder hierin wiedergegebene Funktionen zu entwickeln oder zu verffentlichen. Diese Publikation oder eine zugehrige Prsentation,
die Strategie und etwaige knftige Entwicklungen, Produkte und/oder Plattformen der SAP SE oder ihrer Konzernunternehmen knnen von der SAP SE oder ihren
Konzernunternehmen jederzeit und ohne Angabe von Grnden unangekndigt gendert werden.
Die in dieser Publikation enthaltenen Informationen stellen keine Zusage, kein Versprechen und keine rechtliche Verpflichtung zur Lieferung von Material, Code oder
Funktionen dar. Smtliche vorausschauenden Aussagen unterliegen unterschiedlichen Risiken und Unsicherheiten, durch die die tatschlichen Ergebnisse von den
Erwartungen abweichen knnen. Die vorausschauenden Aussagen geben die Sicht zu dem Zeitpunkt wieder, zu dem sie gettigt wurden. Dem Leser wird empfohlen,
diesen Aussagen kein bertriebenes Vertrauen zu schenken und sich bei Kaufentscheidungen nicht auf sie zu sttzen.
Public
44