Ansicht
Dokumentation

04138 - BC:STOP THE LONG RUNNING ROLLBACK JOURNALING ! !!

04138 - BC:STOP THE LONG RUNNING ROLLBACK JOURNALING ! !!

General Data in Customer Master   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.
SAP E-Book

BC:STOP THE LONG RUNNING ROLLBACK JOURNALING ! !!

Hi again,

You might also have some old savefiles on your system - for example from a
apply of patches from Walldorf, ex. Kernel, TP, LIB_DBSL etc.

Regards
Klaus

-----Oprindelig meddelelse-----
Fra: Klaus Lindegaard (RWDK) [mailto:klaus.lindegaardZr...]
Sendt: 5. december 2001 13:45
Til: 'Zvada Márton'; SAP - Volker Güldenpfennig (E-mail)
Cc: Sap400 (E-mail)
Emne: SV: BC:STOP THE LONG RUNNING ROLLBACK JOURNALING ! !!


Hi,

For extra cleanup you might check for your EPS in box /usr/sap/trans/eps/in
for unneeded files og check /usr/sap/trans/tmp might also contain some
unneeded car files.

In DB02 you could also check for files with a large amount of deleted bytes.

Try to check your historylog files - wrkobj *all/qhst* *file and delete
unneeded files date timestamp in read in the beginning of the file
description.

You could also check for old onneeded print in ex. qezjoblog.

Hope this can give you some free space on the system.

Keep my fingers crossed for you

Regards
Klaus Lindegaard

-----Oprindelig meddelelse-----
Fra: Gueldenpfennig, Volker [mailto:volker.gueldenpfennigZs...]
Sendt: 5. december 2001 13:19
Til: 'Zvada Márton'
Cc: Sap400 (E-mail)
Emne: RE: BC:STOP THE LONG RUNNING ROLLBACK JOURNALING ! !!


as the database of OS/400 is a consistent database it still tries to
rollback, even if you kill the job! It won't end before the end of the
rollback. the same is true for the IPL. The IPL will check for open commit
boundaries and will recover the situation to the last commit, even if takes
for hours or days!

The only way would be to call IBM. They are able to prevent this with a
password if you sign, that you accept an inconsistent database!!!

It's up to you,

I would run an IPL and wait, if I had time enough. Please stop definitely
SAP before and wait till all other WPs died. So you are at least sure, that
only this crazy job is inconsistent and you could use your approach either
to relaod everything or to reload this table after you perhaps used the
IBM-password.

Sorry,

Volker

> -----Original Message-----
> From: Zvada Márton [mailto:m_zvadaZb...]
> Sent: Mittwoch, 5. Dezember 2001 13:13
> To: Gueldenpfennig, Volker
> Subject: Re: BC:STOP THE LONG RUNNING ROLLBACK
> JOURNALING !!!
>
>
> Hello Volker,
>
>
> The job started at 16:52 yesterday, and the rollback started
> ~ at 09:00
> today.
> It seems, that we haven't got enough DASD to wait for the end of the
> rollback process.
> The starting ASP % was 75 %, and we've already saved and
> deleted some GB of
> unnecessary files.
> That's your opinion: If we shut down the SAP system, will the
> rollback ended
> or not.
> I didn't write in he first mail, that we stopped the rollback
> job on the OS
> level too.
> Not too happy situation, isn't it...
>
> In case of database demages this won't be a sirious problem,
> because the
> updated file can be restore from tap.
>
> Best regards:
>
> Martin
>
> ----- Original Message -----
> From: "Gueldenpfennig, Volker" <volker.gueldenpfennigZs...>
> To: <m_zvadaZb...>
> Cc: "Sap400 (E-mail)" <sap400Zm...>
> Sent: Wednesday, December 05, 2001 12:45 PM
> Subject: RE: BC:STOP THE LONG RUNNING ROLLBACK
> JOURNALING !!!
>
>
> > Hello Martin,
> >
> > that's really a pitty!
> >
> > You can't delete the journal-receiver, because the OS needs
> them to do the
> > rollback. As the rollback works from the end to the start, you can't
> delete
> > any of the journal receivers, that were generated since the
> start of that
> > long transaction.
> >
> > You can NOT stop this process at all!!! This would cause
> corruptions of
> the
> > database-integrity.
> >
> > You could try and have a look how many journal receivers
> you are having
> now
> > and how many since the rollback, then you could estimate
> how many you'll
> > need (normally you need the same amount for the runnning
> abap than for the
> > rollback).
> > If this results in more than 100% DASD, you are in bad luck.
> >
> > You could call IBM in order to guide you here.
> >
> > But I think the best will be to shut down your system as
> soon as possible
> > and do an IPL. This will take very long time (several hours
> and more!) but
> > will finally do the complete rollback and will rollback all other
> > non-committed data as well. So, you will achieve a
> consistent database
> after
> > a long time.
> >
> > Sorry, to tell you nothing better,
> >
> > Regards
> >
> > Volker
> >
> > P.S.: How long did this job run ? How long is the rollback
> already in
> > progress ? (sometimes the rollback needs 2-3 as long as the running
> before)
> >
>


DoNotReply@consolut.eu

Your use of consolut is subject to http://www.consolut.net



DoNotReply@consolut.eu

Your use of consolut is subject to http://www.consolut.net


Durban Tours - Südafrika Safari

Vendor Master (General Section)   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 7230 Date: 20240623 Time: 193917     sap01-206 ( 5 ms )