Trigger Database Status

Trigger Database Status Elizabeth Gallas – FNAL CD Trigger Working Page http://www-d0.fnal.gov/~gallas/d0_private/trig/trigger.html D0 Databases Meeting January 27, 2003 D0 Trigger Db Status

Outline • Database corruption • Cause, Recovery, Plans • Need help from D0Db Support • Speeding up TDB Views • Diana and Elizabeth • TriggerDbServer Exception Handling • Steve, Jeremy, Elizabeth • Top priority tasks Done D0 Trigger Db Status

Trigger Database Corruption • Data Corruption • Whenever a STATUS or STREAM was updated using the STATUS menu, element descriptions containing <cr> were updated to contain only the characters proceeding the <cr> • Cause: • Bug: • Web form text box rather than text area box • a bug fix by E in Jan 2002 to make this form useable. • Root: • This interface was quickly put together and has many features that • make data corruption of this type very difficult to detect. • Make this interface difficult to use • Data Recovery • E’s backups – not good because • Typically done after STATUS flags set • Can we use RMAN backups? • For all trigger elements: • Update to use the element description which is the last date it had stat_curr=“local” unless a later (modify_date) description has a longer length D0 Trigger Db Status

Fix the Entry programs: More details in email message. All changes are to existing methods. • DB: 7 columns to TL_MAPS table: • (2) needed for correct (robust) implementation of streaming • (5) include “L2 forced unbiased” and other similar programming needed online ASAP • Trigger Db Server (*TTriggerList): • Remove redundant methods which were added for the streaming ‘test’ • Add the 7 new columns to TL struct, GIUD methods • Check all columns for special characters (bug fix) • STATUS Entry interface • Use textarea box • Update the record retrieved from the database, not from the back of the form • When the SafeUpdate is successful, report the old/new STAT_CURR, STREAM or Description for the column(s) that changed • Trigger List Entry • Modify to have options to enter the 7 new columns by trigger list or by trigger using updated server methods for trigger list. • Streaming Report Interface D0 Trigger Db Status

Need help from D0Db Support • Recovery of lost data (Jeremy/??) • Trigger Db Server (Steve/Jeremy) • Exception handler bug • Does not return database exceptions DONE TODAY v2_2_1 db_server_base • View Performance (Diana) • Trigger database views are slow • Many views used to generate the standard Trigger List Report (TLR) • This is report done most often • Elizabeth looked at TLRViews • Removed where ever possible: • Case insensitivity • Use of like when ‘=‘ can be used • Sent resulting example views to d0db support • Any progress ? • Next views to evaluate are the ones used by the xml generator D0 Trigger Db Status

Needed right away (Jan03) • Jeremy / Adam: • Get streaming into a production mode • No NEW methods (changes to existing methods). Changes are well defined. • Jeremy / Elizabeth • Level 2 preprocessor entry complete • Change L2 Term entry to add L2PP • Elizabeth: • Database queries for getting trigger cross sections as a function of time • xml generator changes • L2 Calorimeter (extended eta) • L2 forced unbiased (etc) programming • L2 preprocessor programming • Python v 2 fixes (still not done) and integrating common routines in Entry and Report Interfaces in order to write L2 Preprocessor report interface • Propagation of STAT_CURR flags • New Server method • Transformation program upgrade: • L2 Terms, L2 Preprocessors, L3 Terms D0 Trigger Db Status

Trigger Database Status