IBM DB2 OLAP Server 8.1

Refreshed Release

Release Notes

Service Levels:

• Essbase OLAP Server 6.5.0.3
• Essbase Integration Services 6.5.0

Contents:

• Read this before you start
• Moving to the Refreshed release
• Other installation updates
• Documentation updates
• Sample applications for OIS
• Known issues and workarounds
• Tips

This Release Notes document and the Installation Guide are essential for installing DB2 OLAP Server products successfully.  Before you begin installing any DB2 OLAP Server products, read this Release Notes document, which supplements and corrects information in the Installation Guide.

The Installation Guide is available in the root directory of the DB2 OLAP Server CD and it can be downloaded along with DB2 OLAP Server, or from our Web site:

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

You can install all the documentation, including the Installation Guide, on your client computer by selecting the Custom option in the installation program, and selecting which books you want to install.

• If you installed the server component from the English-only release, with or without the English-only clients, and you want to upgrade to the Refreshed release, run the installation program from the Refreshed CD and select the Repair option.
• If you installed Clients Only from the English-only release, do not install the clients from the Refreshed release. If you install the Refreshed clients on top of the English-only clients, the clients will be disabled. If you have disabled the clients in this way, the workaround is to uninstall the English-only clients and reinstall the Refreshed clients.  This is a known problem and exists on Windows only.  (IBM5801)
• If you installed Clients Only from the English-only release and now you want to install the Refreshed clients in another language, uninstall the English-only clients before installing the Refreshed clients in your language.

• On Windows, do not install the Arabic clients.  The clients in Arabic are not supported and should not be listed in installation program.  This is a known problem.  (IBM5810)

• Required levels of Java have changed in the Refreshed release.  Check the table below and make sure you have the correct level of Java:

• OLAP Miner requires the DB2 OLAP Server API.  If you run the main installation program but do not install the API, and then run the OLAP Miner installation program, OLAP Miner will not be complete and will fail. Make sure you have the API installed before installing OLAP Miner.

 
• Spreadsheet Add-In Installation for Excel XP: If you install the Spreadsheet Add-In for Excel XP, and have selected "install on first use" in Excel, and haven't started Excel at least once before trying to use the Add-In, be sure to install Visual Basic for Applications, or Excel may not load the Add-In.

• New I/O Default: Buffered I/O is the default beginning with DB2 OLAP Server Version 7.1, FixPak 8. See the Installation Guide for more information about migration issues. The What's New in Version 8.1 chapter of the Installation Guide contains information about how to apply direct I/O to individual databases.

• Migration Information for New I/O Default: Default access methods are different in different versions of DB2 OLAP Server:
• DB2 OLAP Server Version 1x, Version 7.1 FixPak 8 (and later), and Version 8.1 use buffered I/O by default. They also allow you to set the access method to Direct I/O. Verify which access method you are using before migration.
• DB2 OLAP Server Version 7.1 through FixPak 7, uses direct I/O by default.
Cache settings do not change during migration. It's likely that your cache settings were increased if you used direct I/O. If you migrate from direct I/O to a release using buffered I/O, you may wish to re-adjust any cache sizes you changed when using direct I/O.

If you wish to keep the buffered I/O default for databases being migrated from direct I/O, you may want to adjust caches (index cache, data cache) if you previously changed them for direct I/O.

For more detailed information, see the Installation Guide.

• Temporary Directory Path Issues:

On UNIX, if you have an environment variable called TMPDIR set, then unset this environment variable so DB2 OLAP Server can create temporary files in the default directory /tmp. If you want to use the TMPDIR environment variable, ensure that its path name is no longer than 15 characters. If the full path to the temporary file is greater than 15 characters, some functions may fail.

• UNIX Installation: These issues may affect your UNIX installation:

• Erroneous ARBORPATH  Message: If you install to a new directory where DB2 OLAP Server has not been installed previously, you can ignore the following warning during the installation process:
chmod: WARNING: can't access $ARBORPATH/bin/*.*
• HP-UX 11.0, 11i Installation If you install DB2 OLAP Server on HP-UX 11 or 11i, you may need patches from HP, available from the HP Web site (www.software.hp.com). Search for: hp-ux quality pack bundles
• HP-UX and Memory Issues: For optimal use of memory, we recommend the HP-UX environment setting _M_ARENA_OPTS to 4:8. For more information on this setting, consult the HP-UX documentation on malloc. (22847 closed.)
• No Wait I/O Not Supported on HP-UX: DB2 OLAP Server V8.1 does not support no wait I/O on HP-UX.

• DB2 OLAP Integration Server does not accept "Localhost" as a server name. In the Login dialog box, specify a machine name or machine IP address in both the DB2 OLAP Integration Server frame and the DB2 OLAP Server frame.

• DB2 OLAP Integration Server requires an odbc.ini file for operation of Open Database Connectivity (ODBC) connections from DB2 OLAP Integration Server to the relational data source and to the OLAP Metadata Catalog:

• On Windows systems, this file is in the Registry under \HKEY_LOCAL_MACHINE\SOFTWARE\ODBC. Use ODBC Data Source Administrator to store information about how to connect to a relational data source. The ODBC.ini file is available in ODBC software packages and is included with Microsoft Office software. For more information about applications that install ODBC drivers or the ODBC Administrator, visit the Microsoft Support Web site.
• On UNIX systems, the installation program creates a model odbc.ini file. To store information about how to connect to a relational data source, edit the file using your preferred editor or use the odbcconfig tool provided in the ishome/bin directory.

• Automatic upgrade of OIS metadata catalogs does not work. The Installation Guide incorrectly states that you can use the OLAP Metadata Catalog Setup dialog box to automatically upgrade your existing metadata catalogs to Version 8.1.  This feature is temporarily disabled, even though, when select the upgrade option, DB2 OLAP Integration Server displays a message indicating that it successfully upgraded the catalog.  The workaround is to upgrade the metadata catalog manually, following the instructions in the "Creating OLAP Metadata Catalogs for DB2 OLAP Integration Server" chapter in the Installation Guide.  This is a known problem

• Uninstall OLAP Miner before uninstalling DB2 OLAP Server.  If you want to remove DB2 OLAP Server V8.1 from a computer and you have OLAP Miner V8.1 on it, uninstall OLAP Miner first, then uninstall the rest of DB2 OLAP Server.  You uninstall OLAP Miner by selecting Start -> Programs -> IBM DB2 OLAP Server V8.1 -> OLAP Miner - MODIFY OR REMOVE INSTALLATION.  If you uninstall the entire product first and then try to uninstall OLAP Miner, the environment appears corrupted to OLAP Miner, and the uninstallation only partially completes. The workaround is to delete the DB2 OLAP Server directory (for example, c:\ibm\db2olap), which will complete the OLAP Miner uninstallation and will remove all other DB2 OLAP Server files.

• Cleanup after uninstall.  When you remove DB2 OLAP Server from your computer, some directories might still remain on your drive after the uninstallation program completes, and some environment variables might not be deleted.  After backing up whatever applications and logs you want to keep, you can manually delete these directories and environment variables from your computer.

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

Updated network installation instructions

DB2 OLAP Server Version 8.1 offers your enterprise the option of installing the client components from a shared network file server. If you use this option, a file called netinst.htm is installed on the file server in the \install directory.  The netinst.htm  file contains insructions on how to install the clients from the network.  The copy of netinst.htm  that is installed on the file server are incorrect.  The correct copy of netinst.htm  is stored in the root directory of the CD.  If you put the clients on a file server,  copy netinst.htm  from the root of the CD and replace the version that is installed in the \install directory on the file server.

Two books for DB2 OLAP Integration Server moved to online help

The OLAP Integration Server Model User’s Guide and the OLAP Integration Server Metaoutline User’s Guide were discontinued as of Version 7.1 FixPak 8 (Essbase 6.2).  Procedures from these guides are now available in the online help.  Conceptual information and details on preparing relational data for a multidimensional database are provided in a new document entitled the Integration Server Data Preparation Guide.

Documentation refers to Hyperion default directory instead of IBM directory.

The default installation directory for DB2 OLAP Server is different from the default installation directory for Hyperion Essbase.  Most of the documentation refers to the Hyperion directory.  The IBM directory is:

    \ibm\db2olap

To activate Hybrid Analysis, take the following steps:
 

1. Set 'HAENABLE TRUE' in $ARBORPATH/bin/essbase.cfg file.   If you don't set HAENABLE TRUE in the essbase.cfg configuration file, Hybrid Analysis will not work.
2. In Spreadsheet application, click Essbase -> Options and select the Zoom tab.  Then check the Enable Hybrid Analysis option.


DB2 OLAP Server does not support Teradata.  Chapter 1 of the Installation Guide incorrectly states that DB2 OLAP Integration Server supports the Teradata RDBMS.  Teradata is not supported by DB2 OLAP Integration Server.

OLAP Miner configuration file updates:
 

• The language element has been removed from the client configuration file (OMClient.cfg) for DB2 OLAP Server Miner.
• The Spreadsheet parameter for OMClient.cfg now has a new parameter called parms.  With the parms parameter you can provide extra parameters to the spreadsheet program that you start from OLAP Miner. This parameter is useful if you want to start a national language (localized) version of Lotus 1-2-3.  For example, you can specify the following values to start the Swedish version of Lotus 1-2-3 on a computer where the Swedish version is installed:

<spreadsheet  value = "C:\lotus\123\123w.exe"  parms="-L SV" />
If you want to know which localization parameter is required for your version of Lotus 1-2-3, open the properties window for the icon that you double click to start Lotus 1-2-3.
• The spreadsheet element is properly called spreadsheet, not spreadsheet_path. In the "Configuring the OLAP Miner Client" chapter of the OLAP Miner User's Guide,  the spelling of the spreadsheet element name is correct in the sample OMClient.cfg file. However, it is incorrect in the definition list.
Memory Optimization for Parallel Calculation

(32105) When using parallel calculation in multiple bitmap mode, you may encounter high memory usage. If you encounter this, you can use the configuration setting ParCalcMultipleBitmapMemOpt to optimize memory use in multiple bitmap mode. This setting can be used together with, or separately from, MultipleBitmapMemCheck.

To enable ParCalcMultipleBitmapMemOpt, add this line to your essbase.cfg file:

ParCalcMultipleBitmapMemOpt TRUE

101 Port Limit Default Increases to 501, Can Be Changed

Beginning with Version 7.1 FixPak 8 (Essbase 6.2), the default port settings for the ServerPortEnd, ServerPortBegin, and PortInc configuration file settings, when combined, yield an available number of ports to be 101.

Specifically, the number of available ports is equal to:

ServerPortEnd - ServerPortBegin
-----------------------------------------   +  1
PortInc * (ports needed per application)

Prior to Version 7.1 FixPak 8, the number of ports needed per application was 1. In Version 7.1 FixPak 8, that number was increased to 2.

To have access to more than 501 ports in Version 8.1, increase the value of these configuration settings.

For example, assume default values for ServerPortEnd and ServerPortBegin, and default values for PortInc. The formula would be: [((33768 - 32768) / (1 * 2)] + 1 = (1000 / 2) + 1 = 501

(31576)

AGTSVRCONNECTIONS Values Incorrect

The minimum and default value for AGTSVRCONNECTIONS is 1, not 2 and 5 respectively, as stated in the documentation.

Solaris API Makefile Library Order

30328: For Solaris, your makefile should include all of these libraries, in this order:

1. esstest.out
2. posix4
3. socket
4. nsl
5. pthread
6. globalc
7. essotl
8. essglob
9. essapi
10. essnet
11. ssshr
12. essutl
13. esssd
14. esssec

 
API Message Change

Messages sent to the user-defined Callback function are passed to DB2 OLAP Server in EssInit. Previous to Version 7.1 FixPak 8, if a message contained NLS characters (foreign language characters, such as accented characters), DB2 OLAP Server provided them in OEM (DOS) format. In Version 7.1 FixPak 8 and later, these messages are completely in character (Windows) format, to avoid the misinterpretation of certain characters.

This only affects non-English editions of the product.

Server Password Distinct From Supervisor

When you change the password for the supervisor it does not affect the system password, the password required when you start DB2 OLAP Server. During initial installation, DB2 OLAP Server creates two identical user names and passwords, one for the system user who starts DB2 OLAP Server, and a separate supervisor (super user). Thus, you can change the supervisor's password without affecting the password used to start DB2 OLAP Server. To change the system password, use the Agent command PASSWORD. See the Installation Guide or Database Administrator's Guide for details.  (24928, 31846, 31851)

MAXLOGINS Minimum

The documentation should state in the Notes section for configuration setting MAXLOGINS:

If the setting is too low, DB2 OLAP Server increases the value to 1000. (30278)

Some Actions are Always in Committed Access Mode

The documentation should state that these processes always use committed access:

• Spreadsheet Add-in lock and send
• Grid API
(31334)

Memory Issues With Committed Access Mode

This information is missing from the main documentation set:

• If your data cache is too small to hold the number of blocks specified in your commit settings, then blocks will be written to disk before the transaction is committed as soon as the caches become full. This allows other blocks to come in and be worked on.
• Each lock (one lock per block) uses approximately 80 bytes of memory to track through a calculation, and these locks are held in memory until the transaction has been completed. This memory usage can present problems for models with large number of blocks as there is a limit to the addressable memory space per process and eventually large models may hit this limit.
(31334)

Valid Values for CALCPARALLEL

Valid values for CALCPARALLEL (or SET CALCPARALLEL) are 1-4. Documentation incorrectly states 0-4.

Reserved Words Requiring Quotation Marks

The documentation may not contain a complete list of reserved words that must be enclosed in quotation marks to be used for member names. The list will be updated in a future release.

Changing Database Names While Outline Locked

Previous versions of DB2 OLAP Server allowed you to change a database name while the corresponding outline was locked. DB2 OLAP Server now returns an error message and does not change the database name.

If you need to perform this task, you can write an ESSCMD script that unlocks the outline (UNLOCKOBJECTS command). If you need to perform this task from MaxL, you can call the ESSCMD script from a MaxL script, using a MaxL shell escape to ESSCMD. For example, a MaxL script that includes the line: shell ESSCMD unlock.scr will run the ESSCMD script unlock.scr. Note: the ESSCMD script must contain its own login statement. (31617)

HTML Documentation

You may encounter these issues with HTML documentation:

• If you use the browser reload button or command in Netscape 4.x, all the information in the left pane may disappear (Contents, Index, Search). To correct, use File > Open to re-open the file.
• The index for the HTML version of the Database Administrator's Guide may take up to 90 seconds to load.
PDF Documentation:

On Windows NT, the Database Administrator's Guide in PDF format (dbag.pdf) can cause the Acrobat Reader 3.02 to hang when it is launched from the Documentation menu, which is available from Start -> Programs -> DB2 OLAP Server V8.1 -> Documentation.   The workaround is to launch the file directly from the x:\ibm\db2olap\docs directory, or upgrade to a later version of Acrobat Reader.

MaxL Documentation

The MaxL documentation shows an incomplete example for creating a user that will be authenticated using external authentication (32532). This example is more complete because it includes the host name:

'cn=Engineers, ou=Groups, dc=yahoo, dc=com@hostname:389'

For each of the sample databases, a new sample OLAP Metadata Catalog (TBC_MD) contains sample OLAP models (TBC Model or HA TBC Model) and sample metaoutlines (TBC Metaoutline or HA TBC Metaoutline). The OLAP models and OLAP metaoutlines for the sample applications are provided in XML files.

The sample applications demonstrate how to create a Measures dimension recursively, using a sort on an alternate column in the relational data source, and how to load metadata from database columns. Additionally, the sample applications include UDAs and Date Time Series data, additional years, drill-through paths, and a Time table to demonstrate incremental update for data loads. The sample applications also demonstrate how to enable and use Hybrid Analysis.

For each of the sample databases, DB2 OLAP Integration Server V8.1 provides two drill-through sample spreadsheets based on the TBC sample data. These two spreadsheets are:

• essdt.xls
• essdt.123

In order to use the sample drill-through reports, essdt.xls and essdt.123, you need to log in to a computer that has both the DB2 OLAP and DB2 OLAP Integration Server installed. You must perform a member and data load and calculate the data for the sample OIS database that you will access from the Spreadsheet Add-in.

Note:  When creating samples, make sure the user id TBC is in uppercase letters (TBC); otherwise you may get error messages indicating that some tables do not exist.

Hybrid Analysis known issues

Hybrid Analysis supports only DB2 using native drivers or Merant drivers, and Oracle ODBC using Merant drivers. See the Installation Guide for details.

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:

• Oracle SQL does not support the Rollup operator.
• The Descendants operator in Report Writer will work correctly with the Column specification on Hybrid Analysis enabled dimensions but will not function in the Row Specification.
• Drill-down to all levels in a spreadsheet does not work for Hybrid Analysis enabled dimensions.

Version 8.1 of the MaxL Perl Module (essbase.pm) works with Version 8.1 of DB2 OLAP Server. It is not compatible with previous releases.

Although the limit for stored calculations is 64 KB, calculation scripts created in MaxL that have multi-byte characters cannot exceed 40 KB.

Some display output constants are not described in the MaxL documentation. The constant definitions are given below, and can also be found in maxldefs.h.

Possible values of the currency conversion field of the display database statement:
 

Constant	Value
1	division
2	multiplication

Possible values of the file type field of the display disk volume statement:
 

Constant	Value
1	index
2	data
3	index and data

Possible values of the type field of the display privilege statement:
 

Constant	Value
1	system privilege
2	system role
3	execute calculation
4	filter

Every effort has been made to ensure that DB2 OLAP Server and DB2 OLAP Integration Server are as free of bugs as possible. Some known problems and system limitations are listed below, with workarounds when appropriate. The numbers next to each bug are internal reference numbers.
 

Bug Number	Description
IBM5810	Do not install the Arabic version of the product.  The Arabic version is currently not supported but will be in a future update.
IBM5801	If you installed Clients Only from the English-only release, do not install the clients from the Refreshed release. The English clients you already installed are fully-functional; the fixes in Essbase 6.5.0.3 are only on the server.  If you install the Refreshed clients on top of the English-only clients, the licensing program will be disabled and the clients will not work.  The workaround is to uninstall the English-only clients and reinstall the Refreshed clients.
IBM5809	If you install a Lotus 1-2-3 or Microsoft Excel spreadsheet program after you install DB2 OLAP Server, and you have a problem with the spreadsheet program, you must update your Windows PATH statement using the short format.  For example, on Windows NT, take these steps to update your PATH statement: On the Control Panel, select System. On the System Properties notebook, select the Environment tab. In the system variables box, copy the value for ARBORPATH to the clipboard.  The value might look like this:  C:\PROGRA~1\IBM\DB2OLA~1 Add a semicolon to the end of the existing PATH value, and paste the ARBORPATH value after the semicolon. At the end of the value you just appended to the PATH statement, add: \bin   Click Set and then OK. Reboot your computer to apply the new PATH statement. For Windows 98 and Windows Me, add <ARBORPATH>\bin to the end of the PATH statement in the autoexec.bat file.  It must be in the short form.
IBM5725	If you migrated from Version 7.1 to the Refreshed Version 8.1 (Essbase 6.5.0.3) on UNIX, you might see an error message about two license numbers being registered when you launch DB2 OLAP Server.  Disregard this message.
IBM5816	If you install OLAP Miner and then uninstall it, the Spreadsheet Add-in for 1-2-3 might be disabled.  The workaround is to manually add the Spreadsheet Addin to Lotus 1-2-3.  Follow the instructions in "Adding Essbase Spreadsheet Add-in" in Chapter 2 of the Spreadsheet Add-in User's Guide for 1.2.3.
IBMNA1	If you use DB2 OLAP Server or DB2 OLAP Integration Server on UNIX, you might encounter problems with them after you install DB2 Universal Database V7, FixPak 2a or later, or DB2 Universal Database V8.  DB2 installs new ODBC drivers that support UNICODE, but DB2 OLAP Server does not support these new drivers.  The workaround is to switch your ODBC files to point to the non-UNICODE ODBC drivers. The non-UNICODE drivers have been renamed to add "_36" in their names.  For example, for Solaris, the driver libdb2.so was renamed to libdb2_36.so, and for AIX,  the driver db2.o was renamed to db2_36.o.  For more information about changing ODBC drivers, see "Configuring the SQL Interface" in the Installation Guide. Future FixPaks of DB2 Universal Database will continue to have this same restriction until the DB2 OLAP Server ODBC program is changed to accept UNICODE drivers.  See the Installation Guide for more information about supported software.
IBM5238	In the ESSBASE.CFG configuration file, when you specify a value for the HaMemoryCacheSize parameter, do not include a space between the numeral and the qualifier.  For example, "2M" is acceptable, but "2 M" causes an error.
18529	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.
19278	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.
19593	DB2 OLAP Server does not support discontinuous selection in Lotus, although it does in Excel.
19614	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.
20451	DB2 OLAP Server does not warn you if you request that export results be written to a file that already exists. DB2 OLAP Server overwrites the existing file.
20488	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.
20562	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.
20600	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.
20606	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.
21012	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.
22235	Using Dynamic Time Series (DTS) members on a partitioned database may cause a server crash if these conditions are true:  The outline has DTS members defined in the Time dimension and  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").
22545	When compiling client API programs on NT, with MS VC ++ version 6.0 and higher, you may experience random API program crashes because when a workspace file is created a bug in MS VC++ causes the API program to crash. Workaround: compile the program on the command line by using the compiler "cl" directly, after verifying that there are no problems with the API program itself.
22678	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.
23380, 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....
24037	When you view a drill through report via the Spreadsheet Add-In, all members at a particular generation or level in a dimension are displayed with highlighting, even if only one member of that generation or level is associated with the drill through report.
24106	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.
25938, 27865, 27338	Running too many concurrent reports may overwhelm DB2 OLAP Server or operating system resources, especially against partitioned databases. If this occurs, reduce the number of such reports running concurrently.
26931	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.
27034	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.
27370	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."
27927	Whenever one process is logged out by another process (such as Application Manager running on another machine), the process doing the logout is logged off, and trying to access the server produces an error message even though Application Manager controls appear to still be active.  Workaround: Log in again.
28064	Trying to associate an attribute with an implied shared member causes the association to be ignored, and DB2 OLAP Server writes a message to the application log. An implied shared member is a member with only one child.
28140	For EssOtlQueryMembers on UNIX, the currency conversion type returned is incorrect.  Workaround: Use EssOtlFindMember instead.
28506	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.
28507	Some characters, such as those using umlaut or accent marks, cannot be typed in ESSCMD interactive mode.
30122	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.
30600	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.cfgon 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)
30641	The index page size is now fixed at 8 KB.
32024	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)
32060	If you use direct I/O, and have set DLTHREADSWRITE to a value of 16 or greater, DB2 OLAP Server 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 DB2 OLAP Server.
32107	If you perform a calculation on a target database of a transparent partition, and at least one of the source databases is in the same application as the target, and you encounter these errors, your application may crash:  Error message 1042017 issued by the source. Error message 1023040 issued by the target. Error message 1023058, "Transparent operation involving [Source] timed out," issued by the target. Workaround: Increase the value of NetRetryCount to prevent the source from timing out while waiting to receive data. Measure the time from when the last "Processing distributed request" message was issued by the source and the time at which the source issues the timeout message (1042017). Then increase the value of NetRetryCount so that the product of NetRetryCount and NetDelay (NetDelay * NetRetryCount) is greater than the time measured.
32317	DB2 OLAP Server only: You can no longer select 'DB2 relational' as a storage method when creating applications using Application Manager, because beginning with DB2 OLAP Server Release 8.1, the relational storage manager is not available.

Known bugs in DB2 OLAP Integration Server:

1. Erroneous message displayed when Oracle is on same HP-UX system as DB2 Universal Database. When you run DB2 OLAP Integration Server with DB2 Universal Database on an HP-UX system and you also have Oracle installed on the same system, you might see an error message that contains the string "error-2."  Disregard this message (IBM5430)
2. Automatic upgrade of OIS metadata catalogs does not work.  The Installation Guide incorrectly states that you can use the OLAP Metadata Catalog Setup dialog box to automatically upgrade your existing metadata catalogs to Version 8.1.  This feature is temporarily disabled, even though, when you select the upgrade option, DB2 OLAP Integration Server displays a message indicating that it successfully upgraded the catalog.  The workaround is to upgrade the metadata catalog manually, following the instructions in the "Creating OLAP Metadata Catalogs for DB2 OLAP Integration Server" chapter in the Installation Guide.  (IBM4655)
3. Option for Administration Manager still visible (but grayed out) on Tools menu.  In Version 8.1, the Application Manager replaces Administration Manager.  All the function that was available previously in the Administration Manager is available in the Application Manager.  However, the Administration Manager option is still visible on the Tools menu; disregard it.  (IBM4691)
4. Pass-through transformations using SQL functions not supported

DB2 OLAP Integration Server V8.1 does not support Pass-through (Database Specific) transformations using SQL functions. Specifying a built-in RDBMS function, such as Substring, or Left, causes DB2 OLAP Integration Server to generate invalid SQL.
(15131)
5. Incorrect display of attached reports

If you are using Excel and you drill down on Accounts, all account members are highlighted as having an attached report even though you have selected only one member.
(23923)
6. Lower case login id not recognized

DB2 OLAP Integration Server does not recognize the login id 'tbc' when it is entered in lower case in the SQL server database.
(26115)
7. Drill-Through reports not functioning with multiple metaoutlines

Drill-Through reports may not function correctly following incremental loads of two or more metaoutlines. Only the report which loaded with the last metaoutline is present.
(29199)
8. "Essbase Integration Services Shell" not displayed in client-only installations

During the installation, in the Select Components dialog box, if you highlight the option Essbase Integration Services Console, the description reads "Essbase Integration Services Console." The description should also include "Essbase Integration Services Shell."
(32390)
9. Delete and Restore Database parameter not available

In the System Administrator's Guide, the sections covering the LOADALL and LOADMEMBER commands incorrectly list [DELETE_DB=Delete and Restore Database;] as an optional parameter. This parameter is not available and all references to it should be disregarded.
(32394)
10. If you use DB2 OLAP Server or DB2 OLAP Integration Server on UNIX, you might encounter problems with them after you install DB2 Universal Database V7, FixPak 2a or later, or DB2 Universal Database V8.  DB2 installs new ODBC drivers that support UNICODE, but DB2 OLAP Server does not support these new drivers.  The workaround is to switch your ODBC files to point to the non-UNICODE ODBC drivers.  The non-UNICODE drivers have been renamed to add "_36" in their names.  For example, for Solaris, the driver libdb2.so was renamed to libdb2_36.so, and for AIX,  the driver db2.o was renamed to db2_36.o.  For more information about changing ODBC drivers, see "Configuring the SQL Interface" in the Installation Guide.  Future FixPaks of DB2 Universal Database will continue to have this same restriction until the DB2 OLAP Server ODBC program is changed to accept UNICODE drivers.  See the Installation Guide for more information about supported software.

(n/a)

OLAP Miner mines the multidimensional data in Hybrid Analysis cubes.  You can use OLAP Miner to mine the multidimensional portion of cubes that are enabled for Hybrid Analysis.  OLAP Miner does not access the relational portion of Hybrid Analysis cubes.

Known Limitations in DB2 OLAP Integration Server:

• If Oracle 8.0.x on Solaris or HP-UX fails due to the unresolved symbol, slpmprodstab, change directories to ishome/odbc/merant40/src/oracle and run ./genclntsh8.
• If your Operating System file system does not allow more than eight-character names, the member load and view sample functions may fail.

WORKAROUND: Start DB2 OLAP Integration Server in a directory that is in a file system that supports longer names.
• If DB2 OLAP Integration Server encounters a NULL value during a data load, it automatically loads the data into the parent member of the NULL. However, if the NULL is at Generation 2, DB2 OLAP Integration Server cannot load the data to the parent member because the parent member is the dimension level member. In this case, DB2 OLAP Integration Server records an error in the log file.

WORKAROUND: Do not include NULLs at Generation 2.
• If you delete a member and then add a member with the same name, DB2 OLAP Server assumes that restructuring of the database outline is necessary even though restructuring is not required in this situation, and you are thus prompted to restructure. For complete information on restructuring, see the Database Administrator's Guide.
• When creating a drill-through report with an OLAP intersection level based on a User Defined dimension or column, neither of the variables of the form $$dimension-COLUMN$$ or $$dimension-VALUE$$ will be created.
• If you select the option "Enable Hybrid Analysis Down to Here," you are enabling Hybrid Analysis from the selected level down. You are not enabling any level above the one you select for Hybrid Analysis.

Hybrid Analysis is not supported for Accounts dimensions that contain a user-defined member at level zero under the following conditions: there is no formula associated with the user-defined member, and any consolidation option except ~ (ignore) is selected.

Custom-defined functions (CDFs) cannot be validated on the client, because they are only known to the server. DB2 OLAP Server recommends server validation whenever possible.

On Solaris, if you want to use cache memory locking, you must run the root.sh file.

NOTE: Cache memory locking is only available with direct I/O.

CAUTION: Using root.sh may interfere with SQL Interface. You may need to choose between SQL Interface and cache memory locking.

If you receive compilation errors in your calculation scripts, check the errors to be sure that variable names are not enclosed in quotation marks. The first character of variable names must be a letter (a through z). Variable names may contain: letters, numbers (0 through 9), and the special characters: $ (dollar sign), # (number sign), and _ (underscore).

For Japanese versions of  DB2 OLAP Server to work properly on AIX and Solaris, you must install additional locales not shipped with DB2 OLAP Server. These are included on the setup CD of each operating system.

• The locale needed for Solaris is ja_JP.PCK.
• The locale needed for AIX is IBM-943. (21012)
The essbase.jar file should always reside in the /java directory of your installation if you intend to use the samples provided.

When migrating from DB2 OLAP Server V7.1, FixPak 7 and earlier, to Version 7.1 FixPak 8 and later or Version 8 (From Essbase 5.x to 6.2 or later), if you notice a degradation in calculation performance and your outline has several formulas on dynamic calculation members, add a line with CALCMODE BLOCK to your essbase.cfg file. Restart DB2 OLAP Server, then rerun the same calculation to see if it improves performance.
 

• Java adds a startup memory requirement of approximately 10MB per application. If you install Java but are not using custom-defined macros or functions, you can reduce your startup memory requirement by disabling Java. To disable Java, remove all parameters from the JVMMODULELOCATION setting in the essbase.cfg file. For more information about this setting, see the online Technical Reference.

 
• On HP-UX platforms, if you observe DB2 OLAP Server using an inordinate amount of memory, it could be a bug in the HP-UX operating system with respect to memory management for multi-threaded programs. Consider installing the following HP-UX operating system patch:

XSWGR1100    B.11.00.48   HP-UX General Release Patches, March 2000
and the following library patch:
PHCO_22314   1.0          libc cumulative patch