Miscellaneous Messages 1130203 to 1130613
This document describes miscellaneous error messages. It includes 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.
1130203
Possible Problems
Essbase is unable to allocate memory.
Possible Solutions
Try any of the following suggestions to fix the problem. Once you fix the problem, check to see if the
database is corrupt.
- 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 occuring, add more memory
to the server computer.
- If you are on a UNIX computer, check the user limit profile.
- Check the block size of the database. If necessary, reduce the block size.
- Check the data cache and data file cache
setting. If necessary, decrease the data cache and data file cache sizes.
- Make sure that the Essbase computer has enough resources. Consult the
Essbase Installation Guide for a list of system requirements. If a
resource-intensive application, such as a relational database, is running on the same computer,
the resource-intensive application may be using the resources that Essbase needs.
See Also
1006006, 1006010,
1006015, 1006023
1130404
Possible Problems
Essbase timed out while trying to perform an operation.
Possible Solutions
First, check the messages that occured just before this message to see if you can find additional problems. Then
try the following:
- Increase the values for NETDELAY and NETRETRYCOUNT.
- Stop and restart OLAP Server.
- Check to see if the database is corrupt.
- Do not close the OLAP Server window by clicking the "X" in the title bar.
- Make sure that the Essbase computer has enough resources. Consult the
Essbase Installation Guide for a list of system requirements. If a
resource-intensive application, such as a relational database, is running on the same computer,
the resource-intensive application may be using the resources that Essbase needs.
- Run
REGISTER.EXE
again to make sure that the license number is correct and that the ports are activated.
Consult the Essbase Installation Guide.
See Also
1042006, 1042017
1130409
This is an internal error. Contact Hyperion Technical Support.
1130410
This is an internal error. Contact Hyperion Technical Support.
1130610
Possible Problems
Essbase cannot open a file.
Possible Solutions
- Make sure you are using the ESSCMD IMPORT command correctly.
- Put all files the ESSCMD script needs in the
$ARBORPATH\APP\applicationName\databaseName
directory.
- Run the ESSCMD script from the
$ARBORPATH\APP\applicationName\databaseName
directory.
- Check the ESSCMD script for invalid paths. Make sure every folder that the script is pointing to exists.
- If you are using an error file, make sure that the error file is being created in a directory that already exists.
See Also
1003022
1130612
Possible Problems
Essbase could not close a file.
Possible Solutions
Stop and restart OLAP Server.
1130613
Possible Problems
Essbase cannot read from a file.
Possible Solutions
Check the syntax of any ESSCMD commands that access files
on a remote server, such as the IMPORT command.
Make sure that the file is not corrupt.
See Also
1003022