1120000 to 1120002: C Grid API Messages

Table 12 lists C Grid API error and informational messages.

Table 12. C Grid API Messages 1120000 to 1120002

Message Number Message Possible Cause Possible Solution

1120000

Unable to lock file fileName.

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.

Ensure that Essbase can find the listed file.

Ensure that the listed file name and path name are correct. Check for misspellings.

If you are using ESSCMD, ensure that the listed file has the correct capitalization and spelling.

If you are using IMPORT ESSCMD, ensure that you are using the IMPORT command correctly. When you issue the IMPORT command, there are four options for the data file location.

1 (local/client object): Ensure that the data file is in the client folder. Ensure that you have read access to the data file. On UNIX, the file name is case-sensitive, so check capitalization.

2 (remote server object): Ensure that you have read access to the data file. On UNIX, the file name is case-sensitive, so check capitalization.

3 (file): Ensure that you specified the absolute path name and the full file name (including the file type extension).

4 (SQL): Check the ODBC connections. Ensure that Essbase Server is properly configured.

Ensure that Essbase can use the listed file.

See if the file is locked (see Unlocking Objects).

Ensure that you have the correct Essbase permissions for the listed file.

Ensure that you have the correct operating system privileges for the listed file and the drive you are writing it to.

Ensure that disk space is adequate.

Ensure that the listed file is not corrupt (see Checking for Database Corruption).

Determine whether the security file is corrupt.

If an operation did not complete, perform recovery procedures. Then determine whether 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.

1120000 continued

   

If you are using disk volumes, check these items:

  • Ensure that the DISKVOLUMES setting in the ESSBASEPATH/bin/essbase.cfg file is correct.

  • Ensure that the user spanning the disk volumes has the correct operating system privileges for the drive.

  • After you change the DISKVOLUMES setting, stop and restart Essbase Server. If someone changed the DISKVOLUMES setting without stopping and starting Essbase Server, determine whether the database is corrupt.

If the Essbase Server is on a computer running UNIX, check these items:

  • Ensure that the file descriptor limit (see Checking the User Limit Profile) is set correctly.

  • Ensure that the root partition space is adequate.

  • Ensure that capitalization of the listed file is correct.

1120001

Unable to unlock physical memory allocated by the Essbase Kernel for database databaseName.

Essbase cannot unlock the physical memory allocated by the Essbase kernel for the listed database.

Turn off cache memory locking. If the problem persists, contact Oracle Support.

1120002

Unable to clear data while the database databaseName is in readonly mode for backup.

Essbase cannot clear 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.