Trigger Database Status

1
Trigger Database Status

• Elizabeth Gallas FNAL CD
• Trigger Working Page
• http//www-d0.fnal.gov/gallas/d0_private/trig/tri
  gger.html

D0 Databases Meeting January 27, 2003
2
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
3
Trigger Database Corruption

• Data Corruption
• Whenever a STATUS or STREAM was updated using the
  STATUS menu, element descriptions containing ltcrgt
  were updated to contain only the characters
  proceeding the ltcrgt
• 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
• Es 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_currlocal unless a
  later (modify_date) description has a longer
  length

4
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

5
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

6
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