************************************************************

IBM DB2 OLAP Server 7.1 
Fixpak 3 Release Notes

************************************************************
Patch file name: FIXPAK.HTM

Applies to: All platforms

Patch Date: February 2001

Identification: R6.0.0_P3
************************************************************

Important:

Fixpak 3 for DB2 OLAP Server Version 7.1 is the equivalent of patch 3 for Hyperion Essbase Release 6.0.0 plus patch 1 for Hyperion Integration Server 2.0.

If you are installing client products from a DB2 OLAP Server fixpak, you must install server products to the same fixpak level. For example, if you install a Fixpak 3 client, you must also install the Fixpak 3 server. Using older server versions with newer client versions is not recommended and is not supported.

Contents

Fixpak Installation Overview

Key

Fixpak Summary

Added Features

Problem Summary

Known Problems

Installing the Fixpak

Additional Documentation Copyright Information


Fixpak Installation Overview


This file describes problems corrected by one or more fixpaks for DB2 OLAP Server Version 7.1. Even if you have only one of the problems fixed in one of the patches, you need to perform a full fixpak installation. For instructions on downloading and installing the files in this fixpak, see Installing on UNIX or Installing on Windows, depending on your operating system. For more detailed information about installation, see the OLAP Setup and User's Guide.

Fixpak 3 for DB2 OLAP Server Version 7.1 is the equivalent of patch 3 for Hyperion Essbase Release 6.0.0 plus patch 1 for Hyperion Integration Server 2.0.  Hyperion patches are cumulative; each 6.0.0 patch contains new fixes, plus all the fixes for the previous patches.


Key

R6.0.0_P1 is Release 6.0.0 Patch 1 from Hyperion, which is in Fixpak 1 from IBM.

R6.0.0_P2 is Release 6.0.0 Patch 2 from Hyperion, which is in Fixpak 2 from IBM.

R6.0.0_P3 is Release 6.0.0 Patch 3 from Hyperion, which is in Fixpak 3 from IBM.


Fixpak Summary

R6.0.0_P3 -- Fixpack 3 fixes problems on all server and client platforms, for DB2 OLAP Server and DB2 OLAP Integration Server.

R6.0.0_P2 -- Fixpack 2 fixes problems on all server and client platforms and upgrades DB2 OLAP Integration Server to Hyperion Integration Server 2.0

R6.0.0_P1-- Fixpack Patch 1 fixes problems on all server and client platforms.


Added Features

Following are the additional support that this fixpak provides:

Problem Summary

The following problems are fixed in Fixpack 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)
Fixpack 2 contained incorrect versions of API header files for the HP-UX and AIX platforms. If you installed the Fixpack 2 C API for these platforms, you should install Fixpack 3 over your Fixpack 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 Fixpack 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 Patch Installation. (19775, P2)
Patch 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 Fixpack 7 (Essbase 5.0.2 P11). (21189, P2)
The Escape characters used in ESSCMD to update substitution variables fail when used with Fixpack 11, but work fine for Fixpack 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 Fixpack 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 Fixpacks 11 and 12 for DB2 OLAP Server V1.1 (5.0.2 P11 and 5.0.2 P12) compared to approximately 6 seconds with Fixpack 7 for DB2 OLAP Server V1.1 (5.0.2 P7).

No libglobalc.so in Essbase\api\lib. (21768, P2)
Fixpack 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 Fixpack 10 to Fixpack 12 for DB2 OLAP Server V1.1. (21772, P2)
Calc script time increases from Fixpack 10 of DB2 OLAP Server V1.1 (5.0.2 P10) to Fixpack 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 Fixpack 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 Fixpack 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, Patch 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, Patch 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.


Known Problems

Following are the known problems:

Output to Audit File (.ATX) Is Not Correct When Member and Alias Names Option Is Checked in the Spreadsheet. (18463)
When sending data in the Spreadsheet Add-In, the data sent to output file *.ATX is not correct if the Essbase Spreadsheet option Use Both Member Names and Alias for Row Dimensions is checked.

Approximately 430 Concurrent Partition User Connections Freeze the Agent. (19875)
The Agent freezes when there are approximately 430 concurrent users accessing a transparent partition. It happens most often with one target and several sources with many users doing spreadsheet retrievals from the target.

The ESSCMD Batch Job Is Canceled When Regular User Logs out by the Supervisor CONSOLE. (20434)
When running the nightly batch job, 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 Japanese Version, Header and Footer Strings that Are Set in Cascade Menu Item Are Preceded by Incorrect Characters. (21011)
With Japanese Spreadsheet Add-in for Excel, Header and footer strings that are set in the Cascade menu item are preceded 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 Query Designer (EQD) Value with MBCS Displays Broken Character. (21012)
From within the Query Designer in the Spreadsheet Add-in, attempting to create a member filter using multi-byte characters and an IME mode causes a data entry problem in both Excel and the Query Designer. Work around: Launch the Notepad (or any other text editor that accepts multi-byte input), enter the multi-byte text, copy, and past the text into the Query Designer.

The Database Size Grows When Migrating from DB2 OLAP Server V1 to DB2 Version 7 (21133)
When migrating from DB2 OLAP Server V1 (Essbase Release 5.x) to DB2 OLAP Server V7 (Essbase Release 6.x), the page file and index file size may grow.

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.

Using AND Operators inside FIX Statement can Sometimes Result in Incorrect Member Sets. (21309)
If expressions inside FIX statement have AND and OR operators or member functions appearing inside parantheses, the behavior of FIX may be incorrect.

If Repeat Member Labels option Is Enabled, Retrieve May Modify the Column labels. (21743)
In the Spreadsheet Add-in, if Essbase Options Repeat Member Labels setting is enabled, Retrieve may modify the order of the column labels.


Installing the Fixpak

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.

Physical Memory Requirements

When installing Hyperion Essbase OLAP Server 6.0, remember the following memory recommendations:
Minimum RAM 64 MB or greater (128 MB or greater for UNIX platform) base recommendation:

The base recommendation for running Hyperion Essbase and its sample applications is a 64 MB minimum. On UNIX platforms, base requirement is 128 MB of physical memory (256 MB recommended), and at least twice the MB of physical memory for swap space (when physical memory is less than .5 GB). Contact your system administrator or hardware vendor for optimum swap configuration. Start with the base amount of RAM for your platform, and then allocate additional memory to accommodate your applications.


Stopping Services on Windows NT before Installation

The installation program on Windows NT automatically stops the Window NT services for DB2 OLAP Server and its features before copying files.  In rare circumstances the install program might appear to freeze after displaying the message that it is stopping the services.  If this occurs, exit the installation and manually stop any DB2 OLAP Server services that are running.

To stop Windows NT services:

  1. Select Services from the Control Panel.
  2. From the Service list, select the service for DB2 OLAP Server and, if present, the service for DB2 OLAP Integration Server.
  3. Click Stop.



Installing on UNIX

To apply this fixpak, you need to download and install two files.  The first file contains upgrades for the server, SQL Interface, and API components for your UNIX operating system. The second file contains upgrades for the Application Manager, Spreadsheet Add-in, and other client components for your national language.

The OLAP Setup and User's Guide incorrectly states that you must be logged on with a user ID that has root privileges when you install DB2 OLAP Server on UNIX systems.  You do not need root privileges to install the product.

Downloading and Installing the UNIX Server

Download one of the following files, depending on which UNIX operating system you use, to a temporary directory on the UNIX machine on which you installed the server.
     
    Filename Contents
    aix.tar  AIX Server 
    AIX SQL Interface 
    AIX API 
    solaris.tar  Solaris Operating Environment Server 
    Solaris Operating Environment SQL Interface 
    Solaris Operating Environment API 
    hpux.tar HP-UX Server 
    HP-UX SQL Interface 
    HP-UX API
To start the server installation:
  1. On your UNIX system, expand the server file by entering the following command:
    1. tar -xf filename.tar
    from the temporary directory containing the .tar file. This command extracts the files necessary to perform a complete installation.
  2. Run setup.sh to launch the installation program.  Follow the installation instructions in the OLAP Setup and User's Guide.
  3. After the files are expanded, you can delete the .tar file.

Downloading and Installing the Windows Client

Download one of the following files, depending on your national language, to the Windows machine on which you have installed the clients.
     
    Filename Contents National
    Languages
    wincd1.zip Application Manager 
    Spreadsheet add-in for Excel 
    Spreadsheet add-in for Lotus 1-2-3 
    SQL Drill Through 
    Japanese
    Korean
    Simplified Chinese
    Traditional Chinese 
    wincd2.zip Application Manager 
    Spreadsheet add-in for Excel 
    Spreadsheet add-in for Lotus 1-2-3 
    SQL Drill-Through 
    English
    French
    German
    Italian
    Spanish
    Brazilian Portuguese
    wincd3.zip Application Manager 
    Spreadsheet add-in for Excel 
    Spreadsheet add-in for Lotus 1-2-3 
    SQL Drill-Through 
    Danish
    Finnish
    Norwegian
    Swedish
    Czech
    Hungarian
    Russian
To start the installation:
  1. command prompt, or by double-clicking the file.
  2. Run SETUP.EXE to launch the installation program.  Follow the installation instructions in the OLAP Setup and User's Guide.  Use the Custom option to install only the clients you want.
  3. After the files are expanded, you can delete the zip file.

Installing on Windows

To apply this fixpak, you need to download one file that contains both the server and client components.  If you run your servers and clients on different machines, you can download the same file to each machine.

Downloading the Fixpak

1.  Download one of the following files, depending on your national language, to the Windows machine on which you have installed the server.  If you have installed clients on other machines, you need to download the file to those machines, too.
     
    Filename Contents National
    Languages
    wincd1.zip Application Manager 
    Spreadsheet add-in for Excel 
    Spreadsheet add-in for Lotus 1-2-3 
    SQL Drill-Through 

    Windows NT Server 
    Windows SQL Interface 
    Windows API 

    Japanese
    Korean
    Simplified Chinese
    Traditional Chinese 
    wincd2.zip Application Manager 
    Spreadsheet add-in for Excel 
    Spreadsheet add-in for Lotus 1-2-3 
    SQL Drill-Through 

    Windows NT Server 
    Windows SQL Interface 
    Windows API 

    English
    French
    German
    Italian
    Spanish
    Brazilian Portuguese
    wincd3.zip Application Manager 
    Spreadsheet add-in for Excel 
    Spreadsheet add-in for Lotus 1-2-3 
    SQL Drill-Through 

    Windows NT Server 
    Windows SQL Interface 
    Windows API 

    Danish
    Finnish
    Norwegian
    Swedish
    Czech
    Hungarian
    Russian

Starting the Installation

  1. Expand the executable file by typing the name of the file (without the extension) from a command prompt, or by double-clicking the file.
  2. Run SETUP.EXE to launch the installation program.  Follow the installation instructions in the OLAP Setup and User's Guide.  Use the Custom option to install only the server or clients you want.
  3. After the files are expanded, you can delete the zip file.

Workaround for bug on Windows 2000

On Windows 2000, DB2 OLAP Server experiences problems if the TMP User Variable or the TEMP Environment Variable is longer than seven characters.  The temporary workaround is to set both variables to the following value:
c:\temp
To change your Windows 2000 TMP User Variable and TEMP Environment Variable, take these steps:
  1. On your Windows 2000 workstation, click Start -> Settings -> Control Panel -> System.
  2. Select the Advanced tab of the System Properties dialog.
  3. Click Environment Variables.
  4. In the User variables box, scroll down to the TEMP variable, highlight it, and click Edit....
  5. On the Edit User Variable dialog, change the Variable Value to c:\temp and click OK.
  6. In the System  variables box, scroll down to the TMP variable, highlight it, and click Edit....
  7. On the Edit System Variable dialog, change the Variable Value to c:\temp and keep clicking OK until you close the Environment Variables dialog.
IBM is working on this problem and will update a future Fixpack with a permanent solution.


Additional Documentation

The documentation that follows refers to Hyperion Essbase instead of DB2 OLAP Server.  This is consistent with the user documentation written by Hyperion Solutions.
 

Updated Books for DB2 OLAP Integration Server Available on Web Site

The following books for the DB2 OLAP Integration Server have been updated to the Hyperion Integration Server 2.0 level and are available on Web site for IBM DB2 OLAP Server: The books are available at the following address:

www.ibm.com/software/data/db2/db2olap/library.html

Basic Amount of RAM Needed for Most Applications

With Hyperion Essbase 6.0, you should consider starting with 0.5-1.0 GB of physical memory on the server per processor or per 50-75 concurrent users. This number can vary depending on number of users, number of concurrent batch processes, and use of memory-intensive features. See Database Administrator's Guide; Volume I, Chapter 15, "Estimating Disk and Memory Requirements for a Database ."

Memory Problems

If memory is low, the following unpredictable problems can occur: When one of the above situations occur:

Compiling Solaris Operating Environment API Programs

Solaris Operating Environment customers must create soft links to libessapi.so.1 and libessotl.so.1 in order to compile Grid API programs:


@CALCMODE Function

Function

The @CALCMODE function tells Hyperion Essbase to use the block calculation mode or the cell calculation mode when calculating formulas containing certain functions (in particular the @ISMBR function). Using block calculation mode is faster, but may introduce data dependency issues.

Using block calculation mode, Hyperion Essbase groups the cells within a block, and simultaneously calculates the cells in each group. Block calculation mode is fast, but you must carefully consider data dependencies within the block to ensure that the resulting data is accurate.

Using cell calculation mode, Hyperion Essbase calculates each cell sequentially, following the calculation order, which is based on the order of the dense dimensions in the outline. For more information on calculation order, see the Hyperion Essbase Database Administrator's Guide.

For more information on which mode Hyperion Essbase uses and on the data dependency issues, see Notes.
Syntax

@CALCMODE (CELL|BLOCK)
CELL Turns on the cell calculation mode.
BLOCK Turns on the block calculation mode.

Notes

Knowing Which Calculation Mode Hyperion Essbase Uses

Understanding Data Dependency Issues With Block Calculation Mode Data Dependency Issues With IF/ELSE and IF/ELSEIF Other Data Dependency Issues

Data dependencies can occur in formulas that do not contain IF/ELSE conditions. See Example 3 for an example of data dependency in a formula containing the @PRIOR function.

Example 1

Consider a database with two dense dimensions, Time and Accounts. The following formula is placed on the Budget Sales member of the Accounts dimension. As this is a formula containing @ISMBR applied to a dense dimension member (Budget Sales), by default Hyperion Essbase would use the cell calculation mode. However we use the @CALCMODE(BLOCK) function to specify the block calculation mode for this formula.

@CALCMODE(BLOCK);
IF(@ISMBR(Feb))
   "Budget Sales"=100;
ELSE
   "Budget Sales"=Feb+10;
According to the above formula, we expect that if the member being calculated is Feb, the Budget Sales value is 100. If the member being calculated is not Feb, the Budget Sales value is 100+10 (the value for Feb + 10).

Assume that we load the values 10, 20, and 30 into the Budget Sales data block for January (Jan), February (Feb), and March (Mar), as follows:
Jan Feb Mar
Budget Sales 10 20 30

Using block calculation mode, Hyperion Essbase calculates the members satisfying the IF condition first. In this example, Feb is the only member that satisfies the IF condition. After calculating Feb, Hyperion Essbase calculates the members Jan and Mar. In this example, the results are as expected:
Jan Feb Mar
Budget Sales 110 100 110

Example 2

Now consider the same database as in Example 1, but we place the following formula on the Budget Sales member of the Accounts dimension. As in Example 1, as this is a formula containing @ISMBR applied to a dense dimension member (Budget Sales), by default Hyperion Essbase would use the cell calculation mode. However we use the @CALCMODE (BLOCK) function to specify the block calculation mode for this formula.

@CALCMODE(BLOCK);
IF(@ISMBR(Mar))
   "Budget Sales"=Feb+20;
ELSEIF(@ISMBR(Jan))
   "Budget Sales"=Feb+10;
ELSE
   "Budget Sales"=100;
According to this formula, we want the Jan and Mar Budget Sales values to be calculated based on the Feb Budget Sales value, which is 100. We want to see the following results:
Jan Feb Mar
Budget Sales 110 100 120

Assume that we load the values 10, 20, and 30 into the Budget Sales data block for Jan, Feb, and Mar, as follows:
Jan Feb Mar
Budget Sales 10 20 30

Using block calculation mode, Hyperion Essbase calculates the members satisfying the IF condition first, followed by the members satisfying the ELSEIF condition, followed by the members satisfying the ELSE condition. In this example, Hyperion Essbase calculates the members in the following order: Mar, Jan, Feb. The results are not as we want, because the calculation of Jan and Mar is dependent on the calculation of Feb. However, Feb is calculated after Jan and Mar. The results are as follows:
Jan Feb Mar
Budget Sales 30 100 40

Example 3

The following formula calculates the members Opening Inventory and Ending Inventory using the @PRIOR function. There is a data dependency between Opening Inventory and Ending Inventory. The formula is placed on the Opening Inventory member. The example shows the results for Jan, Feb, and Mar.

@CALCMODE(BLOCK)
"Opening Inventory"=@PRIOR("Ending Inventory")+10;
"Ending Inventory"="Opening Inventory";
Before the calculation there is no data for these members (the data is #MISSING or #MI):
Jan Feb Mar
Opening Inventory #MI #MI #MI
Ending Inventory #MI #MI #MI

Using block calculation mode, Hyperion Essbase calculates the members simultaneously, taking the previous month's Ending Inventory #MISSING value as 0 for all member combinations and adding 10. This is not the required result.
Jan Feb Mar
Opening Inventory 10 10 10
Ending Inventory 10 10 10

The following formula on the Opening Inventory member causes Hyperion Essbase to use the cell calculation mode (the default for formulas containing the @PRIOR function):

"Opening Inventory"=@PRIOR("Ending Inventory")+10;
"Ending Inventory"="Opening Inventory";
The results are as follows:
Jan Feb Mar
Opening Inventory 10 20 30
Ending Inventory 10 20 30


Event 28

If your calculation performance does not improve even after tagging some dense stored (regular) members in your outline as dynamic-calc-non-store, then look for formulas in your outline or calculation script. If at least one formula contains a regular stored member that depends on a dynamic-calc-non-store member, then it is possible that EVENT 28 in the ESSBASE.CFG file can help improve the calculation times. However some of the calculation results may not be backward compatible, so your results may not match those in earlier Essbase versions.

To use this option, add the line EVENT 28 to Hyperion ESSBASE.CFG and restart Essbase.


Event 29

Essbase assumes (or implies) a shared member relationship in two situations:
  1. A parent has only one child
  2. A parent has only one child that consolidates to the parent
If you are calculating a database whose outline has implied share members and the calculation involves formulas, then in some cases implied share member values may be incorrect. If you notice such a situation you have two choices:
  1. Mark the parent as NEVER SHARE. This will trigger a dense restructure. Essbase will no longer assume the implied share relationship after the restructure.
  2. Use EVENT 29 as follows:
Upon restart, Essbase internally eliminates the implied share optimization so your formulas will return the correct results.
 

Root.sh Information

The OLAP Setup and User's Guide incorrectly states that you must be logged on with a user ID that has root privileges when you install DB2 OLAP Server on UNIX systems.  You do not need root privileges to install the product.

Solaris and HP-UX SQL interface users should not run the file root.sh unless they want to turn on the "Cache Memory Locking" feature. Furthermore, if they want to use Cache Memory Locking, they need to have root privileges to run root.sh.
 

Windows 95 Environment

On Windows 95, unlike 5.0.2 patches in 6.0 you must first install the client and next the sever, otherwise the system may crash.
 

Calc Script Variable Names

If you receive compilation errors in calc scripts, make sure that the variable names are not enclosed in quotation marks. And also, remember the first character of variable names must be alphabetic (a through z) and only characters these names may contain are numbers (0 through 9), and special characters: $ (dollar), # (pound), and _ (underscore)."
 

Spreadsheet Add-in Tools/Dialog Box

The name of the Spreadsheet Add-in in Excel's Tools/Add-in dialog box has changed from Hyperion Essbase OLAPServerDLL to Hyperion Essbase OLAP Server DLL.


Copyright Information

(c) Copyright International Business Machines Corporation 1998, 2001. All Rights Reserved.
(c) Copyright 1991-2001 Hyperion Solutions Corporation. All Rights Reserved.