Kbase P149451: Database not shutting down after an shut command was issued and database log file shows a (334) Mult
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/14/2009 |
|
Status: Unverified
SYMPTOM(s):
Database not shutting down after an shut command was issued and database log file shows a (334) Multi-User session end.
Standard shut command was issued via a batch job.
<time><Multi/Single> session end. (334)
Multi-User session end. (334)
BROKER : (-----) Removed shared memory with segment_id: 3702793.
_mprosrv process appears to be getting CPU even though the database is shutdown according to the log file.
Logout messages were still being received 31 minutes after the (334) message.
Database logged one local user receiving a kill message 45 minutes after the (334) message was entered in the log file.
.lk file is still present for this database.
dbipcs command showed memory segment for this database was still active.
FACT(s) (Environment):
Red Hat Enterprise Linux 5
OpenEdge 10.2A01 64-bit Service Pack
CAUSE:
Bug# OE00187463
FIX:
Workaround:
1. If _mprosrv is still active for this database, dump a couple of stack traces of the _mprosrv process and save for Progress analysis. Then issue:
proshut <dbname> -F
2. If the .lk file is gone check for active shared memory segments using:
proutil -C dbipcs
If there are still active segments for this database, remove them using the proper OS command.
3. If the _mprosrv is still active for this database then issue an OS kill -9 command for all active sessions against this database.
4. If the process can not be killed then reboot the Server.
5. Restart database via the normal process when ready.