Ansicht
Dokumentation
05383 - MCH3601, MCH0602 errors during upgrade
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
MCH3601, MCH0602 errors during upgrade
Hi Russ,normally there are no obejcts duplicate in the patches on sapserv or the
marketplace. At the moment, there is an exception of the rule with SAPOSCOL,
that is in the KERNEL-Patch as well, because of a major necessary change.
But you can be sure, that both versions are the same. So, it doesn't matter
in what order you load the patches.
You should always update at least KERNEL and LIB_DBSL. Then the "normal
SAP-Systrem" is fine. Everything else are more or less rarely used
executables. In order to reduce the problems on your site, TP and R3TRANS
are always a good choice, during upgrades R3LOAD as well.
All other are normally only necessary, if problems occur. But you can update
them all!
Regards
Volker
-----Original Message-----
From: rcookZa...
To: Gueldenpfennig, Volker
Sent: 19.03.02 00:37
Subject: MCH3601, MCH0602 errors during upgrade
Hi Volker,
I just wanted to give you an update on the problem I had below. I
updated
the 46D "kernel" from sapserv4 but I was still receiving mch3601 and
mch0602 errors when starting SAP during the upgrade. I later applied
the
lib_dbsl patch from sapserv4 and now SAP will start up so I can continue
on
my upgrade. I do have a question in regards to the patches on the
sapserv4
directory. Is it always good practice to apply all the patches listed
there? I am somewhat confused as to what patches get placed in the
"kernel" save file and what does not. Is there a possibility that the
same
objects exists in both the kernel save file and also in one of the
individual save files like lib_dbsl? If so, how do you know which is
the
latest?
Kind regards,
Russ Cook
Durban Tours - Südafrika Safari
PERFORM Short Reference BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 2302 Date: 20240328 Time: 202013 sap01-206 ( 3 ms )