1019002 to 1019056: Database Object Messages

Table 9 lists database object error and informational messages.

Table 9. Database Object Messages 1019002 to 1019056

Message Number Message Possible Cause Possible Solution

1019002

Related Topics

1019003

Unable To Find Or Open fileName

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.

  1. Stop Essbase Server.

  2. Delete the databaseName.ind, Essxxx.ind, Essxxx.pag, databaseName.esm, and databaseName.tct files.

  3. Restart Essbase Server.

  4. Reload the database, and then recalculate the database.

  5. Determine whether the database is corrupt (see Checking for Database Corruption).

1019003

Related Topics

1019002

Unable to Read Information From fileName

Essbase cannot read from the listed file.

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.

  1. Stop Essbase Server.

  2. Delete the databaseName.ind, Essxxx.ind, Essxxx.pag, databaseName.esm, and databaseName.tct files.

  3. Restart Essbase Server.

  4. Reload the database.

  5. Recalculate the database.

1019004

Unable to write information to file fileName, errno is operatingSystemErrorNumber.

Essbase cannot write to the listed file.

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:

  • ESSBASEPATH (PC and UNIX)

  • PATH (PC and UNIX)

  • LD_LIBRARY_PATH (UNIX only)

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.

  1. Stop Essbase Server.

  2. Delete the databaseName.ind, Essxxx.ind, Essxxx.pag, databaseName.esm, and databaseName.tct files.

  3. Restart Essbase Server.

  4. Reload the database.

  5. Recalculate the database.

1019005

Unable to Read fileName, Not a Recognized Format

Essbase cannot read the listed file.

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.

  1. Stop Essbase Server.

  2. Delete the databaseName.ind, Essxxx.ind, Essxxx.pag, databaseName.esm, and databaseName.tct files.

  3. Restart Essbase Server.

  4. Reload the database.

  5. Recalculate the database.

1019006

Unable to Read fileName, Created Using A Previous Version

Essbase cannot read the listed file.

Determine whether the database is corrupt (see Checking for Database Corruption).

The listed file may be corrupt. If possible, restore the file from backups.

1019007

Unable To Read fileName, Type Does Not Match Name

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.

1019008

Reading Application Definition For appName

Essbase is reading the application definition for the listed application.

Not applicable

1019009

Reading Database Definition For databaseName

Essbase is reading the database definition for the listed database.

Not applicable

1019010

Writing Application Definition For appName

Essbase is writing the application definition for the listed application.

Not applicable

1019011

Writing Database Definition For databaseName

Essbase is writing the database definition for the listed database.

Not applicable

1019012

Reading Outline For Database databaseName

Essbase is reading the outline definition for the listed database.

Not applicable

1019013

Writing Outline For Database databaseName

Essbase is writing the outline for the listed database back to the disk.

Not applicable

1019014

Unable To Write Information For Database databaseName

Essbase cannot find the listed database.

Ensure that the database name is correct.

Ensure that the database exists in the specified location.

1019015

Database Outline Already Loaded For Database databaseName

The database outline for the listed database is loaded.

Do not try to load a database more than once.

1019017

Reading Parameters For Database databaseName

Essbase is reading the parameters for the listed database.

Not applicable

1019018

Writing Parameters For Database databaseName

Essbase is writing the parameters for the listed database.

Not applicable

1019019

Reading Data File Free Space Information For Database databaseName

Essbase is reading the free space for the listed database.

Not applicable

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.

1019020

Writing Free Space Information For Database databaseName

Essbase is writing the free space for the listed database.

Not applicable

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.

1019021

Reading Database Mapping For databaseName

Essbase is reading database information for the listed database.

Not applicable

1019022

Writing Database Mapping For databaseName

Essbase is writing database information for the listed database.

Not applicable

1019024

Reading Outline Transaction For Database databaseName

Essbase is reading the outline updates from the ARBORPATH/app/appName/databaseName/databaseName.otn file.

Not applicable

1019025

Reading Rules From Rule Object For Database databaseName

Essbase is reading a rules file for the listed database.

Not applicable

1019026

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.

  • Are you using the correct rules file?

  • Is the rules file connected to the correct outline?

  • Can you validate the rules file?

  • Are member names or variable names enclosed in quotation marks where necessary?

  • Does the member exist in the outline? If not, you can add the member by modifying the outline during the dimension build or add the member in the Outline Editor.

  • Ensure that the member is not specified as a header in the rules file.

1019028

Out of disk space, Unable to write information to file fileName

Essbase is out of disk space and cannot write to the listed file.

Ensure that you have enough disk space.

1019031

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.

1019032

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.

1019034

Reading Outline Change Log For Database databaseName

Essbase is reading the outline changes in the ARBORPATH/app/appName/databaseName/databaseName.ocl file.

Not applicable

1019035

Writing Outline Change Log For Database databaseName

Essbase is writing the outline changes to the ARBORPATH/app/appName/databaseName/databaseName.ocl file.

Not applicable

1019036

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.

1019037

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

If necessary, restore the outline file from backups.

1019038

DB file is missing.

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.

1019039

Cannot write to file fileName because object type type is invalid. Make sure Essbase is properly installed and configured.

Essbase cannot write to the listed file.

Ensure that Essbase is installed correctly. If necessary, reinstall Essbase.

1019040

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:

  1. As a user, exit Administration Services or Spreadsheet Add-in.

  2. If the previous step does not work, have the administrator disconnect the user.

  3. If the previous step does not work, unlock any locked objects (see Unlocking Objects), unload the database, stop the database, and try again to disconnect the user.

  4. If the previous step does not work, have the administrator log off the user in the Agent window.

  5. If the previous step does not work, stop the application from the Agent window.

  6. If the previous step does not work, end the task (see Ending the Server Task).

  7. If the previous step does not work, restart the server machine.

1019041

Related Topics

1019004

Unable to write information to file fileName, adWriteObject returns EssbaseErrorNumber. See server logfile for details.

Essbase cannot write to the listed file.

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:

  • ESSBASEPATH (PC and UNIX)

  • PATH (PC and UNIX)

  • LD_LIBRARY_PATH (UNIX only)

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.

  1. Stop Essbase Server.

  2. Delete the databaseName.ind, Essxxx.ind, Essxxx.pag, databaseName.esm, and databaseName.tct files.

  3. Restart Essbase Server.

  4. Reload the database.

  5. Recalculate the database.

1019042

Unable to move the file pointer to the location specified for file fileName, errno is operatingSystemError.

 

Contact Oracle Support.

1019043

Error Creating 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.

1019044

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.

1019045

Reading Partition Definition File For Database databaseName

Essbase is reading the partition definition file for the listed database.

Not applicable

1019046

Outline buffer cannot handle more than number hole

 

Contact Oracle Support.

1019047

Outline buffer error. Hole position number does not match with number in the buffer

 

Contact Oracle Support.

1019048

Outline buffer writing error. number bytes written does not match with hole size number

 

Contact Oracle Support.

1019049

Outline buffer error. Cannot flush buffer with number hole to a fragmented outline file

 

Contact Oracle Support.

1019050

Outline buffer error. File position number does not match with number bytes written

 

Contact Oracle Support.

1019051

Total adReadStruct Elapsed Time using outline buffer: number seconds

The time used to read the outline buffer.

Not applicable

1019052

Total adOtlReadOutline Elapsed Time using outline buffer: number seconds

The time used to read the outline data into memory.

Not applicable

1019053

Total adOtlWriteOutline Elapsed Time using outline buffer: number seconds

The time used to write the outline data.

Not applicable

1019054

Invalid Named Attribute Opcode For Member memberName

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.

1019056

Object file path path is too long.

The listed path is too long.

Ensure that the listed path is smaller than 1025 bytes.