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 Analytic Services
Database Administrator's Guide and the Analytic Services Technical
Reference for more information on how to fix errors.
Click an error message number to view information about that error message.
1014004 Unable to Update Members Which Have Not
Been Locked
Possible Problems
Analytic Services cannot update the members because the members are
not locked.
Possible Solutions
1014018 Members Currently Locked by another transaction
Possible Problems
Analytic Services cannot update the members because they are locked
by another user.
Possible Solutions
- Wait a few minutes and retry the operation to allow
the other active user's process to finish.
- See if another user has locked
the file.
- If this error happens frequently, make sure that
users are logging off Analytic Services correctly.
1014025 Unable to update database while in readonly
mode for backup
Possible Problems
Analytic Services cannot update the database because the database is
in read-only mode.
Possible Solutions
- Wait until the archival process, starting with the
BEGINARCHIVE command
and ending with the ENDARCHIVE
command, is finished.
- If the archival process is finished, be sure that
the administrator issues the ENDARCHIVE command.
- If you are using ESSCMD, you may need to add sleep
commands to make sure that the archive process is completed before
the next process begins.
1014026 Requested lock is currently held by another
transaction, and waiting is currently not allowed.
Possible Problems
Analytic Services cannot lock the object because it is currently locked
by another transaction.
Possible Solutions
- Wait a few minutes and retry the operation to allow
the other active user's process to finish.
- See if another user has locked
the file.
- Set Analytic Services to wait
automatically and then retry the operation.
- If this error happens frequently, make sure that
users are logging off Analytic Services correctly.
1014027 Transaction transactionHandle is
deadlocked with transaction transactionHandle.
Possible Problems
Analytic Services 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
- Make sure that two users are not performing calculations
on the same blocks at the same time.
- If this errror happens frequently, have spreadsheet
users clear the Update Mode check box in the Mode tab of the Analytic
Services Options dialog box. See the Analytic Services Spreadsheet
Add-in User's Guide for more information.
1014028 Transaction transactionHandle is
waiting for transaction transactionHandle.
Possible Problems
Analytic Services cannot complete the transaction because the current
transaction is waiting for a deadlocked transaction.
Possible Solutions
- Make sure that two users are not performing calculations
on the same blocks at the same time.
- If this error happens frequently, have spreadsheet
users clear the Update Mode check box in the Mode tab of the Analytic
Services Options dialog box. See the Analytic Services Spreadsheet
Add-in User's Guide for more information.
1014031 Analytic Services could not get a lock
in the specified wait time.
Possible Problems
Analytic Services could not lock the object in the user-specified wait
time.
Possible Solutions
- Wait a few minutes and retry the operation to allow
the other active user's process to finish.
- Increase the time that Analytic Services waits
automatically for a lock.
- See if another user has locked
the file.
- Increase the values for NETDELAY
and NETRETRYCOUNT.
- If this error happens frequently, make sure that
users are not starting complex calculations and then logging off Analytic
Services before the calculation is completed.
- Stop and restart
Analytic Server. Then check to see if the database
is corrupt.
-
If this error is happening because spreadsheet users are locking objects,
increase the values for LOCKTIMEOUT.
- If you do not have an
$ARBORPATH/bin/essbase.cfg
file on the
server computer, create one using a text editor.
- In the
$ARBORPATH/bin/essbase.cfg
file on the server computer, add or increase the value for LOCKTIMEOUT.
- Stop and
restart Analytic Server.
See Also
1014032
1014032 Analytic Services could not get a lock.
Analytic Services will keep trying until it reaches the specified wait
time.
Possible Problems
Analytic Services 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
- Wait a few minutes and retry the operation to allow
the other active user's process to finish.
- See if another user has locked
the file.
- Increase the values for NETDELAY
and NETRETRYCOUNT.
- If this error happens frequently, make sure that
users are not starting complex calculations and then logging off Analytic
Services before the calculation is completed.
- Stop and restart
Analytic Server. Then check to see if the database
is corrupt.
-
If this error is happening because spreadsheet users are locking objects,
increase the values for LOCKTIMEOUT.
- If you do not have an
$ARBORPATH/bin/essbase.cfg
file on the
server computer, create one using a text editor.
- In the
$ARBORPATH/bin/essbase.cfg
file on the server computer, add or increase the value for LOCKTIMEOUT.
- Stop and
restart Analytic Server.
See Also
1014031
1014033 Failed to allocate lock manager event.
operation aborted
Possible Problems
Analytic Services 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
Analytic Services 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, Analytic Services is configured to not allow waiting, so the
current transaction cannot wait to lock the block.
Possible Solutions
Set Analytic Services 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 Analytic Services was waiting to release a write
lock.
Possible Solutions
Contact Hyperion Technical Support.