*****************************************************************
*****************************************************************
Welcome to Fix Pack 5.1 for the IBM® DB2® OLAP Server™, Version 8.1 products.
This fix pack corrects a problem that prevented installation of Fix Pack 5 for DB2 OLAP Integration Server on Japanese systems.
This fix pack includes fixes at the following service level:
The following features are not updated in this fix pack:
Hyperion maintenance levels are cumulative: Each level contains new fixes and all the fixes for the previous maintenance levels.
For more support information, go to the DB2 OLAP Server Support site:
http://www.ibm.com/software/data/db2/db2olap/support.html
Fix Pack 5.1 does not change the levels of support software.
In Fix Pack 5, support for some operating systems and RDBMSs have been added, and others dropped. For exact information, see the following documents on our Web site:
To install this fix pack, make sure that your system has enough memory. Then, download the files that match your operating system and language, or copy the files from a CD, and begin the installation. For complete installation instructions, see the Installation Guide.
See the Installation notes for information about issues that affect the installation of this fix pack.
| Operating system | Memory limit |
|---|---|
| Windows 2000 Professional | 2 GB |
| Windows 2000 Server | 4 GB |
| Windows 2000 Advance Server | 4 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 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 or later, remove the libesssql.so.1 library file from the $ARBORPATH/bin directory, and all links to that file. Fix Packs 3 and later install the correct library.
Administration Services, Enterprise Services, and Spreadsheet Services are not updated by Fix Pack 5.1 but were updated in previous fix packs:
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp05_1/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/fp05_1/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:
A new book, the Security Platform Reference, is available in Fix Pack 3 and later, in HTML format on Windows only. The book is not installed with the fix pack automatically. To install the book:
Install the fix pack for Windows (the setup.exe file) and reboot.
Launch the setup.exe again.
In the Maintenance window, click Modify and then Next.
In the Modify Entry window, Click Add Components and click Next.
In the tree view, open IBM DB2 OLAP Server Documentation and then Client and Server Documentation. Select Security Platform Reference and any other books you want to install, and click Next.
For more information about the Hyperion Security Platform in this document, see User authentication through the Hyperion security platform and Security platform setup.
Fix pack 5.1, Fix Pack 5, and Fix Pack 4 do not add any new installation notes.
Fix Pack 3 adds the following installation notes:
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 or later (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 or later (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; 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 Installation Guide.
To find the latest levels of data sources and ODBC, see the following support matrices:
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 describes how to download and install fix pack 3 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:
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/ess/
Important installation tip:
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/fp02/eas/
Important installation tips:
Fix Pack 5.1 does not add new features, but it fixes defects listed in Problems fixed. The levels of supported software are the same as in Fix Pack 5.
This fix pack changes the levels of supported software. For example, the ODBC drivers shipped with Fix Pack 5 have been upgraded to ODBC DataDirect version 4.2. Additionally, for the server component of DB2 OLAP Integration Server, this release includes support for Red Hat Linux AS 2.1 and AIX 5.2. Support for other operating systems has been dropped. For client installations, this release provides support for Windows 2003.
For a complete list of supported software, see the following documents on our Web site:
Fix Pack 5 also fixes defects listed in Problems fixed and adds some documentation in Documentation updates.
Fix Pack 4 does not add new features, but it fixes defects listed in Problems fixed and adds some documentation in Documentation updates.
Fix Pack 3 also fixes the defects listed in Problems fixed and adds some documentation in Documentation updates.
This fix pack adds the following changes to DB2 OLAP Server:
Fix Pack 3includes 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
Fix pack 3 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.
To see what's new in Fix Pack 3 for Enterprise Services and to start the Fix Pack 3 installation, see Installing Fix Pack 3 for DB2 OLAP Server Enterprise Services.
To see what's new in Fix Pack 3 for Spreadsheet Services and to start the Fix Pack 3 installation, see Installing Fix Pack 3 for DB2 OLAP Server Spreadsheet Services.
Fix Pack 2 adds the following new features to DB2 OLAP Server 8.1:
fetch_desc function
(new usage requirements). Editing partition definitions using new alter partition statement.
Use the alter partition statement to fix invalid or dangling partition references. Use this statement to change the authorized user who can connect to both databases, or to change the name of an application, database, or host (in the event that something was renamed).
>>--alter---transparent---partition <DBS-NAME>-->
| |
+-replicated--+
| |
+-linked------+
>-to-----<DBS-NAME>--------------------->
| | | |
+-from-+ +-at <HOST-NAME>-+
<-set- connect as <USER-NAME> identified by <PASSWORD>------------------------><
| |
+-hostname as <HOST-NAME> instead of <HOST-NAME> direction--single-----+
| | | |
| +-all----+ |
| |
+-application as <APP-NAME> instead of <APP-NAME> direction--single----+
| | | |
| +-all----+ |
| |
+-database as <DBS-STRING> instead of <DBS-STRING>---------------------+
Note: To change the authorized partition user, you must change the user for both partitioned databases, as shown in the following example.Example 1:
alter transparent partition app1.source to app2.target set connect as newuser identified by newpasswd; alter transparent partition app2.target to app1.source set connect as newuser identified by newpasswd;Note: If a partitioned host, application, or database is renamed, the rename does not propagate to the partition definition, so you must use alter partition to change the name in the partition definition. As shown in the following example, you must give the old name and the new name. If both names were changed, the partition definition is not recoverable, and must be re-created.
Example 2:
In the following example, alter partition is used to fix a partition definition that became invalid when a host name (
oldHost) changed and affected only one half of the partition definition (app2.target):alter transparent partition app1.source to app2.target at oldHOST set hostname as newHOST instead of oldHOST direction single;wheredirection singleindicates that only the target host name needs to be changed.Example 3:
In the following example, alter partition is used to fix a partition definition that became invalid when a host-name change affected both the source and the target, because both applications were on the same host:
alter transparent partition app1.source to app1.target at newHOST set hostname as newHOST instead of oldHOST direction all;where
direction allindicates that the host-name change needs to be made on both the target and source halves of the partition definition.Example 4:
In the following example, alter partition is used to fix a partition definition that became invalid when the source application name (
oldAppName) changed tonewAppName, and affected only one half of the partition definition:alter transparent partition newAppName.source to app2.target set application as newAppName instead of oldAppName direction single;wheredirection singleindicates that only one half of the partition definition needs to be corrected.Note:
oldAppNamecan be discovered by issuing the display partition statement prior to correcting the partition definition.Example 5:
In the following example, alter partition is used to fix a partition definition that became invalid when the source application name (oldAppName) changed to newAppName, and affected both halves of the partition definition because both partitioned databases were on the same application:
alter transparent partition newAppName.source to newAppName.target set application as newAppName instead of oldAppName direction all;wheredirection singleindicates both halves of the partition definition need to be corrected.
Using IP addresses for partitioned databases.
The display partition statement returns two new columns:source_host_IPandtarget_host_IP. Also, you can use IP addresses in addition to hostnames when creating, dropping, or altering partition definitions. For example:drop replicated partition Samppart.Company from Sampeast.East at '127.0.0.1';
Forcing deletion of a partition definition.
The force keyword used at the end of the drop partition statement specifies that the source half of a partition definition should be dropped regardless of whether the target half is missing or invalid.
For example, in the following session, assume there is a partition definition between app1.source and app2.target, but the app2.target database has been dropped. An ordinary attempt to drop the partition definition fails:
MAXL> drop transparent partition app1.source to app2.target;
OK/INFO - 1053012 - Object source is locked by user system.
OK/INFO - 1051034 - Logging in user System.
OK/INFO - 1051035 - Last login on Friday, January 10, 2003 2:28:09 PM.
ERROR - 1051032 - Database target does not exist.
OK/INFO - 1053013 - Object source unlocked by user system.
OK/INFO - 1051037 - Logging out user system, active for 0 minutes.In the second attempt, the force keyword allows the invalid source partition to be dropped:
MAXL> drop transparent partition app1.source to app2.target force; OK/INFO - 1053012 - Object source is locked by user system. OK/INFO - 1051034 - Logging in user System. OK/INFO - 1051035 - Last login on Friday, January 10, 2003 2:31:50 PM. ERROR - 1051032 - Database target does not exist. OK/INFO - 1051037 - Logging out user system, active for 0 minutes. OK/INFO - 1053013 - Object source unlocked by user system. OK/INFO - 1241125 - Partition dropped.Note: The force keyword only works to drop a partition definition when the source half of the partition definition remains valid. In other words, if the source database is deleted, the partition cannot be dropped from the dangling target.
Saving partitions that have "Cell count mismatch" warnings.
Prior to this release, it was not possible to create a partition which would not validate because of "cell count mismatch" errors. Now, MaxL creates and saves the partition definition, with warning messages.
Getting datatype information from the Perl-module
fetch_desc function (results in new usage requirements for
fetch_desc).
Thefetch_desc()function insideEssbase.pmnow returns a reference to a row of query results and a reference to a corresponding row of datatypes for the query results.A datatype is information about what sort of data a certain value is.
Hellois a string, and is represented by aChardatatype.0could be aNumber, but it could also be a False value for a Boolean datatype.If you fetch only column-description records and ignore the datatypes, the array of values might look like the following:
application comment startup max_file_sizeBy fetching the datatype information in addition to the column values, the array of values might look like the following:
application comment startup max_file_size 3 3 1 2A row of datatype (just like the row of column descriptions) is defined as
{ val[0], val[1], ...,val[NUM_OF_FIELDS-1] }Row numbers are counted cardinally from 0:
[0, 1, 2, ... , NUM_OF_ROWS - 1]The values placed into the row of datatypes are 0, 1, 2, or 3 corresponding to the values of
MAXL_DTINT_Tinsidemaxldefs.h.None = 0 Bool = 1 Number = 2 Char = 3As of this release, the new way to call
fetch_desc()is as follows:($column_name, $datatypes) = $dbh->fetch_desc();Prior to this release,
fetch_desc()was called as follows:$column_name = $dbh->fetch_desc();This will no longer return correct results, because
$column_namewill contain a datatype array instead of the column name. You must place the variable that is getting the return value inside parentheses, even if you do not want to fetch the datatype row. To retrieve only column names with the query results, use:($column_name) = $dbh->fetch_desc();Example
# # Returns a result set in the form of a table. # sub tab { my $dbh = shift; my ($colnum, $rec, $dt, $name, $tab, $line); # build an output table # setup the header ($name, $dt) = $dbh->fetch_desc(); for ($col = 0; $col < $dbh->{NUM_OF_FIELDS}; $col++) { $str = sprintf " %-19.19s", $name->[$col]; $tab .= $str; $line .= "+-------------------"; } $tab .= "\n$line\n"; # now populate the table with data $rec = $dbh->fetch_row(); while(defined($rec)) { for ($col = 0; $col < $dbh->{NUM_OF_FIELDS}; $col++) { if ($dt->[$col] == 3) { #format for characters $str = sprintf " %-19.19s", $rec->[$col]; } elsif ($dt->[$col] == 2) { #format for numbers $str = sprintf " %19.19s", $rec->[$col]; } elsif ($dt->[$col] == 1) { #format for bools if ($rec->[$col] == 0) { $str = sprintf " %19.19s", "FALSE"; } else { $str = sprintf " %19.19s", "TRUE"; } } $tab .= $str; } $tab .= "\n"; $rec = $dbh->fetch_row(); } $tab .= "\n"; if ($tab=~s/^\n//) { $tab=""; } return $tab; }
The @SHARE() function checks each member from rangeList to see if it has a shared member and returns a list of the shared members it has found.
Syntax
@SHARE(rangeList)
rangeList A comma-delimited list of members, functions that return members, and ranges. All the members in rangeList must be from the same dimension. Example
In the Sample Basic database:
@SHARE("100-10":"300-30")returns the shared members 100-20, 200-20, and 300-10.
Note: Use of a colon between member names denotes a range of members at the same level.
Fix Pack 2 adds the following new features to DB2 OLAP Integration Server 8.1:
To see what's new in Fix Pack 2 for Administration Services and to start the Fix Pack 2 installation, see Installing Fix Pack 2 for DB2 OLAP Server Administration Services.
The following links work only after you finish installing the fix pack.
User-Defined Tables
In DB2 OLAP Integration Server 8.1 Fix Pack 1 and later, you can create your own user-defined tables. These virtual tables, which behave as a standard RDBMS view, can be used anywhere a regular RDBMS table or view is used. This feature enables you to create and edit OLAP models without altering your relational schema or modifying the Integration Services generated SQL.
You create a table in the new User-Defined Table Definition dialog box by simply entering a name for the table and entering its SQL definition. The new table is listed in the left frame of the OLAP model main window.
Drill-Through From Secondary Data Sources
With DB2 OLAP Integration Server 8.1 Fix Pack 1 and later, you can create and run a drill-through report using both primary and secondary data sources. In previous versions of Integration Services, a system administrator could define primary and secondary data sources from which to load members and data; however, the system administrator could only create drill-through reports from the primary data source.
Fix Pack 1 and later fix packs enable the OIS system administrator to create a drill-through report that accesses data from the primary data source and to create other drill-through reports that access data from a secondary data source. With this feature, the spreadsheet user can drill through to data from multiple data sources that display on multiple sheets within a single workbook.
Enhanced Support for Recursive Hierarchies
DB2 OLAP Integration Server 8.1 Fix Pack 1 and later greatly enhances the support for recursive hierarchies by enabling you to perform the following tasks:
DB2 OLAP Integration Server 8.1 Fix Pack 1 and later gives you the option of saving your customized drill-through report filters for later use. After you select and modify a system-generated drill-through report with the Spreadsheet Add-in, you can elect to save the filter and store it in the OLAP Metadata Catalog. Later, you can pick and choose from a list of your customized report filters when performing a drill-through query using the Spreadsheet Add-in.
Replace Zeroes with #MISSING Option
DB2 OLAP Integration Server 8.1 Fix Pack 1 and later gives you the option of substituting zero values with the string #MISSING during data loads. This action provides several immediate benefits:
Protection of Changes During Disconnects
DB2 OLAP Integration Server 8.1 Fix Pack 1 and later prevents the loss of any changes to your OLAP model or metaoutline if you are disconnected from your data source, DB2 OLAP Integration Server, or the OLAP Metadata Catalog. This protection covers all changes that you enter while editing an OLAP model or metaoutline. Should a connection be lost, OIS lets you reconnect to the source, catalog, or server as needed.
OLAP Model Save As and Rename Commands
DB2 OLAP Integration Server 8.1 Fix Pack 1 and later extends the options available when you save an OLAP model. Earlier versions of Integration Services did not keep associated metaoutlines when an OLAP model was saved under a different name. Consequently, you were required to rebuild the metaoutlines for the new OLAP model.
In Fix Pack 1 and later, the Save As command is modified and a new Rename command is provided. These commands enable you to choose among the following options when saving an OLAP model:
After installing DB2 OLAP Integration Server 8.1 Fix Pack 1 and later, when you create or update an OLAP Metadata Catalog for the first time within a new release, a set of scripts is automatically run. These scripts enable you to migrate to the current release of Integration Services from your earlier version. Starting in Fix Pack 1, you can migrate automatically from all earlier versions.
Rapid Display of Tables
DB2 OLAP Integration Server 8.1 Fix Pack 1 and later displays up to 50,000 tables within the left frame of the OLAP model main window in significantly less time than was required in previous releases. Earlier versions of Integration Services read all the tables and all the columns in retrieving needed data; Fix Pack 1 reads the table names only and retrieves detailed information later when you expand the tables. This feature enables companies with very large data sources to import source tables rapidly for use in creating OLAP models.
Expanded Support of RDBMS Data Types
DB2 OLAP Integration Server 8.1 Fix Pack 1 and later adds several data types to its list of supported RDBMS data types on DB2 and SQL Server. For these databases, Fix Pack 1 supports the following additional data types:
DB2 OLAP Integration Server 8.1 Fix Pack 1 and later gives you the option of resetting your OLAP database prior to a member load or a member and data load. This feature can significantly reduce the amount of time required for the load.
Earlier versions of OIS provided you with the option to “Delete all members first” before a member load or a member and data load. Deleting all members first required that the OLAP outline be opened. If the outline was large or if there were drill-through reports in the outline, a significant amount of time was needed to open it. By enabling you to reset the OLAP database prior to the load, DB2 OLAP Integration Server 8.1 Fix Pack 1 empties the database outline, thus eliminating the necessity of opening it before the load can be started.
Cancel Button in View Sample
In DB2 OLAP Integration Server 8.1 Fix Pack 1 and later, the View Sample operation has been modified so that you can cancel the operation at any time without exiting from Integration Services or losing any changes that you have made to an OLAP model or metaoutline. This feature prevents time-consuming system processing and server disconnects when accessing an excessive number of data rows in the relational source.
Fix Pack 5.1 does not update the documentation.
The following information updates the 6.5.0 documentation.
The following support matrices list the levels of software supported by this fix pack:
The MaxL documentation for the spool on shell command incorrectly states that you can append to existing spool files. Writing to existing spool files overwrites the previous contents.
For example, if the file output.txt already exists and the following statement is
issued:
spool on to 'output.txt';
then output.txt is overwritten.
The following MaxL statement
alter database DBS-NAME validate data to local logfile FILE-NAME;
creates a local log file with all index combinations for which blocks contain invalid block headers.
Before using this MaxL statement, be sure that the server is not performing other operations, such as calculations or dataloads; otherwise, an exception error may occur.
The recommended procedure is:
For example,
alter application sample disable commands; alter system logout session on database sample.basic; alter database sample.basic validate data to local logfile 'invalid_blocks'; alter database sample.basic repair invalid_block_headers;
The following MaxL statements
alter
database DBS-NAME validate using error_file FILE-NAME;
or
alter database DBS-NAME validate using default error_file;
check the database for data and structural integrity. A file is created containing error
messages if there are problems. The default error file is VALIDATE.LST in the
application\database directory. For example: ESSBASE\APP\sample\basic\VALIDATE.LST.
The validate utility verifies the following:
The following MaxL statement
alter database DBS-NAME repair invalid_block_headers;
deletes all blocks that have invalid headers. Before using this statement, see information above for
alter database DBS-NAME validate data to local logfile FILE-NAME.
The documentation for the Hyperion Security Platform refers to directories and filenames that include "css-2_0_1" in the directory or file name. Due to internal changes, these directories and files now include "css-2_5_3" instead of "css-2_0_1" in the directory or file name.
If you are using NT LAN Manager authentication and you have users who will log in from UNIX, you need to install the Hyperion Remote Authentication Module on a Windows server. On the Essbase CD, the setup file can be found in the hram directory. Or, download the file from the Hyperion Download Center. Run esb6560hram_win32.exe and follow the prompts. Afterwards, be sure to complete the configuration of the
Note: The existing documentation for the Hyperion Security Platform refers to the NTLM Remote Server instead of Hyperion Remote Authentication Module. This component and its executable have been renamed since Release 6.5.5.
The environment variable ESS_CSS_JVM_OPTION (0 through 9) is available to address any platform and JRE version-specific options required by JVM.
ESS_CSS_JVM_OPTION1 is required on Solaris 1.4.1_06 if you are
using the security platform supplied by Hyperion. You must set an
ESS_CSS_JVM_OPTION environment variable to use a special Java
argument, Xusealtsigs.
Note: This requirement applies only to JRE version 1.4.1_06 on Solaris and is not
applicable to other JRE versions on Solaris. The only ESS_CSS_JVM_OPTION setting required for this release is -Xusealtsigs.
To set ESS_CSS_JVM_OPTION1:
setenv ESS_CSS_JVM_OPTION1 "-Xusealtsigs"
ESS_JVM_CSS_OPTION1=-Xusealtsigs;
export ESS_CSS_JVM_OPTION1;Essbase allows records that do not have members from each dimension to be loaded as long as the missing dimensions are specified in previous records. Except the first row, the subsequent records do not have to have members from each dimension. For any missing dimensions, the member names from the previous records are inherited.
The following support matrices list the levels of software supported by this fix pack:
A silent install (also called an unattended install) is done in a two-step process:
The file on which the install was recorded contains the user ID and password that was entered during the original installation. Be cautious to prevent disclosing this information, and the files should be destroyed when you are finished using them. The files can also be edited to change some data, such as user ID and passwords.
To record the installation on Windows, enter setup /r in the command line. Then proceed performing a normal installation.
Note:
if you select Reboot at the finish, the reboot will be recorded, and subsequent silent installations will also reboot.When done, the recorded installation will be saved in a file named setup.iss, and will be located in your system directory. On NT, the directory is most likely located in c:\winnt, although it could be different on some systems.
Next, you should create a copy of the IBM DB2 OLAP Installation CD on a networked drive or on the target system. Move the setup.iss file to the same directory that contains the setup.exe file (such as win32\). Execute the installation program from a command prompt. Go to the directory that contains setup.iss and enter "setup /s". The installation will start, and silently run to completion in the background. If you want to check whether the installation has completed, look for ikernel.exe in the task manager.
Before running a silent installation, it is necessary to run an installation using the IBM DB2 OLAP Server panel installation. This will generate file olapinst.rsp (or olapfp#.rsp for Fix Packs) that can then be used for silent installations. Ensure that the user running the silent installation has write privileges on the target installation directory. The response file can be located in any directory to which you have access on the server. Make sure to use the FULL path when passing the file name with its directory to the installation.
You can run the silent installation by calling setup.sh in the OLAP Server CD directory and adding the full path to the response file.
Example 1. Use a release installation response file that is in your home directory:
./setup.sh /home/username/olapinst.rsp
Example 2. Use a fixpack installation response file that is in the installation directory (using /home/essbase as an example of the ARBORPATH):
./setup.sh /home/essbase/install/olapfp1.rsp
The following parameters are set in the response file:
Note:
You can change these parameters as needed.The silent installation will update the olapinst.ini and olapinst.log files with installed components and note any errors encountered during the installation. It will also display, on the console, information on the progress of the installation while it is running.
As a general rule, a silent install should take no more than 15 minutes. It will take slightly longer than an interactive installation on the same computer. When the silent install starts, a minimized icon labeled "Setup" appears on the taskbar. However, there is no progress bar or other indication of how long the silent install should take. Silent install works in the same way as interactive installation. Do not interrupt the installation program because doing so can result in an incomplete environment.
If you want to check the progress of the silent install, use the Windows Task Manager to check whether ikernel.exe. is running. If the process appears frozen in the task manager, look for a response window hidden under another window on your desktop. Also, be sure there is no network failure if you are installing over the network.
IMPLIEDSHAREONMINUS specifies that single parent/child members whose child's aggregation symbol is MINUS are treated as implied share.
Syntax
IMPLIEDSHAREONMINUS TRUE | FALSE
TRUE means that single parent/child members whose child's aggregation symbol is MINUS are treated as implied share.
FALSE means that single parent/child members whose child's aggregation symbol is MINUS are not treated as implied share.
Note: This setting should be used only if problems are occuring with attribute associations; for example, if an outline looks correct in Application Manager but has incorrect attribute associations when displayed in Spreadsheet Add-in or the outline query API. If attribute associations are incorrect, setting IMPLIEDSHAREONMINUS to TRUE will fix the problem.
The documentation for the EsbOtlGetLevelName and EsbOtlGetGenName functions should state that a level and/or generation name must be added to the outline in order for these functions to work properly.
Before issuing the VALIDATE command, Hyperion recommends placing the database in read-only mode.
The maximum number of aliases that can be displayed by EssDisplayAlias is 32K.
The VBA functions EssVSendData and EssMenuVLock do not work when used together.
The documentation for the DISABLELOGINS command (ESSCMD) should include a statement indicating that database connections are re-enabled if the application is stopped.
Drill-Through operations (for Essbase Integration Services or other related purposes) are also available in the Essbase Grid API.
For Release 6.5.5, there are a few limitations to the platforms and drivers that are supported for DB2:
In addition to the configuration information found in Installation Notes and in the Security Platform Reference (a new book available in Fix Packs 3 and later), 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 Windows
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 |
After uninstalling clients that were installed over a network, client image remains on network.
If you installed clients from a network and then uninstall them, the client image on the network is not uninstalled. Contact your system administrator about removing the client image from the network. This is not documented in the Installation Guide.
Valid TEMP or TMP environment variables
Your TEMP or TMP environment variable must point to a valid directory location (a location that exists) when working with Essbase, EAS, EIS or Application Manager. Otherwise Essbase may have trouble creating temporary files.
No spaces in MEMORYLIMIT valueThis corrects the documentation for the memory configuration file from the
6.5.1 readme file. In the memory configuration file (config.mem, stored in
ARBORPATH/bin), be sure that there are no spaces between the memory limit value
and unit in the syntax of the memory limit setting. The format is:
MEMORYLIMIT nG|M
Where n is a whole
number, the number of gigabytes or megabytes. Use either G or M to indicate
gigabytes or megabytes. For example:
CLEARBLOCK NONINPUT description updateMEMORYLIMIT 2G, or MEMORYLIMIT 1024M
This corrects the documentation for the CLEARBLOCK calculation command in the
Essbase Technical Reference. The NONINPUT parameter for this command should be
described as follows:
NONINPUT: Clears blocks containing values derived
from calculations. Applies to block that are completely created by a calculation
operation. Cannot be a block into which certain values were loaded through a
data load operation.
This corrects the documentation for the MAXLOGINS configuration setting in the Essbase Technical Reference. The default for the MAXLOGINS configuration setting has been changed from 1,000 to 10,000.
New NETBINDRETRYDELAY Configuration SettingNETBINDRETRYDELAY specifies the amount of time, in milliseconds, that the application server retries on a bind failure.
Syntax
NETBINDRETRYDELAY n
| n | Integer value, expressed in milliseconds. The default value is 10
seconds. The minimum value is 0. |
Configuring your spreadsheet program manually
If you have Lotus 1-2-3 or Excel installed before you install DB2 OLAP
Server, the installation program for DB2 OLAP Server detects the spreadsheet
program and configures it to work with OLAP applications. But if you
install Lotus 1-2-3 or Excel after installing DB2 OLAP Server for the first
time, you must configure the spreadsheet program manually. Follow these
steps:
If license error occurs when installing on UNIX, leave "other" directory blank
If you are running the installation and you reference an "other" OLAP directory for the license information, and the installation cannot detect the directory, leave the directory blank on the panel where you are prompted for the "other" directory. The installation continues, and later in the installation process you are prompted for the license information.
On UNIX, use only the Fix Pack installation to add components
After you install Fix Pack 1 or later on UNIX, you must use the Fix Pack installation program to add any additional components to your UNIX system. If you run the GA-level installation program after installing Fix Pack 1 or later, the license program causes an error. After you enter the license information you are prompted with a list of OLAP components. The products detected on your existing 8.1 installation will be checked and you can check additional products to add to the installation.
On Windows, stop servers before running Modify Component or License Information
In the Windows installation program, on the Setup - Maintenance panel, when you select the Modify or Repair actions, the installation program attempts to stop the server components so they won't interfere with the action. Under some circumstances, the servers might not stop successfully. IBM recommends you manually stop the servers for all DB2 OLAP Server products before running the Modify or Repair actions.
On AIX, do not use the "./olapisvr" command to start the OIS server
On AIX, if you try to start the server component of DB2 OLAP Integration
Server using the command './olapisvr', a core dump occurs. To start the
server successfully, invoke the $ISHOME/hisjava.sh file to set up
the OIS environment variables, and then run the olapisvr command to
start the server. For example:
arbor@cubogrande:/olaptest/jian/tc030_si/is/bin >
./olapisvr
Tip for using 'Aggregate Missing Values'
If your database allows or requires 'Aggregate Missing Values' setting set to YES, then you may want to consider using ZLIB as the compression scheme. ZLIB particularly works well on such databases compared to other compression schemes. However, changing the aggregate missing values setting may have an impact on calculation results - see the Database Administrator's Guide. Consider using ZLIB only if you have already determined that the setting should be YES for other reasons.
Tip for validating outlines that use formulas with customer-defined functions
Outlines containing formulas that use custom-defined functions (CDFs) cannot be validated on the client. Outlines containing CDFs must be validated on the server.
Installations on UNIX require adding $arborpath/dll to LD_LIBRARY_PATH
Currently, the Installation Guide states that you need to set $arborpath/dlls to LD_LIBRARY_PATH before you can run SQL Interface. In fact, you must set $arborpath/dlls to the LD_LIBRARY_PATH environment variable for any UNIX installation regardless of whether you use SQL Interface. (28270)
New configuration setting to support ragged hierarchies
A new configuration file setting, HARAGGEDHIERARCHY, enables support of null values in columns of dimension tables that are used to create dimensions for Hybrid Analysis-enabled outlines. The dimension build that these dimension tables result in the outlines are known as ragged hierarchies.
NOTE: The HARAGGEDHIERARCHY setting is not valid for the Accounts dimension.
If you have null values in columns of dimension tables used to create
dimensions in an Hybrid Analysis-enabled outline, use the
HARAGGEDHIERARCHY setting in essbase.cfg to enable Hybrid
Analysis to account for these null values during SQL generation.
Syntax
HARAGGEDHIERARCHY [appname [dbname]]
TRUE | FALSE
| appname | Optional parameter. If you supply an application name, the setting applies to all databases within the named application. If you do not supply an application name, the setting applies to all applications and databases on the server. |
| dbname | Optional parameter. If you supply a database name and an application name, the setting applies only to the named database. If you do not also provide an application name, the database is ignored and the setting applies to all applications and databases on the server. |
| TRUE | Setting the value to TRUE enables Hybrid Analysis to account for null values during SQL generation. Note that this setting may have impact on performance because SQL generation is not optimized well on most relational databases. |
| FALSE | Setting the value to FALSE prevents Hybrid Analysis from recognizing the null values or gaps in the ragged hierarchy. This option does not affect performance. The default is FALSE. |
(56003)
Correction to Hybrid Analysis Configuration File Settings
The following Hybrid Analysis configuration file settings are missing the application and database parameter in the documentation. Specifying the application and database is optional and lets you apply the configuration setting at the application, database, or global level. The correct syntax is given below:
HAENABLE [appname [dbname]] TRUE | FALSE
HAMAXNUMCONNECTION [appname [dbname]] n
HAMAXNUMSQLQUERY [appname [dbname]] n
HAMAXQUERYROWS [appname [dbname]] n
HAMAXQUERYTIME [appname [dbname]] n
HARETRIEVENUMROW [appname [dbname]] n
ODBCINI Environment Variable Needs to be Set for UNIX Platforms
To run Hybrid Analysis on UNIX platforms, set, in the .profile, the ODBCINI environment variable to $ARBORPATH/ODBC.INI, which contains the definition for the relational data source. (55168)
Quicklogin No Longer Required to Start Parallel Login Processing
To enable parallel login processing when you start DB2 OLAP Server, you no longer need to specify essbase password -quicklogin or set the QUICKLOGIN command in the Essbase configuration file. DB2 OLAP Server automatically starts up with parallel login. (55520)
Incremental Restructuring Turned Off When Adding Shared Members
Adding shared members to an outline automatically turns off incremental restructuring. (55467)(55470)
Correction for EsbGetDatabaseInfo Example
The example for the EsbGetDatabaseInfo Visual Basic API documentation contains errors.
The following sample code is incorrect:
If sts = 0 Then For n = 1 To Items sts = EsbGetNextItem(hCtx, ESB_REQINFO_TYPE, Items) Next End IfThe correct code is:
If sts = 0 Then For n = 1 To Items sts = EsbGetNextItem(hCtx, ESB_DBREQINFO_TYPE, DbReqInfo) Next End If(43501)
Correction to Hybrid Analysis Guidelines
The following information updates the documentation in Appendix D of the Database Administrator's Guide:
Hybrid Analysis has some guidelines with which you should be familiar:
Correction to ESTIMATEFULLDBSIZE Documentation
The following text corrects the ESTIMATEFULLDBSIZE ESSCMD documentation in the online Technical Reference.
Outlines that contain sparse formulas of any type or topdown formulas are not supported. Results of the estimation on such databases may be invalid.
Syntax
ESTIMATEFULLDBSIZE
Description
You can select an application and database, then issue this command. DB2 OLAP Server returns the number of blocks the database creates. The database can have all data loaded, or it can have a random sampling of data loaded.
Example
Assume that you have fully loaded Sample Basic. Use this command before
calculation to predict the number of blocks that the calculation would create if
it were executed. This example shows the command and the output that results:
estimatefulldbsize;
Estimated count of blocks after full
calculation = 335
Time elapsed to calculate this estimation = 0.02
seconds
(55822)
Range List Requirement Removed
Functions that take a range list as a parameter no longer require that the list contain only members from the same dimension. (39993)
The following customer reported problems are fixed in DB2 OLAP Server and DB2 OLAP Integration Server V8.1. Vantive ID numbers are listed first; numbers in parentheses are internal reference numbers for Hyperion Solutions; numbers in brackets indicate previous Hyperion tracking numbers.
On Japanese systems, installing Fix Pack 5 could not be installed on systems
that had DB2 OLAP Integration Server on them.
The console cannot connect to the sever. (IBM 7914, 7952, 7962)
A replicated partition fails to replicate #Missing values. 121590(57587)
A replicated partition that works in Version 7.1, Fix Pack 9 (Essbase 6.2.2) fails to replicate #Missing values in
Version 8.1 and subsequent Version 8.1 fix packs (Essbase 6.5.x
releases).
A dimension build returns an error even though it completes successfully. 172820(61850)
A SQL Interface dimension build, performed using MaxL, returns the following error message:
ERROR - 1241101 - Unexpected Essbase error 1030001
Although this error is displayed, the dimension build is successful and the outline is updated correctly.
Calculations using @SANCESTVAL and @SPARENTVAL may take longer than expected. 173125(61879)
A calculation that uses @SANCESTVAL and @SPARENTVAL takes much longer in Version
8.1 (Essbase 6.5.x) than in Version 1 Fix Pack 12 (Essbase 5.0.2p12).
Two-pass Dynamic Calc tags on sparse accounts members may return incorrect results. 246820(66152)
When dense Dynamic Calc members are present in the outline, two-pass dynamic calculations on accounts members that are sparse may return incorrect results.
Database access is incorrectly granted to a user without permission to access the application. 281621(68511)
If a user or group is granted application and database access, and later the application access is revoked, the user or group may still have database access.
DB2 OLAP Server appears to fail to span drives during a restructure. 282930(68658)
Restructuring results in an error message and appears to fail (even though it is actually successful) if the current data/index volume is exactly 100% full when the restructuring begins.
The EssOtlNewOutline API function creates an outline that does not work. 283512(69538)
Running the ESSCMD GETATTRIBUTESPECS command against an outline created using EssOtlNewOutline fails and causes an exception log to be created.
Calculation may fail with error number 1012601. 285095(70230)
During a batch calculation, if an upper level member in a sparse dimension has a child that is non-consolidating, the calculation may be aborted with error number 1012601.
When upper level blocks are created using the DATACOPY command, the database may fail to aggregate data properly. 288138(70663)
When upper level blocks are created by the DATACOPY command, the database may fail to aggregate data properly.
Modifying a filter using MAXL causes the filter to lose its association to the user. 289349(70761)
Using MaxL to modify a filter causes the filter to lose its association to the user.
Spreadsheet Add-in may display the incorrect styles. 289471(70806)
In the Spreadsheet Add-in, data cell styles have the following order of precedence:
1. LRO
2. Drill through
3. Read only
4. Read/write
If a data cell is a combination of both a lower option and a higher option, for example, LRO and Read/write, and the higher option is not selected to use styles, but the lower option is, then no style is displayed. The correct behavior is for the style associated with the lower option to be displayed.
Exported data may be larger in size than the database from which it is exported. 290334(71090)
Exporting data from a database that is less than 2 GB in size may result in an export file that is greater than 2 GB in size, and the export may fail to complete. Subsequent attempts to import the data (from the export file that is created) may fail.
An excessive number of entries about outline queries may be written to the
application log file. 291974(71187)
If an excessive number of entries about outline queries are written to the
application log file, you have the option to turn off logging of outline queries. To turn off logging of outline queries, set the following in your essbase.cfg file:
SILENTOTLQUERY TRUE
Terminating asynchronous requests from the application manager may fail, causing the application to hang. 298010(71906)
Terminating asynchronous requests from the application manager may fail, causing the application to hang.
The PRINTPARTITIONDEFFILE ESSCMD command may fail and return an error message. 298404(72203)
The PRINTPARTITIONDEFFILE ESSCMD command may return the error message "cannot create object 1030201."
Attribute retrievals are faster in Version 8.1 (Essbase 6.5.0) than in subsequent
Version 8.1 fix packs. 351397(72365)
Retrieval times for attribute dimensions have degraded in V8.1 fix packs
(Essbase releases later than 6.5.0.)
Garbage object names are displayed while using the "drop database" MaxL command. 356837(72797)
Garbage object names are displayed while using the "drop database" MaxL command.
SSAUDIT may not create log files when combined with DYNCALCCACHEMAXSIZE setting in essbase.cfg file. 358581(72894)
With SSAUDIT and DYNCALCCACHEMAXSIZE both set in the essbase.cfg file, SSAUDIT may fail to work properly.
Upper-level members are incorrectly overwritten by #Missing. 360061(72971)
When AggMissg is set to OFF, the NO SKIP tag is used, and all zero level members are #Missing, upper-level members are incorrectly overwritten with #Missing.
Japanese Essbase may incorrectly interpret lower case characters as uppercase. 360336(72997)
If alphabetic characters are entered as double-byte characters, Essbase interprets lowercase characters as uppercase. For example, during a dimension build, double-byte "abc" is stored as "ABC".
Replicating data takes longer in Version 8.1 Fix Pack 2 (Essbase 6.5.3) than it did in an earlier release. 360493(73030)
Replicating partitioned data, where the source and target are on the same application, takes much longer in
Version 8.1 Fix Pack 2 (Essbase 6.5.3) than it did in Version 1 (Essbase 5.0.2).
Drilling down on a Hybrid Analysis member in Spreadsheet Add-in returns incorrect error.
For outlines with user-defined members, which are used in the member formula, drilling down on a Hybrid Analysis member in the Excel Spreadsheet Add-in returns the following incorrect error: "Error 1198075: The metaoutline Moduleid 0 is invalid." 364034(73232)
The VB API function EsbBuildDimension may fail to update the outline. 364390(73329)
The VB API function EsbBuildDimension appears to work and it does not return an error message, but it may fail to update the outline.
Uninstalling DB2 OLAP Server removes OLAP applications. 364661(73394)
Numerous files are removed from the ARBORPATH\app directory when the
OLAP server is uninstalled. The removal of these files renders the OLAP applications useless.
Spreadsheet Add-in terminates abnormally when retrieving a large number of rows in free form mode. 365450(73606)
When retrieving more than 65536 rows in free form mode, the Spreadsheet Add-in terminates abnormally. The fix for this problem is to generate an error stating that the report has been truncated.
Retrieving a two-pass member with the @MDANCESTVAL function may cause the application to crash. 365453(73608)
In the Spreadsheet Add-in, retrieving a two-pass member with the @MDANCESTVAL function may cause the application to crash.
Calculation notices may be written more frequently than CALCNOTICE settings in the essbase.cfg file. 366652(73855)
Calculation notices may be written to the application log more frequently than CALCNOTICE settings if the calc script contains SET MSG ERROR command.
Attribute retrieval may return incorrect values. 366736(73990)
Zoom-in on attribute members in Spreadsheet Add-in may return incorrect values if one or more of the associated base members has no siblings.
Dimension Build via an ESSCMD script may return an incorrect error code. 366926(74031)
An esscmd script that performs a dimension build returns an incorrect error code with a status of zero (sts = 0 Reject).
Replicating data may cause an application to terminate abnormally. 367203(74148)
Replicating partitioned data may cause the source database to terminate abnormally if the user has filter access.
The CALC ALL command may not aggregate data properly. 367646(74540)
When upper level blocks are created by any means other than a dataload or normal aggregation based on outline hierarchies, the database may fail to aggregate data properly.
Setting a specific calc script as the default causes the Essbase server to terminate abnormally. 367907(74598)
Setting a specific calc script as the default causes the Essbase server to terminate abnormally.
Report runs more slowly than expected. 368091(74664)
A report may take significantly longer to run after a calculation or after restarting the application or reloading the database.
A calculation involving a top-down member may return incorrect results. 368139(74689)
A calculation involving a top-down member may skip some members in the calculation, thus returning incorrect results.
The @TRUNCATE function rounds numbers instead of truncating them. 368402(74790)
The @TRUNCATE function changed behavior after Release 5.0.2, incorrectly rounding numbers instead of truncating them.
Calculations may take longer than expected. 368406(74793)
Calculations may take longer in release 6.5.4 than in release 6.5.0. Add the following setting to the essbase.cfg file to improve performance in this case:
AggressiveBlkOptimization TRUE
Retrievals that include multiple attribute dimensions may return incorrect results. 368564(74852)
Retrievals that include multiple attribute dimensions and shared members may return incorrect results.
Some calculations using @VAR may terminate abnormally. 368236(74853)
Running a calc script that contains more than ten instances of @VAR may cause the application to terminate abnormally.
Replicating partitioned data may cause the application to terminate abnormally. 368651(74884)
When dynamic time series members are present on the source but not on the target, replicating partitioned data that includes the dynamic time series members may cause the application to terminate abnormally.
Style setting for LROs are lost when the database is unloaded. 368983(74989)
In the Spreadsheet Add-in, styles for LROs are lost when the database is stopped.
Report may fail to return a shared member. 369074(75011)
If a real and a shared member have different alias names, and the user specifies the alias name of the shared member in a script, the report writer incorrectly displays the real member instead of the shared member.
Incorrect data may be retrieved from dynamic calc members that are dependent on two-pass dynamic calc members. 369302(75076)
Retrieving data for two pass dynamic calc members that are dependent on other two-pass dynamic calc members may return incorrect results.
Locking and sending data fails when a member name exceeds eighty characters including leading spaces. 369315(75081)
When a member name exceeds eighty characters including leading spaces, locking and sending data for that member may fail. Leading spaces are created by turning on the indentation subitems option in the options dialog box.
Drill-through report forces a logout and automatically reconnects only the most recent user. 369730(75187)
If a user has two or more spreadsheets in the same Excel workbook open and connected to
DB2 OLAP Server under different usernames, executing a drill-through report in any of the spreadsheets will, unknown to the user, log off all users and log all spreadsheets back in using only the username and password of the most most recently created user connection.
Dimension build stops loading if a member in data source is exactly eighty-one characters long. 370458(75421)
A dimension build containing a member that is exactly eighty-one characters long stops loading when it reaches that member.
A dimension build that updates attribute members may fail. 370790(75525)
A dimension build that updates attribute members may fail.
A calculation deadlock may cause the application to refuse further requests involving data. 370824(75535)
When two or more calculations executing concurrently overlap in the blocks
they attempt to update, and a deadlock occurs, the aborting transaction
causes the application to enter a state where it can refuse to accept
further requests involving data.
A parallel calculation may cause the database to terminate abnormally. 371220(75701)
The database may terminate abnormally during a parallel calculation with an @XREF member formula on a dynamic calc member that is a dependent of a regular member formula.
An attribute calculation may return incorrect results. 373157(76496)
An attribute calculation where a two-pass calc member is defined on a base dimension with shared members may return incorrect results.
Report writer may hang and return an error if a connection to Analyzer is forcibly terminated. 373290(76553)
Report writer may hang and return the error "Abnormal Exit From Report Writer" if a connection to Analyzer is forcibly terminated.
Dimension build may fail if the data source file contains blank records surrounded by double quotes (" "). 373363(76602)
Dimension build may fail if the data source file contains blank records surrounded by double quotes (" ").
The @XREF function may fail when used with IF statements. 373562(76704)
Calculations that use the @XREF function with IF statements may return incorrect calculation results.
Sparse restructure may cause a partitioned database to terminate abnormally. 373660(76751)
A sparse restructure against the target database of a transparent partition may cause certain server requests (such as validating the partition) to terminate the database abnormally.
A dimension build may fail to add a prefixes or suffixes to alias names. 374061(76953)
A dimension build designed to add prefixes or suffixes to alias names containing double quotes may fail.
Dimension builds reject records that contain double quotes. 374154(77011)
Dimension builds may incorrectly reject records that contain double quotes.
Running C API code that modifies an outline may cause the application to terminate abnormally. 374818(77390)
An application may terminate abnormally and an .xcp file and core file may be created while running C API code that modifies an outline.
Incorrect calculation results may follow a level zero restructure. 374880(77428)
Adding level zero sparse members to an outline and then performing a level zero restructure may cause calculations to return incorrect results.
Using a MaxL script to run multiple report scripts may cause the application to terminate abnormally. 376217(78242)
Using a MaxL script to run multiple report scripts may cause the application to terminate abnormally.
Outline synchronization may fail to propagate changes to level-one attribute data. 376237(78246)
When level one attribute members are added to one outline, and the outline changes are propagated to the second outline, those attribute members are not added.
The EsbOtlAddMember may fail to add text type attribute members. 376286(78259)
Using the EsbOtlAddMember API function to add members to an attribute dimension may fail when the attribute type is text.
OLAP server may crash when drilling to level-0 attribute member.
In some cases, the OLAP server (esssvr) crashes when drilling down on a level-0 attribute member. 379765(79576)
Attribute report scripts may return varying results.
Certain report scripts that query an attribute dimension return different output file size and records of data based on the location of the parent of the attribute dimension in the script.
OLAP Server does not compensate for Daylight Savings Time.
(496719)
The time stamp in the OLAP Server does not recognize Daylight
Savings Time in relation to Greenwich Mean Time (GMT).
Retrieves with multiple attribute dimensions have incorrect rollup
(368564)
Retrieves with multiple attribute dimensions has incorrect
rollup.
Fix Pack 3 disables CSS/LDAP function.
After installing Fix Pack 3,
you cannot configure or initialize LDAP.
Warning when retrieving in SQL Interface. 356417(72680)
A warning
message is being returned even when the correct Merant 4.1 Sybase Wire Protocol
drivers are being used, which is affecting nightly batch loads. The warning
message is no longer displayed.
Problem with Japanese Characters in installation files.
30300(28959)
In Windows Explorer, Japanese characters are broken in the
file properties of the icons for the installation program.
@ROUND function produces inconsistent results. 168062(61475)
The
@ROUND calculation function rounds numbers inconsistently; for example, two
numbers both ending in .765 may round to different directions (one to .76, one
to .77).
Parallel calculation does not consolidate to parent of implicit share.
281745(68571)
Running a parallel calculation may fail to consolidate to
the parent of an implicit share member during intelligent recalculation.
Problem with parallel calculation and FIX. 355526(72612)
During
parallel calculation, if a member formula contains cross-dimensional operators
(->), the formula execution may calculate all members in the
cross-dimensional list regardless of the FIX statement.
@POWER function produces different results on Solaris.
137817(58151)
The @POWER calculation function produces different results
on Solaris operating systems and Windows operating systems when the exponent is
a negative number.
Error message returned incorrectly during data load.
173845(63536)
An error message is being returned during data load
indicating that there are duplicate members from the same dimension on the data
record. There are no duplicate members from the same dimension on those records,
so the error message should not be returned and the load should complete.
Intelligent Calc using CALC DIM does not consolidate properly.
291825(71173)
Intelligent Calculation using the CALC DIM command does not
consolidate properly. The issue of not creating upper level blocks during
intelligent calculation is restricted to using CALC DIM as opposed to CALC ALL.
@SUM function for Two-Pass Dynamic Calc member returns incorrect results
for attribute retrieval. 162407(60454)
A calculation using the @SUM
calculation function for a Two-Pass Dynamic Calc member returns incorrect
results when the retrieval includes attribute members.
@MDPARENTVAL calculation does not work on Dynamic Calc parents.
360518(73035)
A calculation using the @MDPARENTVAL calculation function
does not work on Dynamic Calc parents. The same calculation worked correctly
with DB2 OLAP Server, V7.1, Fix Pack 8 or later (Essbase Analytic
Services 6.2.x).
Export/import operation incorrectly moves decimal places.
287592(70631)
After exporting, clearing, and importing data, certain
values are incorrect because the decimal place has been moved. DB2 OLAP
Server V8.1, Fix Pack 3 (Essbase Analytic Services 6.5.4) is the only release
impacted by this problem.
During export, locked cells crash the application.
163418(60804)
During an export operation, if any user is in the middle of
a spreadsheet Lock&Send operation while the export is being performed, the
application may crash.
Incorrect results returned with attribute retrieval.
294226(71538)
Incorrect results are returned on an attribute retrieval
when there is a formula on a sparse member that is dynamically calculated.
Certain attribute retrievals return incorrect results. 281680(68536)
When an attribute query contains shared members from two different base
dimensions, retrieval may return incorrect results.
Parallel calculation crashes application. 173750(63493)
During
parellel calculation, if DB2 OLAP Server cannot split the calculation into four
threads as specified, it must automatically execute the script with one thread.
On Windows, this behavior works fine, but on Solaris, the application
crashes.
Parallel calculation returns incorrect results.
291956(71183)
Parallel calculation may produce incorrect results if a
regular stored member has a formula that is dependent on a Dynamic Calc member.
Incorrect calculation results with values divided by very small numbers.
173408(61959)
Precision error caused by floating point arithmetic may
produce incorrect results in calculation due to values divided by a very small
number.
DATACOPY not working with a replicated partition.
162900(60632)
Data is missing after running the DATACOPY command on
a replicated partition.
Partition definition for slice does not parse when a mixture of
commas and spaces are used as delimiters. 50259(55526)
Partition
will not validate if a mixture of comma delimiters and space delimiters is used
in a partition.
Need to provide an easier way to distribute the Excel Spreadsheet
Add-in to a client machine that has a secure WINNT directory.
290275(71074)
Distributing Excel Spreadsheet Add-in to a large
number of client machines that have a secure WINNT directory is cumbersome
because you have to install to each client as an admin and then have them log in
the first time. This problem has been fixed so that the essbase.id file is now created in home/temp/tmp (in that order, whichever is available) if a
user does not have permission to the WINNT directory.
Message 'Invalid member in global map' is not translated into
Japanese. 38360(14776)
On Japanese clients, the following error
message text is not translated into Japanese: 'Invalid member in global
map'.
If query logging on source and target partition is enabled, an
exception is thrown at the source when drilling down in Excel Spreadsheet Add-in
on the target database. 166920(61042)
If query logging on source and
target partition is enabled, the source application crashes with an exception
when drilling on the target database in Excel Spreadsheet Add-in. Additionally,
if no valid query logging buffer is provided, then the query logging at source
option should be disabled.
Transparent partition performance impacted by change in how it
operates with 'distributed requests'. 364659(73397),
173160(61885)
If a calculation is run against the target on members
outside the area definition but specifies a member that is used within the area
definition, DB2 OLAP Server starts a distributed request although a distributed
request is not required. Batch calc setup should check for local sparse members
(which are part of the calc) that depend on remote members before making
distributed requests.
When the Retain on Zoom option is selected, performing a drill-up in
Excel Spreadsheet Add-in gives inconsistent results.
118832(56930)
In Excel Spreadsheet Add-in, the behavior is
unpredictable if the Retain on Zoom option is selected. For some members the
results are correct, but for others it duplicates members or puts them below the
dimension.
Transparent partition data is not rolling to the top of a sparse
dimension on the target database. 116157(56386)
When running a Calc
All on a target database that includes a member that is transparently
partitioned, the transparent data does not roll up properly unless the Aggregate
Missing database setting is enabled.
Transparent partition data on the source database is not showing at
the top level of the target database. 157947(60052)
Even though
partitions are validating properly and are running correctly from the target
database, the top number on the target database is missing. This is because
Dynamic Calc is not triggering on the source database.
Japanese issue: In Excel Spreadsheet Add-in, the Essbase toolbar
remains after selecting Close. 120835(57407)
In Excel Spreadsheet
Add-in, the Essbase menu disappears after selecting Close, but the Essbase
toolbar remains. Then if you select an item on the Essbase toolbar, an error
message displays.
Japanese translation issue on menus. 39816(24690)
DBCS
characters on the pull-down menus appear corrupted.
Dimension load attributes associates with multi-level members
incorrectly with some members. 119030(56980)
When updating an
outline with attribute members associated with base members, some attributes are
associated with incorrect base members.
Dimension build hangs server when case-sensitivity is used on member
names. 40959(27920)
If case-sensitivity is enabled, members with
unique names (for instance, Squid and squid) are not building properly and are
not associating dynamically.
Dimension build is not successful on DB2 OLAP Server
V8.1, Fix Packs 1 through 3 (Essbase Analytic Services 6.5.1 -
6.5.4), but it is working on DB2 OLAP Server V8.1, General
Availability level (Analytic Services version 6.5.0). 279457(68258),
283876(70200)
Attribute build at level zero associates attributes to
different levels in the outline. Member is being updated with an attribute that
is not even called out in the data.
When loading member formulas, Analytic Services is dropping the
double quotes (" ") for formulas with long names.
49617(55340)
While reading the dimension build source file, Analytic
Services only reads the sub-string inside a pair of double quotes and ignores
the double quotes. This causes Analytic Services to drop the double quotes when
loading member formulas.
Changing a shared member to a stored member and then renaming it
causes application to crash with exception. 290380(71114)
Changing a
shared member to a stored member and then renaming that member causes an
application crash with exception log.
Warning from the Analytic Services Perl Module.
167408(61211)
When running MaxL in Perl using the connect function,
a warning message displays.
Using MaxL, alter user username enable not working.
278690(66603)
MaxL fails to re-enable a user if the user is disabled
by Password Management check.
When using MaxL, granting both filter access and a calc script access
enables user for "All Calc's". 167747(61366)
If you use MaxL to
grant a user filter access and access to a calculation script, the user is
granted access to "All Calc's".
"Source Data" not translated correctly in Japanese Application Manager.
114655(56044)
In the Japanese Application Manager, in the Database >
Data Replicate > Source Data menu selection, the phrase "Source Data" is not
correctly translated.
Data field lengths greater than 600 characters may cause dimension build
crash. 119948(57208)
If a data input file contains fields longer than 600
characters, the dimension build process may crash.
"Object" not translated correctly in Japanese Application Manager.
164588(60997)
In the Japanese Application Manager, open the Data Load
Rule dialog box. Edit the information. Select File > Close. The word "object"
in the Save File dialog box is correctly translated, but the last Japanese
character (katakana) is missing.
"Invalid serial number" error message is not translated correctly in
Japanese Application Manager. (60184)
When an unregistered copy of
Application Manager is created in the $ARBORPATH\BIN directory and is launched,
the "Invalid serial number" error message is displayed but the translated
message is not correct in Japanese.
Dimension build may take 100% of CPU cycles and take hours to complete.
157744(60000)
When the outline change log is enabled, rebuilding
dimensions may take hours to complete and consume 100% of CPU resources.
Outline changes involving many attributes may not synchronize with
transparent partitions, and Application Manager may not display an error message
when this happens. 289702(70897)
When making outline changes on a
transparently partitioned database with many attribute dimensions, the outlines
may not synchronize and Application Manager will not display an error. The error
becomes evident when validating the partitions after synchronization. The error
message may read "Base dimension members in slice {x} have different mappings
for {} attributes."
MaxL script containing "execute calculation" may cause Essbase service to
stop. 119757(57172)
Running certain extremely long calc scripts through
MaxL may cause the Essbase service to stop and an exception log to be
generated.
MaxL partition definition not valid.
165702(61008)
Using variables in a MaxL
partition definition file returns a warning message stating that the
partition definition is not valid. The warning is returned because of invalid
syntax in the script. The syntax should be changed so that the first area
definition is enclosed in double quotation marks as well as single quotation
marks. An example has been added to the documentation for future releases.
Calc script performance may be slower in DB2 OLAP Server V8.1, Fix Pack 1
(Essbase Analytic Services 6.5.1) than in the V8.1 General Availability
level (Essbase Analytic Services 6.5.0). 281803(68596)
Upgrading to
Fix Pack 1 might cause some calc scripts to take significantly longer to
execute.
Partition Wizard - Close dialog box not translated correctly in Japanese
Application Manager. 38361(14777)
In the Japanese Application Manager,
select Database > Partition Manager, then select Partition > New. When you
reach the "Partition Wizard - Close" dialog box, the English word "To" is
displayed.
"Network Cannot Send Data" and access errors when running large queries.
279472(68267)
Running certain extremely large queries may cause the
Essbase application to crash, generating a "Network Cannot Send Data" error and
generating an xcp log.
Incomplete data returned in certain report scripts.
162458(60470)
If {OUTALTNAMES}<OUTALTSELECT "Default" instead of
{OUTMBRNAMES} is used in a report script, incomplete data is being returned.
This problem has been fixed by increasing the size of the report output
buffer.
Running a report with long member names may truncate the results.
157992(60066)
Running a report in Essbase that retrieves members with
extremely long names may cause columns of data to be missing from the
report.
Use of <TOP command in report script causes incorrect formatting.
281594(68500)
When a report script contains the <TOP command, the
first line of the report may not be formatted correctly.
Network connection persists after running script containing @XREF formula.
162038(60362)
When one of the dynamic calc members of a database has an
@XREF formula as a member calc and is retrieved into a spreadsheet, the network
session connection may remain active even after the retrieval is complete and
the spreadsheet has disconnected from the database.
Essbase calculates named user port usage incorrectly.
290198(71053)
When Essbase calculates named user port usage, it applies
concurrent user rules. This can cause one user connection to count as multiple
named users.
Error message: "Number of users defined is greater than number licensed."
163096(62049)
In certain cases, Essbase incorrectly counts the number of
groups rather than user when the following warning message is displayed: "Number
of users defined [X] is greater than the number licensed [Y]."
Drill through report sort order not saved correctly in metadata on AIX (370320)
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.
Unable to open Custom Macros/Functions help in Japanese Application Manager
(7922)
Workaround: see the technical reference for help.
"Open" button does not work in the Formula Editor (7923)
Workaround: copy the content of the file that you want to open in the formula
editor.
On Japanese, Fix Pack 5 for Integration Server does not work.
Do not install this fix pack on a computer on which Integration Server is
installed, or OIS might become corrupted.
Application Manager, running on Windows XP, shuts down when you switch windows while opening an outline. 376683 (78450)
When running on Windows XP, Application Manager shuts down if you switch to another window such as notepad during the process of opening an outline.
On Windows, for some non-English languages, you might encounter file
permission problem on the client when logged on as a power user.
This problem can occur when the client target language does not match the language of the operating system. If you are using the client while logged on to Windows as a power user, might encounter file a permission problem in which some of the installed .DLL files have not been granted "execute" permissions. The client will work normally when you are logged on as an Administrator.
For example, on an English system, if you are logged onto Windows XP system as administrator, you can enter successfully the following command:
cacls %ARBORPATH% /T /E /G Everyone:F
Where %ARBORPATH% is the path where you installed DB2 OLAP Server, and Everyone is the group name for all users on your system. This name may vary depending upon the language and type of operating system. In this example, the DB2 OLAP Server client is installed in the default location.
However, if you are logged onto a German system as a power user, and you use "Jeder" instead of "Everyone" in the following command, a file permissions error is generated:
cacls "c:\ibm\db2olap" /T /E /G Jeder:F
If you are logged on as an administrator, the command runs successfully. You can get more information by running the CACLS at a Windows command prompt.
Empty .odbc.ini File After Running inst-sql.sh (75469)
On Linux
Advanced Server 2.1, an empty .odbc.ini file is created after
running the inst-sql.sh file. The inst-sql.sh file
should copy the odbc.ini file from
$ARBORPATH/odbc/merant41/odbc.ini to
$ARBORPATH/bin/.odbc.ini and link to $HOME/.odbc.ini.
Although the original odbc.ini file contains DSN entries, the
.odbc.ini file is empty. A workaround is to copy the file manually.
After copying, execute the following command:dos2unix
.odbc.ini
Shared Members and Partitions. 50520(55620)
Adding both shared and
non-shared members to a parent in the outline of a partitioned database may
cause the application to crash and may cause an access violation
error.
Workaround: Change the order in which the shared and
non-shared children are listed in the outline under the parent. The non-shared
children should be listed first and the shared children should be listed at the
end of the outline
Calculation Runs Out of Physical Memory. 278593(66565)
Due to an
interaction between Direct I/O and cache memory locking on Windows, physical
memory may run out when performing certain calculations. This problem occurs
with applications that have both Direct I/O and cache memory locking enabled.
Problem with Time Balance Calculations. 298143(71950)
When
there is a Dynamic Calc tag on dense members, or when the Time dimensions is
sparse, there may be problems with Time Balance calculations. The Dynamic Calc
order dictates that Time Balance calculation happens before Dense Dynamic Calc
aggregation. Therefore, when Time Balance is calculated, the top-level Dynamic
Calc member in a Dense dimension is #Missing. When the Dense Dynamic Calc
happens, it has to skip Time Balance member so as not to replace possible Time
Balance values with aggregated values. The workaround is to remove the Dynamic
Calc tag on dense members or change the Time dimension to Dense.
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 DB2 OLAP Integration Server 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.
Fact tables cannot be created automatically.
The workaround is to create the fact table manually. (IBM 7966)
Help dialog disappears after clicking the links for "Create a new
drill-through report.." and "Copy an existing drill-through report.."
(7973)
Workaround: go back to "Template Drill-Through" panel and click
the Help button to get the help dialog.
Do not install this fix pack on a computer on which Integration Server is installed, or OIS might become corrupted.
There are no known issues with Fix Pack 4 for DB2 OLAP Integration Server.
OTHER LIMITATIONS
HYBRID ANALYSIS LIMITATIONS:
Licensed Material - Program Property of IBM
© Copyright IBM Corporation 1998, 2005. 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-2005 Hyperion Solutions Corporation. All rights
reserved. Hyperion is a registered trademark and Hyperion Solutions
is a trademark of Hyperion Solutions Corporation.
Microsoft, Windows, and the Windows
logo are trademarks of Microsoft Corporation in the United States, other
countries, or both.