Kbase P148534: Database not shutting down even though database log file says it is down.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/08/2010 |
|
Status: Verified
SYMPTOM(s):
Cannot start the database because Progress Explorer getting a message that the database is already running.
Database not shutting down after an emergency shutdown was initiated against a bistalled database.
Database was stalled due to server process (_mprosrv) trying to exceed bithold (bi threshold) of 3.9
Emergency shutdown command: proshut dbname -F was issued via a batch job.
Database log file says the db shutdown within 1 minute of the Emergency Shutdown command being issued.
<time><Multi/Single> session end. (334)
Multi-User session end. (334)
proutil dbname -C busy ran via a script indicates that the database is still in use.
Task Manager showing one _mprosrv process running.
_mprosrv process appears to be getting CPU even though the database is shutdown according to the log file.
The PID of the _mprosrv process that is still running is the same _mprosrv process that was trying to exceed the bithold parameter.
FACT(s) (Environment):
This machine only has 1 database running on this machine.
10.1A0228 Hot fix
Windows
OpenEdge 10.1A02 Service Pack
CAUSE:
Bug# OE00187463
FIX:
Workaround:
From a proenv window, issue another emergency shutdown using proshut dbname -F command.
If the hung _mprosrv process does not terminate after the Emergency shutdown, then terminate the _mprosrv process using the Windows Task Manager.
Truncate the bi file (to shrink it back to original size). Can then use bigrow parameter to proutil to alleviate any performance concerns associated with the truncation of the bi file.