Changes between Initial Version and Version 1 of queryDerby


Ignore:
Timestamp:
02/10/14 11:54:49 (8 years ago)
Author:
niles
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • queryDerby

    v1 v1  
     1= Examining the JMD Derby database = 
     2 
     3As discussed, the JMD uses an underlying database. Querying this database can give useful information when debugging the JMD. 
     4 
     5One can connect to the derby database using the $JMD_HOME/bin/jmdij script, which will bring up the "ij>" prompt. This prompt 
     6accepts SQL style queries. For the JMD, the table of interest is named "drms.su_cache", which can be described with : 
     7 
     8{{{ 
     9ij> describe drms.su_cache;           
     10}}} 
     11 
     12The general state of the database can be queried : 
     13 
     14{{{ 
     15ij> select count(*), state, request_type from drms.su_cache group by state, request_type order by REQUEST_TYPE, STATE; 
     161          |STA&|REQUE& 
     17----------------------- 
     187          |OFLN|MIRROR 
     1981         |OFLN|USER 
     20}}} 
     21 
     22 
     23Occasionally the JMD will try repeatedly to download a sunum without success, in which case something like this 
     24will appear in the JMD log : 
     25 
     26{{{ 
     27Jan 28, 2014 9:17:50 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[44]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     28Jan 28, 2014 9:19:50 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[37]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     29Jan 28, 2014 9:21:50 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[49]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     30Jan 28, 2014 9:23:45 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[59]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     31Jan 28, 2014 9:25:45 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[41]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     32Jan 28, 2014 9:27:45 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[54]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     33Jan 28, 2014 9:29:45 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[74]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     34Jan 28, 2014 9:31:45 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[79]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     35Jan 28, 2014 9:33:45 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[64]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     36Jan 28, 2014 9:35:45 AM org.vso.jmd.Downloader.SCPDownloader call INFO: Th ID:[69]; SU:[97359684]; RN:[0];[aia_test.lev1];[USER]; Sz:[9990778]; STP:[SCP]; ST:[FAIL] [N/A] [SAO] 
     37}}} 
     38 
     39In this case, the endless failures are occurring because the vendor in fact no longer serves out these data, so we want to stop trying (this is unusual).  
     40First, we establish if this storage unit number (sunum) is still in the derby database : 
     41 
     42{{{ 
     43ij> select * from drms.su_cache where sunum in (97359684); 
     44}}} 
     45 
     46and if it is, we delete it : 
     47 
     48{{{ 
     49ij> delete from drms.su_cache where sunum in (97359684); 
     50}}} 
     51 
     52 
     53The "ij>" prompt can be exited with CNTL-D, or by entering "exit;". 
     54