1006002 to 1006057: Data Cache Messages

Table 4 lists data cache error and informational messages.

Table 4. Data Cache Messages 1006002 to 1006057

Message NumberMessagePossible CausePossible Solution

1006002

Unable to Store Information In Page File

Disk space is inadequate for Essbase to store the data in a page file.

If possible, add more disk space. If you cannot add more disk space, consider spanning disk volumes.

If an operation, such as a calculation, did not complete, perform recovery procedures.

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

1006004

Unable to Read Information From Page File

Essbase cannot read the page file.

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:

    • ARBORPATH/app/appName/databaseName/databaseName.inn

    • ARBORPATH/app/appName/databaseName/essxxxxx.inn

    • ARBORPATH/app/appName/databaseName/essxxxxx.pan

    • ARBORPATH/app/appName/databaseName/databaseName.otn

    • ARBORPATH/app/appName/databaseName/databaseName.esn

    • ARBORPATH/app/appName/databaseName/databaseName.tcu

  2. Restart Essbase Server.

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

1006006

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

Essbase cannot store the block in its memory.

Decrease the block size by changing the dense/sparse configuration.

Increase the data cache size to hold at least 100 blocks.

Increase the memory of the server computer.

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

1006010

Invalid block header: Block's numbers do not match

Essbase cannot match the block header to the numbers of the block. The database is probably corrupt. The corruption may be due to one anomalous event, such as a power failure, that caused Essbase to shut down incorrectly.

To fix the database:

  1. Stop Essbase Server.

  2. Delete the ARBORPATH/app/appName/databaseName/databaseName.ind file.

  3. Start Essbase Server.

  4. Start the application.

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

1006015

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

Essbase cannot complete the listed operation because there was not enough memory.

Try any of these to fix the problem. After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

  • Check the physical memory on the server computer. In a Windows environment, 64 MB is the suggested minimum for one database. In a UNIX environment, 128 MB is the suggested minimum for one database. If the error keeps occurring, add more memory to the server computer.

  • If you are on a UNIX computer, check the user limit profile (see Checking the User Limit Profile).

  • 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 Essbase Server.

  • Restart the server computer.

1006016

Invalid block header: Illegal block type

Essbase cannot read the block header. The database is probably corrupt. The corruption may be due to one anomalous event, such as a power failure, that caused Essbase to shut down incorrectly.

To fix the database:

  1. Stop Essbase Server.

  2. Delete the ARBORPATH/app/appName/databaseName/databaseName.ind file.

  3. Start Essbase Server.

  4. Start the application.

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

1006023

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

The data cache was full.

Increase the data cache size to hold at least 100 blocks.

If necessary, decrease the block size.

Ensure that memory is adequate.

Once you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006025

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

Size of the data cache and the number of data pages.

Not applicable

1006026

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

Size of the data file cache and the number of data file pages.

Not applicable

1006027

Locking the data cache pages into physical memory.

Essbase is locking the data cache pages into physical memory.

Not applicable

1006028

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

Essbase ran out of physical memory and is now using virtual memory.

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.

Your privileges are inadequate to use cache memory locking.

On UNIX, ensure that you have root privileges. See the operating system documentation.

On Windows, ensure that you have the SE_INC_BASE_PRIORITY_NAME privilege. Users in the Administrators and Power Users groups generally have this privilege. See the operating system documentation.

1006030

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

Essbase cannot store the data file page in the data file cache.

Increase the data file cache size. After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006031

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

The data file cache for the listed database was full.

Increase the data file cache size.

Once you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006032

Invalid stored logical data block size number.

Essbase cannot read the data block. The database is probably corrupt. The corruption may be due to one anomalous event, such as a power failure, that caused Essbase to shut down incorrectly.

To fix the database:

  1. Stop Essbase Server.

  2. Delete the ARBORPATH/app/appName/databaseName/databaseName.ind file.

  3. Start Essbase Server.

  4. Start the application.

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

1006034

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

Essbase is swapping pages to memory.

Not applicable

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 Oracle Support.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006036

Data cache output transfer buffer for database databaseName is unavailable.

 

Contact Oracle Support.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006037

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

 

Contact Oracle Support.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006039

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

 

Contact Oracle Support.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006040

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

 

Contact Oracle Support.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006041

A read from file fileName, messageText.

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

Once you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006042

Completion of a read from file fileName, messageText.

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006043

A write to file fileName, messageText.

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006044

Completion of a write to file fileName, messageText.

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006045

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

Essbase cannot increase the page file size.

If possible, add more disk space. If you cannot add more disk space, consider spanning disk volumes.

If an operation, such as a calculation, did not complete, perform recovery procedures.

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

1006046

A read from file fileName, messageText.

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006047

A write to file fileName, messageText.

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006048

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

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006049

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

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006050

For transaction transactionNumber, messageText.

Essbase encountered a fatal error.

Check the previous messages in the Essbase Server log to determine what caused Essbase Server to crash.

After you fix the problem, determine whether the database is corrupt (see Checking for Database Corruption).

1006051

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

The input and output transfer buffers for the listed database are free.

Not applicable

1006052

Data cache input transfer buffer for database databaseName is unavailable.

The operating system resources are insufficient.

Contact Oracle Support.

1006053

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

The operating system resources are insufficient.

Contact Oracle Support.

1006054

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

The operating system resources are insufficient.

Contact Oracle Support.

1006055

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

The operating system resources are insufficient.

Contact Oracle Support.

1006056

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

The operating system resources are insufficient.

Contact Oracle Support.

1006057

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

The operating system resources are insufficient.

Contact Oracle Support.