The journal receiver objects grow with each insert, update, and delete that
occurs over the tables being journaled. As a result, they can grow very
large, very quickly.
After a journal receiver object reaches a threshhold size, a new one will
get created, and new journal entries get written to the new journal
receiver. Splitting the activity to a new journal receiver object allows
the organization to save the older journal receivers, and to delete the
older ones.
Most companies I've worked for, tend to only keep the journal receiver
objects online for about 2 or 3 days, due to the DASD they consume. If you
have a good journal scraping tool, the contents of the journal receiver
objects can be incredibly useful for diagnosing issues in production and/or
testing, hence if you can afford the DASD consumed, I recommend keeping
them online longer.
I made a journal scraping tool years ago that would take journal receiver
data, and turn it into easily query-able data. Without such a tool,
interpreting the data in the journal receiver objects is quite tedious.
Over the years, that tool has helped me find many root causes for issues,
very efficiently, that would have been very difficult and/or very time
consuming to diagnose otherwise.
P.S. for tables to participate in a commitment control unit of work, they
have to be journaled. The contents of the journal receivers is what the
system uses to ROLLBACK a transaction, if requested.
Mike
date: Fri, 23 Oct 2015 17:33:12 +0000
from: Justin Dearing <zippy1981@xxxxxxxxx>
subject: Re: Foreign key causing Error:55019 Message:SQLSTATE=55019
SQLCODE=-7008
Ok, I'll try that next time I'm in front of the computer. Do I have to do
anything to maintain the journal? Does it just grow with every insert or
update?
midrange.com
