Subject | limbo transaction prevents user login |
---|---|
Author | Guido Klapperich |
Post date | 2005-08-18T18:51:34Z |
We have a FB database in the headquarter and several sales
representatives with a local copy of the database on their laptops. The
sales reps replicate every day their database with the database in the
headquarter via ISDN or DSL. Sometimes it happens, that the connection
between the laptops and the server gets interrupted while they
replicate. Until today this has never been a problem, but today we had
the problem, that nobody in the headquarter could login to the database.
They all got the error: record from transaction 32141 is stuck in
limbo. I know what limbo means and I have been able to repair the
database with gfix, but I don't why a single limbo transaction prevents
all user from login. Can someone please explain it to me.
Regards
Guido
representatives with a local copy of the database on their laptops. The
sales reps replicate every day their database with the database in the
headquarter via ISDN or DSL. Sometimes it happens, that the connection
between the laptops and the server gets interrupted while they
replicate. Until today this has never been a problem, but today we had
the problem, that nobody in the headquarter could login to the database.
They all got the error: record from transaction 32141 is stuck in
limbo. I know what limbo means and I have been able to repair the
database with gfix, but I don't why a single limbo transaction prevents
all user from login. Can someone please explain it to me.
Regards
Guido