|
Back to BaBar Bookkeeping docs
17 Aug 2006 :
With the new skim cycle (R18d) people have now come up with a stream
name which is longer than 20 characters long... yeah I know. So the
current schema needs to be changed to allow longer stream names.
SQL statements to change the BookKeeping database can be
found here:
MySQL databases:
modify_streamname_mysql.sql
Oracle databases:
modify_streamname_oracle.sql
04 May 2006 :
Added several indices to the mysql version of the bookkeeping database.
Originally these were not thought to be necessary for normal queries but rather
only for database management. However it turned out that with growing size
of the various tables, in particular the bbk_dsereject table, the missing
indices causes long query times.
SQL statements to change the BookKeeping database can be
found here:
MySQL databases:
add_mysql_indices.sql
23 Nov 2005 :
We are trying to extend the use of the bookkeeping system to
root files which are not collections. But to do this we need to
keep entries with no component or suffix values, and to do this
we need to remove the 'not null' on these fields. These updates
will allow these values in the database to be empty.
These changes are included in the tag of BbkTools.
SQL statements to change the BookKeeping database can be
found here:
MySQL databases:
fix_files_mysql.sql
Oracle databases:
fix_files_oracle.sql
27 June 2005 :
This is a fairly small update that doesn't seem to effect all people. But there
is a column that is allowed to be null in the SLAC database, but not in remote
databases. This causes problems in mirroring for only certain records, and the
columns everywhere need to allowed to be null.
These changes are included in the tag V00-01-00 of BbkTools.
SQL statements to change the BookKeeping database can be
found here:
MySQL databases:
fix_input_ds_mysql.sql
Oracle databases:
fix_input_ds_oracle.sql
7 Apr 2005 :
To help in the management and updating of all types of possible datasets, there
needs to be more columns added to the dataset table. Also there is a desire to
be able to keep condition month info in the bookkeeping to be able to map run
cycles to condition months, and to map relative lumi info to each condition
month.
These changes are included in the tag V00-00-39 of BbkTools.
SQL statements to change the BookKeeping database can be
found here:
MySQL databases:
add_dataset_mysql.sql
Oracle databases:
add_dataset_oracle.sql
9 Nov 2004 :
We are starting the new skim cycle now, and there will be a need to create
datasets of collections based on the skim cycle, and this info. needs to exist
in the Bookkeeping as an atribute of a collection. Also there needs to be a
way of determining which collections have or have not been skimmed for a certain
skim cycle. To do both these things, there needs to be another column in the
table bbk_dseskim called skim_cycle. Also the unique constraint on this table
needs to be changed from just the dse_id to the dse_id and skim_cycle. Which
is another way of stating that each collection can only be skimmed once in any
given skim_cycle. SQL statements to change the BookKeeping database can be
found here:
MySQL databases:
mysql -u <user> -p <database> < add_skimcycle_mysql.sql
Oracle databases:
add_skimcycle.sql
23 June 2004 :
It was recognised that for a few collections from the skim production, some PR collections were not
actually skimmed, even though it is marked as such in the book keeping. This resulted in links
in the database between runs and collections which are not actually there, and these links should
be removed, since they are not in the collections themselves. Database deletes are not mirrored
in the current tools, so to mirror these deletes to remote sites you need to apply these sql.
There is no change in the database schema in this update.
The sql's to run to alter existing database are:
MySQL databases:
mysql -u <user> -p <database> < delete_missing_runs.sql
Oracle databases:
delete_missing_runs.sql
16 June 2004 :
Need to add a few more columns to the database, the run_nev to track the number of
events in a collection from a certain run, and the rel_id, dse_nev and dse_lumi to
the bbk_dsetodse table to track the released used to create the skim collection, the
number of events and lumi info from the input collection to the skim.
Also in this change there was an error in setting 1/4 of run3 PR collection bad, and this
was updated as an extra 82k run reject entries to the run 3 skim collections. The existance
of this many entries in this table which just shouldn't be there could effect eff. of the
system when creating job tcl file for run3 analysis, and it will be easier (but perhaps
not better) to just delete these entries from the bbk_dsereject table. The delete
sql is included in this database update, just in case you picked up on these record
in a database mirror.
The tables schema includes
this change as of BbkTools tag V00-00-24, The sql's to run to alter existing database are:
MySQL databases:
mysql -u <user> -p <database> < add_nev_others_mysql.sql
Oracle databases:
add_nev_others_oracle.sql
11 June 2004 :
Need to add tables the bbk_table_schema.*, to help manage which collections
need to be skimmed in general for the whole experiment. The schema includes
this change as of BbkTools
tag V00-00-21, The sql's to run to alter existing database are:
MySQL databases:
mysql -u <user> -p <database> < add_skimstate_mysql.sql
Oracle databases:
add_skimstate_oracle.sql
24 May 2004 :
Need to add tables the data_table_schema.*, to track what collections and datasets
are local to a site. These database schemas have been updated as of BbkTools
tag V00-00-19, The sql's to run to alter existing database are:
MySQL databases:
mysql -u <user> -p <database> < add_data_tables_mysql.sql
Oracle databases:
add_data_tables_oracle.sql
17 May 2004 :
Need to add more columns to the dse table, to aid in selects of list of collections with
unique qualities. Also add the dsereject table to track the history of run rejections in
the use of extended collection names. These database schemas have been updated as of BbkTools
tag V00-00-17, The sql's to run to alter existing database are:
MySQL databases:
mysql -u <user> -p <database> < alterdse_addreject_mysql.sql
Oracle databases:
alterdse_addreject_oracle.sql
28 April 2004 :
Need to drop the uniqueness condition on the bbk_dstodse table, to do this run:
MySQL databases:
mysql -u <user> -p <database> < dropunique_dstodse_mysql.sql
Oracle databases:
dropunique_dstodse_oracle.sql
23 February 2004 :
Alter bbkr14.bbk_stream.id and change it from tinyint (4) to
smallint (5) if the db was built with a schema older than BbkTools V00-00-09.
It will try to delete the entry with id=255 if you don't have that
entry and it complains you might remove the delete line and retry the command.
mysql -u <user> -p < alterstreamid.sql
22 February 2004 :
Add column merge_no to the stm_jobs table if the db was built with a schema
older than the one in the BbkTaskManager V00-00-11. Changes applied to
db bbrora.
mysql -u <user> -p < addmergeno.sql
11 February 2004 :
To drop bbk_dsentities.is_imported bbk_runs.bb_counts bbk_runs.mm_counts
bbk_runs.mh_counts columns applies to schema older than BbkTools V00-00-08.
mysql -u <user> -p < dropcolumns.sql
| Last significant update: 12-MAY-2004 |
Expiry date: 08-DEC-2004 |
|
