Main Links

• Introduction
• Slave Site Operation
• Database Priming
• Master Site Operation
• System Files
• Distributing Update Files
• Contact mail
• Distribution Validation System
• Using KERBEROS
• Status
• Rules on SEQNO, INSERTDATE and CREATIONDATE
• Data Mappings

Database Distribution

DBMauto can only distribute Dbi compliant database tables i.e. ones that come in pairs, the main data table and an auxiliary (VLD) validity range table.

The flow of data is shown schematically in diagram. At the heart of the system is the Master Database at Fermilab. Most database updates enter the database realm here. At regular intervals the DBMauto job dbmjob is used to export all recently updated data and these export files are distributed to all other databases where the data is imported if not already present. This is done by the local database manager again using DBMauto. These primary data flows are shown in red.

Smaller amounts of data come from secondary databases e.g. at CalDet and these are exported up to the Master Database where they join other up

Depending on what you want to do or your interests are, you should look at pages as follows:-

• If you are a local database manager and want to set up DBMauto at a local (Slave) site:-
  • Slave Site Operation
• If you are a master database manager want to set up DBMauto at a Master site:-
  • Master Site Operation
• If you are a Table Czar or plan to write data to the database:-
  • Table Czars
  • Rules on SEQNO, INSERTDATE and CREATIONDATE
• If you just have a general interest and want to know more:-
  • Introduction
  • Status
  • Migration