|
4 Mar 2003
|
Known Causes of Corruption in InterBase Databases
InterBase is, in general, a very stable database server and corruption is rare. When corruption does occur, then, it is important to determine the cause of the corruption. This article describes circumstances that can cause corruption.
|
Craig Stuntz
|
Contributed Article
|
|
|
|
|
24 Jul 2000
|
Error Message: statement failed sql code -104, lock manager out of room
Increasing shared memory may resolve the problem
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
fatal lock manager error: Semop failed, errno=22
This error is due to running out of semaphores or shared memory.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
fatal lock manager error: Semop failed, errno=28 [-no space left on device]
This error is due to running out of semaphores or shared memory.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
fatal lock manager error: inconsistent lock table version number
Possible cause is an application that was compiled or linked with another version of InterBase, one that had a different lock table version.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
fatal lock manager error: invalid lock id() errno=??
The meaning of this error isn't always the same.
|
Borland Staff
|
FAQ
|
|
|
|
|
24 Jul 2000
|
Getting 'Lock Manager out of room' error
Increasing V4_LOCK_MEM_SIZE should resolve the problem
|
Borland Staff
|
FAQ
|
|
|
Connect with Us