Ansicht
Dokumentation
12938 - Digest Number 1163
ABAP Short Reference ABAP Short ReferenceThis documentation is copyright by SAP AG.
Digest Number 1163
Hello Volker and Gerhard,We had similar experience, which is kind of mysterious to myself.
Faisal, another Basis guy in Plastipak and this group, applied the latest
CumPack and DB Fix on our backup/test machine, and everything was working. Then
he refreshed QAS database. After that QAS could not start...
I cannot remember what exactly I saw, but I am sure "ES_SHM" was in the first
"error" line. The problem was fixed by rolling back the kernel from 1728 to
1617. Then I reapplied the kernel 1728 with the original kernel library, and the
system came up. Because the issue was "fixed" by 2 rebounces, the traces were
gone. So I don't have a detailed log now.
Hope the extra info can help!
Victor
SAP Basis Manager
Plastipak Packaging INC
*****************************8
Message: 17
Date: Wed, 18 Feb 2004 11:32:22 -0000
From: "Volker Gueldenpfennig" <volker.gueldenpfennigZsap.com>
Subject: Re: Exception MCH4431 in file sapo4start.c line 1105
OK,
but in both cases you will see the MCH4431.
That makes sense if the CLEANIPC program doesn't work.
This has to remove the shared memory before and after SAP. It is
cleared with an IPL as well.
Regards
Volker
--- In DoNotReply@consolut.eu, "Gerhard Farmer" <luck_fgZy...>
wrote:
>
> Hey Volke
>
> When we shut down SAP then it is not possible to restart.
> Then we must do an IPL and SAP start.
> That is what i mean with solved.
>
> LG.
> Gerhard
> --- In DoNotReply@consolut.eu, "Volker Gueldenpfennig"
> <volker.gueldenpfennigZs...> wrote:
> > Hi Gerhard,
> >
> > even when you think, that this can be solved with an IPL:
> > I don't beleive this!
> >
> > MCH4431 is "Signature Violation"
> >
> > That means some program has a different signature than a
different
> > service program. This problem is always there, when it is there
at
> > all.
> > So, your last kernel patch went wrong, either because it
> terminated,
> > or because SAP did something wrong with the delivery.
> >
> > Regards
> >
> > Volker
> >
> > --- In DoNotReply@consolut.eu, "Gerhard Farmer"
> <luck_fgZy...>
> > wrote:
> > > addional Information about our Problem
> > >
> > > Using implementation
> > > std
> > > *** ERROR => EsAS4MapInit: Cannot create ES_SHM; rc 4
> > [eso4i.c
> > > 291]
> > > *** ERROR => EsIOsInit: EsAS400MapInit failed [eso4i.c
> > > 189]
> > > *** Error 11 while initializing OS dependent
> > > part.
> > > *** ERROR => DpEmInit: EmInit (1) [dpxxdisp.c
> > > 6666]
> > > *** ERROR => DpMemInit: DpEmInit (-1) [dpxxdisp.c
> > > 6611]
> > > *** DP_FATAL_ERROR => DpSapEnvInit:
> > > DpMemInit
> > > *** DISPATCHER EMERGENCY SHUTDOWN
> > > ***
> > >
> > > --- In DoNotReply@consolut.eu, "Gerhard Farmer"
> > <luck_fgZy...>
> > > wrote:
> > > > Hey
> > > >
> > > > Has anybody experience with this error.
> > > > We are using 46D Kernel 1756. Not EXT Kernel
> > > > This problem can only solved if we do an IPL.
> > > >
> > > > Execute Pre-Startup Commands
> > > > ----------------------------
> > > > (46) Local: /usr/sap/P21/SYS/exe/run/CLEANIPC 21 remove
> > > > Exception MCH4431 in file sapo4start.c line 1105
> > > > Ung}ltige Programmkennung.
> > > > (46) Local: CLRLIB LIB(R3WRK21)
> > > >
> > > > Lg. Gerhard
Durban Tours - Südafrika Safari
CL_GUI_FRONTEND_SERVICES - Frontend Services PERFORM Short Reference
This documentation is copyright by SAP AG.
Length: 5134 Date: 20240424 Time: 030411 sap01-206 ( 3 ms )
