ÿþE ssbase E rror M essage R eference R

Oracle® Essbase
Error Message Reference
Release 11.1.2.3
Essbase Error Message Reference, 11.1.2.3
Copyright © 1996, 2013, Oracle and/or its affiliates. All rights reserved.
Authors: EPM Information Development Team
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation
of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find
any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of
the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS:
Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers
are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition
Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and
adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to
the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial
Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates
disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
This software or hardware and documentation may provide access to or information on content, products, and services
from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any
kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible
for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Documentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 1. Understanding Essbase Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Chapter 2. 1002122 to 1270527: Aggregate Storage Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 3. 1003000 to 1003048: Data Load Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 4. 1006002 to 1006057: Data Cache Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 5. 1008001 to 1008152: System Call Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Chapter 6. 1012000 to 1012750: Calculation Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Chapter 7. 1013000 to 1013999: Requestor Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Chapter 8. 1014004 to 1014043: Lock Manager Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Chapter 9. 1019002 to 1019056: Database Object Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Chapter 10. 1040002 to 1042025: Network Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Chapter 11. 1051002 to 1055041: Agent Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Chapter 12. 1120000 to 1120002: C Grid API Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Chapter 13. 1130203 to 1130613: Miscellaneous Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Appendix A. Referenced Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Setting Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Checking for Database Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Fixing Database Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Replacing Database Files with Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Checking the User Limit Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Setting NETDELAY and NETRETRYCOUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Ending the Server Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Unlocking Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Determining Operating System Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Contents
iii
iv
Contents
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://
www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=trs if you are hearing impaired.
5
6
Documentation Accessibility
1
Understanding Essbase Error
Messages
This document describes common Oracle Essbase error messages and informational messages,
including possible causes and possible solutions for the errors. This reference does not document
every error message that you may encounter.
See also the Oracle Essbase Database Administrator's Guide and the Oracle Essbase Technical
Reference.
Table 1 provides error message categories for each error number range that is shown in the first
column. When you receive an error message, use this table to identify the Essbase component
to which the error is related. .
Table 1
Error Message Categories
Error Message Number Range
Component That Generated the Error
1001000-1001999
Report Writer
1002000-1002999
General server
1003000-1003999
Data load
1004000-1004999
General server
1005000-1005999
Backup, export, or validate
1006000-1006999
Data cache
1007000-1007999
Outline restructure
1008000-1008999
System calls, portable layer, ASD, or Agent
1009000-1009999
Restoring ASCII data
1010000-1010999
Internal (block numbering)
1011000-1011999
Internal (utilities)
1012000-1012999
Calculator
1013000-1013999
Requestor
1014000-1014999
Lock manager
1015000-1015999
Alias table
1016000-1016999
Report Writer
7
8
Error Message Number Range
Component That Generated the Error
1017000-1017999
Currency
1018000-1018999
Not currently used
1019000-1019999
Database artifacts
1020000-102999
Spreadsheet extractor
1021000-1021999
SQL Interface
1022000-1022999
Security
1023000-1023999
Partitioning
1024000-1024999
Query Extractor
1030000-1030999
API
1040000-1040999
General network
1041000-1041999
Network—Named Pipes
1042000-1042999
Network—TCP
1043000-1049999
Not currently used
1050000-1055999
Agent
1056000-1059999
Not currently used
1060000-1060999
Outline API
106100-1069999
Not currently used
1070000-1070999
Index manager
1071000-1079999
Not currently used
1080000-1080099
Transaction manager
1081000-1089999
Not currently used
1090000-1099999
Rules file processing
1010000-1019999
Not currently used
1100000-1100999
Not currently used
1110000-1119999
Oracle Hyperion Web Analysis
1120000-1129999
Grid API
1130000-1139999
Miscellaneous
1140000-1149999
Linked Reporting Objects (LRO)
Understanding Essbase Error Messages
Error Message Number Range
Component That Generated the Error
1150000-1159999
Outline synchronization
1160000-1169999
Outline change records
1170000-1179999
Attributes
1180000-1189999
Showcase
1190000-1199999
Oracle Essbase Integration Services
1200000-1200999
Calculator framework
9
10
Understanding Essbase Error Messages
2
1002122 to 1270527: Aggregate
Storage Messages
Table 2 lists general server error and informational messages that are specific to aggregate storage.
Table 2
Aggregate Storage Messages 1002122 to 1270517
Message
Number
Message
Possible Cause
Possible Solution
1002112
Unable to convert outline
[%s], verification failed.
The OTL file is corrupt.
Copy the OTL file from a successful
backup and paste it to overwrite the
corrupt OTL file. Start the application and
database, and then verify the outline.
1002122
Aggregate storage
applications ignore disk
volume settings in essbase.
cfg
A DISKVOLUMES setting that applies to this
database is specified in essbase.cfg.
Essbase ignores this setting as it does not use
disk volume settings to allocate storage for
aggregate storage databases.
Allocate storage by defining tablespace
properties in the Administration Services
Console or by using MaxL.
Essbase uses tablespaces to optimize data
storage and retrieval for aggregate storage data
files and work files. Tablespaces are location
definitions that map data objects, such as
aggregate views and aggregations to files.
1003055
Aggregate storage
applications ignore update
to derived cells. [%s] cells
skipped
The data source contains data values for upper
level aggregate cells or for members with
formulas. For aggregate storage databases, you
cannot load data to upper level cells or cells
whose values depend on formulas in the outline.
Load data only to level zero cells whose
values do not depend on formulas in the
outline.
1023057
Cannot replace partition
definition file while there are
other active users on
database [%], check
application log for details
Creating or replacing a partition definition is an
administrative task that requires exclusive
access to the database by the administrative
account user.
Log off other users.
You cannot restructure a database if there are
other users active on the database.
Log off other users.
Transaction [%] aborted
due to status [1023057]
1013101
Cannot restructure. There
are other active users on
database [%s]
11
Message
Number
Message
Possible Cause
Possible Solution
1013294,
1241164
A stopping size strictly
greater than 1.0 is required
for aggregate selection
Essbase cannot select aggregate views because
the storage stopping value, specified using MaxL,
is smaller than 1.0.
Specify a storage stopping value that is
1.0 or greater.
1060145,
1150091
It is not possible to have a
formula on a label member
A label only member has a formula associated
with it. No data is associated with label only
members, so it does not make sense for them to
have formulas.
Remove the formula.
1060147
Aggregate storage outlines
require non level-0
members in accounts
dimension and dynamic
hierarchies to be either nonstored members or have
internal/external formula
A non level 0 member in the accounts dimension
or in a dynamic hierarchy has these traits:
Ensure that all non level 0 members in
the accounts dimension and in dynamic
hierarchies are tagged as label only,
have a child that rolls up, or have a
member formula.
Label-only members must
span all of the uppermost
levels.
In a stored hierarchy, either:
1060149
l
No label only tag.
l
No child that rolls up.
l
No member formula.
l
l
1060172
Aggregate storage outlines
only allow any shared
member once in a stored
hierarchy, including
prototype.
The parent of a label only member is not
tagged as label only.
A member at the same level as a label only
member is not tagged as label only.
A stored hierarchy in a dimension where multiple
hierarchies are enabled contains either:
l
A non-shared instance of a member and a
shared instance of that member.
l
Two shared instances of one stored member.
The stopping value is the database size,
expressed as a multiple of the size of the
unaggregated level 0 data. For example,
a stopping value of 1.5 means that the
aggregation should increase the
database size by no more than 50%. It
does not make sense to specify a value
lower than 1.0, because that would
mean the aggregated database size is
smaller than the size of the original
unaggregated level 0 data.
Convert the label only member to a nonlabel only member of a dynamic
hierarchy (stored hierarchies cannot
have formulas).
Ensure that the parents of label only
members are also label only.
Ensure that members at the same level
as label only members are also label
only.
Be sure that stored hierarchies in
dimensions with multiple hierarchies
enabled do not contain two shared
instances of one member or one nonshared and one shared instance of one
member.
1060175
Top member in dimensions
with multiple hierarchies
must be tagged as Label.
The label only tag was removed from the top
member in a dimension with multiple hierarchies
enabled. When you tag the top level member as
multiple hierarchies enabled, it is automatically
tagged as label only, but it is possible to remove
the tag. If the label only tag is removed, the
outline fails verification.
Tag the top level member as label only.
1060180
The primary hierarchy must
be tagged as Stored.
The member representing the first hierarchy (top
level member of the hierarchy) in a dimension
that has multiple hierarchies enabled is not
tagged as a stored hierarchy. Essbase requires
such a hierarchy to be a stored hierarchy.
Tag as a stored hierarchy, the top-level
member of the first hierarchy in the
dimension.
12
1002122 to 1270527: Aggregate Storage Messages
Message
Number
Message
Possible Cause
Possible Solution
1150085
OUTLINE SYNC VERIFY:
Member %s has an incorrect
label tag. Label only
members must span all of
the uppermost levels.
In a stored hierarchy, either:
Ensure that the parents of label only
members are also label only.
OUTLINE SYNC VERIFY:
Member %s has an incorrect
aggregation operator.
Aggregate storage outlines
require all members of nonaccounts dimensions to
have ADD (+) aggregation,
except for label-only
members and their children
A non-accounts dimension member in a release
7.1 outline does not have an addition (+)
consolidation operator and it is not tagged as:
OUTLINE SYNC VERIFY:
Aggregate storage outlines
require non level-0 member
%s in accounts dimension
to be either non-stored
members or have internal/
external formula
A non-level 0 member in the accounts dimension
or in a dynamic hierarchy is not tagged as label
only, had no member formula, and is not an
aggregated value.
Ensure that all non-level 0 members in
the accounts dimension and in dynamic
hierarchies are tagged as label only,
have at least one child that rolls up, or
have a member formula.
Memory allocation failed
Essbase cannot complete the requested
operation because it ran out of memory.
Check the Essbase Server memory
requirements.
1150086
1150090
l
l
The parent of a label only member is not
tagged as label only.
A member at the same level as a label only
member is not tagged as label only.
l
A label only member
l
The child of a label only member
Ensure that members at the same level
as label only members are also label
only.
Apply the addition (+) consolidation
operator to the member.
Note: When editing aggregate storage
outlines that were created in release 7.
1, the restrictions on release 7.1
aggregate storage outlines apply, even if
you are using a later release of Essbase.
1150091
See
1060145,
1150091
1241164
See
1013294,
1241164
1270001
Configure the operating system to handle
more memory.
If necessary, increase the physical
memory.
1270004
Cannot complete operation:
insufficient aggregate
storage cache size
Essbase cannot perform the requested operation
because the aggregate storage cache size is
insufficient.
Use these guidelines to estimate the
correct aggregate storage cache size.
13
Message
Number
Message
Possible Cause
Possible Solution
1270005
Fatal error: invalid page
encountered in aggregate
storage file at location [%s]
The database is corrupt.
Delete the application using Oracle
Essbase Administration Services or MaxL
and rebuild it from backup files. Do not
delete the application from the file
system.
If you cannot delete the application,
delete all tablespace directories and file
locations, and reload data.
Tablespace directories:
ARBORPATH/app/default
ARBORPATH/app/log
ARBORPATH/app/metadata
ARBORPATH/app/temp
Call Oracle Support.
1270006
Failed to extend tablespace
[%s]. Please see
application log for details
Essbase cannot extend files, nor can it create
files in the tablespace file locations. Possible
causes of this problem include:
Look in the application log for warning
messages that led up to this error.
l
Running out of disk space
Specify additional file locations to
accommodate the application.
l
Reaching a user specified limit
Call Oracle Support.
Essbase uses tablespaces to optimize data
storage and to optimize retrieval for data files and
work files. Tablespaces define one or more
location definitions that map data objects, such
as aggregate views and aggregations, to files.
You can specify the maximum file size allowed
within each location in a tablespace.
As needed, Essbase allocates disk space in fixed
size increments. When Essbase fails to extend a
tablespace, it prints a warning message to the
application log, indicating why it could not
extend the tablespace. After each failure,
Essbase makes another attempt to extend the
tablespace. After repeated failures, this error
message is displayed.
1270009
1270011
14
Failed to remove
tablespace: operation not
allowed on this special
tablespace
You specified for removal a tablespace that
cannot be removed.
Failed to create file location
[%s]: that file location is
already used by this
tablespace
Essbase cannot create the listed file location
because the file location is used.
Essbase sets up two tablespaces that cannot be
altered (log and metadata). You cannot remove
the system defined tablespaces. In addition, you
cannot delete a file location within a default or
temp tablespace if it contains data.
1002122 to 1270527: Aggregate Storage Messages
Check whether this is the metadata or log
tablespace. Essbase cannot remove
metadata and log tablespaces.
Check whether the tablespace contains
data. Essbase cannot remove
tablespaces that contain data.
Specify another file location.
Message
Number
Message
Possible Cause
Possible Solution
1270018
Failed to create file location:
path too long
The path that you specified for the tablespace
file location is too long.
Specify a file location path that is 460
bytes or less.
1270022
Failed to extend file: user
limit reached
Essbase cannot further increase the size of the
listed file because it has reached the specified
maximum file size for that location in the
tablespace.
Increase the maximum file size setting for
that tablespace location.
Essbase uses tablespaces to optimize data
storage and to optimize retrieval for data files and
work files. Tablespaces define one or more
location definitions that map data objects, such
as aggregate views and aggregations, to files.
You can specify the maximum file size allowed
within each location in a tablespace.
1270024
Fatal error at [%s], line
[%s]; terminating the server
The aggregate storage application is about to
shut down abnormally.
Messages before this one in the
application log may indicate the cause
of the abnormal shutdown.
Call Oracle Support.
1270030
Cannot proceed: the cube
has no aggregations
Essbase cannot clear aggregate views because
no aggregate views exist in the database.
Proceed with your next task. You do not
need to clear aggregate views because
none exist in the database.
1270032
The specified view list is
invalid or the views were
selected using a different
outline
Essbase cannot use the view list. Significant
changes may were made to the outline after the
views were last selected. Examples of outline
changes that may make a view list invalid are
changes to the number of dimensions or to the
number of levels in a dimension.
After changing an outline, delete
obsolete views (this is not done
automatically).
1270035
Cannot alter tablespace:
this tablespace is special
You tried to add, remove, change the location of,
or change the size of the listed log or metadata
tablespace. Altering log or metadata
tablespaces is not permitted.
Check the rules for working with
tablespaces.
1270036
Cannot add file location: file
location directory [%s]
already exists. If this
directory is not in use by
another application, please
remove it and try again.
A directory exists at the file location specified.
Choose another file location.
Failed to remove file
location: file location
already has blocks
allocated
Essbase cannot remove a file location in a
tablespace if the database contains data.
1270039
Repeat aggregate view selection after
making major changes to the outline.
If you are sure that the directory is not
used by another application, remove it
and try to create the file location again.
Clear data from the database, and
remove the file location.
15
Message
Number
Message
Possible Cause
Possible Solution
1270040
Data load buffer [%s] does
not exist
A data load buffer has not been created. When
using MaxL to load data to an aggregate storage
database, you must specify a buffer ID.
If using MaxL to load data, ensure you
specify a buffer ID.
The data load buffer was destroyed. The data
load buffer is automatically destroyed in some
cases, such as running out of disk space during
a data load. It can also be destroyed using MaxL,
alter database.
If you encountered a problem that
caused the data load buffer to be
destroyed, resolve that problem, and
retry the data load.
1270041
Sort operation ran out of
memory. Please increase
the size of the aggregate
storage cache
The aggregate storage cache size is too small.
Increase the aggregate storage cache
size.
1270044
Cube cannot have more
than [%s] aggregates
Essbase cannot create additional aggregate
views because it has reached the upper limit.
Select fewer aggregate views.
1270047
Data load buffer [%s] is
currently in use
Essbase cannot execute the MaxL command,
alter database destroy load_buffer, because the
data load buffer is active. The data load buffer is
active when data is being loaded to it or from it.
Wait until the data load is finished, and
issue the command again.
1270049
The data set is too small to
perform this operation
An aggregate view contains less than 1,000
cells.
Increase the number of cells in an
aggregate view.
1270052
Failed to aggregate views.
Please see application log
for more information
Essbase could not aggregate the aggregate
views.
Additional error or warning messages in
the application log should indicate the
cause of the problem.
1270054
Failed to read bytes from
file: end of file
The database is corrupt.
Delete the application using
Administration Services or MaxL and
rebuild it from backup files. Do not delete
the application from the file system.
If you cannot delete the application,
delete all tablespace directories and file
locations, and reload data.
Tablespace directories:
ARBORPATH/app/default
ARBORPATH/app/log
ARBORPATH/app/metadata
ARBORPATH/app/temp
Call Oracle Support.
1270057
Requested file size limit is
greater than maximum.
Setting file size limit to
maximum
Essbase cannot accept the specified file size for
the tablespace because it is greater than the
maximum. Instead, Essbase sets the file size
limit to the maximum.
Specify a file size limit that is smaller
than or equal to the maximum.
1270058
No file locations exist in
tablespace
Essbase cannot write to a tablespace because
all tablespace file locations are removed.
Add a file location to the tablespace. It
is possible to remove all file locations
from a tablespace, but one or more file
locations must exist before data can be
written to it.
16
1002122 to 1270527: Aggregate Storage Messages
Message
Number
Message
Possible Cause
Possible Solution
1270059
Specified maximum disk
size is not on 8 MB
boundary. Rounding up to
nearest 8 MB
The maximum disk size for the tablespace file
location is set to a number that is not a multiple
of 8. Essbase allocates disk space in 8 MB
segments, so it understands settings that are
multiples of 8, for example 8, 16, 24, 32.
Do nothing. Essbase automatically
rounds up to the nearest 8 MB.
1270060
Specified maximum file size
is not on 8 MB boundary.
Rounding up to nearest 8
MB
The maximum file size for the tablespace file
location is set to a number that is not a multiple
of 8. Essbase increments files in 8 MB segments,
so it recognizes settings that are multiples of 8,
for example 8, 16, 24, 32.
Do nothing. Essbase automatically
rounds up to the nearest 8 MB.
1270063
Attempting to re-create all
aggregate storage files
Essbase is unable to find data files (.dat files)
while attempting to start an aggregate storage
application. It is attempting to create dummy
data files, containing no data, to enable the
application to start. This is because the data files
are corrupt or were accidentally deleted.
Restore the original data files from a
backup copy.
Essbase cannot execute the execute aggregate
selection MaxL command because the view list
provided does not meet one of these
requirements:
Replace the aggregation.
1270069
Preselected view list must
begin with input view; it
must be followed by all
existing aggregate views for
query-based view selection
l
l
1270070
Serial number [%s] in the
page header doesn't match
[%s] in the footer
Contact Oracle Support.
In the using views clause, ensure you list
all views in the aggregation.
You are selecting views based on query data,
and the aggregation script (.csc) file that
you are using does not contain all views in
the current aggregation.
In MaxL, you are selecting views based on
query data, and you did not list all views in
the using clause.
The database is corrupt.
Delete the application using
Administration Services or MaxL and
rebuild it from backup files. Do not delete
the application from the file system.
If you cannot delete the application,
delete all tablespace directories and file
locations, and reload data.
Tablespace directories:
ARBORPATH/app/default
ARBORPATH/app/log
ARBORPATH/app/metadata
ARBORPATH/app/temp
Call Oracle Support.
17
Message
Number
Message
Possible Cause
Possible Solution
1270071
Page ID [%s] in the page
header doesn't match page
location
The database is corrupt.
Delete the application using
Administration Services or MaxL and
rebuild it from backup files. Do not delete
the application from the file system.
If you cannot delete the application,
delete all tablespace directories and file
locations, and reload data.
Tablespace directories:
ARBORPATH/app/default
ARBORPATH/app/log
ARBORPATH/app/metadata
ARBORPATH/app/temp
Call Oracle Support.
1270082
A system error occurred with
error number [%s]: [%s].
The operating system encountered a problem.
This is an operating system error.
Check the operating system
documentation.
The outline generated more warnings than
Essbase can display. Essbase does not display
further warnings.
Ignore this message and continue to use
the outline. Essbase does not prevent
you from using an outline that generates
warnings.
Note: The second [%s] is
replaced by a description of
the error as reported by the
operating system.
1270506
Outline generated too many
warnings. Further warnings
ignored
Edit the outline to remove conditions that
generate warnings.
1270517
Hierarchy [%s] is too
complex: maximal width
member number exceeds
64 bits. See application log
for details
The specified hierarchy contains too many levels.
1270526
Alternate hierarchy [shared]
is attached to the primary
hierarchy at an unstored
level
A shared member's prototype can not be a label
only member.
1270527
Attribute dimension [%s]
has an invalid association
with an alternate hierarchy.
For alternate hierarchies,
attributes may only be
associated with members at
level zero.
An attribute dimension can not be tagged to an
upper level stored hierarchy unless it is primary.
18
1002122 to 1270527: Aggregate Storage Messages
Reduce the number of levels in the
hierarchy.
3
1003000 to 1003048: Data Load
Messages
Table 3 lists data load error and informational messages.
Table 3
Data Load Messages 1003000 to 1003048
Message
Number
Message
Possible Cause
Possible Solution
1003000
Unknown Item itemName in Data
Load, number Records
Completed
Essbase encountered a
field in the data source
that it did not
recognize.
Examine the data load log for other messages that may help
to identify the problem.
Related
Topics
1003034
Ensure that the data source is valid. If no records loaded,
either the first record is invalid or the entire data source is
invalid.
l
Is the data source corrupt?
l
Is the data source in the correct location?
l
Is the data source correctly formatted?
Ensure that the record that caused the data load to fail is
valid.
l
Is a member from each dimension specified in the data
source or the rules file?
l
Is each member name in the record valid?
l
Are there multiple numeric data fields in the record?
l
Try removing the record that caused the data load to fail
and running the data load again.
If you are using a rules file, ensure that the rules file is valid.
l
Is the rules file in the correct location?
l
Is the rules file set up correctly?
l
Can you validate the rules file?
If you are using ESSCMD, ensure that the syntax is valid.
l
Check the error log in the ESSCMD script to determine
where the unknown item exists.
l
Are the parameters correct and enclosed in quotation
marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2
"ACTUALS" "Y";
l
Do the files you are loading exist in the correct locations?
l
Can you run the data load using Administration Services?
19
Message
Number
Message
Possible Cause
Possible Solution
1003001
Duplicate Members From Same
Dimension On Data Record,
number Records Completed
Essbase encountered
multiple members from
a dimension in one
record. Essbase does
not load this record and
skips to the next record.
Ensure that the data source is valid.
Related
Topics
1003015
l
l
l
Does each record contain only one member name for
each dimension? For example, the Time dimension can
contain only January in one record. If columns contain
duplicate members in a record, ignore those columns.
Is each member name mapped to the correct dimension?
For example, in the Sample Basic database, January
should be mapped to the Time dimension.
Are member or alias names duplicated in other
dimensions? Member and alias names must be unique.
For example, January cannot exist in the Time and Market
dimensions. If names of members or aliases in other
dimensions match, add a prefix or suffix to the members
or aliases in one dimension to make them unique.
l
Are ranges set up correctly?
l
Are all members that might contain numbers (such as
"100") enclosed in quotation marks in the data source?
l
Are two members from one dimension on one line in the
data source?
If you are using a rules file, ensure that it is valid.
l
Are extra member names ignored in the rules file?
l
Do you need to move columns to ensure that each
member is connected to the correct dimension?
If you are using ESSCMD, ensure that the syntax is valid.
l
Check the error log in the ESSCMD script to determine
where the duplicate member exists.
l
Are the parameters cirrect and enclosed in quotation
marks? For example:
IMPORT 2 "ACTUALS" 4 "Y" 2
"ACTUALS" "Y";
l
Do the files you are loading exist in the correct locations?
l
Can you run the data load using Administration Services?
If you are using Integration Services, try these steps:
l
Ensure that duplicate members that are shared are
tagged as such.
l
Ensure that member names are unique.
l
Map all members to the correct dimension.
l
Ensure that you are using the correct DataDirect drivers.
l
Launch Integration Server using a non-default value for
the -B parameter.
l
20
1003000 to 1003048: Data Load Messages
In Integration Services Console, select Delete All
Members First; in Integration Services shell, use OTL_
CLEAR=[Y].
Message
Number
Message
Possible Cause
Possible Solution
1003003
Unable to Continue Data Load
After Item itemName, number
Records Completed
Essbase aborted the
data load. This error
message usually
occurs after other error
messages that
describe why the data
load failed.
Look through the data load error log to see why the data load
failed.
If no data load error log exists, set up the load to create an
error log and restart the data load.
Check the error messages that preceded this error message
to determine what happened.
In the data source, ensure that all data fields are after the
member name fields. In the rules file, ensure that you define
the fields using dimension names instead of member names.
1003004
Related
Topics
Incorrect Number of Column
Members in Symmetric File After
recordNumber Records
Completed
1003005
Essbase encountered
more or fewer columns
than it expected while
reading the data
source.
Ensure that the data source is valid.
l
l
1003005
Related
Topics
Incorrect Number of Column
Members in Asymmetric File After
recordNumber Records
Completed
1003004
Essbase encountered
more or fewer columns
than it expected while
reading the data
source.
1003007
Are all ranges set up correctly in the data source?
Ensure that the data source is valid.
l
l
1003006
Are all members that might contain possible file
delimiters (such as spaces or commas) surrounded by
quotation marks in the data source?
Are all members that might contain possible file
delimiters (such as spaces or commas) surrounded by
quotation marks in the data source?
Are all ranges set up correctly in the data source?
Unknown Text File Type After
recordNumber Records
Completed
Essbase did not
recognize the text file.
Ensure that the text file is valid.
Data value numericValue
Encountered Before All
Dimensions Selected
Essbase encountered a
numeric data value in
the data source before
all dimensions were
specified.
Ensure that the data source is valid.
If multiple records loaded, ensure that ranges in the data
source are correctly formatted.
l
l
l
l
Is a member from each dimension specified correctly in
the data source or rules file?
Is the numeric data field at the end of the record? If not,
move the numeric data field in the data source or move
the numeric data field in the rules file.
Are all members that might contain numbers (such as
"100") enclosed in quotation marks in the data source?
If you are using a header, is the header set up correctly?
Remember that you can add missing dimension names
to the header.
l
Does the data source contain extra spaces or tabs?
l
Has the updated outline been saved?
21
Message
Number
Message
Possible Cause
Possible Solution
1003008
With Data Value numericValue,
Too Many Values In Row,
number Records Completed
Essbase encountered
more numeric data
fields in the record than
it can map to the
database.
Ensure that the data source is valid.
l
Are all members that might contain numbers (such as
"100") enclosed in quotation marks in the data source?
l
Are extra numeric data fields in the record? If so, you can
ignore extra data fields.
l
Is the numeric data field the last field in the record? If
not, move the numeric data field in the data source or
move the numeric data field in the rules file.
l
Is each field in the data source valid?
l
Is each dimension specified in the data source or the
rules file?
Ensure that the rules file is valid.
1003010
Related
Topics
Data Value numericValue Does
Not Match #Missing Value in
Database, number Records
Completed
1003011
1003012
Essbase encountered a
problem when it tried to
validate the database
against the data source
to see if both contain
the same values.
Ensure that the data source is the contains the same values
as the database.
Essbase encountered a
problem when it tried to
validate the database
against the data source
to see if both contain
the same values.
Ensure that the data source contains the same values as the
database.
Essbase encountered a
problem when it tried to
validate the database
against the data source
to see if both contain
the same values.
Ensure that the data source contains the same values as the
database.
Essbase encountered a
problem when it tried to
validate the database
against the data source
to see if both contain
the same values.
Ensure that the data source contains the same values as the
database.
Ensure that you are validating the database against the
correct data source.
If you think that the data loaded incorrectly, ensure that the
data source is set up correctly.
1003013
1003011
Related
Topics
Data Value numericValue Does
Not Match #Invalid Value in
Database, number Records
Completed
1003010
1003012
Ensure that you are validating the database against the
correct data source.
If you think that the data loaded incorrectly, ensure that the
data source is set up correctly.
1003013
1003012
Related
Topics
Data Value numericValue Is
Greater Than Value in Database,
number Records Completed
1003010
1003011
Ensure that you are validating the database against the
correct data source.
If you think that the data loaded incorrectly, ensure that the
data source is set up correctly.
1003013
1003013
Related
Topics
Data Value numericValue Is Less
Than Value in Database,
number Records Completed
1003010
1003011
1003012
22
1003000 to 1003048: Data Load Messages
Ensure that you are validating the database against the
correct data source.
If you think that the data loaded incorrectly, ensure that the
data source is set up correctly.
Message
Number
Message
Possible Cause
Possible Solution
1003014
Unknown Member
memberName in Data Load,
number Records Completed
Essbase did not
recognize the member
name.
Ensure that the data source is valid.
l
Are you using the correct data source?
l
Is there an incorrect member in the data source? If so,
delete that member.
l
Did you try to load the correct data source with the correct
rules file?
l
Is the file extension correct for the data source? All text
files must have a file extension of .txt. All rules files
must have a file extension of .rul.
Ensure that the rules file is valid.
l
Are you using the correct rules file?
l
Is the rules file connected to the correct outline?
l
Can you validate the rules file?
Ensure that the member name is valid.
l
l
l
Are member names or variable names enclosed in
quotation marks where necessary?
Does the member exist in the outline? If not, you can add
the member by modifying the outline during the data load
or by adding the member in the Outline Editor.
Ensure that the member is not specified in both the
header file and the text file.
If you are using ESSCMD, ensure that the ESSCMD syntax is
valid.
l
Check the error log in the ESSCMD script to determine
where the unknown member name exists.
l
Are the parameters enclosed in quotation marks? For
example:
IMPORT 2 "ACTUALS" 4 "Y" 2
"ACTUALS" "Y";
l
Are the parameters correct?
l
Do the files you are loading exist in the correct locations?
l
Can you run the data load using Administration Services?
If you are using Oracle Essbase Integration Services, ensure
that these conditions are met.
l
l
If members in other dimensions have matching names,
add a prefix or suffix to the member names to make them
unique.
Ensure that the outline build is successful before starting
the data load.
23
Message
Number
Message
Possible Cause
Possible Solution
1003015
Member memberName is from
the same dimension as members
defined in Header Name,
number Records Completed
Essbase aborted the
load because two
different members
were specified for the
same dimension. One
member from the
dimension was
specified in the header
record and another
member from the same
dimension was
specified in a record in
the data source.
Ensure that the data source is valid.
Related
Topics
1003001
24
1003000 to 1003048: Data Load Messages
l
l
Did you set the correct record as the header record?
Do members that you specify in the header also appear
in the data source? If so, you must change the header
record or the data source.
If you are using a rules file, ensure that the rules file is valid.
l
Did you set the correct record as the header record?
l
Are extra member names that should be ignored in the
rules file?
l
Can you validate the rules file?
l
Did you accidentally reject the header record?
Message
Number
Message
Possible Cause
Possible Solution
1003022
Unable to Open Data File
Essbase cannot open
the data file.
Ensure Essbase can find the data file.
Related
Topics
1003027
l
Are the data file name and path name correct? Check for
misspellings.
l
If Essbase Server is on a computer running UNIX, is
capitalization correct?
l
Is the data file in the specified location? Ensure that no
one moved or deleted the data file.
1003030
Ensure Essbase can use the data file.
l
l
Is the data file locked by a another user (see “Unlocking
Objects” on page 126)
Is the file extension for the data file correct? All text files
must have a file extension of .txt. All rules files must
have a file extension of .rul.
l
Is the data file valid?
l
Are your permissions correct for the Essbase database
into which you are loading the data file?
l
Are your operating system privileges correct for the data
file you are trying to load?
If you are using ESSCMD, ensure that you are using the
IMPORT command correctly. When you issue the IMPORT
command, you have four options to choose the data file
location.
l
1 (local/client object): Ensure the data file is in the
client folder.
Ensure you have read access to the data file.
If Essbase Server is on a UNIX platform, remember that
the file name is case-sensitive and check capitalization.
l
2 (remote server object): Ensure you have read access
to the data file.
If Essbase Server is on a UNIX platform, remember that
the file name is case-sensitive and check capitalization.
l
l
3 (file): Ensure that you specified the absolute path
name and the full file name (including the file type
extension).
4 (SQL): Check the ODBC connections.
Ensure Essbase Server is properly configured.
1003023
You have insufficient access
privileges to perform a lock on
this database
You did not have the
necessary permissions
to lock the database so
that you can load data.
Contact your Essbase system administrator.
If you are a system administrator, grant yourself the correct
permissions.
25
Message
Number
Message
Possible Cause
Possible Solution
1003024
Data Load Elapsed time :
number seconds
Length of time it took
Essbase to load a data
source.
Not applicable
1003025
DATAERRORLIMIT reached
numberOfRecords. Rejected
records will no longer be logged
The error log was full.
Fix the errors in the data load or dimension build error log
and restart the data load.
You have too many
error messages to fit in
the data load or
dimension build error
log, or you are rejecting
too many records to fit
in the log.
Change the maximum number of records allowed in the data
load or dimension build error log.
1. If ESSBASEPATH/bin/ essbase.cfg does not exist
on the server computer, create one using a text editor.
2. Add or increase the DATAERRORLIMIT setting in the
ESSBASEPATH/bin/essbase.cfg file.
3. Stop and restart Essbase Server.
4. Restart the data load.
26
1003000 to 1003048: Data Load Messages
Message
Number
Message
Possible Cause
Possible Solution
1003027
Unable to open file
Essbase cannot open
the file.
Ensure Essbase can find the file.
Related
Topics
1003022
l
Are the file name and path name correct? Check for
misspellings.
l
If Essbase Server is on a UNIX platform, is capitalization
correct?
l
Is file is in the specified location? Ensure that no one has
moved or deleted the file.
1003030
Ensure Essbase can use the file.
l
l
Is the data file locked by another user (see “Unlocking
Objects” on page 126) ?
Does the file have the correct file extension? All text files
must have a file extension of .txt. All rules files must
have a file extension of .rul.
l
Is the file valid?
l
Do you have the correct permissions for the Essbase
database into which you are loading the file?
l
Do you have the correct operating system privileges for
the file you are trying to load?
If you are using ESSCMD, ensure that you are using the
IMPORT command correctly. When you issue the IMPORT
command, you have four options to choose the file location .
l
1 (local/client object): Ensure that the data file is in the
client folder.
Ensure that you have read access to the data file.
If Essbase Server is on a UNIX platform, remember that
the file name is case-sensitive and check capitalization.
l
2 (remote server object): Ensure that you have read
access to the data file.
If Essbase Server is on a UNIX platform, remember that
the file name is case-sensitive and check capitalization.
l
l
3 (file): Ensure that you specified the absolute path
name and the full file name (including the file type
extension).
4 (SQL): Check the ODBC connections.
Ensure Essbase Server is properly configured.
1003028
File fileName is password
protected and could not be read
Essbase did not have
the necessary
operating system
privileges to open the
file you are trying to
load.
Ensure that you have read privileges for the file. See the
operating system documentation.
27
Message
Number
Message
Possible Cause
Possible Solution
1003029
Encountered formatting error in
spreadsheet file fileName
Essbase encountered a
formatting error in the
file.
Open the file outside of Essbase and Ensure that the file is
valid.
1003030
Related
Topics
Unable to load file fileName; see
server logfile for details
1003027
Essbase cannot read
the file.
l
Is the data load running correctly?
l
Is the file corrupt?
l
Is the file empty?
l
Is the file a type that you can load into Essbase?
Ensure Essbase can find the file.
l
Are the file name and path name correct? Check for
misspellings.
l
If Essbase Server is on a UNIX platform, is capitalization
correct?
l
Is file is in the specified location? Ensure that no one has
moved or deleted the file.
1003022
Ensure Essbase can use the file.
l
l
Is the data file locked by another user (see “Unlocking
Objects” on page 126) ?
Does the file have the correct file extension? All text files
must have a file extension of .txt. All rules files must
have a file extension of .rul.
l
Is the file valid?
l
Do you have the correct permissions for the Essbase
database into which you are loading the file?
l
Do you have the correct operating system privileges for
the file you are trying to load?
If you are using ESSCMD, ensure that you are using the
IMPORT command correctly. When you issue the IMPORT
command, you have four options to choose the file location.
l
1 (local/client object): Ensure that the data file is in the
client folder.
Ensure that you have read access to the data file.
If Essbase Server is on a UNIX platform, remember that
the file name is case-sensitive and check capitalization.
l
2 (remote server object): Ensure that you have read
access to the data file.
If Essbase Server is on a UNIX platform, remember that
the file name is case-sensitive and check capitalization.
l
l
3 (file): Ensure that you specified the absolute path
name and the full file name (including the file type
extension).
4 (SQL): Check the ODBC connections.
Ensure that Essbase Server is properly configured.
28
1003000 to 1003048: Data Load Messages
Message
Number
Message
Possible Cause
Possible Solution
1003031
Commit at record
recordNumber during arithmetic
data load
Essbase saved the
record to the Essbase
database.
Not applicable
1003032
Input line too long near record
recordNumber
Essbase encountered a
record that was too
long to process.
Essbase cannot
process records that
contain more than 32,
000 characters.
Ensure that all records are separated by a carriage return.
Invalid member memberName in
data column
Essbase encountered a
non-numeric value in
the in data column.
Data columns must
contain numeric values
only.
Make that sure that the data source is valid.
1003034
Related
Topics
1003000
Ensure that no single record contains more than 32,000
characters.
l
Is the data source corrupt?
l
Is the data source correctly formatted?
Ensure that the record that caused the data load to fail is
valid.
l
Is a member from each dimension specified in the data
source or the rules file?
l
Is each member name in the record valid?
l
Are there multiple numeric data fields in the record? If
so, you can ignore extra data fields.
l
Is the numeric data field at the end of the record? If not,
move the numeric data field in the data source or move
the numeric data field in the rules file.
l
Are all member names that might contain numbers (such
as "100") enclosed in quotation marks?
l
Try removing the record that caused the data load to fail
and running the data load again.
If you are using a rules file, ensure that the rules file is valid.
l
Is the rules file in the correct location?
l
Is the header record in the rules file set up correctly?
l
Can you validate the rules file?
l
Are all dimensions specified in the dimensions specified
in the data source or rules file?
1003035
No data values modified by load
of this data file
Essbase did not
change the values in
the Essbase database
as a result of the data
load.
Not applicable
1003036
Cannot load data. Member name
too long: memberName
Essbase encountered a
member name that was
too long.
Ensure that the member name is valid.
l
Is the member name less than 80 bytes?
l
Did you set the file delimiter?
l
Does a prefix or suffix make the member name too long?
29
Message
Number
Message
Possible Cause
Possible Solution
1003037
Data Load Updated
numberOfCells cells
Essbase updated the
indicated number of
cells in the database.
Not applicable
1003038
Dataload queue overflow on
node nodeNumber
1003039
Cannot load data. Implied
shared member memberName
does not have a real child
Contact Oracle Support.
Essbase cannot load
data into the selected
member because the
member is shared.
Shared members
cannot contain data.
Ensure that the member is not shared. Members are shared
under these conditions:
l
l
l
If you tag the member as shared in the outline.
If the member is a parent with only one child. If a member
only has one child, the parent and the child share a value.
This is called an implied share.
If the member has multiple children, but only one child
that consolidates to the parent. This is also called an
implied share.
1003040
Parallel dataload enabled:
number block prepare threads,
number write threads.
Parallel data load is
enabled.
Not applicable
1003041
Data Unlock Elapsed Time :
number seconds
The time required to
unlock all locks after
the Unlock command is
issued in the
Spreadsheet Add-in.
Not applicable
1003048
Loading Unicode-encoded data
to non-Unicode mode
application is not supported
You have attempted to
load Unicode encoded
data to a non-Unicode
application.
Verify that you have migrated your application to Unicode
mode.
30
1003000 to 1003048: Data Load Messages
4
1006002 to 1006057: Data Cache
Messages
Table 4 lists data cache error and informational messages.
Table 4
Data Cache Messages 1006002 to 1006057
Message
Number
Message
Possible Cause
Possible 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” on page 124).
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:
l
l
l
l
l
l
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” on page 124).
31
Message
Number
Message
Possible Cause
Possible Solution
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” on page 124).
1006010
1006015
Invalid block header: Block's numbers
do not match
Not Enough Memory to Allocate the
Data Buffer Cache. operation aborted
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.
Essbase cannot
complete the listed
operation because
there was not enough
memory.
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” on page 124).
Try any of these to fix the problem. After you fix the
problem, determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
l
l
1006016
32
Invalid block header: Illegal block type
1006002 to 1006057: Data Cache Messages
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.
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” on page
125).
l
Check the block size of the database. If necessary,
reduce the block size.
l
Check the data cache setting. If necessary, increase
the data cache size.
l
Restart Essbase Server.
l
Restart the server computer.
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” on page 124).
Message
Number
Message
Possible Cause
Possible Solution
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” on
page 124).
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.
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” on page 124).
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.
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:
1006032
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.
Once you fix the problem, determine whether the database
is corrupt (see “Checking for Database Corruption” on
page 124).
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” on page 124).
33
Message
Number
Message
Possible Cause
Possible Solution
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
1006035
1006036
1006037
1006039
1006040
1006041
To reduce swapping and increase performance, increase
the data file cache size.
Error errorNumber encountered while
waiting for completion of a data file
cache flush for database
databaseName.
Contact Oracle Support.
Data cache output transfer buffer for
database databaseName is
unavailable.
Contact Oracle Support.
Error encountered while waiting for an
in-transit data page of database
databaseName.
Contact Oracle Support.
Error encountered while waiting for an
in-transit data file page of database
databaseName.
Contact Oracle Support.
Unable to flush to disk a data block
within database databaseName.
Contact Oracle Support.
A read from file fileName,
messageText.
After you fix the problem, determine whether the database
is corrupt (see “Checking for Database Corruption” on
page 124).
After you fix the problem, determine whether the database
is corrupt (see “Checking for Database Corruption” on
page 124).
After you fix the problem, determine whether the database
is corrupt (see “Checking for Database Corruption” on
page 124).
After you fix the problem, determine whether the database
is corrupt (see “Checking for Database Corruption” on
page 124).
After you fix the problem, determine whether the database
is corrupt (see “Checking for Database Corruption” on
page 124).
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” on
page 124).
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” on
page 124).
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” on
page 124).
34
1006002 to 1006057: Data Cache Messages
Message
Number
Message
Possible Cause
Possible Solution
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” on
page 124).
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” on page 124).
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” on
page 124).
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” on
page 124).
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” on
page 124).
1006049
1006050
Unable to generate the data file name
for file fileName for database
databaseName.
Essbase encountered
a fatal error.
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” on
page 124).
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” on
page 124).
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.
35
Message
Number
Message
Possible Cause
Possible Solution
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.
36
1006002 to 1006057: Data Cache Messages
5
1008001 to 1008152: System
Call Messages
Table 5 lists error and informational messages about system calls.
Table 5
System Call Messages 1008001 to 1008152
Message
Number
Message
Possible Cause
Possible Solution
1008001
Unable to Allocate Memory
Essbase cannot allocate
enough memory to perform
the operation.
Ensure that the virtual memory is two to three times as
large as the physical memory.
Ensure that the swap space is two to three times as large
as the RAM.
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.
Check the index cache setting. If necessary, increase the
index cache size.
If you are on a UNIX computer, check the user limit profile
(see “Checking the User Limit Profile” on page 125).
Determine whether the security file is corrupt.
If the server computer is running the HP-UX operating
system, increase MAXDSIZE to at least 2 * (data cache
size + index cache size).
Determine whether any databases are corrupt (see
“Checking for Database Corruption” on page 124).
Restart the server computer.
Ensure that you have enough RAM.
1008006
Unable to Free Memory for
memoryToBeFreed in
funtionName
Contact Oracle Support.
1008009
Pointer is NULL - Free Canceled:
variableName in functionName
Essbase cannot free the
listed memory.
Contact Oracle Support.
1008010
Read Failed
Essbase cannot read a
calculation script located
on the client.
1. Run the calculation script again.
2. Restart the client and rerun the calculation script.
3. Copy the calculation script to the server and rerun the
calculation script.
37
Message
Number
Message
Possible Cause
Possible Solution
1008021
Named Pipe Create Failed
Essbase cannot create the
named pipe.
Consult the networking documentation.
1008022
Pipe Create Failed
Essbase cannot create the
named pipe.
Consult the networking documentation.
1008023
Named Pipe Connect Failed
Essbase cannot
disconnect from the
named pipe.
Consult the networking documentation.
1008024
Named Pipe Disconnect Failed
Essbase cannot
disconnect from the
named pipe.
Consult the networking documentation.
1008025
Named Pipe Peek Failed
Essbase cannot peek to
the named pipe.
Consult the networking documentation.
1008028
Pipe Read Error
Essbase cannot read from
the named pipe.
Determine whether Essbase Server is running.
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
l
If Essbase Server has frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126).
1008029
Pipe Write Error
Essbase cannot write to
the named pipe.
Consult the networking documentation.
1008030
Pipe Open Failed
Essbase cannot open the
named pipe.
Consult the networking documentation.
1008031
Pipe Close Failed
Essbase cannot close the
named pipe.
Consult the networking documentation.
1008036
Incorrect # of Bytes Written To
Pipe
Essbase cannot finish
writing to the named pipe.
Consult the networking documentation.
1008037
Find Next Failed
Essbase cannot find the
next file in the sequence.
This might occur if Essbase is processing multiple files,
such as during a copy or a load. If you can determine
which file is missing, restore it from backups.
1008039
Find Close Failed
Essbase cannot close the
next file in the sequence.
This might occur if Essbase is processing multiple files,
such as during a copy or a load. If you can determine
which file is having problems, restore it from backups.
38
1008001 to 1008152: System Call Messages
Message
Number
Message
Possible Cause
Possible Solution
1008089
Error receiving data from Agent
Essbase cannot receive
data from the Agent.
Determine whether Essbase Server is running.
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
l
1008090
Timed out receiving data from
Agent
Essbase cannot receive
data from the Agent.
If Essbase Server has frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126), and restart Essbase Server.
Determine whether Essbase Server is running.
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
l
If Essbase Server has frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126), and restart Essbase Server.
1008091
Error sending data to Agent
Essbase cannot send data
to the Agent.
Contact Oracle Support.
1008092
Timed out sending data to Agent
Essbase cannot send data
to the Agent.
Contact Oracle Support.
1008093
Invalid data type for conversion
Contact Oracle Support.
1008099
HALLOC: Possible duplicate
memory allocation!
variableName in functionName
Contact Oracle Support.
1008100
HFREE: Pointer already freed!
variableName in functionName
Contact Oracle Support.
1008101
HFREE: Likely memory overwrite!
variableName in functionName
The original memory
allocation was overwritten
by a newer allocation to the
same pointer.
Contact Oracle Support.
39
Message
Number
Message
Possible Cause
Possible Solution
1008106
Exception error log
errorLogName.XCP is being
created
Essbase is generating an
exception log just before it
shuts down abnormally.
Search the exception log for information about what
caused the shut down.
l
l
l
l
l
If the server crashes, the log is written to
HYPERION_HOME/logs/essbase; for example,
log00001.xcp.
If the application crashes and the application name
is unknown, the log is written to HYPERION_HOME/
logs/essbase/app; for example, log00001.
xcp.
If the application crashes and the application name
is known, the log is written to HYPERION_HOME/
logs/essbase/app/appName; for example,
sample/log00001.xcp.
If the database crashes and the database name is
unknown, the log is written to HYPERION_HOME/
logs/essbase/app/appName/; for example,
app/sample/log00001.xcp.
If the database crashes and the database name is
known, the log is written to HYPERION_HOME/
logs/essbase/app/appName/
databasename; for example, app/sample/
basic/log00001.xcp.
Determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
Contact Oracle Support.
40
1008001 to 1008152: System Call Messages
Message
Number
Message
Possible Cause
Possible Solution
1008107
Exception error log completed -please contact technical support
and provide them with this file
Essbase finished
generating the error log
and shuts down.
Search the exception log for information about what
caused the shut down.
l
l
l
l
l
If the server crashes, the log is written to
HYPERION_HOME/logs/essbase; for example,
log00001.xcp.
If the application crashes and the application name
is unknown, the log is written to HYPERION_HOME/
logs/essbase/app/; for example, app/
log00001.xcp.
If the application crashes and the application name
is known, the log is written to HYPERION_HOME/
logs/essbase/app/appName/; for example,
app/sample/log00001.xcp.
If the database crashes and the database name is
unknown, the log is written to HYPERION_HOME/
logs/essbase/app/appName/; for example,
app/sample/log00001.xcp.
If the database crashes and the database name is
known, the log is written to HYPERION_HOME/
logs/essbase/app/appName/
databasename; for example, app/sample/
basic/log00001.xcp.
Determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
Contact Oracle Support.
41
Message
Number
Message
Possible Cause
Possible Solution
1008108
Essbase Internal Logic Error
logicErrorNumber
Essbase encountered a
logic error and shut down
abnormally.
Ensure that Essbase Server is running.
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
l
If Essbase Server has frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126).
Determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
Ensure that the networking and computer hardware are
running correctly.
Ensure that the virtual memory is two to three times as
large as the physical memory. If that is still not large
enough, increase the memory of the server computer.
Check the block size.
Ensure that the data cache can hold at least 100 blocks.
Ensure that the index cache size is within the
recommended range.
1008109
Unable to Reallocate Memory for
pointerName in functionName
Essbase cannot reallocate
memory to the listed
function.
Ensure that you have enough memory.
1008110
Unable to Allocate Memory. Refer
to the Application Log for details.
Essbase cannot allocate
memory.
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Ensure that you have enough memory.
Do not close the Essbase Server window by clicking the
"X" in the title bar.
After you restart Essbase Server, determine whether the
database is corrupt (see “Checking for Database
Corruption” on page 124).
See appName.log.
42
1008001 to 1008152: System Call Messages
Message
Number
Message
Possible Cause
Possible Solution
1008111
Unable to Reallocate Memory for
pointerName in functionName.
Refer to the Application Log for
details.
Essbase cannot reallocate
memory.
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Ensure that you have enough memory.
Do not close the Essbase Server window by clicking the
"X" in the title bar.
After you restart Essbase Server, determine whether the
database is corrupt (see “Checking for Database
Corruption” on page 124).
See appName.log.
Memory Allocation error codes:
O/S error = errorCode, O/S return
code = errorNumber
Essbase could not allocate
memory.
Ensure that you have enough memory.
Memory Reallocation error codes:
O/S error = errorCode, O/S return
code = errorNumber
Essbase could not
reallocate memory.
Ensure that you have enough memory.
1008114
Allocation request for number
bytes of virtual memory.
Percentage of memory in use is
number %.
Bytes of virtual memory
requested and the
percentage of virtual
memory currently being
used by Essbase.
Not applicable
1008115
Total physical memory is number
bytes. Available physical memory
is number bytes.
Total bytes of physical
memory and bytes of
available physical
memory.
Not applicable
1008116
Total swap space is number bytes.
Available swap space is number
bytes.
Total bytes of swap space
and bytes of available
swap space.
Not applicable
1008117
Total virtual memory is number
bytes. Available virtual memory is
number bytes.
Total bytes of virtual
memory and bytes of
available virtual memory.
Not applicable
1008118
Memory page size is number
bytes. Allocation granularity is
number bytes.
Total bytes of memory
page size and the size that
memory is allocated in.
Not applicable
1008119
Memory page size is number
bytes
Total bytes of memory
page size.
Not applicable
1008112
1008113
Look up the operating system error code and the
operating system return code in the operating system
documentation.
Look up the operating system error code and the
operating system return code in the operating system
documentation.
43
Message
Number
Message
Possible Cause
Possible Solution
1008120
Unable to Allocate Physical
Memory for pointerName in
functionName
Essbase cannot allocate
physical memory to the
listed function.
Ensure that you have enough physical memory.
1008121
Unable to Allocate Physical
Memory for pointerName in
functionName for reallocation
Essbase cannot reallocate
physical memory to the
listed function.
Ensure that you have enough physical memory.
1008122
Unable to Lock the Allocated
Memory for pointerName in
functionName
Essbase cannot lock the
needed memory.
Ensure that the Agent is assigned the correct operating
system privileges (see “Determining Operating System
Privileges” on page 126).
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Ensure that the memory to be locked is valid. Consult the
operating system documentation.
1008123
Unable to Lock the Allocated
Memory for pointerName in
functionName for reallocation
Essbase cannot lock the
needed memory.
Ensure that the Agent is assigned the correct operating
system privileges (see “Determining Operating System
Privileges” on page 126).
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Ensure that the memory to be locked is valid. See the
operating system documentation.
1008124
Unable to Lock the Allocated
Memory pointerName in
functionName, because of
insufficient quota
Essbase does not have
enough physical memory
to lock the memory.
Check the Essbase Server memory requirements. If
necessary, increase the physical memory.
1008125
Unable to Lock the Allocated
Memory pointerName in
functionName, because of
insufficient privilege
Essbase is not assigned
the correct operating
system privileges to lock
the memory.
Ensure that the Agent is assigned the correct operating
system privileges (see “Determining Operating System
Privileges” on page 126).
1008126
Unable to Lock the Allocated
Memory pointerName in
functionName for reallocation,
because of insufficient quota
Essbase does not have
enough physical memory
to lock the memory.
Check the Essbase Server memory requirements. If
necessary, increase the physical memory.
1008127
Unable to Lock the Allocated
Memory pointerName in
functionName for reallocation,
because of insufficient privilege
Essbase is not assigned
the correct operating
system privileges to lock
the memory.
Ensure that the Agent is assigned the correct operating
system privileges (see “Determining Operating System
Privileges” on page 126).
44
1008001 to 1008152: System Call Messages
Message
Number
Message
Possible Cause
Possible Solution
1008128
Unable to Allocate Physical
Memory for pointerName in
functionName. Refer to the
Application Log for details.
Essbase does not have
enough physical memory
to lock the memory.
If necessary, decrease the cache sizes.
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Restart the server computer.
Check the Essbase Server physical memory requirements.
If necessary, increase the physical memory.
See appName.log.
1008129
Unable to Allocate Physical
Memory for pointerName in
functionName for reallocation.
Refer to the Application Log for
details.
Essbase does not have
enough physical memory
to lock the memory.
If necessary, decrease the cache sizes.
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Restart the server computer.
Check the Essbase Server physical memory requirements.
If necessary, increase the physical memory.
See appName.log.
1008130
Unable to Lock the Allocated
Memory for pointerName. Refer to
the Application Log for details.
Essbase cannot lock the
needed memory.
Ensure that the Agent is assigned the correct operating
system privileges (see “Determining Operating System
Privileges” on page 126).
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Ensure that the memory to be locked is valid.
See appName.log.
45
Message
Number
Message
Possible Cause
Possible Solution
1008131
Unable to Lock the Allocated
Memory for pointerName in
functionName for reallocation.
Refer to the Application Log for
details.
Essbase cannot lock the
needed memory.
Ensure that the Agent is assigned the correct operating
system privileges (see “Determining Operating System
Privileges” on page 126).
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Ensure that the memory to be locked is valid.
See appName.log.
1008132
1008133
Unable to Lock the Allocated
Memory pointerName in
functionName, because of
insufficient quota. Refer to the
Application Log for details.
Essbase does not have
enough physical memory
to lock the memory.
Check the Essbase Server memory requirements. If
necessary, increase the physical memory.
Unable to Lock the Allocated
Memory pointerName in
functionName, because of
insufficient privilege. Refer to the
Application Log for details.
Essbase is not assigned
the correct operating
system privileges to lock
the needed memory.
Ensure that the Agent is assigned the correct operating
system privileges (see “Determining Operating System
Privileges” on page 126).
See appName.log.
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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 appName.log.
1008134
Unable to Lock the Allocated
Memory pointerName in
funtionName for reallocation,
because of insufficient quota.
Refer to the Application Log for
details.
Essbase does not have
enough physical memory
to lock the memory.
If necessary, decrease the cache sizes.
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
Restart the server computer.
Check the Essbase Server physical memory requirements.
If necessary, increase the physical memory.
See appName.log.
46
1008001 to 1008152: System Call Messages
Message
Number
Message
Possible Cause
Possible Solution
1008135
Unable to Lock the Allocated
Memory pointerName in
functionName for reallocation,
because of insufficient privilege.
Refer to the Application Log for
details.
Essbase is not assigned
the correct operating
system privileges to lock
the needed memory.
Ensure that the Agent is assigned the correct operating
system privileges (see “Determining Operating System
Privileges” on page 126).
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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 appName.log.
1008136
Unable to Free Locked Memory for
pointerName in functionName
Essbase cannot free the
memory, probably
because an invalid pointer
was passed to the function
that frees the memory.
Contact Oracle Support.
1008137
Unable to Free Memory for
pointerName in functionName in
reallocation
Essbase cannot free the
memory, probably
because an invalid pointer
was passed to the function
that frees the memory.
Contact Oracle Support.
1008138
Unable to Free Memory for
pointerName in functionName in
reallocation. Refer to the
Application Log for details.
Essbase cannot free the
memory, probably
because an invalid pointer
was passed to the function
that frees the memory.
See appName.log.
1008139
Unable to Allocate Aligned
Memory for pointerName in
functionName
Essbase does not have
enough virtual memory to
allocate the memory to the
listed pointer.
Check the Essbase Server virtual memory requirements.
If necessary, increase the virtual memory and restart
Essbase Server.
1008140
Unable to Free Aligned Memory
for pointerName in functionName
Essbase cannot free the
memory, probably
because an invalid pointer
was passed to the function
that frees the memory.
Contact Oracle Support.
1008141
Unable to Allocate Aligned
Memory for pointerName in
functionName for reallocation
Essbase does not have
enough virtual memory to
allocate the memory to the
listed pointer.
Check the Essbase Server virtual memory requirements.
If necessary, increase the virtual memory and restart
Essbase Server.
1008142
Unable to Free Aligned Memory
for pointerName in
functionName in reallocation
Essbase cannot free the
memory, probably
because an invalid pointer
was passed to the function
that frees the memory.
Contact Oracle Support.
Contact Oracle Support.
47
Message
Number
Message
Possible Cause
Possible Solution
1008143
Unable to Allocate Aligned
Memory for pointerName in
functionName. Refer to the
Application Log for details.
Essbase does not have
enough virtual memory to
allocate the memory to the
listed pointer.
Check the Essbase Server virtual memory requirements.
If necessary, increase the virtual memory and restart
Essbase Server.
Check the Essbase Server virtual
memory requirements. If
necessary, increase the virtual
memory and restart Essbase
Server.
Essbase does not have
enough virtual memory to
allocate the memory to the
listed pointer.
Check the Essbase Server virtual memory requirements.
If necessary, increase the virtual memory and restart
Essbase Server.
Unable to Free Aligned Memory
for pointerName in
functionName in reallocation.
Refer to the Application Log for
details.
Essbase cannot free the
memory, probably
because an invalid pointer
was passed to the function
that frees the memory.
See appName.log.
1008146
Unable to Unlock the Allocated
Memory pointerName in
functionName
Essbase cannot free the
memory, probably
because an invalid pointer
was passed to the function
that frees the memory.
Contact Oracle Support.
1008147
Unable to Allocate Memory for
pointerName in functionName
Essbase does not have
enough virtual memory to
allocate the memory to the
listed pointer.
Check the Essbase Server virtual memory requirements.
If necessary, increase the virtual memory and restart
Essbase Server.
1008148
Unable to Allocate Memory for
pointerName in functionName.
Refer to the Application Log for
details.
Essbase does not have
enough virtual memory to
allocate the memory to the
listed pointer.
Check the Essbase Server virtual memory requirements.
If necessary, increase the virtual memory and restart
Essbase Server.
Abnormal shutdown request
entered Are you sure you want to
forcibly shutdown the application
[1-yes,2-no]?
You are trying to shut down
Essbase Server incorrectly.
If possible, stop Essbase Server correctly.
1008144
1008145
1008149
See appName.log.
See appName.log.
Contact Oracle Support.
See appName.log.
1. Enter 2 and try to stop Essbase Server correctly.
2. If you cannot stop Essbase Server correctly, enter 1
to stop Essbase Server.
3. If this does not work, end the task (see “Ending the
Server Task” on page 126).
4. After you stop Essbase Server, follow the procedures
for an abnormal shutdown.
1008150
The abnormal shutdown request
is aborted, the application will
continue processing
The administrator aborted
an abnormal shutdown
request, probably by
answering no to message
1008149.
1008151
System is busy. The application
will re-attempt the abnormal
shutdown request.
Essbase Server is
performing an important
task, such as writing to the
index.
48
1008001 to 1008152: System Call Messages
When the task is complete, Essbase Server tries to shut
down again.
Message
Number
Message
Possible Cause
Possible Solution
1008152
System is still busy. The abnormal
shutdown request is aborted, try
again later.
Essbase Server is
performing an important
task, such as writing to the
index. Essbase Server
aborted the abnormal
shutdown request to finish
this task.
If possible, wait a few minutes and stop Essbase Server
correctly. If you cannot stop Essbase Server correctly, end
the task (see “Ending the Server Task” on page 126).
After you stop Essbase Server, follow the procedures for
an abnormal shutdown.
49
50
1008001 to 1008152: System Call Messages
6
1012000 to 1012750:
Calculation Messages
Table 6 lists error and informational messages that are specific to calculations.
Table 6
Calculation Messages 1012000 to 1012750
Message
Number
Message
Possible Cause
Possible Solution
1012000
Invalid Syntax - Not a CALC command
invalidCommandName
Essbase encountered a
command in a calculation
script that is not a valid
calculation command.
Ensure that the calculation command is correct.
1012001
Invalid Calc Script syntax
calculationCommandWithErrors
Essbase encountered a
syntax error in a
calculation script.
l
Is the calculation command spelled correctly?
l
Are all variables in the calculation command
spelled correctly?
l
Is the calculation command valid?
Ensure that the calculation script is valid.
See also "Understanding Calculation Script Syntax"
in the Oracle Essbase Database Administrator's
Guide.
l
Is everything enclosed in quotation marks that
needs to be?
l
Can you verify the syntax of the calculation script
in the Calc Script Editor?
l
Are all member names correct, including spaces?
Member names with spaces must be enclosed in
quotation marks.
l
Is the syntax correct for all formulas?
l
Is the syntax correct for commands that define
calculation behavior, such as SET?
51
Message
Number
Message
Possible Cause
Possible Solution
1012004
Invalid member name memberName
Essbase encountered an
invalid member name in
the calculation script.
Ensure that the member name is valid.
Related
Topics
l
1012005
l
l
l
1012005
Related
Topics
Invalid dimension name
dimensionName
Essbase encountered an
invalid dimension name in
the calculation script.
1012004
Does the member still exist in the outline? This
error message usually occurs when a member is
deleted from the outline but not from the
calculation script. If a member does not exist in
the outline, delete all references to that member
from the calculation script.
Is the member name spelled correctly, including
spaces?
If the member name contains special characters,
such as spaces, periods, or numbers only, ensure
that the member name is enclosed in quotation
marks.
Instead of typing in the member name, try
associating the correct outline with the
calculation script and using the Calc Script Editor
to fill in the member name.
Ensure that the dimension name is valid.
Does the dimension still exist in the outline? This
message usually occurs when a dimension is deleted
from the outline but not from the calculation script.
If a dimension does not exist in the outline, delete all
references to that dimension and its members from
the calculation script.
Is the dimension name spelled correctly, including
spaces?
If the dimension name contains special characters,
such as spaces, ensure that the dimension name is
enclosed in quotation marks.
Instead of typing in the dimension name, try
associating the correct outline with the calculation
script and using the Calc Script Editor to fill in the
dimension name.
1012009
Variable name variableName too long
Essbase encountered a
variable name that is too
long. Variable names
must be no more than 32
bytes.
Find the variable name and make it 32 bytes or fewer.
Ensure that the dimension name is valid.
Ensure that you are declaring the variable correctly
before you use it.
1012010
Redeclared Variable name
variableName
The variable was declared
multiple times in one
calculation script.
Check the calculation script and remove the extra
variable declarations. Ensure that you are declaring
the variable correctly before you use it.
1012011
Variable name variableName conflicts
with member name
The name assigned to the
listed variable matches a
member name in the
outline.
Assign the variable a unique name. Remember that
the variable name must be 32 bytes or fewer and
must follow Essbase naming rules. Ensure that you
are declaring the variable correctly before you use it.
52
1012000 to 1012750: Calculation Messages
Message
Number
Message
Possible Cause
Possible Solution
1012012
The array variable range specifier
dimensionName is not a dimension
The dimension in the
calculation script that
determines the size of the
array variable was not a
valid dimension.
Ensure that the dimension name is valid.
l
l
l
Does the dimension exist in the outline?
Is the dimension spelled correctly, including
spaces? Instead of typing in the member, try
associating the correct outline with the
calculation script and using the Calc Script Editor
to fill in the member name.
If the dimension name contains special
characters, such as spaces, ensure that the
dimension name is enclosed in quotation marks.
Ensure that the dimension name is enclosed in
brackets [dimensionName] in the calculation script.
Ensure that the ARRAY command in the calculation
script is valid.
1012013
Calc Script Error - Unexpected End of
File reached
The calculation script
contained a comment
open symbol /*, but did
not contain a matching
comment close symbol
*/.
Add the comment close symbol */ at the end of the
comment.
1012015
CALC ALL cannot be used in restricted
calculation
Essbase encountered a
CALC ALL command
inside a FIX-ENDFIX
command block.
Ensure that the CALC ALL command is not used inside
FIX-ENDFIX command blocks. The CALC ALL
command calculates the entire database but the FIX
command calculates only a part of the database.
1012016
Cannot calculate dimension member
memberName with restricted member
memberName
The calculation script
contained a calculation
that tried to calculate a
member after restricting
the calculation to another
member in the same
dimension.
Ensure that the member is correctly positioned in the
FIX statement. If you fix on a member, you can
calculate only that member. For example, this FIX
statement is incorrect because the FIX is on the Sales
member, but the statement tries to calculate Profit,
which is another member:
Related
Topics
1012017
FIX(Sales) Profit; ENDFIX
This FIX statement is correct:
FIX (Sales) Sales; ENDFIX
1012017
Related
Topics
Cannot calculate dimension
dimensionName with restricted
member memberName
1012016
The calculation script
contained a calculation
that tried to calculate a
dimension after restricting
the calculation to a
member of that
dimension.
Ensure that the dimension is correctly positioned in
the FIX statement. If you fix on a member, you can
calculate only that member in the same dimension.
For example, this FIX statement is incorrect because
the FIX is on the Sales member, which is part of the
Measures dimension, but the statement tries to
calculate the entire Measures dimension:
FIX(Sales) CALC DIM Measures; ENDFIX
1012018
Redeclared dimension
dimensionName in AGG command
The dimension name was
declared multiple times in
one AGG command.
Check the calculation script and remove the extra
dimension name declarations.
53
Message
Number
Message
Possible Cause
Possible Solution
1012019
Calc Script block delimiter
delimiterName not balanced
delimiterName
The calculation script is
missing opening or closing
parentheses.
Check the calculation script to add the missing
parenthesis or delete the extra parenthesis.
1012021
Calc Script command
calculationScriptCommand is
incomplete
The listed calculation
script command was not
complete.
Ensure that the calculation script command contains
all pertinent data.
l
Are there open flow control commands, such as
a FIX command without an ENDFIX command, or
a LOOP command without an ENDLOOP
command?
l
Are semicolons missing?
l
Are all left parentheses closed by right
parentheses?
1012023
Aggregating on Dense Dimension
dimensionName is currently not
supported
Essbase cannot use the
AGG command with dense
dimensions.
Check the calculation script to Ensure that you are
not using the AGG command on a dimension tagged
as dense.
1012024
Cannot aggregate dimension
dimensionName with restricted
member memberName
The calculation script
contains a calculation that
tries to aggregate a
dimension after restricting
the calculation to a
member of that
dimension.
Ensure that the dimension is correctly positioned in
the FIX statement. If you fix on a member, you can
aggregate only that member. For example, This FIX
statement is incorrect because the FIX is on the Sales
member, but the statement tries to aggregate
Measures, which is a dimension:
FIX(Sales) AGG(Measures); ENDFIX
This FIX statement is correct:
FIX (Sales) AGG (Sales); ENDFIX
1012025
No Currency Database has been set on
this database
Essbase tried to perform a
calculation that required a
currency database but no
currency database
existed.
Ensure that the main database is linked to the
currency database.
Ensure that the main database can connect to the
currency database. First, try these two steps:
Stop and restart the application.
Ensure that the main database is linked to the
currency database.
If these steps do not work, perform these steps on
the application and main database:
1. Stop the application and main database.
2. Rename the main database ARBORPATH/app/
appName/databaseName/
databaseName.db file to something else.
3. Create a new application and database.
4. Move the databaseName.db file you created in
step 3 to the application and database you
stopped in step 1.
5. Restart the application you stopped in step 1.
54
1012000 to 1012750: Calculation Messages
Message
Number
Message
Possible Cause
Possible Solution
1012026
commandName command can only be
fixed on a CURPARTITION member
Essbase tried to FIX on a
member that does not
belong to the
CURPARTITION
dimension.
When using the CCONV command, ensure that all
members that appear inside the FIX command belong
to the CURPARTITION dimension.
1012027
No dimension is tagged
CURPARTITION, commandName
command cannot be fixed on any
member
Essbase tried to FIX on a
member of the
CURPARTITION dimension
but the CURPARTITION
dimension is not defined
for the database.
Essbase tried to FIX on a member of the
CURPARTITION dimension but the CURPARTITION
dimension is not defined for the database.
1012028
commandName command must be
fixed on a CURPARTITION member
Essbase cannot use the
CCONV command without
a currency partition
defined.
When using the CCONV command, ensure that all
members that appear inside the FIX command belong
to the CURPARTITION dimension.
1012029
Invalid target range range of DCOPY
command
In the DATACOPY
command, the number of
members in the source
range do not match those
in the target range.
Ensure that the number of members in the source
range (the set of members you are copying from)
matches the number of members in the target range
(the set of members you are copying to). Ensure that
the DATACOPY command is correct.
1012030
DATACOPY command command
cannot copy data to itself
The DATACOPY command
copies a range of
members from a source
range to a target range.
The DATACOPY command
cannot copy a range of
members from a source
range back onto the
source range.
Ensure that the DATACOPY command is set to copy
the correct range. Compare the source and target
ranges to Ensure that the DATACOPY command is not
copying the data back onto the source range.
1012031
DATACOPY command command is
conflict with Range Fix
Essbase tried to copy a
range of members that
was outside of the range
you fixed on.
Make the DATACOPY range and FIX range compatible
by making the ranges match, or by making the
DATACOPY range a subset of the FIX range.
1012032
When CURPARTITION is tagged,
DATACOPY command command can
only be used to copy a whole Currency
Partition
Essbase tried to use the
FIX command while using
DATACOPY to copy a
currency partition and this
is not permitted.
Ensure that you are not using a FIX command in the
DATACOPY command if you are copying a currency
partition. Use the DATACOPY command to copy the
entire currency partition.
1012033
Currency Conversion is not available
with this server, calc command
commandName is not supported
This command is available
only when using Currency
Conversion applications.
1012034
Variable variableName not declared
The variable used in the
calculation script is not
declared.
Ensure that you are declaring the variable correctly
before you use it.
1012035
Variable variableName must be of VAR
type
The variable listed must be
of VAR type instead of
ARRAY type.
Ensure that you are declaring the variable correctly.
55
Message
Number
Message
Possible Cause
Possible Solution
1012036
Calc Script block command
blockCommandName does not end
with blockEndCommandName
Essbase encountered a
block command that was
not closed.
Ensure that each FIX command is closed by an
ENDFIX command. Ensure that each LOOP command
is closed by an ENDLOOP command.
1012037
Custom calculation is not allowed for
kindOfShare share member
sharedMemberName
Essbase tried to calculate
a formula on a shared
member.
Because shared members do not store data, you
cannot attach formulas to them. Ensure that the
listed member is not shared, either because the
member's storage property is explicitly tagged as
shared or because the member is implicitly shared.
1012038
The constant constantName assigned
to variable variableName is not a
number
Essbase tried to assign a
value that was not a
number to the listed
variable. The listed
variable can accept only
numeric values.
Ensure that you are declaring the variable correctly.
1012039
The constant constantName assigned
to array variable arrayVariableName is
not a number
Essbase tried to assign a
value that was not a
number to the listed array
variable. The listed array
variable can accept only
numeric values.
Ensure that you are assigning the array variable
correctly.
1012040
Too many initial constants assigned to
array variable arrayVariableName
EssbaseThe number of
values that Essbase tried
to assign to the array
exceeds the number of
members in the
associated dimension.
Ensure that you are using the ARRAY command
correctly.
Ensure that you are assigning the values to the correct
dimension.
1012041
memberName is not a valid currency
type member
Essbase tried to specify
the currency type using a
member that does not
belong to the CurType
dimension.
Ensure you are using the CCONV function correctly
and that the currency database is set up correctly.
Ensure that the listed member is defined as the
currency type member.
1012042
Substitution variable
substitionVariableName doesn't exist
The calculation script
cannot find the listed
substitution variable.
Ensure that you created the substitution variable
correctly. Ensure that the substitution variable was
created at the correct level.
l
l
l
56
1012000 to 1012750: Calculation Messages
Substitution variables created at the database
level are available to all calculation scripts within
that database.
Substitution variables created at the application
level are available to all calculation scripts within
that application.
Substitution variables created at the server level
are available to all calculation scripts on the
Essbase Server.
Message
Number
Message
Possible Cause
Possible Solution
1012043
Calculation is not allowed for virtual
member memberName in the Calc
script
The calculation script tried
to set a Dynamic Calc
member value or request
calculation of a Dynamic
Calc member.
Dynamic Calc members are calculated at query time
if a query requests the value of the member. They
cannot be calculated through calculation scripts.
Ensure that the Dynamic Calc member is not on the
left side of the equation; for example, if Qtr1 is
Dynamic Calc, this equation is incorrect:
Qtr1 = Jan + Feb + Mar;
If Qtr1 is Dynamic Calc, this equation is also
incorrect:
vbb Qtr1;
This equation is correct, if Year is not Dynamic Calc,
but Qtr1 and Qtr2 are Dynamic Calc:
Year = Qtr1 + Qtr2;
1012044
Invalid fix member count number when
converting from Bitmap
Contact Oracle Support.
1012045
Unable to convert bitmap to fix member
in function functionName
Contact Oracle Support.
1012046
Unable to convert MEMNOR to MEMNO
in function functionName
Contact Oracle Support.
1012047
Aggregating on Attribute Dimension
attributeDimensionName is currently
not supported
Essbase tried to calculate
the listed attribute
dimension using the AGG
command.
Ensure that you are not using the AGG command to
calculate an attribute dimension. Attribute
dimensions do not store data. They are calculated at
query time if a query requests the value of the
member.
1012048
Calc Dim on Attribute Dimension
attributeDimensionName is not
supported
Essbase tried to calculate
the listed attribute
dimension using the CALC
DIM command.
Ensure that you are not using the CALC DIM
command to calculate an attribute dimension.
Attribute dimensions do not store data. They are
calculated at query time if a query requests the value
of the member.
1012049
Cannot clear data from Attribute
dimension member memberName
Essbase tried to clear data
from the listed attribute
dimension.
Attribute dimensions do not store data. They are
calculated at query time if a query requests the value
of the member. You cannot clear data from an
attribute dimension or attribute dimension member.
1012050
Cannot DATACOPY on Attribute
dimension member memberName
Essbase tried to copy data
into the listed attribute
dimension using the
DATACOPY command.
Ensure that you are not using the DATACOPY
command to copy data into an attribute dimension.
Attribute dimensions do not store data. They are
calculated at query time if a query requests the value
of the member.
1012051
Batch calc error, FIX statement cannot
contain Dynamic Calc member from
dimension dimensionName
Essbase tried to FIX on a
Dynamic Calc member.
Ensure that you are not fixing on a member that is
tagged as Dynamic Calc. Dynamic Calc members do
not store data. They are calculated at query time if a
query requests the value of the member. To FIX on
the listed member, change the member from
Dynamic Calc to store.
57
Message
Number
Message
Possible Cause
Possible Solution
1012052
Unable to unfix blocks after calculation
encounters an error
The data blocks that were
changed by a calculation
were left in an inconsistent
state.
Stop and restart the database or contact Oracle
Support. Essbase reverted all values to their previous
state or retained values calculated before the error.
How Essbase handles the cancellation depends on
the Essbase kernel isolation level settings.
1012053
Calculation is cancelled by user
The user pressed Cancel
while performing the
calculation. Essbase
reverted all values to their
previous state or retained
values calculated before
the cancellation.
How Essbase handles the cancellation depends on
the Essbase kernel isolation level settings.
1012054
Batch calc error. All members that need
to be calculated in dimension
dimensionName are Two Pass Calc and
Dynamic
Essbase tried to FIX on a
dimension that contains
no stored members.
Ensure that at least one member in the dimension
that the calculation script fixes on is tagged as stored.
Ensure that at least one stored member is not tagged
as Two Pass.
1012055
The expression inside FIX evaluates to
an empty set. Operation aborted
Essbase tried to fix on a
member or set of
members that do not exist.
Ensure that the members that the calculation script
fixes on are valid. If the calculation script fixes on a
set of members determined by a function, ensure that
the function returns at least one member. This
calculation script is incorrect because January is a
level 0 member; that is, it has no children and the
calculation script tries to fix on the children of
January:
FIX(@CHILDREN (January))
DIM (Product); ENDFIX
CALC
This calculation script is correct, because Qtr1 is not
a level 0 member:
FIX(@CHILDREN (Qtr1))
(Product); ENDFIX
CALC DIM
1012061
The CALC command commandName
can only be used within a CALC
Member Formula
Essbase cannot execute
the listed command.
The IF and ELSE commands must be used within a
member formula. They cannot be used in a
calculation script.
1012062
Substitution variable name variable
name exceeds the maximum length
number of characters
Your substitution variable
name contains more
characters than allowed.
Rename the variable so that it does not exceed the
maximum character length.
1012063
Substitution variable cannot process
UTF-8 encoded data in non-Unicode
configured application
You attempted to process
Unicode encoded data in
a non-Unicode
application.
Verify that you migrated your application to Unicode
mode.
1012106
Calc String function functionName
must be followed by '('
The listed function needs
an opening parenthesis
“(”.
Insert the opening parenthesis after the function
name, with the function parameters separated by
commas, and a closing parenthesis. Check the
function syntax.
58
1012000 to 1012750: Calculation Messages
Message
Number
Message
Possible Cause
Possible Solution
1012121
Error encountered when loading
member memberName's calc string
memberFormula, ignored
Essbase could not
compile the formula
attached to the member
because of one or more
syntax errors.
Check the application log (HYPERION_HOME/
1012134
Generation number number must be an
integer
Essbase encountered a
generation number that
was not an integer.
Ensure that all generations are numbered with
integers.
1012135
Level number number must be an
integer
Essbase encountered a
level number that was not
an integer.
Ensure that all levels are numbered with integers.
1012136
Named generation generationName is
not defined
Essbase encountered a
generation name that is
not defined in the
database.
Ensure that the generation name is properly defined
in the database.
1012137
Named Level levelName is not defined
Essbase encountered a
level name that is not
defined in the database.
Ensure that the level name is properly defined in the
database.
1012139
No memberType member found in
Account dimension
The listed member type
was not found in the
dimension tagged as
accounts.
If you are using the CALC FIRST, CALC LAST, CALC
AVERAGE, or CALC TWOPASS commands, ensure that
the outline contains a dimension tagged as accounts,
and that the dimension tagged as accounts contains
these members:
logs/essbase/app/appName/appName.log)
for a list of syntax errors. Correct the syntax errors.
Check the calculation script command syntax.
l
l
l
l
If you are using the CALC FIRST command, the
accounts dimension must contain a member
tagged with a time balance of First.
If you are using the CALC LAST command, the
accounts dimension must contain a member
tagged with a time balance of Last.
If you are using the CALC AVERAGE command,
the accounts dimension must contain a member
tagged with a time balance of Average.
If you are using the CALC TWOPASS command,
the accounts dimension must contain a member
tagged as Two-Pass.
1012141
Illegal match string stringToMatch
The pattern specified in
the @MATCH function was
not valid.
Check the syntax of the @MATCH function and correct
the problem.
1012142
Input inputValue is not a valid gen/level
name or valid gen/level number
Essbase encountered a
generation or level
number or a generation or
level name that was not
valid.
Ensure that all generations or levels are numbered
with integers or valid names. Follow the same rules
as for naming members.
59
Message
Number
Message
Possible Cause
Possible Solution
1012143
@MATCH search string
stringToSearchFor should always be in
double quote
Essbase could not search
for the listed string
because it was not
enclosed in quotation
marks.
Check the @MATCH command syntax.
1012500
The requested calc script
calcScriptName not found
Essbase could not open
the listed calculation
script.
Ensure that Essbase can find the calculation script.
l
Are the calculation script name and path name
correct? Check for misspellings.
l
If the calculation script is on a UNIX platform, is
capitalization correct?
l
Is the calculation script in the specified location?
Ensure that no one has moved or deleted the
calculation script.
Ensure that Essbase can use the calculation script.
l
l
Is the calculation script being used by another
user or application?
Is the file extension correct for the calculation
script? All calculation scripts must have a file
extension of .csc.
l
Is the calculation script valid?
l
Are the permissions set up correctly for the
Essbase database you are calculating?
1012501
Calculator internal error -- invalid input
type inputTypes
Essbase could not read
the calculation script.
Ensure that the client is correctly passing the
calculation script location to Essbase Server.
1012550
Total Calc Elapsed Time : number
seconds
Length of time it took
Essbase to perform the
calculation.
Not applicable
1012551
Converting database databaseName's
currency to currencyType
Essbase is converting the
currency type for the listed
database.
Not applicable
1012552
Copying data from rangeOfCells
Essbase is copying the
data from the listed range
of cells.
Not applicable
1012553
Copying data from rangeOfCells with
fixed members memberNames
Essbase is copying the
data from the listed range
of cells.
Not applicable
1012554
Clearing data from partitionName
partition
Essbase is clearing the
data from the listed
partition.
Not applicable
1012555
Clearing data from partitionName
partition with fixed members
memberNames
Essbase is clearing the
data from the listed
partition.
Not applicable
60
1012000 to 1012750: Calculation Messages
Message
Number
Message
Possible Cause
Possible Solution
1012556
Calculation canceled by user
userName
The listed user canceled
the calculation before it
completed.
Not applicable
1012557
Clearing all data blocks from
partitionName partition
Essbase is clearing the
data from the listed
partition.
Not applicable
1012558
Clearing all data blocks from
partitionName partition with fixed
members memberNames
Essbase is clearing the
data from the listed
partition.
Not applicable
1012559
Clearing upper level data blocks from
partitionName partition
Essbase is clearing the
data from the upper level
data blocks in the listed
partition.
Not applicable
1012560
Clearing upper level data blocks from
partitionName partition with fixed
members memberNames
Essbase is clearing the
data from the upper level
data blocks in the listed
partition.
Not applicable
1012561
Clearing noninput data blocks from
partitionName partition
Essbase is clearing the
data from the noninput
data blocks in the listed
partition.
Not applicable
1012562
Clearing noninput data blocks from
partitionName partition with fixed
members memberNames
Essbase is clearing the
data from the noninput
data blocks in the listed
partition.
Not applicable
1012563
Calculation is aborted due to floating
point error errorType
Essbase canceled the
calculation because it
encountered a floating
point error, such as
overflow, underflow, or a
division by zero.
1. Correct the floating point error.
Essbase reverted all values to their previous state or
retained values calculated before the cancellation.
How Essbase handles the cancellation depends on
the Essbase kernel isolation level settings.
Overflow errors result when you try to multiply two
very large numbers and the result is so large that
it is not supported by the computer hardware.
Underflow errors result when you try to divide a
very small number by a very large number and
the result is so small that it is not supported by
the computer hardware.
Division by zero errors result when you try to
divide one member by another member that is
zero.
2. Return the data values to their previous states.
Essbase reverted all values to their previous
states or retained values calculated before the
cancellation. How Essbase handled the
cancellation depends on the Essbase kernel
isolation level settings.
3. Run the calculation again.
61
Message
Number
Message
Possible Cause
Possible Solution
1012564
Calculation is aborted due to floating
point error
Essbase canceled the
calculation because it
encountered a floating
point error, such as
overflow, underflow, or a
division by zero.
1. Correct the floating point error.
Overflow errors result when you try to multiply two
very large numbers and the result is so large that
it is not supported by the computer hardware.
Underflow errors result when you try to divide a
very small number by a very large number and
the result is so small that it is not supported by
the computer hardware.
Division by zero errors result when you try to
divide one member by another member that is
zero.
2. Return the data values to their previous states.
Essbase reverted all values to their previous
states or retained values calculated before the
cancellation. How Essbase handled the
cancellation depends on the Essbase kernel
isolation level settings.
3. Run the calculation again.
1012566
Begin of LOOP -- looping following
commands number times
Essbase is looping
through the calculation
script commands the
listed number of times.
Not applicable
1012567
End of LOOP -- actually looped above
commands number times
Essbase completed the
loop specified in the
calculation script the
listed number of times.
Not applicable
1012568
Commit Blocks Interval was adjusted to
be number blocks
Essbase Server changed
the commit blocks interval
to optimize performance.
Not applicable
1012569
Formula on (or backward dependence
from) member memberName forces
calculation to execute in serial mode
The formula on the listed
member requires that the
calculation be performed
in serial mode instead of
parallel mode.
Not applicable
A circular or recursive dependency
along dimension dimensionName
forces calculation to execute in serial
mode
The listed dimension
contains a dependency
that requires the
calculation be executed in
serial mode instead of
parallel mode.
Not applicable
Presence of variables or formulas with
@XREF function forces calculation to
execute in serial mode
Calculation is executed in
serial mode instead of
parallel mode.
Not applicable
1012570
1012571
62
1012000 to 1012750: Calculation Messages
To run the calculation in parallel mode, consider
removing the formula or tagging the member as
Dynamic Calc.
To run the calculation in parallel mode, consider
removing the formula or tagging the member as
Dynamic Calc.
Formulas or calculation scripts that use variables with
the @XREF function must be calculated in serial
mode.
Message
Number
Message
Possible Cause
Possible Solution
1012600
Member memberName attempts to
divide by Missing, Invalid, or Near Zero
value (Message will not repeat)
When calculating the
listed member, Essbase
attempted to perform a
division by an invalid
value, such as zero or a
missing value.
Check the formula or calculation script that
calculated the listed member to Ensure that all values
used in the calculation are valid.
1012667
Your Server does not have a Currency
Conversion Option, the Calc Script
command [CCONV] is ignored
Your Essbase Server does
not have the currency
conversion option.
This command is available only when using Currency
Conversion applications.
1012668
Calculating memberNames with fixed
members memberNames
Members that Essbase is
calculating and members
that are fixed.
Not applicable
1012669
Calculating memberNames
Members that Essbase is
calculating.
Not applicable
1012670
Aggregating memberNames with fixed
members memberName
Members that Essbase is
aggregating and members
that are fixed.
Not applicable
1012671
Aggregating memberNames
Members that Essbase is
aggregating.
Not applicable
1012672
Calculator Information Message:
messageInformation
Essbase is performing an
action. The information is
logged because you
requested it. For example,
if you use the SET MSG
command, details about
the calculation are logged.
Not applicable
1012674
Hash memory number allocated for
Calc is used up, Hash Table is turned
off. Please increase the
CalcHashTblMemLimit in the essbase.
cfg file.
Essbase had no more
hash memory.
1. If ESSBASEPATH/bin/ essbase.cfg does
not exist on the server computer, create one using
a text editor.
2. In the essbase.cfg file on the server
computer, add or increase the value for
CALCHASHTBLMEMORY.
3. Stop and restart Essbase Server.
4. Perform the calculation again.
1012675
Commit Blocks Interval for the
calculation is number
Number of blocks
committed at one time.
Not applicable
1012676
Member memberName attempts to
execute @POWER/@FACTORIAL
function. Arguments are out of range.
Results may be different from versions
before 6.0 (Message will not repeat)
Essbase cannot calculate
the @POWER or
@FACTORIAL function
because the value is too
large.
Ensure that the formula or calculation script is not
requesting extremely large values, such as 2 raised
to the 1 millionth power.
63
Message
Number
Message
Possible Cause
Possible Solution
1012677
Calculating in serial
Essbase Server is
performing the
calculations in the
calculation script serially,
instead of in parallel.
If you requested the calculation run in parallel mode,
look in HYPERION_HOME/logs/essbase/app/
appName/appName.log.
Calculating in parallel with number
threads
Essbase Server is
performing the
calculations in the
calculation script in
parallel using the listed
number of threads.
Not applicable
Calculation task schedule number
Number of tasks that can
be executed concurrently.
Not applicable
Related
Topics
1012569
1012570
1012571
1012678
1012679
This indicates the kind of
performance gain you can
expect from parallel
calculation. Larger
numbers indicate more
parallel calculation.
1012680
Parallelizing using number task
dimensions.
Number of task
dimensions Essbase is
using for parallel
calculation.
You can set the number of threads using the
CALCPARALLEL configuration setting or the SET
CALCPARALLEL calculation script command. If the
listed number differs from the value you set using
CALCPARALLEL, the calculator picked the listed
number as the optimal degree of parallelism for your
database.
If the listed numbers are smaller than the number of
threads you specified using the CALCPARALLEL
configuration setting or the SET CALCPARALLEL
calculation script command, parallel calculation
does not provide a large performance gain.
Not applicable
To set the number of task dimensions, use the
CALCPARALLEL configuration setting or the SET
CALCPARALLEL calculation script command.
If the number of task
dimensions is less than
the listed number, "Usage
of calculator cache
caused reduction in task
dimensions" is displayed.
1012681
Empty tasks number
Number of tasks that
contain no calculations.
Not applicable
The number of empty
tasks affect the gains you
can receive from parallel
calculation. The ideal
number of empty tasks is
0.
1012682
64
Multiple bitmap mode calculator cache
memory usage attempted to cross limit
of number bitmaps. To ignore limit, do
not set MultipleBitmapMemCheck to
TRUE in $ESSBASEPATH/bin/essbase.
cfg.
1012000 to 1012750: Calculation Messages
The calculator cache
memory tried to use more
bitmaps than allowed,
causing Essbase to abort
the calculation.
To continue the calculation with more bitmaps, set
MULTIPLEBITMAPCHECK to FALSE in the
ESSBASEPATH/bin/essbase.cfg file on the
server computer.
Message
Number
Message
Possible Cause
Possible Solution
1012683
Multiple bitmap mode calculator cache
memory usage crossed limit of
number bitmaps. Set
MultipleBitmapMemCheck to TRUE in
$ESSBASEPATH/bin/essbase.cfg to
enforce limit.
The calculator cache
memory is using more
bitmaps than allowed.
To prevent this from happening, set
MULTIPLEBITMAPCHECK to TRUE in the
1012684
Multiple bitmap mode calculator cache
memory usage has a limit of number
bitmaps.
Number of bitmaps
Essbase can use in the
calculator cache.
Not applicable
1012700
Dynamic calc processor cannot
allocate more than number blocks from
the heap. Please increase
CalcLockBlock setting and then retry
Essbase cannot allocate
enough blocks to perform
the calculation.
Increase the number of blocks that Essbase can
allocate for a calculation:
ESSBASEPATH/bin/essbase.cfg file on the
server computer.
1. Set the maximum number of blocks that Essbase
can allocate to at least 500:
a. If ESSBASEPATH/bin/ essbase.cfg
does not exist on the server computer, create
one using a text editor.
b. In the essbase.cfg file on the server
computer, set CALCLOCKBLOCKHIGH to 500.
c. Stop and restart Essbase Server.
2. Add the SET LOCKBLOCK HIGH command to the
beginning of the calculation script.
3. Set the data cache large enough to hold all
blocks specified in the CALCLOCKBLOCKHIGH
setting.
l
Determine the block size.
l
Set the data cache size.
1012701
Unknown block type during the
dynamic calculation, neither an ESM
block nor a heap block. Essbase
internal error, Please report to
Hyperion.
Contact Oracle Support.
1012702
The block in the dynamic calc
processor block array is not marked
correctly. Essbase internal error. Please
report to Hyperion.
Contact Oracle Support.
1012703
Unknown calculation type
calculationType during the dynamic
calculation. Only default agg/formula/
time balance operations are handled.
Contact Oracle Support.
65
Message
Number
Message
Possible Cause
Possible Solution
1012704
Dynamic Calc processor cannot lock
more than number ESM blocks during
the calculation, please increase
CalcLockBlock setting and then retry (a
small data cache setting could also
cause this problem, please check the
data cache size setting).
Essbase could not lock
enough blocks to perform
the calculation.
Increase the number of blocks that Essbase can
allocate for a calculation:
1. Set the maximum number of blocks that Essbase
can allocate to at least 500.
a. If ESSBASEPATH/bin/essbase.cfg
does not exist on the server computer, create
one using a text editor.
b. In the essbase.cfg file on the server
computer, set CALCLOCKBLOCKHIGH to 500.
c. Stop and restart Essbase Server.
2. Add the SET LOCKBLOCK HIGH command to the
beginning of the calculation script.
3. Set the data cache large enough to hold all
blocks specified in the CALCLOCKBLOCKHIGH
setting.
1012706
Need to copy to Esm block during the
dynamic calculation. Esm Block not
found. Essbase internal error, Please
report to Hyperion.
1012708
For virtual time series timePeriod
retrieval, the latest time period is not
set
l
Determine the block size.
l
Set the data cache size.
Contact Oracle Support.
Essbase tried to retrieve
the time series data
without knowing the latest
time period.
Set the latest time period member name in the
retrieval tool.
l
l
For Essbase Spreadsheet Add-in, specify the
“Latest Time Series” option. See the Oracle
Essbase Spreadsheet Add-in User's Guide.
For Report Writer, use the LATEST command.
1012709
For virtual time series, the latest time
period setting timePeriod is not a level
0 member
Essbase tried to retrieve
the latest time period, but
the time member is not at
level 0 in the outline.
Ensure that the time period you want to use to
calculate the period-to-date value is a level 0
member of the dimension tagged as time.
1012710
Essbase needs to retrieve number
Essbase Kernel blocks in order to
calculate the top dynamicallycalculated block.
Number of blocks
thatEssbase must retrieve
to perform the dynamic
calculation along a sparse
dimension.
Not applicable
1012711
Clearing dynamic calc store data
blocks from partitionName partition
Essbase is clearing data
blocks from the listed
partition.
Not applicable
1012712
Clearing dynamic calc store data
blocks from partitionName partition
with fixed members memberNames
Essbase is clearing data
blocks from the listed
partition.
Not applicable
66
1012000 to 1012750: Calculation Messages
You can use this to estimate the retrieval performance
for members of sparse dimensions that are tagged
as Dynamic Calc.
Message
Number
Message
Possible Cause
Possible Solution
1012713
Two-pass Member memberName is not
tagged as Dynamic Calc.
The listed member is
tagged as Two Pass but
not tagged as Dynamic
Calc and is not a member
of the Accounts
dimension.
Not applicable
Regular member memberName
depends on dynamic-calc member
memberName.
The listed regular member
depends on a Dynamic
Calc member to calculate
its value. The listed
member may be a parent
of the Dynamic Calc
member or may use the
Dynamic Calc member in
a formula.
Because you are calculating the listed Dynamic Calc
member during batch calculation in order to calculate
the regular member that depends on it, you are losing
the benefits of tagging the listed member as Dynamic
Calc.
The listed member is
calculated using members
in a transparent partition.
When you calculate a member in a target database
using values from a source database transparent
partition, the calculation can take a long time to
complete. To improve calculation speed, use one
method:
1012714
1012715
Regular member memberName
depends on member memberName
from transparent partition. Consider
making this member Dynamic or
replicating the dependents.
Generally, it is recommended that you tag all Two
Pass members as Dynamic Calc and that all Two Pass
members be in the accounts dimension.
Consider tagging the listed Dynamic Calc member as
stored or tagging the dependent regular member as
Dynamic Calc.
l
l
At the target database, tag the member as
Dynamic Calc.
At the source database, roll up the members
needed to calculate the target member into an
upper level member. Put the upper level member
in the source database into a replicated partition.
1012716
Remote region regionDefinition is not
validated correctly yet. Cannot
continue the calc.
Essbase encountered a
remote partition region
that has not been
validated.
Open the partition definition and validate it. If
necessary, correct any errors.
1012717
Remote bitmap cache is on/off
Status of bitmap cache
(on or off).
Not applicable
The latest period setting
was at a higher generation
than the time series
member.
Ensure that the latest period setting, such as May, is
lower in the outline than the time series member,
such as Q-T-D (quarter-to-date).
1012718
For dynamic time series, the latest
period settingName setting has higher
generation member than the time
series member memberName
1012727
Dynamic calc cache sanity failed
Essbase Server determines whether to turn the
bitmap cache on or off; you cannot change this
setting.
Contact Oracle Support.
67
Message
Number
Message
Possible Cause
Possible Solution
1012733
Dynamic calc cache compression
buffer full
The Dynamic Calc cache
buffer was out of space.
The Dynamic Calc cache compression buffer is used
only when you set DYNCALCCACHEWAITFORBLK and
DYNCALCCACHEBLKRELEASE to TRUE in the
ESSBASEPATH/bin/essbase.cfg file. To fix this
problem:
1. If ESSBASEPATH/bin/ essbase.cfg does
not exist on the server computer, create one using
a text editor.
2. In the essbase.cfg file on the server
computer, increase the value of
DYNCALCCACHECOMPRBLKBUFSIZE.
3. In the essbase.cfg file on the server
computer, set DYNCALCCACHEWAITFORBLK and
DYNCALCCACHEBLKRELEASE to FALSE.
4. Stop and restart Essbase Server.
1012734
Timed out waiting for blocks from the
dynamic calc cache.
Essbase waited for a block
to become available in the
Dynamic Calc cache, but
the cache was full.
Decrease the number of concurrent queries to keep
the cache from becoming full.
Increase the amount of time that Essbase waits for
blocks in the Dynamic Calc cache:
1. If ESSBASEPATH/bin/ essbase.cfg does
not exist on the server computer, create one using
a text editor.
2. In the essbase.cfg file on the server
computer, add or increase the value of
DYNCALCCACHEBLKTIMEOUT.
3. Stop and restart Essbase Server.
Specify that queries should not wait for available
blocks in the Dynamic Calc cache:
1. If ESSBASEPATH/bin/ essbase.cfg does
not exist on the server computer, create one using
a text editor.
2. In the essbase.cfg file on the server
computer, set DYNCALCCACHEWAITFORBLK to
FALSE.
3. Stop and restart Essbase Server.
1012735
68
Thread synchronization error when
allocating from the dynamic calc
cache.
1012000 to 1012750: Calculation Messages
Contact Oracle Support
Message
Number
Message
Possible Cause
Possible Solution
1012736
The Dyn.Calc.Cache for database
databaseName can hold a maximum of
number blocks.
Maximum number of
blocks that the Dynamic
Calc cache for the listed
database can hold.
Not applicable
To change the number of blocks in the Dynamic Calc
cache:
1. If ESSBASEPATH/bin/ essbase.cfg does
not exist on the server computer, create one using
a text editor.
2. In the essbase.cfg file one the server, add or
change DYNCALCCACHEMAXSIZE.
3. Stop and restart Essbase Server.
1012737
The Dyn.Calc.Cache for database
databaseName, when full, will result in
action.
Essbase performs these
actions when the dynamic
calculator cache is full:
l
l
Not applicable
If
DYNCALCCACHEWAIT
FORBLK in the
essbase.cfg file is
TRUE, Essbase waits
to store and calculate
data blocks for the
current query in the
dynamic calculator
cache
If
DYNCALCCACHEWAIT
FORBLK in the
ESSBASEPATH/
bin/essbase.cfg
file is FALSE, Essbase
checks
DYNCALCCACHEONLY
m
m
If
DYNCALCCACHEO
NLY is TRUE,
Essbase
generates an error
message
If
DYNCALCCACHEO
NLY is FALSE,
Essbase stores
and calculates
data blocks for the
current query in
memory outside of
the dynamic
calculator cache
69
Message
Number
Message
Possible Cause
Possible Solution
1012738
The Dyn.Calc.Cache for database
databaseName has a timeout of
number seconds when waiting for free
blocks.
Current value of
DYNCALCCACHEBLKTIME
OUT.
Not applicable
1012739
The Dyn.Calc.Cache for database
databaseName, upon timeout of a wait
for free blocks, will result in action.
Essbase performs this
action after the specified
waiting period:
Not applicable
l
If
DYNCALCCACHEBLKR
ELEASE in the
ESSBASEPATH/
bin/essbase.cfg
file is TRUE, Essbase
makes room available
in the dynamic
calculator cache by
temporarily storing
inactive blocks in
another, compressedblock buffer.
l
If
DYNCALCCACHEBLKR
ELEASE in the
ESSBASEPATH/
bin/essbase.cfg
file is FALSE, Essbase
does not find room in
the dynamic
calculator cache for
another set of blocks,
soEssbase checks
DYNCALCCACHEONLY
m
m
70
1012000 to 1012750: Calculation Messages
If
DYNCALCCACHEO
NLY is TRUE,
Essbase
generates an error
message
If
DYNCALCCACHEO
NLY is FALSE,
Essbase stores
and calculates
data blocks for the
current query in
memory outside of
the dynamic
calculator cache.
Message
Number
Message
Possible Cause
Possible Solution
1012740
The Dyn.Calc.Cache for database
databaseName uses a buffer of size
number bytes to store compressed
released blocks.
Current value of
DYNCALCCACHECOMPRB
LKBUFSIZE.
Not applicable
1012741
Allocation outside the dynamic calc
cache is disallowed
Current value of
DYNCALCCACHEONLY is
TRUE.
Not applicable
1012742
Two-pass calc skipped on member
memberName in attribute calc
The listed member was
skipped during Two Pass
calculation because the
listed member has no
member formula or the
listed member has a
runtime dependency.
Runtime dependent
functions include:
@CURRMBR, @PARENT,
@PARENTVAL,
@MDPARENTVAL,
@ANCEST, @ANCESTVAL,
and @MDANCESTVAL.
Not applicable
1012750
Retrieve & Lock operation is not
supported on attribute cells
Essbase cannot update
cells that belong to a
relational partition.
Ensure that the cells being updated do not belong to
a relational partition.
71
72
1012000 to 1012750: Calculation Messages
7
1013000 to 1013999: Requestor
Messages
Table 7
Message
Number
Message
Possible Cause
Possible Solution
1013009
Administrator Has
Temporarily
Disabled User
Commands
When a database is being restructured or any application/database
on the server is being copied, you can get this message.
In Application Settings, verify
that the Allow Commands or
Allow Updates options are not
selected.
When a cube is being restructured, commands are restricted
because the integrity of the cube has to be stable and no one is
allowed to access it.
Copying an application requires that the Essbase security file be in
read/write mode and therefore other applications are not
accessible until the process is completed.
1013136
Invalid login id please login again
Restructuring outline using EsbOtlRestructure VB API function
causes error.
This function requires you to have the appropriate level of access
to the specified application and/or database to contain the outline
object.
Verify that you have
Application Designer or
Database Designer privileges
(ESB_PRIV_APPDESIGN or
ESB_PRIV_DBDESIGN) for the
specified application or
database containing the
outline.
73
74
1013000 to 1013999: Requestor Messages
8
1014004 to 1014043: Lock
Manager Messages
Table 8 lists Lock Manager error and informational messages.
Table 8
Lock Manager Messages 1014004 to 1014043
Message
Number
Message
Possible Cause
Possible Solution
1014004
Unable to Update Members
Which Have Not Been Locked
Essbase cannot update the
members because the
members are not locked.
Wait a few minutes and retry the operation to allow the
other active user's process to finish.
See if another user has locked the file (see “Unlocking
Objects” on page 126).
Increase the values for NETDELAY and NETRETRYCOUNT
(see “Setting NETDELAY and NETRETRYCOUNT” on page
125).
1014018
Members Currently Locked by
another transaction
Essbase cannot update the
members because they are
locked by another user.
Wait a few minutes and retry the operation to allow the
other active user's process to finish.
See if another user has locked the file (see “Unlocking
Objects” on page 126).
If this error happens frequently, ensure that users are
logging off Essbase correctly.
1014025
Unable to update database
while in readonly mode for
backup
Essbase cannot update the
database because the
database is in read-only
mode.
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 Ensure that the archive process is
completed before the next process begins.
1014026
Requested lock is currently
held by another transaction,
and waiting is currently not
allowed.
Essbase cannot lock the
object because it is currently
locked by another
transaction.
Wait a few minutes and retry the operation to allow the
other active user's process to finish.
See if another user has locked the file (see “Unlocking
Objects” on page 126).
Set Essbase to wait automatically, and retry the operation.
If this error happens frequently, ensure that users are
logging off Essbase correctly.
75
Message
Number
Message
Possible Cause
Possible Solution
1014027
Transaction
transactionHandle is
deadlocked with transaction
transactionHandle.
Essbase cannot complete the
transaction because two or
more users tried to lock the
same two blocks in the
opposite order at the same
time. For example, user1 tried
to access block 1 then block
2, while user2 tried to access
block2 then block 1.
Ensure that two users are not performing calculations on
the same blocks at the same time.
Transaction
transactionHandle is waiting
for transaction
transactionHandle.
Essbase cannot complete the
transaction because the
current transaction is waiting
for a deadlocked transaction.
Ensure that two users are not performing calculations on
the same blocks at the same time.
Essbase could not get a lock in
the specified wait time.
Essbase could not lock the
object in the user-specified
wait time.
Wait a few minutes and retry the operation to allow the
other active user's process to finish.
1014028
1014031
Related
Topics
1014032
If this error happens frequently, instruct spreadsheet
users to clear the “Update Mode” option. See the Oracle
Essbase Spreadsheet Add-in User's Guide.
If this error happens frequently, instruct spreadsheet
users to clear the “Update Mode” option. See the Oracle
Essbase Spreadsheet Add-in User's Guide.
Increase the time that Essbase waits automatically for a
lock.
See if another user has locked the file (see “Unlocking
Objects” on page 126).
Increase the values for NETDELAY and NETRETRYCOUNT
(see “Setting NETDELAY and NETRETRYCOUNT” on page
125).
If this error happens frequently, ensure that users are not
starting complex calculations and logging off Essbase
before the calculation is completed.
Stop and restart Essbase Server. Then determine whether
the database is corrupt (see “Checking for Database
Corruption” on page 124).
If this error is happening because spreadsheet users are
locking objects, increase the values for LOCKTIMEOUT.
1. If ESSBASEPATH/bin/essbase.cfg does not
exist on the server computer, create one using a text
editor.
2. In the ESSBASEPATH/bin/essbase.cfg file on
the server computer, add or increase the value for
LOCKTIMEOUT.
3. Stop and restart Essbase Server.
76
1014004 to 1014043: Lock Manager Messages
Message
Number
Message
Possible Cause
Possible Solution
1014032
Essbase could not get a lock.
Essbase will keep trying until it
reaches the specified wait
time.
Essbase could not lock an
object. This message is
repeated every thirty seconds
until the object is locked or
until the user-specified wait
time is reached.
Wait a few minutes and retry the operation to allow the
other active user's process to finish.
Related
Topics
1014031
See if another user has locked the file (see “Unlocking
Objects” on page 126).
Increase the values for NETDELAY and NETRETRYCOUNT
(see “Setting NETDELAY and NETRETRYCOUNT” on page
125).
If this error happens frequently, ensure that users are not
starting complex calculations and logging off Essbase
before the calculation is completed.
Stop and restart Essbase Server. Then determine whether
the database is corrupt (see “Checking for Database
Corruption” on page 124).
If this error is happening because spreadsheet users are
locking objects, increase the values for LOCKTIMEOUT.
1. If ESSBASEPATH/bin/essbase.cfg does not
exist on the server computer, create one using a text
editor.
2. In the ESSBASEPATH/bin/essbase.cfg file on
the server computer, add or increase the value for
LOCKTIMEOUT.
3. Stop and restart Essbase Server.
Essbase cannot allocate the
lock manager event because
it is out of memory.
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.
1014033
Failed to allocate lock manager
event. operation aborted
1014034
Failed to create lock manager
event. operation aborted
1014035
Failed to allocate lock manager
waiter node. operation aborted
Essbase cannot allocate the
lock manager waiter node
because it is out of memory.
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.
1014036
Lock request would block, but
waiting is not allowed.
The block this transaction is
trying to lock is locked by
another transaction.
Currently, Essbase is
configured to not allow
waiting, so the current
transaction cannot wait to
lock the block.
Set Essbase to wait a specified amount of time to lock a
block.
1014039
Unable to perform a write
operation to database
databaseName while the
database is in read-only mode.
The listed database is in
read-only mode because the
administrator issued the
BEGINARCHIVE command to
back up the database.
Wait until the archival process, starting with the
BEGINARCHIVE command and ending with the
ENDARCHIVE command, is finished. When the archival
process finishes, issue the ENDARCHIVE command.
Contact Oracle Support.
77
Message
Number
Message
1014040
Failed to get the current
thread's handle. operation
aborted
Contact Oracle Support.
1014041
Failed to get the current
thread's base priority.
operation aborted
Contact Oracle Support.
1014042
Failed to get the current
thread's high priority.
operation aborted
Contact Oracle Support.
1014043
Error encountered while
releasing a lock in database
databaseName.
78
Possible Cause
An error occurred while
Essbase was waiting to
release a write lock.
1014004 to 1014043: Lock Manager Messages
Possible Solution
Contact Oracle Support.
9
1019002 to 1019056: Database
Object Messages
Table 9 lists database object error and informational messages.
79
Table 9
Database Object Messages 1019002 to 1019056
Message
Number
Message
Possible Cause
Possible Solution
1019002
Unable To Find Or Open fileName
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.
Ensure that the file exists. If it does not exist, restore
the file from backups.
Related
Topics
1019003
Ensure that you have the correct operating system
privileges for the file and directory.
If you are using ESSCMD, ensure that the file name
and path are correct. On UNIX, ensure that
capitalization is correct.
Ensure that you have enough disk space. On UNIX,
ensure that you have enough space on the root
partition.
If the file is essbase.sec, determine whether it
is corrupt.
On UNIX, check the user limit profile (see “Checking
the User Limit Profile” on page 125).
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 to copy or
delete the application correctly.
If the file is a rules file, ensure that it is associated
with the correct outline.
Stop and restart the application.
Stop and restart Essbase Server.
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.db, replace
the file with its backup (see “Replacing Database
Files with Backups” on page 125).
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.ind, delete
and reload the data files. Deleting your data files
deletes all data in your database; you must reload
and recalculate the database.
1. Stop Essbase Server.
2. Delete the databaseName.ind, Essxxx.
ind, Essxxx.pag, databaseName.esm,
and databaseName.tct files.
3. Restart Essbase Server.
4. Reload the database, and then recalculate the
database.
5. Determine whether the database is corrupt (see
“Checking for Database Corruption” on page
124).
80
1019002 to 1019056: Database Object Messages
Message
Number
Message
Possible Cause
Possible Solution
1019003
Unable to Read Information From
fileName
Essbase cannot read from
the listed file.
Ensure that the listed file exists. If it does not exist,
restore the file from backups.
Related
Topics
1019002
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.
Ensure that you have enough disk space.
See if another user has locked the file (see
“Unlocking Objects” on page 126).
If you are using Essbase Spreadsheet Add-in,
increase the retrieval buffer size to at least 50 KB.
Determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
If the listed file is ARBORPATH/App/appName/
databaseName/databaseName.db, replace
the file with its backup (see “Replacing Database
Files with Backups” on page 125).
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.ind, try to
restore the file from backups. If that does not work,
delete and reload the data files. Deleting your data
files deletes all data in your database; you must
reload and recalculate the database.
1. Stop Essbase Server.
2. Delete the databaseName.ind, Essxxx.ind,
Essxxx.pag, databaseName.esm, and
databaseName.tct files.
3. Restart Essbase Server.
4. Reload the database.
5. Recalculate the database.
81
Message
Number
Message
Possible Cause
Possible Solution
1019004
Unable to write information to file
fileName, errno is
operatingSystemErrorNumber.
Essbase cannot write to the
listed file.
Ensure that the listed file exists. If it does not exist,
restore the file from backups.
Ensure that you have enough disk space.
Ensure that these environment variables (see
“Setting Environment Variables” on page 123) are
set correctly:
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
If you are on a UNIX computer, check the user limit
profile (see “Checking the User Limit Profile” on
page 125).
Verify that you are using data compression to limit
page file size.
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.db, replace
the file with its backup (see “Replacing Database
Files with Backups” on page 125).
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.ind, try to
restore the file from backups. If that does not work,
delete and reload the data files. Deleting your data
files deletes all data in your database; you must
reload and recalculate the database.
1. Stop Essbase Server.
2. Delete the databaseName.ind, Essxxx.ind,
Essxxx.pag, databaseName.esm, and
databaseName.tct files.
3. Restart Essbase Server.
4. Reload the database.
5. Recalculate the database.
82
1019002 to 1019056: Database Object Messages
Message
Number
Message
Possible Cause
Possible Solution
1019005
Unable to Read fileName, Not a
Recognized Format
Essbase cannot read the
listed file.
If possible, restore the file from backups.
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.db, replace
the file with its backup (see “Replacing Database
Files with Backups” on page 125).
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.ind, try to
restore the file from backups. If that does not work,
delete and reload the data files. Deleting your data
files deletes all data in your database; you must
reload and recalculate the database.
1. Stop Essbase Server.
2. Delete the databaseName.ind, Essxxx.
ind, Essxxx.pag, databaseName.esm,
and databaseName.tct files.
3. Restart Essbase Server.
4. Reload the database.
5. Recalculate the database.
1019006
Unable to Read fileName, Created
Using A Previous Version
Essbase cannot read the
listed file.
Determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
The listed file may be corrupt. If possible, restore
the file from backups.
1019007
1019008
Unable To Read fileName, Type Does
Not Match Name
Reading Application Definition For
appName
1019009
Reading Database Definition For
databaseName
1019010
Writing Application Definition For
appName
1019011
Writing Database Definition For
databaseName
1019012
Reading Outline For Database
databaseName
The listed file type does not
match the contents of the
file. The listed file is probably
corrupt.
Determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
Essbase is reading the
application definition for the
listed application.
Not applicable
Essbase is reading the
database definition for the
listed database.
Not applicable
Essbase is writing the
application definition for the
listed application.
Not applicable
Essbase is writing the
database definition for the
listed database.
Not applicable
Essbase is reading the
outline definition for the
listed database.
Not applicable
The listed file may be corrupt. If possible, restore
the file from backups.
83
Message
Number
Message
Possible Cause
Possible Solution
1019013
Writing Outline For Database
databaseName
Essbase is writing the outline
for the listed database back
to the disk.
Not applicable
1019014
Unable To Write Information For
Database databaseName
Essbase cannot find the
listed database.
Ensure that the database name is correct.
1019015
Database Outline Already Loaded For
Database databaseName
The database outline for the
listed database is loaded.
Do not try to load a database more than once.
1019017
Reading Parameters For Database
databaseName
Essbase is reading the
parameters for the listed
database.
Not applicable
1019018
Writing Parameters For Database
databaseName
Essbase is writing the
parameters for the listed
database.
Not applicable
1019019
Reading Data File Free Space
Information For Database
databaseName
Essbase is reading the free
space for the listed
database.
Not applicable
Ensure that the database exists in the specified
location.
Free space information is stored in the
ARBORPATH/app/appName/databaseName/
databaseName.ind file. If ample free space
exists, it may take some time to read the free space
information.
Writing Free Space Information For
Database databaseName
Essbase is writing the free
space for the listed
database.
Not applicable
1019021
Reading Database Mapping For
databaseName
Essbase is reading database
information for the listed
database.
Not applicable
1019022
Writing Database Mapping For
databaseName
Essbase is writing database
information for the listed
database.
Not applicable
1019024
Reading Outline Transaction For
Database databaseName
Essbase is reading the
outline updates from the
Not applicable
1019020
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.
ARBORPATH/app/
appName/
databaseName/
databaseName.otn file.
1019025
84
Reading Rules From Rule Object For
Database databaseName
1019002 to 1019056: Database Object Messages
Essbase is reading a rules
file for the listed database.
Not applicable
Message
Number
Message
Possible Cause
Possible Solution
1019026
Unknown member memberName
found while processing string string
Essbase does not recognize
the listed string as a member
of the outline.
Ensure that the member name is valid. The member
name is in the rules file.
l
Are you using the correct rules file?
l
Is the rules file connected to the correct
outline?
l
Can you validate the rules file?
l
Are member names or variable names enclosed
in quotation marks where necessary?
l
l
Does the member exist in the outline? If not,
you can add the member by modifying the
outline during the dimension build or add the
member in the Outline Editor.
Ensure that the member is not specified as a
header in the rules file.
1019028
Out of disk space, Unable to write
information to file fileName
Essbase is out of disk space
and cannot write to the listed
file.
Ensure that you have enough disk space.
1019031
Unable to write fileName; database is
in readonly mode for backup
Essbase cannot write to the
listed file because the
database is in read-only
mode.
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 a
sleep command to Ensure 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 readonly mode.
1019032
Unable to write to fileName; database
is in readonly mode for archive
Essbase cannot write to the
listed file because the
database is in read-only
mode.
it 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 a
sleep command to Ensure 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 readonly mode.
85
Message
Number
Message
Possible Cause
Possible Solution
1019034
Reading Outline Change Log For
Database databaseName
Essbase is reading the
outline changes in the
Not applicable
ARBORPATH/app/
appName/
databaseName/
databaseName.ocl file.
1019035
Writing Outline Change Log For
Database databaseName
Essbase is writing the outline
changes to the
Not applicable
ARBORPATH/app/
appName/
databaseName/
databaseName.ocl file.
1019036
1019037
1019038
Dimension number number for
Database databaseName is invalid
Member number memberName for
Database databaseName is invalid
DB file is missing.
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.
Determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
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.
Determine whether the database is corrupt (see
“Checking for Database Corruption” on page 124).
Essbase cannot find the
If ARBORPATH/app/appName/
databaseName/databaseName.db exists,
rename it to databaseNameold.db. Then
rename the databaseName.dbb backup file to
databaseName.db.
ARBORPATH/app/
appName/
databaseName/
databaseName.db file.
If the outline file is corrupt, restore the outline file
from backups.
If necessary, restore the outline file from backups.
If databaseName.db does not exist, rename the
databaseName.dbb file to databaseName.
db.
If databaseName.dbb does not exist, restore the
databaseName.db file from backups.
1019039
86
Cannot write to file fileName because
object type type is invalid. Make sure
Essbase is properly installed and
configured.
1019002 to 1019056: Database Object Messages
Essbase cannot write to the
listed file.
Ensure that Essbase is installed correctly. If
necessary, reinstall Essbase.
Message
Number
Message
Possible Cause
Possible Solution
1019040
Unable to write to file fileName
because the application is shutting
down
Essbase cannot write to the
listed file because the
application is closing.
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 all of these steps:
1. As a user, exit Administration Services or
Spreadsheet Add-in.
2. If the previous step does not work, have the
administrator disconnect the user.
3. If the previous step does not work, unlock any
locked objects (see “Unlocking Objects” on
page 126), unload the database, stop the
database, and try again to disconnect the user.
4. If the previous step does not work, have the
administrator log off the user in the Agent
window.
5. If the previous step does not work, stop the
application from the Agent window.
6. If the previous step does not work, end the task
(see “Ending the Server Task” on page 126).
7. If the previous step does not work, restart the
server machine.
87
Message
Number
Message
Possible Cause
Possible Solution
1019041
Unable to write information to file
fileName, adWriteObject returns
EssbaseErrorNumber. See server
logfile for details.
Essbase cannot write to the
listed file.
Check HYPERION_HOME/logs/essbase/
app/appName/appName.log for information
about the listed Essbase error number.
Related
Topics
Ensure that the file exists. If it does not exist, restore
the file from backups.
1019004
Ensure that you have enough disk space.
Ensure that these environment variables (see
“Setting Environment Variables” on page 123) are
set correctly:
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
If you are on a UNIX computer, check the user limit
profile (see “Checking the User Limit Profile” on
page 125).
Verify that you are using data compression to limit
page file size.
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.db, replace
the file with its backup (see “Replacing Database
Files with Backups” on page 125).
If the listed file is ARBORPATH/app/appName/
databaseName/databaseName.ind, try to
restore the file from backups. If that does not work,
delete and reload the data files. Deleting your data
files deletes all data in your database; you must
reload and recalculate the database.
1. Stop Essbase Server.
2. Delete the databaseName.ind, Essxxx.
ind, Essxxx.pag, databaseName.esm,
and databaseName.tct files.
3. Restart Essbase Server.
4. Reload the database.
5. Recalculate the database.
1019042
Unable to move the file pointer to the
location specified for file fileName,
errno is operatingSystemError.
1019043
Error Creating Outline Pool For
Database databaseName
Essbase can not create the
outline memory pool. The
outline memory pool holds
outline items in memory.
Ensure that you have sufficient memory on the
server computer.
1019044
Error Allocating Mem in Outline Pool
For Database databaseName
Essbase can not create the
outline memory pool. The
outline memory pool holds
outline items in memory.
Ensure that you have sufficient memory on the
server computer.
88
1019002 to 1019056: Database Object Messages
Contact Oracle Support.
Message
Number
Message
Possible Cause
Possible Solution
1019045
Reading Partition Definition File For
Database databaseName
Essbase is reading the
partition definition file for the
listed database.
Not applicable
1019046
Outline buffer cannot handle more
than number hole
Contact Oracle Support.
1019047
Outline buffer error. Hole position
number does not match with number
in the buffer
Contact Oracle Support.
1019048
Outline buffer writing error. number
bytes written does not match with hole
size number
Contact Oracle Support.
1019049
Outline buffer error. Cannot flush
buffer with number hole to a
fragmented outline file
Contact Oracle Support.
1019050
Outline buffer error. File position
number does not match with number
bytes written
Contact Oracle Support.
1019051
Total adReadStruct Elapsed Time
using outline buffer: number seconds
The time used to read the
outline buffer.
Not applicable
1019052
Total adOtlReadOutline Elapsed Time
using outline buffer: number seconds
The time used to read the
outline data into memory.
Not applicable
1019053
Total adOtlWriteOutline Elapsed Time
using outline buffer: number seconds
The time used to write the
outline data.
Not applicable
1019054
Invalid Named Attribute Opcode For
Member memberName
The type defined for the
listed attribute member is
not valid.
Ensure that all attribute members use one of these
types: text, numeric, Boolean, or date.
1019056
Object file path path is too long.
The listed path is too long.
Ensure that the listed path is smaller than 1025
bytes.
89
90
1019002 to 1019056: Database Object Messages
10
1040002 to 1042025: Network
Messages
Table 10 lists network error and informational messages.
Table 10
Network Messages 1040002 to 1042025
Message
Number
Message
Possible Cause
Possible Solution
1040002
Too many arguments supplied for this
request
The number of buffers to be
sent does not match the
number of buffers predicted
at the start of the session. In
the networking layer, ensure
that the number of buffers
predicted to be sent in this
session is correct.
This is an internal error. Contact Oracle
Support.
1040003
No length specified for data type
The network cannot
determine the network buffer
length based on the buffer
type. In the networking layer,
specify the length of the buffer
explicitly.
This is an internal error. Contact Oracle
Support.
1040004
Invalid structure type. An application
protocol error might exist between server
and client processes.
Essbase encountered data
with an incorrect data type.
Ensure that the client computer and the
server computer run the same release of
ODBC. Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
1040006
No message database specified
Essbase did not have a
message database defined.
This is an internal error. Contact Oracle
Support.
1040007
Cannot find message database fileName,
which is required for normal operations.
Make sure your PATH and ESSBASEPATH
variables are pointing to the correct
directories. Make sure that databaseName
exists in the ESSBASEPATH/bin directory
Essbase cannot find the
message database file,
Ensure that your PATH and ESSBASEPATH,
and environment variables (see “Setting
Environment Variables” on page 123) are
set correctly.
ESSBASEPATH/bin/
essbase.mdb.
Ensure that the network is up and running
correctly.
Hyperion recommends that the file descriptor
limit (see “Checking the User Limit Profile” on
page 125) setting be 1024 files.
91
Message
Number
Message
Possible Cause
Possible Solution
1040008
Error reading message database fileName.
fileName could be corrupted, or it could be
the wrong release. Make sure that the file
you are using is from the same Essbase
release level as the .exe and .dll files
Essbase cannot read the
message database file,
Ensure that you are using the correct release
of the message database file,
ESSBASEPATH/bin/essbase.mdb. If
you are not sure, reinstall Essbase.
1040010
Invalid data type for conversion
Essbase encountered an
invalid data type while
creating a message string.
This is an internal error. Contact Oracle
Support.
1040011
NULL network context passed to message
function
Essbase did not have a valid
network context to use to
create a message.
This is an internal error. Contact Oracle
Support.
1040012
Invalid structure type
Essbase cannot read the
information in the data
structure.
This is an internal error. Contact Oracle
Support.
1040013
Invalid structure field type
Essbase cannot read the
fields inside the data
structure.
Ensure that Essbase Server and the Essbase
client are installed correctly.
1040014
RegOpenKeyEx() Failed
Essbase cannot find the host
name in the registry.
Ensure that your registry is set up correctly.
Consult your Windows documentation.
1040015
RegQueryInfoKey() Failed
Essbase cannot retrieve the
registry key.
Ensure that your registry is set up correctly.
Consult your Windows documentation.
1040016
RegEnumValue() Failed
Essbase cannot retrieve
values from the registry.
Ensure that your registry is set up correctly.
Consult your Windows documentation.
1040017
Host Name Not Available
Essbase cannot find the
specified host name.
Ensure that the host name is correct.
1040018
Bad hostname to adNetIsLocalHost()
Essbase cannot find the host
name.
Ensure that the host name is correct.
1040019
Message code message; see server log for
message text
The listed error occurred.
Check the application and Essbase Server
logs for more details about the error that
occurred. The listed error is not an Essbase
error. Check the operating system
documentation or networking
documentation.
1041000
Network error message: Cannot Create
Named Pipe
Essbase cannot create the
named pipe because of the
listed error.
The listed error is not an Essbase error.
Consult the networking documentation.
92
1040002 to 1042025: Network Messages
ESSBASEPATH/bin/
essbase.mdb.
Message
Number
Message
Possible Cause
Possible Solution
1041002
Network error: Timed out waiting for
connection, Error Code: message
Essbase cannot connect to
the named pipe.
Determine whether the ESSBASEPATH/
bin/essnet.dll files match on the client
computer and the server computer.
l
l
If the ESSBASEPATH/bin/essnet.
dll files do not match, reinstall the
networking protocol. Be sure to select
named pipes as the networking protocol.
Consult the Oracle Hyperion Enterprise
Performance Management System
Installation Start Here.
If the ESSBASEPATH/bin/essnet.
dll files match, consult the networking
documentation.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
1041003
Network error message: Cannot disconnect
named pipe
Essbase cannot disconnect
from the named pipe.
This is not an Essbase error. Consult the
networking documentation.
1041004
Network error message: Cannot send data
Essbase cannot send data
over the network using named
pipes.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
Check the index cache size, data cache size,
and block size to Ensure that they are within
the recommended ranges.
1041005
Network error message: The Network API
timed out waiting to receive data from the
Named Pipe. Increase the NetRetryCount
and/or NetDelay values in your essbase.cfg
file. Make sure you update this file on both
client and server, if they exist on different
computers. Restart the client and try again.
The Essbase network API
timed out before receiving
data from the named pipe.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
1041006
Network error: Timed out waiting to receive
message
Essbase timed out before
receiving data from the
named pipe.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
1041007
Network error: Cannot locate connect
information for namedPipe
Essbase cannot find the
named pipe.
Create the named pipe. Consult the
networking documentation.
93
Message
Number
Message
Possible Cause
Possible Solution
1041008
Network error: Cannot locate Essbase on
server serverComputerName. Verify that the
serverComputerName is accessible using
the Named Pipe and that the Essbase Agent
is running on the server
The Essbase client, such as
Essbase Spreadsheet Add-in,
cannot connect to Essbase
Server.
Ensure that the installation is correct.
l
Did you select named pipes as the
protocol when you installed?
l
Are you using the correct release of
ESSBASEPATH/bin/essnetw.dll?
If you are not sure, reinstall the
networking protocol. Be sure to select
named pipes as the networking protocol.
Consult the Oracle Hyperion Enterprise
Performance Management System
Installation Start Here.
Ensure that Essbase Server is running
correctly. If necessary, stop and restart
Essbase Server.
1041009
Network error: Cannot connect to server
serverName
Essbase API cannot complete
the OpenOutline function.
Ensure that Essbase Server is running.
Ensure that the network is running.
Ensure that the client can connect to Essbase
Server.
Check the return values from
EssOtlOpenOutline and EssOtlVerifyOutline.
1041011
Network error
message:InitializeSecurityDescriptor failed
Essbase cannot initialize and
set the security descriptor for
the named pipe.
This is not an Essbase error message. Consult
the operating system documentation and the
networking documentation.
1041012
Network error message:
SetSecurityDescriptorDacl failed
Essbase cannot initialize and
set the security descriptor for
the named pipe.
This is not an Essbase error message. Consult
the operating system documentation and
networking documentation.
1041013
Network error: Timed out sending data
Essbase timed out before
sending data to the named
pipe.
Ensure that Essbase Server is running.
Ensure that the network is running.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
1041014
Network error: NodeName required in
essbase.cfg for Named Pipe
The NODENAME setting was
not specified in the
ESSBASEPATH/bin/
essbase.cfg file.
1. If ESSBASEPATH/bin/essbase.cfg
does not exist on the server computer in
the ESSBASEPATH/bin directory,
create one using a text editor.
2. In the ESSBASEPATH/bin/essbase.
cfg file, set NODENAME.
3. Stop and restart Essbase Server.
1042002
94
Network error message: Cannot Terminate
Socket
1040002 to 1042025: Network Messages
Essbase cannot close the
socket.
Close the socket manually. Consult the
networking documentation.
Message
Number
Message
Possible Cause
Possible Solution
1042003
Network Error message: Unable To Locate
serverName In Hosts File
Essbase cannot locate the
server computer name.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
Are the server computer and the client
computer running the same network
protocols?
Are you using the TCP/IP or named pipes
network protocol? These are the only two
network protocols supported by Essbase.
Is the network protocol installed correctly?
Consult the Oracle Hyperion Enterprise
Performance Management System
Installation Start Here.
Are you using a stand-alone computer with
no network interface card? Consult the
Oracle Hyperion Enterprise Performance
Management System Installation Start Here.
Is the server name you entered correct? Are
there typographical errors?
Is the hosts file correct?
l
Windows: Check the HOSTS file for an
entry for the server name. If no entry
exists, add one. For example, add this
line to the HOSTS file to add a server
named aspen with the IP address of 127.
0.0.1:
127.0.0.1 aspen
l
UNIX: Check the .rhosts file for an
entry for the server name. If no entry
exists, add one. For example, add this
line to the .rhosts file to add a server
named aspen with the IP address of 127.
0.0.1:
127.0.0.1 aspen
Ensure that the .rhosts file is included
in your path.
1042004
Network Error message: Unable To Create
Local Socket
The Essbase client cannot
create a TCP/IP socket.
Ensure that you have the correct release of
ESSBASEPATH/bin/essnetw.dll and
ESSBASEPATH/bin/winsock.dll. If
you are not sure, reinstall the Essbase client.
If reinstalling the Essbase client does not
solve the problem, look up the listed
message text in the networking
documentation.
95
Message
Number
Message
Possible Cause
Possible Solution
1042006
Network Error message: Unable To Connect
To serverName. The client timed out waiting
to connect to the Essbase Agent using TCP/
IP. Check your network connections. Also
please make sure that Server and Port
values are correct.
Administration Services can
find the server computer but
cannot connect to Essbase
Server.
Are you trying to connect to the correct server
computer? Are there typographical errors?
Is Essbase Server running on the listed
computer?
l
If Essbase Server is not running, restart
Essbase Server.
l
If Essbase Server crashed, follow the
procedures for an abnormal shutdown.
l
If Essbase Server has frozen, stop
Essbase Server and follow the
procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the
standard methods, end the task (see
“Ending the Server Task” on page 126).
Are the network protocols installed correctly
on the server computer and the client
computer? Consult the Oracle Hyperion
Enterprise Performance Management
System Installation Start Here.
Are the ports for Essbase Server open and
running? If not, specify non-default ports.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
If you are using ESSCMD, ensure that you are
using the correct server name (not an alias)
and that the server name, user name, and
password are all enclosed in quotation
marks. For example, use this command to log
on a user named Max to a server named
ASPEN:
LOGIN "ASPEN" "Max" "PASSWORD";
1042007
Network Error message: Unable To Listen For
Connections
The TCP/IP socket of the
server computer cannot be
listened on.
This is not an Essbase message. Check the
operating system and networking
documentation.
1042008
Network Error message: Unable To Accept
Connections
The server computer cannot
accept more requests from
the client.
This is not an Essbase message. Check the
operating system and networking
documentation.
96
1040002 to 1042025: Network Messages
Message
Number
Message
Possible Cause
Possible Solution
1042009
Network Error message: Unable To Create
Host Server Socket
The server computer cannot
create a TCP/IP socket.
Are the network protocols installed correctly
on the server computer and the client
computer? Is TCP/IP bound to the network
adapter? Consult the Oracle Hyperion
Enterprise Performance Management
System Installation Start Here.
Is the hosts file correct?
l
Windows: Check the HOSTS file for an
entry for the server name. If no entry
exists, add one. For example, add this
line to the HOSTS file to add a server
named aspen with the IP address of 127.
0.0.1:
127.0.0.1 aspen
l
UNIX: Check the .rhosts file for an
entry for the server name. If no entry
exists, add one. For example, add this
line to the .rhosts file to add a server
named aspen with the IP address of 127.
0.0.1:
127.0.0.1 aspen
Ensure that the .rhosts file is included in
your path.
1042010
Network Error message: Unable to Bind Host
Server Socket On Port number
Essbase cannot bind a server
socket on the listed port.
Is Essbase Server running on the listed
computer?
l
If Essbase Server is not running, restart
Essbase Server.
l
If Essbase Server crashed, follow the
procedures for an abnormal shutdown.
l
If Essbase Server has frozen, stop
Essbase Server and follow the
procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the
standard methods, end the task (see
“Ending the Server Task” on page 126).
Is another application using the Essbase
port? The Essbase agent listens on TCP/IP
port 1423 for incoming requests. If another
application assigns that port before you start
Essbase Server, Essbase Server cannot
process requests. If necessary, reboot the
server computer and start Essbase Server
before other applications.
1042011
Network error message: Cannot Close
Socket
Essbase cannot close the
socket.
Close the socket yourself. Consult the
networking documentation.
97
Message
Number
Message
Possible Cause
Possible Solution
1042012
Network error message: Cannot Send Data
Essbase cannot send data
over the network using named
pipes.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
Check the index cache size, data cache size,
and data block size to Ensure that they are
within the recommended ranges.
1042013
Network error message: Cannot Receive
Data
Essbase cannot receive data
using the TCP/IP connection.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
Ensure that Essbase Server and the client are
running.
l
l
l
If Essbase Server receives this message,
ensure that the client you are trying to
connect to is running.
If a client receives this message, ensure
that the Essbase Server you are trying to
connect to is running.
If Essbase Server has frozen, stop
Essbase Server and follow the
procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the
standard methods, end the task (see
“Ending the Server Task” on page 126).
Determine whether the database is corrupt
(see “Checking for Database Corruption” on
page 124).
1042015
Network error: Cannot Locate Connect
Information For APICommand
The active application and
database are not set.
If you are using the C API, use the
EssSetActive function to set the active
application and database.
If you are using the Visual Basic API, use the
EsbSetActive function to set the active
application and database.
98
1040002 to 1042025: Network Messages
Message
Number
Message
Possible Cause
Possible Solution
1042017
Network error: The client or server timed out
waiting to receive data using TCP/IP. Check
network connections. Increase the
NetRetryCount and/or NetDelay values in
the essbase.cfg file. Update this file on both
client and server. Restart the client and try
again.
The server computer or client
computer cannot receive data
using a TCP/IP network
connection.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
Ensure that Essbase Server and the client are
running.
l
l
l
If Essbase Server receives this message,
ensure that the client you are trying to
connect to is running.
If a client receives this message, ensure
that the Essbase Server you are trying to
connect to is running.
If Essbase Server has frozen, stop
Essbase Server and follow the
procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the
standard methods, end the task (see
“Ending the Server Task” on page 126).
If you are spanning disk volumes, ensure that
you have enough space.
Determine whether the security file is corrupt.
Determine whether the database is corrupt
(see “Checking for Database Corruption” on
page 124).
1042018
Network error: Timed out waiting to send
message
Essbase cannot send all data
before timing out.
Increase the values for NETDELAY and
NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
1042019
Network error message: Cannot initialize
windows sockets
Essbase cannot initialize the
Windows sockets.
This is not an Essbase error message. Consult
the operating system documentation.
1042020
Network error message: Cannot initialize
windows sockets
Essbase cannot initialize the
Windows 3.0 sockets.
This is not an Essbase error message. Consult
the operating system documentation.
1042022
Network error message: Cannot Get Host
Name
Essbase cannot find the local
host name.
This is not an Essbase error message. Consult
the networking or operating system
documentation.
Ensure that the buffer that holds the returned
name is a valid address. Ensure that the
buffer size is a positive number.
1042023
Network Error: file descriptor limit per
process has been reached
Essbase has reached the file
descriptor limit. The file
descriptor limit determines
how many files an application
can open simultaneously.
Hyperion recommends that the file descriptor
limit (see “Checking the User Limit Profile” on
page 125) setting be 1024 files.
99
Message
Number
Message
Possible Cause
Possible Solution
1042024
Network Error: file descriptor limit in the
system has been reached
Essbase has reached the file
descriptor limit. The file
descriptor limit determines
how many files an application
can open simultaneously.
Hyperion recommends that the file descriptor
limit (see “Checking the User Limit Profile” on
page 125) setting be 1024 files.
1042025
Network error errorCode: Cannot Get Host
Address
The getpeername network
system call failed.
Consult the networking documentation to
determine the cause of the listed error code.
100 1040002 to 1042025: Network Messages
11
1051002 to 1055041: Agent
Messages
Table 11 lists Agent error and informational messages.
Table 11
Agent Messages 1051002 to 1055041
Message
Number
Message
Possible Cause
Possible Solution
1051002
Unrecognized command:
Most likely indicates a
version mismatch between
Essbase Server and client.
Ensure that the Essbase Server and client versions are
compatible.
Error error number
processing request name of
failed request -disconnecting
The request that failed.
Review your log, and find and correct the error that
precedes the failed request.
1051004
Logins are currently not
permitted
Maintenance is being
performed on the database
and logins are not permitted
during maintenance.
1051006
Disconnecting user user name
from application appName
You exited an application.
1051009
Setting application appName
active for user user name
You are logged on to an
application.
1051011
System timed out error
Most likely, too many users
are on the system, or there
may be other resource
constraints.
Try logging in later or see your Essbase system
administrator.
You are attempting to
perform maintenance or
administrative processes on
a user that does not exist.
Verify the user name.
command name
1051003
number
1051012
User user name does not exist
Requests generally fail due
to an error condition that
exists before the request is
issued.
Try logging in later or see your Essbase system
administrator.
Generally this occurs when
you log on to another
application.
You are attempting to log in
with an invalid user ID.
1051013
User/group user name/group
name does not exist
You are attempting to
perform maintenance or
administrative processes on
a user that does not exist.
Verify the user or group name.
101
Message
Number
Message
Possible Cause
Possible Solution
1051014
User/group user name/group
name already exists
You are attempting to create
a user or group with a name
already assigned to a user
or group.
Use another user name or group name.
1051016
Cannot rename yourself!
Your privileges are
insufficient to rename
yourself.
See your Essbase system administrator.
1051017
Cannot delete yourself!
Your privileges are
insufficient to delete
yourself.
See your Essbase system administrator.
1051018
Cannot rename to same name!
You are attempting to
change a user name to their
current name.
Use another user name.
1051019
Cannot alter your own access
level
Your privileges are
insufficient to alter your
access level.
See your Essbase system administrator.
1051020
Cannot log yourself out!
Message intended for
administrators.
See your Essbase system administrator.
Your privileges are
insufficient to log yourself
out.
1051021
You have been logged out due to
inactivity or explicitly by the
supervisor.
The system logged you off
because of extended
inactivity.
Log in to the system and resume your processes.
See your system administrator or supervisor.
Your system administrator
or supervisor has logged
you off.
1051022
Password too short -- must be at
least number characters
102 1051002 to 1055041: Agent Messages
The password you created
does not meet the minimum
number of characters. This
number is set by your
system administrator. The
default value is six.
Create a password that contains more characters.
Message
Number
Message
Possible Cause
Possible Solution
1052001
Error reading from server
Essbase cannot read from
Essbase Server, probably
because Essbase Server
was stopped incorrectly.
Determine whether Essbase Server is running:
Related
Topics
1006010
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
1052002
l
If Essbase Server is frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126).
Ensure that these environment variables are set correctly
(see “Setting Environment Variables” on page 123):
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
Ensure that Essbase Server and the Essbase client are
installed correctly.
If you just migrated, ensure that you followed the migration
information correctly. Check the Oracle Hyperion
Enterprise Performance Management System Installation
and Configuration Guide.
Increase the values for NETDELAY and NETRETRYCOUNT
(see “Setting NETDELAY and NETRETRYCOUNT” on page
125).
Determine whether the security file is corrupt.
If you are on a UNIX computer, check the user limit profile
(see “Checking the User Limit Profile” on page 125).
Determine whether any databases are corrupt (see
“Checking for Database Corruption” on page 124).
103
Message
Number
Message
Possible Cause
Possible Solution
1052002
Error writing to server
Essbase cannot write to
Essbase Server, probably
because Essbase Server
was stopped incorrectly.
Determine whether Essbase Server is running:
Related
Topics
1052001
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
l
If Essbase Server is frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126).
Ensure that the block size is within the recommended
range.
If you just migrated, ensure that you followed the migration
information correctly. Check the Oracle Hyperion
Enterprise Performance Management System Installation
and Configuration Guide.
Determine whether the security file is corrupt.
Ensure that disk space is adequate.
Determine whether any databases are corrupt (see
“Checking for Database Corruption” on page 124).
104 1051002 to 1055041: Agent Messages
Message
Number
Message
Possible Cause
Possible Solution
1052003
Timed out reading from server
Essbase timed out before it
could read from the server.
Ensure that the block size is within the recommended
range.
Ensure that these environment variables are set correctly
(see “Setting Environment Variables” on page 123):
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
Ensure that the network is functioning correctly. Check the
previous messages in the application log for network error
messages (see Chapter 10, “1040002 to 1042025:
Network Messages”).
Stop and restart Essbase Server.
Increase the values for NETDELAY and NETRETRYCOUNT
(see “Setting NETDELAY and NETRETRYCOUNT” on page
125).
Increase the values for AGENTDELAY.
1. If ESSBASEPATH/bin/essbase.cfg does not
exist on the server computer, create one using a text
editor.
2. In ESSBASEPATH/bin/essbase.cfg on the
server computer, add or increase the value for
AGENTDELAY.
3. Stop and restart Essbase Server.
Ensure that Essbase Server and the Essbase client are
installed correctly.
Determine whether any databases are corrupt (see
“Checking for Database Corruption” on page 124).
105
Message
Number
Message
Possible Cause
Possible Solution
1052004
Timed out writing to server
Essbase timed out before it
could write to the server.
Ensure that the block size is within the recommended
range.
Ensure that these environment variables are set correctly
(see “Setting Environment Variables” on page 123):
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
Ensure that the network is functioning correctly. Check the
previous messages in the application log for network error
messages (see Chapter 10, “1040002 to 1042025:
Network Messages”).
Stop and restart Essbase Server.
Increase the values for NETDELAY and NETRETRYCOUNT
(see “Setting NETDELAY and NETRETRYCOUNT” on page
125).
Increase the values for AGENTDELAY.
1. If ESSBASEPATH/bin/essbase.cfg does not
exist on the server computer, create one using a text
editor.
2. In ESSBASEPATH/bin/essbase.cfg on the
server computer, add or increase the value for
AGENTDELAY.
3. Stop and restart Essbase Server.
Ensure that Essbase Server and the Essbase client are
installed correctly.
Determine whether any databases are corrupt (see
“Checking for Database Corruption” on page 124).
1052005
You have been forced to
disconnect from the selected
application
106 1051002 to 1055041: Agent Messages
Essbase has no connection
to the selected application.
You might have been disconnected because you were
timed out, logged out by an administrator, or the
application stopped. Connect to the selected application
again.
Message
Number
Message
Possible Cause
Possible Solution
1053001
Cannot open object file:
fileName
Essbase cannot open the
listed file.
Ensure that your operating system privileges are correct
for the listed file and directory.
Related
Topics
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 to copy or delete the application
correctly.
1003022
Ensure that the block size is within the recommended
range.
Ensure that the file name (including the entire path) 256
characters or less. If the length exceeds 256 characters,
the file name is truncated in the error message.
See if another user has locked the file (see “Unlocking
Objects” on page 126).
Ensure that the file exists. If the file does not exist, restore
the file from backups.
Ensure that memory is adequate.
If the listed file is essbase.sec:
l
Ensure that the security file is not read-only at the
operating system level.
l
Ensure that the security file is not corrupt.
If you are using the BEGINARCHIVE command, specify a
directory for the archive.
Stop and restart Essbase Server.
1053002
Cannot create application
directory: directoryName
operatingSystemErrorCode
Essbase cannot create the
listed application directory.
Ensure that your operating system privileges are correct
for the listed file and directory.
Ensure that disk space is adequate.
Ensure that these environment variables are set correctly
(see “Setting Environment Variables” on page 123):
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
107
Message
Number
Message
Possible Cause
Possible Solution
1053003
Application directory does not
exist: directoryName
Essbase cannot find the
listed application directory.
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 to copy or delete the application
correctly.
Ensure that the directory exists in the correct location.
Ensure that your operating system privileges are correct
for the listed directory.
See if another user has locked the directory (see
“Unlocking Objects” on page 126).
Ensure that these environment variables are set correctly
(see “Setting Environment Variables” on page 123):
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
Ensure that the security file is not corrupt.
If you are using ESSCMD, ensure that the correct
application directory is specified in the ESSCMD
command.
1053004
Cannot create database
directory: directoryName
operatingSystemErrorCode
Essbase cannot create the
listed database directory.
Ensure that your operating system privileges are correct
for the listed file and directory.
Ensure that disk space is adequate.
Ensure that these environment variables are set correctly
(see “Setting Environment Variables” on page 123):
108 1051002 to 1055041: Agent Messages
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
Message
Number
Message
Possible Cause
Possible Solution
1053005
Database directory does not
exist: directoryName
Essbase cannot find the
listed database directory.
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 to copy or delete the application
correctly.
Ensure that the directory exists in the correct location.
Ensure that your operating system privileges are correct
for the listed directory.
See if another user has locked the directory (see
“Unlocking Objects” on page 126).
Ensure that these environment variables are set correctly
(see “Setting Environment Variables” on page 123):
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
Ensure that the security file is not corrupt.
If you are using ESSCMD, ensure that the correct
application directory is used in the ESSCMD command.
1053006
Invalid object type
Essbase cannot open the
object because it is not a
recognized type. Essbase
recognizes Essbase objects,
such as applications,
outlines, database files,
alias tables, rules files, and
linked reporting objects.
Essbase also recognizes
some external objects, such
as spreadsheet files.
Ensure that Essbase Server and the client (such as
Spreadsheet Add-in) are at the same release level.
1053007
Cannot rename object
originalName to newName
Essbase cannot rename the
listed object.
Ensure that your operating system privileges are correct
for the listed object.
Ensure that the new name is valid.
Ensure that an object using the new name does not exist.
1053008
Cannot create object
objectName
The operating system is not
allowing Essbase to create
the listed object.
Ensure that your operating system privileges are correct
for the listed object.
Ensure that the object name is valid.
Ensure that the object name (including the entire path) is
not more than 256 characters. If it is longer than 256
characters, the object name is truncated in the error
message.
1053009
Cannot delete object
objectName
The operating system is not
allowing Essbase to delete
the listed object.
Ensure that your operating system privileges are correct
for the listed object.
Ensure that the object name is valid.
109
Message
Number
Message
Possible Cause
Possible Solution
1053010
Object objectName is already
locked by user userName
The object you are trying to
lock is locked by the listed
user.
Wait a few minutes to allow the other active user's process
to finish and retry the operation.
If necessary, unlock the file (see “Unlocking Objects” on
page 126).
If this error happens frequently, ensure that users are
logging off Essbase correctly.
Stop and restart Essbase Server.
1053011
Object objectName is not locked
by user userName
Essbase cannot unlock the
listed object because it is
not locked.
See if another user has locked the file (see “Unlocking
Objects” on page 126).
Stop and restart Essbase Server.
Determine whether the database is corrupt (see “Checking
for Database Corruption” on page 124).
1053012
Object objectName is locked by
user userName
The listed object is locked
by the listed user.
Wait a few minutes to allow the other active user's process
to finish and retry the operation.
If necessary, unlock the file (see “Unlocking Objects” on
page 126).
If this occurs frequently, ensure that users are logging off
Essbase correctly.
Stop and restart Essbase Server.
1053013
Object objectName unlocked by
user userName
The listed object was
unlocked by the listed user.
Not applicable
1053014
Object objectName does not
exist
Essbase cannot find the
listed object.
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 you are using partitions, ensure that the listed file exists
at the source and at the target.
Determine whether the security file is corrupt.
Ensure that disk space is adequate.
1053015
Object objectName already
exists
Essbase cannot create the
listed object because it
exists.
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.
1053016
Cannot open temporary file
Essbase cannot open a
temporary file to save the
security file.
Ensure that disk space is adequate.
110 1051002 to 1055041: Agent Messages
Ensure that your operating system privileges are correct.
Message
Number
Message
Possible Cause
Possible Solution
1053017
Cannot open log file for
application appName
Essbase cannot open the
application log file for the
listed application.
Ensure that your operating system privileges are correct
for the listed application.
Make yourEssbase permissions are correct for the listed
file.
Ensure that disk space is adequate.
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.
1053018
Operation not permitted on
outline objects
Essbase cannot perform the
operation on outline
objects.
You cannot delete, copy, or rename an outline. Instead
you must delete, copy, or rename the database.
1053019
Cannot rename directory:
oldDirectoryName
operatingSystemErrorCode
Essbase cannot rename the
listed directory.
See if another user has locked the file (see “Unlocking
Objects” on page 126).
Ensure that the new directory name does not match an
existing directory name.
Make your operating system privileges are correct for the
old and new directories.
Ensure that yourEssbase permissions are correct for the
listed old directory.
Determine whether the security file is corrupt.
Stop and restart the application. If that does not work,
stop and restart Essbase Server.
Ensure that disk space is adequate.
Close Windows Explorer. Sometimes Explorer can hold the
directory open, which can lead to the error.
If the suggested solutions do not work, create a new
application and database and copy the outline and other
objects to the new application and database. When you
are finished, ensure that the new application and
database are not corrupt (see “Checking for Database
Corruption” on page 124).
Ensure that the OLAP Server is running.
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
l
If Essbase Server is frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126).
111
Message
Number
Message
Possible Cause
Possible Solution
1053020
Error writing file: fileName
Essbase cannot write the
listed file.
Ensure that disk space is adequate. If disk space is
insufficient , consider spanning disk volumes.
Ensure that virtual memory is two to three times larger
than physical memory.
If the listed file is essbase.sec, determine whether the
security file is corrupt.
1053021
Cannot copy object
objectName to itself
Essbase cannot copy the
listed object to itself.
Check the syntax of the ESSCMD commands.
1053022
Database databaseName is in
read-only mode for backup
The listed database is in
read-only mode because
the administrator issued the
BEGINARCHIVE command
to back up the database.
Wait until the archival process, starting with the
BEGINARCHIVE command and ending with the
ENDARCHIVE command, is finished. If the archival
process has finished, be sure to issue the ENDARCHIVE
command.
1053023
User's log message:
messageText
You created this message
using EssWriteToLogFile.
Not applicable
1053024
Cannot create temporary file
Essbase cannot open a
temporary file. Essbase
needs to open the
temporary file to create an
object, such as a rules file,
before saving the object to
the remote Essbase Server
computer.
Ensure that disk space is adequate.
112 1051002 to 1055041: Agent Messages
Ensure that your operating system privileges are correct
to create the temporary file.
If you are on a UNIX computer and are using the
TMPDIR environment variable, ensure that the full path
to the TMPDIR directory does not exceed 15 characters.
Message
Number
Message
Possible Cause
Possible Solution
1054001
Cannot load application
appName with error number
number - see server log file
Essbase cannot load the
listed application because
of the listed error.
Check the Essbase Server log for more details about the
listed error.
Determine whether the listed application is corrupt (see
“Checking for Database Corruption” on page 124) .
Increase the values for NETDELAY and NETRETRYCOUNT
(see “Setting NETDELAY and NETRETRYCOUNT” on page
125).
Ensure that the block size is within the recommended
range.
Ensure that these environment variables (see “Setting
Environment Variables” on page 123) are set correctly:
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
Ensure that Essbase Server and the Essbase client are
installed correctly.
Run REGISTER.EXE again to ensure that ports are
activated. Consult the Oracle Hyperion Enterprise
Performance Management System Installation and
Configuration Guide.
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.
1054002
Related
Topics
Loading application appName is
not currently permitted
Essbase cannot load the
listed application.
Delete all essXXXX.tmp files in the ARBORPATH/app/
appName/databaseName directory.
1054009
Determine whether the database is corrupt (see “Checking
for Database Corruption” on page 124).
1054011
1054003
In Administration Services, ensure that “Allow users to
start application” is selected.
Error number loading
application: appName
Essbase cannot load the
listed application.
Stop and restart Essbase Server.
Copy the ARBORPATH/app/appName/
databaseName/databaseName.dbb file to
ARBORPATH/app/appName/databaseName/
databaseName.db.
Determine whether the database is corrupt (see “Checking
for Database Corruption” on page 124).
Run only one application at a time.
Delete the ARBORPATH/app/appName/
databaseName/databaseName.esm file, stop and
restart Essbase Server, and try to open the application
again.
113
Message
Number
Message
Possible Cause
Possible Solution
1054004
Application appName is not
loaded
Essbase tried to perform an
operation on the listed
application, but the
application was not loaded.
Ensure that you load an application before you use it.
1054005
Shutting down application
appName
Essbase shut down the
listed application.
Not applicable
1054006
Cannot terminate application
appName
Essbase cannot stop the
listed application.
Ensure that Essbase Server is running.
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
l
1054007
Application appName not
responding
Essbase cannot connect to
the listed application.
If Essbase Server is frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126).
Ensure that Essbase is installed correctly. If necessary,
reinstall Essbase.
Ensure that these environment variables (see “Setting
Environment Variables” on page 123) are set correctly:
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
Stop and restart Essbase Server.
Ensure that the block size is in the recommended range.
Increase the data cache size to hold at least 100 blocks.
Increase the values for NETDELAY and NETRETRYCOUNT
(see “Setting NETDELAY and NETRETRYCOUNT” on page
125).
Check for the ARBORPATH/app/appName/
databaseName/databaseName.db file. If
databaseName.db does not exist, rename the
databaseName.dbb file to databaseName.db.
Check for the ARBORPATH/app/appName/
databaseName/databaseName.app file. If
databaseName.app file does not exist, rename the
databaseName.apb file to databaseName.app.
Determine whether the database is corrupt (see “Checking
for Database Corruption” on page 124).
114 1051002 to 1055041: Agent Messages
Message
Number
Message
Possible Cause
Possible Solution
1054009
Application appName is
currently not accepting
connections.
Users cannot log on to the
listed application.
In Administration Services, ensure that “Allow
Connections” is selected.
1054010
Application appName is
currently not accepting user
commands
The listed application is
performing an operation
that requires exclusive
control, such as a
calculation.
Not applicable
1054011
Loading database
databaseName is not currently
permitted
Essbase cannot load the
listed database.
In Administration Services, ensure that “Allow Database
to Start” is selected.
Invalid syntax in filter line
incorrectFilter
The security filter had a
syntax error.
Ensure that you created the filter correctly.
Syntax error loading filters operation canceled
Essbase cannot load the
security filters.
Ensure that you created the filters correctly.
1054014
Database databaseName
loaded
The listed database loaded
correctly.
Not applicable
1054016
Invalid file name fileName.
operation aborted
Essbase cannot create the
listed index or page file. This
error occurs when Essbase
tries to create the nth index
or page file for an
application where n is
greater than 5 digits, that is,
greater than 99999.
Contact Oracle Support.
1054017
Cannot read from file with
handle number, operation failed
Essbase cannot perform the
listed operation.
Determine whether the database is corrupt (see “Checking
for Database Corruption” on page 124).
Related
Topics
In ESSCMD, ensure that you are using the ENABLELOGIN
command correctly.
1054002
1054011
Related
Topics
1054002
1054009
1054012
Related
Topics
1054013
1054013
Related
Topics
1054012
115
Message
Number
Message
Possible Cause
Possible Solution
1054018
RECEIVED ABNORMAL
SHUTDOWN COMMAND ESSBASE TERMINATING
Essbase shut down
because it received an
invalid shutdown
command.
Do not close the Essbase Server window by clicking the
"X" in the title bar.
Ensure that the Essbase computer has enough resources.
Consult the Oracle Hyperion Enterprise Performance
Management System Installation Start Here for 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.
After you restart Essbase Server, determine whether the
database is corrupt (see “Checking for Database
Corruption” on page 124).
1054019
Cannot modify settings for
application appName while
application is loaded and user
who has modified the settings is
logged in
Essbase cannot modify the
settings for the listed
application.
1054020
*** Missing command line
password!
Essbase cannot start
because the command line
password was not issued.
When you start Essbase to run in the background (using
the -b switch), ensure that you enter the system password
on the command line.
1054021
Cannot modify settings for
application appName. See
server log for more information
The listed application was
not loaded.
Issue the UNLOADAPP and LOADAPP commands before
the ENABLELOGIN command.
1054022
Cannot copy application
appName while database
databaseName is in archive or
read only mode
The database was in readonly mode because
someone was archiving the
database.
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 to issue the ENDARCHIVE
command.
1054023
Cannot modify settings for
application appName while
database databaseName is in
archive or read only mode
The database was in readonly mode because
someone was archiving the
database.
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 to issue the ENDARCHIVE
command.
1054025
Cannot rename application
appName while database
databaseName is in archive or
read only mode
The database was in readonly mode because
someone was archiving the
database.
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 to issue the ENDARCHIVE
command.
1054026
Cannot create a new database
in application appName while
database databaseName is in
archive or read only mode
The database was in readonly mode because
someone was archiving the
database.
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 to issue the ENDARCHIVE
command.
116 1051002 to 1055041: Agent Messages
1. Log off other users.
2. Unload the application.
3. Reload the application.
4. Change the settings. Ensure that you are using the
SETAPPSTATE command correctly.
See appName.log.
Message
Number
Message
Possible Cause
Possible Solution
1054027
Application appName started
with process id number
Process ID assigned to the
listed application by the
operating system.
Not applicable
1054029
Invalid parameter values for
database file information
request.
The API or ESSCMD
command did not supply
enough information about
the Essbase database.
Ensure that each ESSCMD command or API command
contains correct information.
Select for application appName
failed, error number
Essbase cannot select the
listed application.
Ensure that you are using the SELECT command correctly.
1054030
Ensure that each ESSCMD command or API command
contains all required parameters.
Ensure that the listed application is running and that you
can select it from Oracle Essbase Administration Services.
If not, ensure that Essbase Server is running on the listed
computer.
l
If Essbase Server is not running, restart Essbase
Server.
l
If Essbase Server crashed, follow the procedures for
an abnormal shutdown.
l
1055041
Cannot create daemon thread.
The agent cannot initialize
the daemon thread or one of
its internal threads.
If Essbase Server is frozen, stop Essbase Server and
follow the procedures for an abnormal shutdown. If
you cannot stop Essbase Server using the standard
methods, end the task (see “Ending the Server Task”
on page 126).
Restart your process.
Available memory is
insufficient to initialize the
process.
117
118 1051002 to 1055041: Agent Messages
12
1120000 to 1120002: C Grid API
Messages
Table 12 lists C Grid API error and informational messages.
Table 12
C Grid API Messages 1120000 to 1120002
Message
Number
Message
Possible Cause
Possible Solution
1120000
Unable to lock file
fileName.
Essbase cannot lock
the listed file to
perform operations
on it. This usually
occurs when
Essbase cannot find
the file or the user
does not have
permission to write
to the file.
Ensure that Essbase can find the listed file.
Ensure that the listed file name and path name are correct. Check for
misspellings.
If you are using ESSCMD, ensure that the listed file has the correct
capitalization and spelling.
If you are using IMPORT ESSCMD, ensure that you are using the IMPORT
command correctly. When you issue the IMPORT command, there are four
options for the data file location.
1 (local/client object): Ensure that the data file is in the client folder.
Ensure that you have read access to the data file. On UNIX, the file name
is case-sensitive, so check capitalization.
2 (remote server object): Ensure that you have read access to the data
file. On UNIX, the file name is case-sensitive, so check capitalization.
3 (file): Ensure that you specified the absolute path name and the full file
name (including the file type extension).
4 (SQL): Check the ODBC connections. Ensure that Essbase Server is
properly configured.
Ensure that Essbase can use the listed file.
See if the file is locked (see “Unlocking Objects” on page 126).
Ensure that you have the correct Essbase permissions for the listed file.
Ensure that you have the correct operating system privileges for the listed
file and the drive you are writing it to.
Ensure that disk space is adequate.
Ensure that the listed file is not corrupt (see “Checking for Database
Corruption” on page 124).
Determine whether the security file is corrupt.
If an operation did not complete, perform recovery procedures. Then
determine whether the database is corrupt .
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.
119
Message
Number
Message
Possible Cause
1120000
continued
Possible Solution
If you are using disk volumes, check these items:
l
Ensure that the DISKVOLUMES setting in the ESSBASEPATH/bin/
essbase.cfg file is correct.
l
Ensure that the user spanning the disk volumes has the correct
operating system privileges for the drive.
l
After you change the DISKVOLUMES setting, stop and restart Essbase
Server. If someone changed the DISKVOLUMES setting without
stopping and starting Essbase Server, determine whether the database
is corrupt.
If the Essbase Server is on a computer running UNIX, check these items:
l
Ensure that the file descriptor limit (see “Checking the User Limit
Profile” on page 125) is set correctly.
l
Ensure that the root partition space is adequate.
l
Ensure that capitalization of the listed file is correct.
1120001
Unable to unlock
physical memory
allocated by the
Essbase Kernel for
database
databaseName.
Essbase cannot
unlock the physical
memory allocated by
the Essbase kernel
for the listed
database.
Turn off cache memory locking. If the problem persists, contact Oracle
Support.
1120002
Unable to clear data
while the database
databaseName is in
readonly mode for
backup.
Essbase cannot
clear the database
because the
database is in readonly mode.
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 Ensure
that the archive process is completed before the next process begins.
120 1120000 to 1120002: C Grid API Messages
13
1130203 to 1130613:
Miscellaneous Messages
Table 13 lists miscellaneous error and informational messages.
Table 13
Miscellaneous Messages 1130203 to 1130613
Message
Number
Message
1130203
Essbase is
unable to
allocate
memory.
Related
Topics
1006006
Possible
Cause
Possible Solution
Try any of these suggestions to fix the problem. After you fix the problem, determine
whether the database is corrupt (see “Checking for Database Corruption” on page
124).
l
1006010
1006015
1006023
l
If you are on a UNIX computer, check the user limit profile (see “Checking the
User Limit Profile” on page 125).
l
Check the block size of the database. If necessary, reduce the block size.
l
Check the data cache and data file cache setting. If necessary, decrease the
data cache and data file cache sizes.
l
1130404
Related
Topics
Essbase timed
out while trying
to perform an
operation.
Ensure that the Essbase computer has enough resources. Consult the Oracle
Hyperion Enterprise Performance Management System Installation Start Here
for 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.
First, check the messages that occurred just before this message to see if you can
find additional problems. Then try these items:
l
Increase the values for NETDELAY and NETRETRYCOUNT (see “Setting NETDELAY
and NETRETRYCOUNT” on page 125).
l
Stop and restart Essbase Server.
l
Determine whether the database is corrupt (see “Checking for Database
Corruption” on page 124).
l
Do not close the Essbase Server window by clicking the "X" in the title bar.
1042006
1042017
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.
l
l
Ensure that the Essbase computer has enough resources. Consult the Oracle
Hyperion Enterprise Performance Management System Installation Start Here
for 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 ensure that the ports are activated. Consult the
Oracle Hyperion Enterprise Performance Management System Installation and
Configuration Guide.
121
Message
Number
Message
1130409
This is an internal
error.
Contact Oracle Support.
1130410
This is an internal
error.
Contact Oracle Support.
1130610
Essbase cannot
open a file.
Related
Topics
1003022
Possible
Cause
Ensure that
you are
using the
ESSCMD
IMPORT
command
correctly.
Possible Solution
Put all files the ESSCMD script needs in the ARBORPATH/app/appName/
databaseName directory.
Run the ESSCMD script from the ARBORPATH/app/appName/databaseName
directory.
Check the ESSCMD script for invalid paths. Ensure that every folder that the script
is pointing to exists.
If you are using an error file, ensure that the error file is being created in a directory
that exists.
1130612
Essbase could
not close a file.
Stop and restart Essbase Server.
1130613
Essbase cannot
read from a file.
Check the syntax of ESSCMD commands that access files on a remote server, such
as the IMPORT command.
Related
Topics
1003022
122 1130203 to 1130613: Miscellaneous Messages
Ensure that the file is not corrupt.
Referenced Procedures
A
In This Appendix
Setting Environment Variables .......................................................................... 123
Checking for Database Corruption ..................................................................... 124
Fixing Database Corruption ............................................................................. 124
Replacing Database Files with Backups ............................................................... 125
Checking the User Limit Profile ......................................................................... 125
Setting NETDELAY and NETRETRYCOUNT .............................................................. 125
Ending the Server Task .................................................................................. 126
Unlocking Objects........................................................................................ 126
Determining Operating System Privileges.............................................................. 126
Setting Environment Variables
Ensure that these environment variables are set correctly:
l
ARBORPATH (PC and UNIX)
l
ESSBASEPATH (PC and UNIX)
l
PATH (PC and UNIX)
l
LD_LIBRARY_PATH (UNIX only)
If Essbase is installed in the default location, use these variable settings:
l
Windows:
PATH=C:/Hyperion/products/Essbase/EssbaseServer/bin
ARBORPATH=C:/Hyperion/products/Essbase/EssbaseServer/app
ESSBASEPATH=C:/Hyperion/products/Essbase/EssbaseServer
l
UNIX:
path=/home/hyperion/products/essbase/essbaseserver/binARBORPATH=/home/hyperion/
products/essbase/essbaseserver/appESSBASEPATH=/home/hyperion/products/essbase/
essbaseserverLD_LIBRARY_PATH=$ARBORPATH/bin:$ARBORPATH/dlls:$ARBORPATH/api/lib
arbormsgpath=/home/hyperion/essbase/bin
For other environment variables, see the Oracle Hyperion Enterprise Performance Management
System Installation Start Here.
Setting Environment Variables 123
Checking for Database Corruption
ä To check if the database is corrupt:
1
Issue the VALIDATE command in ESSCMD.
2
If the VALIDATE command has errors, fix the corrupt database (see “Fixing Database Corruption” on
page 124).
3
If the VALIDATE command does not have errors, check the application log for Invalid Block Header and
AVL Tree errors.
4
If the application log contains Invalid Block Header or AVL Tree errors, the database is corrupt. Fix the
corrupt database (see “Fixing Database Corruption” on page 124).
5
If no Invalid Block Header or AVL Tree errors exist, the database is not corrupt. Back up the database.
Fixing Database Corruption
ä To fix a corrupt database:
1
Clear the database.
2
Reload from backups.
3
Recalculate the data.
4
Issue the VALIDATE command in ESSCMD.
ä If the database is still corrupt:
1
Stop Essbase Server.
2
Delete these files:
3
l
ARBORPATH/app/appName/databaseName/databaseName.esm
l
ARBORPATH/app/appName/databaseName/databaseName.ind
l
ARBORPATH/app/appName/databaseName/databaseName.tct
l
ARBORPATH/app/appName/databaseName/essXXXXX.ind
l
ARBORPATH/app/appName/databaseName/essXXXXX.pag
If any of these temporary files are present, delete them:
l
ARBORPATH/app/appName/databaseName/databaseName.esn
l
ARBORPATH/app/appName/databaseName/databaseName.inn
l
ARBORPATH/app/appName/databaseName/databaseName.otm
l
ARBORPATH/app/appName/databaseName/databaseName.otn
l
ARBORPATH/app/appName/databaseName/databaseName.tcu
l
ARBORPATH/app/appName/databaseName/essXXXXX.inn
l
ARBORPATH/app/appName/databaseName/essXXXXX.pan
124 Referenced Procedures
l
ARBORPATH/app/appName/databaseName/essXXXXX.tmp
4
Create a new application and database.
5
Reload from backups.
6
Recalculate the new database.
7
Restart Essbase Server.
Replacing Database Files with Backups
ä To replace a database file with its backup:
1
Stop Essbase Server.
2
Rename databaseName.db to databaseNamedb.old, and then rename
databaseName.dbb to databaseName.db.
3
Restart Essbase Server.
Checking the User Limit Profile
If you are on a UNIX computer using the Korn shell, check the user limit profile using the
ulimit -a command. If you are using another shell, check the flags for the limit command
by typing man limit or man ulimit.
l
Set data to unlimited using the ulimit -d unlimited command.
l
Set virtual memory to unlimited using the ulimit -v unlimited command.
l
l
Set the file descriptor limit to at least 1024 using the ulimit -n 1024 command. If possible,
set the file descriptor limit to unlimited.
Add these statements to the .profile or .cshrc file.
Setting NETDELAY and NETRETRYCOUNT
Increasing the values for NETDELAY and NETRETRYCOUNT can solve network problems.
ä To set NETDELAY and NETRETRYCOUNT:
1
If ESSBASEPATH/bin/essbase.cfg does not exist on the server and client computers, create it
using a text editor.
2
In the ESSBASEPATH/bin/essbase.cfg file on the server and client computers, set NETDELAY
to at least 800.
3
In the ESSBASEPATH/bin/essbase.cfg file on the server and client computers, set
NETRETRYCOUNT to at least 1000.
4
Stop and restart Essbase Server.
Replacing Database Files with Backups 125
Ending the Server Task
If you cannot stop Essbase Server using the standard method:
l
l
Windows—Use Task Manager to end the Essbase Server task. Consult the Windows
documentation.
UNIX—Check for the ESSSVR process:
ps -ef |grep ESS
Kill the process:
kill -9 process id
Consult the operating system documentation.
After you end the server task, follow the procedures for an abnormal shutdown.
Unlocking Objects
Users lock objects while performing some operations on them.
If an object that you need is locked, try these solutions, in order.
1. Wait for the user request to finish normally.
2. Check to see which users have requests running. If necessary, terminate those requests.
3. Check to see which users have objects locked. If necessary, unlock those objects at the client.
4. If this does not solve the problem, unlock the object at the server.
a. In the Agent window, use the DUMP command to get a list of locked objects. If you are
on a UNIX platform, you must run Essbase in the foreground.
b. Open the text file generated by the DUMP command. Information about locks is at the
end of the file in the Locked Objects section.
c. Unlock objects not currently being used.
5. If the object remains locked, stop and restart Essbase Server.
Determining Operating System Privileges
The Essbase Agent must be assigned the correct operating system privileges to run, regardless
of the privileges of the user who starts the Agent.
If the Agent is not assigned the correct privileges, change the privileges using the operating system
or reinstall Essbase using the correct privileges.
On UNIX:
If Essbase is running on a UNIX computer, the Agent runs as the ESSSVR process. The ESSSVR
process must have root privileges.
126 Referenced Procedures
ä To check privileges, in the ESSBASEPATH/bin directory, enter ls -l ESSBASE.
The file should have these read, write, and execute privileges:
159749 -rwxr-xr-x
1 essbase staff
730168 Aug 31 05:06 ESSBASE
On Windows:
If Oracle Essbase is installed on a Windows computer, the Agent runs as the essbase.exe
process, which must be assigned Administrator privileges.
ä To check privileges:
1
In ESSBASEPATH/bin, select essbase.exe, right click and select Properties to open the
essbase.exe dialog box.
2
In the essbase.exe dialog box, click Security.
3
On Security, click Advanced, to open Access Control Settings.
4
In Access Control Settings, click Owner.
5
Verify that Owner is set to Administrator.
Determining Operating System Privileges 127
128 Referenced Procedures
A
C
D
E
F
L
M
N
O
P
R
S
U
V
Index
Numbers
1002112, 11
1002122, 11
1003000, 19
1003001, 20
1003003, 21
1003004, 21
1003005, 21
1003006, 21
1003007, 21
1003008, 22
1003010, 22
1003011, 22
1003012, 22
1003013, 22
1003014, 23
1003015, 24
1003022, 25
1003023, 25
1003024, 26
1003025, 26
1003027, 27
1003028, 27
1003029, 28
1003030, 28
1003031, 29
1003032, 29
1003034, 29
1003035, 29
1003036, 29
1003037, 30
1003038, 30
1003039, 30
1003040, 30
1003041, 30
1003048, 30
1003055, 11
1006002, 31
1006004, 31
1006006, 32
1006010, 32
1006015, 32
1006016, 32
1006023, 33
1006025, 33
1006026, 33
1006027, 33
1006028, 33
1006029, 33
1006030, 33
1006031, 33
1006032, 33
1006034, 34
1006035, 34
1006036, 34
1006037, 34
1006039, 34
1006040, 34
1006041, 34
1006042, 34
1006043, 34
1006044, 35
1006045, 35
1006046, 35
1006047, 35
1006048, 35
1006049, 35
1006050, 35
1006051, 35
1006052, 35
1006053, 36
1006054, 36
1006055, 36
1006056, 36
1006057, 36
1008001, 37
Index 129
A
1008006, 37
1008009, 37
1008010, 37
1008021, 38
1008022, 38
1008023, 38
1008024, 38
1008025, 38
1008028, 38
1008029, 38
1008030, 38
1008031, 38
1008036, 38
1008037, 38
1008039, 38
1008089, 39
1008090, 39
1008091, 39
1008092, 39
1008093, 39
1008099, 39
1008100, 39
1008101, 39
1008106, 40
1008107, 41
1008108, 42
1008109, 42
1008110, 42
1008111, 43
1008112, 43
1008113, 43
1008114, 43
1008115, 43
1008116, 43
1008117, 43
1008118, 43
1008119, 43
1008120, 44
1008121, 44
1008122, 44
1008123, 44
1008124, 44
1008125, 44
1008126, 44
1008127, 44
1008128, 45
1008129, 45
130 Index
C
D
E
F
L
M
N
O
P
R
1008130, 45
1008131, 46
1008132, 46
1008133, 46
1008134, 46
1008135, 47
1008136, 47
1008137, 47
1008138, 47
1008139, 47
1008140, 47
1008141, 47
1008142, 47
1008143, 48
1008144, 48
1008145, 48
1008146, 48
1008147, 48
1008148, 48
1008149, 48
1008150, 48
1008151, 48
1008152, 49
1012000, 51
1012001, 51
1012004, 52
1012005, 52
1012009, 52
1012010, 52
1012011, 52
1012012, 53
1012013, 53
1012015, 53
1012016, 53
1012017, 53
1012018, 53
1012019, 54
1012021, 54
1012023, 54
1012024, 54
1012025, 54
1012026, 55
1012027, 55
1012028, 55
1012029, 55
1012030, 55
1012031, 55
S
U
V
A
1012032, 55
1012033, 55
1012034, 55
1012035, 55
1012036, 56
1012037, 56
1012038, 56
1012039, 56
1012040, 56
1012041, 56
1012042, 56
1012043, 57
1012044, 57
1012045, 57
1012046, 57
1012047, 57
1012048, 57
1012049, 57
1012050, 57
1012051, 57
1012052, 58
1012053, 58
1012054, 58
1012055, 58
1012061, 58
1012062, 58
1012063, 58
1012106, 58
1012121, 59
1012134, 59
1012135, 59
1012136, 59
1012137, 59
1012139, 59
1012141, 59
1012142, 59
1012143, 60
1012500, 60
1012501, 60
1012550, 60
1012551, 60
1012552, 60
1012553, 60
1012554, 60
1012555, 60
1012556, 61
1012557, 61
C
D
E
F
L
M
N
O
P
R
S
U
V
1012558, 61
1012559, 61
1012560, 61
1012561, 61
1012562, 61
1012563, 61
1012564, 62
1012566, 62
1012567, 62
1012568, 62
1012569, 62
1012570, 62
1012571, 62
1012600, 63
1012667, 63
1012668, 63
1012669, 63
1012670, 63
1012671, 63
1012672, 63
1012674, 63
1012675, 63
1012676, 63
1012677, 64
1012678, 64
1012679, 64
1012680, 64
1012681, 64
1012682, 64
1012683, 65
1012684, 65
1012700, 65
1012701, 65
1012702, 65
1012703, 65
1012704, 66
1012706, 66
1012708, 66
1012709, 66
1012710, 66
1012711, 66
1012712, 66
1012713, 67
1012714, 67
1012715, 67
1012716, 67
1012717, 67
Index 131
A
1012718, 67
1012727, 67
1012733, 68
1012734, 68
1012735, 68
1012736, 69
1012737, 69
1012738, 70
1012739, 70
1012740, 71
1012741, 71
1012742, 71
1012750, 71
1013009 , 73
1013101, 11
1013136, 73
1013294, 12
1014004, 75
1014018, 75
1014025, 75
1014026, 75
1014027, 76
1014028, 76
1014031, 76
1014032, 77
1014033, 77
1014034, 77
1014035, 77
1014036, 77
1014039, 77
1014040, 78
1014041, 78
1014042, 78
1014043, 78
1019002, 80
1019003, 81
1019004, 82
1019005, 83
1019006, 83
1019007, 83
1019008, 83
1019009, 83
1019010, 83
1019011, 83
1019012, 83
1019013, 84
1019014, 84
132 Index
C
D
E
F
L
M
N
O
P
R
1019015, 84
1019017, 84
1019018, 84
1019019, 84
1019020, 84
1019021, 84
1019022, 84
1019024, 84
1019025, 84
1019026, 85
1019028, 85
1019031, 85
1019032, 85
1019034, 86
1019035, 86
1019036, 86
1019037, 86
1019038, 86
1019039, 86
1019040, 87
1019041, 88
1019042, 88
1019043, 88
1019044, 88
1019045, 89
1019046, 89
1019047, 89
1019048, 89
1019049, 89
1019050, 89
1019051, 89
1019052, 89
1019053, 89
1019054, 89
1019056, 89
1023057, 11
1040002, 91
1040003, 91
1040004, 91
1040006, 91
1040007, 91
1040008, 92
1040010, 92
1040011, 92
1040012, 92
1040013, 92
1040014, 92
S
U
V
A
1040015, 92
1040016, 92
1040017, 92
1040018, 92
1040019, 92
1041000, 92
1041002, 93
1041003, 93
1041004, 93
1041005, 93
1041006, 93
1041007, 93
1041008, 94
1041009, 94
1041011, 94
1041012, 94
1041013, 94
1041014, 94
1042002, 94
1042003, 95
1042004, 95
1042006, 96
1042007, 96
1042008, 96
1042009, 97
1042010, 97
1042011, 97
1042012, 98
1042013, 98
1042015, 98
1042017, 99
1042018, 99
1042019, 99
1042020, 99
1042022, 99
1042023, 99
1042024, 100
1042025, 100
1051002, 101
1051003, 101
1051004, 101
1051006, 101
1051009, 101
1051011, 101
1051012, 101
1051013, 101
1051014, 102
C
D
E
F
L
M
N
O
P
R
S
U
V
1051016, 102
1051017, 102
1051018, 102
1051019, 102
1051020, 102
1051021, 102
1051022, 102
1052001, 103
1052002, 104
1052003, 105
1052004, 106
1052005, 106
1053001, 107
1053002, 107
1053003, 108
1053004, 108
1053005, 109
1053006, 109
1053007, 109
1053008, 109
1053009, 109
1053010, 110
1053011, 110
1053012, 110
1053013, 110
1053014, 110
1053015, 110
1053016, 110
1053017, 111
1053018, 111
1053019, 111
1053020, 112
1053021, 112
1053022, 112
1053023, 112
1053024, 112
1054001, 113
1054002, 113
1054003, 113
1054004, 114
1054005, 114
1054006, 114
1054007, 114
1054009, 115
1054010, 115
1054011, 115
1054012, 115
Index 133
A
1054013, 115
1054014, 115
1054016, 115
1054017, 115
1054018, 116
1054019, 116
1054020, 116
1054021, 116
1054022, 116
1054023, 116
1054025, 116
1054026, 116
1054027, 117
1054029, 117
1054030, 117
1055041, 117
1060145, 12
1060147, 12
1060149, 12
1060172, 12
1060175, 12
1060180, 12
1120000, 119
1120001, 120
1120002, 120
1130203, 121
1130404, 121
1130409, 122
1130410, 122
1130610, 122
1130612, 122
1130613, 122
1150085, 13
1150086, 13
1150090, 13
1150091, 13
1241164, 13
1270001, 13
1270004, 13
1270005, 14
1270006, 14
1270009, 14
1270011, 14
1270018, 15
1270022, 15
1270024, 15
1270030, 15
134 Index
C
D
E
F
L
M
N
O
P
R
S
U
V
1270032, 15
1270035, 15
1270036, 15
1270039, 15
1270040, 16
1270041, 16
1270044, 16
1270047, 16
1270049, 16
1270052, 16
1270054, 16
1270057, 16
1270058, 16
1270059, 17
1270060, 17
1270063, 17
1270069, 17
1270070, 17
1270071, 18
1270082, 18
1270506, 18
1270517, 18
1270526, 18
1270527, 18
A
Agent messages, 101
aggregate storage messages, 11
application logs
message categories, 7
C
C Grid API messages, 119
calculation messages, 51
checking
for database corruption, 124
User Limit Profile, 125
corruption, database
checking for, 124
fixing, 124
D
data cache messages, 31
data load messages, 19
database corruption
checking for, 124
A
C
D
E
F
fixing, 124
database object messages, 79
determining operating system privileges, 126
E
ending server task, 126
environment variables, setting, 123
error codes and numbers, 7
error message categories, 7
Essbase Server
errors, 7
Essbase Server logs
message categories, 7
L
M
N
O
P
R
S
U
V
S
server task, ending, 126
setting
environment variables, 123
NETDELAY and NETRETRYCOUNT, 125
system call messages, 37
system errors
categories, 7
system privileges, operating, determining, 126
U
unlocking objects, 126
User Limit Profile, checking, 125
F
V
fixing database corruption, 124
variables, environment, setting, 123
L
Lock Manager messages, 75
locked objects, 126
M
miscellaneous messages, 121
N
NETDELAY, setting, 125
NETRETRYCOUNT, setting, 125
network messages, 91
O
objects, unlocking, 126
operating system privileges, determining, 126
overview, 7
P
privileges, operating system, determining, 126
procedures, referenced, 123
R
referenced procedures, 123
Requestor messages, 73
Index 135
A
136 Index
C
D
E
F
L
M
N
O
P
R
S
U
V
Download PDF
Similar pages