This edition of FixPak 8 is for Japanese only. If you have DB2 OLAP Server for AS/400 7.1 installed in a language other than Japanese, do not install this edition of FixPak 8. The English-only edition of FixPak 8 is available here.
Starting in FixPak 7, you need new levels of OS/400, Java, and other software. See Before you Install for more information.
Service Level: The service levels of this FixPak are:
Problem Summary -- STRATEGY: A list of all ShowCase STRATEGY problems fixed by this and previous FixPaks.
FixPaks 7 and later FixPaks upgrade your Warehouse Manager server and Warehouse Builder client to ShowCase STRATEGY 4.5. It also adds major new components, such as DB2 OLAP Server Miner and the Warehouse Manager Client. See New Features and Changes in this FixPak for important information about these upgrades.
New levels of operating system required for server components, FixPak 7 and later:
Starting in FixPak 7, you need to upgrade your server computers to the following new levels of required software:
Additionally, the APPC communications protocol is no longer supported.
Changes in client software:
FixPak 7 and later FixPaks add support in the Spreadsheet Add-in for Microsoft Excel XP.
FixPak 7 and later adds a new component, the Enterprise Server, which runs Windows NT 4.0, Windows 2000, or Windows XP. The Enterprise Server component enables access to additional data sources. When you install Enterprise Server, the network workstation installation option is not available.
Changes in installation of Warehouse Manager and Warehouse Builder:
If you want to run both DB2 OLAP Server and ShowCase STRATEGY clients (Warehouse Manager and Warehouse Builder) on the same Windows computer, or are installing Builder and Warehouse Manager clients for the first time, follow the directions in Warehouse Manager and Warehouse Builder client components. The installation and coexistance procedures have changed.
|
|
|
|
|
|
Choose 1 of 2:
(see instructions for details) |
|
|
|
(see instructions for details) |
|
|
|
(see instructions for details) |
|
The EXE files in this FixPak might inflate to
over 100MB. Make sure you have enough disk space on your computer.
Getting the FixPak
This FixPak must be applied only to DB2 OLAP Server for AS/400 V7.1 (ShowCase STRATEGY 4.00, dated 10/16/00 or later). Refer to the instructions below for downloading and applying the FixPak.
Note: This patch will update both the OLAP server component and the Warehouse Manager server component. Before installing the patch, 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:\>
Back to table of contents to continue installation
Before Installing
Programs -> Showcase STRATEGY 4.0 toAddtionally, Builder requires the runtime clients from DB2 OLAP Server. If you have not already installed them on your computer, then follow the directions in Installing the DB2 OLAP Server Runtime Clients.
Programs -> DB2 OLAP Server AS400 7.1 Clients -> Builder
Download the FixPak and save it to a temporary directory on your PC. If you're installing from a CD, copy the builder_client/l450060j.exe file from the CD to a temporary directory.
FixPak Installation Instructions.
For Enterprise Server, the network workstation installation option is not available.
Installing the DB2 OLAP Server Runtime Clients
The runtime clients for DB2 OLAP Server must be present on the computer on which you run Warehouse Manager and Warehouse Builder.
If you have the following situation:
You cannot rollback FixPak 8 to an earlier FixPak level. When you remove FixPak 8, you delete the components from your computer. You can remove either the entire product or only the Warehouse Builder and Warehouse Manager components.
Back to table of contents to continue installation
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 FixPaks, you need to perform a full FixPak installation.
Before installing this FixPak, make sure your system has enough memory. For complete installation instructions, see the OLAP Setup and User's Guide.
FixPak 7 and later FixPaks add support in the Spreadsheet Add-in for Microsoft Excel XP.
FixPak 4 and later FixPaks make the following changes in the levels of software supported by the OLAP clients of DB2 OLAP Server for AS/400 7.1:
The client installation program copies the Java files to your workstation and sets up the environment variables that OLAP Miner needs to access the Java files. To confirm these changes, check the following environment variables on Window NT and Windows 2000:
JREHOME=%ARBORPATH%\java\jre
CLASSPATH=%ARBORPATH%\java\jre\lib\ext\jaxp.jar;
%ARBORPATH%\java\jre\lib\ext\parser.jar;%CLASSPATH%
If you remove these variables on Windows 2000 and then want to restore them, add this variable to your PATH statement:
%JREHOME%\binOn Windows NT, you would add this variable to your PATH statement:For example, you could set your PATH to the following value:
PATH=%JREHOME%\bin;%PATH%
C:\Program Files\IBM\DB2 OLAP Server\java\jre\binFor example, you could set your PATH to the following value:
PATH= C:\Program Files\IBM\DB2 OLAP Server\java\jre\bin;%PATH%
c:\tempTo change your Windows 2000 TMP User Variable and TEMP Environment Variable, take these steps:
The OLAP Miner client component includes a graphical user interface that guides the user through the process of setting up a deviation detection definition. This involves selecting:
The server component of OLAP Miner runs on Windows NT 4.0 and Windows 2000. The OLAP Miner client supports Microsoft Windows 95, Windows 98, Windows ME, Windows NT 4.0, and Windows 2000.For more information about OLAP Miner, see the OLAP Miner User's Guide, a new book in FixPak 7 and later. IBM DB2 OLAP Server Miner is licensed for use only with IBM DB2 OLAP Server.
MaxL is a practical, expressive interface for administering system administration in the following ways:
The STRDD (Start data distribution) and SBMDD (Submit data distribution) commands now run Warehouse Builder distribution sets by set (object) name (OBJNAME). For example, either of the following commands run the distribution set named Sales:STRDD OBJNAME(’Sales’) OBJID(*NONE)You can still run the commands by set (object) ID (OBJID). For example, either of the following commands run the distribution set with an ID of 51:
STRDD OBJNAME(’Sales’)STRDD OBJNAME(*OBJID) OBJID(51)If you are running sets from your own CL programs with the object IDs hard-coded in either the STRDD or SBMDD command, and you restore Warehouse Builder information into a server library already containing distribution definitions, the object IDs of the distribution sets will change. To avoid this problem, use the object name of the distribution set in the STRDD or SBMDD commands. See the newly updated AS/400 Administrator’s Guide for more information.
STRDD OBJID(51)
The STRSCSVR command now requires only *JOBCTL authority. The ENDSCSVR command now requires only *JOBCTL and *ALLOBJ authority.
FixPak 5 fixes defects listed in the Problem
Summary. FixPak 5 does not introduce any new function.
FixPak 4 and later adds the following features
and changes to DB2 OLAP Server V7.1:
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.
FixPaks 3 and 1.5 fix defects listed in
the Problem Summary. These FixPaks do not introduce
any new function.
www.ibm.com/software/data/db2/db2olap/library.html
In FixPak 8: The following books for DB2 OLAP Server are new or have been updated in FixPak 8:
ShowCase STRATEGY 4.5 readme file, in Japanese only.
This document is provided for reference only.
ShowCase STRATEGY Migration Guide, 2.5 to 4.5, in Japanese only.
This document is provided for reference only.
New Error Messages Document:
FixPak 8 provides an HTML document that describes what to do when you receive certain error messages. Each documented error message includes the message number, message text, potential problems that caused the error, and potential solutions. For Release 6.2, messages involve data loading, calculation, data cache, networking, and the agent. In future releases, more functional areas will be explained.
Database Administrator’s Guide improvement: FixPak 8 reorganizes the Database Administrator's Guide into three volumes to provide better access to the information. The updated version is available in English only.
Additional books updated:
FixPak 8 updates the following books:
Note: When Warehouse Builder runs a definition, it pulls data in blocks of records, inserts the data into the target table, and converts the data mapping errors in the rows of the blocks to null values.
The online API Reference incorrectly states that the C MAIN API function, EssCopyApplication, starts the application. The new application is not started and has never been in the past.
The Database Administrator's Guide erroneously stated when calculating an average, if the skip property was None, DB2 OLAP Server did not count #MISSING values when it calculated an average. The correct behavior is that if the skip property is None, #MISSING values are not skipped when DB2 OLAP Server calculates parent values, averages are not shown as exceptions. All values are counted.
Last Login on Fri Apr 20 21:52:16 2001Now the agent log message displays the following Date/Time format:
Last Login on Friday, April 20, 2001 10:57:29 AMHowever, all other date and time formats remain the same.
Therefore, if performing maintenance operations that require disabling connections, updates, or commands, you must make those maintenance operations within the same session as the one in which the setting was disabled. So while performing maintenance operations in batch mode, you must either complete all the tasks that motivated the disabling of commands, connects, or updates as part of the same session in the same script, or, disable commands/connects/updates manually in Application Manager or Administration Console prior to performing those tasks, staying logged in to that session for the duration of the maintenance operations.
Note:
The session-persistent application settings
are accessed in the following interfaces: Essbase Application Manager (In
the Application Settings dialog box, Allow Commands, Allow Connects, and
Allow Updates) Essbase Administration Console (In Application Properties,
Allow Commands, Allow Connects, and Allow Updates) ESSCMD command-line
interface: SETAPPSTATE options 6-8. MaxL language interface:
alter application
alter application
alter application
Rather than having to specify @CALCMODE(BLOCK) or @CALCMODE(BOTTOMUP) in each of your formulas, you can now set these modes once, globally. The global scope may be for all applications, a specific application, or a specific database. In your ESSBASE.CFG file, you can specify CALCMODE in any of the following ways:
CALCMODE (BLOCK | BOTTOMUP) CALCMODE <App> (BLOCK | BOTTOMUP) CALCMODE <App> <Db> (BLOCK | BOTTOMUP)For information about the purpose and operation of CALCMODE, see the online Technical Reference, Essbase Functions section.
FixPak 8 (OLAP server MR6.2.3 and OLAP client MR6.2.1) resolves the following problems in the OLAP function:
Essbase may not allow
users to edit partitions under certain conditions. (16882)
When a user (user_1) tries
to edit a partition that is locked by another user (user_2), user_1 may
continue to get an error message stating that the partition is locked even
after user_2 logs out.
The @ISGEN function may
fail when used in calculation scripts with the genName parameter. (22495)
When you use the @ISGEN
function in a calculation script with the genName parameter (instead of
genNum), the calculation may fail. The calculation script verifies, but
when you run it on the server, it returns the error message: "Error compiling
formula for member [memname] line 110: expected type [NUMBER} found [STRING]
in function [@_D2LONG]."
Replicating data from
source to target may crash the target application if mappings are not complete.
(25233, old id 29595)
In a replicated partition,
replicating data from the source to the target may crash the target application
if mappings are incomplete. The fix for this bug prevents the application
crash, causes DB2 OLAP Server to ignore the unmapped block, and writes
an error message to the target application log.
Dimension build may incorrectly
tag some members dynamic calc. (26165)
Some members in a dimension
build may be tagged dynamic calc even though the rules file is not set
to tag them dynamic calc.
Dimension build fails
if one field contains UDA. (26603)
Performing a dynamic dimension
build fails if one field in the data source contains a user-defined attribute
(UDA).
A dimension build that
runs without errors in FixPaks 4 through 7 might crash the application
in FixPak 8. (27209)
A dimension build that creates
an invalid outline runs without errors in DB2 OLAP Server 7.1 FixPaks 4
through 7 (Essbase 6.1) might crash the application in FixPak 8 (Essbase 6.2). The fix for this problem is to ensure that Essbase validates
the outline after it is build and before it is written to the server.
Alternatively, a dimension build that creates an invalid outline might fail and generate an error message, but
might not crash the
application.
Calculation with @XREF
returns memory message. (28167, old 33286)
Running a default calculation
on a database that uses the @XREF function returns an "unable to allocate
memory" message.
Data is incorrectly rounded
when <ORDERBY command is present. (28882)
Running a report script
that contains the <ORDERBY command incorrectly rounds data.
Using the CLEARDATA calculator
command may crash the application. (29193)
Running a calculation script
with the CLEARDATA calculator command may crash the application under the
following conditions:
FIX ("Diet Cola")
CLEARDATA "Diet Cola" ;
ENDFIX;
Cannot assign a Dynamic
Calc member to a stored member in batch calculation. (30725)
Running a batch calculation
that assigns a stored member the value of a Dynamic Calc upper level member
returns the following warning:
"Regular member [] depends on dynamic-calc member []"
This can occur when the formula refers to a dense Dynamic Calc member in another block.
Data load is only able
to process strings up to 32KB in length. (36324)
DB2 OLAP Server crashes
if you attempt to perform a data load with strings longer than 32KB, contrary
to what is stated in the documentation. An error message is now provided,
and the data load aborts instead of crashing DB2 OLAP Server.
The OLAP server may crash
if users retrieve data during a data load, cleardata operation, or calculation.
(36779)
The OLAP server may generate
network errors and then crash if users retrieve data during a data load,
a cleardata, or a calulation.
Large report scripts that
use the 'restrict' command may hang. (37037)
Running large report scripts
that use the "Restrict" command may hang the application and may cause
a performance degradation in other applications running on the same OLAP
server.
Restructuring a database
with a corrupt or missing .db file causes data loss. (43204)
If you restructure a database
that has a corrupt or missing .db file, the .pag and .ind files may disappear.
An attribute query with
two-pass and dynamic calc members may have incorrect results. (43262)
Certain spreadsheet retrievals
that contain attributes, two-pass calc members, and dynamic calc members
may have incorrect results.
EssCell function may fail
when retrieving Dynamic Time Series (DTS) members from the target in a
transparent partition. (43275)
Using the EssCell function
to retrieve DTS members from the target in a transparent partition may
fail if those members are part of the partitioned area.
A dimension build may
truncate some member names. (43365)
Building an outline using
a rules file may result in some truncated member names. The truncated member
names have a ">" character at the end.
Retrievals from transparent
partitions with attribute members may return incorrect data. (43403)
Spreadsheet retrievals from
transparent partitions that include attribute members (in the spreadsheet)
may have incorrect results.
Issuing a BEGINARCHIVE
command when a user has locked blocks may cause the application to crash
or hang. (43522)
If a user has locked blocks,
issuing a BEGINARCHIVE command will fail and will return an error message,
as expected. If the BEGINARCHIVE command is repeated, the application may
hang or crash. The fix for this problem prevents repeated BEGINARCHIVE
commands from causing the application to hang or crash.
Application crashes after
running calcs and doing ad-hoc retrievals. (54976)
Running calculations on
four source databases in a partition and then doing ad-hoc retrievals against
those databases may crash the application.
Moving attribute members
in a dimension build may fail. (55514)
Dimension builds that move
attribute members may fail to move those members and the following error
may be written to the err file: "Illegal data type for attribute member."
Calculations that involve
top-down members and use FRMLBOTTOMUP ON may create blocks unexpectedly.
(55773)
Calculations that involve
top-down members and use the calculation command SET FRMLBOTTOMUP ON, or
the Essbase.cfg setting CalcOptFrmlBottomUp TRUE, may create blocks unexpectedly,
causing some calculation results to be incorrect.
With quicklogin enabled,
Essbase does not update the security file every time you create an application
and database. (55816)
When running with quicklogin
enabled, DB2 OLAP Server does not update the security file every time you
create an application and database. In the event of an abnormal shutdown,
this can result in security information being lost.
Dimension builds that
add alias names with the Japanese character Hankaku kana may result in
error messages being written to the rejected record file. (55843)
Even though you can successfully
update outlines with alias names that contain the Japanese character Hankaku
kana, error messages are written to the rejected record file.
A data load may crash
the application if the user performing the operation does not have write
access to some of the cells being loaded. (55962)
Loading data may crash the
application if the user performing the data load does not have access to
some of the cells in the data load.
Reports that use the <TOP
command may crash the application. (56173)
Reports that use the <TOP
Report Writer command and include dimension names with more than thirty
characters may crash the application. The fix for this problem allows dimension
names to be up to eighty characters long.
Copying a database many
times and then viewing application information may crash the application.
(56404)
Copying a database 58 times
and then selecting App > information in the application manager may crash
the application
Parallel calculations
that use the Calc TwoPass calculation command may crash the application.
(56407, 28718)
Running a parallel calculation
that uses the Calc TwoPass command may crash the application.
With Essbase One App Option, able to copy databases (F3858)
iSeries userid previous sign-on attempt updated when a user signs in to Essbase/400 if Integrated security is enabled. (F8860)
List separator will remain the "semi-colon" when adding result column to the Expression dialog. (F9454)
Importing a query (.dbq) with a prompt will no longer result in a gpf. (F9325)
Resolved a problem whereby
names with a different CASE would generate duplicate column errors.
(F9414)
FixPak 7 (STRATEGY 4.50.000 and Essbase 6.1.4) resolves the following problems in the OLAP function:
Formulas containing the
@PARENT or @ANCEST functions with two parameters may generate syntax errors.
(20851, R614)
@PARENT and @ANCEST functions
work as expected only if the first argument is a member of the first dimension
in the outline. If you request a second parameter that is not from the
first dimension in the outline, DB2 OLAP Server may display formula syntax
errors such as: "Error: Invalid number of parameters for this function."
Incorrect results from
the member formula A=B/-C. (21993, R614)
When DB2 OLAP Server calculates
the member formula A=B/-C, it may multiply B and -C instead of dividing
B by -C.
Increase in retrieval
times between 5.0.2p13 and 6.1.0p3a. (22494, R614)
Retrievals from the same
spreadsheet view may take longer on 6.1.0p3a than they do on 5.0.2p13.
A Partition validates
in 5.0.2p13 but does not validate in 6.1.0. (23360, 26108, R614)
When you validate a correctly
defined partition in 6.1.0, the following error may be returned: "Cell
count mismatch: area for slice [1] members per dimension." The same partition
validates without errors on 5.0.2p13.
ESSCMD scripts that contain
ENABLELOGIN/DISABLELOGIN commands prevent subsequent scripts from processing.
(23763, 26101, R614)
When an Esscmd script contains
the ENABLELOGIN/DISABLELOGIN commands, actions specified in the script
are processed, but the Esscmd process may be left running; therefore, if
another script is scheduled to run after it, the second script will not
be started.
Selecting a linked partition
in the Linked Object Browser brings up a blank spreadsheet. (23921, 26098,
R614)
After you select a linked
partition from the Linked Objects Browser, Essbase may display an empty
spreadsheet that is not connected to the source database.
Running a calculation
that uses the @XREF function may crash the application. (24198, R614)
While running a calculation
that uses the @XREF function, the Essbase application may crash.
Certain spreadsheet retrievals
cause application errors. (24413, 26102, R614)
Certain spreadsheet retrievals
containing member formulas and dynamic calcs may cause application errors
and crashes.
The @CALCMODE function
causes application crash during a calculation on Microsoft Windows 2000.
(24745, R614)
On Microsoft Windows 2000,
when you run a calculation that uses the @CALCMODE function, the OLAP application
may crash and Essbase may create an .xcp log.
Retrieval from a partitioned
database may cause the OLAP application to crash. (25091, R614)
A retrieval from the target
of a transparent partition may cause the OLAP application to crash if the
spreadsheet includes a sparse dynamic calc member that has a self referencing
member formula.
Error when drilling down
in a spreadsheet if the outline has two or more attribute dimensions. (25212,
26104, R614)
Drilling down in a spreadsheet
that is connected to an outline with two or more attribute dimensions may
cause Essbase to display an attribute dimension in the wrong position and
to display the error message "currently, multiple reports per retrieval
is not supported."
Error when validating
a correctly defined partition if a previous validation attempt resulted
in an error. (25215, R614)
When validating a correctly
defined partition definition, DB2 OLAP Server may display the following
error message: "Unable to open file (C:\Docume\Admini\Locals\Temp\Ess00000.tmp)."
This occurs after the following sequence of events:
Data retrieval times may
be much longer on Version 7 FixPak 4 (and later) than on Version 1.1. (25735,
R614)
On outlines that contain
many dense dynamic calcs, spreadsheet retrievals that take a few minutes
on Version 1.1 may take several hours on Version 7, FixPak 4 and
later.
A temporary Excel book
file is not erased after the Spreadsheet Add-in is closed. (25764, R614)
When the Essbase Cascade
feature is used to create multiple worksheets with the Spreadsheet Add-in,
a temporary Excel book file remains after the Add-in is closed.
"Retrieve and Lock" incorrectly
displays non-missing data as #Missing. (26105, 25214, R614)
When a retrieval contains
errors and "Retrieve and Lock" is selected from the Essbase drop down menu
in the Excel Add-in, DB2 OLAP Server may display #Missing in non-missing
data cells.
A report takes 24 hours
to run after adding an attribute dimension to the outline. (26451, R614)
When the outline is modified
to add an attribute dimension with one attribute, a report that previously
took only 4 minutes to run now takes 24 hours to run. The attributes are
not being referenced at all in the report script.
The Essbase agent and
clients may hang after repeated unsuccessful attempts to load applications.
(26726, 24506, R614)
After repeated unsuccessful
attempts to load applications, and when the number of file descriptors
is too low, the Essbase agent may display the error "Network error [24]"
repeatedly until the Essbase agent and clients hang.
DB2 OLAP Server may skip
some disk drives specified in the DISKVOLUME settings. (26808, R614)
If Essbase is using buffered
I/O, it may not use the order specified in the DISKVOLUME settings when
spanning disk drives.
Certain calculations take
much longer to run in Version 7 FixPak 4 (and later) compared to Version
1.1. (26932, R614)
Some calculation times may
be much longer on Version 4 FixPak 4 and later than on Version 1.1.
Updating a database after
a database copy may cause an application crash. (26984, R614)
An application may crash
with the error message "1080021 (Invalid transaction handle [0x120017]
passed to the Storage Manager for database [V_ini])" after the following
sequence of events:
Essbase completes the
processing of a dimension build with 100 attribute dimensions, but it does
not allow the resulting outline to be saved. (27424, R614)
After completing a dimension
build with 100 attribute dimensions, DB2 OLAP Server fails to save the
resulting outline. It displays the error message "Unable to read information
from [ARBORPATH\App\AppName\DbName\DbName.otn]" and and the outline
is not saved.
The PATH statement may
be invalid after the Spreadsheet Add-in is installed. (27523, 27916, R614)
If the last character is
the PATH statement is a space, the PATH may become invalid when the Spreadsheet
Add-in is installed.
DB2 OLAP Server incorrectly
interprets certain distinct Japanese characters as the same character.
(27568, R614)
DB2 OLAP Server may fail
to recognize that certain Japanese characters are different, resulting
in error messages during some operations. For example, when two distinct
characters are added as member aliases, DB2 OLAP Server may return the
error "Record #1 - Alias already used as a member name (3314)."
OLAP Server may crash
during calculation that includes the @WITHATTR function. (27572, 23691,
R614)
When a calculation includes
the @WITHATTR function and specifies the "IN" operator, the calculation
may cause the OLAP Server to crash.
EsbQueryDatabaseMembers
does not display alias names for shared members. (27667, R614)
The EsbQueryDatabaseMembers
VB API function does not display alias names for shared members.
Creating many LROs and
then listing them using the API or ESSCMD causes the application server
to crash. (27698, R614)
Creating 84 LROs and using
EssLROListObjects or ESSCMD to list all of the LROs in the database may
crash the application server.
MaxL may fail to build
a partition correctly. (27700, R614)
When you build a partition
using MaxL, the partition validation may fail with the error "area 1 overlaps
area 2." When you build an identical partition using the Application Manager,
it validates without errors.
Memory leak while running
a recursive retrieval macro. (27779, 28142, 26730, R614)
Memory usage steadily increases
during a recursive retrieval macro. After about 150 retrievals, the application
may crash with the error "unable to allocate aligned memory."
Access violation error
when using EssGPerformOperation. (27844, 28314, R614)
When using the EssGPerformOperation
Grid API function within the EssBeginDrillOrLink function, an access violation
error is returned.
Results of a report script
that uses D-T-S are incorrect. (27848, R614)
Report may contain incorrect
data values when the report script uses dynamic time series (D-T-S) members.
Retrieving data from a
large outline with attribute dimensions may crash the database. (27851,
27494, R614)
Retrieving data from a large
outline with attributes may crash the database when the spreadsheet retrieval
includes attribute dimensions and a two pass calc member with a cross dimensional
dependency. When the spreadsheet retrieval does not include the attributes,
retrieving from the same outline does not cause a crash.
A dimension build may
corrupt the Essbase outline if the "EVENT 29" parameter is in the .cfg
file. (27991, 22819, R614)
If the "EVENT 29" parameter
is in the Essbase .cfg file, a dimension build may corrupt the outline.
DB2 OLAP Server may
not release memory after a retrieval. (27992, 27365, R614)
In certain cases, DB2 OLAP
Server allocates a large amount of memory for a retrieval and it may not
release the allocated memory after the retrieval is finished. The OLAP
application must be unloaded and reloaded to free the memory.
Limit of 512 applications
per OLAP server. (28061, R614)
The limit of 512 applications
per OLAP server has been lifted in FixPak 7.
Certain retrievals may
incorrectly report #Missing values. (28084, 28076, R614)
When all of the following
conditions are met, retrievals incorrectly result in #Missing values:
DB2 OLAP Server incorrectly
displays an error message when @UDA is used to create a partition. (28115,
R614)
When the @UDA function is
used to create a partition, DB2 OLAP Server may incorrectly display the
error "cell count mismatch in area ( )" when the partition is validated.
The EnableLogin Esscmd
script fails periodically with errors 1054021 and 1019031. (28138, 17980,
R614)
The EnableLogin Esscmd,
when it is part of an Esscmd script, may fail periodically with errors
"1054021 cannot modify settings for application" and "1019031 Unable to
write to [c:\ARBBORPATH\APP\AppName\AppName.app]; database is in
read only mode for backup." The second error is displayed even when the
database should not be in read only mode.
A report displays the
alias on the first member of a dimension, but it does not display the aliases
on the other members of that dimension. (28144, 27099, R614)
After running a report script,
only the alias on the first member of the dimension is displayed in the
report. The aliases on subsequent members are not displayed.
EssGConnect may not return
ESS_STS_CANCEL when it should. (28188, R614)
The EssGConnect Grid API
function does not return the value of ESS_STS_CANCEL if you press the Cancel
button or the Esc key in the Essbase System Login dialog box. An error
value is returned instead.
A dimension build that
associates attributes may corrupt aliases on other attributes. (28447,
R614)
Aliases on existing attributes
may be corrupt after a dimension build that associates attributes.
Large spreadsheet retrieval
from a partitioned database with attributes crashes the application. (28489,
R614)
The Essbase application
may crash during a large spreadsheet retrieval when the database is the
target of a transparent partition and the outline contains attributes.
Outline API functions
may fail on Windows 95. (28614, 24218, R614)
On Microsoft Windows 95,
when you use Outline API functions, the function may fail and Essbase may
display the error message: "1060044 cannot create temporary file name."
Results of some queries
that include dynamic calcs and certain functions may not be correct. (28621,
26809, R614)
When dynamic calc formulas
involve certain functions, such as @CURRMBR, @PARENT, @SPARENT, @ANCEST,
@SANCEST, results from queries that reference those formulas may not be
correct because some dynamic calcs may not be triggered properly.
Dimension build may crash
the OLAP server if set ESSLANG=Japanese_Japan.MS932@binary. (28651, 28553,
R614)
The OLAP server may crash
during a dimension build if
set ESSLANG =Japanese_Japan.MS932@binary.
Formulas that reference
dynamic calcs and contain cross dimensional operators may produce incorrect
results. (28838, 24117, R614)
When a formula references
one or more dynamic calcs and contains one or more cross dimensional operators,
results may be incorrect. The fix for this problem requires that you have
the following entry in your essbase.cfg file: EVENT 28.
Deleting members from
an outline may produce an internal logic error. (28883, 27225, R614)
Deleting members from an
outline and saving the changes may cause Essbase to display the following
error: "internal logic error 1178."
Undefined symbols adBarrGet
and adGetStat when linking with libesssql on Solaris. (29007, R614)
When linking a program with
with libesssql on Solaris, the compiler may give one or both of the following
errors:
The OLAP server may hang
when you run EssGetApplicationInfoEx. (29064, R614)
The Essbase OLAP Server
may hang when you run the EssGetApplicationInfoEx() API function before
using the CREATEAPP or COPYAPP Esscmds.
Essbase attempts to bind
a port that is out of the allowed range when it runs out of available ports
within this range. (29294, R614)
When Essbase runs out of
available network ports within the allowed range of 32768 to 33678 (incremented
by 5), it may attempt to bind a port outside of this range, resulting in
the following error message: "Error(1042010) Network Error [125]: Unable
to Bind Host Server Socket On Port [0]." Essbase should not attempt to
bind the unavailable port.
Spreadsheet retrievals
from a database that is the target of a transparent partition may cause
the Essbase application to crash. (29533, 29483, 28548)
When retrieving data from
the target of a transparent partition, the Essbase application may crash
and an .xcp log may be created.
Memory leak during some
spreadsheet retrievals. (29565)
During spreadsheet retrievals,
the esssvr process may fail to release memory after the retrievals have
completed. The OLAP server may run out of memory after running successive
retrievals.
FixPak 5 (Essbase/400 4.10.032 Server patch) resolves the following problems:
If you have filtered
access to a linked partition database, then you may encounter a server
crash while launching the partition. (13907, P3)
If you have Read-only privilege
to a filter on a linked partition database, attempting to launch the partition
may result in an exception file and a server crash.
Attempting to validate
a linked partition fails. (19115, P3)
If you create a linked
partition database and map the source outline to the target outline, attempting
to validate the partition may generate the error message, "Target dimension
count mismatches in Area One."
When you perform a default
calculation containing FIX( @IDESCENDANTS(COMPANY,-1)), the database restructure
fails. (19284, P3)
When you are performing
default calculation containing FIX( @IDESCENDANTS(COMPANY,-1)) for a database,
the settings in the Set Default Calc dialog box may change from the Use
Calc Script Object option to the Use String option, and the statement FIX(@IDESCENDANTS(COMPANY,
-1) may be truncated. As a result, your attempt to perform a database restructure
may fail.
If dimension names are
similar but not duplicate, the Essbase Member Selection dialog box displays
an incorrect dimension. (19413, P3)
If an outline has similar
dimension names, the Essbase Member Selection dialog box may ignore the
dimension that is selected on a spreadsheet and display an incorrect dimension
and its members.
In Hyperion Essbase OLAP
Server, the Agent messages are mistranslated. (19476, 19937, P3)
In Hyperion Essbase OLAP
Server, the following messages may be mistranslated: "port," "ports available,"
"connections in use," and "ports in use."
The Linked Objects Browser
dialog box does not display the scroll bar. (19500, P3)
When you open the Linked
Objects Browser dialog box, the scroll bar may not be visible at the bottom
of the dialog box. The scroll bar may be displayed when you enlarge the
dialog box or try to resize the columns.
In Hyperion Essbase Spreadsheet
Add-in for Lotus 1-2-3, the context-sensitive help is mistranslated. (19508,
P3)
In Hyperion Essbase Spreadsheet
Add-in for Lotus 1-2-3, the context-sensitive helps may not be translated.
The default query name
is not translated in the Hyperion Essbase Query Designer dialog box. (19510,
P3)
In the Hyperion Essbase
Query Designer dialog box of Hyperion Essbase Spreadsheet Add-in for Excel,
the default name assigned to a new query may not be translated.
In the Hyperion Essbase
Query Designer dialog box, the drop-down list box name is truncated. (19532,
P3)
In the Hyperion Essbase
Query Designer dialog box, the Data Sort panel drop-down list box name,
Ordering, may be truncated. The problem may be noticeable in non-English
versions of Hyperion Essbase Spreadsheet Add-in.
The short cut key to
select Enable Secondary Button does not function properly. (19595, P3)
In Hyperion Essbase Spreadsheet
Add-in, in the Global tab section of the Essbase Options dialog box, the
short cut key for selecting Enable Secondary Button fails.
After retrieving data
for a new query, the mouse pointer does not change back to an arrow. (19697,
P3)
In Hyperion Essbase Spreadsheet
Add-in for Lotus 1-2-3, after retrieving data for a new query in the Hyperion
Essbase Query Designer dialog box, the mouse pointer may not change back
to an arrow.
F1 key does not consistently
display help in Hyperion Essbase Spreadsheet Add-in. (19918, P3)
In Hyperion Essbase Spreadsheet
Add-in, the F1 key does not consistently display Essbase Help.
In non-English versions
of Hyperion Essbase OLAP Server, while initializing Essbase.exe, the server
requires the English characters. (19988, P3)
In non-English versions
of Hyperion Essbase OLAP Server, such as on German NT, while initializing
Essbase.exe, the confirmation message accepts the English alphabet "Y"
instead of a language-independent value.
The Find option in the
Edit menu of the Member Selection dialog box does not function properly.
(20266, P3)
In Hyperion Essbase Spreadsheet
Add-in, when you use the Find option to locate a value for a member that
is selected in the Member Selection dialog box and using a Windows Server,
the Find option may search for the value incorrectly.
Cannot delete the Server
log if the Application Server is running on Windows 95/98. (20630, P3)
In Hyperion Essbase Application
Manager, You cannot delete the Server log if the Application Server is
running on Windows 95/98.
Attempting to rename
a Boolean attribute member corrupts the outline. (20901, P3)
In Hyperion Essbase Application
Manager, if you attempt to rename a Boolean attribute member directly on
the outline and then enter the changes in the Boolean Member Names fields
of the Attribute Member Names dialog box, when you reopen the outline,
you may find the outline is corrupted.
If a dimension consists
of more than 32 members with a single non-consolidated child, the attribute
association with that dimension is erroneous. (21933, 23982, 25014 P3)
If there are more than
32 members in one dimension, and that dimension contains a parent with
exactly one child that does not consolidate to its parent, an attempt to
associate attributes to that dimension may result in a corrupt outline,
with no error message.
Attribute query with
sparse Two-Pass calculation members returns incorrect values. (22752, P3)
If 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.
The retrieval time increases
compared to the previous releases of Hyperion Essbase OLAP Server. (22836,
24397 P3)
When retrieving data on
a large number of sparse member combinations, the retrieval process is
slower than the previous releases of Hyperion Essbase OLAP Server.
Calculation script does
not set cells to #MISSING. (22961, 25168 P3)
In a calculation script,
if a formula on a sparse member results in #MISSING, cells may
not be updated.
While importing an outline
from a rules file, you receive a segmentation fault. (23115, P3)
In MaxL, while importing
an outline from a rules file, you may notice a segmentation fault.
The application crashes
while retrieving data on an attribute dimension. (23211, P3)
In Hyperion Essbase Spreadsheet
Add-in, an attempt to retrieve data on an attribute dimension may crash
the application.
The "Allow" settings
may fail if a supervisor attempts to log in. (23657, P3)
If you disallow commands,
connects, or updates through Application Manager in the Application Settings
dialog box, through the SETAPPSTATE command in Esscmd, or using the "alter
application" command in MaxL, the settings may change if another supervisor
simultaneously attempts to log in.
Shared members of a sparse
Dynamic Calc member are not aggregated. (23865, P3)
Batch calculations involving
shared members that are shared members of sparse Dynamic Calc members may
produce incorrect results.
An EQD (Essbase Query
Designer) query for more than 65536 rows crashes a spreadsheet. (23871,
P3)
Using Hyperion Essbase
Query Designer, attempting to create queries for more than the limit of
65536 rows crashes the spreadsheet.
When attribute dimensions
are added, calculations are performed incorrectly during data retrieval.
(23881, P3)
In Hyperion Essbase Spreadsheet
Add-in or Report Writer, when attribute dimensions are added, calculations
may be performed incorrectly on Two-Pass member formulas during data retrieval.
Queries involving attributes
and Two-Pass calculation members may sometimes yield incorrect results.
(23903, P3)
If a query involving attributes
references a Two-Pass member and that two-pass member is dependent in turn
on other two pass member(s) the query results may sometimes be incorrect.
The Visual Basic API
function, EsbGetApplicationInfoEx, returns incorrect number of users connected.
(23911, P3)
Although the user is connected
to an application and a database, the Visual Basic API function, EsbGetApplicationInfoEx,
may return zero users connected with no error code.
When performing a replicated
partition on a large amount of data, an exception file is generated. (24051,
P3)
In Hyperion Essbase Application
Manager, when you perform a replicated partition on a large amount of data,
the replicated partition may fail, resulting in a network error and an
exception file.
The Visual Basic API
function, EsbLROAddObject(), generates an application error. (24116, P3)
When the Visual Basic Main
API function, EsbLROAddObject, is applied to associate linked reporting
objects to a cell, the error message, "Cell: EXCEL.EXE - Application Error"
may occur.
In an outline, the dimension
order affects XREF results. (24281, P3)
XREF may return incorrect
results if the dimension order in the source cube differs from the dimension
order in the target cube.
Calculation never finishes
across a transparent partition database. (24292, P3)
Transparent partitions
may cause the database calculation to run infinitely.
Retrieving data on a
spreadsheet containing a generation name produces an exception log and
crashes the application. (24384, P3)
If you attempt to retrieve
data on a spreadsheet containing a generation name, you may encounter an
exception log and application crash.
While loading data, if
the data file consists of attribute members, some data are skipped. (24477,
P3)
While loading data, if
the data file consists of attribute members, Hyperion Essbase OLAP Server
may skip the remaining records after the first attribute member.
Using the Grid API function,
BeginConditionalZoomIn, with the report specification, {UCHARACTERS}, causes
a crash. (24521, P3)
If using the BeginConditionalZoomin
function with the report specification, {UCHARACTERS}, results in an underlined
character string longer than 127 characters, the Grid API program may crash.
During multiple bitmap
mode calculation, excessive memory is allocated. (24552, P3)
When there are many shared
members in the last sparse dimension, multiple bitmap mode calculation
may use too much memory. Set the configuration parameter MultipleBitmapMemCheck
to TRUE to prevent the excessive use of memory.
Attempting to validate
an outline while performing incremental building generates an error message.
(24557, P3)
While performing incremental
dimension building, if you try to validate the outline, the incremental
dimension building process fails and generates an error message.
If a query involving
too many dynamic calculations with complex formulas fails to execute because
of insufficient memory on the server, the application crashes instead of
the query failing. (24669, P3)
If a query involving too
many dynamic calculations with complex formulas fails to execute because
of insufficient memory on the server, the application crashes instead of
the query failing.
An attribute calculation
with Two-Pass calculation returns inconsistent results. (24786, P3)
If you attempt to perform
attribute calculations with Two-Pass calculation repeatedly, you may encounter
inconsistent results.
Programs with multiple
calls to EsbOtlGetAssociatedAttributes and EsbOtlGetMemberInfo result in
a crash. (24807, P3)
Using the Visual Basic
Main API functions, EsbOtlGetAssociatedAttributes and EsbOtlGetMemberInfo
repeatedly may crash the Visual Basic program.
Registering more than
20,000 Essbase users to Hyperion Essbase OLAP Server gives fatal error
when restarting. (24875, P3)
After registering 20,000
users to Hyperion Essbase OLAP Server, if you terminate Essbase and then
restart, you may encounter the error message, "Fatal Error: Error reading
security file [22]."
Retrieving data on a
blank cell results in an application crash. (24895, P3)
If you try to retrieve
data on a blank cell, the application may crash with an exception file.
In Hyperion Essbase Application
Manager Japanese version, the Dynamic Time Series (DTS) settings cannot
be saved. (24905, P3)
Hyperion Essbase Application
Manager Japanese version may not retain the DTS settings.
While retrieving data
on sparse dynamic calculation members, you may receive incorrect results.
(24976, P3)
If the formula is executed
in a cell mode, attempting to retrieve data on sparse dynamic calculation
members may result in incorrect #MISSING values.
The Grid API function,
EssGetApplicationInfoEx(), generates the error 1051030 when you pass a
Null parameter to it. (24982, P3)
The use of a Null value
as the second parameter in the Grid API function, EssGetApplicationInfoEx(),
generates the error message 1051030, "Application does not exist."
The Agent hangs when
another user attempts to access the same application while filters are
being verified. (25089, P3)
Hyperion Essbase OLAP Agent
may hang if one user attempts to verify a filter, while another user attempts
to access the same application.
Attempting to perform
a zoom in on attribute members may result in the Spreadsheet Extractor
error 1130001. (25127, P3)
If you attempt to expand
attribute members, you may receive the Spreadsheet Extractor error 1130001.
Attempting to retrieve
data on attribute members crashes the server. (25278, P3)
Attempting to retrieve
data on specific attribute members results in an exception log and application
crash.
Creating 60,000 filters
causes the server to crash and corrupt security files. (25298, P3)
If you try to create 60,000
filters using the ESSCMD, copy filter command, the server may crash with
an exception segmentation violation. Moreover, if you attempt to restart
Hyperion Essbase OLAP Server, you may receive an error message, "The security
file is corrupted."
A database may lose its
currency link upon stopping the Essbase Agent. (25364, P3)
If you shutdown Hyperon
Essbase OLAP Server, the currency link to your database may disappear.
Deleting a shared member
removes all data from the actual member. (25376, P3)
If you delete a shared
member, all data from the actual member may be deleted.
Attempting to retrieve
data on attribute members across transparent partitions results in incorrect
values. (25585, P3)
If you perform a retrieval
on attribute members from a target database of a transparent partition,
you may receive incorrect results.
Using the ESSCMD command,
ENDARCHIVE, the .cfg setting _SM__BUFFERED_IO TRUE results in a crash.
(25715, P3)
With the .cfg setting __SM__BUFFERED_IO
TRUE, if you attempt to complete archiving of data using the ESSCMD command,
ENDARCHIVE, or the MaxL command END ARCHIVE, the application may crash.
The .cfg setting, __SM__BUFFER_IO
TRUE, erroneously returns zero values. (25789, P3)
If the buffered IO setting
is set to True, the calculated values may erroneously return zeros.
Sub-optimal performance
for formulas executed in top-down mode. (26003, P3)
If a formula attached to
a member is executed in a top-down mode as indicated in the application
log file, performance may be sub-optimal.
Locking and sending data
to the target of a transparent partition may not work. (12008, P2)
When using either Hyperion
Essbase 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 Hyperion Essbase 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 Hyperion Essbase 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 Hyperion Essbase 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 Hyperion Essbase 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 Hyperion Essbase Application
Manager Japanese version, Field Properties dialog box contains mangled
characters. (19953, P2)
In Hyperion Essbase 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 Hyperion Essbase
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 Hyperion Essbase 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.
Creating Hyperion Essbase
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 Hyperion Essbase 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 Hyperion Essbase Spreadsheet Add-in 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 Hyperion Essbase 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 Hyperion Essbase 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, Hyperion Essbase
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 patch, the error message
indicates that the database was corrupted. This patch 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 Hyperion Essbase 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 Hyperion
Essbase OLAP Server, building dimensions by Dynamic Dimension Build, uploading
data by Dynamic Data Load, and calculating and then shutting down Hyperion
Essbase OLAP Server, allocated memory may not be released and the operating
system may crash.
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, Hyperion Essbase Spreadsheet Add-in and Report Writer 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 Hyperion Essbase 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 Hyperion Essbase OLAP
Server Release 6.1, 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.This FixPak (Essbase/400
4.10.032 Server patch) also includes the following from the 4.10.000 patch
FixPak 7 (ShowCase STRATEGY 4.50.000) resolves the following problems in the Builder function:
Products Affected: Warehouse Builder
Online HTML
books might not display properly in Netscape Navigator (n/a)
When you use
Netscape Navigator to display HTML books that are intended for a three-frame
layout, Netscape might not load the book completely, displaying only one
page of information and not displaying the table of contents in the navigation
pane on the left. If this occurs, click the Reload button on the Netscape
Navigator browser to display the book in three-frame format.
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.