This page last changed on Aug 25, 2009 by tether.
Duplicate run entries for the same delivery ID
Sometimes the summary page will show the same run over and over again for the same delivery ID. The root cause may be that the database table ISOC_FLIGHT.FCOPY_INCOMING has the same downlink ID for two different science deliveries (VC08 tarballs). This can happen if two science deliveries arrive within a few minutes of each other. The data goes into L1 processing with the correct ID; it's only the updating of this table that gets it wrong.
In a terminal window that has the ISOC production environment set up execute the following commands (where nnn stands for the ID of the earliest delivery with the problem):
sqlplus '/@isocflight'
select * from fcopy_incoming where downlink_id >= nnn order by incoming_pk;
You should see two deliveries with INCOMING_PK values close to one another which have the same DOWNLINK_ID. These IDs are assigned by incrementing a counter each time a science delivery arrives. It should be obvious therefore which ID should have been assigned to the second delivery with the same ID; normally you just have to bump it up by one:
update fcopy_incoming set downlink_id=nnn+1 where incoming_pk=xxx;
quit
 | Have a L1 expert check that this is in fact the correct delivery ID. |
|