Calibration Database Simulation Instructions (Sep 03)

This web page seeks to give a user enough information to run the calibration database simulation. Here is a prescription:

newrel -t 'release' dbase_sim
cd dbase_sim
addpkg CalibDBLoadTest
addpkg SvxCalibDBTables
gmake SvxCalibDBTables.codegen
gmake CalibDBLoadTest.nobin
gmake CalibDBLoadTest.tbin

In this example, 'release' is the most recent (or your favorite) frozen release. CalibDBLoadTest is the core package for the Calib-Dbase simulation. The example assumes that the codegen hasn't been done properly for the release (hopefully not true for you), which is why, as an example, the package SvxCalibDBTables is added and the codegen target is made. What this does is to put various important files (.icc most importantly) into the tmp directory. These are then picked up when you do make the nobin target of the CalibDBLoadTest package.

The most definitive and succinct reference to this software is a readme in CalibDBLoadTest:

CalibDBLoadTest/doc/README.txt

This was written by the code's main author: Jim Kowalkowski. So read this if you want to understand the guts of the code.

Here is an example command line to run the Calibration Simulation writer:

./bin/Linux2-KCC_4_0/CalibDBWriter -dbtype OTL -dblogin /@cdfondev -days 50 -run 88337790 -period 20 -propdb onotl_dev > & ! sep24_1.txt

Here are some comments on the options:

The -dbtype is *very* important. If you don't have this switch right you will get a message "No calibrations are available for writing!" which peversely results from there being no database available to the program. This link is not obvious and took me several days (and the help of jbk to figure out). So get it right! (From the OTL example, you presumably can also have mysql and text as other alternatives).

The -dblogin switch in the above example is set to "external authentication". This means the database figures out who you are and decides whether you have the permissions to write to the database. Notice also that its the dev database so as not to damage anything in the more crucial integration and production databases. Note also that you can only run in external authentication mode from a central machine which is behind the firewall (eg fcdflnx2).

The -days switch is described in the readme.

The -run switch better be different each time otherwise you will get a complaint from oracle that this value has already been used.

The -period switch is also explained in the readme.

The -propdb switch is also very important. This is the source for the Calibration Properties database. I used onotl_dev. I'm pretty sure you have to be consistent with the rest of the command line here: ie both online data bases ("on") and both oracle ("OTL").

> & ! sep24_1.txt just redirects to an output file, overwrites it, and puts the error there too. In tsch (t-shell). And if you're not using tcsh.....then you're smarter than me!

Matthew Martin

Last modified: Wed Sep 24th 10:01 CST 2003 AD