1. May 21, 2004ElizabethGallas -- D0 Luminosity Db1 D0 Luminosity Database Status Elizabeth Gallas Fermilab Computing Division / D0 Computing and Analysis Group D0 Luminosity Meeting May 21, 2004

2. ElizabethGallas -- D0 Luminosity Db2 Luminosity Database Schema

3. May 21, 2004ElizabethGallas -- D0 Luminosity Db3 Fairly Recent Changes STATUS FLAGS –Status flags are no longer called ‘masks’ because they are not packed words –8 sets of tables storing status flags STATUS_EXPLAIN_% (tk,lbn,lt,pfc,ls,tr,lf,rf) STATUS_TO_% (tk,lbn,lt,pfc,ls,tr,lf,rf) –A set of centralized STATUS flags in LBN table (LBN) – implementation indefinite at this point Connection to file processing (Thanks Marco) –plan laid out for PRD_FILE_CHKS tables (3) Data Quality by LBN (Thanks Stefan Soldner…) –plan laid out for LBN_QUALITY tables (5)

4. May 21, 2004ElizabethGallas -- D0 Luminosity Db4 New Integer Primary Keys for 3 tables: Steve White (FNAL CD) is building lum_db_server –the current database server generator can’t handle more than 3 primary keys –he looked at expanding this limit to 4 primary keys claims this will be a BIG problem –therefore, Steve and Anil have been changing 3 tables pk’s: LBN_TRIGGER.LT_ID LBN_STREAM.LS_ID LBN_QUALITY.LS_ID –there are positive and negative aspects to this change, but we really had no option – We had to change to use these integer keys in order to get Steve to build a db server. –they agreed they would make the changes in Oracle Designer and have not gotten it right yet.

5. May 21, 2004ElizabethGallas -- D0 Luminosity Db5 The Status of STATUS_Records Status records – what are they ? –the RULE: indicate something is WRONG with that data the entered value in a column indicates bad data quality –example: checksum_file and checksum_onl do not agree the value in a column is missing from the input dictionary –example: exp_lum_nim the value in a column was changed so that it met db constraints –example: LBN_TRIGGER.EG_NUM has value > 10 (database constraint: 1 or 2 digit integer) –the EXCEPTION: QUALITY TABLES we want to enter good and various forms of bad just like in Run Quality these records will be inserted by web/comline programs (not Helena’s programs) Status records : where do they go? –STATUS_EXPLAIN_% - store each type of condition/description –STATUS_TO_% - store the condition id and the record for which it occurs Status records are not being inserted right now –Helena/Tim are making a list –Helena is adding to the list when she finds questionable inputs