Ansicht
Dokumentation
12700 - CPA7090 - Entry not Journaled to journal QSQJR N hit maximum sequence # 2,147,483,136
CL_GUI_FRONTEND_SERVICES - Frontend Services rdisp/max_wprun_time - Maximum work process run timeThis documentation is copyright by SAP AG.
CPA7090 - Entry not Journaled to journal QSQJR N hit maximum sequence # 2,147,483,136
Doreen & Vincenzo,My memory is a bit hazy, but I recall something like the following from past
experience.
Prior to V5R1 (I think) the maximum sequence number was 2,147,483,648
(2**32). This number was increased to 9,999,999,999 with V5R1, but you had
to change the receiver size option to *MAXOPT1 using CHGJRN.
We subsequently found that Vision (v6.2) still only recognised the lower
number, but upgrading to v7.0 fixed that. Other HA vendors may also have the
same issues on lower releases.
Our policy is to regularly reset the journal sequence numbers when they
start getting too high. Because of our HA system, we need to shutdown R/3,
ensure the HA system is completely up to date, shut the HA system down,
reset the sequence numbers (CHGJRN R3SIDJRN/QSQJRN SEQOPT(*RESET)) on both
systems, then restart everything. We normally do this twice a year.
Regards,
Andrew
-----Original Message-----
From: Vincenzo Boesch [mailto:vboeschZbluewin.ch]
Sent: Wednesday, 28 January 2004 8:29 AM
To: DoNotReply@consolut.eu
Subject: AW: CPA7090 - Entry not Journaled to journal QSQJRN
hit maximum sequence # 2,147,483,136
But this is not the maximum of journal entries; it is the maximum number of
entries with open commits!
Imagine a program is updating so many records and is never doing any commit!
I would say this is not a problem of the operating system; it is a problem
of the program who is never executing a commit!
I have seen this problem before at a customer site and the solution was to
change the program in a way that it executes more often a commit.
Regards, Vincenzo
-----Ursprüngliche Nachricht-----
Von: Anderson, Doreen [mailto:dandersoZballhort.com]
Gesendet: Dienstag, 27. Januar 2004 19:59
An: DoNotReply@consolut.eu
Betreff: CPA7090 - Entry not Journaled to journal QSQJRN hit
maximum sequence # 2,147,483,136
How is everyone else handling the journal sequence # maximum?
We hit this at 20:18 last night, found out about it at 11pm and a fun
time was had by all till 12midnight.
Is a maximum journal sequence # of 2,147,483,136 IBM's idea of a joke?
Document Title
Journal Sequence Number Filled Up with Pending Commits in Journal
Receiver
Document Description
The maximum sequence number for a journal is 2,147,483,136 (see note).
If this number is reached, journaling is stopped for the journal. The
system sends a warning message to the message queue for the journal when
the sequence number exceeds 2,147,000,000. This warning message is
CPI70E7.
However, if this message is ignored or the user does not notice it,
journaling may stop because the sequence number has filled up and
recovery may not be possible. Recovery is to CHGJRN SEQOPT(*RESET). The
reset could fail because the sequence number is required to be
consecutive for commitment control.
[Non-text portions of this message have been removed]
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
consolut Links
To visit your group on the web, go to:
http://groups.consolut.net/group/SAP on System i/
To unsubscribe from this group, send an email to:
DoNotReply@consolut.eu
Your use of consolut is subject to:
http://www.consolut.net
[Non-text portions of this message have been removed]
Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu
consolut Links
To visit your group on the web, go to:
http://groups.consolut.net/group/SAP on System i/
To unsubscribe from this group, send an email to:
DoNotReply@consolut.eu
Your use of consolut is subject to:
http://www.consolut.net
***************************************************************************
This e-mail is confidential and may contain legally privileged information
or copyright material. If you are not the intended recipient you should not
read, copy or distribute, disclose or otherwise use the information in this
e-mail without written authorisation. If received in error, please contact
us at once by return e-mail and then immediately delete both messages and
any attachments from your system.
Dairy Farmers do not accept liability in connection with any computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment.
***************************************************************************
[Non-text portions of this message have been removed]
Durban Tours - Südafrika Safari
BAL_S_LOG - Application Log: Log header data TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 6618 Date: 20240426 Time: 131023 sap01-206 ( 3 ms )
