Ansicht
Dokumentation
10710 - Kernel 1499 + Three Tier + 46C
ROGBILLS - Synchronize billing plans ABAP Short ReferenceThis documentation is copyright by SAP AG.
Kernel 1499 + Three Tier + 46C
To be more specific, SAP is not aware of a kernel in which the problem isnot present, so there may be a good kernel but SAP is not yet sure which one
that might be.
Regards,
Tom
-----Original Message-----
From: Rooyen Tom van [mailto:tvroZoce.nl]
Sent: donderdag 10 juli 2003 12:00
To: 'DoNotReply@consolut.eu'
Subject: RE: Re: Kernel 1499 + Three Tier + 46C
Hi Agoes,
All the problems in this thread that relate to kernel 1499 we have
experienced with kernel 1444 which is the CD kernel. These errors occurred
in our production system within a week from starting the SAP system. We
backed down to 1098 in production and that runs fine. Our development and
test systems run fine with 1444 but the activity of these systems is much
lower.
We have our own problem record concerning this with SAP.
As far as i know there is no kernel that is NOT faulty. I hear things that
1330 is more stable, but the statement from SAP (Sally Power Z 26/06/03) is
that there is no correct kernel at the moment.
Kind regards,
Tom van Rooyen
-----Original Message-----
From: Agoes B. Poerwanto [mailto:abpZecco.com]
Sent: donderdag 10 juli 2003 11:44
To: DoNotReply@consolut.eu
Subject: RE: Re: Kernel 1499 + Three Tier + 46C
Hi Tom,
But due to Sally Power, sorry not Sally Summer as I wrote before, this
kernel is the most stable one. I supposed to be back to kernel 1385, but
according to her, there were some faulties on it. Would you explain me the
reason ?
Thank you in advance.
Best regards,
Agoes
Rooyen Tom van
<tvroZoce.nl> To:
"'DoNotReply@consolut.eu'" <DoNotReply@consolut.eu>
cc:
10-07-03 11:07 AM Subject: RE:
Re: Kernel 1499 + Three Tier + 46C
Please respond to
SAP on System i
Kernel 1444 is faulty as well, don't use it in production.
Regards,
Tom van Rooyen
-----Original Message-----
From: Agoes B. Poerwanto [mailto:abpZecco.com]
Sent: donderdag 10 juli 2003 11:00
To: DoNotReply@consolut.eu
Subject: RE: Re: Kernel 1499 + Three Tier + 46C
Dear all,
I found also some dumps in our PRD system due to the kernel problem in
patch 1499. The only way to solve is restarting the instance. I was
suggested by Sally Summer from SAP iSeries Development to go back to kernel
patch 1444, of which available in Kernel CD 46D. So far it works fine,
except dumps CONVT_OVERFLOW in program RSHOST2M and RSHOST4M due to the
broken record in table MONI. OSS suggested some solution in note 49763,
39606, 19227 and 6833, but so far they don't help. I am still trying to
'repair' this one.
Do you have experience in the problem like what I have now ? Please share
to me, if you have. I would really appreciate.
Best regards,
Agoes Boedi Poerwanto
SAP Basis
ECCO SKO A/S
Phone: +45 7491 1957
Mobile: +45 2373 1059
mailto:abpZecco.com
"Anderson,
Doreen" To:
<DoNotReply@consolut.eu>
<dandersoZballhor cc:
t.com> Subject: RE:
Re: Kernel 1499 + Three Tier + 46C
09-07-03 11:55 PM
Please respond to
SAP on System i
We are in need of kernel 1330 (we are moving to V5R2 and the only kernel
"up" available is 1499)
Would someone be able to send 1330 to me? Please?
Thank you - Thank you!
Doreen
-----Original Message-----
From: sapbasisguy [mailto:craig_welchZbradycorp.com]
Sent: Wednesday, July 09, 2003 3:57 PM
To: DoNotReply@consolut.eu
Subject: Re: Kernel 1499 + Three Tier + 46C
Just a follow up on this:
First, I added another application server instance to each of our two
login groups. The intensity of the dumping lessened considerably with
the 1499 Kernel. Last weekend, I backed the Kernel down to version
1330 and we have not experienced the dumps in the first 3 business
days. We were getting the dumps on one to two application server
instances every day before backing out the kernel.
Craig.
--- In DoNotReply@consolut.eu, Rooyen Tom van <tvroZo...> wrote:
> When we first reported this problem there was an attached note.
This note
> however is now in maintenance and cannot be viewed. We made a copy
of it
> however and here is what it says:
>
> SAP Notes 624909 matches 100%
>
> SAP Note No. 624909
17.06.2003 Page
> 1
>
>
______________________________________________________________________
__
>
> Number 624909
> Version 2 from 24.05.2003
> Status Released for Customer
> Set on 24.05.2003
>
> Language EN
> Master language DE
> Short text iSeries: Many short dumps on the system
>
> ResponsibleSAP AG
> Component BC-OP-AS4
> IBM AS/400 (incl. IBM JVM on OS/400)
>
>
______________________________________________________________________
__
>
> Long text
>
> Symptom
> The system is producing manyshort dumps. The dumps are also
produced
> for reports which have, up to now, run without any errors. The
> following
> dumps are frequently among those produced :
>
> o RUNT_ILLEGAL_SWITCH
>
> o TSV_ILLEGAL_REFERENCE
>
> o SYSTEM_RUDI_INVALID
>
> o LOAD_PROGRAM_LOST
>
> Additional key words
> iSeries, AS/400, Shortdumps, RUNT_ILLEGAL_SWITCH,
> TSV_ILLEGAL_REFERENCE,SYSTEM_RUDI_INVALID, LOAD_PROGRAM_LOST
>
> Cause and preconditions
>
> The cause of this problem is probably a storage overwrite in
shared
> memory. This problem occurs only rarely and is, unfortunately,
not
> reproducible. Regrettably, the exact cause of the problem has
not been
> found yet.
> The error appears to occur after a report is manually
terminated by a
> user via SM50 or SM04 (not the work process but only the report
> itself),
> together with several other auxiliary conditions which have
not been
> completely determined yet. In the R/3 system log (SM21), the
message
> R0M
> appears, followed by several R0K messages. As a consequence,
short
> dumps
> with the titles given above begin to occur very frequently
and, after
> some little time, the system is no longer usable, since many
users
> abort
> with the various short dumps mentioned above. In SM50 it can
be seen
> that there are many work processes showing a restart after
error. The
> exact symptoms can vary a little, as they are dependent on how
shared
> memory has been overwritten, which appears to vary from case
to case.
>
> Solution
> If the symptoms described above occur on the system, then the
system
> must be recycled, as this is the only possibility to
reinitialize
> shared
> memory correctly. Once this has been done, the errors should
no longer
> occur.
> At the moment there is, unfortunately, no final solution for
this
>
Page
> 2
>
> problem. Patch level 1517 does, however, provide a workaround,
which
> has
> prevented a renewed occurence of this error on all the
customer systems
> on which it has been installed.
> Please install patch level 1517 on your system. If the error
should
> still occur even after this, then please create a SAPNet R/3
Frontend
> message for the component BC-OP-AS4 immediately and request
that it be
> sent directly to development support,
>
>
______________________________________________________________________
__
>
> Valid releases
> Software Component Release
> from to
>
>
> SAP_BASIS SAP Basis component 46C - 46D
> 46B - 46B
>
> Further components
>
> BC-DB-DB4
> DB2 for AS/400
>
>
> -----Original Message-----
> From: sapbasisguy [mailto:craig_welchZb...]
> Sent: dinsdag 1 juli 2003 13:12
> To: DoNotReply@consolut.eu
> Subject: Re: Kernel 1499 + Three Tier + 46C
>
>
> Tom,
>
> I thought 1499 would be stable since it had been out there so long.
> It sounds like we'll be backing down to kernel 1330 this weekend.
> This is impacting our ability to take orders when it happens.
>
> Craig.
>
> --- In DoNotReply@consolut.eu, Rooyen Tom van <tvroZo...>
wrote:
> > We had this problem after upgrading the kernel from 1098 to 1499.
> Ours is a
> > 2 tier landscape. Because we could not afford all these dumps we
> went back
> > to 1098.
> >
> > This is a known problem for SAP for which their is no solution at
> the
> > moment. They had a workaround in kernel 1517 or so, but it got
> withdrawn I
> > think because it did not work. At the moment we just have to wait
> for the
> > new kernel to be released.
> >
> > We need this kernel, or the fix within it, badly for our V5R2 and
> subsequent
> > hardware upgrade
> >
> > Tom van Rooyen
> >
> > -----Original Message-----
> > From: sapbasisguy [mailto:craig_welchZb...]
> > Sent: dinsdag 1 juli 2003 0:29
> > To: DoNotReply@consolut.eu
> > Subject: Re: Kernel 1499 + Three Tier + 46C
> >
> >
> > Not to flood these messages but if anyone from SAP is interested
in
> > looking at this I have had a high message open since Thursday
> > afternoon that has yet to be read. Customer note 330134.
> >
> > Thanks,
> > Craig
> >
> >
> > --- In DoNotReply@consolut.eu, "sapbasisguy"
> <craig_welchZb...>
> > wrote:
> > > FYI, we did have this occasionally with the 1330 kernel before
> the
> > > upgrade, but this is happening several times a week now. It
> happens
> > > on one or two app servers at a time and the rest continue to
> > function
> > > just fine. Sometimes a /$sync will help but not always.
> > >
> > > Craig
> > > --- In DoNotReply@consolut.eu, "sapbasisguy"
> > <craig_welchZb...>
> > > wrote:
> > > > Hello,
> > > >
> > > > We are having issues with our system since the upgrade to
46C.
> We
> > > > also upgraded from Kernel 46D 1330 to Kernel 1499 at the same
> > time
> > > we
> > > > performed the upgrade.
> > > >
> > > > The issue is that we get a spurt of dumps that I can't find a
> > root
> > > > cause for. I was wondering if there were any known issues
with
> > the
> > > > 1499 kernel (or OS400 V5R1) that anyone else is experiencing.
> > > Here's
> > > > a sample of the dumps that come out in quick succession once
it
> > > > starts dumping:
> > > >
> > > > RUNT_ILLEGAL_SWITCH
> > > > SYSTEM_RUDI_INVALID
> > > > GETWA_NOT_ALLOC
> > > > TSV_ILLEGAL_REFERENCE
> > > > MOVE_TO_LIT_NOTALLOWED_NODATA
> > > > OBJMGR_INTERNAL_ERROR
> > > > SYSTEM_RUDI_INVALID
> > > > STORAGE_FREE_FAILED
> > > > CONVT_NO_NUMBER
> > > > RUNT_ILLEGAL_SWITCH
> > > > SYSTEM_ROLL_IN_ERROR
> > > > IMC_PUT_MODE_ERROR
> > > > TEXTENV_INVALID
> > > > SAPSQL_CLIENT_ILLEGAL_FORMAT
> > > > RUNT_ILLEGAL_SWITCH
> > > > TIME_OUT
> > > > DBIF_REPO_PART_NOT_FOUND
> > > > DBIF_REPO_PART_NOT_FOUND
> > > > GETWA_WRONG_LENGTH
> > > > DSTEP_ILLEGAL_MODULE_INDEX
> > > > SYSTEM_RUDI_INVALID
> > > > TSV_TNEW_OCCURS_NO_ROLL_MEMORY
> > > > SYSTEM_NO_ROLL
> > > > SAPSQL_CLOSE_RSQL_STACK_ERROR
> >
> >
> >
> > Have a look to our homepage at: http://www.consolut.net
> > DoNotReply@consolut.eu
> >
> > Your use of consolut is subject to
> http://www.consolut.net
>
>
>
> Have a look to our homepage at: http://www.consolut.net
> DoNotReply@consolut.eu
>
> Your use of consolut is subject to
http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to
http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
Your use of consolut is subject to http://www.consolut.net
Durban Tours - Südafrika Safari
ABAP Short Reference rdisp/max_wprun_time - Maximum work process run time
This documentation is copyright by SAP AG.
Length: 18984 Date: 20240520 Time: 150119 sap01-206 ( 4 ms )
