×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have some really basic questions on using journals to recover from a bad
SQL based update to a file. The SQL was to update a single field and a
rather small number of records from what I was told, but updated several
hundred thousand before it was stopped. So the file was journaled with
Before and After images.
1st question I assume that what is journaled is the Entire Record not just
what was changed ( say 1 field ), correct?
2nd Question Since the file was in active use and other jobs could have
updated other fields of the modified records after the bad SQL was run I
don't think we can just use RMVJRNCHG cmd to backup those SQL changes and
then run APYJRNCHG from the SEQ directly following the the bad changes. If
we use the APLYJRNCHG to a recorded we rolled back it will just put the bad
data back if my assumption in #1 is correct?
Last question for now, What happens if there are triggers on this file if
we were to use RMVJRNCHG cmd? How about APYJRNCMD?
Thanks
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.
midrange.com
