We are performing an upgrade from ECC6.0 EHP3 to EHP6 and encounter a major deviation of the runtimes observed between dry run and live upgrade.

We have finished the uptime phases and here is what we see so far:

In red are the main phases for which the run time literally exploded:

PHASEDRY_RUN

LIVE PROTIMES

Extraction 1:31:45PROFREAD (+dialogs) 0:00:03 0:00:37SCANDIR_EPS0 0:47:34 0:24:29

SPAMCHK_INI (+dialogs) 0:03:24 1:05:52

KX_CPYORG 0:00:30 0:08:41SCANDIR_COLLECT 0:00:47 0:00:07SCANDIR_EXTRACT 0:01:00 0:00:53

INSTANCELIST_PRE (+dialogs) 0:18:45 0:10:09

JOB_RSUPDTEC 0:01:02 0:01:33TOOLIMPD 0:00:30 0:00:57TOOLIMPI 0:00:30 0:01:04Configuration 3:42:20INITSUBST (+dialogs) 1:01:29 0:09:20RUN_RSUPGSLI 0:00:33 0:00:32RUN_GENPUTTBSHD 0:00:46 0:01:06RUN_RSPTBFIL_PREP 0:00:31 0:00:31EHP_INCLUSION 0:40:53 8:10:59IS_SELECT (+dialogs) 0:27:30 8:35:10

BIND_PATCH (+dialogs) 0:09:28 0:03:52

TR_CMDIMPORT_FDTASKS 0:05:24 0:20:18

TR_CMDIMPORT_PREPARE 0:12:10 2:43:56

CONFLICT_CHECK 0:43:00 2:54:17ADJUSTPRP (+dialogs) 0:08:35 0:05:54SCANDIR_KRN 0:00:57 0:00:12INITSHD (+dialogs) 0:01:27 0:00:49RUN_RSUPGRFC 0:00:31 0:00:33

RUN_RSPTBFIL_SPACE 0:00:32 0:00:31

RUN_RSDBSCPY_INIT 0:01:51 0:05:51[-] Checks 0:19:18[+] NTACT_CHK 0:08:49 0:12:13ACTREF_CHK 0:02:51 0:06:20

ECC6 upgrade from EHP3 to EHP6 : Dry run Vs Real upgrade runtimes

REPACHK 0:00:43 0:05:28

ADJUSTCHK_PRE_EHPI (+dialogs) 0:03:13 0:10:54

[-] Preprocessing

REPACHK1 0:02:30 0:07:12JOB_RSVBCHCK2 0:00:11 0:18:52

JOB_RS_OLTPSOURCE (+dialogs) 0:02:56 0:17:53

RUN_RSPTBFIL_INIT 0:00:31 0:01:01

REPACHK_CLONE (+dialogs) 0:02:19 0:05:47

ADJUSTCHK_EHPI (+dialogs) 0:04:02 0:08:49

[+] DBCLONE 1:48:13 4:13:50

[+] UPDATE_DBSTATS_SHDCLONE 0:05:29 0:14:39

[+] NTACT_NODBPOS 0:00:53 0:03:46

SHADOW_IMPORT_UPG1 0:00:52 0:00:25

START_SHDI_FIRST 0:01:25 0:02:44

[+] ALTNTAB_FILL_PRE 0:05:24 0:18:16

JOB_RSUPDTEC_SHD_PRE 0:01:01 0:02:37

CMDFILE_PREPUT 0:00:51 0:00:25PREPUTRECOVER 0:00:48 0:01:37DDIC_PREPUT 0:00:54 0:00:42PREACT_UPG 0:01:52 0:01:45

RUN_RSPTBFIL_DEST_PRE 0:00:32 0:01:02

JOB_RUTTTYPSET_PRE 0:01:11 0:01:53

[+] PARDISTPRE_SHD 0:02:28 0:02:44

PARMVNT_PRE 0:00:40 0:01:02

SHADOW_NTACT_RECP_PRE 0:01:14 0:01:21

SHADOW_IMPORT_PRE 0:00:51 0:00:41

START_SHDI_PREPUT 0:00:53 0:01:17[+] ALTNTAB_FILL 0:06:35 0:13:30[+] DDIC_UPG 1:41:54 6:06:56

RUN_RSINCGEN_SHD1 0:00:32 0:01:23

JOB_UMOD20_UPG 0:00:50 0:01:36ACT_UPG 15:49:01 19:58:17RUN_RSCPINTS_PREP 0:01:24 0:03:40

1. 1.09:58:26

RUN_RSPTBFIL_DEST 0:03:42 0:06:15JOB_RUTTTYPSET 0:00:48 0:01:08RUN_INDC_UPG 0:01:11 0:01:21PARDIST_SHD 0:08:33 0:31:54RUN_RSPTBFIL_PDIST 0:00:41 0:01:03

RUN_RSUPG_DDXTT_TABLSIZE 0:01:11 0:01:21

RUN_RSPTBFIL_TRINIT_S 0:00:31 0:00:31

RUN_RSCPINTS_STDSAVE 0:00:51 0:02:34

RUN_RSCPINTS_RESTINIT 0:02:20 0:05:36

RUN_RSCPINTS_ALTNTUPD 0:00:51 0:04:52

RUN_RSPTBFIL_SHDDEST 0:03:10 0:03:02

PARDIST_SHD2 0:07:54 0:29:42

RUN_RSPTBFIL_SHD2PDIST 0:00:31 0:00:21

RUN_RSUPG_DDXTT_TABLSIZE_SHD2 0:01:10 0:01:06

RUN_RSCPINTS_SAVE 0:00:51 0:02:02

JOB_RS_APPLINTS_UPDATE 0:00:35 0:00:36

RUN_RSCPINTS_SHDRESTORE 0:01:11 0:02:45

RUN_RSVWSDROP 0:00:33 0:00:32PARMVNT_SHD 0:08:55 0:28:29SCEXEC_GRANT 0:00:53 0:02:50SCEXEC_ALIAS 0:00:34 0:01:58

SHADOW_NTACT_RECP 0:00:44 0:01:01

TP_ACTION_CP2STAB 0:03:58 0:08:39

SHADOW_IMPORT_BAS 0:01:02 0:00:11

SHADOW_IMPORT_UPG2 0:01:02 0:00:11

SHADOW_IMPORT_INC 5:45:07 10:05:55

UPDATE_DBSTATS_NEWSHD 0:03:25 0:03:01

PMVNTAB_VIEW_SHD2 0:00:51 0:00:58

START_SHDI_SHD2 0:01:04 0:01:47

RUN_RSCPINTS_ALTNTUPD2 0:01:49 0:03:20

RUN_RSCPINTS_STDRESTORE 0:01:11 0:02:42

RUN_RSINCGEN_SHD3 0:00:30 0:00:41

RUN_RSCPINTS_POOL2SHD 0:00:30 0:00:21

TABIM_POST_SHD 0:32:11 0:40:41

RUN_RSAIMMERGE_UPG_SHD 0:15:22 0:20:03

CONVBUFFER_AIMMRG_L2B_SHD 0:02:36 0:10:34

XPRAS_SHD_AIMMERGE 0:06:57 0:08:49

JOB_RSUPD_ABSTAMP 0:00:30 0:00:46

RUN_RSGENLOD 0:07:11 0:08:33RUN_RSGEN 2:10:51 2:50:35

UPDATE_DBSTATS_SCHDSGEN 0:11:06 0:22:14

RUN_RSCPINTS_NOXCONV 0:02:11 0:02:31

SCEXEC_DEL_ALI 0:00:33 0:01:28SCEXEC_DEL_GRA 0:00:41 0:01:46

PSCRGEN_DROP_SHD_TABLE2 0:01:00 0:02:09

EU_CHECK 0:00:38 0:00:42

We also noticed a difference in the CPU usage so far.

Here is the figure representing CPU usage during the dry runs:

[-] Transition to Downtime for

Downtime-minimizedMAIN_DTTRANS

The above figure is the CPU usage during the dry run performed without users activity.

This one is the one during the real uptime phase performed on the production system.

What we don’ t really get is why is the CPU usage so low on the production run. I mean, we had users activity in parallel to this uptime upgrade phase and would have expected the CPU to be much higher. But it is not the case.

All the parameters set for the upgrade were exactly the same in dry run and live run.

Has anyone ever experienced such a situation ?

Does anyone has an explanation to this phenomenon ?

It’ s like the upgrade process is “caping” the CPU usage in some way. Is this kind of feature included in the upgrade tools ?

Has anyone ever experienced such a time drift between a dry run and a live run ? .

We are performing an upgrade from ECC6.0 EHP3 to EHP6 and encounter a major deviation of the runtimes observed between dry run and live upgrade.

What we don’ t really get is why is the CPU usage so low on the production run. I mean, we had users activity in parallel to this uptime upgrade phase and would have expected the CPU to be much higher. But it is not the case.

It’ s like the upgrade process is “caping” the CPU usage in some way. Is this kind of feature included in the upgrade tools ?

What we don’ t really get is why is the CPU usage so low on the production run. I mean, we had users activity in parallel to this uptime upgrade phase and would have expected the CPU to be much higher. But it is not the case.