IBM DB2 OLAP Server for iSeries, Version 8.1
Fix Pack 3.5

Release Notes 

December 2004

Welcome to Fix Pack 3.5 for IBM® DB2® OLAP Server™ for iSeries™, Version 8.1.  This document is your starting point for downloading and installing the fix pack.  

Contents

Introduction for Fix Pack 3.5

Fix Pack 3.5 updates the Warehouse Manager and OLAP server components to run on OS/400 V5R3, and fixes some server defects.  The clients are not updated.

If you have not yet installed Fix Pack 3 client updates, you need to do so after installing Fix Pack 3.5 server updates.  Please read the following section.

Introduction for Fix Pack 3

If you are installing client products from a DB2 OLAP Server fix pack, you must install server products to the same fix pack level. For example, if you install a Fix Pack 3 client update, you must also install the Fix Pack 3 or Fix Pack 3.5 server. Using older server versions with newer client versions is not recommended and is not supported.

If you use STRATEGY® Analyzer™, do not install this fix pack until you read the procedures for migrating STRATEGY Analyzer. Go to the fix packs Web site for DB2 OLAP Server for iSeries to find the migration procedures:

http://www.ibm.com/software/data/db2/db2olap/fixpacks.html

If you use Enterprise Reporting, you must upgrade to STRATEGY 4.5 patch 12 or later. 

If you plan to use lightweight directory access protocol (LDAP), read "Essbase External Authentication via LDAP."

All DB2 OLAP Server fix packs are cumulative. You do not need to install previous fix packs. 

DB2 OLAP Server Miner™ (OLAP Miner) is not included in the DB2 OLAP Server for iSeries client package. You can install OLAP Miner from the DB2 OLAP Server fix packs Web site. 

Service levels

This fix pack updates the server components only:

The following components are not updated by this fix pack and remain at the Fix Pack 3 level:

Verify that you have the correct versions of Java and other software. See Before you install for more information.

Before you install

Before updating your servers the Fix Pack 3.5 level, be sure to perform a save and restore of your existing environment. Then, check that your server computers meet the following requirements:

Warehouse Manager server requirements

Additionally, IBM strongly recommends that you install all the latest cumulative PTFs, database group PTFs, and Java group PTFs.

S36 files are no longer supported. You must use IBM® DB2® Universal Database™ for iSeries™ (DB2 UDB iSeries) for externally described files.

OLAP server requirements

If you are upgrading your servers from a level prior to Fix Pack 3, you must install over version 8.1:

Additionally, IBM strongly recommends that you install all the latest cumulative PTFs, database group PTFs, and Java group PTFs.  For example,  PTFs SI16219 and SI15407 are required for the OLAP server.

Builder client requirements

Fix Pack 3.5 does not update the clients.  However, if you are updating your server to Fix Pack 3.5, your clients must be at the Fix Pack 3 level.  If you will be installing the Fix Pack 3 clients, check that your client computers meet the following requirements:

Back to the top

Fix pack installation

You need to install one file on your server computer to install Fix Pack 3.5.  If you have not yet installed the clients updated in Fix Pack 3, then you need to install one file on each client computer.  

Server components

This section describes how to install the fix pack for both the STRATEGY Warehouse Manager and DB2 OLAP Server.

Getting the fix pack

This fix pack must be applied to DB2 OLAP Server for iSeries V8.1 (ShowCase STRATEGY 4.50, patch 3) or later. See the instructions below for downloading and applying the fix pack.

Prerequisites for applying the fix pack

Installing the fix pack

This fix pack will update both the OLAP server component and the Warehouse Manager server component.  Before you install the patch, read and follow the prerequisites listed previously.

  1. iSeries: Start with a fresh iSeries session. Create a save file in QGPL using the following command:
      CRTSAVF QGPL/UPDTSAVF
  2. PC: Use FTP to transfer db2ptch.svf to the AS/400:
      C:\>FTP<iSeries IP Address>
      User (system:(none)): <userid>
      331 Enter password.

      Password: <password>
      230 <userid> logged on.
      ftp> binary
      ftp> put c:...\db2ptch.svf QGPL/UPDTSAVF
      ftp> quit
      C:\>

  3. Designate a temporary working library to restore the contents of this save file into. We suggest that you create a temporary library for this purpose. For the remainder of these instructions, this library if referred to as <templib>.
  4. On the iSeries, restore the save file by using the following command:
      RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(QGPL/UPDTSAVF) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(<templib>)
  5. Add templib to your library list with the following command:
              ADDLIBLE <templib>
  6. To start the full installation of both servers, issue the following command and respond to the installation prompts:
          CALL UPDDB2OLAP
  7. During the installation, you are prompted to schedule the ShowCase jar file. Enter a time and date for the compile process. Because this will take as long as it did for the installation, it is advised that this be done during off hours. Until you recompile, you will experience performance issues.
  8. The fix pack process is now complete.
  9. Restart your ShowCase Server with the command
          <SCSERVER>/STRSCSVR
    where <SCSERVER> is your ShowCase library.
  10. Restart your OLAP server with the following command:
               <Essbase Installation Library>/STRESSSVR
After you compile the jar files, you should end (ENDSCSVR) and restart (STRSCSVR) the ShowCase Server.

If you have not yet installed the clients for Fix Pack 3, install them now.

Back to the top

OLAP and Builder clients

Fix pack 3.5 does not update the clients.  If you have installed the client updates from Fix Pack 3, you can skip this section.

Whenever you install client products from a DB2 OLAP Server fix pack, you must install server products to the same fix pack level. For example, if you install a Fix Pack 3 client, you must also install the Fix Pack 3 or Fix Pack 3.5 server. Using older server versions with newer client versions is not recommended and is not supported.

Even if you have only one of the problems fixed in one of the fix packs, you need to perform a full fix pack installation.

Installation error when updating components or updating spreadsheet add-ins

You might receive the following error during the 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. 

Network installation--the OLAP server does not load when Lotus 1-2-3 is started

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. 

Before installing this fix pack, make sure that your system has enough memory.  For complete installation instructions, see the Installation Guide for iSeries.

Getting the fix pack

To apply this fix pack, you need to download and install one file that contains the OLAP client components.

Download the wincd.zip file to the Windows machine on which you have installed the clients.  If you're installing from a CD, copy the wincd.zip file from the CD to a temporary directory.

Installing the Windows client fix pack

Be sure to read the information in Before you install before you install the DB2 OLAP Server client.

  1. Extract the files from the wincd.zip file.
  2. Run setup.exe to start the installation program.
  3. After the files are extracted, you can delete the zipped file.

Back to the top

 

Starting DB2 OLAP Integration Server 

Use the following instructions to configure and begin using DB2 OLAP Integration Server (OIS). For complete instructions, see the Installation Guide for iSeries.

  1. Create a new job description (or modify an existing one) to include the STRATEGY Essbase installation library and any other libraries you want to use with OIS. Use the following command, where ESSBASE is the STRATEGY Essbase installation library, and DATALIB contains user data files.

CRTJOBD JOBD(QGPL/EISJOBD) INLLIBL(ESSBASE QGPL DATALIB)

OIS will have access to only the libraries specified in the INLLIBL parameter. You can add only libraries that exist on the system. Otherwise, the library list will not be replaced and may cause errors.

  1. Create a new user profile (or modify an existing one) that will use this job description during OIS startup. This user profile must have the authority required to start the server as documented in Installation Guide for iSeries. In the following command, EISADMIN is the new user profile and EISPASSWORD is the new password:

CRTUSRPRF USRPRF(EISADMIN) PASSWORD(EISPASSWORD) USRCLS(*SECOFR) JOBD(QGPL/EISJOBD)

  1. Sign on to the iSeries with the new profile, and start the Essbase Integration Services Server:

STRESSSVR SERVER(*INTEGRATION)

  1. From a client PC, open the Essbase Integration Services console and, using the following guidelines, create the OLAP metadata catalog:

  1. After the catalog is created, you can connect to the OIS server. At the login screen, you must provide information similar to what you provided in step 4. You can also provide Essbase login information and connect to the Essbase OLAP server.

You are now ready to create your model and metaoutline.

  1. You can create a sample application to see how OIS works. You must create an iSeries profile called TBC before you can create the sample application. Then, to create the sample application, from the Tools menu, select Create Sample. Use the following guidelines:

Back to the top

Starting Hybrid Analysis

Hybrid Analysis must be set up using DB2 OLAP Integration Server (OIS). 

Enabling Hybrid Analysis on the server

  1. Stop the OLAP server by using the instructions in the Installation Guide for iSeries.
  2. Add the line HAENABLE TRUE to the OLAP server essbase.cfg file. For instructions about how to modify this file, see the Administrator's Guide for OLAP on  iSeries.
  3. Restart the OLAP server to implement your changes.

Enabling Hybrid Analysis for the spreadsheet add-in

  1. In the spreadsheet, select Essbase --> Options.
  2. In the Essbase Options window, select the Zoom tab.
  3. Select Enable Hybrid Analysis. This selections enables data retrieval from the Hybrid Analysis source.
  4. Click OK to close the Essbase Options window.

Back to the top

What's new in this Fix Pack

Fix Pack 3.5 does not add any new features, but does fix defects listed in Problems fixed.

What's new in Fix Pack 3 DB2 OLAP Server 

For information on the new features in Fix Pack 3, see the following online documents.

The information in these documents supplements and in some instances changes the information in the DB2 OLAP Server 8.1 documentation that was originally installed.

What's new in DB2 OLAP Server (Essbase XTD Analytic Services 6.5.4.2 build 003)?

This fix pack adds the following new features to DB2 OLAP Server 8.1:

MaxL Changes

Undo Forced Password Change

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.'
Display user has a new column

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.

Username, servername, and password cannot include spaces at the beginning or at the end.

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'.

Documentation update for no_access

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.

Setting column size in essmsh

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.

Setting the 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.

API Changes 

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.

Change in Display of Query Results For Members With Formulas

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 %

New Configuration Settings

TARGETTIMESERIESOPT

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

CRASHDUMP TRUE/FALSE  

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

What's new in Fix Pack 3 for DB2 OLAP Integration Server (Essbase Integration Services 6.5.4.1)

The following section describes the changes is DB2 OLAP Integration Server 8.1 Fix Pack 3 (Essbase Integration Services 6.5.1).

User-defined tables

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.

Enhanced Support for Recursive Hierarchies

DB2 OLAP Integration Server 8.1 Fix Pack 3 greatly enhances the support for recursive hierarchies by enabling you to perform the following tasks:

Replace Zeroes with #MISSING Option

You have the option of substituting zero values with the string #MISSING during data loads. This action provides several immediate benefits:

During a data load, loading zero values creates blocks in the database. In some scenarios, this can cause unneeded input blocks and hamper performance. This fix pack addresses these problems with a search-and-replace option to change zero values to the string #MISSING during the load process.

Protection of Changes During Disconnects

New function 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

This fix pack 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.

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:

Automatic Migration to Release Fix Pack 1

When you create or update an OLAP Metadata Catalog for the first time in 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

Up to 50,000 tables are displayed 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. This fix pack functionality 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.

Database Reset Prior to Member Loads

You have 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 and 1.5 empty the database outline, thus eliminating the necessity of opening it before the load can be started.

Cancel Button in View Sample

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.

This fix pack adds the following new features to DB2 OLAP Integration Server 8.1:

Cancel button in view operations

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.

Resizable dialog boxes

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:

Improved compatibility on nondefault ports

DB2 OLAP Integration Server addresses two limitations that in previous releases affected the ability to run DB2 OLAP Server applications on nondefault ports:

Support for multiple alias tables

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.

Find and Replace Null Values

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. 

Selection of Dynamic Time Series Member Name

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.

Improvements in Error Reporting

DB2 OLAP Integration Server has several significant improvements in error reporting on data loads:

Automatic Migration to Version 8.1

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 DB2 OLAP Integration Server, Version 8.1, you can migrate automatically from DB2 OLAP Server, Version 8.1.

Back to the top

Documentation updates

Fix Pack 3.5 does not update the documentation.

Documentation updates for Fix Pack 3

Hybrid Analysis is not supported with the Member Selection feature

Hybrid Analysis is not supported with the Member Selection feature. In other words, you will not be able to select Hybrid Analysis members from the Member Selection dialog box.

If you have multiple levels of Hybrid Analysis members in your outline, a zoom out operation on the bottom level Hybrid Analysis member takes you directly to the Essbase parent member, thus bypassing all other Hybrid Analysis levels.

Correction for the ESS_MBRINFO_T read fHasRelDesc Outline API function

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

The word 'descendants' is incorrect. Instead, the description should say the member has relational children.

ESS_BOOL_T

fHasRelDesc

The member has relational children

Updates for DB2 OLAP Integration Server documentation

On page 19, the Essbase Integration Services Installation Guide incorrectly refers to the Essbase Integration Services Migration Guide. The reference should be to Chapter 7, "Migration" within the Installation Guide.

In the Essbase Integration Services online help, in the Dimension Properties, Member Properties, Attribute Dimension Properties, and Attribute Member Properties dialog box topics, the tab "hot spots" may occasionally not function. If so, use the index to locate the appropriate dialog box.

Documentation updates for Fix Pack 1 and Fix Pack 1.5

Updated administration information available

The STRATEGY Essbase 6.51 Administrator's Guide is included with this fix pack for your  reference. 

Using unattended installation (silent installation)

The instructions for silent installation are mislabeled in the Installation Guide as applying only to DB2 OLAP Server Miner.  You can use the instructions in "Installing DB2 OLAP Server Miner on Windows" to do a silent installation for DB2 OLAP Server on Windows and OLAP Miner.

If you use silent installation for both DB2 OLAP Server and for OLAP Miner, ensure that 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.

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 under the following circumstances, you must configure the spreadsheet program manually:

To configure the spreadsheet program manually, follow these steps:

  1. Install the latest Fix Pack on your Windows computer.
  2. Restart the computer.
  3. Select Start --> IBM DB2 OLAP Server 8.1 --> Modify Component or License Information.
  4. Click Modify.
  5. Select Configure Spreadsheet Add-in.
  6. Follow the prompts.

Tip for using 'Aggregate Missing Values'

If your database allows or requires 'Aggregate Missing Values' setting set to YES, then you might 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 might 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.

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.

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 might 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

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 If
The 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.

ESTIMATEFULLDBSIZE

The ESTIMATEFULLDBSIZE command provides an estimate of the number of blocks a database will create after full calculation (CALC ALL), based on the number of blocks that exist before calculation. You can use this estimate to help you plan disk space requirements.

Outlines that contain sparse formulas of any type or topdown formulas are not supported. Results of the estimation on such databases might 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)

Back to the top

Problems fixed

This section lists the defects that were fixed in each fix pack.

Builder server problems fixed in Fix Pack 3.5

From patch  6.50.100:

MCH3601: pointer not set error when saving lookup or data model to server.(F17976)

*PUBLIC not being honored for JDE World BU (business unit) security when user has an attached group profile.(F17854)

Can not set up a non-db2 data source mapping on a server installed on a V5R3 system.(F17783)

Customer is reporting that SCSERVER crashed. MCH6902.(F17581)

Restoring from a 4.5 save file into a 6.50.090 server returns inappropriate error message.(F17556)

WHMGR.EXE errors in Warehouse Manager when you attempt to add a Data Administrator.(F17480)

Clean catalogs not working for ALL catalogs.(F17469)

Not seeing the correct column headings for a custom JDE file (data view) created through ShowCase.(F17334)

[ShowCase Corp][ShowCase ODBC Driver][OS/400] 52004: "POWER" in libname type FILE not found.(F17087)

TCP server won't start after installing 6.5 or 6.51 servers on V5R3.(F16727)

UPDSMGCONT Utility missing in 6.5.(F16501)

Need a utility to save all IFS files that users customize for ER.(F16267)

From patch 6.50.090:

Scserver is crashing. There are messages MCH6902 in the server joblog.(F17581)

Cannot autostart ShowCase after IPL (Only happens on a DBCS system).(F17194)

Big Switch to not limit *ALLOBJ security does not work when query is run dynamically.(F16833)

Error running batch query after changing group profiles of user, "group profile xxx not found".(F16823)

Cannot add a quoted long table name when running in a French Windows2000 operating system.(F16812)

If a DATE UDF is used in a GROUP BY clause and the format is not enclosed in single quotes, the SQL statement fails to execute with a "Column not found in table" exception.(F16798)

Unable to change passwords using 4.x against the 6.5 server. Value for new password not allowed at password level 0.(F16773)

Incorrect error message is returned when restoring ER and leaving the "Restore ER Scheduled Queries" field empty on the RSTSRVRINF command.(F16240)

RSTSRVRINF goes into infinite loop when specifying *YES to restore scheduled objs, and there are none to restore.(F16111)

Running a RSTSRVRINF command from a job using CCSID 6535 could cause scheduled information to not be restored, this issue has been addressed.(F16091)

From patch 6.50.080:

Warehouse Builder;WHS BLD Batch set in error:(1030213) Cannot create local file: /tmp/D40629111000001A30001.SCE.(F16480)

If a DATE UDF is used in a GROUP BY clause and the format is not enclosed in single quotes, the SQL statement fails to execute with a "Column not found in table" exception. (F16798)

Cannot add tables with long names.(F16657)

Dynamic report failing with com.showcasecorp.jdbc.SCSQLException: Column COUNCS or expression specified in SELECT list not valid.(F16383)

JDE OneWorld; The code was changed to support long file names in the single table cache. (F16181)

Not authorized to clear batch destination results file.(F15771)

User unable to run dynamic query or RDO. User is able to run fat client Queries.(F14998)

Multi member query: ERROR = java.sql.DataTruncation: Data truncation running a dynamic report in 6.5(F14791)

From patch 6.50.070:

Table not found error when running join with JDE application security disabled.(F15722)

If you apply a patch when Orion is not installed:A shell comes up, and you get the following error:6.50.060 host patch error: java.io.FileNotFoundException: No such path or directory. /SCSRVTST/PatchSPSSWeb.jar. If you press enter or F3, the patch apply will continue, and complete normally.(F15711)

If the user chooses to type a table name in the Query tables dialog when creating a query, the server retrieves all table names from the chosen library and stores them in a cache instead of just retrieving the information for the single table specified.(F15484)

ERROR = java.lang.NullPointerException when running a JDE dynamic report.(F15448)

Application security not being honored when opening queries where table has been secured.(F15377)

From patch 6.50.060:

Resource setting in WMC to disallow save to the server does not work in 6.5.(F15120)

Restoring all server information that was saved in one 6.5 library to another 6.5 library does not restored the ER scheduled information. (F15381)

OLAP server problems fixed in Fix Pack 3.5

Libraries with names of exactly 10 characters can only be expanded once in the EIS console.

From patch 6.51.050: 

Member load through EIS hangs after MCH3601 message. (F17219)

When adding more than one filter in EIS for a dimension build, you must delete the file prefix name. (F16422)

When a new app/database is created Essbase is set to auto config the dense sparse settings and ignores the EIS settings. (F16409)

MaxL/400 does not create partition unless ddb files happen to exist in source and target dbs. (F17395)

From patch 6.51.040:

Invalid table qualifiers used: a«, a», ađ, aý in generating EIS Sql in HA drill. (F16644)

Displaying DBCS data through model or building outline was incorrect. (F16297)

Outline fails to restructure through 'load database', works through 'update outline'. (F16810)

INCBUILDDIM is not creating the error file member. (F16377)

Getting "Error -1:" when trying to export/save a model to an xml file from DBCS server. (F16238)

During calc of EIS created cube, application job crashes. (F16223)

ISR and Dynamic Time Series could produce invalid data returns. (F16112)

Report times out on iSeries and not on NT, after upgrading to 6.51. (F15876)

From patch 6.51.030:

Single CPU systems experienced excessive CPU usage and slow performance. (F14724)

To implement this fix we have provided a new config option to bypass the code to syncronize parallel calculation. If you are experiencing this issue, place "SCSerialModeDBExtract" in the CFG file before starting the Essbase server. The default value for this parameter is FALSE. Set it to TRUE if you are having similar performance problem.

Hybrid Analyis for DBCS data did not work. (F15482)

CRTOLAPRUL abends when ran via CL program or on command line. (F14533)

Recurisve parent/child join definitions in EIS could case an MCH3601. (F16007)

File descriptor limit reached, causing the Essbase server to crash. (F15976)

Essbase server fails with MCH3601 (adGetLogStartTime) when we encountered invalid date strings in the applicatoin job. (F15937)

Cetain fields on the statistics tab was showing incorrect information. The problem is correct. (F15517)

Essbase server crashed with integrated security turned on when attempting to synchronize users. (F15274)

Not possible to display the essbase server and application log if a date from is requested. (F14597)

Receiving "unable to find message database" after patch 6.51.020. (F15603)

Builder server problems fixed in Fix Pack 3

The following problems were fixed in the Builder server:

Use of subselect on a nonsecured table in WHERE clause will no longer cause row security to be ignored on the primary table. (F13014)

AS/400 Test Connection will display the correct versions for both STRATEGY ODBC and  the Microsoft Compliancy Level. (F1983)

The Essbase API services programs are now updated TO Essbase 6.51 in the Warehouse Manager Server library. (F13824)

Quoted constant in SQL being uppercased.ex: "quote" would turn into QUOTE. (F13951)

VARCHAR and VARGRAPHIC will now execute through Report Services and JDBC. (F14190)

Error:"Failed to save definition" received when attempting to save definition with UDC field in it. (F14345)

DATE(expression) where expression is complex (2 or more parameters) results in a "Token not valid" error. (F14412)

Use of PI() as the parameter in the DIGITS function results in the SQL exception - DIGITS use not valid. (F14417)

Customer receives, "Error, XError, null" when running One World query dynamically. The showcasecorp.log shows the following text: JDEOneWorldDataDictionaryInfo.setF9200Data: Exception occurred so it mustn't be UDC column: F9200 in PRODCTL type *FILE not found. (F14531)

SCSQLException: MSG_Referenced_Table_Not_Defined_In_From_Clause error for query with EXISTS. (F14665)

Non-DB2 distributions (Lotus, Access, Excel and SQL Server) and DB2 if the target server connection could not be made because of invalid password. The set failed with no errors displayed in the client when going to messages tab. (13244)

The error messages "PTF WWG010US ALREADY APPLIED TO LIBRARY" appears when you  attempt to apply patch after INSTORI. (F13469)

Restore of scheduled WB set that has past the run date now set to another set's scheduled date/time. (F13390)

Strategy Row security not applied to dynamically run JDE query. (F13329)

The 6.5 restore does not appear to restore .sdm and .slp files. (F12896)

SCPUB command issues "Value ' ' for parameter MSGID not a valid name." when running it from a 6.5 server.(F12867)

JDE BU security not being applied when a subselect is used. (F11887)

Underscore is treated as wild card -- More tables are shown in the list of tables than exist in the selected library. (F11488)

Back to the top

DB2 OLAP Server problems fixed in Fix Pack 3

The following fixes were implemented in Fix Pack 3 for DB2 OLAP Server (Essbase/400 6.51.022 Server patch):

MaxL changes: 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. User name, server name, and password cannot include spaces at the beginning or at the end. Spaces will be automatically trimmed. See your Hyperion documentation for more information.

New configuration setting: TARGETTIMESERIESOPT - 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 benefit from faster query times. See your Hyperion documentation for more information.

Saving a metaoutline in OIS causes MCH3601 message. (F15288)

DTS is not reflected in Essbase outline when created through OIS. (F15342)

"Invalid String" message appears after you double-click a linked-object in HESS in the Excel™ spreadsheet add-in for double byte character set (DBCS) client. (F15416)

OIS SQL Drill-through does not work in the samples. (F14990)

OS400DaysLogRetain will no longer block the application from starting. The session that started the application will be locked. (F14588)

Essbase server fails with integrated security turned on MCH3601 from module SynchronizeUser. (F15274)

Connection times in Application Manager do not display properly. (F14149)

Filters do not appear in Application Manager. (F14770)

Documentation: Essbase configuration file entry of '__SM__SERIAL_MODE'. See published resolution 36861. (F14447)

Port Hyperion Essbase XTD Analytic 6.5.4 Server. (F12816)

Message "Internal Error: Cannot disconnect from Olap service" when a user signs out of Analyzer. (F12997)

Configuration settings AGENTPORT, SERVERPORTBEGIN, SERVERPORTEND and PORTINC now work properly. (F13759)

Essbase now allows connections from 6.5.x API to talk to 6.2.x and 6.5.x servers. (F13682)

The "Error computing Generation" message was being returned incorrectly causing an empty report. (F13185)

Enable Essbase External Authentication via LDAP. (F13730)

Verify filter option in OIS console was failing, blank error message. (F14324)

Saving or exporting scripts in EYES would not run, garbled characters. (F14118)

Enhanced EYES scheduler. (F12722)

Getting SQL0104 errors running ISR based reports - SQL is garbled. (F14520)

Poor calc performance after applying 8.1fp1 on V5R2. (F14286)

If a user has a profile that is set to expire, with Integrated security, it will hang the server. (F14128)

Negative numbers are being loaded as positive in Essbase after upgrading to 6.51.001 using UDA sign flip. (F14120)

Reports with ISR Rule either returns error or causes application crash. (F14104)

Calculation with parallel calc never ends. (F13833)

Created more accurate error message in Excel. Instead of 'Columns in the report exceeded the maximum of 256', we now will receive the true 'The number of Cells in the report exceeded the allowed maximum of 2^32'. (F13287)

Problem when data load from file stored on server did not work on DBCS system if file contained member names with double byte characters is fixed. (F12959)

ISR and a partitioned database are not returning data correctly, Generation 2/level 0 members were not placed in ROT table. (F111592)

Numeric formats for regional settings: 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. Spreadsheet retrievals using the EssVZoomIn function may display multiple occurrences of the same value if preserve formulas is turned on. (24786)

Drop Partition when there is more than 1 source Corrupts the .ddb file. 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. (25956)

EssOtlGetGenName may not return generation names. The EssOtlGetGenName API may fail to return generation names. (27889)

Truncated words in the Japanese Application Manager. 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. (43538, 43539)

Report scripts containing the ORDERBY or TOP commands may fail to return some alias names. Report script may fail to return some alias names when using the ORDERBY or TOP commands. (56070)

Cannot create a transparent partition using MaxL. Creating transparent partitions in MaxL fails and returns an error message saying that the maxl execution failed and that the partition already exists. (56280)

Updating a transparently partitioned source outline may take longer than expected. 
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). (56412)

Reports that use the suppress missing rows (SUPMISSINGROWS) command and access data from a relational source may return incorrect results. 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. (56808)

EssVSetSheetOption function not working correctly in VBA toolkit. 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. (57194)

The create or replace MaxL statement fails when the application being copied is not empty. The create or replace MaxL statement fails when the application being copied is not empty. (57895)

Outlines with label-only attribute members can not be completely verified using EsbVerifyOutline(). 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). (58043)

Running a report script numerous times may cause the OLAP server crash. 
Running a report script a large number of times in quick succession may cause the OLAP server to crash. (58291)

Calculations with Intelligent Calc ON may not create the correct number of blocks. Intelligent re-calculation in single bitmap mode may not calculate some blocks, thus generating incorrect results. (58304)

EssQueryDatabaseMembers with the ALLSIBLINGSOF operator and relational members may fail. Using EssQueryDatabaseMembers with the ALLSIBLINGSOF operator and relational members may fail and may return network errors. (58343)

Running a Calc Script from MaxL may stop the Essbase server. 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. (59851)

Large concurrent retrievals that use the @XREF function may execute slowly. (59938)

Essbase may fail to load some zero level data during a parallel data load. (59998)

Loading data files that contain a large number of unknown records may cause the OLAP server to crash. (60016)

Unable to save report scripts in the Japanese Application Manager. 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. (60054)

The MaxL 'display filter row' statement may truncate large filters created by Planning. (60060)

Essbase may fail to display all mounted disk volumes on HP-UX. On HP-UX, Essbase may display only those disk volumes that are mounted at boot-up. (60098)

When "," is specified in the operating system as the decimal symbol, Essbase fails to recognize it as such during data loads. 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. (60126)

Creating large filters in MaxL may fail and may return the following error message: 'essmsh error: Statement exceeds maximum possible size.' (60159)

The VB API function EsbGetNextItem may fail when used with EsbLogin function. (60200)

Spreadsheet retrievals containing attribute members may cause the Essbase application to crash. (60224)

Using MaxL to create a partition with a large number of fields may cause the OLAP server to crash. (60241)

The OLAP server may crash during bottom up calculations with the Create Blocks on Equations setting enabled. The OLAP Server may crash during calculations when all of the following conditions are true: (60334)

Essbase does not return correct indicator when Hybrid Analysis members have children. 
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. (60785)

Maxl treats the append and write options in reverse. 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. (60844)

Essbase does not provide an automated way to perform a single outline verification at the end of an incremental dimension build. 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: (60930)

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. 
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. (60993)

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. (61084)

Drill through reports on multiple cells may cause the OLAP Server to hang. The OLAP server may hang when drill-through reports exceed a certain number of cells. (61111)

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. (61163)

MaxL script succeeds in importing data but the return code appears to indicate that the import failed. The following return code is displayed after a MaxL script successfully imports data: Bad free() ignored.(61228)

Intelligent re-calculations that use single bitmap calculator cache may not create the correct number of blocks. 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. (61581)

When multiple bitmap calculator cache is used, and there are backward references in the outline, intelligent recalculation may return incorrect results. 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. (61587)

Back to the top

DB2 OLAP Server problems fixed in Fix Pack 3 for Japanese

6588: Failure to set up SAMPLE on OIS.

6589: DBCS corruption on OIS Member Load and Data Load message.

6590: Version of exported XML is not supported to import.

6592: Help file is missing for Custom Definition Manager.

6593: (MaxL) Server shows incorrect time.

6602: DBCS string for "version" is garbled.

6608: (truncation SBCS) SBCS truncation in installation panel.

6646: (truncation) object in message on rule editor is truncated.

6674: (truncation) SBCS truncation on installation panels.

6675: The entry for DB administration guide in essdocs.htm is wrong.

6775: Unable to use HA.

6787: Cannot import metaoutline XML with DTRintersection.

6832: HA sample cannot be opened for version mismatch.

Back to the top

DB2 OLAP Server problems fixed in Fix Pack 1

Inability to initialize HA for DBCS.  (12301)

CALC DEFAULT does not work from OIS in certain DBCS NLV. (12322)

OIS Data load returns 1 record rejected error in DBCS. (12350)

During Essbase/400 install OIS member is not always added. (12312)

The Essbase server fails to start with OS400DAYSLOGRETAIN after upgrading to 6.5. (12262)

LRO function EssSmListLinkObjects() needs to support -1 as valid date range. (12401)

Replace brackets (left and right brackets) in server log files. (12297)

ENDESSSVR errors when taking defaults. (12484)

C2M1212 (server crash) when a user has more than 4 supplemental groups and is added with integrated security. (12385)

(1030213) ERROR: Cannot create local file. (12576)

Password is too short. It must be at least 1536 characters after upgrading Essbase to 6.5. (11788)

Query Logging file is not created after Query Logging is specified in database configuration file and app is restarted. (12036)

Dynamic Calc Report tests fail with Network Error after attempting to run report. (12180)

Syntax error loading filters. (11610)

Port Hyperion Essbase OLAP Server 6.5.1. (11501)

Runcalc error in Accxcalc calculator test. (11748)

Installation of 6.5.0 fails with existence of ESSSQL and ESSRSVR files. (12817)

Essbase fails with incorrect length of AS/400 password. (13888)

Retrieving cell note returns blank. (13449)

NPE when attempting to open a view. (13875)

Unable to expand sample TBC tables within HIS console. This is an OIS library list problem. (13711)

Client or server timed out while waiting to receive data using TCP/IP. (13877)

Menu in the member selection dialog box in the Spreadsheet Add-in might 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 might 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 might round relational data using incorrect precision. 22946. DB2 OLAP Server V8.1  might 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 might 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 might 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 might fail. 27608. Copying a database during a data export might 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 might 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 might 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 might cause the application to crash. 27911. Running a calc script with at least one formula might cause the application to crash and cause DB2 OLAP Server to create an exception log.

The @ROUND function might produce different results in DB2 OLAP Server V1.1 than it does in V7.1. 27971. Calculations that use the @ROUND function might have different results.

In the Spreadsheet Add-in, retrievals that return exactly 256 columns might fail. 28121. Any retrieval or spreadsheet operation, such as a pivot or drill down, that returns exactly 256 columns might fail.

The OLAP server might crash during a database copy if the security file is very large. 28271 (33419). Copying a database with a very large security file (73MB), might cause the OLAP server to crash.

Spreadsheet retrievals with all members in the same column might crash the application. 28342 (33499, 33113). Certain spreadsheet retrievals that have unusual formatting, such as displaying all members in a single column, might 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 might crash the application. 28718. Running a parallel calculation that uses the Calc TwoPass command might crash the application.

Certain spreadsheet retrievals might 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 might misalign the column headings and data.

The UPDATEVARIABLE command might 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 might fail when connecting to Analyzer. 29039. When running on the Solaris 8 platform, the OLAP server might fail when connecting to an application via DB2 OLAP Server Analyzer 7.1 (Hyperion Analyzer 5.0.3).

Certain queries might fail the application. 29187. Retrievals of dynamic calc members with member formulas containing the @PRIOR function might cause the application to fail.

Linked Partitions might not work. 29190. Drilling down on partitioned target members might not launch the linked objects browser.

Calculations that use the CALC DIM calculation command might crash the OLAP server. 29211. Using the CALC DIM calculation command with the dimension names listed out of outline order might 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 might fail and might result in the error "Unable to free aligned memory for [datctxp->ppDatMemPage[]]in[adDatTermDatCtx]."

The results of calculations that use SET AGGMISSG ON might be incorrect. 30739. Some calculations that include the command SET AGGMISSG ON might 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 might take longer than expected. 33869. Running the CCONV calculation command on Currency Conversion applications might take longer than expected.

The MaxL Perl Module might limit the length of query results to 128 characters. 35170. Query results from the MaxL Perl Module might 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 might return incorrect results. 36982. Queries from databases with upper level attribute members that have level-one base members with only one child might return incorrect results.

Memory leak when running calculations that use the @XREF function. 37090. Calculations that use the @XREF function might fail and might result in the error message "Unable to Allocate Memory"

Some calculations might be incorrect in DB2 OLAP Server V8.1 that were correct in previous versions. 37742, 40027, 40039

Data loads with one or more unknown members might hang. 43211. Loading data from a file that has at least one unknown member might cause the OLAP application to hang.

Spreadsheet retrievals that have the same member in two consecutive rows might 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 might crash Excel. 43248. Using styles for linked objects, read only cells, or read/write cells might cause Excel to crash during spreadsheet retrievals.

Spreadsheet retrievals from transparently partitioned databases with attribute dimensions might crash the application. 43306. Retrieving from a database that has attribute dimensions and is the target in a transparent partition might 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 might fail because of excessive memory usage. 43433. Certain free form data loads from data files that have a large number of columns might fail because of excessive memory usage. Data files created by exporting data from a database with a large number of sparse members might have a large number of columns.

The SQL Drill Through Add-in (DB2 OLAP Server V.1. FixPak 14) might 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 might fail. 43553. The Esscell function might incorrectly return zeros for dynamic time series data.

Deleting databases might not delete data that resides on spanned disk volumes. 54953. Using ESSCMD or Application Manager to delete databases might fail to delete .pag files from the spanned disk volumes.

Parallel calculations might crash the application under certain circumstances. 55126. Parallel calculations might 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 might 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 might take longer.

Dimension builds that change consolidation properties might also alter attribute associations. 55244. Changing consolidation properties using a dimension build rules file might alter existing attribute associations, causing the outline to become invalid.

Back to the top

DB2 OLAP Integration Server problems fixed in Fix Pack 1

Numbers in parentheses are current internal reference numbers for Hyperion Solutions; numbers in brackets indicate previous Hyperion tracking numbers.

User-defined members cannot be added to drill-through report intersection levels. In OIS V8.1, users are not able to add members from user-defined dimensions to the intersection level specifications of drill-through reports. Prior to V8.1, users were able to add user-defined members as intersection levels in drill-through reports. (27126) [32002]

Users are unable to drill down on multiple cells. In OIS V8.1, users are unable 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 might 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 you perform a member load, duplicate members from the Accounts dimension are rejected. (26479) [31187]. Current limitations are:

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)

Back to the top

Known issues

Every effort has been made to ensure that DB2 OLAP Server products perform without problems. 

Essbase open issues

Unsupported functions:

Hybrid Analysis--EssException (ODBC message--operands not compatible) when creating report against 10.10.61.61:HA_NuCT:basic (13153).

Warehouse Builder open issues

Possibility of unhandled MCH exceptions from JDEUDCF. The locks by default waits for the default job wait time of 30 seconds. If, for some reason, the lock doesn't occur in that time, an exception is thrown. Since there are currently no exception handlers, this causes an unhandled exception. There needs to be an exception handler around the lock/unlock so it can fail gracefully rather than failing with unhandled MCH exceptions appearing in the job log.

Unable to open non-DB2 definitions after 6.5 over the 4.5 installation. There is a workaround--update via definition properties. The cause of this problem is that the non-DB2 definitions restored with the value of "JDBC_DATASOURCE" in OBATR contain useless data. This causes the set to fail during loading of the definition information before running any part of the set. JDBC_DATASOURCE value in OBATR must reference a MAPID in the JDBCODBC table. The MAPID must be a number padded with spaces up to 18 characters.

Warehouse Builder closed issues

No error message displays in Warehouse Builder for a set that fails due to an incorrect password. This issue was resolved in 6.5 patch 1.

Installation error when updating components or updating spreadsheet add-ins

You might receive the following error during a installation update:

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. 

Network installation--the OLAP server does not load when Lotus 1-2-3 is started

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. 

Incorrect level for sample database on an installation window

If you install the Warehouse Manager server component of DB2 OLAP Server for iSeries, Version 8.1 (Essbase 6.51) and install the sample database, and then you try to install it again, an installation window will appear asking if you want to install the SCSAMPLE45 sample database. The text in the window is incorrect. Although the windows says SCSAMPLE45, the actual sample database is SCSAMPLE65.  The installation program will not install the older version of the sample database whether you answer Yes or No to the prompt.

Hybrid Analysis Known Issues

When working with a Hybrid Analysis-enabled outline with formulas attached to one or more members in the Accounts dimension that have parent members that are not marked as Label Only, you must explicitly propagate these formulas up the Accounts dimension hierarchy in order for queries involving relational members to reflect calculations using the formulas. Otherwise, DB2 OLAP Server uses the hierarchical relationships between members to determine the values for the relational cells. For example, in the sample Hybrid Analysis application shipped with the product, Ratios is a member in the Accounts with two children, Margin and Profit, containing formulas. If Ratios is not marked as Label Only and Ratios is intended to be the sum of Margin and Profit values, you must edit the outline to add the formula Ratios = Margin%Sales + Profit%Sales. This limitation will be addressed in a future release. (23411)

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 might be incorrect.

NOTES ON LIMITATIONS:

Running drill-through reports generates different SQL for same members

Running drill-through reports on a stored member and a shared version of that same stored member generates different SQL, and no reports are created. (56503)

Drill-through values from recursive hierarchies replaced by null values or spaces

When running a drill-through report based on user-defined drill-through SQL, values and parameters from dimensions containing recursive hierarchies are sometimes replaced by null values or spaces. (56901)

Drill-through reports fail to generate on members below intersection level

Drill-through reports complete successfully for members at the intersection level but fail to generate data for all members below the intersection level. The user receives the false message, "There are no reports defined for selected intersection." (56925)

Filters not working on shared members in drill-through reports

Drill-through reports on shared members are ignoring the filter in the WHERE clause of the generated SQL, causing reports to display rows belonging to all members of the dimension rather than just the designated shared member. (56646)

Multiple drill-through reports use incorrect WHERE clause

If multiple drill-through reports exist based on the same intersection level of a dimension, the drill-through reports sometimes fail to use the correct WHERE clause in the SQL. (57085)

Drill-through reports not functioning on Accounts dimension with recursive hierarchies

Drill-through reports are failing to complete successfully on the Accounts dimension if it has a recursive hierarchy. (56852)

Unable to access data source during drill-through operations in Excel

Attempting to access a data source while performing a drill-through report in Excel causes an Online Database Connectivity (ODBC) error, and the data source cannot be accessed for the report. (56868)

Back to the top

Problems not fixed

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.
16412 In Excel, in Query Designer, the server location radio button might 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 might 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 might cause extra "Please Log In" messages, because the user might have been logged out due to inactivity. Click OK until the message stops appearing.
18041 DB2 OLAP Server might 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 might 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 might cause a server crash if these conditions are true: 
  1. The outline has DTS members defined in the Time dimension and 
  2. The partition definition doesn't mention the Time dimension, indicating it should include all members. 
Then you should mention the Time dimension explicitly, for example, @Idesc("Time-dimension-name").
19522 When compiling client API programs on NT, with MS VC ++ version 6.0 and higher, you might 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 might not validate in the Calc Script Editor of the Application Manager and might 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 might 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 might 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 might 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 might open in a separate window.
23374 The application log, when displayed via Application Manager, might 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 might 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: 
  • If each source database is part of a different application on a different machine, increase SERVERTHREADS in the configuration file essbase.cfg on each machine. Increase the value by the same number you use in CALCPARALLEL.
  • If all source databases are part of the same application on the same machine, increase the value of SERVERTHREADS using this formula:
(number of source databases) * (value of CALCPARALLEL)
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: 
  • From Spreadsheet Add-in, you perform a Zoom with the All Levels option selected on a dimension that is Hybrid-Analysis enabled, and that zoom creates more than one rollup.
  • In a report script, you use a Hybrid-Analysis enabled dimension in a ROW report command and use the report command DESCENDANTS on that dimension, creating more than one rollup. For example: 
    <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 might 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 Fix Pack 5 or V8.1 on Windows 2000 or Windows NT systems, using the EsbSetActive Visual Basic API in code samples in Microsoft Access 2000 might 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) might 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 might cause the application to crash and might 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 might 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 data loads; otherwise, an exception error might 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';.

Back to the top

Copyright Information

Licensed Material.  Property of IBM.
© Copyright International Business Machines Corporation 1998, 2003, 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
© 1997–2004 ShowCase Corporation. All Rights Reserved.
©Copyright 1991-2004 Hyperion Solutions Corporation. All Rights Reserved.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

Intel, Intel Inside (logos), MMX and Pentium are trademarks of Intel Corporation in the United States, other countries, or both.