Table 9 lists database object error and informational messages.
Table 9. Database Object Messages 1019002 to 1019056
| Message Number | Message | Possible Cause | Possible Solution |
|---|---|---|---|
Related Topics | Essbase cannot find the listed file. Essbase cannot run without the listed file. The data in the database may be corrupt due to an abnormal shutdown. | Ensure that the file exists. If it does not exist, restore the file from backups. Ensure that you have the correct operating system privileges for the file and directory. If you are using ESSCMD, ensure that the file name and path are correct. On UNIX, ensure that capitalization is correct. Ensure that you have enough disk space. On UNIX, ensure that you have enough space on the root partition. If the file is essbase.sec, determine whether it is corrupt. On UNIX, check the user limit profile (see Checking the User Limit Profile). 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 to copy or delete the application correctly. If the file is a rules file, ensure that it is associated with the correct outline. Stop and restart the application. Stop and restart Essbase Server. If the listed file is ARBORPATH/app/appName/databaseName/databaseName.db, replace the file with its backup (see Replacing Database Files with Backups). If the listed file is ARBORPATH/app/appName/databaseName/databaseName.ind, delete and reload the data files. Deleting your data files deletes all data in your database; you must reload and recalculate the database.
| |
Related Topics | Ensure that the listed file exists. If it does not exist, restore the file from backups. 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. Ensure that you have enough disk space. See if another user has locked the file (see Unlocking Objects). If you are using Essbase Spreadsheet Add-in, increase the retrieval buffer size to at least 50 KB. Determine whether the database is corrupt (see Checking for Database Corruption). If the listed file is ARBORPATH/App/appName/databaseName/databaseName.db, replace the file with its backup (see Replacing Database Files with Backups). If the listed file is ARBORPATH/app/appName/databaseName/databaseName.ind, try to restore the file from backups. If that does not work, delete and reload the data files. Deleting your data files deletes all data in your database; you must reload and recalculate the database. | ||
Unable to write information to file fileName, errno is operatingSystemErrorNumber. | Ensure that the listed file exists. If it does not exist, restore the file from backups. Ensure that you have enough disk space. Ensure that these environment variables (see Setting Environment Variables) are set correctly: If you are on a UNIX computer, check the user limit profile (see Checking the User Limit Profile). Verify that you are using data compression to limit page file size. If the listed file is ARBORPATH/app/appName/databaseName/databaseName.db, replace the file with its backup (see Replacing Database Files with Backups). If the listed file is ARBORPATH/app/appName/databaseName/databaseName.ind, try to restore the file from backups. If that does not work, delete and reload the data files. Deleting your data files deletes all data in your database; you must reload and recalculate the database. | ||
If possible, restore the file from backups. If the listed file is ARBORPATH/app/appName/databaseName/databaseName.db, replace the file with its backup (see Replacing Database Files with Backups). If the listed file is ARBORPATH/app/appName/databaseName/databaseName.ind, try to restore the file from backups. If that does not work, delete and reload the data files. Deleting your data files deletes all data in your database; you must reload and recalculate the database. | |||
Determine whether the database is corrupt (see Checking for Database Corruption). The listed file may be corrupt. If possible, restore the file from backups. | |||
The listed file type does not match the contents of the file. The listed file is probably corrupt. | Determine whether the database is corrupt (see Checking for Database Corruption). The listed file may be corrupt. If possible, restore the file from backups. | ||
Essbase is reading the application definition for the listed application. | |||
Essbase is reading the database definition for the listed database. | |||
Essbase is writing the application definition for the listed application. | |||
Essbase is writing the database definition for the listed database. | |||
Essbase is reading the outline definition for the listed database. | |||
Essbase is writing the outline for the listed database back to the disk. | |||
Reading Data File Free Space Information For Database databaseName | Free space information is stored in the ARBORPATH/app/appName/databaseName/databaseName.ind file. If ample free space exists, it may take some time to read the free space information. | ||
Free space information is written to disk when a database is shut down, when a database is set in read-only mode, and when a database is being recovered. | |||
Essbase is reading database information for the listed database. | |||
Essbase is writing database information for the listed database. | |||
Essbase is reading the outline updates from the ARBORPATH/app/appName/databaseName/databaseName.otn file. | |||
Unknown member memberName found while processing string string | Essbase does not recognize the listed string as a member of the outline. | Ensure that the member name is valid. The member name is in the rules file.
| |
Out of disk space, Unable to write information to file fileName | Essbase is out of disk space and cannot write to the listed file. | ||
Unable to write fileName; database is in readonly mode for backup | Essbase cannot write to the listed file 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 a sleep command to Ensure that the archive process completes before the next process begins. If you are using ESSCMD and the problem persists, use the UNLOADAPP command to remove the application from memory and issue the LOADAPP command to reload the application in memory and to ensure that the database is no longer in read-only mode. | |
Unable to write to fileName; database is in readonly mode for archive | Essbase cannot write to the listed file because the database is in read-only mode. | it 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 a sleep command to Ensure that the archive process completes before the next process begins. If you are using ESSCMD and the problem persists, use the UNLOADAPP command to remove the application from memory and issue the LOADAPP command to reload the application in memory and to ensure that the database is no longer in read-only mode. | |
Essbase is reading the outline changes in the ARBORPATH/app/appName/databaseName/databaseName.ocl file. | |||
Essbase is writing the outline changes to the ARBORPATH/app/appName/databaseName/databaseName.ocl file. | |||
Dimension number number for Database databaseName is invalid | Essbase assigns a dimension index number for each dimension of an outline. An assigned dimension index number is not valid. The number may be larger than the count of dimensions in the outline. | Determine whether the database is corrupt (see Checking for Database Corruption). If the outline file is corrupt, restore the outline file from backups. | |
Member number memberName for Database databaseName is invalid | Essbase assigns a member index number for each member of each dimension. An assigned member index number is not valid. The number may be larger than the count of members in the dimension. | Determine whether the database is corrupt (see Checking for Database Corruption). | |
Essbase cannot find the ARBORPATH/app/appName/databaseName/databaseName.db file. | If ARBORPATH/app/appName/databaseName/databaseName.db exists, rename it to databaseNameold.db. Then rename the databaseName.dbb backup file to databaseName.db. If databaseName.db does not exist, rename the databaseName.dbb file to databaseName.db. If databaseName.dbb does not exist, restore the databaseName.db file from backups. | ||
Cannot write to file fileName because object type type is invalid. Make sure Essbase is properly installed and configured. | Ensure that Essbase is installed correctly. If necessary, reinstall Essbase. | ||
Unable to write to file fileName because the application is shutting down | Essbase cannot write to the listed file because the application is closing. | To prevent this problem from recurring, be sure to log off of Essbase and shut Essbase down correctly. To log off and shut down, try all of these steps:
| |
Related Topics | Unable to write information to file fileName, adWriteObject returns EssbaseErrorNumber. See server logfile for details. | Check HYPERION_HOME/logs/essbase/app/appName/appName.log for information about the listed Essbase error number. Ensure that the file exists. If it does not exist, restore the file from backups. Ensure that you have enough disk space. Ensure that these environment variables (see Setting Environment Variables) are set correctly: If you are on a UNIX computer, check the user limit profile (see Checking the User Limit Profile). Verify that you are using data compression to limit page file size. If the listed file is ARBORPATH/app/appName/databaseName/databaseName.db, replace the file with its backup (see Replacing Database Files with Backups). If the listed file is ARBORPATH/app/appName/databaseName/databaseName.ind, try to restore the file from backups. If that does not work, delete and reload the data files. Deleting your data files deletes all data in your database; you must reload and recalculate the database. | |
Unable to move the file pointer to the location specified for file fileName, errno is operatingSystemError. | |||
Essbase can not create the outline memory pool. The outline memory pool holds outline items in memory. | Ensure that you have sufficient memory on the server computer. | ||
Error Allocating Mem in Outline Pool For Database databaseName | Essbase can not create the outline memory pool. The outline memory pool holds outline items in memory. | Ensure that you have sufficient memory on the server computer. | |
Essbase is reading the partition definition file for the listed database. | |||
Outline buffer error. Hole position number does not match with number in the buffer | |||
Outline buffer writing error. number bytes written does not match with hole size number | |||
Outline buffer error. Cannot flush buffer with number hole to a fragmented outline file | |||
Outline buffer error. File position number does not match with number bytes written | |||
Total adReadStruct Elapsed Time using outline buffer: number seconds | |||
Total adOtlReadOutline Elapsed Time using outline buffer: number seconds | |||
Total adOtlWriteOutline Elapsed Time using outline buffer: number seconds | |||
The type defined for the listed attribute member is not valid. | Ensure that all attribute members use one of these types: text, numeric, Boolean, or date. | ||