|
Thanks, Alexei, I'm very familar with the journallling process; my concern is that we haven't had this escalated creation of journal receivers before for a Qrecovery library. We've encountered it during Y2K & Euro testing, where vast amounts of (copies of) production files were being updated at weekends, and the test -journalling spiralled. I interpreted this having as a known cause & the decision was made, not to resize the receivers, as it was an atypical growth, but to suspend journalling on some files & delete receivers as we went along on most. So now I see it happening again, & this time populating a journal in QRECOVERY. My concerns are; - What's causing the increase & how can I tell ? (What kind of objects are affected - does it warrant a change in system administration & monitoring) - If the changes are being stored to facilitate recovery of part of the DB, should we be throwing receivers away so fast ? (System-managed, delete on chgjrnrcv, threshold is currently 5,000, so the receivers are being zapped faster than they could be backed up) All suggestions gratefully received, Thanks, Fiona +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.