> What do you mean you load the script via python.
I mean this:
echo "Load database system tables:"
x_python $IND_PROG_DBROOT/env/lsystab.py \
-v \
-u $DBA_USERNAME,$DBA_PASSWORD \
-dompwd domain \
-d $SERVERDB \
-l en
test $? = 0 && echo "OK" || { echo "not ok"; exit 1 }
> This script is part of the database installation via the repmcli
> and not used by now. It's for further use but tested without
> problems. So how do you call it and why?
How: see above
Why: I am updating my SAP DB RPM. When SAP DB 7.2.4.9 came out, I
created my own RPM. Basically I wanted something clean and lean, so I
left out everything that was not needed. I also added
etc-init.d-scripts for vserver and the databases, so that the whole
thing fit's into a linux way of doing things.
The excerpt from above is from my createsapdb script. I did not use
dbmcli ... load_systab ... because this in turn calls xload. And xload
is not very good supported *) anymore and, to my best knowledge, will
eventually go the same way as xquery, to /dev/null.
So I decided to go the Python way and get rid of xload/xquery/xuser &
co (pgm/load, pgm/query etc).
I have a plethora of helperscripts that get our projects up and going
in minutes, e.g. createsapdb, dropsapdb, sapsql (basically ireport.py
with auto-less-mode and readline-history), sapload/sapunload
(loads/unloads single tables) and so on. They are either running as
shell with repmcli or in python.
Current sizes of my rpms are about:
944kB sapdb
4640kB sapdb-server
~ 940kB sapdb-odbc
~1000kB sapdb-precompiler
*) try xquery in a KDE konsole and you know what I mean.
--
MN-Logistik GmbH http://www.mn-logistik.de
Holger Schurig Network Administrator
Dieselstr. 18
61191 Rosbach v.d.H�he
Tel: 06003/9141-0 Fax: 06003/9141-49
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
