FixPak Date: April 2003
This FixPak includes fixes for DB2 OLAP Server V8.1 and its features at the following service levels:
FixPak 2 is the equivalent of Release 6.5.3 of the Hyperion products.
Hyperion maintenance levels are cumulative; each level contains new fixes
and all the fixes for the previous maintenance levels.
To stop Windows NT and Windows 2000 services:
echo $SHELL
If the returned value is: /usr/bin/csh, change your shell to Korn Shell with this command:
setenv SHELL /usr/bin/ksh
The Korn Shell persists as your shell until you logout 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 Runtime Client on Solaris and then installed FixPak 1, the libesssql.so.1 library file might be corrupted. Before installing FixPak 2, remove the libesssql.so.1 library file from the $ARBORPATH/bin directory, and all links to that file. FixPak 2 installs the correct library
If you use Lotus 1-2-3 but do not use the English version of DB2 OLAP Server, contact IBM Service before installing FixPak 1 or 2. For some languages, numbers in Lotus 1-2-3 are formatted incorrectly after installing FixPak 1 or 2.
In FixPak 1 and later, DB2 OLAP Integration Server has the following changes to its supported software:
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp02/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/fp02/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:
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:
Here is your starting point for downloading and installing FixPak 1 for Enterprise Services (Essbase XTD Deployment Services 6.5.1 ):
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/fp01/eas/
Important installation tips:
FixPak 2 also fixes the defects listed in Problems fixed and adds some documentation in Documentation updates. DB2 OLAP Server Enterprise Services is not updated in FixPak 2.
FixPak 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.
FixPak 2 adds the following new features to DB2 OLAP Integration Server 8.1:
To see what's new in FixPak 2 for Administration Services and to start the FixPak 2 installation, see Installing the FixPak for DB2 OLAP Server Administration Services.
The following links work only after you finish installing FixPak 1 or later, or if you are reading this from the DB2 OLAP Server Web site. These links do not work while you are running the installation program. The documents displayed by these links refer to the OLAP products by their Hyperion names, not by their IBM names.
To read the Administration Services documentation and begin the installation, see Installing the FixPak for DB2 OLAP Server Administration Services.
To read the Enterprise Services documentation and begin the installation, see Installing the FixPak for DB2 OLAP Server Enterprise Services.
User-Defined Tables
In DB2 OLAP Integration Server 8.1 FixPak 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 FixPak 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.
FixPak 1 and later FixPaks 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 FixPak 1 and later greatly enhances the support for recursive hierarchies by enabling you to perform the following tasks:
DB2 OLAP Integration Server 8.1 FixPak 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 FixPak 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 FixPak 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 FixPak 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 FixPak 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 FixPak 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 FixPak 1, you can migrate automatically from all earlier versions.
Rapid Display of Tables
DB2 OLAP Integration Server 8.1 FixPak 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; FixPak 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 FixPak 1 and later adds several data types to its list of supported RDBMS data types on DB2 and SQL Server. For these databases, FixPak 1 supports the following additional data types:
DB2 OLAP Integration Server 8.1 FixPak 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 FixPak 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 FixPak 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.
Using unattended installation (silent install)
The unattended install or silent install feature is available for both UNIX and Windows. The unattended install feature enables you to reinstall DB2 OLAP Server on the same workstation or other workstations using the same install options as your original installation . You can use a silent installation so your users do not have to type responses to the prompts of the installation program.
When you install DB2 OLAP Server, the installation options that you select are saved in a response file. The response file is used by the installation program during a silent install.
To perform an unattended install on Windows:
1. Record your responses to the installation program prompts. To record your responses, locate your OLAP installation setup.exe program and run the following command from a DOS prompt:
setup.exe -r
This records your responses to the installation prompts into a file called setup.iss , which is stored in the main Windows directory. On Windows XP and Windows 98, the file is stored in C:\Windows. On Windows NT and Windows 2000, the file is stored in c:\WINNT .
2. Copy the setup.iss file into a temporary directory on the computer on which you are installing DB2 OLAP Server.
Your user ID and password are stored unencrypted in the setup.iss file. The contents of the file are scrambled, but the algorithm is not secure.. You should erase the file after you have installed DB2 OLAP Server to avoid a security exposure.
If you use silent install for both DB2 OLAP Server and for OLAP Miner, ensure you copy the setup.iss file for OLAP Miner into a different temporary directory, or the file will overwrite the one for DB2 OLAP Server.
3. To run the silent installation, run the setup.exe command using the s parameter (for silent installation) and the f1 parameter (which indicates the location of the setup.iss file). For example, if you stored the setup.iss file in the C:\TEMP directory, enter the following command:
setup.exe -s -f1C:\TEMP \setup.iss
4. When the installation program finishes, check the messages in the log. The log file is in the same directory as setup.iss. Also, check c:\DB2LOG\Olap.log for detailed information about the unattended installation.
To create a log file for your silent install, run the following command.
setup.exe -s -f1C:\TEMP \setup.iss -f2 c:\yourlocation\nameof yourlog.log
To perform an unattended install on UNIX:
1. The Install automatically generates a response file by invoking the UNIX install program and performing the first installation. The installation information is stored in the olapinst.rsp response file in $ARBORPATH/install.
2. From a command line on the target system, type the following command to run the unattended install:
setup.sh <reponsefile_directory>/<reponse_file>
where <reponsefile_directory> is the directory where the response file is located, and <reponse_file> is the name of the response file.
4. When the installation program finishes, check the messages in the log. The default location of the log file is: install/olapinst.log
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:
New MAXLOGINS limit
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.
The following updates to the DB2 OLAP Server documentation are new in FixPak 1:
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 FixPak installation to add components
After you install FixPak 1 or later on UNIX, you must use the FixPak installation program to add any additional components to your UNIX system. If you run the GA-level installation program after installing FixPak 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:
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 problems that are fixed in DB2 OLAP Server Administration Services are listed in the documentation, which you can access from Installing the FixPak for DB2 OLAP Server Administration Services.
FixPak 2 does not update DB2 OLAP Server Enterprise Services.
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 FixPak 1 or higher. If you attempt a Find operation against a
Version 8.1 server earlier than FixPak 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 chidren 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 FixPak 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
Spreadheet 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.
FixPak 1 fixes the following problems in DB2 OLAP Server:
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 FixPak 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 FixPak 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. FixPak 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 FixPak 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 FixPak
8 and later, and in V8.1, than in V7.1 FixPak 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.
FixPak 2 fixes the following problems in DB2 OLAP Integration Server:
FixPak 1 fixes the following problems in DB2 OLAP Integration Server:
Remote network file systems not supported on Windows or UNIX
DB2 OLAP Server does not support the use of network file systems such as NFS3
to access disk storage on remote servers.
If you set a remote disk as volume for an OLAP database, errors might result.
Clients installed from network must be reinstalled after adding a new spreadsheet program
If you installed the clients from a network image and then install a spreadsheet program, the spreadsheet program is not enabled with the Spreadsheet Add-in for DB2 OLAP Server. To enable the Spreadsheet Add-in, uninstall and then reinstall the network clients.
Killing Essbase processes not supported on UNIX
Executing a "kill" command of any kind in UNIX against any type of Essbase process is unsupported. Issuing a kill command, especially on a database that is calculating, has a high probability of corrupting the database.
If all supported methods of shutting down an Essbase process have been exhausted, and a kill must be executed, heed the following precautions to reduce the amount of damage to the database:
Hybrid Analysis known issues
Hybrid Analysis supports only DB2 using native drivers or Meant drivers, Oracle ODBC using Meant drivers or native drivers, and SQL Server. See the Installation Guide for details about platform release levels and drivers supported.
If your system has Oracle ODBC drivers and you plan to use Hybrid Analysis, you must upgrade to Oracle 8.1.6 or later (30531). Enabling Hybrid Analysis while using Oracle ODBC drivers earlier than 8.1.6 causes the following conditions:
MaxL known issues
V8.1 of the MaxL Perl Module (essbase.pm) works with V8.1 of the DB2 OLAP Server. It is not compatible with previous releases of DB2 OLAP Server.
Although the limit for stored Essbase calculations is 64 KB, calculation scripts created in MaxL that have multi-byte characters cannot exceed 40 KB.
Database notes created using MaxL appear stripped of newline-character formatting when viewed in the Spreadsheet Add-in.
Memory and system information on Microsoft
Because of a Microsoft system limitation, if you are running DB2 OLAP Server on a Microsoft platform with more than 4 GB memory, the information about memory and disk swapping in the System Information tab of the Server Information dialog box may be incorrect.
$ISHOME/odbc/merant40
Please see the Installation Guide for information on updating
environment variables in UNIX. (54870)
The instructions for using the Delete button in the "Drill-Through Reports Dialog Box" online help topic are incomplete. The online help states that the Delete button is used to delete drill-through reports but fails to state that the button is also used to remove intersection levels and report columns. (58284)
| Problem
Number |
Description | |
| IBM6154 | On Windows, if you are logged on with a user ID that does not have administrator privileges, and you try to run the Modify License utility, an error occurs. Ask your server administrator to run the utility for you. Additionally, if you run the Spreadsheet Add-in with a user ID that does not have administrator privileges, you might see a message such as, "Error loading USE or USELSX module lsx123.dll". To prevent this message from occurring, manually remove the Spreadsheet Add-in from the spreadsheet program for this user ID, using the spreadsheet interface. | |
| IBM6193 | On Windows 98, if you run silent install, you might encounter this error: "Sharing Violation Reading drive C... Abort, Retry, Fail." If you type Fail, the installation completes successfully. | |
| 16412 | In Excel, in Query Designer, the server location radio button may not be active in the "Hyperion Essbase Query Designer Save As Query" window when you try to save a query. This occurs because a selected cell is in Edit mode. If you are typing in a cell, Essbase menu items do not function, although they appear enabled, until you get out of Edit mode. | |
| 17023 | If a member name contains the ampersand (&), even if it is surrounded with quotation marks, and if the member name is in a calculation script, the script may fail validation if the user has Application Designer permission. DB2 OLAP Server incorrectly interprets the ampersand as the signal for a substitution variable. If you run the script without validation, it performs the calculation correctly. Users with supervisor privilege do not receive this validation error. | |
| 17253 | DB2 OLAP Server does not support discontinuous selection in Lotus, although it does in Excel. | |
| 17267 | At the end of a calculation started in Lotus, a dialog box appears with a message that the calculation is complete. Clicking on the dialog box does not close it. Press Esc/Cancel from the keyboard to close the dialog box. | |
| 17927 | DB2 OLAP Server does not warn you if you request that export results be written to a file that already exists. Essbase overwrites the existing file. | |
| 17957 | If you create a dimension build rule that uses "Create Using Text" on the last column, and if the last true field in the input file is an "Alias" column that has some blank records, the text generated by the "Create Using Text" feature will not be placed into the last column, but will be placed in any record where the "Alias" column is blank. The rule, which passes validation, will fail during the build. To correct, delimit the blank fields. | |
| 18015 | Leaving the Spreadsheet Add-in idle for long periods of time may cause extra "Please Log In" messages, because the user may have been logged out due to inactivity. Click OK until the message stops appearing. | |
| 18041 | DB2 OLAP Server may not be able to open a file if the directory location contains a space. This is true for all files such as load files, rules files, calculation scripts, etc. Consider moving the file so that there are no spaces in the directory path. | |
| 18046 | When logged in with database designer privilege, the entire list of users is displayed in Security > Database, even though only the list of users that the database designer has privileges to modify should appear. Attempts to modify users for whom database designer should not have privileges will not be successful. | |
| 18342 | If you use Set Member Filter in EQD, any MBCS values may display as broken characters. Type the values into Notepad, and then copy and paste them over the broken characters. | |
| 19288 | Using Dynamic Time Series (DTS) members on a partitioned database may
cause a server crash if these conditions are true:
|
|
| 19522 | When compiling client API programs on NT, with MS VC ++ version 6.0
and higher, you may experience API program crashes if you have used a constant
string assignment to a CHAR pointer, such as:
char * name = "myname";Workaround: Do not use a constant string assignment to a CHAR pointer, or use only ESSBASE data types. |
|
| 19632 | Valid calculation scripts with a FIX command and nested parentheses within the FIX command may not validate in the Calc Script Editor of the Application Manager and may report spurious errors. The same script will run without problems on the server. | |
| 20203, 30329 | If you start DB2 OLAP Server as a service on NT, you can
ignore this message, it is informational only:
The description for Event ID ( 0 ) in Source ( EssbaseService ) cannot be found. It contains the following insertion string(s): EssbaseService error: 0, Starting Essbase Service.... |
|
| 20775 | If you use the Query Designer to change members in a spreadsheet,
then select a dimension and choose Essbase > Cascade, and then in
the Destination Options tab, select the option "One Workbook, Separate
Sheets," you may receive the Microsoft Visual C++ Runtime Library error:
Runtime Error! C:\Program Files\Microsoft Office\Office\Excel.exe....abnormal program termination! error. |
|
| 22233, 23800, 23344 | Running too many concurrent reports may overwhelm product or operating system resources, especially against partitioned databases. If this occurs, reduce the number of such reports running concurrently. | |
| 22999 | If, during outline revision, you delete a member with a
particular alias name, and then create a new member with the same alias
name, the alias will fail to register and DB2 OLAP Server creates the new
member without an alias.
Workaround: Either delete the alias from the Outline Editor and save, or use a different alias name when revising. |
|
| 23086 | Due to a Microsoft bug, you may not be able to display the Spreadsheet Add-in in IE 5.0 if you are running on operating system NT4.0. If you try to open an .xls file from IE 5.0 on NT4.0, the spreadsheet may open in a separate window. | |
| 23374 | The application log, when displayed via Application Manager, may incorrectly fail to show some log entries for the current day because it evaluates the time using GMT. To view missing log entries, select "All Dates." | |
| 23974 | Trying to associate an attribute with an implied shared member causes the association to be ignored, and Essbase writes a message to the application log. An implied shared member is a member with only one child. | |
| 24044 | For EssOtlQueryMembers on UNIX, the currency conversion
type returned is incorrect.
Workaround: Use EssOtlFindMember instead. |
|
| 24350 | When the installation program for SQL Interface asks you to specify a driver, if you specify Merant, you won't be able to use DB2 Native drivers, and if you specify DB2 Native drivers, you won't be able to use Merant drivers. | |
| 24351 | Some characters, such as those using umlaut or accent marks, cannot be typed in ESSCMD interactive mode. | |
| 25659 | If you use a partition definition where one or more member functions in the definition resolve to an empty set, then DB2 OLAP Server may write more than one message in the application log when you validate the partition. Each message has the same information about a member function resolving to an empty set. All but the first message in the sequence can be ignored. | |
| 26028 | If you enable parallel calculation (CALCPARALLEL or SET
CALCPARALLEL greater than the default 0) on a database that is part of
a transparent partition, increase the value of SERVERTHREADS for each source
database that is part of the transparent partition, using these rules:
|
|
| 27139 | If you use Hybrid Analysis with source data in Oracle,
in either of these situations, you must use Oracle version 8.1.7 or higher:
<ROW (Market) [HA-enabled dimension] <DESCENDANTS (Market) |
|
| 27171 | If you use direct I/O, and have set DLTHREADSWRITE to a value of 16 or greater, Essbase may crash during a parallel data load. If you encounter this error, reduce the number of block write threads by lowering the value of DLTHREADSWRITE to 15 or less, then restarting Essbase. | |
| 29248 | When running DB2 OLAP Server V7.1 FixPak 5 or V8.1 on Windows 2000 or Windows NT systems, using the EsbSetActive Visual Basic API in code samples in Microsoft Access 2000 may crash Microsoft Access. | |
| 31691 | You must save a rules file and the data file it uses to the same ARBORPATH/App/database_name directory as the database whose outline you are working with. | |
| 33810 | On AIX, due to limitations of the operating system, the information displayed in the System Info tab and License Info tab (or equivalent if retrieved outside Application Manager) may be unavailable. | |
| 43247 | Visual Basic API does not support VB.net at this time. | |
| 43406 | In DB2 OLAP Server V8.1, Application Manager is unable to modify an outline or load data if the text file is located in a different application database directory on the same server. | |
| 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. |
|
| 55837 | After importing a large number of LROs (for example, over
100 LROs) using MaxL or Administration Services, restructuring the outline
may cause the database to crash.
Workaround: Increase the index cache size from the default value of 10240 KB using the alter database MaxL statement, the Index Cache setting in the Database Properties window (Caches tab) in Administration Services, or the Index Cache setting in the Database Settings dialog box (Storage tab) in Application Manager. |
|
| 55926 | Before using the MaxL alter database statement to
get invalid block header information for a given database, be sure that
the server is not performing other operations, such as calculations or
dataloads; otherwise, an exception error may occur. Before running the
MaxL statement to get invalid block header information, the database administrator
must forcibly log off all users and disable all logins to ensure that no
other users or processes are using the server.
The complete MaxL statement to get invalid block header information is alter database DBS-NAME validate data to local logfile 'FILE-NAME';. |
Licensed
Material - Program Property of IBM
(c)
Copyright IBM Corp. 1998, 2003. All Right Reserved.
US
Government Users Restricted Rights - Use, duplication or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.
IBM,
DB2, and DB2 OLAP Server are trademarks of International Business Machines
Corporation in the United States, other countries, or both.
Portions
(c) 1991-2003 Hyperion Solutions Corporation. All rights reserved.
Hyperion is a registered trademark and Hyperion Solutions is a trademark
of Hyperion Solutions Corporation.
Portions
(c) Blue Sky Corporation. All rights reserved.