1014004 to 1014043: Lock Manager Messages

Table 8 lists Lock Manager error and informational messages.

Table 8. Lock Manager Messages 1014004 to 1014043

Message Number Message Possible Cause Possible Solution

1014004

Unable to Update Members Which Have Not Been Locked

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

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 (see Unlocking Objects).

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

1014018

Members Currently Locked by another transaction

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

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 (see Unlocking Objects).

If this error happens frequently, ensure that users are logging off Essbase correctly.

1014025

Unable to update database while in readonly mode for backup

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

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 Ensure 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.

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

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 (see Unlocking Objects).

Set Essbase to wait automatically, and retry the operation.

If this error happens frequently, ensure that users are logging off Essbase correctly.

1014027

Transaction transactionHandle is deadlocked with transaction transactionHandle.

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 to access block 1 then block 2, while user2 tried to access block2 then block 1.

Ensure that two users are not performing calculations on the same blocks at the same time.

If this error happens frequently, instruct spreadsheet users to clear the “Update Mode” option. See the Oracle Essbase Spreadsheet Add-in User's Guide.

1014028

Transaction transactionHandle is waiting for transaction transactionHandle.

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

Ensure that two users are not performing calculations on the same blocks at the same time.

If this error happens frequently, instruct spreadsheet users to clear the “Update Mode” option. See the Oracle Essbase Spreadsheet Add-in User's Guide.

1014031

Related Topics

1014032

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

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

Wait a few minutes and retry the operation to allow the other active user's process to finish.

Increase the time that Essbase waits automatically for a lock.

See if another user has locked the file (see Unlocking Objects).

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

If this error happens frequently, ensure that users are not starting complex calculations and logging off Essbase before the calculation is completed.

Stop and restart Essbase Server. Then determine whether the database is corrupt (see Checking for Database Corruption).

If this error is happening because spreadsheet users are locking objects, increase the values for LOCKTIMEOUT.

  1. If ESSBASEPATH/bin/essbase.cfg does not exist on the server computer, create one using a text editor.

  2. In the ESSBASEPATH/bin/essbase.cfg file on the server computer, add or increase the value for LOCKTIMEOUT.

  3. Stop and restart Essbase Server.

1014032

Related Topics

1014031

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

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

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 (see Unlocking Objects).

Increase the values for NETDELAY and NETRETRYCOUNT (see Setting NETDELAY and NETRETRYCOUNT).

If this error happens frequently, ensure that users are not starting complex calculations and logging off Essbase before the calculation is completed.

Stop and restart Essbase Server. Then determine whether the database is corrupt (see Checking for Database Corruption).

If this error is happening because spreadsheet users are locking objects, increase the values for LOCKTIMEOUT.

  1. If ESSBASEPATH/bin/essbase.cfg does not exist on the server computer, create one using a text editor.

  2. In the ESSBASEPATH/bin/essbase.cfg file on the server computer, add or increase the value for LOCKTIMEOUT.

  3. Stop and restart Essbase Server.

1014033

Failed to allocate lock manager event. operation aborted

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

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 occurring, add more memory to the server computer.

1014034

Failed to create lock manager event. operation aborted

 

Contact Oracle Support.

1014035

Failed to allocate lock manager waiter node. operation aborted

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

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 occurring, add more memory to the server computer.

1014036

Lock request would block, but waiting is not allowed.

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.

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.

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

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 Oracle Support.

1014041

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

 

Contact Oracle Support.

1014042

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

 

Contact Oracle Support.

1014043

Error encountered while releasing a lock in database databaseName.

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

Contact Oracle Support.