Sie sind auf Seite 1von 44

Upgrade Preparation Session

As part of the Customer Facing Training project


Tomas Black/SAP Services and Support
March, 2015

Public

Customer Facing Trainer


A SAP Support service initiative

Public

This presentation intends to train SAP customers who are about to


upgrade or update their systems, helping to avoid the most common
problems registered in SAP Support services.
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.
The content included on this document express the latest information
processed by SAP Support services, as per its date stamp.
Content accuracy is assured as much as possible.

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

The SUM tool


Context, usage, news, nZDM

Technical Overview and troubleshooting


Concepts of the different actions initiated by SUM and how to analyze errors

Post processing activities


XPRAs phase runtime and SPAU adjustments.

2015 SAP SE or an SAP affiliate company. All rights reserved.

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.

System Optimization and Tuning


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, well 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
2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

Preparation

Preparation

The preparation for an upgrade require many actions:

1.

Check PAM for the OS x HW x SAP product combinations

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:

Performance issues when running a SAP Upgrade (general note)


Automated Oracle DB parameter check (run the attached scripts to identify missing or faulty parameters)
Parameter recommendations for Oracle 10g
Oracle 11.2.0: Database Parameter Settings
FAQ: Oracle
Upgrade/Support Package import hang due to INACTIVE wait event "SQL*Net break/reset client" in Oracle

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

Preparation
b) MSSQL
o
o
o
o
o
o
o
o
o

1744217:
1237682:
1702408:
1986775:
987961:
363018:
1725220:
1558087:
1054852:

MSSQL: Improving the database performance


Configuration Parameters for SQL Server 2008
Configuration Parameters for SQL Server 2012
Configuration Parameters for SQL Server 2014
FAQ: SQL Server I/O performance
File management for SQL Server
New Trace Flags set and recommended with SQL Server 2012
SQL Server Statistics Maintenance
Recommendations for migrations using Microsoft SQL Server

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

Preparation
c) DB6 (DB2 on Unix/Windows)
o
o
o
o

1314750
1456402
1309424
1312006

DB6: DBA Cockpit Correction Collection SAP Basis 7.00 / 7.10


DB6: DBA Cockpit Corrections for SAP Basis 7.02/7.30/7.31
DB6: DBA Cockpit Correction Collection SAP Basis 7.01 / 7.11
DB6: Database Performance Warehouse Master Note

o SAP DB2 document in SCN listing the important notes and documents

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

Preparation
d) HANA
o 1732157:

Collecting diagnosis information for SAP HANA

o SAP SCN Hana and In-Memory Computing troubleshooting document

2015 SAP SE or an SAP affiliate company. All rights reserved.

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

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

11

Preparation
SUM upgrade paths
1981278: Software Update Manager 1.0 SP12 [lmt_008] (last SUM version)

SUM usage paths for SP12 PDF


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

2015 SAP SE or an SAP affiliate company. All rights reserved.

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

2015 SAP SE or an SAP affiliate company. All rights reserved.

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)

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

14

Preparation
ABAP checks
o Perform consistency checks in SM65:
1.
2.
3.
4.
5.

Run Transaction SM65


Select Goto ... Additional tests
Select "Consistency check DB Tables" and click execute.
Once you get the results check to see if you have any inconsistencies in any of your tables.
If there are any inconsistencies reported then run the "Background Processing Analyses" (SM65 .. Goto ... Additional Tests) again. This time check both the
"Consistency check DB Tables" and the Remove Inconsistencies" option.
6. Run this a couple of times until all inconsistencies are removed from the tables.

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.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

15

The SUM tool

The SUM tool


Introduction
Overview
Difference between SUM and SUM with DMO
New SUM GUI
Advanced options and the
Near Zero Downtime (nZDM) option

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

17

Configuration to influence downtime

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

18

SUM in advanced pre-configuration to optimize the downtime

Parallel operation of production system and shadow system

Import of the substitution set into the shadow tables during production
operation (2nd shadow) enables the following in uptime

2015 SAP SE or an SAP affiliate company. All rights reserved.

Execute selected time consuming After Import Methods (AIMs)

Activation ABAP loads (SGEN)

Import selected customer transports (available on request, see note


1759080)

near-Zero Downtime Maintenance (nZDM)

Ongoing process improvements, e.g. faster log scanning or optimize main


import (TABIM-UPG)

Public

19

Quick facts nZDM


near-Zero Downtime Maintenance capability (nZDM) to minimize the business downtime
significantly in Advanced Configuration
Unrestricted available after a period of controlled delivery

Introduction of "Record & Replay" technique for business transactions based


on database trigger technology

Minimizes manual effort: all steps run automatically in background

Minimal additional hardware requirements due to shadow-technique, only


additional DB space needed (80 350 GB)

Is available for all ABAP-based Business Suite products

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

How to activate nZDM in SUM

Chose number of processes for change


recording replication (CRR)

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

21

nZDM: Standard procedure vs. downtime procedure in SUM


Uptime

Business Downtime
SGEN

50 - 60%

Additional runtime: 20-30 %

Uptime

2015 SAP SE or an SAP affiliate company. All rights reserved.

SGEN
selected AIMs
Customer transports
Main import & conversions

Record and replication


of changed tables

Ramp up

Add on
,...

Uptime
Validation

Downtime steps now in uptime:

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

SGEN not needed


anymore

Public

22

Maintenance downtime improvements already realized


reference customer example
1:00

4:30

1:00

18:15

11:15
9:00

2:30

4:00

9:15
1:00

2:15
2:15

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

23

Technical Overview

Technical overview
SUM initiates 4 different actions during an upgrade:

1.

run ABAP programs

2.

triggers background jobs

3.

starts DB import actions via tp and R3trans

4.

loads data from DVDs via R3load

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

25

Technical overview main picture


user interface

main programs

User interaction &


SAPup output

ABAP programs

UI
(admin)

SAPup

tools used during upgrade

tp
starts

R3load

DB

SLC

SAP system

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

26

Technical overview job phases: control flow


external programs

within SAP system


RFC

SAPup

function module
schedules

read & write

job
write

logfiles in
DIR_PUT/log

2015 SAP SE or an SAP affiliate company. All rights reserved.

database
Public

27

Technical overview transport phases control flow

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

Technical overview transport phases control flow (ACT, XPRA)


jobs
within SAP
system

external programs

SAPup

start

tp

start

sapevt
trigger

RDDIMPDP
write
schedules

read & write


write

logfiles in
DIR_PUT/log
2015 SAP SE or an SAP affiliate company. All rights reserved.

RDD*

database
Public

29

Technical overview bulk import phases control flow

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

Technical overview troubleshooting


Main log file: SAPupConsole.log
<open zip file>

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

31

Technical overview logfiles of job phases


During a JOB phase the following kind of logfiles are written :
<name>.LOG
RFC login, start and check of a backgroundjob <name>
<name>.<SID>
where <name> is not a transport logfile can be the logfile of a background job
<name>.ELG
error collected from the previous log
<name>.SAV
.LOG and .ELG from previous runs

Example for phase PARCONV_UPG :


PDDIT020.LOG
RFC logon
ADDBIND.PR2
logfile of backgroundjob JOB_RDDIT020
PDDIT020.ELG
condensed errors from ADDBIND.PR2
(PDDIT020.SAV) .LOG and .ELG from previous runs.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

32

Technical overview logfiles of job phases: troubleshooting


1. Does SAPup finish with errors found in logfile?
No: check #2
Yes: check the .ELG and the logfile of the backgound job.

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).

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

33

Technical overview logfiles of job phases: troubleshooting


4. Did the job finish sucessful (SM37)?
Yes: nothing to do.
No:
Find the corresponding work process (button Job Details)
Check the corresponding dev_w* file in ST11 or on the OS level, directory /work

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

34

Technical overview logfiles of transport phases: logfiles


SAPup calls tp with a special transport profile (TPPARAM).
Logfiles of SAPup :
TP.ECO or SAPup.ECO
*.ELG

stdout of tp,
collected error lines from transport logs.

Logfiles of tp :
ULOG...
ALOG<rel>
SLOG<rel>

Tp call inclusive used transport profile,


finished steps (request, returncode),
details of tp call.

Logfiles of R3trans :
SAPI*
SAPH*

(main) import logs,


dictionary import logs.

Logfiles of transport background jobs :


SAPA*
activation logs,
DS<nnnnnn>
distribution,
N<nnnnnn> or NCONV<nn> conversion.
2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

35

Technical overview logfiles of transport phases: troubleshooting


Did a tool write a error message into its logfile ? (Check the .ELG file)
Yes (an error line appears in ELG):
Check the corresponding original logfile mentioned in the ELG.
R3trans import :
In most cases during import phases it is related to DB problems and a DB error message is found in the import
log.
Activation error :
Check the object in transaction SE11.
XPRA error or short dump :
Check the report documentation of the XPRA.

No (ELG of a transport phase does not contain error lines):


Check if tp did finish correct (ECO file).
Check logfiles written by tp for errors (esp. SLOG).
2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

36

Post processing

Post-processing: XPRAs and SPAU


EXecution of PRograms After Import
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
Note #1947874 contains a comprehensive analysis of performance issues in XPRAs

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

38

Post-processing: XPRAs and SPAU


SPAU

Must be run after the 1st system upgrade of the


landscape (usually DEV)

Generates transport request which will be used on the


next systems (QAS and PRD)

http://wiki.scn.sap.com/wiki/display/TechTSG/XPRAS+phases
14-day expire period

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

39

Post-processing: XPRAs and SPAU


SPDD and SPAU in upgrades

2015 SAP SE or an SAP affiliate company. All rights reserved.

Special SPAU request

DEV QAS PRD

Avoid duplicated work

Public

40

Resources and references

Oficial SAP Systems Upgrade and Update troubleshooting Wiki


SCN Software Logistics Space
SUM download, guide, notes and related documents
Upgrade newsletter (received via e-mail, also attached to this presentation)

2015 SAP SE or an SAP affiliate company. All rights reserved.

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.

2015 SAP SE or an SAP affiliate company. All rights reserved.


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.
National product specifications may vary.
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 SEs 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 forwardlooking 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.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

43

2015 SAP SE oder ein SAP-Konzernunternehmen.


Alle Rechte vorbehalten.
Weitergabe und Vervielfltigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrckliche schriftliche
Genehmigung durch SAP SE oder ein SAP-Konzernunternehmen nicht gestattet.
SAP und andere in diesem Dokument erwhnte Produkte und Dienstleistungen von SAP sowie die dazugehrigen Logos sind Marken oder eingetragene Marken der
SAP SE (oder von einem SAP-Konzernunternehmen) in Deutschland und verschiedenen anderen Lndern 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 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.

2015 SAP SE or an SAP affiliate company. All rights reserved.

Public

44