This fix pack includes fixes for IBM® DB2® OLAP Server™, Version 8.1 and its features at the following service levels:
The following products are not updated in this fix pack:
For more support information, go to the following DB2 OLAP Server Support site:
http://www.ibm.com/software/data/db2/db2olap/support.html
Fix
Pack 3 is the equivalent of release 6.5.4.2 of the Hyperion® Essbase XTD
Analytic Services and release 6.5.4.1 of the Hyperion® Essbase XTD Integration
Services.
Hyperion maintenance levels are cumulative: Each level contains new fixes
and all the fixes for the previous maintenance levels.
See the Installation notes for information about issues that affect the installation of this fix pack.
| Operating system | Memory limit |
|---|---|
| Windows NT 4.0 Workstation/Server (service pack 3 or later) | 2 GB |
| Windows NT 4.0 Enterprise Server (service pack 3 or later) | 4 GB |
| Windows 2000 Professional | 2 GB |
| Windows 2000 Server | 4 GB |
| Windows 2000 Advance Server | 8 GB |
| Windows Data Center Server | 64 GB |
| AIX | 2 GB per process |
| HP-UX | 1.7 GB per process |
| Solaris | 2 GB per process |
To stop Windows NT and Windows 2000 services:
echo $SHELL
If the returned value is: /usr/bin/csh, change your shell to Korn Shell with this command:
setenv SHELL /usr/bin/ksh
The Korn Shell persists as your shell until you log out of your current session. When you log in again, your shell reverts to your default shell, which is C Shell in this example.
If you installed the run-time client on Solaris and then installed fix pack 1, the libesssql.so.1 library file might be corrupted. Before installing Fix Pack 3, remove the libesssql.so.1 library file from the $ARBORPATH/bin directory, and all links to that file. Fix Pack 3 installs the correct library
DB2 OLAP Server Miner (OLAP Miner) is supported on Windows XP Professional and AIX 5L.
For information about supported drivers for relational data sources, see the document, Supported ODBC Drivers and Relational Sources at:
http://www.ibm.com/software/data/db2/db2olap/fixpacks.html
For Fix Pack 3, the OLAP server is supported on the following additional operating systems and platforms. See the Installation Guide for a list of previously supported operating systems:
In Fix Pack 1 and later, the supported software for DB2 OLAP Integration Server had the following changes:
Note that DB2 OLAP Integration Server, Version 8.1, Fix Pack 3 (Essbase Integration Services Release 6.5.4) requires that you install DB2 OLAP Server, Version 7.1, Fix Pack 8 or later (Essbase Integration Services Release 6.2.0 or later). To use Hybrid Analysis, you must install DB2 OLAP Server, Version 8.1, Fix Pack 1 or later (Essbase OLAP Server, Release 6.5.0 or later).
See the Installation notes for information about issues that affect the installation of this fix pack.
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp03/olap_win/wincd.zip
If you are installing from a CD, copy the file to the temporary directory. If you have installed clients on other computers, you need to download the file to those computers, too.
To start the installation:
To start the server installation:
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp03/olap_win/wincd.zip
If you are installing from a CD, copy the file to the temporary directory. If you have installed clients on other computers, you need to download the file to those computers, too.
To start the installation:
This section describes how to download and install the fix pack for DB2 OLAP Server Enterprise Services (Essbase XTD Deployment Services). Here is the starting point:
You need to download a number of files that contain the product code and documentation. The number varies according to how many operating systems you use and which documentation you want. You can download the files from here:
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp03/ees/
Important installation tips:
IBM DB2 Universal Database™, Version 8.1 (DB2 UDB) requires that the client software or the RDBMS and ODBC driver be installed on the same computer as Essbase Integration Server. The instructions below assume that you have installed the DB2 UDB, Version 8.1 database client and configured it to access the required databases.
On Windows-based systems, you must start the ODBC Administrator and then create connections to the data source database for the relational data and OLAP Metadata Catalog. On UNIX systems, you must manually configure environment variables to access database client software and libraries. General information on configuring data sources is available in the Essbase Integration Services Installation Guide.
To configure data sources on Windows-based systems, use the Windows Control Panel to access the ODBC Data Source Administrator dialog box. Click the System DSN tab and perform the following tasks:
Click Add and then in the Create New Data Source dialog box, select the IBM DB2 ODBC driver, and click Finish.
In the Database alias drop-down list of the ODBC IBM DB2 Driver - Add dialog box, select the name of the database for which you want this data source configured.
Accept or edit the name of the data source that is displayed in the Data Source Name text box.
In the Description text box, type an optional description that indicates how you use this driver and click Add. Click OK to return to the ODBC Data Source Administrator dialog box.
The data source name that you just configured and the driver that you mapped to it are displayed in the System Data Sources list box on the System DSN tab.
To configure a data source on UNIX, you must edit the odbc.ini file: Add a name and description for the ODBC data source and provide the ODBC driver path and file name in a separate section that you create for the data source name. The odbc.ini file is located in the ISHOME directory. Below is an example of an ODBC setting for DB2 8.1 on AIX:
Use the vi $ODBCINI command to edit the odbc.ini file and insert the following statements:
[ODBC Data Sources]
db2data=DB2 Source Data on AIX
...
[db2data]
Driver=/home/db2inst1/sqllib/lib/db2_36.o
Description=DB2 Data Source - AIX, native
This section contains new documentation about installation.
You might receive the following error during a network installation:
Error number: 0x80040702
Description: Failed to load dll: winscp
Setup will now terminate
This error does not affect the client installation. The winscp.dll is loaded by the installation program, but it is not used.
Click OK and restart your computer.
If the OLAP server does not load on Lotus 1-2-3 after running the network installation, you might have old OLAP paths in the system's PATH that are causing a conflict.
Remove the old OLAP paths from the system environment variable PATH and restart the computer.
DB2 OLAP Integration Server requires Java Runtime Environment (JRE) files.
For AIX and HP-UX machines, DB2 OLAP Server, Version 7.1 Fix Pack 8 (Essbase OLAP Server Release 6.2.0) supports JRE 1.2.2, whereas DB2 OLAP Server, Version 8.1, Fix Pack 3 (Essbase Integration Services Release 6.5.4) requires JRE 1.3. If both OLAP Server and Integration Server are installed on same computer AND the same user ID starts both servers, you must set the Java environment variables associated with each server so that, depending on whether you are logged in as the Essbase user or as the Integration Server user, the correct version of Java is referenced.
Examples of how you might set the JAVA_HOME and related variables to point to the version of Java required by OLAP Server and Integration Server are shown in the Essbase Integration Services Installation Guide.
If you see a JRE 131 error when you use the DB2 OLAP Integration Server XML import/export function with DB2 UDB, Version 7.2 on UNIX, change Integration Server's environment setup to use JRE 1.3.0.
In the Essbase Integration Services Login dialog box, the user must specify a machine name or machine IP address in both the Essbase Integration Server frame and the Hyperion Essbase OLAP Server frame.
DB2 OLAP Integration Server, Version 8.1 Fix Pack 3 (Essbase Integration Services Release 6.5.4.1) software requires an odbc.ini file for operation of Open Database Connectivity (ODBC) connections from DB2 OLAP Integration Server to the relational data source and to the OLAP Metadata Catalog.
On HP-UX 11.0, it may be necessary to build your own Perl. We recommend using the HP ansic C compiler, and aCC linker. Building the Perl module on this platform may require some changes to the Makefile.PL.unix. Change the LIBS value to "-lCsup -lnsl -lc_r -lpthread -L$EH/api/lib -lessmaxl -L$EH/bin -lessglob -lglobalc".
In this fix pack, there are a few limitations to the platforms and drivers that are supported:
Essbase needs the ODBC libraries at startup. In previous releases, the ODBC libraries were located in the $ARBORPATH/dlls folder. On UNIX platforms, you were required to set your LD_LIBRARY_PATH to point to $ARBORPATH/dlls to enable Essbase to start.
In Release 6.5.4, the libraries are located in $ARBORPATH/odbc/merant41/lib. So, you must add $ARBORPATH/odbc/merant41/lib to your LD_LIBRARY_PATH environment variable, to enable Essbase to start.
The following requirements apply to setting up the Java Runtime Environment on HP-UX. JRE is required if you want to use custom-defined functions, the security platform, or both.
LD_PRELOAD
using a shell script that you design for starting Essbase. Warning:
Setting LD_PRELOAD in UNIX environment scripts such as .profile
is not recommended, as it may have side effects.For example, create a script called startessbase.sh in $ARBORPATH/bin
with the following contents (for Bourne or Korn shell):
export LD_PRELOAD="/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl" $ARBORPATH/bin/ESSBASE
and start Essbase using the startup script, as follows:
cd $ARBORPATH/bin ./startessbase.sh
The following example of a startessbase.sh script is for the C
shell:
setenv LD_PRELOAD "/opt/java1.4/jre/lib/PA_RISC2.0/server/libjvm.sl" $ARBORPATH/bin/ESSBASE
On Solaris, if you are using JRE version 1.4.1_01, you need to set an ESS_JVM_OPTION environment variable to use a special Java argument, Xusealtsigs.
ESS_JVM_OPTION1 through ESS_JVM_OPTION9 are available for setting options for
the Java Virtual Machine on Essbase.
Note: This is a requirement for the Essbase application process and not specifically for the security platform. This requirement applies only to JRE version 1.4.1_01 on Solaris, and is not applicable to other JRE versions on Solaris.
Examples:
In the C shell, add the following text to the .cshrc file:
setenv ESS_JVM_OPTION1 "-Xusealtsigs"
In the Bourne or Korn shell, add the following text to the .profile
file:
ESS_JVM_OPTION1=-Xusealtsigs;
export ESS_JVM_OPTION1;
If you are using JRE version 1.3.1, you need to set an ESS_JVM_OPTION
environment variable to use a special Java argument, -XX:+AllowUserSignalHandlers.
ESS_JVM_OPTION1 through ESS_JVM_OPTION9 are available for setting options for
the Java Virtual Machine on Essbase. Note: This is a requirement for the
Essbase application process, and not specifically for the security platform.
This requirement applies only to JRE version 1.3.1 on Solaris, and is not
applicable to other JRE versions on Solaris.
Examples:
In the C shell, add the following text to the .cshrc file:
setenv ESS_JVM_OPTION1 "-XX:+AllowUserSignalHandlers"
In the Bourne or Korn shell, add the following text to the .profile
file:
ESS_JVM_OPTION1=-XX:+AllowUserSignalHandlers;
export ESS_JVM_OPTION1;
Fix Pack 3 also fixes the defects listed in Problems fixed and adds some documentation in Documentation updates.
This fix pack adds the following new features to DB2 OLAP Server 8.1:
This fix pack includes fixes for Linux, AIX, HP-UX, Solaris Operating System, and Windows.
You can set up Essbase XTD Analytic Server to use external authentication supplied by the Hyperion security platform. Although Essbase provided custom external authentication modules in earlier releases, the new security platform is common to all Hyperion products. Using the security platform to manage user accounts on Essbase provides these benefits:
For more information, see the Security Platform Reference, a new book installed with this fix pack. For the latest setup information, see Security Platform Setup and Installation Notes.
Note: If for any reason the Hyperion Security Platform Reference link is not active, launch the documentation from the filesecurity_platform.htm, which is installed in thedocs\security\directory of your Essbase 6.5.4 installation.
New MaxL grammar enables the administrator to undo a previous decision to force a user to change his or her password at the next login. The new grammar is shown in bold; the previous grammar is also listed and described for context.
1. alter user USER-NAME set password_reset_days INTEGER days; |
Specify the number of days before a password expires. |
2. alter user USER-NAME set password_reset_days immediate; |
Force the user to change a password at next login. |
3. alter user USER-NAME set password_reset_days exact; |
Undo the 'immediate' setting above. The reason for this is as follows: If the administrator chooses 'immediate' and then attempts to revert back to allowing a set number of days, it will not work because 'immediate' takes a high priority. Using 'exact' is the only way to reverse 'immediate.' |
When the display user MaxL statement is issued, MaxL displays information about all users on the system. The following information is displayed in columns:
We have added a new column, called change_password that indicates whether a password change will be required at the next login.
In the past, we allowed MaxL users to create user names, server names, and passwords with leading or trailing spaces, tabs, or returns. For example, you could create a user named 'user1 ' Now, if you create a user named 'user1 ', that name will be automatically trimmed to 'user1'.
Granting any privilege, including calc and filter privilege, on a database also grants the implicit ability to load the application containing that database. To remove this ability, you must give no_access to the application, not just to the database.
In previous releases, the column size in essmsh was limited to 128 bytes. Now, you can set the column size to any value up to the size of the MaxL statement (the default size limit for MaxL statements is 81920 bytes).
To set column size in essmsh, use set column_width VALUE; The VALUE must be larger than eight and less than the current maximum MaxL statement size.
To set the MaxL statement size, use set maxl_statement size VALUE;
Note: For the MaxL Script Editor, there is no need to set the MaxL statement size, as Essbase Administration Services does this automatically.
Two new API functions are included for this fix pack in order for Essbase application programs to take advantage of External Authentication. The two new functions, EssLoginEx() and EssGConnectEx() accept a login token rather than a username and password. If these functions fail to authenticate, the standard login/connect functions are called. For more information refer to the Essbase API Reference.
For members with formulas attached, query results are sometimes displayed in a different order than in previous releases. This change is due to an internal change in the Calculator. It does not affect data.
For example, in Sample basic, Ratios has three children with formulas Margin%,
Profit per Ounce, and Profit%. In previous releases, a
zoom or cascade may have returned these members in the following order:
Ratios Margin % Profit % Profit per Ounce
In this release, the members may be returned in reverse outline order:
Ratios Profit per Ounce Profit % Margin %
Globally sets query optimization across transparent partitions for outlines that have a time dimension with Dynamic Time Series members. If this setting is specified, queries with Dynamic Time Series members will incur faster query times. Use this setting only if the time dimensions on the source and target partitions are identical. If the time dimensions on the source and target partitions are not the same, this setting may produce incorrect results. Restart the server to enable this setting to take effect for the Dynamic Time Series members that have been enabled at run time.
Syntax: TARGETTIMESERIESOPT
Example: TARGETTIMESERIESOPT
Previously, in response to agent or server crashes on UNIX platforms, Essbase created core dump files. In Release 6.5.4, to capture core dumps, include CRASHDUMP TRUE in the essbase.cfg configuration file. For agent crashes, Essbase creates a core file in a new directory ESSBASE.abc (where abc is the date and time) under ARBORPATH. For server crashes, a new directory, ESSSVR.abc is located within the application directory under ARBORPATH/app; for example,
/hyperion/essbase/app/Sample/ESSSVR.Mon_Jun_3_18_16_17_2003/core
This fix pack adds the following new features to DB2 OLAP Integration Server 8.1:
DB2 OLAP Integration Server, Version 8.1 adds Cancel buttons to several operations that query relational data sources. This feature enables you to stop cleanly and efficiently an operation that is accessing an excessive number of data rows and consuming system resources.
In DB2 OLAP Integration Server (OIS), several dialog boxes can be resized, which helps you to see data displayed behind the dialog box. The following four boxes can be resized:
DB2 OLAP Integration Server addresses two limitations that in previous releases affected the ability to run DB2 OLAP Server applications on nondefault ports:
DB2 OLAP Integration Server provides you with the capability of loading static or multiple relational database management system (RDBMS) columns into multiple alias tables. You are no longer limited to loading alias into the default table.
DB2 OLAP Integration Server expands find-and-replace options to include null values. With this option, you can add placeholders in hierarchies when null values are present in the relational database.
DB2 OLAP Integration provides you with the additional option of selecting a DTS member name instead of limiting you to a member name automatically set by OIS.
DB2 OLAP Integration Server has several significant improvements in error reporting on data loads:
When you create or update an OLAP Metadata Catalog for the first time in a new release of DB2 OLAP Integration Server, a set of scripts is run automatically. These scripts enable you to migrate to the current release of OIS from an earlier release. In OIS, Version 8.1, you can migrate automatically from DB2 OLAP Integration Server, Version 7.1, Fix Pack 4 or later or from DB2 OLAP Server, Version 8.1.
In addition to the configuration information found in Installation Notes and in the Security Platform Reference (a new book installed with this fix pack), the following setup is needed if you are using NT LAN Manager authentication on UNIX.
UNIX Applications Using NT LAN Manager Authentication
If you are using NT LAN Manager authentication and you have users who will
log in from UNIX, you need to install the Hyperion NTLM Remote Server on a
Windows NT or Windows 2000 server. On the Essbase CD, the setup file, hess654NTLMremoteserver_nt.exe,
can be found in the ntlm directory. Or, download the file from the
Hyperion Download Center. Run hess654NTLMremoteserver_nt.exe and
follow the prompts. Afterwards, be sure to complete the configuration of the
<remoteServer> element and all required elements as described in the
Hyperion Security Platform Reference for Essbase.
Note to JRE 1.3.1 Users
Please note that with JRE 1.3.1, for the Hyperion security platform to work, you need to upgrade the JRE to include the following components:
The existing documentation for the ESS_MBRINFO_T read fHasRelDesc Outline API function reads as follows:
| ESS_BOOL_T | fHasRelDesc | The member has relational descendants |
| ESS_BOOL_T | fHasRelDesc | The member has relational children |
The following customer reported problems are fixed in DB2 OLAP Server and DB2 OLAP Integration Server V8.1. The numbers in parentheses are current internal reference numbers for Hyperion Solutions; numbers in brackets indicate previous Hyperion tracking numbers.
In
Essbase 6.5.4.2, the way numeric formats for regional settings are interpreted
for a data import was changed back to its pre-6.5.4 release behavior.
Prior to 6.5.4, a period (.) is used as decimal point in both data load
and data export. In 6.5.4, the behavior for data import changed to use ESSLANG
or regional settings for the decimal point; in other words, a comma (,) may be
used to indicate a decimal point if ESSLANG is set to certain European locale or
regional settings. However, data export always uses a period (.) as a decimal
point, thus necessitating a fix in 6.5.4.2 to revert back to its pre-6.5.4
behavior.
EssVSetSheetOption function not working correctly in VBA toolkit. 14914,
57194
Essbase does not allow you to disable the option Use Both Member Name and
Alias name (EssVSetSheetOption 24) if either Retain on Remove and Keep Only or
Retain on Zooms options is enabled.
EssVZoomIn function with preserve formulas may cause Essbase to display
multiple occurrences of a value. 24786
Spreadsheet retrievals using the EssVZoomIn function may display multiple
occurrences of the same value if preserve formulas is turned on.
Drop Partition when there is more than 1 source Corrupts the .ddb file.
25956
When a single database is associated with more than one partition (for
example, if two source databases are associated with partitions leading to
different parts of one target database), using the Drop Partition MaxL statement
on one of the partitions may cause both of the partitions to stop working.
EssOtlGetGenName may not return generation names. 27889
The EssOtlGetGenName API may fail to return generation names.
Truncated words in the Japanese Application Manager. 43538, 43539
In the Japanese Application Manager, in the Partition Wizard > Areas tab
> Essbase Member Selection dialog box > Open Selection Object dialog box,
some words are truncated.
Report scripts containing the ORDERBY or TOP commands may fail to return
some alias names. 56070
Report script may fail to return some alias names when using the ORDERBY or
TOP commands.
Cannot create a transparent partition using MaxL. 56280
Creating transparent partitions in MaxL fails and returns an error message
saying that the maxl execution failed and that the partition already exists.
Updating a transparently partitioned source outline may take longer than
expected. 56412
Dimension builds may take longer than expected when performed on the source
outline for multiple transparent partitions (where one outline is the source for
several target outlines).
Reports that use the suppress missing rows (SUPMISSINGROWS) command and
access data from a relational source may return incorrect results. 56808
In reports that use the suppress missing rows command and access data from a
relational source, the values for the first row are repeated in the subsequent
rows.
EssVSetSheetOption function not working correctly in VBA toolkit. 57194
TheEssVSetSheetOption function is not working correctly in VBA toolkit.
Parameter 24 of the EssVSetSheetOption function fails to disable the "Use
Both Member Name and Alias" option in the Spreadsheet Add-in.
The create or replace MaxL statement fails when the application being
copied is not empty. 57895
The create or replace MaxL statement fails when the application being copied
is not empty.
Outlines with label-only attribute members can not be completely verified
using EsbVerifyOutline(). 58043
Outlines with label-only attribute members cannot be completely verified
using EsbVerifyOutline(). In these cases, EsbWriteOutline() fails with an error
of 1060053 and EsbVerifyOutline() returns ulCount = 1, but ulErrors = zero
(indicating a conflict).
Running a report script numerous times may cause the OLAP server crash.
58291
Running a report script a large number of times in quick succession may
cause the OLAP server to crash.
Calculations with Intelligent Calc ON may not create the correct number of
blocks. 58304
Intelligent re-calculation in single bitmap mode may not calculate some
blocks, thus generating incorrect results.
EssQueryDatabaseMembers with the ALLSIBLINGSOF operator and relational
members may fail. 58343
Using EssQueryDatabaseMembers with the ALLSIBLINGSOF operator and relational
members may fail and may return network errors.
Running a Calc Script from MaxL may stop the Essbase server. 59851
Running calc scripts from MaxL may cause the OLAP server to crash because
the MaxL parser does not allow a large enough buffer size. The fix for this
problem is to increase the size buffer size allowed by the MaxL parser.
Large concurrent retrievals that use the @XREF function may execute
slowly. 59938
Large concurrent retrievals that use the @XREF function may execute slowly.
Essbase may fail to load some zero level data during a parallel data load.
59998
Some zero level data may not be loaded during a parallel data load.
Loading data files that contain a large number of unknown records may
cause the OLAP server to crash. 60016
Data loads with a large number of rejected records may cause the OLAP server
to crash.
Unable to save report scripts in the Japanese Application Manager. 60054
The List Objects of Type field in the Save Server Object dialog box displays
a garbage string, and saving report scripts fails in the Japanese version of the
Application Manager.
The MaxL 'display filter row' statement may truncate large filters created
by Planning. 60060
The MaxL display filter row statement may truncate large filters
created by Planning.
Essbase may fail to display all mounted disk volumes on HP-UX. 60098
On HP-UX, Essbase may display only those disk volumes that are mounted at
boot-up.
When "," is specified in the operating system as the decimal
symbol, Essbase fails to recognize it as such during data loads. 60126
When the decimal symbol is set to comma in the operating system, Essbase
fails to recognize the comma as a decimal symbol during data loads. For example,
Essbase interprets 10,55 as 1055.00
Creating large filters in MaxL may fail and may return an error message.
60159
Creating large filters in MaxL may fail and may return the following error
message: 'essmsh error: Statement exceeds maximum possible size.'
The VB API function EsbGetNextItem may fail when used with EsbLogin
function. 60200
The VB API function EsbGetNextItem may fail when used with EsbLogin
function.
Spreadsheet retrievals containing attribute members may cause the Essbase
application to crash. 60224
Spreadsheet retrievals containing attribute members may cause the
application to crash.
Using MaxL to create a partition with a large number of fields may cause
the OLAP server to crash. 60241
Running a MaxL script that creates a partition with a large number of fields
may cause the OLAP server to crash.
The OLAP server may crash during bottom up calculations with the Create
Blocks on Equations setting enabled. 60334
The OLAP Server may crash during calculations when all of the following
conditions are true:
Essbase does not return correct indicator when Hybrid Analysis members
have children. 60785
When Hybrid Analysis members have children of their own, Essbase does not
return the correct indicator. It returns a - indicating that there are no
children when it should return a + indicating that there are children.
Maxl treats the append and write options in reverse. 60844
In the import data MaxL statement, you have three options for error
handling: abort, write errors to a log file, or append errors to a log file. The
write option is supposed to overwrite the existing log file or create a new one.
The append option is supposed to add information to the log file without
overwriting existing contents. In this bug, MaxL was treating these options in
reverse.
Essbase does not provide an automated way to perform a single outline
verification at the end of an incremental dimension build. 60930
The fix for this bug was to add an optional parameter, verify, to the
INCBUILDDIM ESSCMD syntax:
INCBUILDDIM location rulobjName dataLoc sourceName fileType errorLog
appendLog [verify].
Specifying Y or no value causes the outline to be verified for that step.
Specifying N causes the outline not to be verified. Be sure to verify the
outline during the last INCBUILDDIM step. For example:
BEGININCBUILDDIM;
INCBUILDDIM 2 "GENREF.RUL" 2 "GENREF.TXT" 4 "ERR.OUT"
1 N;
INCBUILDDIM 2 "LEVELMUL.RUL" 2 "LEVELMUL.TXT" 4 "ERR.OUT"
1 Y;
On UNIX platforms, wildcard queries may cause the OLAP Server to crash.
60993
Wildcard queries may cause the OLAP Server to crash on some platforms. The
OLAP Server will crash on some (but not all) versions of Solaris, and possibly
some versions of the other UNIX platforms.
Essbase installation incorrectly creates a PERL directory instead of
PERLMOD directory. 61084
Essbase installation incorrectly creates a PERL directory instead of PERLMOD
directory. The fix for this problem was to change the installation so that it
creates a PERLMOD directory.
Drill through reports on multiple cells may cause the OLAP Server to hang.
61111
The OLAP server may hang when drill-through reports exceed a certain number
of cells.
Spreadsheet retrievals with attribute members may return incorrect
results. 61163
Spreadsheet retrievals with attributes may return incorrect results if the
first base member that has an attribute association is an implied share member.
This bug happens on Essbase Release 6.5.3 only.
MaxL script succeeds in importing data but the return code appears to
indicate that the import failed. 61228
The following return code is displayed after a MaxL script successfully
imports data: Bad free() ignored.
Intelligent re-calculations that use single bitmap calculator cache may
not create the correct number of blocks. 61581
When a sparse dimension contains shared members under many branches,
intelligent re-calculations that use Single Bitmap Calculator Cache may not
calculate some blocks, and therefore, may generate incorrect results.
When multiple bitmap calculator cache is used, and there are backward
references in the outline, intelligent recalculation may return incorrect
results. 61587
When there are backward references in the outline (shared members appear
before real members in a Sparse dimension), and multiple bitmap calculator cache
is used, intelligent calculation may return incorrect results.
The Essbase > Cascade command may fail to copy formatting in the Lotus
123 Spreadsheet Add-in. 17769
In the Spreadsheet Add-in for Lotus 123 Release 9, the Essbase > Cascade
command fails to copy formatting when the "Copy Formatting" option is
selected.
Cannot list data sources using client SQL drill through. 18910
If there are several data sources for client SQL drill through, and one data
source returns an error, the lists from the other data sources are not displayed
and Essbase displays the following error message: "Failed to get the
list of available SQL data sources. See server log for more information."
The @ROUND function may return incorrect results if the number to be
rounded has several nines immediately following the decimal point. 21505
Calculations that use the @ROUND function may return incorrect results if the
number to be rounded is a decimal number that has several nines immediately
following the decimal point. In some of these cases, the number may not be
rounded to the next whole number.
Find operation in Member Select finds only first instance of shared
member. 22552
In the Member Select component of the Spreadsheet Add-in, the Find feature finds
only the first instance of a shared member. Subsequent instances of the shared
member are not found when Find Next is clicked.
Note: The fix for this problem applies only when you are connecting to
DB2 OLAP Server V8.1 Fix Pack 1 or higher. If you attempt a Find operation
against a Version 8.1 server earlier than Fix Pack 1, the fix for this bug
causes an error message to be returned.
Spreadsheet cells cannot be properly linked when Query Designer is open.
23342
In the Spreadsheet Add-in, cells cannot be properly linked between two
worksheets when Query Designer is open. This problem causes the link that is in
a cell in one worksheet to move to the wrong cell in a second worksheet.
Retrieval from an empty database incorrectly returns a zero. 25389
Dynamic Calc with no data, a negative consolidator, and a formula incorrectly
returns a zero instead of returning #MI. For example, #MI - #MI is
incorrectly returned as zero instead of #MI.
Upgrading from Release Version 1.1 to Version 8.1 or later might fail on
AIX platforms. 26379
If the size of at least one of the page files in Version 1.1 is 2147483647 bytes
(or 2GB-1 byte), upgrading from DB2 OLAP Server V1.1 to V8.1 might fail with the
following error message: "Error [1130614] encountered while
attempting to create or extend a data file for database []" during
migration.
Cell borders are incorrectly turned on when "Use Styles" is
selected in the Essbase Options dialog box. 26763
In the Spreadsheet Add-in, cell borders are incorrectly turned on when "Use
Styles" is selected in the Essbase Options dialog box (cell borders are not
controlled by this option). In addition, after drilling up or down in the sheet,
empty cells retain cell borders when they should be deleted.
The OLAP server may crash when disk volumes partition size set to
unlimited. 26983
On UNIX platforms, updating disk volume partition size to "unlimited"
may appear to complete successfully even if there is inadequate disk space. This
can cause subsequent updates page and index files to fail.
Dimension build may fail to update the outline when the existing outline
contains an attribute dimension. 27537
Performing a dimension build on an outline that contains an attribute dimension
may fail to update the outline.
Performing multiple retrievals using a VBA macro may result in a memory
leak. 27579
Using a VBA macro to perform multiple spreadsheet retrievals may cause a memory
leak.
The Cascade feature in the Spreadsheet Add-in may fail under certain
conditions. 27807
In the Spreadsheet Add-in, when using the Cascade feature, you cannot choose a
directory that is five or more levels from the root drive and that has a space
in the directory name as the destination directory for the cascade (for example,
c:\1 dir\2 dir\3 dir\4 dir\5 dir).
Large parallel calculations may crash the application. 35292
Running a large calculation with SET FRMLBOTTUMUP ON and SET CALCPARALLEL 3 may
crash the application with deadlock errors because of incomplete dependency
analysis.
Replicating data may result in an error. 36490
Replicating partitioned data on Version 8.1 and later may fail with a 'data
cache full' error because certain blocks were not being unfixed correctly.
The @REMOVE function does not remove shared members. 36865
This is expected behavior, but you can remove shared members by using the
@REMOVE function in combination with the @SHARE function. For more information
about using @SHARE with @REMOVE to remove shared members, see @SHARE.
A problem with the <UDA command causes unexpected results in a report
that uses <ICHILD and <LINK. 43159
The <UDA report script command returns the top member of the dimension,
regardless of whether that member has the UDA attribute. This may cause the <ICHILD
command to fail to include parent member within <LINK command in a particular
report script. The fix for this bug makes the <UDA command return the correct
members, which, in turn causes the <ICHILD command to include the parent
member within the <LINK command in this report.
Essbase allows you to create a filter name with more than 30 characters,
but it does not allow you to delete the filter. 43272
Using the Essbase VB API, you can create a filter name with more than 30
characters, but Essbase does not allow you to delete filters with names longer
than 30 characters.
The Subset Dialog box allows the condition "is not", but this
condition is not supported in Essbase partitioning. 43342
In the Partition Wizard > Areas tab > Essbase Member Selection > Subset
Dialog box, a drop-down menu enables you to select the condition "is
not", but this condition is not supported in Essbase partitioning. The fix
for this bug is to remove the "is not" option from the dialog box.
In the Query Designer, reports that use "Rank Bottom" or
"Rank Top" may fail. 43412
In the Query Designer, the following error is returned when you select
"Rank Bottom" or "Rank Top" as a Data Filtering option:
Report Error -- The DATACOL() argument [0] in the TOP or BOTTOM command
must have a value between [1] and the max number of columns [8] in the report.
Replicating partitioned data may fail. 43505
The OLAP server may crash/replication fails when the partition source has
many Dynamic Calc members. The partition definition should be fixed so that the
replication completes. The fix is to map the children of implied share members
appropriately. If member mapping errors are not fixed in the partition
definition, replication finishes but is not complete.
In the Spreadsheet Add-in, Style Options are not saved when you exit
Excel. 43514
In the Spreadsheet Add-in, styles you select in Essbase > Options > Style
tab are not saved when you exit Excel.
Error messages regarding temporary files when working with OLAP products
and features. 54894
Your TEMP or TMP environment variable must point to a valid directory
location (a location that exists) when working with DB2 OLAP Server products and
features. Otherwise these products may have trouble creating temporary
files.
Running Validate from Esscmd may incorrectly return the message "no
error found during validation." 55044
Running the Validate command on a database that contains Invalid Block
Headers may incorrectly return the message "no error found during
validation" even though the application log displays several errors
involving invalid block headers.
The DB2 OLAP Server agent is not returning SYN/FIN for every request from
a client. 55155
The DB2 OLAP Server agent is not returning SYN/FIN for every request from a
client, as it should. A user can monitor these by using the command "snoop
-V IP "xxx.xxx.xxx.xxx" | egrep 'Syn|Fin'". The Agent was not
returning these processes until the application was unloaded.
The server can hang during spreadsheet retrievals that contain out of
place members. 55475
Spreadsheet retrievals with out of place members may cause the OLAP server
to hang (with CPU at 100%).
Certain calculations may run in serial mode unnecessarily. 55614
Under the following conditions, the calculator may force a calculation to run in
serial mode unnecessarily:
This causes the following message to be written to the application log: "A
circular or recursive dependency along dimension [] forces calculation to
execute in serial mode."
The DELETEDB Esscmd command may fail if the user session times out or if
the user is logged off by the supervisor. 55628
If a database that is being deleted has users that were forcibly logged our or
timed out (ghost users), then deletion of the database may fail.
The OLAP Server may hang when performing a specific set of concurrent
operations. 55718, 55613
When running esscmd scripts that concurrently load applications, validate or
report a database, and unload applications, the following message may be written
to the application log: "Unable to bind host server socket on port
[]." If you see this message in your application log after
performing the above mentioned concurrent operations, consider using the new NETBINDRETRYDELAY
configuration setting.
Restructuring a database with a large number of LROs may cause the
database to crash. 55837
Restructuring a database with a large number of LROs may cause the database to
crash.
Certain parallel calculations may cause an internal server assertion
failure. 55847
During parallel calculation, an internal server assertion failure may occur.
The EsbGetDatabaseState API function may return the currency database name
and default currency type variables incorrectly. 55907
The EsbGetDatabaseState API function may fail to return the first 2 letters
from currency database name and default currency type variables.
Using MaxL to export data may fail. 55912
Exporting data using MaxL may fail and may result in the following error
message: "Cannot export data using MaxL - ERROR - 1005030 Parallel
export failed: too many segments [11453] in database. Start single-threaded
export."
EssVZoomOut may not work properly if there is at least one blank row at
the top of the specified range. 55983
If there is at least one blank row at the top of the specified range, the
EssVZoomOut function may fail.
Certain retrievals in Essbase Query designer return a report error. 56030
In the Essbase Query Designer, attempting to do top ranking based on members
of an attribute dimension returns a report error.
Parallel calculations may cause a misleading message to be written to the
log. 56125
If CALCTASKDIMS is set to a number higher than the number of sparse dimensions
in the outline, the following (incorrect) message is written to the application
log (even if calculator cache is turned off): "Parallelizing using []
task dimensions. Usage of Calculator cache caused reduction in task
dimensions".
Retrievals of Hybrid Analysis data may return incorrect values if the
Measures dimension is not from the fact table. 56248
When retrieving Hybrid Analysis data for an outline whose Measures dimension is
not from the fact table, only #Missing values are returned because of an
incorrect orderby clause in the generated SQL query.
In Excel XP, loading multiple worksheets that contain macros may cause
Excel to crash. 56374
In Excel XP, Loading multiple worksheets that contain macros may cause Excel
to crash
Requesting connection information from an application to which you do not
have access may cause the OLAP Server to hang. 56435
The OLAP Server may hang when users with privileges to view requests in some
loaded applications but not in other loaded applications request connection
information.
Renaming an application may fail under certain conditions. 56446
Renaming an application may fail with the error message: 'Cannot
rename directory ARBORPATH\App name [Permission Denied]'under the
following conditions:
Renaming the database leaves directories on the partitioned drive with the old database name. The error occurs if you attempt to rename the database back to the original name.
Saving an outline that contains a large formula may fail. 56458
In a partitioned database, when saving an outline that contains a large member
formula that exceeds 2KB, exception errors are returned.
API executables built with DB2 OLAP Server V1.1 shared libraries may not
work with newer releases of DB2 OLAP Server. 56486
If you have an API-based program that was last linked with API libraries from
Version 1.1, and you replace the API libraries from Version 7.1 or later
releases of Essbase, you may encounter the following error when running the
program:
adGlobSetEssLocale: referenced symbol not found
If so, consider upgrading to API libraries from DB2 OLAP Server V8.1 Fix Pack 2
and recompiling your API program.
During serial calculations, the SET NOTICE calculation command may fail to
record completed blocks. 56623
During serial calculations, the SET NOTICE calculation command may fail to
record completed blocks.
Launching a linked partition may cause Excel or Lotus 1-2-3 to crash.
56651
When the Spreadsheet Add-in is connected to an instance of the OLAP server
running on a UNIX platform, launching a linked partition may cause the
spreadsheet software (Excel or Lotus 1-2-3) to crash.
Loading two or more applications at the same time may fail. 56653
When loading two or more applications at the same time, the Essbase agent
intermittently hangs (stops responding) and dumps an exception error file.
Dimension builds launched from MaxL may fail if the database outline is
empty. 56841
Dimension builds that are launched from MaxL may fail if the existing
database outline contains no dimensions or members.
Essbase hangs (and spikes the processor usage) when the MAXLOGINS setting
is high. 56899
When the MAXLOGINS setting is very high (on the order of several hundred
thousands), the OLAP server may hang and processor usage may spike momentarily
to 100%.
Some report scripts may spike the CPU usage on the server machine to 100%.
56911, 56950
Running a query from a report script against the OLAP server spikes the CPU
usage on the server machine to 100%.
Retrievals that include attribute members may have incorrect results.
56920
Attribute retrievals may have incorrect results if one or more attribute members
are associated with non-zero level base members and at least one base member in
the query is an implied share member.
The OLAP server may crash when listing user connections. 56928
Listing user connections from a machine with a name (including domain name)
longer than 29 characters, may cause the OLAP server to crash.
Viewing connections in the application manager may cause the OLAP server
to hang. 56931
Logging in with a user name that does not have security privilege to access user
connection information and then selecting Security > Connections, may cause
the OLAP Server to hang.
An API program that calls a substitution variable may fail after a large
number of iterations. 56961
If a client API program opens too many connections to DB2 OLAP Server, then
subsequent connections may return network errors because of delays in clearing
out closed ports.
Parallel calculations may fail to finish in a reasonable amount of time.
57052
Parallel calculations that make multiple passes may take longer than serial
calculations if the commit blocks value is either zero or very large.
Variables surrounded by double quotes may not work with MaxL. 57055
MaxL does not recognize variables surrounded by double quotes.
Parallel calculation may take longer than expected. 57186
Running a parallel calculation after an incremental data load may take longer
than expected.
Certain spreadsheet retrievals may crash the application. 57200
In the Spreadsheet Add-in, a retrieval may crash the application if the sheet
contains Dynamic Time Series members and a dynamically calculated member with a
formula containing the @XREF function.
Migration to DB2 OLAP Server 8.1 or later from Version 7 may fail and the
migrated databases may be corrupt. 57254
DB2 OLAP Server incorrectly handles 5 different status bits during a migration
from Version 7 to Version 8 or later. The status bits were not getting copied
properly and could be replaced by randomly chosen values (the same value would
be used for all pages). One of the status bits was used during incremental
restructuring, three were used during calculations, and one tracked data pages
containing input data. If you did an incremental restructuring prior to
migrating, the bug would have caused IBH (Invalid Block Header) errors after the
migration. The effect on the other bits was less obvious.
If you have not yet migrated from Version 7 to Version 8 or later, the fix for this bug does fix all of the known problems associated with the bug. In this case, your databases should migrate fine and the status bits will be correct.
If you have already migrated from an earlier version of Version 7 to Version 8 or later, the fix deals only with the IBH errors that show up when you touch a block that has been part of an incremental restructuring (such as with the VALIDATE command which touches everything). In this case, the fix for this bug does not fix your status bits. Some of the status bits can be corrected by doing a full calculation; another can be fixed by doing a dense restructuring. Both of these operations are likely to be time consuming. Unfortunately, the final status bit can only be fixed by clearing all data and reloading it. This is the status bit that tracks which data pages contain input data and is used by commands like EXPORT.
If you made a backup of your database before migrating, we recommend that you delete the migrated database, restore the database from the backup, and then redo the migration (using the fixed executable).
MaxL returns an error message after running the alter database command to
find and fix IBH errors. 57268, 57306
MaxL returns the following error message after the alter database command has
been issued to find and fix IBH errors: "ERROR - 1013153 - No IBH is
found from last diagnosis run." The fix for this problem is to
change the error message to a warning message since nothing is wrong.
Spreadsheet Add-in retrievals that use the ESSCELL function may fail.
57666
Spreadsheet retrievals that use the ESSCELL function may cause Excel to hang
with CPU usage spiked at 100%.
Calculations that aggregate missing values may have incorrect results.
57676
In some cases, incremental calculations (calculations after an incremental
data load) that use "SET AGGMISSG ON" may produce incorrect results.
Certain attribute calculations may return incorrect results. 57745
Attribute calculations may return incorrect results when a two-pass calc
formula is dependent on another two-pass calc member that is not part of the
query.
The MaxL command 'Alter System unload application all;' may fail to unload
applications. 57721, 57865
This command works only if all applications are loaded.
Adding a shared member and its non-shared sibling inside a partition may
cause the application to crash. 58253
Adding a shared member and its non-shared sibling inside a partition in the
same restructure many cause the application to crash. Specifically, the
application will crash if the non-shared sibling immediately follows the shared
member in the outline.
Certain spreadsheet retrievals may cause DB2 OLAP Server to hang. 58317
Spreadsheet retrievals that use the EssCell function may trigger a memory leak
that causes Essbase to hang.
Grid API does not pass all required parameters to DB2 OLAP Integration
Server. 60144
The Grid API function EssGDTRequestDrillThrough does not pass SYSTARGET
information to DB2 OLAP Integration Server for Drill-Through reports.
Setting the aggregation of Amount to NONE generated errors
Setting the aggregation of Amount to NONE in the Accounts dimension in an OLAP
model would sometimes generate an error when a user attempted to drag
Accounts:Amount to a new metaoutline based upon that model. The user would
receive the error message, "AMOUNT not a measure or user-defined
member." (56487)
The Integration Console cannot reconnect to Essbase Integration Server
when a non-default port was used
If you are running DB2 OLAP Server with a non-default port, and the server was
either shut down or went down, the Integration Console could not reconnect to
the non-default port. The user was required to connect to a default port.
(57563)
Drill-through intersection did not reflect saved changes to Accounts
dimension
If Measures.Child was removed from an OLAP intersection level and the model was
saved, the deleted Measures.Child would still appear in the OLAP intersection
level. (57717)
On the Oracle platform, Essbase Integration Services loaded only the first
255 characters when adding formulas manually in the console.
On the Oracle platform, if a user opened a metaoutline and set the formula to
more than 255 characters and then loaded the metaoutline into Essbase, the
formula was truncated after the 255th character. (57725)
Menu in the member selection dialog box in the Spreadsheet Add-in may be
displayed in the wrong location. 17249 (19585)
In the Spreadsheet Add-in, right-clicking in the member selection dialog box
under Rules sometimes displays the pop-up menu outside of the dialog box.
The online help for the Edit URL dialog box does not work. 17408 (19807)
When you select Edit URL from the Linked Object Browser dialog box and click
Edit and then Help, the Spreadsheet Add-in displays an error message and the
help topic fails to appear.
In the Spreadsheet Add-in, the style selected for drill-through reports is
applied to all members in a dimension at the same level or below that of the
member with the drill-through report. 20724
If any member of a dimension has a drill-through report available, and
Integration Server Drill-Through is selected in the Essbase > Options >
Style tab of the Spreadsheet Add-in, all members of that dimension at that level
or below are displayed as having drill-through reports.
The Getdbstate Esscmd may fail to return the correct value for Concurrency
Wait. 21276 (24720)
The Getdbstate Esscmd incorrectly returns a zero value for Concurrency Wait.
In some cases, Hybrid Analysis may round relational data using incorrect
precision. 22946
DB2 OLAP Server V8.1 may round all of the data from relational sources to
the same precision regardless of data type. In Fix Pack 1, Essbase uses the
column definitions from the fact table columns to generate expressions in the
select list with the correct casting. The fix for this problem is to have
Essbase HA use the precision described in the relational data.
Repeated calculations that fix on sparse members might run slowly due to
excessive fragmentation. 24882
If you run repeated calculations or data loads affecting the same set of data
blocks, subsequent calculation or data load times may deteriorate because of
excessive fragmentation. In Fix Pack 1, the effects of fragmentation due to
repeated loads or calculations is minimal and there should be no drastic
degradation in performance.
Calc script validation may fail to detect certain errors. 25734 (30211)
A calc script that fixes on one of the members to be calculated does not
generate errors during validation, and running the calc script crashes the
application. The validation now detects the error.
Copying a database during a data export may fail. 27608
Copying a database during a data export may fail if the original database and
the database created by copying the original have the same name.
In the Spreadsheet Add-in, the Essbase > Cascade option creates a file
in which the timestamp is not NLS enabled. 27656 (32684)
The cascade option creates worksheets and a file containing an index of the
worksheets. The timestamp in the index file is not NLS enabled, that is, the
format of the date is mm-dd-yy, instead of the format required by regional
settings.
Data load via transparent partition may fail. 27759
You can load data remotely to the source database of a transparent partition by
loading the data to the partitioned area of the target database. This bug may
cause the remote data load to fail with the following error message
"(1014004) Unable to Update Members Which Have Not Been Locked."
Calculating a database using a calc script with at least one formula may
cause the application to crash. 27911
Running a calc script with at least one formula may cause the application to
crash and cause DB2 OLAP Server to create an exception log.
The @ROUND function may produce different results in DB2 OLAP Server V1.1
than it does in V7.1. 27971
Calculations that use the @ROUND function may have different results.
In the Spreadsheet Add-in, retrievals that return exactly 256 columns may
fail. 28121
Any retrieval or spreadsheet operation, such as a pivot or drill down, that
returns exactly 256 columns may fail.
The OLAP server may crash during a database copy if the security file is
very large. 28271 (33419)
Copying a database with a very large security file (73MB), may cause the OLAP
server to crash.
Spreadsheet retrievals with all members in the same column may crash the
application. 28342 (33499, 33113)
Certain spreadsheet retrievals that have unusual formatting, such as displaying
all members in a single column, may cause the application to crash.
LDAP Authentication does not work using Active Directory. 28417
An externally authenticated DB2 OLAP Server user cannot log in using LDAP
parameters when the external LDAP repository is Microsoft Active Directory on
Windows 2000.
Parallel calculations that use the Calc TwoPass calculation command may
crash the application. 28718
Running a parallel calculation that uses the Calc TwoPass command may crash the
application.
Certain spreadsheet retrievals may misalign column headings and data.
28728
In spreadsheets that have Use Both Member Names and Aliases for Row Dimensions
selected (in Essbase > Options > Display tab), and have row members placed
between two columns, retrievals may misalign the column headings and data.
The UPDATEVARIABLE command may fail to update substitution variables.
28849
The UPDATEVARIABLE command fails to update substitution variables when the case
does not match that of the original database and application. After updating
substitution variables using the UPDATEVARIABLE command, the new variables are
displayed in the Application Manager under Server > Substitution Variables,
but a spreadsheet retrieval returns the old variables and their associated
values.
The OLAP server may crash when connecting to Analyzer. 29039
When running on the Solaris 8 platform, the OLAP server may crash when
connecting to an application via DB2 OLAP Server Analyzer 7.1 (Hyperion Analyzer
5.0.3).
Certain queries may crash the application. 29187
Retrievals of dynamic calc members with member formulas containing the @PRIOR
function may cause the application to crash.
Linked Partitions may not work. 29190
Drilling down on partitioned target members may not launch the linked objects
browser.
Calculations that use the CALC DIM calculation command may crash the OLAP
server. 29211
Using the CALC DIM calculation command with the dimension names listed out of
outline order may crash the OLAP server and generate an exception log.
Essbase error while clearing database. 29225
When INCRESTRUC TRUE is specified in the essbase.cfg file, clearing
data may fail and may result in the error "Unable to free aligned
memory for [datctxp->ppDatMemPage[]]in[adDatTermDatCtx]."
The results of calculations that use SET AGGMISSG ON may be incorrect.
30739
Some calculations that include the command SET AGGMISSG ON may fail to aggregate
the missing values, thereby resulting in incorrect values.
A calculation fails to use the correct values for substitution variables
that have been changed using EsbCreateVariable. 33115
Values for substitution variables that have been created or changed through the
Visual Basic API function EsbCreateVariable() might not be evaluated correctly
by subsequent calculations.
Calculating currency conversions may take longer than expected. 33869
Running the CCONV calculation command on Currency Conversion applications may
take longer than expected.
The MaxL Perl Module may limit the length of query results to 128
characters. 35170
Query results from the MaxL Perl Module may be truncated if they are greater
than 128 characters in length.
Cannot view connection information in the Application Manager during a
dimension build. 36451
While running a dimension build, you cannot access Security > Connections
from Application Manager for any application on that OLAP server.
The memory used when starting the OLAP Server increases as the setting for
CALCLOCKBLOCKDEFAULT is increased. 36822
The OLAP Server uses relatively more memory at startup when the
CALCLOCKBLOCKDEFAULT is higher than it does when this setting is lower.
Attribute queries containing upper-level attribute members that have
implied share base members may return incorrect results. 36982
Queries from databases with upper level attribute members that have level-one
base members with only one child may return incorrect results.
Memory leak when running calculations that use the @XREF function. 37090
Calculations that use the @XREF function may fail and may result in the error
message "Unable to Allocate Memory"
Some calculations may be incorrect in DB2 OLAP Server V8.1 that were correct in previous versions. 37742, 40027, 40039
Spreadsheet retrievals that have the same member in two consecutive rows
may fail. 43242
Spreadsheet retrievals that have the same member in two consecutive rows worked
in earlier releases, but in V8.1 the same spreadsheet retrievals fail with the
error message, "A column item [] conflicts with a row item []."
Spreadsheet retrievals that use certain styles may crash Excel. 43248
Using styles for linked objects, read only cells, or read/write cells may cause
Excel to crash during spreadsheet retrievals.
Spreadsheet retrievals from transparently partitioned databases with
attribute dimensions may crash the application. 43306
Retrieving from a database that has attribute dimensions and is the target in a
transparent partition may crash the application.
The VB API EsbGetDatabaseState incorrectly reports that "Two Pass
Calculation" is not selected even though it has been selected through the
Database Administrator. 43321
The Database Administrator interface does not set the CalcTwoPass field in the
ESS_DBSTATE_T structure used by the Visual Basic API function
EsbGetDatabaseState(). The function incorrectly returns that "Two Pass
Calculation" is not selected when "Two Pass Calculation" was set
through the Database Administrator (through Database > Settings >
General tab).
Data loads from files with a large number of columns may fail because of
excessive memory usage. 43433
Certain free form data loads from data files that have a large number of columns
may fail because of excessive memory usage. Data files created by exporting data
from a database with a large number of sparse members may have a large number of
columns.
The SQL Drill Through Add-in (DB2 OLAP Server V.1. Fix Pack 14) may fail
to work with the V8.1 DB2 OLAP Server and Spreadsheet Add-in. 43499
After installing the V8.1 level of the OLAP server and Spreadsheet Add-in, and
the V1.1 Fix Pack 14 SQL Drill Through Add-in, SQL Drill Through fails to appear
in Essbase pull down menu of the Spreadsheet Add-in.
Retrieving dynamic time series data using the Esscell function may fail.
43553
The Esscell function may incorrectly return zeros for dynamic time series data.
Deleting databases may not delete data that resides on spanned disk
volumes. 54953
Using ESSCMD or Application Manager to delete databases may fail to delete .pag
files from the spanned disk volumes.
Parallel calculations may crash the application under certain
circumstances. 55126
Parallel calculations may crash the application if the calculation includes a
sparse dynamic calc member that (1) consolidates into its stored parent and (2)
has a formula that causes a top down calculation.
Spreadsheet retrievals may be slower in DB2 OLAP Server V7.1 Fix Pack 8
and later, and in V8.1, than in V7.1 Fix Pack 7 or earlier. 55512
Certain spreadsheet retrievals may take longer.
Dimension builds that change consolidation properties may also alter
attribute associations. 55244
Changing consolidation properties using a dimension build rules file may alter
existing attribute associations, causing the outline to become invalid.
Users unable to drill down on multiple cells In OIS V8.1, users are not able to drill down simultaneously on multiple cells in Spreadsheet Add-in. Prior to V8.1, users were able to select multiple cells in Spreadsheet Add-in, then drill down, and access a report that reflected data for all items selected. (29115)
Windows service for Integration Server is disconnected when user logs off server When running OIS as a Windows service, the service stops when the user logs off the computer that is running it. (43132)
Values with comma decimal delimiters are loaded incorrectly OIS incorrectly loads values with comma decimal delimiters from SQL data sources; for example, the value 123,456 becomes 123456, instead of 123.456. (28297) [33452]
No error is displayed when duplicate member names exist across dimensions When trying to load duplicate members across dimensions, OIS produces an incorrect outline rather than displaying an error message. (28226) [33361]
Filters in date field columns in customized drill-through reports may cause error In some instances, adding a filter to a date field column in a customized drill-through report causes a syntax error. (36288)
Shared members not allowed in Accounts dimension built from fact table When performing a member load, duplicate members from the Accounts dimension are rejected. Current limitations are: one, when users drag duplicate measures into the Accounts dimension, the second occurrence of the same measure is tagged as shared in the member load; and, two, duplicate measures must have unique parents.(26479) [31187]
Metaoutline fails to open after OLAP model is modified When an OLAP model is modified after a metaoutline has been created based on that model, OIS fails to reset the model ID. When the user attempts to reopen the metaoutline, the model ID cannot be found, causing the metaoutline to not open. No error message is generated. (27210) [32111]
Attribute dimension records rejected when "Delete all members first" option not selected If a user accesses the same database and uses the same metaoutline several times without selecting the "Delete all members first" option, at some point the application will begin rejecting attribute dimension members. (27476) [32453]
Drill-through reports do not return more than 6000 rows Drill-through reports running with V8.1 fail to return more than 6000 rows regardless of the actual number of records that should be returned. (43463)
Excessive time required to save OLAP model and metaoutlines In some circumstances in V8.1, saving OLAP models and metaoutlines can take large amounts of time. (42975)
The following are some known problems and system limitations with workarounds when appropriate.
Uninstall issue
Some cases of erroneous behavior occurred when the ODBC component of Essbase XTD Analytic Services 6.5.4.0 was uninstalled by using the Microsoft uninstall option and Essbase XTD Analytic Services Server was running on the same machine as programs that use Microsoft Data Access Components (MDAC).
During the uninstall process, four files were inadvertently deleted from shared directories. This can cause connectivity issues in some programs.
If you upgraded to or plan to upgrade to Essbase XTD Analytic Services 6.5.4, it is strongly recommended that you install Essbase XTD Analytic Services 6.5.4.2. Essbase XTD Analytic Services 6.5.4.2 does not have this issue. Migrating to the next version of Essbase XTD Analytic Services will also solve the issue if you have Essbase XTD Analytic Services 6.5.4.0 installed on the machine.
It is recommended that you do not uninstall ODBC component of Essbase XTD Analytic Services 6.5.4.0.
Division-by-Zero Limitation for Custom-defined Functions on HP-UX
On HP-UX with JRE 1.4.1, if you want to develop and register custom-defined Java
functions, make sure that in those functions there is no division by zero. If
division by zero must be used, you must use JRE 1.3.1.
Note that with JRE 1.3.1, for the Hyperion security platform to work, you need to upgrade the JRE to include the following components:
Every effort has been made to ensure that Essbase Integration Services is as free of bugs as possible. The following are some known problems and system limitations, with workarounds when appropriate. Numbers in parentheses are internal reference numbers for Hyperion Solutions.
OTHER LIMITATIONS
HYBRID ANALYSIS LIMITATIONS:
Licensed
Material - Program Property of IBM
(c)
Copyright IBM Corp. 1998, 2003. All Right Reserved.
US
Government Users Restricted Rights - Use, duplication or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.
IBM,
DB2, and DB2 OLAP Server are trademarks of International Business Machines
Corporation in the United States, other countries, or both.
Portions
(c) 1991-2003 Hyperion Solutions Corporation. All rights reserved.
Hyperion is a registered trademark and Hyperion Solutions is a trademark
of Hyperion Solutions Corporation.
Portions
(c) Blue Sky Corporation. All rights reserved.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.