Kbase P5741: Database shutdown after a process hangs up or is killed
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  10/15/2008 |
|
Status: Unverified
SYMPTOM(s):
User <num> died with <num> buffers locked. (2523)
Disconnecting dead user <number>. (2527)
Stopped. (2520)
CAUSE:
An idle status process detected and decided to be killed by using kill -9. This action has been known to cause the above errors when disconnecting the process on that way.
FIX:
After seeing these error messages an abnormal shutdown of the database will follow. This indicates that the user was killed while holding a lock or latch in shared memory and the database is shutdown to protect data integrity.
This presents a particular problem for Progress as we are not able to trap a kill -9.
In Progress 8.2x and higher the Virtual System Tables should be used to determine if a user has an Active transaction and therefore a lock.
Generate a program using the VST's to determine which processes can be disconnected normally when they do not have any active transaction. The Virtual System table that has this information is _Connect.