Lock Manager Error Messages 1014004 to 1014043

This document describes lock manager error messages and information messages. The discussions of error messages include possible causes and possible solutions for each problem, with links to the Essbase Database Administrator's Guide and the Essbase Technical Reference for more information on how to fix errors.

Click an error message number to view information about that error message.
1014004 1014042
1014018 1014043
1014025
1014026
1014027
1014028
1014031
1014032
1014033
1014034
1014035
1014036
1014039
1014040
1014041

1014004 Unable to Update Members Which Have Not Been Locked

Possible Problems
Essbase cannot update the members because the members are not locked.

Possible Solutions

1014018 Members Currently Locked by another transaction

Possible Problems
Essbase cannot update the members because they are locked by another user.

Possible Solutions

1014025 Unable to update database while in readonly mode for backup

Possible Problems
Essbase cannot update the database because the database is in read-only mode.

Possible Solutions

1014026 Requested lock is currently held by another transaction, and waiting is currently not allowed.

Possible Problems
Essbase cannot lock the object because it is currently locked by another transaction.

Possible Solutions

1014027 Transaction transactionHandle is deadlocked with transaction transactionHandle.

Possible Problems
Essbase cannot complete the transaction because two or more users tried to lock the same two blocks in the opposite order at the same time. For example, user1 tried access block 1 and then block 2, while user2 tried to access block2 and then block 1.

Possible Solutions

1014028 Transaction transactionHandle is waiting for transaction transactionHandle.

Possible Problems
Essbase cannot complete the transaction because the current transaction is waiting for a deadlocked transaction.

Possible Solutions

1014031 Essbase could not get a lock in the specified wait time.

Possible Problems
Essbase could not lock the object in the user-specified wait time.

Possible Solutions
See Also
1014032


1014032 Essbase could not get a lock. Essbase will keep trying until it reaches the specified wait time.

Possible Problems
Essbase could not lock an object. This message will be repeated every thirty seconds until the object can be locked or until the user-specified wait time is reached.

Possible Solutions
See Also
1014031


1014033 Failed to allocate lock manager event. operation aborted

Possible Problems
Essbase cannot allocate the lock manager event because it is out of memory.

Possible Solutions
Check the physical memory on the server computer. In a Windows environment, 64 MB is the suggested minimum for one database. In a UNIX environment, 128 MB is the suggested minimum for one database. If the error keeps occuring, add more memory to the server computer.


1014034 Failed to create lock manager event. operation aborted

Contact Hyperion Technical Support.


1014035 Failed to allocate lock manager waiter node. operation aborted

Possible Problems
Essbase cannot allocate the lock manager waiter node because it is out of memory.

Possible Solutions
Check the physical memory on the server computer. In a Windows environment, 64 MB is the suggested minimum for one database. In a UNIX environment, 128 MB is the suggested minimum for one database. If the error keeps occuring, add more memory to the server computer.


1014036 Lock request would block, but waiting is not allowed.

Possible Problems
The block this transaction is trying to lock is locked by another transaction. Currently, Essbase is configured to not allow waiting, so the current transaction cannot wait to lock the block.

Possible Solutions
Set Essbase to wait a specified amount of time to lock a block.


1014039 Unable to perform a write operation to database databaseName while the database is in read-only mode.

Possible Problems
The listed database is in read-only mode because the administrator issued the BEGINARCHIVE command to back up the database.

Possible Solutions
Wait until the archival process, starting with the BEGINARCHIVE command and ending with the ENDARCHIVE command, is finished. When the archival process finishes, issue the ENDARCHIVE command.


1014040 Failed to get the current thread's handle. operation aborted

Contact Hyperion Technical Support.


1014041 Failed to get the current thread's base priority. operation aborted

Contact Hyperion Technical Support.


1014042 Failed to get the current thread's high priority. operation aborted

Contact Hyperion Technical Support.


1014043 Error encountered while releasing a lock in database databaseName.

Possible Problems
An error occurred while Essbase was waiting to release a write lock.

Possible Solutions
Contact Hyperion Technical Support.