Ansicht
Dokumentation

12699 - CPA7090 - Entry not Journaled to journal QSQJR N hit maximum sequence # 2,147,483,136

12699 - CPA7090 - Entry not Journaled to journal QSQJR N hit maximum sequence # 2,147,483,136

rdisp/max_wprun_time - Maximum work process run time   CPI1466 during Backup  
This documentation is copyright by SAP AG.
SAP E-Book

CPA7090 - Entry not Journaled to journal QSQJR N hit maximum sequence # 2,147,483,136

It has more to do with the number of bits used to store the value. If you just
rolled the number over, added one to the value, it would be the equivalent of 0,
which would cause problems with recovery. It is too bad that there isn't a
warning or something that is sent to someone but then there would be issues with
that.

Alan

-----Original Message-----
From: Anderson, Doreen [mailto:dandersoZballhort.com]
Sent: Tuesday, January 27, 2004 4:47 PM
To: DoNotReply@consolut.eu
Subject: RE: CPA7090 - Entry not Journaled to journal
QSQJRN hit maximum sequence # 2,147,483,136


See below especially - "Last sequence number" value

Display Journal Receiver Attributes

Receiver . . . . . . . : QSQJRN4484 Library . . . . . . . : R3P01JRN

Journal . . . . . . . : QSQJRN Library . . . . . . . : R3P01DATA
Threshold (K) . . . . : 200000 Size (K) . . . . . . . : 8412
Attach date . . . . . : 01/26/04 Attach time . . . . . : 20:18:04
Detach date . . . . . : 01/26/04 Detach time . . . . . : 23:13:34
Save date . . . . . . : 01/27/04 Save time . . . . . . : 10:09:03
Text . . . . . . . . . : Created by upgrade

Auxiliary storage pool . . . . . . . . . . . . . . : 2
Status . . . . . . . . . . . . . . . . . . . . . . : SAVED
Number of entries . . . . . . . . . . . . . . . . . : 5186
Minimized fixed length . . . . . . . . . . . . . . : NO
Receiver maximums option . . . . . . . . . . . . . : 0
Maximum entry specific data length . . . . . . . . : 30064
Maximum null value indicators . . . . . . . . . . . : 133
First sequence number . . . . . . . . . . . . . . . : 2147477951
Last sequence number . . . . . . . . . . . . . . . : 2147483136


-----Original Message-----
From: Vincenzo Boesch [mailto:vboeschZbluewin.ch]
Sent: Tuesday, January 27, 2004 3:29 PM
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




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


Durban Tours - Südafrika Safari

CL_GUI_FRONTEND_SERVICES - Frontend Services   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 7666 Date: 20240328 Time: 170451     sap01-206 ( 4 ms )