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 Analytic Services Database Administrator's
Guide and the Analytic Services Technical Reference for more information
on how to fix errors.
Click an error message number to view information about that error message.
Analytic Services did not have enough disk space to store the data in a page file.
Analytic Services 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:
$ARBORPATH/app/applicationName/databaseName/databaseName.inn
$ARBORPATH/app/applicationName/databaseName/essxxxxx.inn
$ARBORPATH/app/applicationName/databaseName/essxxxxx.pan
$ARBORPATH/app/applicationName/databaseName/databaseName.otn
$ARBORPATH/app/applicationName/databaseName/databaseName.esn
$ARBORPATH/app/applicationName/databaseName/databaseName.tcu
Analytic Services cannot store the block in its memory.
Analytic Services 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 Analytic Services to shut down incorrectly.
To fix the database:
$ARBORPATH/app/applicationName/databaseName/
databaseName.ind
file.Analytic Services cannot complete the listed operation because there was not enough memory.
Try any of the following to fix the problem. Once you fix the problem, check to see if the database is corrupt.
Analytic Services 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 Analytic Services to shut down incorrectly.
To fix the database:
$ARBORPATH/app/applicationName/databaseName/databaseName.ind
file.The data cache was full.
This information message states the size of the data cache and the number of data pages. There is nothing wrong.
This information message states the size of the data file cache and the number of data file pages. There is nothing wrong.
This information message states that Analytic Services is locking the data cache pages into physical memory. There is nothing wrong.
Analytic Services 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.
You did not have the correct privileges to use cache memory locking.
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.
Analytic Services cannot store the data file page in the data file cache.
Increase the data file cache
size.
Once you fix the problem, check to see if the database
is corrupt.
The data file cache for the listed database was full.
Increase the data file cache
size.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services 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 Analytic Services to shut down incorrectly.
To fix the database:
$ARBORPATH/app/applicationName/databaseName/databaseName.ind
file.This information message states that Analytic Services is swapping pages to memory. There is nothing wrong. To reduce swapping and increase performance, increase the data file cache size.
Contact Hyperion Technical Support.
Once you fix the problem, check to see if the database
is corrupt.
Contact Hyperion Technical Support.
Once you fix the problem, check to see if the database
is corrupt.
Contact Hyperion Technical Support.
Once you fix the problem, check to see if the database
is corrupt.
Contact Hyperion Technical Support.
Once you fix the problem, check to see if the database
is corrupt.
Contact Hyperion Technical Support.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services cannot increase the size of the page file.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
Analytic Services encountered a fatal error.
Check the previous messages in the Analytic
Server log to determine what caused Analytic Server to crash.
Once you fix the problem, check to see if the database
is corrupt.
This information message states that the input and output transfer buffers for the listed database are free. There is nothing wrong.
The operating system resources are insufficient.
Contact Hyperion Technical Support.
The operating system resources are insufficient.
Contact Hyperion Technical Support.
The operating system resources are insufficient.
Contact Hyperion Technical Support.
The operating system resources are insufficient.
Contact Hyperion Technical Support.
The operating system resources are insufficient.
Contact Hyperion Technical Support.
The operating system resources are insufficient.
Contact Hyperion Technical Support.