При загрузке Галактики 5.84 выскакивает ошибка.
Запись заблокирована. Код ошибки:84. Таблица N59.
Причём только в одной базе. а в других всё хорошо.
Как исправить ошибку.
Модераторы: m0p3e, edward_K, Модераторы
-
edward_K
- Заслуженный деятель интернет-сообщества
- Сообщения: 5187
- Зарегистрирован: 29 мар 2005, 17:49
- Откуда: SPB galaxy spb
атрибуты файла проверте.
вообще help смотрите первасива.
84: The record or page is locked
An Insert, Update, or Delete operation attempted to lock an index page to insert or delete a key value. Have your application check for this status code and retry the operation if the status code is returned.
When using a NetWare server engine, you can receive this status code when running an application on a Win95 client if the NetWare operating system runs out of record locks. To solve this, increase the "maximum record locks per connection" and, if necessary, the "maximum record locks" (system wide limit) on the NetWare server.
The application tried one of the following:
Applied a no-wait lock on a record that is currently locked by another application
Tried to access a file in a no-wait transaction while another application holds one or more active record locks in that file
Tried to update or delete a record locked by another application.
The application can use either of the following recovery methods:
Retry the operation until it is successful. This can be the simplest and quickest solution for a network with light to moderate use.
Note
Applications should limit the number of retry attempts when status 84 is received inside a concurrent transaction. Otherwise, the application might enter a deadlock situation with another transaction. If status 84 is still received after a few retries, abort the transaction and then attempt the transaction again.
Use the wait option (+100/+300) instead of the no-wait option (in versions that support the wait option).
вообще help смотрите первасива.
84: The record or page is locked
An Insert, Update, or Delete operation attempted to lock an index page to insert or delete a key value. Have your application check for this status code and retry the operation if the status code is returned.
When using a NetWare server engine, you can receive this status code when running an application on a Win95 client if the NetWare operating system runs out of record locks. To solve this, increase the "maximum record locks per connection" and, if necessary, the "maximum record locks" (system wide limit) on the NetWare server.
The application tried one of the following:
Applied a no-wait lock on a record that is currently locked by another application
Tried to access a file in a no-wait transaction while another application holds one or more active record locks in that file
Tried to update or delete a record locked by another application.
The application can use either of the following recovery methods:
Retry the operation until it is successful. This can be the simplest and quickest solution for a network with light to moderate use.
Note
Applications should limit the number of retry attempts when status 84 is received inside a concurrent transaction. Otherwise, the application might enter a deadlock situation with another transaction. If status 84 is still received after a few retries, abort the transaction and then attempt the transaction again.
Use the wait option (+100/+300) instead of the no-wait option (in versions that support the wait option).