On 23 Aug 2005 at 10:25, Guido Klapperich wrote:

>of limbo transactions, but they never had been a problem. But now it
>has been the first, that a limbo transaction causes a serious problem.
>No user was able to log in to the database neither the user, who
>started the replication nor any other user. They all get the error:
>record from transaction 32141 is stuck in limbo.

May be your application updates a table on login?

--
SY, Dimitry Sibiryakov.