Kbase P147481: Emergency shutdown occurs after bi threshold is reached and database is stalled and a normal shutdow
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/08/2010 |
|
Status: Verified
SYMPTOM(s):
Emergency shutdown occurs after bi threshold is reached and database is stalled and a normal shutdown has began
BI File Threshold size of <size+identifier> has been reached. (9239)
SRV 27: (9239) BI File Threshold size of 1.5 GBytes has been reached.
Forward processing stalled until database administrator intervention. (6560)
SRV 27: (6560) Forward processing stalled until database administrator intervention.
Server shutdown started by <user-id> on <tty>. (542)
Begin normal shutdown (2248)
Emergency shutdown initiated... (5316)
SRV 27: (5316) Emergency shutdown initiated...
mtLockWait: umLockWait returns . (3721)
SRV 27: (3712) SYSTEM ERROR: mtlatch 2, holding 0x12.
Latchid 2 is the USR latch that deals with usrctl and misc other structures.
** Save file named core for analysis by Progress Software Corporation. (439)
Stack trace from _mprosrv reads:
latlatch
dbUserDisconnect
FACT(s) (Environment):
Database was started with -bistall parameter.
x86_64 (AMD64/EMT64)
OpenEdge 10.1B
CAUSE:
Bug# OE00185796
CAUSE:
Server was attempting to disconnect a user as a part of the normal shutdown process but could not due to the Bi Threshold having been reached. This resulted in the SRV process terminating holding the USR latch and then an emergency shutdown of the database.
FIX:
This is expected behavior because when attempting to shutdown a database normally, transactions may need to be rolled back. In this case, transactions cannot be rolled back because 1) the BI threshold has been reached and 2) the database is in a stalled state. Recommendation would be to increase the bi threshold (-bithold) instead of bringing down the database immediately. Once the threshold is increased, the database can be brought down normally or the database can remain online while the Database Administrator investigates the cause of the excessive bi growth. A request OE00185796 has been made into Development to add additional messages to the log file (or possibly to the screen as well) indicating that a normal shutdown is not possible in this state and that an emergency shutdown will occur.