Changes between Version 4 and Version 5 of drmsSumRm

Timestamp:

04/29/14 08:38:02 (11 years ago)

Author:

niles

Comment:

--

drmsSumRm

@@ -18 +18 @@
 }}}
 
-This happens when an entry for a sunum is in the SUMS database in the sum_partn_alloc table but not in the sum_main table (a situation that can arise in the event of a failed download). The error is not serious.
+This happens when an entry for a sunum is in the SUMS database in the sum_partn_alloc table but not in the sum_main table (a situation that can arise in the event of a failed download). The error is generally not serious. An entry in sum_partn_alloc without a corresponding entry in sum_main generally indicates that a download failed. Hopefully failed downloads are due to a transient event that only lasted a short time, so sum_rm should work its way through the data from that time and get back to deleting data soon.
 
+It's also worth noting that sum_rm is *very* quiet in the event that there are no data for which the effective date is in the past - it does not print anything to indicate that this is the case. The user will have to run this query :
 
-The configuration file is below :
+{{{
+select effective_date from sum_partn_alloc order by effective_date limit 30;
+}}}
+
+to ascertain if this may be the case.
+
+The configuration file for sum_rm is below :
 
 {{{