Calculation Messages 1012000 to 1012750
This document describes calculation error messages and information messages. The discussions
of error messages include possible causes and
possible solutions for each problem, with links to the Essbase Database
Administrator's Guide and the Essbase Technical Reference for more information
on how to fix errors.
Click an error message number to view information about that error message.
1012000 Invalid Syntax - Not a CALC command invalidCommandName
Possible Problems
Essbase encountered a command in a calculation script that is not a valid calculation command.
Possible Solutions
Make sure that the calculation command is correct.
- Is the calculation command spelled correctly?
- Are all variables in the calculation command spelled correctly?
- Is the calculation command valid?
1012001 Invalid Calc Script syntax calculationCommandWithErrors
Possible Problems
Essbase encountered a syntax error in a calculation script.
Possible Solutions
Make sure that the calculation script is valid.
1012004 Invalid member name memberName
Possible Problems
Essbase encountered an invalid member name in the calculation script.
Possible Solutions
Make sure that the member name is valid.
- Does the member still exist in the outline? This error message usually occurs when a member has been 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, make sure 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.
See Also
1012005
1012005 Invalid dimension name dimensionName
Possible Problems
Essbase encountered an invalid dimension name in the calculation script.
Possible Solutions
Make sure that the dimension name is valid.
- Does the dimension still exist in the outline? This message usually occurs when a dimension has been 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, make sure
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.
See Also
1012004
1012009 Variable name variableName too long
Possible Problems
Essbase encountered a variable name that is too long. Variable names must be no more than 32 bytes.
Possible Solutions
1012010 Redeclared Variable name variableName
Possible Problems
The variable was declared more than once in a single calculation script.
Possible Solutions
Check the calculation script and remove the extra variable declarations.
Make sure that you are declaring the variable correctly before you use
it.
1012011 Variable name variableName conflicts with member name
Possible Problems
The name assigned to the listed variable was the same as the name of a member in the outline.
Possible Solutions
Assign the variable a unique name. Remember that the variable name must be 32 bytes or fewer and must
follow Essbase naming rules.
Make sure that you are declaring the variable correctly before you use
it.
1012012 The array variable range specifier dimensionName
is not a dimension
Possible Problems
The dimension in the calculation script that determines the size of the array variable
was not a valid dimension.
Possible Solutions
- Make sure that the dimension name is valid.
- 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, make sure that the dimension name is enclosed in
quotation marks.
- Make sure that the dimension name is enclosed in brackets [dimensionName] in
the calculation script.
- Make sure that the ARRAY command
in the calculation script is valid.
1012013 Calc Script Error - Unexpected End of File reached
Possible Problems
The calculation script contained a comment open symbol /*
, but did not contain
a matching comment close symbol */
.
Possible Solutions
Add the comment close symbol */
at the end of the comment.
1012015 CALC ALL cannot be used in restricted calculation
Possible Problems
Essbase encountered a CALC ALL command inside a FIX-ENDFIX command block.
Possible Solutions
Make sure 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 fixes on a part of the database and calculates only that part.
1012016 Cannot calculate dimension member memberName with restricted member memberName
Possible Problems
The calculation script contained a calculation that tried to calculate a member after restricting the calculation
to a different member in the same dimension.
Possible Solutions
Make sure that the member is correctly positioned in the FIX statement. If you fix on a member, you can calculate only that
member. For example, the following FIX statement is incorrect because the FIX is on the Sales member, but the statement tries
to calculate Profit, which is a different member:
FIX(Sales)
Profit;
ENDFIX
The following FIX statement is correct:
FIX (Sales)
Sales;
ENDFIX
See Also
1012017
1012017 Cannot calculate dimension dimensionName with restricted member memberName
Possible Problems
The calculation script contained a calculation that tried to calculate a dimension after restricting the calculation
to a member of the same dimension.
Possible Solutions
Make sure 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, the following FIX statement
is incorrect because the FIX is on the Sales member, which is part of the the Measures dimension,
but the statement tries to calculate the entire Measures dimension:
FIX(Sales)
CALC DIM Measures;
ENDFIX
See Also
1012016
1012018 Redeclared dimension dimensionName in AGG command
Possible Problems
The dimension name was declared more than once in a single AGG command.
Possible Solutions
Check the calculation script and remove the extra dimension name declarations.
1012019 Calc Script block delimiter delimiterName not balanced delimiterName
Possible Problems
The calculation script did not have the correct number of opening or closing parentheses.
Possible Solutions
Check the calculation script to add the missing parenthesis or delete the extra parenthesis.
1012021 Calc Script command calculationScriptCommand is incomplete
Possible Problems
The listed calculation script command was not complete.
Possible Solutions
Make sure that the calculation script command contains all pertinent data.
- Are any flow control commands not closed, such as a FIX command
without an ENDFIX command, or a LOOP command without an ENDLOOP command?
- Are semicolons missing?
- Are all left parentheses closed by right parentheses?
1012023 Aggregating on Dense Dimension dimensionName is currently not supported
Possible Problems
Essbase cannot use the AGG command with dense dimensions.
Possible Solutions
Check the calculation script to make sure that you are not using the AGG command on a
dimension tagged as dense.
1012024 Cannot aggregate dimension dimensionName with restricted
member memberName
Possible Problems
The calculation script contains a calculation that tries to aggregate a dimension after restricting the calculation
to a member of the same dimension.
Possible Solutions
Make sure that the dimension is correctly positioned in the FIX statement. If you fix on a member, you
can aggregate only that member. For example, the following 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
The following FIX statement is correct:
FIX (Sales)
AGG (Sales);
ENDFIX
1012025 No Currency Database has been set on this database
Possible Problems
Essbase tried to perform a calculation that required a currency database but
no currency database existed.
Possible Solutions
1012026 commandName command can only be fixed on a CURPARTITION member
Possible Problems
Essbase tried to FIX on a member that was not a member of the CURPARTITION dimension.
Possible Solutions
When using the CCONV command, make sure 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
Possible Problems
Essbase tried to FIX on a member of the CURPARTITION dimension but the CURPARTITION dimension is
not defined for the database.
Possible Solutions
When using the CCONV command, make sure that all members that appear inside
the FIX command belong to
the CURPARTITION dimension and that the CURPARTITION dimension is correctly defined.
1012028 commandName command must be fixed on a CURPARTITION member
Possible Problems
Essbase cannot use the CCONV command without a currency partition defined.
Possible Solutions
When using the CCONV command, make sure that all members that appear inside
the FIX command belong to
the CURPARTITION dimension.
1012029 Invalid target range range of DCOPY command
Possible Problems
The DATACOPY command did not have the same number of members in the source range as the target range.
Possible Solutions
Make sure that the source range (the set of members you are copying from) has the same number of members as the target
range (the set of members you are copying to).
Make sure that the DATACOPY command is correct.
1012030 DATACOPY command command cannot copy data to itself
Possible Problems
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.
Possible Solutions
Make sure that the DATACOPY command is set to copy the
correct range.
Compare the source and target ranges to make sure that the DATACOPY command is not copying the data back
onto the source range.
1012031 DATACOPY command command is conflict with Range Fix
Possible Problems
Essbase tried to copy a range of members that was outside of the range you fixed on.
Possible Solutions
Make the DATACOPY range and FIX range
compatible, either 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
Possible Problems
Essbase tried to use the FIX command while using DATACOPY to copy a currency partition and this is not
permitted.
Possible Solutions
Make sure 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 if your company has purchased
the Currency Conversion option for Essbase.
1012034 Variable variableName not declared
Possible Problems
The variable used in the calculation script is not declared.
Possible Solutions
Make sure that you are declaring the variable correctly before you use
it.
1012035 Variable variableName must be of VAR type
Possible Problems
The variable listed must be of VAR type instead of ARRAY type.
Possible Solutions
Make sure that you are declaring the variable correctly.
1012036 Calc Script block command blockCommandName does not end with
blockEndCommandName
Possible Problems
Essbase encountered a block command that was not closed.
Possible Solutions
Make sure that each FIX command is closed by an ENDFIX command.
Make sure that each LOOP command is closed by an ENDLOOP command.
1012037 Custom calculation is not allowed for kindOfShare share
member sharedMemberName
Possible Problems
Essbase tried to calculate a formula on a shared member.
Possible Solutions
Because shared members do not store data, you cannot attach formulas to them.
Make sure that the listed member is not shared, either because the storage property of the member is explicitly
tagged as shared or because the member is
implicitly shared.
1012038 The constant constantName assigned to variable variableName
is not a number
Possible Problems
Essbase tried to assign a value that was not a number to the listed variable. The listed variable
can accept only numeric values.
Possible Solutions
Make sure that you are declaring the variable correctly.
1012039 The constant constantName assigned to array variable arrayVariableName
is not a number
Possible Problems
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.
Possible Solutions
Make sure that you are assigning the array variable correctly.
1012040 Too many initial constants assigned to array variable arrayVariableName
Possible Problems
Essbase tried to assign more values to the array than there are members in the dimension with which it is
associated.
Possible Solutions
Make sure that you are using the ARRAY command correctly.
Make sure that you are assigning the values to the correct dimension.
1012041 memberName is not a valid currency type member
Possible Problems
Essbase tried to specify the currency type using a member that was not part of the dimension
tagged as CurType in the Essbase database.
Possible Solutions
Make sure you are using the CCONV function correctly and that you have
set up the currency database correctly.
Make sure that the listed member is defined as the currency type member.
1012042 Substitution variable substitionVariableName doesn't exist
Possible Problems
The calculation script cannot find the listed substitution variable.
Possible Solutions
Make sure that you created the substitution variable correctly.
Make sure that the substitution variable was created at the correct level.
- 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 OLAP Server.
1012043 Calculation is not allowed for virtual member memberName in the Calc script
Possible Problems
The calculation script tried to set the value of a Dynamic Calc member or request the calculation of a Dynamic Calc member.
Possible Solutions
Dynamic Calc members are calculated at query time if a query requests the value of the member. They cannot
be calculated through calculation scripts. Make sure that the Dynamic Calc member is not
on the left side of the equation; for example, if Qtr1 is Dynamic Calc, the following equation is incorrect:
Qtr1 = Jan + Feb + Mar;
If Qtr1 is Dynamic Calc, the following equation is also incorrect:
vbb
Qtr1;
The following 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 Hyperion Technical Support.
1012045 Unable to convert bitmap to fix member in function functionName
Contact Hyperion Technical Support.
1012046 Unable to convert MEMNOR to MEMNO in function functionName
Contact Hyperion Technical Support.
1012047 Aggregating on Attribute Dimension attributeDimensionName is currently not supported
Possible Problems
Essbase tried to calculate the listed attribute dimension using the AGG command.
Possible Solutions
Make sure 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
Possible Problems
Essbase tried to calculate the listed attribute dimension using the CALC DIM command.
Possible Solutions
Make sure 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
Possible Problems
Essbase tried to clear data from the listed attribute dimension.
Possible Solutions
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 any member of an attribute dimension.
1012050 Cannot DATACOPY on Attribute dimension member memberName
Possible Problems
Essbase tried to copy data into the listed attribute dimension using the DATACOPY command.
Possible Solutions
Make sure 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
Possible Problems
Essbase tried to FIX on a Dynamic Calc member.
Possible Solutions
Make sure 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.
1012052 Unable to unfix blocks after calculation encounters an error
Possible Problems
The data blocks that were changed by a calculation were left in an inconsistent state.
Possible Solutions
Stop and restart the database or contact Hyperion Technical Support.
Essbase either reverted all values to their previous state or retained any values calculated before the error.
How Essbase handles the cancellation depends on the Essbase kernel isolation level settings.
1012053 Calculation is cancelled by user
This information message states that the user pressed the cancel button
while performing the calculation. Essbase either reverted all values to their previous state
or retained any 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
Possible Problems
Essbase tried to FIX on a dimension that contains no stored members.
Possible Solutions
Make sure that at least one member in the dimension that the calculation script fixes on is tagged as stored. Make sure that
at least one stored member is not tagged as Two Pass.
1012055 The expression inside FIX evaluates to an empty set. Operation aborted
Possible Problems
Essbase tried to fix on a member or set of members that do not exist.
Possible Solutions
Make sure 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, make sure that the function returns at least one member. The following 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))
CALC DIM (Product);
ENDFIX
The following calculation script is correct, because Qtr1 is not a level 0 member:
FIX(@CHILDREN (Qtr1))
CALC DIM (Product);
ENDFIX
1012061 The CALC command commandName can only be used within a
CALC Member Formula
Possible Problems
Essbase cannot execute the listed command.
Possible Solutions
The IF and ELSE
commands must be used within a member formula. They cannot be used in a calculation script.
1012106 Calc String function functionName
must be followed by '('
Possible Problems
The listed function needed a left parenthesis (
.
Possible Solutions
Insert the left parenthesis (
after the function name, with the function parameters separated by commas, and a closing
parenthesis. Check the syntax of the function.
1012121 Error encountered when loading member memberName's
calc string memberFormula, ignored
Possible Problems
Essbase could not compile the formula attached to the member because of one or more syntax
errors.
Possible Solutions
Check the application log
($ARBORPATH/app/applicationName/applicationName.log
) for a
list of syntax errors.
Correct the syntax errors. Check the calculation
script command syntax.
1012134 Generation number number must be
an integer
Possible Problems
Essbase encountered a generation number that was not an integer.
Possible Solutions
Make sure that all generations are numbered with integers.
1012135 Level number number must be an integer
Possible Problems
Essbase encountered a level number that was not an integer.
Possible Solutions
Make sure that all levels are numbered with integers.
1012136 Named generation generationName
is not defined
Possible Problems
Essbase encountered a generation name that is not defined in the
database.
Possible Solutions
Make sure that the generation name is properly defined in the database.
1012137 Named Level levelName is not defined
Possible Problems
Essbase encountered a level name that is not defined in the database.
Possible Solutions
Make sure that the level name is properly defined in the database.
1012139 No memberType member found in Account dimension
Possible Problems
The listed member type was not found in the dimension tagged as accounts.
Possible Solutions
If you are using the CALC FIRST, CALC LAST, CALC AVERAGE, or CALC TWOPASS commands, make sure
that there is a dimension tagged as accounts in the outline and that the dimension tagged as accounts
contains the following members:
- If you are using the CALC FIRST command, the accounts dimension must have a member tagged with a time balance of First.
- If you are using the CALC LAST command, the accounts dimension must have a member tagged with a time balance of Last.
- If you are using the CALC AVERAGE command, the accounts dimension must have a member tagged with a time balance of Average.
- If you are using the CALC TWOPASS command, the accounts dimension must have a member tagged as Two-Pass.
1012141 Illegal match string stringToMatch
Possible Problems
The pattern specified in the @MATCH function was not valid.
Possible Solutions
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
Possible Problems
Essbase encountered a generation or level number or a generation or level name that was not valid.
Possible Solutions
Make sure that all generations or levels are numbered with integers or valid names.
Follow the same rules as for naming members.
1012143 @MATCH search string stringToSearchFor
should always be in double quote
Possible Problems
Essbase could not search for the listed string because it was
not enclosed in quotation marks.
Possible Solutions
Check the syntax of the @MATCH command.
1012500 The requested calc script calcScriptName
not found
Possible Problems
Essbase could not open the listed calculation script.
Possible Solutions
Make sure that Essbase can find the calculation script.
- Are the calculation script name and path name correct? Check for misspellings.
- If the calculation script is on a UNIX platform, is capitalization correct?
- Is the calculation script in the specified location? Make sure that no one has moved or deleted the calculation script.
Make sure that Essbase can use the calculation script.
- Is the calculation script being used by another user or application?
- Does the calculation script have the correct file extension? All calculation scripts must have a file extension of
.csc
.
- Is the calculation script valid?
- Are the permissions set up correctly for the
Essbase database you are calculating?
1012501 Calculator internal error -- invalid input type inputTypes
Possible Problems
Essbase could not read the calculation script.
Possible Solutions
Make sure that the client is correctly passing the location of the calculation script to OLAP Server.
1012550 Total Calc Elapsed Time : number
seconds
This information message states how long it took
Essbase to perform the calculation. There is nothing wrong.
1012551 Converting database databaseName's currency to
currencyType
This information message states that
Essbase is converting the currency type for the listed database. There is nothing wrong.
1012552 Copying data from rangeOfCells
This information message states that Essbase is copying the data from the listed range of cells. There is
nothing wrong.
1012553 Copying data from rangeOfCells with fixed members
memberNames
This information message states that Essbase is copying the data from the listed range of cells. There is
nothing wrong.
1012554 Clearing data from partitionName partition
This information message states that Essbase is clearing the data from the listed partition. There is nothing wrong.
1012555 Clearing data from partitionName partition with
fixed members memberNames
This information message states that Essbase is clearing the data from the listed partition. There is nothing wrong.
1012556 Calculation canceled by user userName
This information message states that the listed user canceled the calculation
before it completed. There is nothing wrong. Essbase either reverted all values to their previous state
or retained any values calculated before the cancellation. How Essbase handles the cancellation depends on the
Essbase kernel isolation level settings.
1012557 Clearing all data blocks from partitionName partition
This information message states that Essbase is clearing the data from the listed partition. There is nothing wrong.
1012558 Clearing all data blocks from partitionName partition
with fixed members memberNames
This information message states that Essbase is clearing the data from the listed partition. There is nothing wrong.
1012559 Clearing upper level data blocks from partitionName
partition
This information message states that Essbase is clearing the data from the upper level data blocks in the listed
partition. There is nothing wrong.
1012560 Clearing upper level data blocks from partitionName
partition with fixed members memberNames
This information message states that Essbase is clearing the data from the upper level data blocks in the listed
partition. There is nothing wrong.
1012561 Clearing noninput data blocks from partitionName
partition
This information message states that Essbase is clearing the data from the noninput data blocks in the listed
partition. There is nothing wrong.
1012562 Clearing noninput data blocks from partitionName
partition with fixed members memberNames
This information message states that Essbase is clearing the data from the noninput data blocks in the listed
partition. There is nothing wrong.
1012563 Calculation is aborted due to floating point error errorType
Possible Problems
Essbase canceled the calculation because it encountered a floating point error, such as
overflow, underflow, or a division by zero.
Possible Solutions
- 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.
- Return the data values to their previous states. Essbase either reverted all values to their previous states
or retained any values calculated before the cancellation. How Essbase handled the cancellation depends on the
Essbase kernel isolation level settings.
- Run the calculation again.
1012564 Calculation is aborted due to floating
point error
Possible Problems
Essbase canceled the calculation because it encountered a floating point error, such as
overflow, underflow, or a division by zero.
Possible Solutions
- 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.
- Return the data values to their previous states. Essbase either reverted all values to their previous states
or retained any values calculated before the cancellation. How Essbase handled the cancellation depends on the
Essbase kernel isolation level settings.
- Run the calculation again.
1012566 Begin of LOOP -- looping following commands
number times
This information message states that Essbase is looping through the calculation script commands the listed
number of times. There is nothing wrong.
1012567 End of LOOP -- actually looped above commands
number times
This information message states that Essbase completed the loop
specified in the calculation script the listed number of times. There is nothing wrong.
1012568 Commit Blocks Interval was adjusted to be
number blocks
This information message states that OLAP Server changed
the commit blocks interval to optimize performance. There is nothing
wrong.
1012569 Formula on member memberName forces
calculation to execute in serial mode
This information message states that the formula on the listed
member requires that the calculation be performed in serial mode instead of
parallel mode. There is nothing wrong.
To run the calculation in parallel mode, consider removing the formula or tagging the member
as Dynamic Calc.
1012570 A circular or recursive dependency along
dimension dimensionName forces calculation to execute in serial mode
This information message states that the listed
dimension contains a dependency that requires the calculation be
executed in serial mode instead of
parallel mode. There is nothing wrong.
To run the calculation in parallel mode, consider removing the formula or tagging the member
as Dynamic Calc.
1012571 Presence of variables or formulas with
@XREF function forces calculation to execute in serial mode
This information message states that calculation will be
executed in serial mode instead of
parallel mode. Formulas or calculation
scripts that use variables with the @XREF function must be calculated in
serial mode. There is nothing wrong.
1012600 Member memberName attempts to divide by Missing,
Invalid, or Near Zero value (Message will not repeat)
Possible Problems
When calculating the listed member, Essbase attempted to perform
a division by an invalid value, such as zero or a missing value.
Possible Solutions
Check the formula or calculation script that calculated the listed member to make sure 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
Possible Problems
Your OLAP Server does not have the currency conversion option.
Possible Solutions
To use currency conversion functionality, you must purchase the Currency Conversion option for Essbase.
1012668 Calculating memberNames with fixed members memberNames
This information message states which members Essbase is calculating
and which members are fixed. There is nothing wrong.
1012669 Calculating memberNames
This information message states which members Essbase is calculating. There is nothing wrong.
1012670 Aggregating memberNames with fixed members memberName
This information message states which members Essbase is aggregating
and which members are fixed. There is nothing wrong.
1012671 Aggregating memberNames
This information message states which members Essbase is aggregating. There is nothing wrong.
1012672 Calculator Information Message: messageInformation
This information message states that Essbase is performing a specific action.
The information is logged because you requested it. For example, if you use the
SET MSG command, specific details
about the calculation are logged. There is nothing wrong.
1012674 Hash memory number allocated for Calc is
used up, Hash Table is turned off. Please increase the CalcHashTblMemLimit in the
essbase.cfg file.
Possible Problems
Essbase had no more hash memory.
Possible Solutions
- If you do not have an
$ARBORPATH/bin/
essbase.cfg
file on the server computer, create one using a text editor.
- In the
essbase.cfg
file on the server computer, add or increase
the value for CALCHASHTBLMEMORY.
- Stop and restart OLAP Server.
- Perform the calculation again.
1012675 Commit Blocks Interval for the calculation
is number
This information message states the number of blocks committed at a time. There is nothing wrong.
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)
Possible Problems
Essbase cannot calculate the @POWER or @FACTORIAL function because the value is too large.
Possible Solutions
Make sure that the formula or calculation script is not requesting extremely large values, such as 2 raised to
the 1 millionth power.
1012677 Calculating in serial
Possible Problems
OLAP Server is performing the calculations in the
calculation script serially, instead of in parallel.
Possible Solutions
If you requested the calculation run in parallel mode, look
in $ARBORPATH/app/applicationName/applicationName.log
for more information.
See Also
1012569
1012570
1012571
1012678 Calculating in parallel with number threads
This information message states that OLAP Server is performing the calculations
in the calculation script in parallel using the
listed number of threads. You can set the number of
threads using the CALCPARALLEL
configuration setting or the SET
CALCPARALLEL calculation script command. If the listed number is different
from the value you set using CALCPARALLEL, the calculator picked the listed number
as the optimal degree of parallelism for your database. There is nothing wrong.
1012679 Calculation task schedule number
This information message states the number of tasks that can be
executed concurrently at any one time and, therefore, indicates the kind of
performance gain you can expect from parallel calculation. Larger numbers indicate more
parallel calculation. If the listed number(s)
are smaller than the number of threads you specified using the CALCPARALLEL
configuration setting or the SET
CALCPARALLEL calculation script command, you will not experience a large performance
gain from parallel calculation.
There is nothing wrong.
1012680 Parallelizing using number task
dimensions.
This information message states the number of task dimensions Essbase
is using for parallel calculation. If the
number of task dimension was reduced from the listed number, the message
will also state that the "Usage of calculator cache caused reduction in
task dimensions." To set the number of task dimensions, use
the CALCPARALLEL
configuration setting or the SET
CALCPARALLEL calculation script command.
There is nothing wrong.
1012681 Empty tasks number
This information message states the number of tasks that
contain no calculations. The number of empty tasks affect the
gains you can receive from parallel calculation. The
ideal number of empty tasks is 0.
There is nothing wrong.
1012682 Multiple bitmap mode calculator cache memory usage attempted
to cross limit of number bitmaps. To ignore limit, do not set MultipleBitmapMemCheck to
TRUE in $ARBORPATH/bin/essbase.cfg.
This information message states that 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 $ARBORPATH/bin/essbase.cfg
file on the server computer.
1012683 Multiple bitmap mode calculator cache memory usage crossed
limit of number bitmaps. Set MultipleBitmapMemCheck to TRUE in
$ARBORPATH/bin/essbase.cfg to enforce limit.
This information message states that the calculator cache memory is using
more bitmaps than allowed. To prevent this from happening, set
MULTIPLEBITMAPCHECK
to TRUE in the $ARBORPATH/bin/essbase.cfg
file on the server computer.
1012684 Multiple bitmap mode calculator cache memory usage has a
limit of number bitmaps.
This information message states the number of bitmaps Essbase can use in
the calculator cache. There is nothing wrong.
1012700 Dynamic calc processor cannot allocate more than
number blocks from the heap. Please increase CalcLockBlock setting and then
retry
Possible Problems
Essbase cannot allocate enough blocks to perform the calculation.
Possible Solutions
Increase the number of blocks that Essbase can allocate for a calculation:
- Set the maximum number of blocks that Essbase can allocate to at least 500:
- If you do not have an
$ARBORPATH/bin/
essbase.cfg
file on the server computer, create one using a text editor.
- In the
essbase.cfg
file on the server computer, set
CALCLOCKBLOCKHIGH to
500.
- Stop and restart OLAP Server.
- Add the SET LOCKBLOCK HIGH command to the beginning of the
calculation script.
- Set the data cache large enough to hold all the blocks specified in the CALCLOCKBLOCKHIGH setting.
1012701 Unknown block type during the dynamic calculation, neither an ESM block nor a heap block.
Essbase internal error, Please report to Hyperion.
Contact Hyperion Technical Support.
1012702 The block in the dynamic calc processor block array is not marked correctly. Essbase internal
error. Please report to Hyperion.
Contact Hyperion Technical Support.
1012703 Unknown calculation type calculationType during the dynamic calculation.
Only default agg/formula/time balance operations are handled.
Contact Hyperion Technical Support.
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).
Possible Problems
Essbase could not lock enough blocks to perform the calculation.
Possible Solutions
Increase the number of blocks that Essbase can allocate for a calculation:
- Set the maximum number of blocks that Essbase can allocate to at least 500.
- If you do not have an
$ARBORPATH/bin/essbase.cfg
file on the server computer, create one using a text editor.
- In the
essbase.cfg
file on the server computer, set
CALCLOCKBLOCKHIGH to
500.
- Stop and restart OLAP Server.
- Add the SET LOCKBLOCK HIGH command to the beginning of the
calculation script.
- Set the data cache large enough to hold all the 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.
Contact Hyperion Technical Support.
1012708 For virtual time series timePeriod retrieval, the latest time period is not set
Possible Problems
Essbase tried to retrieve the time series data without knowing the latest time period.
Possible Solutions
Set the latest time period member name in the retrieval tool.
- For Essbase Spreadsheet Add-in, specify the Latest Time Series
option in the Spreadsheet Add-in Essbase Options dialog box. For more information, see
the 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
Possible Problems
Essbase tried to retrieve the latest time period, but the time member is not at level 0 in the outline.
Possible Solutions
Make sure 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
dynamically-calculated block.
This information message states the number of blocks that Essbase will need to retrieve
to perform the dynamic calculation along a sparse dimension. You can use this to estimate the retrieval
performance for members of sparse dimensions that are tagged as Dynamic Calc. There is nothing wrong.
1012711 Clearing dynamic calc store data blocks from partitionName partition
This information message states that Essbase is clearing data blocks from the listed
partition. There is nothing wrong.
1012712 Clearing dynamic calc store data blocks from partitionName partition with
fixed members memberNames
This information message states that Essbase is clearing data blocks from the listed
partition. There is nothing wrong.
1012713 Two-pass Member memberName is not tagged as Dynamic Calc.
This information message states that the listed member is tagged as Two Pass but not tagged as Dynamic Calc and
is not a member of the dimension tagged as accounts. 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. There is nothing wrong.
1012714 Regular member memberName depends on dynamic-calc member memberName.
Possible Problems
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.
Possible Solutions
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.
Consider tagging the listed Dynamic Calc member as stored or tagging the dependent
regular member as Dynamic Calc.
1012715 Regular member memberName depends on
member memberName from transparent partition. Consider making this member Dynamic or replicating the dependents.
Possible Problems
The listed member is calculated using members in a transparent partition.
Possible Solutions
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 either of the following methods:
- 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.
Possible Problems
Essbase encountered a remote partition region that has not been validated.
Possible Solutions
Open the partition definition and validate it. If necessary, correct any errors.
1012717 Remote bitmap cache is on/off
This information message states whether the bitmap cache is turned on or off. OLAP Server determines whether
to turn the bitmap cache on or off; you cannot change this setting. There is nothing wrong.
1012718 For dynamic time series, the latest period settingName setting has
higher generation member than the time series member memberName
Possible Problems
The latest period setting was at a higher generation than the time series member.
Possible Solutions
Make sure 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).
1012727 Dynamic calc cache sanity failed
Contact Hyperion Technical Support.
1012733 Dynamic calc cache compression buffer full
Possible Problems
The Dynamic Calc cache buffer was out of space.
Possible Solutions
The Dynamic Calc cache compression buffer is used only when you set DYNCALCCACHEWAITFORBLK and
DYNCALCCACHEBLKRELEASE to TRUE in the $ARBORPATH/bin/essbase.cfg
file.
To fix this problem:
- If you do not have an
$ARBORPATH/bin/
essbase.cfg
file on the server computer, create one using a text editor.
- In the
essbase.cfg
file on the server computer, increase the value of
DYNCALCCACHECOMPRBLKBUFSIZE.
- In the
essbase.cfg
file on the server computer, set
DYNCALCCACHEWAITFORBLK
and
DYNCALCCACHEBLKRELEASE
to FALSE.
- Stop and restart OLAP Server.
1012734 Timed out waiting for blocks from the dynamic calc cache.
Possible Problems
Essbase waited for a block to become available in the Dynamic Calc cache, but the cache was full.
Possible Solutions
You can solve this problem in any of the following ways:
- 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.
- If you do not have an
$ARBORPATH/bin/
essbase.cfg
file on the server computer, create one using a text editor.
- In the
essbase.cfg
file on the server
computer, add or increase the value of
DYNCALCCACHEBLKTIMEOUT.
- Stop and restart OLAP Server.
- Specify that queries should not wait for available blocks in the Dynamic Calc
cache.
- If you do not have an
$ARBORPATH/bin/
essbase.cfg
file on the server computer, create one using a text editor.
- In the
essbase.cfg
file on the server computer, set
DYNCALCCACHEWAITFORBLK
to FALSE.
- Stop and restart OLAP Server.
1012735 Thread synchronization error when allocating from the dynamic calc cache.
Contact Hyperion Technical Support.
1012736 The Dyn.Calc.Cache for database databaseName can hold a maximum
of number blocks.
This information message states the maximum number of blocks that the Dynamic
Calc cache for the listed database can hold. There is nothing wrong. To change the
number of blocks in the Dynamic Calc cache:
- If you do not have an
$ARBORPATH/bin/
essbase.cfg
file on the server computer, create one using a text editor.
- In the
essbase.cfg
file one the server, add or change
DYNCALCCACHEMAXSIZE.
- Stop and restart OLAP Server.
1012737 The Dyn.Calc.Cache for database databaseName, when full, will result in
action.
This information message states that Essbase will perform the following action
when the dynamic calculator cache is full:
- If DYNCALCCACHEWAITFORBLK
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 DYNCALCCACHEWAITFORBLK
in the
$ARBORPATH/bin/essbase.cfg
file is FALSE, Essbase checks DYNCALCCACHEONLY.
- If DYNCALCCACHEONLY is TRUE, Essbase generates an error message.
- If DYNCALCCACHEONLY is FALSE, Essbase stores and calculates data blocks for the
current query in memory outside of the dynamic calculator cache.
There is nothing wrong.
1012738 The Dyn.Calc.Cache for database databaseName has a timeout of number seconds
when waiting for free blocks.
This information message states the current value of
DYNCALCCACHEBLKTIMEOUT. There is nothing wrong.
1012739 The Dyn.Calc.Cache for database databaseName, upon timeout of a wait for free blocks,
will result in action.
This information message states that Essbase will perform the following
action when the specified waiting period is over:
- If DYNCALCCACHEBLKRELEASE in
the
$ARBORPATH/bin/essbase.cfg
file is TRUE, Essbase makes room available in the
dynamic calculator cache by temporarily storing inactive blocks in a separate, compressed-block buffer.
- If DYNCALCCACHEBLKRELEASE in
the
$ARBORPATH/bin/essbase.cfg
file is FALSE, Essbase does not find room in the
dynamic calculator cache for a different set of blocks. Instead, Essbase checks
DYNCALCCACHEONLY .
- If DYNCALCCACHEONLY is TRUE, Essbase generates an error message.
- If DYNCALCCACHEONLY is FALSE, Essbase stores and calculates data blocks for the
current query in memory outside of the dynamic calculator cache.
There is nothing wrong.
1012740 The Dyn.Calc.Cache for database databaseName uses a buffer of size number bytes
to store compressed released blocks.
This information message states the current value of
DYNCALCCACHECOMPRBLKBUFSIZE. There is nothing wrong.
1012741 Allocation outside the dynamic calc cache is disallowed
This information message states the current value of
DYNCALCCACHEONLY is TRUE. There is nothing wrong.
1012742 Two-pass calc skipped on member memberName in attribute calc
This information message states that the listed member was skipped during Two Pass
calculation because the listed member has no member formula or the listed member
has a run-time dependency. Run-time dependent functions include:
@CURRMBR,
@PARENT,
@PARENTVAL,
@MDPARENTVAL,
@ANCEST,
@ANCESTVAL, and
@MDANCESTVAL.
There is nothing wrong.
1012750 Retrieve & Lock operation is not supported on attribute cells
Possible Problems
Essbase cannot update cells that are part of a relational partition.
Possible Solutions
Make sure that none of the cells being updated is part of a relational partition.