dbload help needed
Posted in 1991
Topics: Transactions, Locking & Isolation
A couple of questions about some dbload problems we've encountered:
I. I am trying to put together a shell script that does something like:
if dbload -d xx -c yy -l zz
then ........
However, dbload returns any number of (positive) values, which seem to
vary (somewhat) with the number of rows loaded. The best I can get for
consistency is that a retcode of 1003 means that it core dumped.
Anybody have any explanation for the retcodes? or is there none?
II. Core dumping leads to the second question:
TFM says that the command line option -n x will cause it to commit or, if
you're not using transaction logging, to write a message to the terminal
every x lines. For us, it core dumps. Discovered that -n 0 seems to
disable the feature. Bug? Known problem?
We are running 2.10.00B on an Intel 320, Xenix 3.5
-----------------------------------------------------------------------------
| Bruce Funk OLD ==> funkb@zweibrucken-emh1.army.mil|
|C, *IX SUPPORT TEAM NEW ==> funkb@worms-emh6.army.mil |
|USAISEC-EUR (MINI/MICRO DIV)________AUTOVON/ETS: 383-7780-------------------|
|BOX 1478 | Any resemblance between me and reality |
|APO NY, 09056 | is strictly coincidental |
-----------------------------------------------------------------------------