Data Cache Error Messages 1006002 to 1006057

This document describes data cache error messages and information messages. The discussions of error messages include 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.
1006002 1006034 1006050
1006004 1006035 1006051
1006006 1006036 1006052
1006010 1006037 1006053
1006015 1006039 1006054
1006016 1006040 1006055
1006023 1006041 1006056
1006025 1006042 1006057
>1006026 1006043
1006027 1006044
1006028 1006045
1006029 1006046
1006030 1006047
1006031 1006048
1006032 1006049

1006002 Unable to Store Information In Page File

Possible Problems
Essbase did not have enough disk space to store the data in a page file.
Possible Solutions

1006004 Unable to Read Information From Page File

Possible Problems
Essbase cannot read the page file.
Possible Solutions
Is there a hardware problem? Check your Windows event log. If you do not know how to do this, consult the Windows documentation.
Are the index and page file corrupt? Check them by issuing the VALIDATE command in ESSCMD. If the index and page files are corrupt:
  1. Delete the temporary files. The temporary files include:
  2. Restart OLAP Server.
  3. Check to see if the database is corrupt.

1006006 Failed to bring block into the memory. Data cache is too small. Please increase the data cache size.

Possible Problems
Essbase cannot store the block in its memory.
Possible Solutions

1006010 Invalid block header: Block's numbers do not match

Possible Problems
Essbase cannot match the block header to the numbers of the block. The database is probably corrupt. The corruption could have been caused by a single anomalous event, such as a power failure, that caused Essbase to shut down incorrectly.
Possible Solutions
To fix the database:
  1. Stop OLAP Server.
  2. Delete the $ARBORPATH/app/applicationName/databaseName/ databaseName.ind file.
  3. Start OLAP Server.
  4. Start the application.
  5. Check to see if the database is corrupt.

1006015 Not Enough Memory to Allocate the Data Buffer Cache. operation aborted

Possible Problems
Essbase cannot complete the listed operation because there was not enough memory.
Possible Solutions
Try any of the following to fix the problem. Once you fix the problem, check to see if the database is corrupt.
  • Check the block size of the database. If necessary, reduce the block size.
  • Check the data cache setting. If necessary, increase the data cache size.
  • Restart OLAP Server.
  • Restart the server computer.

  • 1006016 Invalid block header: Illegal block type

    Possible Problems
    Essbase cannot read the block header. The database is probably corrupt. The corruption could have been caused by a single anomalous event, such as a power failure, that caused Essbase to shut down incorrectly.
    Possible Solutions
    To fix the database:
    1. Stop OLAP Server.
    2. Delete the $ARBORPATH/app/applicationName/databaseName/databaseName.ind file.
    3. Start OLAP Server.
    4. Start the application.
    5. Check to see if the database is corrupt.

    1006023 Data cache is full. Please increase the data cache size for database databaseName.

    Possible Problems
    The data cache was full.
    Possible Solutions

    1006025 Data cache size ==> number bytes, number data pages

    This information message states the size of the data cache and the number of data pages. There is nothing wrong.

    1006026 Data file cache size ==> number bytes, number data file pages

    This information message states the size of the data file cache and the number of data file pages. There is nothing wrong.

    1006027 Locking the data cache pages into physical memory.

    This information message states that Essbase is locking the data cache pages into physical memory. There is nothing wrong.


    1006028 Turning off cache memory locking due to lack of physical memory. Using virtual memory to allocate the remainder of the data cache.

    Possible Problems
    Essbase ran out of physical memory and is now using virtual memory.
    Possible Solutions
    If you wish to use physical memory, add more physical memory to the computer.

    1006029 Turning off cache memory locking due to insufficient privileges. Using virtual memory to allocate the remainder of the data cache.

    Possible Problems
    You did not have the correct privileges to use cache memory locking.
    Possible Solutions
    On UNIX, make sure that you have root privileges. Consult the operating system documentation for more information.
    On Windows, make sure that you have the SE_INC_BASE_PRIORITY_NAME privilege. Users in the Administrators and Power Users groups generally have this privilege. Consult the operating system documentation for more information.

    1006030 Failed to bring a data file page into cache. Data file cache is too small. Please increase the data file cache size.

    Possible Problems
    Essbase cannot store the data file page in the data file cache.
    Possible Solutions
    Increase the data file cache size.
    Once you fix the problem, check to see if the database is corrupt.

    1006031 Data file cache is full. Please increase the data file cache size for database databaseName.

    Possible Problems
    The data file cache for the listed database was full.
    Possible Solutions
    Increase the data file cache size.
    Once you fix the problem, check to see if the database is corrupt.

    1006032 Invalid stored logical data block size number.

    Possible Problems
    Essbase cannot read the data block. The database is probably corrupt. The corruption could have been caused by a single anomalous event, such as a power failure, that caused Essbase to shut down incorrectly.
    Possible Solutions
    To fix the database:
    1. Stop OLAP Server.
    2. Delete the $ARBORPATH/app/applicationName/databaseName/databaseName.ind file.
    3. Start OLAP Server.
    4. Start the application.
    5. Check to see if the database is corrupt.

    1006034 Waiting to swap a data file cache page for database databaseName. Performance could potentially be improved by increasing the data file cache size.

    This information message states that Essbase is swapping pages to memory. There is nothing wrong. To reduce swapping and increase performance, increase the data file cache size.

    1006035 Error errorNumber encountered while waiting for completion of a data file cache flush for database databaseName.

    Contact Hyperion Technical Support.
    Once you fix the problem, check to see if the database is corrupt.

    1006036 Data cache output transfer buffer for database databaseName is unavailable.

    Contact Hyperion Technical Support.
    Once you fix the problem, check to see if the database is corrupt.

    1006037 Error encountered while waiting for an in-transit data page of database databaseName.

    Contact Hyperion Technical Support.
    Once you fix the problem, check to see if the database is corrupt.

    1006039 Error encountered while waiting for an in-transit data file page of database databaseName.

    Contact Hyperion Technical Support.
    Once you fix the problem, check to see if the database is corrupt.

    1006040 Unable to flush to disk a data block within database databaseName.

    Contact Hyperion Technical Support.
    Once you fix the problem, check to see if the database is corrupt.

    1006041 A read from file fileName, messageText.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006042 Completion of a read from file fileName, messageText.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006043 A write to file fileName, messageText.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006044 Completion of a write to file fileName, messageText.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006045 Error errorNumber encountered while attempting to create or extend a data file for database databaseName.

    Possible Problems
    Essbase cannot increase the size of the page file.
    Possible Solutions

    1006046 A read from file fileName, messageText.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006047 A write to file fileName, messageText.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006048 An attempt to set the file pointer for file fileName, messageText.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006049 Unable to generate the data file name for file fileName for database databaseName.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006050 For transaction transactionNumber, messageText.

    Possible Problems
    Essbase encountered a fatal error.
    Possible Solutions
    Check the previous messages in the OLAP Server log to determine what caused OLAP Server to crash.
    Once you fix the problem, check to see if the database is corrupt.

    1006051 For database databaseName, the Input Transfer Buffer and the Output Transfer Buffer have been freed.

    This information message states that the input and output transfer buffers for the listed database are free. There is nothing wrong.


    1006052 Data cache input transfer buffer for database databaseName is unavailable.

    Possible Problems
    The operating system resources are insufficient.

    Possible Solutions
    Contact Hyperion Technical Support.


    1006053 Error encountered while waiting for initialization of a data block of database databaseName.

    Possible Problems
    The operating system resources are insufficient.

    Possible Solutions
    Contact Hyperion Technical Support.


    1006054 Error encountered while waiting to fix a data file page of database databaseName.

    Possible Problems
    The operating system resources are insufficient.

    Possible Solutions
    Contact Hyperion Technical Support.


    1006055 Error encountered while waiting to access the data file buffer pool of database databaseName.

    Possible Problems
    The operating system resources are insufficient.

    Possible Solutions
    Contact Hyperion Technical Support.


    1006056 Error encountered while waiting for initialization of a data file page of database databaseName.

    Possible Problems
    The operating system resources are insufficient.

    Possible Solutions
    Contact Hyperion Technical Support.


    1006057 Error encountered while waiting for a data file page of database databaseName that is involved in a data block transfer.

    Possible Problems
    The operating system resources are insufficient.

    Possible Solutions
    Contact Hyperion Technical Support.