Upgrade Monitoring

Download Report

Transcript Upgrade Monitoring

Upgrade Monitoring
Tips for Trouble Shooting
the 4.6 Upgrade
Joerg Limbach
SAP AG
 SAP AG 2000 / 1
AcceleratedSAP
Agenda
 Localizing Problems

Monitoring and error analysis

R3up error analysis



Job phases
Transport phases
Bulk import phases
 Required information for opening a problem message
 SAP AG 2000 / 2
AcceleratedSAP
Monitoring and Error Analysis
 R3up

Infos and error messages
(“HELP”  long texts)
 R/3 System

Check syslog (SM21)

Check joblog (SM37)

Check trace files (ST11 or AL11)
 OS

Check log files (in put/tmp or put/log on UNIX: ls -ltr|tail)

Check processes (UNIX: ps -ef | grep <name>, NT: pstat)

Check database alert files
 SAP
2000 filename
/3
 SAP
AGAG
2000
(J.Limbach) / 3
AcceleratedSAP
Monitoring and Error Analysis
 Log files in /usr/sap/put/log

Current activities of R3trans or the batch
processes are continuously logged to
/usr/sap/put/tmp.

In case of problems an alert file is written.
 Hierarchy of error messages

1st level: R3up error messages with menu item HELP (long texts!)

2nd level: summary log file <PHASE>.ELG that contains the names of
the 3rd level log files, the error messages (long texts: SE91)and exit
codes

3rd level: single detailed log files, most often SAP*.<SID> or tp log
 SAP
2000 filename
/4
 SAP
AGAG
2000
(J.Limbach) / 4
AcceleratedSAP
R3up Error Analysis
 There are 3 different types
of R3up phases :

Job Phases : R3up starts a function module or
back ground job.

Transport Phases : R3up starts tp. tp either




Connects to DB to execute a SQL script or,
Starts R3trans for import into DB and/or,
Starts a transport step in background via RDDIMPDP.
Bulk Import Phases : R3up starts R3load.
 At the end of the phase R3up analyses the direct (return code)
and indirect (log files) result of the calls.
 SAP AG 2000 / 5
AcceleratedSAP
JOB_ or RUN_ Phases
 R3up calls function module SUBST_START_BATCHJOB via
RFC.
 This function module schedules a background job.
 R3up calls FM SUBST_CHECK_BATCHJOB via RFC to check
the status of the scheduled job.
 When the job aborts, R3up stops with a error message.
(causes e.g. job canceled manually, short dump, ...)
>scan job log more info in SM37
 After the job finished, R3up scans the log file and continues,
if no errors are found.
If ‘errors found in log file’ R3up stops. > analyze logs
 SAP AG 2000 / 6
AcceleratedSAP
Upgrade and Hostnames : RFC, BTC, DB check
DEFAULT.PFL:
rdisp/btcname
sapevt
over MS
B
T
C
B
T
C
Batch
Instance
Host
 SAP AG 2000 / 7
G
W
RFC
R3trans
TPPARAM:
<SID>/db*
gen.
Central
Instance
Host
tp
DB
Host
R3up
AcceleratedSAP
Log File Names of Job Phases
 <name>.LOG
can contain the RFC login, start and check
of a Batchjob <name>
 <name>.<SID>
where <name> is not a transport log, can
be the log files of a batch job
 <name>.ELG
are the condensed log files
(contain only errors)
 <name>.SAV
can be old .LOG and/or old .ELG files
 Example for Phase RUN_RDDIT006 :

DIFFCALC.LOG

CUSTEXP.<SID> is the log file of the batch job RDDIT006

DIFFCALC.ELG

(DIFFCALC.SAV) .ELG and .LOG of older runs
 SAP AG 2000 / 8
contains the RFC logon
condensed errors
AcceleratedSAP
Log File Analysis by R3up
 R3up scans the log file of the back ground jobs for errors (E
in the second column) and copies these lines into .ELG file.
The analyzed section is marked by the header:
4 EPU201XBEGIN OF SECTION BEING ANALYSED
and the footer
4 EPU202XEND OF SECTION BEING ANALYSED
 The number of errors in one phase are the number of lines
copied into the .ELG.
 A line in a log file starting e.g.. with 2EETG779 ....
means:
Severity 2 (log file display in SE09),
Error, English, message class TG,message 779.
SE91 can be used to display the long texts of error messages.
( Long text  Document  Screen)
 SAP AG 2000 / 9
AcceleratedSAP
Transport Phases: DIFFEXP, DDIC, ACT, TABIM,
ADOIM, XPRAS, ...
 R3up calls tp with special options and a special TPPARAM.
 Log files of R3up :
TP.ECO or R3up.ECO
stdout of tp,
*.ELG
collected errors from transport logs,
 Log files of tp :
ULOG...
tp call incl. TPPARAM,
ALOG<rel>
finished steps (request, return code),
SLOG<rel>
details of tp call,
 Log files of R3trans :
SAPI* or SAPH*
Import log (main~,DDIC~)
 Log files of transport background processes e.g..:
SAPA*, DS<date>, N<date>Activation, Distribution,
Conversion
 SAP AG 2000 / 10
AcceleratedSAP
PCON Logs
 PCON has a specific handling: The batch jobs are started by
R3up, tp does the move name tab, when the distributors have
finished an additional check is started (FDSAVPROT).
 In PCON the log files are
DS<date>.<SID>
calculates the mode flags from
active<>inactive name tab
FDSAVPRT.<SID>
just in case fields are lost
NCONV00.<SID> - NCONV02.<SID> table conversions
PA<date>.<SID>
name tab only activated
PD<date>.<SID>
activation and alter table add field or
similar
PL<date>.<SID>
delete table and remove name tab
 SAP AG 2000 / 11
AcceleratedSAP
Bulk Import Phases: EU_IMPORTx
 R3load import packets of tables direct from CD into the DB
(>CD read problems, CD via NFS is suboptimal)
 The initial extent will be chosen, so that most tables fit into
the first extent (>problems in restart)
 Configuration files for R3load are in put/exchange
 Log files are EX...... .DPR
 SAP AG 2000 / 12
AcceleratedSAP
Agenda
 Avoiding Problems

R/3 Patches in source release > Bind Patches ?

Dependencies OS / DB / Kernel / R/3
> Independent OS, DB, R/3 upgrades possible ?

Strategies, DB backups, file system backups
 Localizing Problems

Monitoring and error analysis

R3up error analysis



Job Phases
Transport Phases
Bulk Import Phases
 Required information to open a problem message
 SAP AG 2000 / 13
AcceleratedSAP
Upgrade Problems: Essential Facts
 Detailed problem description
 Concerned phase ?
 System data




Source release
Target release
Hardware platform (OS version)
Database (version)
 Problems in previous phases / upgrades ?
 Errors ignored / password used ?
 Customer actions/input prior to the error
 Output/reaction of R3up and system
 Precise error message and message number
 Log files / batch logs / trace files
 Access to OS / SAP System possible ?
 SAP AG 2000 / 14
AcceleratedSAP
Upgrade Monitoring
Tips for Trouble Shooting
the 4.6 Upgrade
Questions & Answers
 SAP AG 2000 / 15
AcceleratedSAP