Kbase P1566: dbman -stop dbname will not shutdown databases.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/25/2005 |
|
Status: Verified
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
SYMPTOM(s):
dbman -stop dbname does not shut down the database
dbman -stop dbname returns message: process still in use
proshut dbname -by returns message: waiting for transaction to complete
Offline database backup cannot take place because database in use
Waiting for requested action to complete (Dbman012)
Database <{0}>, configuration <{1}> failed to stop (DBMan008)
CAUSE:
The database could not be shut down with the proshut command, because the webspeed transaction server was still connected to the database and dbman could also not shutdown the database because the AdminServer was shutdown proir to sending the dbman command.
FIX:
If the AdminServer is stopped first (typically in the shutdown script):
proadsv -stop dbname
The comands to shut other processes:
dbman, asbman, wtbman, nsman
will not work because they need the AdminServer to be running. This is an expected behaviour - The Progress AdminServer does not shutdown databases when it gets shutdown - this behaviour is by design.
The only processes that will be shut down, are those that are shut down automatically when the AdminServer is shut down (ie the ubroker processes).
The order that the brokers (if used) should be stopped in the shutdown script are:
1.) wtbman,
2.) asbman,
3.) dbman,
4.) nsman (optional),
5.) proadsv
Backup of databases can now take place, followed by startup script
It is worth checking the pause interval between shutdown steps.