Database Objects Messages 1019002 to 1019056
This document describes database objects 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.
1019002 Unable To Find Or Open fileName
Possible Problems
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.
Possible Solutions
- Make sure that the listed file exists. If it does not exist,
restore the file from backups.
- Make sure that you have the correct operating system privileges for the listed
file and directory.
- If you are using ESSCMD, make sure that the file name and the path are correct. If you
are on a UNIX computer, make sure that capitalization is also correct.
- Make sure that you have enough disk space.
If you are on a Unix computer, make sure that you have enough space on the
root partition.
- If the listed file is
essbase.sec
, check to see if the
security file is corrupt.
- If you are on a UNIX computer, check 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
copy or
delete the application correctly.
- If the listed file is a rules file, make sure that it is
associated with the
correct outline.
- Stop and restart the application.
- Stop and restart OLAP Server.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.db
,
replace the file with its backup:
- Stop OLAP Server.
- Rename
databaseName.db
to databaseNamedb.old
.
- Rename
databaseName.dbb
to databaseName.db
.
- Restart OLAP Server.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.ind
,
delete and reload the data files. Deleting your data files deletes all the data in your database; you will have to
reload and recalculate the database.
- Stop OLAP Server.
- Delete the
databaseName.ind
,
Essxxx.ind
, Essxxx.pag
,
databaseName.esm
, and
databaseName.tct
files.
- Restart OLAP Server.
- Reload the database.
- Recalculate the database.
- Check to see if the database is corrupt.
See Also
1019003
1019003 Unable to Read Information From fileName
Possible Problems
Essbase cannot read from the listed file.
Possible Solutions
- Make sure 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.
- Make sure that you have enough disk space.
- See if another user has locked the file.
- If you are using Essbase Spreadsheet Add-in, increase the retrieval buffer size
to at least 50 K.
- Check to see if the database is corrupt.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.db
,
replace the file with its backup:
- Stop OLAP Server.
- Rename
databaseName.db
to databaseNamedb.old
.
- Rename
databaseName.dbb
to databaseName.db
.
- Restart OLAP Server.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.ind
,
try to restore the file from backups.
If that doesn't work, then delete and reload the data files. Deleting your data files deletes all the data in your database; you will have to
reload and recalculate the database.
- Stop OLAP Server.
- Delete the
databaseName.ind
,
Essxxx.ind
, Essxxx.pag
,
databaseName.esm
, and
databaseName.tct
files.
- Restart OLAP Server.
- Reload the database.
- Recalculate the database.
See Also
1019002
1019004 Unable to write information to file fileName,
errno is operatingSystemErrorNumber.
Possible Problems
Essbase cannot write to the listed file.
Possible Solutions
- Make sure that the listed file exists. If it does not exist,
restore the file from backups.
- Make sure that you have enough disk space.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
- If you are on a UNIX computer, check the
user limit profile.
- Verify that you are using data compression to limit page
file size.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.db
,
replace the file with its backup:
- Stop OLAP Server.
- Rename
databaseName.db
to databaseNamedb.old
.
- Rename
databaseName.dbb
to databaseName.db
.
- Restart OLAP Server.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.ind
,
try to restore the file from backups.
If that doesn't work, then delete and reload the data files. Deleting your data files deletes all the data in your database; you will have to
reload and recalculate the database.
- Stop OLAP Server.
- Delete the
databaseName.ind
,
Essxxx.ind
, Essxxx.pag
,
databaseName.esm
, and
databaseName.tct
files.
- Restart OLAP Server.
- Reload the database.
- Recalculate the database.
1019005 Unable to Read fileName, Not a Recognized
Format
Possible Problems
Essbase cannot read the listed file.
Possible Solutions
- If possible, restore the file from backups.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.db
,
replace the file with its backup:
- Stop OLAP Server.
- Rename
databaseName.db
to databaseNamedb.old
.
- Rename
databaseName.dbb
to databaseName.db
.
- Restart OLAP Server.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.ind
,
try to restore the file from backups.
If that doesn't work, then delete and reload the data files. Deleting your data files deletes all the data in your database; you will have to
reload and recalculate the database.
- Stop OLAP Server.
- Delete the
databaseName.ind
,
Essxxx.ind
, Essxxx.pag
,
databaseName.esm
, and
databaseName.tct
files.
- Restart OLAP Server.
- Reload the database.
- Recalculate the database.
1019006 Unable to Read fileName, Created Using A
Previous Version
Possible Problems
Essbase cannot read the listed file.
Possible Solutions
Check to see if the database is corrupt.
The listed file may be corrupt. If possible, restore
the file from backups.
1019007 Unable To Read fileName, Type Does Not
Match Name
Possible Problems
The listed file type does not match the contents of the file. The
listed file is probably corrupt.
Possible Solutions
Check to see if the database is corrupt.
The listed file may be corrupt. If possible, restore
the file from backups.
1019008 Reading Application Definition For
applicationName
This information message states that Essbase is reading the application definition
for the listed application. There is nothing wrong.
1019009 Reading Database Definition For
databaseName
This information message states that Essbase is reading the database definition
for the listed database. There is nothing wrong.
1019010 Writing Application Definition For
applicationName
This information message states that Essbase is writing the application definition
for the listed application. There is nothing wrong.
1019011 Writing Database Definition For
databaseName
This information message states that Essbase is writing the database definition
for the listed database. There is nothing wrong.
1019012 Reading Outline For Database databaseName
This information message states that Essbase is reading the outline definition
for the listed database. There is nothing wrong.
1019013 Writing Outline For Database databaseName
This information message states that Essbase is writing the outline for the listed database
back to the disk. There is nothing wrong.
1019014 Unable To Write Information For Database databaseName
Possible Problems
Essbase cannot find the listed database.
Possible Solutions
Make sure the database name is correct.
Make sure that the database exists in the specified location.
1019015 Database Outline Already Loaded For Database
databaseName
Possible Problems
The database outline for the listed database is already loaded.
Possible Solutions
Do not try to load a database more than once.
1019017 Reading Parameters For Database databaseName
This information message states that Essbase is reading the parameters
for the listed database. There is nothing wrong.
1019018 Writing Parameters For Database databaseName
This information message states that Essbase is writing the parameters
for the listed database. There is nothing wrong.
1019019 Reading Data File Free Space Information For
Database databaseName...
This information message states that Essbase is reading the free space
for the listed database. Free space information is stored in the
$ARBORPATH/app/applicationName/databaseName/databaseName.ind
file. If there is a lot of free space, it may take some time to read the free
space information. There is nothing wrong.
1019020 Writing Free Space Information For Database
databaseName
This information message states that Essbase is writing the free space
for the listed database. 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
This information message states that Essbase is reading database information
for the listed database. There is nothing wrong.
1019022 Writing Database Mapping For
databaseName
This information message states that Essbase is writing database information
for the listed database. There is nothing wrong.
1019024 Reading Outline Transaction For Database databaseName
This information message states that Essbase is reading the outline
updates from the
$ARBORPATH/app/applicationName/databaseName/databaseName.otn
file.
There is nothing wrong.
1019025 Reading Rules From Rule Object For Database
databaseName
This information message states that Essbase is reading a rules file for the
listed database. There is nothing wrong.
1019026 Unknown member memberName found while
processing string string
Possible Problems
Essbase does not recognize the listed string as a member of the outline.
Possible Solutions
Make sure that the member name is valid.
The member name is in the rules file.
1019028 Out of disk space, Unable to write information to
file fileName
Possible Problems
Essbase is out of disk space and cannot write to the listed file.
Possible Solutions
Make sure that you have enough disk space.
1019031 Unable to write fileName; database is in
readonly mode for backup
Possible Problems
Essbase cannot write to the listed file because the database is in read-only mode.
Possible Solutions
- 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 sleep
commands to make sure 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
Possible Problems
Essbase cannot write to the listed file because the database is in read-only mode.
Possible Solutions
- 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 sleep
commands to make sure 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
This information message states that Essbase is reading the outline
changes in the
$ARBORPATH/app/applicationName/databaseName/databaseName.ocl
file.
There is nothing wrong.
1019035 Writing Outline Change Log For Database
databaseName
This information message states that Essbase is writing the outline
changes to the
$ARBORPATH/app/applicationName/databaseName/databaseName.ocl
file.
There is nothing wrong.
1019036 Dimension number number for
Database databaseName is invalid
Possible Problems
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.
Possible Solutions
Check to see if the database is corrupt.
If the outline file is corrupt, restore the outline
file from backups.
1019037 Member number memberName for Database databaseName
is invalid
Possible Problems
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.
Possible Solutions
Check to see if the database is corrupt.
If necessary, restore the outline file from backups.
1019038 DB file is missing.
Possible Problems
Essbase cannot find the
$ARBORPATH/app/applicationName/databaseName/databaseName.db
file.
Possible Solutions
- If there is an
$ARBORPATH/app/applicationName/databaseName/databaseName.db
file, rename it to databaseNameold.db
. Then rename the
databaseName.dbb
backup file to databaseName.db
.
- If there is no
databaseName.db
file, rename the
databaseName.dbb
file to databaseName.db
.
- If there is no
databaseName.dbb
file, 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.
Possible Problems
Essbase cannot write to the listed file.
Possible Solutions
Make sure that Essbase is installed correctly. If necessary, reinstall Essbase.
1019040 Unable to write to file fileName
because the application is shutting down
Possible Problems
Essbase cannot write to the listed file because the application is closing.
Possible Solutions
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 each of the following steps.
- As a user, exit Application Manager or Spreadsheet Add-in.
- If the previous step does not work, have the administrator
disconnect the user.
- If the previous step does not work, unlock any
locked objects, unload the
database, stop the database,
and try again to disconnect the user.
- If the previous step does not work, have the administrator log off the user
in the Agent window.
- If the previous step does not work, stop the application from the Agent window.
- If the previous step does not work, end the task.
- If the previous step does not work, restart the server machine.
1019041 Unable to write information to file fileName,
adWriteObject returns EssbaseErrorNumber. See server logfile for details.
Possible Problems
Essbase cannot write to the listed file.
Possible Solutions
- Check the
$ARBORPATH/app/applicationName/applicationName.log
log
for more information about the listed Essbase error number.
- Make sure that the file exists. If it does not exist,
restore the file from backups.
- Make sure that you have enough disk space.
- Make sure that the following environment
variables are set correctly:
ARBORPATH
(PC and UNIX)
PATH
(PC and UNIX)
LD_LIBRARY_PATH
(UNIX only)
- If you are on a UNIX computer, check the
user limit profile.
- Verify that you are using data compression to limit page
file size.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.db
,
replace the file with its backup:
- Stop OLAP Server.
- Rename
databaseName.db
to databaseNamedb.old
.
- Rename
databaseName.dbb
to databaseName.db
.
- Restart OLAP Server.
- If the listed file is
$ARBORPATH/App/applicationName/databaseName/databaseName.ind
,
try to restore the file from backups.
If that doesn't work, then delete and reload the data files. Deleting your data files deletes all the data in your database; you will have to
reload and recalculate the database.
- Stop OLAP Server.
- Delete the
databaseName.ind
,
Essxxx.ind
, Essxxx.pag
,
databaseName.esm
, and
databaseName.tct
files.
- Restart OLAP Server.
- Reload the database.
- Recalculate the database.
See Also
1019004
1019042 Unable to move the file pointer to the location
specified for file fileName, errno is operatingSystemError.
Contact Hyperion Technical Support.
1019043 Error Creating Outline Pool For
Database databaseName
Possible Problems
Essbase can not create the outline memory pool. The outline
memory pool holds outline items in memory.
Possible Solutions
Make sure that you have enough memory on the server
computer.
1019044 Error Allocating Mem in Outline Pool For
Database databaseName
Possible Problems
Essbase can not create the outline memory pool. The outline
memory pool holds outline items in memory.
Possible Solutions
Make sure that you have enough memory on the server
computer.
1019045 Reading Partition Definition File For
Database databaseName
This information message states that Essbase is reading
the partition definition file for the listed database. There is nothing wrong.
1019046 Outline buffer cannot handle more than
number hole
Contact Hyperion Technical Support.
1019047 Outline buffer error. Hole position number does
not match with number in the buffer
Contact Hyperion Technical Support.
1019048 Outline buffer writing error. number bytes written
does not match with hole size number
Contact Hyperion Technical Support.
1019049 Outline buffer error. Cannot flush buffer with
number hole to a fragmented outline file
Contact Hyperion Technical Support.
1019050 Outline buffer error. File position number does not
match with number bytes written
Contact Hyperion Technical Support.
1019051 Total adReadStruct Elapsed Time using outline
buffer: number seconds
This information message states the time used to read the
outline buffer. There is nothing wrong.
1019052 Total adOtlReadOutline Elapsed Time
using outline buffer: number seconds
This information message states the time used to read the
outline data into memory. There is nothing wrong.
1019053 Total adOtlWriteOutline Elapsed Time using outline
buffer: number seconds
This information message states the time used to write the
outline data. There is nothing wrong.
1019054 Invalid Named Attribute Opcode For
Member memberName
Possible Problems
The type defined for the listed attribute member is not valid.
Possible Solutions
Make sure that all attribute members use one of the following types:
text, numeric, Boolean, or date.
1019056 Object file path path is too long.
Possible Problems
The listed path is too long.
Possible Solutions
Make sure that the listed path is smaller than 1025 bytes.