1 / 6

Database Procedures - handing over DB Operations

Database Procedures - handing over DB Operations. Nick West - Who retires in 2 weeks !!. Database Procedures: What are they?. Note 1 When conflicts are identified, correct by fixing the bad rows and rebroadcasting. Note 2 Use full set to prime new Slave sites.

bisa
Download Presentation

Database Procedures - handing over DB Operations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Database Procedures- handing over DB Operations Nick West - Who retires in 2 weeks !!

  2. Database Procedures: What are they? • Note 1 • When conflicts are identified, correct by fixing the bad rows and rebroadcasting. • Note 2 • Use full set to prime new Slave sites. • Use to reprime selected tables on farm databases as dictated by processing needs. • Everything documented:-http://www-numi.fnal.gov/offline_software/srt_public_context/DatabaseMaintenance/doc/dbmauto_master.html

  3. Master Database Manager: Responsibilities • Operations • Ensure the following processes run • Software • Support for DatabaseInterface and DatabaseMaintenance packages

  4. DB Manager Handover:The Plan • Jon Paley is the new DB manager • Ideally all operations via generic account • Simplifies handover • For Farm Slave use minfarm account • Not possible for FNAL Master and Soudan Slave • Have not solved AFS access for cron jobs • Instead have used nwest account • To ameliorate the problem make all files group writable • Anyone in group can run scripts • After transition complete transfer ownership to new manager.

  5. DB Manager Handover:Progress • The Bad News • Less than ideal. • Had hoped by now that Jon would have been in harness for at least a month. • The Good News • Jon has been in contact with me. • He is keen to make significant progress this week. • Software • Jon has looked over the code. • Operations • Have established Jon can do import/export at FNAL by hand. • Checksum generation not checked but should not present new problems. • Have identified (and hopefully corrected) problems creating priming files. • Aim to get cron jobs running before the end of this meeting.

  6. DB Manager Handover:Concerns • Software Support • Risk: Require change and Jon needs time to understand code. • Impact: Mild – very unlikely that any code change would be urgent. • Routine Operations i.e. automated operations • Risk: Jon not running cron jobs by time I retire. • Impact: Mild – system will continue to roll until he takes over (and Art/Robert help with any residual permissions problems). • Abnormal Operations e.g. FARM repriming or checksum conflicts • Risk: Jon does not have detailed knowledge to quickly deal with problem. • Impact: Potentially Severe – could lose production time (as we did over 2009/2010 Christmas break). However • Fixing problems will be a top priority for Jon • I’ll remain in email contact for the remainder of the year

More Related