Grid API Errors Messages 1120000 to 1120002
This document describes Grid API error messages. It includes 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.
1120000 Unable to lock file fileName.
Possible Problems
Essbase cannot lock the listed file to perform operations on it. This usually
occurs when Essbase cannot find the file or the user does not have permission
to write to the file.
Possible Solutions
- Make sure that Essbase can find the listed file.
- Make sure that the listed file name and path name are correct. Check for misspellings.
- Make sure that the listed file is in the specified location and that no one has moved or
deleted the listed file.
- Make sure that the listed file is in the correct location. If you are using ESSCMD, make
sure that the listed file has the correct capitalization and spelling.
- If you are using the IMPORT ESSCMD, make sure that you are using the
IMPORT command
correctly. When you issue the IMPORT command, you have four options to choose the
location of the data file.
- 1 (local/client object): Make sure the data file is in the client
folder.
Make sure you have read access to the data file.
If OLAP Server is on a UNIX platform, remember that the file name is case-sensitive
and check capitalization.
- 2 (remote server object): Make sure you have read access to the data
file.
If OLAP Server is on a UNIX platform, remember that the file name is case-sensitive
and check capitalization.
- 3 (file): Make sure that you specified the absolute path name and the
full file name (including the file type extension).
- 4 (SQL): Check the ODBC connections.
Make sure OLAP Server is properly configured.
- Make sure Essbase can use the listed file.
- See if another user has locked the file.
- Make sure that you have the correct Essbase
permissions for the listed file.
- Make sure that you have the correct operating system privileges for the listed file and the
drive you are writing it to.
- Make sure that there is enough disk space.
- Make sure that the listed file is not corrupt.
- Check to see if the security file is corrupt.
- If an operation, such as a calculation, did not complete, perform
recovery procedures. Then check to see if the
database is corrupt.
- If the application was copied or deleted using file system controls (such as
Windows Explorer or the
cp
or rm
commands), create a
dummy application with the original name and use Essbase
copy or
delete the application correctly.
- If you are using disk volumes, check the following:
- Make sure that the DISKVOLUMES setting
in the
$ARBORPATH/bin/essbase.cfg
file is correct.
- After you change the DISKVOLUMES setting, stop and restart
OLAP Server. If someone changed the DISKVOLUMES setting without stopping and starting OLAP Server,
check to see if the database is corrupt.
- Make sure that the user spanning the disk volumes has the correct operating system
privileges for the new drive.
- If the OLAP Server is on a computer running UNIX, check the following:
- Make sure that the file descriptor limit is set
correctly.
- Make sure that there is enough space on the root partition.
- Make sure that capitalization of the listed file is correct.
1120001 Unable to unlock physical memory allocated by the Essbase Kernel for
database databaseName.
Possible Problems
Essbase cannot unlock the physical memory allocated by the Essbase
kernel for the listed database.
Possible Solutions
Turn off cache memory locking.
If the problem persists, contact Hyperion Technical Support.
1120002 Unable to clear data while the database
databaseName is in readonly mode for backup.
Possible Problems
Essbase cannot clear 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.