Changes between Version 2 and Version 3 of drmsCheckRecnum


Ignore:
Timestamp:
06/16/14 13:05:45 (10 years ago)
Author:
jennifer
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • drmsCheckRecnum

    v2 v3  
    11 
    22== Checking a record number == 
     3This may be required if Slony processes have stalled or if for some reason, JSOC records are offline.  The JMD may stop trying to download them.   
     4 
    35 
    46If the URL : 
    … …  
    2931}}} 
    3032 
    31 Indicating that the sunum does not exist at JSOC (the NA's indicating that things like the path are not properly set). It could be that this means that you have to contact JSOC to resolve the problem. Even after the problem is resolved, it could be that the local JMD has (correctly) marked it as being offline and won't download it until the JMD's internal database is cleaned out by doing something like : 
     33Indicating that the sunum does not exist at JSOC (the NA's indicating that things like the path are not properly set). It could be that this means that you have to contact JSOC to resolve the problem. Even after the problem is resolved, it could be that the local JMD has (correctly) marked it as being offline and won't download it until the JMD's internal database is cleaned out.  To see the records marked "OFLN" (offline) by the JMD, type 
     34 
     35{{{/opt/JMD/bin/jmdij 
     36select from drms.su_cache where state='OFLN'; 
     37exit; 
     38}}} 
     39 
     40 
     41The JMD is doing is refusing to download those records because it thinks they are offline.  To clear it, do something like : 
    3242 
    3343{{{ 
    … …  
    4555The path /opt/JMD may be different on your system depending on where the JMD is installed. 
    4656 
     57You will not lose data since the JMD will now be able to try downloading those records again.  It may be best to wait until the JSOC has confirmed they are available, however.