Marco,
Thanks, that fixed it! I hope I didn't overlook some obvious part in the
install documentation on this :) Very novice question.
The following command is what I used:
dbmcli -d TST -u dbm,dbm db_warm
On my system, which is a pretty clean Windows 2000 install -- the SAP
installer didn't set up many of the paths correctly, dbmcli would not work,
it put xserver service in the wrong path, so it took me some time to track
down these problems. I'll be doing a clean install on another system soon
and will report the details once I watch how it does it on a different
system too.
Thanks again.
Stephen
-----Original Message-----
From: Warga, Marco, X., ASCS/US [mailto:MXWarga@stripped]
Sent: Friday, May 11, 2001 9:39 AM
To: 'Stephen Gutknecht (RoundSparrow)'; 'sapdb-general@stripped'
Subject: RE: Basic questions... Windows 2000 - TEST database fails after
r eboo t
> It appears to me like each database I create gets a unique service to
> stop/start. Why is this? What exactly am I stopping and starting?
By default the service start brings the corresponding database into
opreration mode 'cold'.
Database connections are not possible in this mode, its intended for
maintenance only.
To connect with your client application, start up the database to mode
'warm' first using either the 'dbmcli' executable or (on Windows you will
prefer that) the 'SAP Database Manager'.
There is a database configuration parameter you can set to make the DB start
up into 'warm' mode on service startup. I'm currently at work and cannot
check what its name was though, take a look at the parameters.
[snip]
Good luck,
Marco
