Error 1124

Severity

20

Message text

Failed to get lock on allocation page %ld.

Explanation

Adaptive Server uses allocation pages to track space in the database. Allocation pages are updated when an object’s space requirements change.

Adaptive Server raises error 1124 due to the following sequence of events:

• A server process acquires a lock on an object’s allocation page to allocate pages for the object.

• An exception occurs during allocation that requires “undoing” the allocation steps.

• The server is unable to acquire a lock necessary to abort the allocation, resulting in error 1124.

This error may be accompanied by a kernel error (“Current process infected with %d”); error 945 (“Unable to locate page %ld for database id %d in the in-memory copy of sysusages (spid=%ld). This is an internal error. Please contact Sybase Technical Support.”); error 1205 (“Your server command (family id #%d, process id #%d) was deadlocked with another process and has been chosen as deadlock victim. Re-run your command.”) or other errors.

Error 1124 is raised when Adaptive Server has a problem rolling back space allocation.

Action

When error 1124 is accompanied by a 945 error on tempdb (dbid = 2) that is not resolved by shutting down and restarting the server, there may be insufficient space on tempdb or a problem with tempdb storage.

Resolve these problems using the instructions in the section “Reducing the size of tempdb” in the most recent version of the Troubleshooting and Disaster Recovery guide.

In all other instances of the 1124 error, contact Sybase Technical Support.

Additional information