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.