Welcome to FixPak 4 for DB2 OLAP Server for AS/400, Version 7.1. This is your starting point for downloading and installing all of the files of FixPak 4. You will see references to operating systems and components that are not included in DB2 OLAP Server for AS/400 7.1; please disregard these references.
Service Level: The components of this FixPak are shipped
at the following service levels:
New Features and Changes in this FixPak
Problem Summary: A list of all the problems fixed by this and previous FixPaks.
You need to install four files to completely install all of the components of FixPak 4. Please read and follow all of the instructions for each component.
|
|
|
|
|
|
U.S. English Uppercase English |
|
|
|
Choose 1 of 2 (see instructions for details) |
|
|
|
(see instructions for details) |
|
|
|
(see instructions for details) |
|
| What is Upper English? - Upper English FixPaks are intended for double-byte systems that require English commands to be in ALL UPPER CASE. These are typically systems that use Kanji characters. |
CAUTION!!! ShowCase 4.00 contains Java code, which entails extra steps for patching. In order for a fix to take affect, you must follow these instructions in order.
<SCSERVER>/ENDSCSVR, where SCSERVER is your ShowCase library.
If you are applying a Warehouse Manager FixPak to a library that has already been connected to, the SQL server jobs (QSQSRVR) must be ended and restarted before you re-start the server. To properly enable this FixPak for prestarted server jobs, you will need to stop and restart the SQL server jobs. Otherwise the prestarted server jobs may continue to use older versions of programs and unexpected results may occur. To stop and restart the SQL server jobs, run the following:
ENDPJ SBS(QSYSWRK) PGM(QSQSRVR) OPTION(*IMMED)
STRPJ SBS(QSYSWRK) PGM(QSQSRVR)
Note: ShowCase is not the only application that uses these jobs, so you must make sure that there are no other programs using these jobs. This may require that you dedicate your AS/400.
Installing the FixPak
(At this point, please be sure that Item 2 from "Downloading the FixPak" has completed. That item involves executing the file that was downloaded from the web, thus creating the larger .bin file that will be saved as an FTP file to the server.)
CRTSAVF QGPL/WSE040US
Password: <password>
230 <userid> logged on.
ftp> binary
ftp> put c:...\WSE040US.BIN QGPL/WSE040US
ftp> quit
C:\>
ADDLIBLE <SCSERVER> ,where SCSERVER is your ShowCase
library.
APYSCPTF DEV(*SAVF) SAVF(QGPL/WSE040US)
[You will be prompted for the name of your
server library. Enter your library name
when
prompted]
DSPJRN JRN(<SCSERVER>/SCPTFLOG), where SCSERVER is your ShowCase library.
The ShowCase jar file must be recompiled:
This section describes how to install the FixPak for Upper English version of the Warehouse Manager server component. If you use the US English version, see US English Warehouse Manager server component
CAUTION!!! ShowCase 4.00 contains Java code, which entails extra steps for patching. In order for a fix to take affect, you must follow these instructions in order.
This FixPak will fix all problems described in the previous document. The FixPak must be applied only to the ShowCase STRATEGY 4.00, dated 10/16/00. Refer to the instructions below for downloading and applying the FixPak.
Prerequisites for Applying the FixPak
DSPOBJD <SCSERVER>/WSE040PP *USRSPC, where SCSERVER is your ShowCase library.
If the following message appears, the FixPak has not been applied.
CPF9801 - Object WSE040PP in library <SCSERVER> not found.
<SCSERVER>/ENDSCSVR, where SCSERVER is your ShowCase library.
WRKOBJLCK OBJ(<SCSERVER>/SCCONNECT) OBJTYPE(*USRSPC),
where SCSERVER is your ShowCase library.
If you are applying a Warehouse Manager FixPak to a library that has already been connected to, the SQL server jobs (QSQSRVR) must be ended and restarted before you re-start the server. To properly enable this FixPak for prestarted server jobs, you will need to stop and restart the SQL server jobs. Otherwise the prestarted server jobs may continue to use older versions of programs and unexpected results may occur. To stop and restart the SQL server jobs, run the following:
ENDPJ SBS(QSYSWRK) PGM(QSQSRVR) OPTION(*IMMED)
STRPJ SBS(QSYSWRK) PGM(QSQSRVR)
Note: ShowCase is not the only application that uses these jobs, so you must make sure that there are no other programs using these jobs. This may require that you dedicate your AS/400.
Installing the FixPak
(At this point, please be sure that Item 2 from "Downloading the FixPak" has completed. That item involves executing the file that was downloaded from the web, thus creating the larger .bin file that will be saved as an FTP file to the server.)
C:\>FTP <AS/400 IP
Address>
User (system:(none)): <userid>
331 Enter password.
Password: <password>
230 <userid> logged on.
ftp> binary
ftp> put c:...\WSE040PS.BIN
QGPL/WSE040PS
ftp> quit
C:\>
ADDLIBLE <SCSERVER> ,where SCSERVER is your ShowCase library.
APYSCPTF DEV(*SAVF) SAVF(QGPL/WSE040PS).
[You will be prompted for the name of your
server library. Enter your library name
when
prompted]
PTF WSE040PS Successfully Loaded for
<SCSERVER>,
where SCSERVER is your ShowCase library.
DSPJRN JRN(<SCSERVER>/SCPTFLOG),
where SCSERVER is your ShowCase library.
The ShowCase jar file must be recompiled:
Downloading the FixPak
This FixPak will fix all problems described in the previous document. The FixPak must be applied only to the ShowCase STRATEGY 4.0 release. Refer to the instructions below for downloading and applying the FixPak.
Prerequisites for Applying the FixPak
Note: Before installing the FixPak, be sure to read and follow the prerequisites listed above.
Password: <password>
230 <userid> logged
on.
ftp> binary
ftp> put c:...\db2ptch.svf QGPL/UPDTSAVF
ftp> quit
C:\>
Summary of problems fixed
The Essbase/400 4.10.020 Server FixPak resolves the following:
These FixPakes are language specific. Please
download the FixPak for your language only.
Downloading the FixPak
Download the FixPak: English (1.48 MB)
Applicable
Versions
This FixPak applies to ShowCase ODBC and
Warehouse Builder version 4.0 and later.
Apply this FixPak if you are using one of
these applications. After the FixPak is applied,
the products will be upgraded to STRATEGY
4.00.040.
FixPak Installation Instructions.
The original file is saved in the BACKUP directory, which is automatically created on the drive from which the FixPak is run.
Back to table of contents to continue installation
Undoing the FixPak
If you want or need to get back to the original
files (before the FixPak was applied), you
will find them in the BACKUP directory, which
is located on the drive that the FixPak is
run from. The BACKUP directory contains a
file called unpatch.bak. This file is a script
file containing the commands necessary to
automatically restore the original files.
To restore the original files (from any operating
system environment):
Locate the unpatch.bak
Rename the unpatch.bak to unpatch.bat
At an MS-DOS prompt, type the path to unpatch.bat
(E.g., C:\ProgramFiles\STRATEGY\Desktop\Backup\unpatch.bat)
and press Enter.
OR
On the desktop, click Start > Run, and browse for the FixPak to unpatch.bat.
Click OK.
Your application is automatically restored to its pre-FixPak configuration. If you apply multiple PTFs over time without deleting the Backup directory, the BACKUP directory will contain multiple copies of unFixPak files and the related original files from each backup. You may wish to periodically clean the BACKUP directory to recover disk space. To keep the most recent backup information, keep the latest unFixPak.bak (or unbatch.bat if you already renamed it) file and the files listed in its text.
Summary of problems fixed
This FixPak resolves the following issues:
Products Affected: Warehouse Builder
This FixPak also resolves the following issues from update 4.00.030:
This FixPak also resolves the following issues from update 4.00.030:
This file describes problems corrected by one or more FixPaks for the OLAP clients of DB2 OLAP Server for AS/400, Version 7.1. Even if you have only one of the problems fixed in one of the FixPakes, you need to perform a full FixPak installation.
To install this FixPak, make sure your system has enough memory. Then download the files that match your operating systems and national languages and begin the installation. For complete installation instructions, see the OLAP Setup and User's Guide.
To stop Windows NT services:
1. Download the following file to the Windows machine on which you want to install your clients.
|
|
Contents | National
Languages |
|---|---|---|
|
|
Spreadsheet add-in for Excel Spreadsheet add-in for Lotus 1-2-3 |
Japanese
Korean Simplified Chinese Traditional Chinese English French German Italian Spanish Brazilian Portuguese Danish Finnish Norwegian Swedish Czech Hungarian Russian |
c:\tempTo change your Windows 2000 TMP User Variable and TEMP Environment Variable, take these steps:
Your applications are automatically migrated to FixPak
4 when you open them.
The Hyperion Essbase calculator language can now be extended through the creation of custom-defined macros and functions.
The Java runtime environment included this FixPak is not set up for general use by other Java applications on your system. This fixpack does not define a path to the Java JRE in either your system environment variables or user environment variables; the JRE will not interfere with other Java environments already on your system.
New Calculator functions:
Member Set Functions:
Mathematical Functions:
The parallel export process works only with the multidimensional
storage manager, not the relational storage manager.
- PAREXPORT--Executes a parallel export by enabling you to specify the number of export threads to be used, export filename(s) for the data, the type of data to export, and and how the data is to be exported.
Although the following additional documentation refers to Hyperion Essbase, it applies to DB2 OLAP Server as well.
All of the latest books are also available on our Web site:
http://www.ibm.com/software/data/db2/db2olap/library.html
FixPak 4: The following books for DB2 OLAP Server
have been updated to the Hyperion Essbase
6.1 level and are shipped in this FixPak:
When using the outline API, if you frequently
encounter the error message "Cannot
create temporary file name," consider
making your temp directory (TMPDIR on UNIX,
TMP on NT) environment variable point to
a shorter directory name.
A top-down calculation is time consuming.
The application log indicates which formulas
are executed in top-down mode. Use @CALCMODE
to alter your formulas to run faster.
Some ESSBASE.CFG settings
are not displayed in the Essbase Configuration panel of the Server Information
in Application Manager. (7381, P2)
Some dialog box settings in
ESSBASE.CFG are not displayed in Hyperion Essbase Application Manager Server
> Information > Essbase configuration.
Locking and sending data
to the target of a transparent partition may not work. (12008, P2)
When using either Spreadsheet
Add-in with Free-Form interpretation or the C or Visual Basic API, an attempt
to lock and send data to the target of a transparent partition may fail
and generate the following error message: Error the 1014004 - Unable to
update members which have not been locked.
Syntax checker does not
move to the problematic line. (14020, 15997 P2)
When the syntax checker is
run in the Calc Script Editor, and if an error is found, the window may
not scroll to show the problematic line. To locate the line, you may have
to scroll through the calculation script text to find the highlighted information.
Performing an Edit > Replace
on a large calculation script will delete some portions from the calculation
script. (18490, P2)
In Application Manager, performing
an Edit > Replace on a large calculation script may stop the replace process
or delete the replaced text and may subsequently generate the following
message, "Text is not found. Do you want to start at the beginning of the
file?"
If an Excel spreadsheet
consists of unknown members, retrieving with Repeat Member Labels selected
may result in a corrupted spreadsheet. (18733, P2)
In the Spreadsheet Add-in,
retrieving for unknown members with Repeat Member Labels selected may return
scrambled data.
Column shifts to the left
after a Keep Only. (18973, P2)
In the Spreadsheet Add-in,
an attempt to perform a Keep Only may shift the first column to the left.
Database state does not
get updated when the data load is partially successful. (19176, P2)
If a data load is partially
successful when you select Database > Calculate, you may encounter the
message, "the database does not contain any data" even if the database
contains data.
NLS characters get corrupted
for object name when viewed in the server console. (19546, P2)
User, Database, and Application
names containing non-English European characters are not displayed correctly
in the server console.
In Lotus 1-2-3, NLS characters
in cascading filenames are displayed incorrectly. (19833, P2)
In the Spreadsheet Add-in
for Lotus 1-2-3, non-English European characters are incorrectly displayed
in the filename when specifying them in the prefix, suffix, or workbook
text box in the Cascade Options dialog box.
Incorrect SSAUDITR setting
in .CFG corrupts database. (19844, P2)
An incorrect SSAUDITR setting
in the Essbase.CFG may give the error message, "unable to connect to database"
when you attempt to connect to the database in any client program.
In the Application Manager
Japanese version, Field Properties dialog box contains mangled characters.
(19953, P2)
In the Application Manager
Japanese version, in the Data Prep Editor, you may find some mangled characters
in the Data Load Properties and the Dimension Building Properties tabs
of the Field Properties dialog box.
When searching for a string,
the Calc Script Editor does not scroll through to locate it. (20492, P2)
When updating a calculation
script, the Edit > Find function does not cause the window to scroll to
the next occurrence and locate the string that you are searching for.
The first part of the formula
disappears when you use Flashback. (20589, P2)
When using the Spreadsheet
Add-in with Lotus 1-2-3, an attempt to retrieve data on a formula that
has an error followed by a Flashback may cause the first part of the formula
to disappear.
EsbGetDatabaseState does
not return default or modified values. (20626, P2)
The VB API routine, EsbGetDatabaseState,
does not return correct values in the ESB_DBSTATE_T structure. In particular,
the default values for Retrieval Buffer Size and Sort Buffer Size are either
0 or incorrect. Additionally, any new values that you enter through Hyperion
Essbase Application Manager are ignored.
@SUM function does not work
correctly with User Defined Attribute (UDA). (20758, P2)
@SUM function may not work
correctly with more than one macro as its expList.
Incorrect handling of operators,
such as AND and OR inside a FIX statement. (20766, P2)
FIX command involving member
functions used with AND, OR operators may generate incorrect member sets.
While using the @CHILDREN
function, you cannot put space between the parentheses and the member name.
(21174, P2)
While using the @CHILDREN
function within a FIX statement, inserting a blank space between the parentheses
and the member name may yield an error message.
Zoom In results in an error
message if maximum number of rows exceeds 8,192. (21242, 23210 P2)
In the Spreadsheet Add-in
with Lotus 1-2-3, an attempt to zoom into more than 8,192 rows may result
in an error message.
Generating an exception
log file, while synchronizing outlines causes the application to crash.
(21293, P2)
While synchronizing outlines,
a crash may occur and an exception error log is generated when using an
alias in the partition definition.
Error in outline synchronization
with transparent partition on a shared member. (21620, P2)
During outline synchronization,
an attempt to add both shared and regular members in the same dimension
to a target database may not add the shared member, and it may give the
error message, "There is 1 Message in the application log identifying a
change that was not applied during the outline synch."
Calculation on a transparent
partition seems to run indefinitely. (21651, P2)
Two types of formulas, Constant
Assignment and Forward References, when attached to a sparse member, trigger
top-down execution. But the application log may not contain messages indicating
top-down execution.
Unable to restructure data
on an HP-UX 64-bit machine if the directory name exceeds 8 characters.
(21656, P2)
Creating directory names with
more than eight characters may generate an exception error log file and
hinder the data restructure process.
Translation for Member Selection
is incorrect. (21744, P2)
In the Spreadsheet Add-in
with Excel, Essbase Member Selection features are erroneously translated.
For example, "insert list before active cell" translation is misleading.
Also, the message at the bottom of the Member Preview dialog box is mistranslated.
This problem is noticed in Spreadsheet Add-in (Essbase Release 6.0 P1)
Japanese version.
Text type attribute member
having only numeric values does not get associated. (21748, P2)
While using a rules file to
associate the attribute members with the base member, a text type attribute
member that contains only numeric values and begins with the 0 may not
get associated with the base member.
Zoom In may cause incorrect
results if Essbase Options are checked. (21785, P2)
In Hyperion Essbase Spreadsheet
Add-in, when the options, Display > Cell > Repeat Member Labels and Zoom
> Member Retention > Remove Unselected Groups are selected, an attempt
to zoom in may cause incorrect results.
When the row header has
invalid alias name, the Excel spreadsheet shows incorrect values. (21804,
P2)
In the Spreadsheet Add-in,
if the option Use Both Member Names and Aliases for Row Dimensions is selected,
retrieving may result in incorrect values when row members contain invalid
alias names.
Case sensitivity does not
work correctly during dimension building. (21906, P2)
Case sensitivity may not function
correctly and may cause the server to freeze during dimension building.
Zoom Out does not function
correctly if Formula Preservation is checked. (21949, P2)
When Formula Preservation
is selected in the Spreadsheet Add-in, zoom out may give erroneous results.
Attribute dimension building
corrupts the outline. (22020, 22325, P2)
When a user tries to build
and associate an attribute dimension on the base dimension, Application
Manager randomly associates attributes at all levels and corrupts the outline.
Internal Rate of Return
(@IRR) function produces incorrect results. (22163, P2)
Using @IRR in a calculation
script may produce incorrect Retrieve results.
Database restructure causes
the application to crash. (22206, P2)
If a member is renamed after
another member that is deleted, the new member may map to both previous
and existing members and cause the server to crash.
"Invalid Block Header" error
following a calculation script or other long running update operation.
(22256, P2)
Error 1006010 or 1006016 appears following
a calculation script or other long-running
update operation. Although the problem has
been corrected by this FixPak, the error
message indicates that the database was corrupted.
This FixPak will not fix corruption that
has already occurred. You must therefore
restore the most recent clean backup of the
database or start over with an empty database.
Lotus 1-2-3 results in an
error message if #MISSING is set to 0. (22333, P2)
In Spreadsheet Add-in with
Lotus 1-2-3, if the #MISSING label is set to zero and there is no data,
an error message is produced stating, "The sheet contains an unknown member
0."
Dimension building for base
member hierarchy does not work properly. (22350, 22695 P2)
Dimension building for a base
member hierarchy may not work properly when using the generation build
method. The rules file does not contain attribute member associations,
but when the rules file updates the outline, it assigns attributes to members
of different levels.
A crash may occur when verifying
an outline containing lengthy date and numeric attribute member names.
(22395, P2)
If a full name of a date or
numeric attribute member, including parents and ancestors when applicable,
is larger than 80 characters, an attempt to save or validate the outline
may cause a crash.
Loading and unloading data
for a 250 GB database may result in a memory leak. (22412, P2)
When starting DB2 OLAP Server,
when you build dimensions by Dynamic Dimension Build, upload data by Dynamic
Data Load, or calculate and then shutting down the product, allocated memory
may not be released and the operating system may crash.
Passwords visible on UNIX
when using the secure mode. (22491, P2)
When DB2 OLAP Server is installed
on UNIX in secure mode, passwords may still be visible.
The C API routine, ESSCMD
EssOtlOpenOutlineQuery, leads to a memory leak. (22543, P2)
The C API function, EssOtlOpenOutlineQuery,
allocates memory that is not released in EssOtlFreeMembers as it should
be, which eventually seriously hinders system performance.
After default calculation
lower level data may override upper level data. (22742, P2)
When Aggregate Missing is
off, lower level consolidation that results in #Missing may override upper
level data.
Data not rolling up properly
when using an attribute dimension. (22756, P2)
When an attribute dimension
is used, the Spreadsheet Add-in may not generate correct data roll-up.
The ESSCMD GETDBSTATS fails
when executed. (22816, P2)
Then ESSCMD GETDBSTATS may
not function if it is executed on a cube whose dimension name consists
of a particular character, such as '%n.'
The ESSCMD EssOtlQueryMembers
returns wrong result when outline exceeds 16K members. (22853, P2)
The outline API, routine EssOtlQueryMembers,
does not return the correct number of outline members when the outline
contains more than 16K members.
Sparse restructure causes
Linked Reporting Object (LRO) counter to be reset. (22926, P2)
When adding a new LRO immediately
after a sparse restructure, the following error occurs: "Object # already
exists".
Unable to initialize GRID
API when Regional Setting is German (Austrian). (22962, P2).
The GRID API will fail to
initialize when the Regional Setting in the Control Panel is set to German
(Austrian).
Memory leak in EssVSetSheetOption
and EssVSetGlobalOption. (22998, P2)
The VBA routines, EssVSetSheetOption
and EssVSetGlobalOption, leak memory on Windows 95/98 clients, causing
degraded performance when they are used repeatedly.
"Cannot access object: Ess00000.TMP"
error when running 4 batch jobs. (23034, P2)
When running concurrent programs
that use the Outline API, Hyperion Essbase OLAP Server occasionally cannot
create temporary file names and displays the error message, "Cannot access
object: Ess00000.TMP."
Hyperion Essbase Application
Manager is not displaying the Disk Volume. (23059, P2)
The Storage tab on the Database
Settings dialog box in Application Manager contains a table that is not
always in synchronization with the Disk Volume edit field or updated when
changes are made to the disk volumes.
EssCell may not work for
Dynamic Time Series. (23119, P2)
In Hyperion Essbase Spreadsheet
Add-in, running EssCell (Y-T-D) on an outline with attributes may return
#MISSING instead of the Y-T-D value.
EssVGetDataPoint returns
incorrect values for Dynamic Time Series. (23130, P2)
When using Dynamic Time Series
in a spreadsheet to return a specific H-T-D (April), the EssVGetDataPoint
mistakenly returns "H-T-D" instead of "H-T-D(April)."
Sparse Dynamic Calc fails
in a calculation script. (23156, P2)
If a calculation of a stored
member depends on a virtual block, either through parent-child relationship
or through formula, calculation of the virtual block may not be triggered
correctly, causing incorrect results for the stored member.
GRID API crashes with multiple
concurrent logins and logouts on a multiprocessor machine. (23175, P2)
The GRID API may crash on
connect or disconnect when using multiple threads on a multiprocessor machine.
Data is incorrect when aggregated
with Create Block on Equation and from bottom-up. (23274, P2)
When using SET FRMLBOTTOMUP
ON, the dependencies of top-down formulas may be processed incorrectly,
causing some blocks to be missed during calculation.
EssVGetDataPoint function
does not return correct data for a first page header. (23275, P2)
EssVGetDataPoint function
may not work properly for the first page header of a query unless the cell
being inquired is in the first column.
Division by values between
.000000000000004 and -.000000000000004 results in a #MISSING. (23375, P2)
In FixPak 4, the division
with denominator values between .000000000000004 and -.000000000000004
may result in a #MISSING.
While ignoring the TimeStamp
parameter, EsbGetLogFile returns the entire log. (23396, P2)
The Visual Basic API routine,
EsbGetLogFile, ignores the TimeStamp parameter and returns the entire log
file rather than the entries of the log file produced after the date and
time specified by the TimeStamp parameter.
@XREF triggered by a query
will not automatically log off the source database. (23470, P2)
Queries involving Dynamic
Calculations with @XREF leave users logged into the remote sources of @XREF
references.
The server produces incorrect
results if the number of blocks to be locked exceeds the LOCKBLOCK setting.
(23656, P2)
When using formulas on sparse
members for which the number of blocks to be locked exceeds the LOCKBLOCK
setting, the current LOCKBLOCK setting may not return correct values.
After moving members of
a sparse dimension, the server crashes while doing a base level restructure
(23925, P2)
After moving a sparse dimension
member, an attempt to restructure at the base level may result in a network
error, 10054, or may even cause the data to disappear.
Back to table of contents
The following problems are fixed in FixPak 3.
DB2 OLAP Integration Server
Is Unable to Obtain a Read Lock Using Oracle (23433)
A date format problem occurs
when using certain combinations of the MERANT ODBC driver and the Oracle
relational database management system (RDBMS). In this circumstance, DB2
OLAP Integration Server is unable to lock a model ormetaoutline in the
OLAP Metadata Catalog, thus preventing access to OLAP models or metaoutlines.
Error message "Cannot access
object: Ess00000.TMP" when using the Outline API. (23034, P3)
When running concurrent programs
that use the Outline API, DB2 OLAP Server occasionally cannot create temporary
file names and displays the error message "Cannot access object: Ess00000.TMP".
HP-UX and AIX only: correct
header file versions required. (23460 P3)
FixPak 2 contained incorrect
versions of API header files for the HP-UX and AIX platforms. If you installed
the FixPak 2 C API for these platforms, you should install FixPak 3 over
your FixPak 2 installation.
Database fails to load with
buffered I/O in effect and an Index Page size less than 8K. (21733, P3)
When buffered I/O is in effect
(see the information message in the application log) and the user specifies
an Index Page size less than 8K, DB2 OLAP Server over-allocates memory
to the Index cache during database startup. If the user then specifices
a large Index cache (for example 500M), the Index cache memory allocation
might consume most or all of the available memory, in which case the database
fails to load.
The following problems are fixed in FixPak 2.
Cannot Tag a Parent and
a Child Dynamic Calc and Store with Dimension Build. (14688, P2)
In the Application Manager,
a parent with a single child cannot be tagged with Dynamic Calc and Store
using Dimension Build.
EsbLROAddObject() May Give
Error 1030718. (17507, P2)
If the usOption parameter
of EsbLROAddObject is set to ESB_STORE_OBJECT_API, the API may produce
error 1030718: Invalid object option for cell not entered.
The Server May Not Be Able
to Create Database Whose Names Contain Certain Foreign Characters. (18532,
P2)
If a database name contains
certain foreign characters, like Kanji or Katakana, the Application Manager
may produce an error 1019002: Failed to create database.
An Attempt to Create and
Delete a Chart on Lotus 1-2-3, Release 9.0 May Disable the Double-Click
Drilling Function of the Mouse. (18719, P2)
When creating and deleting
a chart on the spreadsheet using DB2 OLAP Server V1.1 FixPak 7 (Essbase
5.0.2 P7) with Lotus 1-2-3 Release 9, may disable the double-click drilling
function.
Server Crashes During Extremely
Heavy Concurrent Update Workload. (19397, P2)
Server crashes during extremely
heavy concurrent update workload.
Excel Does Not Prompt to
Save When Essbase Cascade Is Performed. (19431, P2)
In the Spreadsheet Add-in,
if a cascade is performed the users are not prompted to save the file on
exit.
Database Setting "Create
block on equation" Behaves Differently After Release 5.0.2 P9. (19496,
P2)
When "Create blocks on equation"
is enabled, execution of certain formulas during calculations may clear
contents of some data blocks.
Essbase EssRetrieve Macro
Lock Option for 2 and 3 No Longer Works for Lotus 9.1. (19522, P2)
The lock options 2 and 3 available
for the EssRetrieve macro may no longer work for Lotus 9.1. When EssRetrieve
macro is run with EssSend macro, the following error message appears in
Lotus: "Unable to Update Members Which Have Not Been Locked."
5.0.2 P10 Locale Files and ESSBASE.MDB Are
Not Replaced in a New FixPak Installation.
(19775, P2)
FixPak installation does not update <ARBORPATH>
/bin/essbase.mdb or locale files because
they are read/only.
Long Member Formula Gets
Truncated with Member Load Using Rules File. (19902, P2)
An attempt to load members
using rules file fails when long member formulas are truncated in the member
load rules file field. But if the same member formula is entered manually
using the member formula editor text box, then it works fine.
ESBGetLogFile Will Not Get
the Server Log File Unless Application Name Is Undefined. (19936, P2)
The VB API routine EsbGetLogFile
will
not get the server log and will return a non-zero value when the AppName
parameter is explicitly set to null. It only works properly when the AppName
parameter is undefined.
EssVRetrieve (Empty, Empty,
1) and EssVFlash (Empty) Use 100 % of CPU. (19946, P2)
EssVRetrieve or EssRetrieve
with the range parameter is set to empty it may use close to 100% of the
CPU for 2-3 minutes. Furthermore, after the retrieve, EssVFlash may use
close to 100% of the CPU.
Volume Spanning Has Been
Set but Index File Creation Is Not Rolling Over to the Next Volume. (19973,
P2)
The error 1019028: "Out of
disk space, unable to write information to file," appears when a new page
file is created and the current disk volume has less than 1024 bytes of
available space.
Retrieve Returns Invalid
Values on Certain Databases with Circular Dependencies Between Blocks.
(20158, P2)
If a circular dependency between
blocks exists, retrieval of Dynamic Calc values may produce incorrect results.
Retrieval Through C API
Renders Incorrect Results When Compared to Excel. (20283, P2)
An Essbase report containing
a member name in quotes immediately followed by an '!' without any space
in between may not get recognized. This may result in a row with the unrecognized
members to repeat the value from the row above.
EssOtlFreeMembers() Is Declared
Twice in ESSOTL.H. (20409, P2)
API programs that include
the file ESSOTL.H do not compile because EssOtlFreeMembers() is declared
twice.
Calc Never Finishes Across
a Transparent Partition. (20579, P2)
Transparent partitions may
cause database calculation to run infinitely.
Renaming a Member with Shared
Attribute Incorrectly Causes Complete Restructure. (20764, P2)
In a time dimension, an attempt
to add, rename, and categorize members as shared members in the data storage
may rapidly reduce the page size indicating that complete data restructuring
has taken place. But upon each time, if a shared member is deleted or added
to the outline, and the outline is saved, the page file does not change,
thus, indicating that data restructure is not taking place.
Attributes with Lengthy
Text Names May Crash the Application. (20795, P2)
In a Hyperion Essbase outline,
if the sum of all the text characters for attribute member names exceed
80 characters, saving or verifying the outline may crash the application.
Spreadsheet Retrieval Causes
the Application to Crash and Core Dump on HP-UX. (20813, P2)
In the Spreadsheet Add-in,
when using a specific spreadsheet view where the Essbase option Use Both
Alias and Member Name is enabled and where some dimensions are not represented,
performing a Zoom In will cause the application to crash. A core dump may
also be created as a result of the application crash.
EssVSetOption Does Not Work.
(20866, P2)
In the Spreadsheet Add-in,
the use of EssVSetOption may not work if the focus is on any of the VB
controls at the time of the calls.
Unable to Synchronize an
Outline After the Outline Is Revised for Transparent Partition. (20904,
P2)
An attempt to re-synchronize
outlines of transparent partitioned databases may disable the Edit
and Apply option buttons on the Synchronize Outline dialog box.
Sample Report Generates
Error. (20913, P2)
Running Sample report asym.rep
generates an error message: "incorrect asymmetric report [8] records processed."
This has been fixed only in the Japanese version.
Right Click of the Mouse
to Collapse Member Values Displays Irregular Layout with Spreadsheet Add-in.
(20916, P2)
In the Spreadsheet Add-in,
if Repeat Member Labels and Use Both Member Names and Aliases for Row Dimension
settings are enabled, an attempt to collapse data to higher levels may
display irregular layout for member names.
When Substitution Variables
Are Set to Validate a Calc Script an Error "Unknown Member" Is Generated.
(20927, P2)
When running a calc script
that is associated with an outline, the application generates an error
message: "unknown variable or member name," if the substitution variables
are a substring of another.
VB API Crashes on EsbOtlGetMemberInfo.
(20941, P2)
VB API crashes when the API
call EsbOtlGetMemberInfo is used for a text attribute that returns a null
string value.
Report Script with a Substitution
Variable May Result in an Error Message in Double-Byte Platforms. (20945,
P2)
An attempt to run a report
script repeatedly on a double byte platform with a substitution variable
added to may result the following error message: "10001070 UNKNOWN LAST
MEMBER FOR _uY-T-D_v IN REPORT."
Performance Problem with
Dimension Build for Aliases on Shared Members. (20997, P2)
When doing a Dimension Build
on an outline where a large number of shared members that have aliases
are being added, the dimension build may become slow.
If There Is More than One
Substitution Variable, Changing One Value May Cause Some of the Previous
Substitution Variable to Disappear. (20999, P2)
If more than 1 substitution
variable is defined, changing the value of any one substitution variable
may cause the first or the previous substitution variable to disappear.
Record #65536 Is Missed
When Doing a File/Update Outline. (21000, P2)
Record #65536 is missed when
doing a File/Update Outline with a large data file (having more than 65535
records).
In the Japanese Application
Manager, Except for the Active Application, No other Application Names
Are Listed for Copying. (21001, P2)
Unlike the Application Manager
English version, the Japanese Beta of DB2 OLAP Server 7.1 (Essbase Release
6.0 Japanese Beta) does not provide any choices of application names to
be listed for copying to the database.
Some Items Are Truncated
and Misaligned in Server Information Dialog Box and Database Information
Dialog. (21002, 21035, P2)
Some items are truncated and
misaligned in the Application Manager Server Information dialog box and
Database Information dialog box.
Attribute Query with Shared
Members and Two-Pass Calc Members May Cause Server to Crash. (21099, P2)
On AIX 4.3.3 server, in ESSBASE.
CFG file, if the setting is OUTLINECHANELOG TRUE, an attempt to add a member
and save the outline may generate an exception log.
In the Japanese Spreadsheet
Add-in One of the Error Messages Is Not Correctly Translated. (21135, P2)
In the Spreadsheet Add-in,
if Essbase Member Selection menu is selected then an attempt to select
a member will give the incorrectly translated message "1 no 22 sentak saremashita."
Clicking a Member Cell May
Clear the Spreadsheet. (21159, P2)
In the Spreadsheet Add-in,
when dimensions listed in the column heading appear in only one row, double-clicking
a data cell may clear the spreadsheet.
Renaming a Logical Column
Name in a Model Causes Member Load to Abort. (21184, P2)
When the contents of a FIX
statement results in an empty list, the OLAP server ignores the FIX statement
and performs the calculation on the whole database.
In the Japanese Application
Manager, Event Log Displays Overwrapping Characters When Scrolled to Left.
(21188, P2)
In the Application Manager,
event log displays overwrapping 2-byte characters when the window scrolls
to right and then scrolls back to left.
Escape Characters ("\) Do
Not Work Properly in DB2 OLAP Server V1.1 FixPak 7 (Essbase 5.0.2 P11).
(21189, P2)
The Escape characters used
in ESSCMD to update substitution variables fail when used with FixPak 11,
but work fine for FixPak 7.
Adding Members to Outline
with OUTLINECHANGELOG TRUE Crashes the Database. (21190, P2)
On AIX 4.3.3 server, in ESSBASE.
CFG file if the setting is OUTLINECHANELOG TRUE, an attempt to add a member
and save the outline may generate an exception log.
Drill-Through May Not Work
When Outline Has Attribute Dimensions. (21202, P2)
In the Spreadsheet Add-in,
invoking Server Drill-Through may generate an error message.
The Multiple UPDATEVARIABLE
Command Updates the First Variable. (21207, P2)
In DB2 OLAP Server V1.1 FixPak
11, when running the calc script, multiple UPDATEVARIABLE commands only
update the first variable.
Dynamic Calc May Generate
Inconsistent Results. (21215, P2)
In the Spreadsheet Add-in,
retrieval may generate inconsistent results for the same member combination
depending on the view and order of retrievals.
Loading Data by Using an
Excel Workbook with Formulas or Custom Text After the First Sheet Crashes
the Application. (21219, P2)
In the Spreadsheet Add-in
DB2 OLAP Server Version 7, loading data using an Excel spreadsheet as a
source, if there are formulas or custom texts on the sheets after reading
the first sheet the application crashes.
Loading Data with Rules
File Set with "Add to existing value" with #MISSING
After 0 Value, Gives #MISSING. (21272, P2)
In a rules file when loading
data is set with "Adding to the existing value" and if you load data with
#MISSING
after a value of 0 is loaded, the Retrieve instead of returning 0 returns
#MISSING.
The Option CALCOPTCALCHASHTBL
TRUE Causes Inconsistent Results. (21300, P2)
In some cases when the CALCOPTCALCHASHTBL
is set to TRUE in the ESSBASE.CFG file, incorrect data values may be calculated.
Report Script Produces Different
Results from Release 5.0.2 P11 to 6.0 P1. (21305, P2)
In the Application Manager,
a report script with more than one MASK command produces different output
from Release 5.0.2 P11 to 6.0. P1. The file output in 6.0 P1 is larger
than 5.0.2 P11.
Esssvr Crashes When Performing
Dense Restructure. (21501, P2)
Essbase server generates a
general protection fault while doing dense restructure for level 0 data.
Application Manager Crashes
When Viewing a Member with a User-Defined Attribute (UDA) List Display
Larger than 4k. (21534, P2)
If a member has a UDA that
is greater than 4K, when the outline is expanded in the Outline Editor
where such a member with a UDA exists, Application Manager crashes.
Wording of Grandparent and
Parent option of Member Name Format in Application Manager Is Incorrect
(21574, P2)
In the member name format
panel of the attribute member names dialog of Application Manager, the
member name format grandparent and parent is not correct. It should read
grandparent.
Retrieval on a Dynamic Calc
Member Across Transparent Partitions May Be Slow on 5.0.2 P11. (21636,
P2)
In the Spreadsheet Add-in,
retrieval on a Dynamic calc member in a transparent partition may be slower
in 5.0.2 P11 than in 5.0.2 P7.
In the API EsbSetUser, if
the PwdChgNow Option Is Set to True, then the User Is Prompted to Change
the Password Only One Time. (21683, P2)
If the Application Manager
Global Server Setting for the "Number of days before user needs to change
password" is set to greater than 0, and the EsbSetUser option PwdChgNow
is set to True, then the user is requested to Change Password only once
upon the first login.
Attribute Calc Does Not
Aggregate Values from Upper Level Shared Members. (21684, P2)
Attribute calc does not aggregate
values to the parent of a shared member, if the shared member is related
to an upper level member that has base members as its children.
Retrievals on a Transparent
Target Database Take Longer on 5.0.2 P11 than on 5.0.2 P7. (21692, P2)
A retrieval on a target database
with three source databases takes approximately 35 seconds with FixPaks
11 and 12 for DB2 OLAP Server V1.1 (5.0.2 P11 and 5.0.2 P12) compared to
approximately 6 seconds with FixPak 7 for DB2 OLAP Server V1.1 (5.0.2 P7).
No libglobalc.so in Essbase\api\lib.
(21768, P2)
FixPak 11 for DB2 OLAP Server
V1.1 (5.0.2 P11) UNIX installation does not put libglobalc.so into the
Essbase\api\lib directory. This may result in compiler errors when using
the API.
Calc Time Degrades from
FixPak 10 to FixPak 12 for DB2 OLAP Server V1.1. (21772, P2)
Calc script time increases
from FixPak 10 of DB2 OLAP Server V1.1 (5.0.2 P10) to FixPak 12 (5.0.2
P12).
User with Create/Delete
Permissions Cannot Edit Users. (21810, P2)
Two users have been provided
with Create/Delete user permissions and without Create/Delete user permissions
respectively. If you attempt to edit the second user while logged in as
a first user who has Create/Delete permissions, the check boxes are grayed
out.
Huge Formulas with Many
Member References Can Cause an Essbase Internal error. (21821, P2)
If a formula (attached to
a member in an outline or in a calculation script) involves references
to more than a 1000 members, Hyperion Essbase server can report an internal
error "Calculator Stack Contains a NULL Object."
Not All Data Returned When
Buffer Size Is 32K. (21838, P2)
When the API call EsbGetStringBuf
is used on a particular report with a buffer size of 32767, records are
skipped in the report. The report is correct with the buffer size is 32766.
Retrieval on a Target Database
Crashes the Target Application. (21876, P2)
Retrieval across transparent
partitions with attributes could cause crashes in certain cases.
Data Load Causes Error on
the UNIX Server. (21884, P2)
On UNIX platform, loading
data with text file and rules file may generate error message, " unknown
member[...] found while processing string [...]."
In the Application Manager,
the RUN Button in the Calc Script Editor or Report Writer Dialog Box Is
Enabled When the Database Is (all dbs). (21901, P2)
When a calc script or a report
file is created and saved in the (all dbs) database dialog box in Hyperion
Essbase Application Manager, the RUN button is enabled which actually should
not be enabled.
Unable to Set Calc Scripts
as Default Calc with FIX, LOOP, and IF Statements. (21909, P2)
If a calc script containing
FIX/LOOP/IF statement is set to serve as default calculation, Essbase crashes.
The same calc script can be executed as a non-default calculation without
any problem. It is the "Set Default Calc" operation that causes Essbase
to crash.
Security Files May Get Corrupted
When Installing Version 1 FixPak 1. (21924, P2)
When migrating from DB2 OLAP
Server Version 1.1 to Version 7, additional copies of the of the database
may get created each time the server is stopped and started.
Cannot Delete Server Log
if Application Server Is Running. (22035, P2)
In the Application Manager,
an attempt to delete event log may fail if application server is running.
This is fixed in all server platforms except Windows 95/98.
EssVCascade Ignores Suppress
#MISSING
Option. (22044, P2)
The Spreadsheet Add-in VBA
function EssVCascade ignores the suppress #MISSING
flag set in Essbase options.
Changes to Original and
Shared Members on Source Do Not Synchronize Properly to Target. (22048,
P2)
Changes to original and shared
members on the source outline do not properly synchronize at the target
outline and produce an error message in application log, "There is 1 message
in the application log identifying a change that was not applied during
outline synchronization."
Calc Works in FixPak 11
of DB2 OLAP Server V1.1 (5.0.2 P11) but Causes Exception Log in Version
7.1 (6.0 P1) (Only with Data). (22142, P2)
In Versoin 7.1 (6.0 P1) execution
of formulas that contain lists of numbers mixed with member names may cause
the application to crash.
EssCell May Not Work with
Dynamic Time Series. (22184, P2)
#MISSING is
returned instead of the Dynamic Calc member value when EssCell is used
on a Dynamic Time Series member (for example, EssCell ("Q-T-D") ).
@AVG Member Formula in 6.0
P1 Causes the Server to Crash. (22189, P2)
If a Dynamic Calc member has
an @AVG member formula attached, upon retrieval, zooming in the parent
of this member causes the server to crash and generate an exception log
file.
Loading Data with Rules
File May Cause Memory Leak. (22349, P2)
Data Load with 4-GB rules
file errors after loading 10 million records.
Unloading and Loading a
Database in Read-Only Mode, Does Not Start the dbwriter. (22411, P2)
When a database is unloaded,
while in read-only mode and loaded back again, the dbwriter is not started.
So the data operations following this sequence crash the application when
it tries to initiate the dbwriter.
The following problems are fixed in FixPak 1.
Server Ignores Formulas
With Members which Contain a Dot in Their Names. (15758, P1)
The application log gives
error 1200324, if you use a "." in the member name. Furthermore in Application
Manager the Dimension Specification dialog box shows the error: "!!FORMULA
NOT LOADED!!"
No Error Is Generated for
Invalid Formulas. (15815, P1)
No Error Message is generated
if member names with a dot are not quoted.
In a Calc Script, no Error
Is Generated When there Is no Statement After an IF Clause. (17654, P1)
An IF statement not containing
a semicolon is erroneous and the error should be reported.
Insufficient Rights to Various
Essbase Tasks After Running "root.sh." (17830, P1)
After running the root.sh
file, the ownership of many files are changed from "arbor" to "root." Also,
some files cannot be opened; for example, the outline file.
If Multiple Threads Attempt
to Use Essbase APIs Concurrently, the API May Become Unstable. (18117,
P1)
Concurrent API calls may cause
instability or crashes because the API is not thread safe.
In Spreadsheet Add-in, Repeat
Member Labels Option May Cause Incorrect Retrieval. (18734, P1)
During retrievals the Repeat
Member Labels Option, if set to true may change some of the column headers
and retrieve incorrect data.
Cannot Pivot on Certain
Members When Repeat Member Labels Option Is Set to True. (18738, P1)
When Repeat Member Labels
option is set to true in the Spreadsheet Add-in, the pivot operation works
only if mouse points to a specific cell in the target row. It gives an
error for all other cells in the target row.
Incorrect Behavior if Repeat
Member Labels Option Is Set to True. (18740, P1)
When the Repeat Member Labels
option is set to true in the Spreadsheet Add-in, the Remove Only or Keep
Only operations may not function correctly.
Status Is Returned to Cell
on a Wrong Sheet After Flashback Is Called. (18802, P1)
The return value of Lotus
Spreadsheet macro may be displayed on the wrong sheet after the Spreadsheet
Add-in Flashback command is called.
Year-To-Date (Y-T-D) Changes
When Order of Months Changes. (19073, P1)
In some cases, the Y-T-D data shown in the
Spreadsheet Add-in retrieval differs when
the presentation order of month columns is
changed. This bug is a duplicate of 18147,
FixPak 11.
The Set Substitution Variable
Scope Option in the Formula Editor Shows a Problem. (19160, P1)
An attempt to reconnect to
the server after choosing set Substitution Variable Scope may result in
an error message: "Invalid Login ID - request [List Applications] failed."
EssOtlQueryMembersEx Does
not Handle Label Only Members Properly. (19207, P1)
The EssOtlQueryMembersEx API
command does not return shared or label only members.
If a Member Name Is 0 in
the Outline, Error: "Data item found before member" May be Displayed. (19291,
P1)
While using the Spreadsheet
Lock & Send feature with data set to 0 or #MISSING the error: "Data
item found before member" occurs.
No Result When Member Has
a Calc Script Formula that Contains Dynamic Member and Cross-Dimensional
Operator. (19393, P1)
#MISSING is returned upon retrieval of a
member if the value of the member is "fixed"
by a calc script that contains a Dynamic
Calc member. This bug is a duplicate of 17946,
FixPak 11.
Users who Are not Logged
Into Application Manager Are not Logged Off. (19469, P1)
Users who log on to the Application
Manager but do not log on to any applications are not automatically logged
off after some timeout. This bug is a duplicate of bug 18482, P11.
Certain Foreign Characters
May Cause the Spreadsheet Add-in to Freeze. (19479, P1)
If certain foreign characters
are used in the worksheet or file name, the Spreadsheet Add-in freezes.
Using the Down Arrow Key
in the Linked Reporting Objects (LRO) Causes the System to Crash. (19489,
P1)
In the Spreadsheet Add-in,
using the down arrow key in the LRO browser may cause the system to crash.
This problem is specific to Lotus 1-2-3 R9.0 on Windows NT.
Running Currency Conversion
Calc Script Crashes the Application. (19892, P1)
The Application Manager may
crash when running a currency conversion calc script on a database that
has attribute dimensions.
A Rules File that May Be
Saved in Application Manager In DB2 OLAP Server 7.1 May not Work. (19950,
P1)
When saved in DB2 OLAP Server
Application Manager Release 7.1, rules file for SQL import failed.
Migrating the Database Index
from DB2 OLAP Server Version 1 Format to Version 7 Format Failed with the
Version 1 .PAG File Size Between 2 GB and 2 GB Minus 8 Kb. (20008, P1)
This is a boundary case that
affected .pag files whose size is 2 Gb minus 8 Kb when being migrated from
Version 1. Note that part of this fix imposes a maximum file size of 2147475456
bytes (2 Gb minus 8 Kb) for index and .pag files in Version 7. Files
migrated from Version 1 can be a full 2 Gb on NT and 2147483647 bytes (2
Gb - 1 byte) on UNIX.
Database Without Data May
Take Long Time to Restructure. (20063, P1)
With the fix, if the database
does not have data, Link Reporting Objects (LRO), or partitions defined
on it, DB2 OLAP Server will take no time to restructure.
CopyApp Command May not
Function Correctly With Multibyte Characters. (20228, P1)
CopyApp command functions
incorrectly if the source application name contains multibyte characters;
for example, Japanese character sets such as Kanji.
If Advanced Online JFS Is
not Installed, DB2 OLAP Server Will not Start on HPUX. (20319, P1)
If Essbase is using vxfs as
its disk volumes and if advanced online JFS is not installed, then direct
I/O will not be used, buffered I/O will be used instead. Otherwise, Direct
I/O is used. This is a new behavior of DB2 OLAP Server Version 7.
Error 1200420 and 1200324:
Compiler Errors on Member Formulas. (20325, P1)
Member formulas with IF, ELSEIF,
and ENDIF statements may generate compilation errors and be ignored.
Performance Fixes for Formula
Calculation Using Certain @IS* Functions. (20679, P1)
Fixed problem which caused
performance degradation in formula calculator on cubes with large blocks;
optimized @ISLev(dimName, levName | levNum),@ISGen(mbrName) functions and
also, other functions from this family.
DB2 OLAP Server 7.1 May
Freeze on UNIX Platforms. (20684, P1)
DB2 OLAP Server 7.1 may freeze
on some faster UNIX platforms.
When the Spreadsheet Add-in
Is Installed in Excel, Excel Is Unusable from Within Internet Explorer
(IE) V5. (20688, P1)
When the Spreadsheet Add-in
is not installed, Excel works fine within IE V5; but if the Spreadsheet
Add-in is installed, basic Excel functionality does not work.
Occasionally the Server
Crashes When Users Logout After Outline Synchronization. (20717, P1)
The server may occasionally
crash with a "not responding" error when users logout after outline synchronization.
DB2 OLAP Server May Crash
Doing CALC ALL on an Outline with Attribute Dimensions. (20727, P1)
CALC ALL on an outline with
attribute dimensions may cause Hyperion Essbase to crash.
Server Rejects: @AVG("SKIP_Param",
expList) the Following Client Is out of Synchronization. (19340)
The server does not accept
quotations marks around the following skip parameters: SKIPNONE, SKIPMISSING,
SKIPZERO, SKIPBOTH. The Calc Script Editor and client outline verification
will not detect this error. When a calculation is run with this syntax
error, the application log has the following error message output:
Error parsing formula for
member (line <no>): invalid skip instruction in function .
Note that the server validation
will catch this error in the Formula Editor.
Calc Script Editor Does
Not Generate an Error Message When Reserved Words Are Not Quoted. (20343)
When validating a calculation
script, the client may not generate an error message for the incorrect
usage of a non-quoted reserved word used for a dimension or member name.
Calculation script reserved
words include calc script commands, operators, report script commands,
function names, and function arguments in addition to the basic terms,
such as AND, BEGIN, MEMBER, FUNCTION, IF, THEN, and so on. For a list of
these terms, see the Hyperion Essbase Database Administrator's Guide.
It is better not to use these reserved words as dimension names, member
names, and aliases. If you do use them as names or aliases in calculation
scripts, you must enclose them in quotation marks.
The ESSCMD Batch Job Is
Canceled When Regular User Logs out by the Supervisor CONSOLE. (20434)
When running the nightly batch
job, the application log appears and can be logged out via CONSOLE because
the Essbase script files are not locked, the user has no firewall connections,
and has read-only access to the Essbase script files.
In the Japanese Version,
Header and Footer Strings that Are Set in Cascade Menu Item Are Preceded
by Incorrect Characters. (21011)
With Japanese Hyperion Essbase
Spreadsheet Add-in for Excel, header and footer strings that are set in
the Cascade menu item are preceded by incorrect characters when printing
and previewing.
Work around: Go into Print
Preview > Setup to the Header/Footer tab and specify a custom header/footer
that does not contain the incorrect characters.
Set Member Filter in Essbase
Query Designer (EQD) Value with MBCS Displays Broken Character. (21012)
From within the Essbase Query
Designer, attempting to create a member filter using multi-byte characters
and an IME mode causes a data entry problem in both Excel and the Essbase
Query Designer.
Work around: Launch the Notepad
(or any other text editor that accepts multi-byte input), enter the multi-byte
text, copy, and paste the text into the Essbase Query Designer.
If "Allow Application to
Start" Setting Is Disabled When the ESSCMD, Call BEGINARCHIVE, Is Used,
the Application and Database Cannot Restart. (21247)
If "Allow Application to Start"
setting is disabled and a database is placed in the archive mode with ESSCMD,
BEGINARCHIVE, after stopping the application, the application and database
may not restart.
Attribute Calculation with
Sparse Two-Pass Calculation Members Returns Incorrect Value. (22752)
When the attribute query contains
a Sparse Two-Pass Dynamic Calc member, and the calculation formula refers
to some blocks that are not included in the query, the result of the attribute
query may not include the missing blocks.
Work around: Include Sparse
members within the calculation formula as part of the attribute query.
Cryillic characters don't
work in Outline/Calc editors
If you want to use Cyrillic
characters in the outline or calc editors, remember to change the font.
From the Options menu, select Font, and then select Cyrillic from the pull-down
box, the last item in the list.