Consultor Eletrônico

Status: Verified

SYMPTOM(s):

WDOG disconnects dead user during online probkup

BROKER 0: disconnects dead user during online probkup

Either the WDOG or the login broker "BROKER 0:" disconnects the dead user with erro 2527

Disconnecting dead user <number>. (2527)

Error (2527) during online prokup during initial phase of backing up the bi blocks

<num> bi blocks will be dumped. (6688)

As soon as the bi blocks have been backed up (5460):

End backup of Before Image file(s). (5460)

SYSTEM ERROR: bad latch wake usr <num> latch 1 waiting for 0. (3710)

Fatal latch error detected during client logout brings database down

CAUSE:

Bug# 20040511-012

CAUSE:

The watchdog is fully functional during online backup and was doing its job. In the case a WDOG process is not started, the BROKER would have handled these errors.

Latch 1 is a MTX microtransaction in this case, detected during logout which causes the broker to shutdown, as it is a fatal condition. The problem is caused by the fact that when a client dies while queued for a latch, the cleanup code does not remove the client's entry from the latch queue. Later, whenever the process that was holding the latch releases it, it tries to wake up the dead client. But the dead clients usrctl has already been cleared from memory and the latch code sees that that user wasn't waiting for any latch so it brings the database down.

FIX:

Upgrade to Progress 9.1E04

Upgrade to Open Edge 10.0B05

Alternatively, for Enterprise Database Licenses, set a value for -spin on database startup to avoid this problem.