IBM DB2 OLAP Server 7.1
and DB2 OLAP Integration Server 7.1

FixPak 11
Release Notes

FixPak Date:  May 2003

Service Levels:

• Essbase OLAP Server MR6.2.4
• Essbase Integration Services R6.2.1

Important:

The DB2 OLAP Server and DB2 OLAP Integration Server clients no longer support Windows 95.  The clients support Windows 98, Windows NT 4.0 SP5 and later, and Windows 2000.

If your current service level is FixPak 6 or earlier, and if you installed the DB2 OLAP Integration Server (OIS) sample application, then you should back up your existing OIS sample database, OLAP Metadata Catalog, and the OLAP models and metaoutlines that you want to preserve before installing this FixPak.  After backing up your samples, you can upgrade your existing catalog to be compatible with this FixPak (see Upgrading the OLAP Metadata Catalog). You cannot, however, store new sample OLAP models and metaoutlines in your previous catalog.  Nor can you roll back to the previous release after migrating your metadata catalog to FixPak 7 or later, which is not compatible with previous FixPaks.  Do not attempt to use the FixPak 7 or later catalog with previous levels of DB2 OLAP Integration Server software. Doing so could result in corrupted OLAP Metadata Catalog data.

If you are installing client products from a DB2 OLAP Server FixPak, you must install server products to the same FixPak level. For example, if you install a FixPak 11 client, you must also install the FixPak 11 server. Using older server versions with newer client versions is not recommended and is not supported.

IBM DB2 OLAP Server offers a feature exclusive to IBM called DB2 OLAP Server Miner.  See DB2 OLAP Server Miner combines OLAP and data mining technologies for more information about what OLAP Miner can do for you.

Contents:

• FixPak installation overview
• Before you install the FixPak
• Changes to supported software
• Physical memory and disk requirements
• Stopping services on Windows before installation
• Workaround for bug on Windows
• Migrating applications to FixPak 4 and later
• Installing the FixPak
• Installing on UNIX
• Installing on Windows
• Setting up Java
• Setting up Java on UNIX
• Installing Java on UNIX
• Updating Java environment variables for DB2 OLAP Server on UNIX
• Giving the OLAP server access to JAXP on UNIX
• Updating Java environment variables for OIS on UNIX
• Setting up Java on Windows
• Setting Java environment variables on Windows
• Setting JVMMODULELOCATION on Windows
• Additional setup instructions for OLAP Integration Server
• ODBC requirements
• JDBC requirements
• Configuration tips
• After you configure a data source
• Migrating to OLAP Integration Server
• Connecting OIS to Oracle on Solaris
• Additional setup instructions for Excel XP
• Changes in this FixPak
• Additional documentation
• Known problems and limitations
• Problem summary:  A list of all the problems fixed by this and previous FixPaks.
• Tips
• Copyright information

FixPak installation overview

For instructions on downloading and installing the files in this FixPak, see Installing on UNIX or Installing on Windows, depending on your operating system. FixPak 4 and later adds additional function that requires Java; see Setting Up Java on Windows and Setting up Java on UNIX for instructions.  For more detailed information about installation, see the OLAP Setup and User's Guide.

FixPak 11 for DB2 OLAP Server Version 7.1 is the equivalent of maintenance level 4 (patch 4) for Hyperion Essbase Release 6.2 and maintenance level 1 (patch 1) for Hyperion Integration Server 6.2.  Hyperion maintenance levels are cumulative; each level contains new fixes and all the fixes for the previous maintenance levels.

Before you install the FixPak

Changes to supported software

FixPak 7 and later changes the levels of software supported by DB2 OLAP Integration Server:

• Java 1.3 or later is now required.  See Setting Up Java on Windows and Setting up Java on UNIX for more information.
• The Spreadsheet Add-in now supports Excel XP.  If you have a custom installation of Excel XP, the Spreadsheet Add-in may not be visible in Excel XP, or the Essbase System Login box may fail to appear when you choose Essbase > connect. Choose the complete Excel XP installation instead, or, if you have already installed Excel XP using a custom installation, go back and install Office Shared Features and Office Tools from the Excel XP installation program. If you choose the option to install the Office Shared Features on first use, you must pre-install Visual Basic for Applications before running the Spreadsheet Add-in.  Additionally, you must configure Excel XP after installation; see Additional setup instructions for Excel XP for more information.
• The OIS clients no longer support Windows 95.  The OIS clients support Windows 98, Windows NT 4.0 SP5 and later, and Windows 2000.
• The OIS clients require 64MB or more of RAM.

FixPak 4 and later changes the levels of software supported by DB2 OLAP Server:

• To use the custom-defined macros and custom-defined functions, you must install Java^TM Runtime Environment 1.2.2 or later, and Java API for XML Parsing 1.01.  On Windows, if you choose not to install Java, custom-defined macros and functions are not enabled.  On UNIX systems, Java is required; you must install it manually.  See Setting Up Java on Windows and Setting up Java on UNIX for more information.
• The server components of the DB2 OLAP Server support the following operating systems and service levels:
• Windows NT 4.0 servers with SP 5 and Windows 2000
• AIX version 4.3.3 or higher
• Solaris Operating System version 2.6, 7, and 8 (Sun OS 5.6, 5.7, or 5.8)
• The client components run on Windows 95, Windows 98, Windows NT 4.0 SP5, and Windows 2000.
• The Spreadsheet Add-in clients now support Lotus 1-2-3 Millennium R9.5.

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 Configuration tips in this document, and also see "Loading and Configuring ODBC for the SQL Interface" in Chapter 4, "Installing on AIX, Solaris Operating Environment, and HP-UX," of the OLAP Setup and User's 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 OLAP Setup and User's Guide for more information about supported software.

Physical memory and disk requirements

Basic amount of RAM needed for most applications

Memory limitations

• Windows NT 4.0 Workstation/Server (service pack 3 or later):  2GB
• Windows NT 4.0 Enterprise Server (service pack 3 or later): 4GB
• Windows 2000 Professional:  2GB
• Windows 2000 Server:  4GB
• Windows 2000 Advance Server:   8GB
• Windows Data Center Server:  64GB
• AIX - 2 GB per process
• HP-UX - 1.7 GB per process
• Solaris - 2 GB per process

Memory problems

If memory is low, the following unpredictable problems can occur:

• Applications crash
• Operating systems crash
• Calculations remain incomplete
• Shutdown process is disrupted
• Degraded performance is noticeable

• Check the exception error logs to see if you are running low memory.  Run the UNIX performance monitor to determine when Hyperion Essbase is using swap space instead of physical memory.

Stopping services on Windows before installation

To stop Windows NT and Windows 2000 services:

1. Select Services from the Control Panel.
2. From the Service list, select the service for DB2 OLAP Server and, if present, the service for DB2 OLAP Integration Server.
3. Click Stop.

Workaround for bug on Windows

c:\temp

1. On your Windows 2000 workstation, click Start -> Settings -> Control Panel -> System.
2. Select the Advanced tab of the System Properties dialog.
3. Click Environment Variables.
4. In the User variables box, scroll down to the TEMP variable, highlight it, and click Edit....
5. On the Edit User Variable dialog, change the Variable Value to c:\temp and click OK.
6. In the System  variables box, scroll down to the TMP variable, highlight it, and click Edit....
7. On the Edit System Variable dialog, change the Variable Value to c:\temp and keep clicking OK until you close the Environment Variables dialog.

1. Edit the Autoexec.bat file located in C:\ root.
2. Enter these two lines:
• set=TEMP C:\temp
• set=TMP C:\temp

Migrating applications to FixPak 4 and later

Your applications are automatically migrated to the latest FixPak level when you open them.

Installing the FixPak

Starting in FixPak 4, DB2 OLAP Server requires Java to enable new function; starting in FixPak 7, DB2 OLAP Server also requires Java.  See Setting Up Java on Windows and Setting up Java on UNIX for more information.

Installing on UNIX

You can also install OLAP Miner in this FixPak.  The server component of OLAP Miner is available only on AIX 4.3.3 and later.

The OLAP Setup and User's Guide incorrectly states that you must be logged on with a user ID that has root privileges when you install DB2 OLAP Server on UNIX systems.  You do not need root privileges to install the product.

Installing fixes for the UNIX server

To start the server installation:

1. On your UNIX system, extract the installation files by entering the following command from the temporary directory containing the installation .tar file:
tar -xf filename.tar


This command extracts the files necessary to perform a complete installation.
 

2. Run setup.sh to launch the installation program.  Follow the installation instructions in the OLAP Setup and User's Guide.   (On AIX, if you get a segment fault or a core dump when you install or use DB2 OLAP Server, then the current AIX stack size on the computer is not large enough.  To increase the stack size, run the AIX command "ulimit -s unlimited".  For more information about the ulimit command, see the AIX Commands Reference.)

 
3. After the files are expanded, you can delete the .tar file.

Using scripts to update environment settings on UNIX

Starting in FixPak 4, DB2 OLAP Server requires Java, and scripts are included with DB2 OLAP Server that you can use to set the required environment variables for Java.  FixPak 7 updates the scripts with new settings.  The scripts are stored in the main installation directory for DB2 OLAP Server. An explanation of the scripts is provided in the file essbaseenv.doc, which is also located in the main installation directory.  The following scripts are provided:

• essbaseenv.sh:  Korn Shell script to set environment variables for DB2 OLAP Server.
• essbaseenv.csh: CShell script to set environment variables for DB2 OLAP Server.
• essjava.sh:  Korn Shell script to set Java-specific environment variables for DB2 OLAP Server.
• essjava.csh:  CShell script to set Java-specific environment variables for DB2 OLAP Server

• hisjava.sh:  Korn Shell script to set Java-specific environment variables for DB2 OLAP Integration Server.  Starting in FixPak 7, this script contains Java variables that were previously in essbaseenv.sh.
• hisjava.csh:   CShell script to set Java-specific environment variables for DB2 OLAP Integration Server.  Starting in FixPak 7, this script contains Java variables that were previous in essbaseenv.csh.

Installing fixes for the Windows clients

To start the installation:

1. Expand the executable file by typing the name of the file (without the extension) from a command prompt, or by double-clicking the file.
2. Run SETUP.EXE to launch the installation program.  Follow the installation instructions in the OLAP Setup and User's Guide.
3. On one of the installation prompts, you can choose to install the OLAP Miner documentation along with the client.  Installing the documentation is recommended.
4. After the files are expanded, you can delete the zip file.

Installing on Windows

You can also install OLAP Miner in this FixPak.  OLAP Miner supports the following levels of Windows operating systems:

• Server component: Microsoft Windows NT 4.0, Windows 2000
• Client component: Microsoft Windows 95, Windows 98, Windows ME, Windows NT 4.0, and Windows 2000

Installing fixes for the Windows server and clients

Starting the installation

1. Expand the executable file by typing the name of the file (without the extension) from a command prompt, or by double-clicking the file.
2. Run SETUP.EXE to launch the installation program.  Follow the installation instructions in the OLAP Setup and User's Guide.
3. On one of the installation prompts, you can choose to install the OLAP Miner documentation along with the server and client.  Installing the documentation is recommended.
4. After the files are expanded, you can delete the zip file.

Starting in FixPak 8, DB2 OLAP Server changes how the CLASSPATH variable is set.  See Setting Java environment variables on Windows for more information.

Setting up Java

Starting with FixPak 4, DB2 OLAP Server requires Java for custom-defined macros and custom-defined functions.  The Java Runtime Environment and the Java API for XML Parsing must be installed on computers running the server component.  This includes the Java Virtual Machine (JVM), which is a component of the JRE. If you have already installed a supported version of the Java Runtime Environment, you do not have to reinstall the JRE. However, you must verify that the JAXP component is installed, set the JVMMODULELOCATION parameter, and set environment variables.

Starting with FixPak 7, DB2 OLAP Integration Server also requires Java.

After the Java components are installed on your system, you can use a Java development kit (JDK) of your choosing to create your own custom-defined macros and custom-defined functions.  A JDK is not supplied with DB2 OLAP Server or DB2 OLAP Integration Server.

Setting up Java on UNIX

Starting with FixPak 7, DB2 OLAP Integration Server also requires Java, but not the same level used by DB2 OLAP Server. The following table lists the levels of Java you need:
 

Product	Operating system	Java Runtime Environment level
DB2 OLAP Server	AIX	1.2.2
	Solaris	1.3.0
	HP-UX	1.2.2
DB2 OLAP Integration Server	AIX	1.3.0
	Solaris	1.3.0_02
	HP-UX	1.3.0.01

If you have already installed a supported version of the Java Runtime Environment, you do not have to reinstall the JRE. However, you must verify that the JAXP component is installed, set the JVMMODULELOCATION parameter, and set environment variables.

These are the major steps to enable Java to work with DB2 OLAP Server and DB2 OLAP Integration Server on UNIX:

1. Install the Java Runtime Environment (JRE) and the Java API for XML Parsing (JAXP).
2. Set the Java environment variables for DB2 OLAP Server.
3. Set the JVMMODULELOCATION parameter to give DB2 OLAP Server access to JAXP.  This parameter is set in the essbase.cfg file so you can designate a specific installation of the Java Runtime Environment for use with DB2 OLAP Server. This setting is particularly useful if you have multiple versions of Java installed on the computer running the OLAP server component.
4. Set advanced configuration options for Java, if necessary.
5. If you use DB2 OLAP Integration Server (OIS), set the Java environment variables for it.

This section also includes tips on finding out which shell you are using.

After following the instructions in this section, if you are still having difficulties getting DB2 OLAP Server to work with Java, it may be necessary to set start-up options for the Java Virtual Machine (JVM). You can make DB2 OLAP Server use specific JVM start-up options when it loads the JVM by setting the environment variables ESS_JVM_OPTION1 through ESS_JVM_OPTION9.

Installing Java on UNIX

1. Log in using an account that has root privileges.
2. Copy the ARBORPATH/bin/jrte_<platform>_ess.tar file into the /tmp directory.
3. Extract the Java package using tar xvf jrte_<platform>_ess.tar. On AIX, a .gz file is extracted from the jrte tar file, which can then be opened using gunzip on UNIX, or Winzip or PKZip on Windows to extract the .rte package to be installed below.
4. If you use DB2 OLAP Integration Server:
1. Copy the ISHOME/bin/jrte_<platform>_is.tar file into the /tmp directory.
2. Extract the Java package using tar xvf jrte_<platform>_is.tar. On AIX, a .gz file is extracted from the jrte tar file, which can then be opened using gunzip on UNIX, or Winzip or PKZip on Windows.  For example, enter:

  gzip -dv jre130.tar.gz
which makes jre130-20010330.tar available.
5. Install the extracted package as described in the following sections.

Installing Java on AIX:

• X11.adt.lib 4.3.3.0
• X11.adt.motif 4.3.3.1
• bos.adt.include 4.3.3.0
• bos.adt.prof 4.3.3.0

For DB2 OLAP Integration Server:  Copy the file jre130-20010330.tar to ISHOME.  Then type:   tar xvf jre130-20010330.tar   to de-compress the JRE directory and its associated files.

The next step is to set the Java environment variables for your operating system.

Installing Java on Solaris:

 chmod +x jXrel_XXXXX-solsparc.bin

where XXXXX represents the specific version number.  Then run the self-extracting binary:

For DB2 OLAP Server, type:   jXrel_XXXXX-solsparc.bin

For DB2 OLAP Integration Server:  Copy the file jre130-20010330.tar to ISHOME.  Then type:   tar xvf jre130-20010330.tar   to de-compress the JRE directory and its associated files.

The next step is to set the Java environment variables for your operating system.

Installing Java on HP-UX:

 swinstall rte_XXXXX.depot

where XXXXX represents the specific version number.

For DB2 OLAP Integration Server:  Copy the file jre130-20010330.tar to ISHOME.  Then type:   tar xvf jre130-20010330.tar   to de-compress the JRE directory and its associated files.

The next step is to set the Java environment variables for your operating system.

Updating Java environment variables for DB2 OLAP Server on UNIX

After setting the environment variables below, log out of the system and back on to activate the new settings. Run the following command to verify that the correct version of Java is set before starting Essbase:

> java –fullversion

• On HP-UX, you see java full version "1.2.2.05-00/08/14-PA_RISC2.0"
• On AIX, you see java full version "J2RE 1.2.2 IBM build ca122-19991217"
• On Solaris, you see java full version "1.3.0"

Updating environment variables for DB2 OLAP Server on AIX

Important: If you are using a DB2 instance ID, then you need to add the variables into the .profile BEFORE the DB2 instance profile is invoked.

If you use the C shell, add the following text to the .cshrc file:

setenv JREHOME "/usr/java_dev2/jre"
setenv LIBPATH "${JREHOME}/bin:${JREHOME}/bin/classic:${LIBPATH}"
setenv LD_LIBRARY_PATH "${JREHOME}/bin:${JREHOME}/bin/classic:${LD_LIBRARY_PATH}"
set path=( ${JREHOME}/sh /usr/java_dev2/sh $path )
setenv CLASSPATH "${ARBORPATH}/java/jaxp.jar:${ARBORPATH}/java/parser.jar:${CLASSPATH}"

If you use the Bourne or Korn shell, add the following text to the .profile file:

export JREHOME=/usr/java_dev2/jre
export LIBPATH=$JREHOME/bin:$JREHOME/bin/classic:$LIBPATH
export LD_LIBRARY_PATH=$JREHOME/bin:$JREHOME/bin/classic:$LD_LIBRARY_PATH
export PATH=$JREHOME/sh:/usr/java_dev2/sh:$PATH
export CLASSPATH=$ARBORPATH/java/jaxp.jar:$ARBORPATH/java/parser.jar:$CLASSPATH

Updating environment variables for DB2 OLAP Server for Solaris

NOTE that JREHOME must be at the beginning of the PATH statement, before /usr/bin.

If you use the C shell, add the following text to the .cshrc file:

setenv ESS_JVM_OPTION1 "-XX:+AllowUserSignalHandlers"
setenv JREHOME "${ARBORPATH}/bin/j2re1_3_0"
set path=( ${JREHOME}/bin $path )
setenv CLASSPATH "${ARBORPATH}/java/jaxp.jar:${ARBORPATH}/java/parser.jar:${CLASSPATH}"
setenv LD_LIBRARY_PATH "${JREHOME}/bin:${LD_LIBRARY_PATH}"

ESS_JVM_OPTION1=-XX:+AllowUserSignalHandlers
export ESS_JVM_OPTION1
JREHOME=$ARBORPATH/bin/j2re1_3_0
export JREHOME
PATH=$JREHOME/bin:$PATH
export PATH
export CLASSPATH=$ARBORPATH/java/jaxp.jar:$ARBORPATH/java/parser.jar:$CLASSPATH
export LD_LIBRARY_PATH=$JREHOME/bin:$LD_LIBRARY_PATH

Updating environment variables for DB2 OLAP Server on HP-UX

Note: The directory, PA_RISC, may be PA_RISC2.0, depending on the processor used by the computer running HP-UX.  In addition, due to a problem with the Just In Time compiler in release 1.2.2 of the JRE for HP-UX, you must also set an ESS_JVM_OPTION.

Note: Some of these environment variable settings are coded assuming the variables are already set on your HP-UX system, and they add new values to your existing settings.  HP-UX does not automatically create these variables if they do not exist.  If you receive an error message about environment variables not being set, you must manually create the variables.  See your HP-UX documentation for more information about setting environment variables.

If you use the C shell, add the following text to the .cshrc file:

setenv JREHOME "/opt/java1.2/jre"
setenv SHLIB_PATH "${JREHOME}/lib/PA_RISC:${JREHOME}/lib/PA_RISC/classic:${SHLIB_PATH}"
set path=( $path ${JREHOME}/bin  )
setenv ESS_JVM_OPTION1 "-Djava.compiler=NONE"
setenv CLASSPATH "${ARBORPATH}/java/jaxp.jar:${ARBORPATH}/java/parser.jar:${CLASSPATH}"

JREHOME=/opt/java1.2/jre
export JREHOME
SHLIB_PATH=$JREHOME/lib/PA_RISC:$JREHOME/lib/PA_RISC/classic:$SHLIB_PATH;
export SHLIB_PATH
PATH=$PATH:$JREHOME/bin;
export PATH
ESS_JVM_OPTION1=-Djava.compiler=NONE;
export ESS_JVM_OPTION1
CLASSPATH=$CLASSPATH:$ARBORPATH/java/jaxp.jar:$ARBORPATH/java/parser.jar;
export CLASSPATH

Giving the OLAP server access to JAXP on UNIX

/ARBORPATH/java/*.jar

1. On the computer that runs the OLAP server, change to the ARBORPATH/bin directory.
2. In the essbase.cfg file, add a new line to the end of the file and type the following text:
JVMMODULELOCATION FullpathAndFilenameOfJvmLibraryFile

On AIX (JRE 1.2.2): Make sure you enter this setting in mixed case, as follows:

JvmModuleLocation /usr/java_dev2/jre/bin/classic/libjvm.a

/usr/j2se/jre/lib/sparc/client/libjvm.so

CAUTION: On Solaris, do not set the JVMMODULELOCATION to point directly to the libjvm.so file, or the JVM will crash when DB2 OLAP Server attempts to load it. Set JVMMODULELOCATION to the symbolic link for this file. The default location for the symbolic link is:\

/olaptest/essbase7/bin/j2re1_3_0/lib/sparc/libjvm.so

where /olaptest/essbase7/bin/ is the ARBORPATH in this example.

On HP-UX (JRE 1.2): Make sure you enter this setting in mixed case, as follows:

JvmModuleLocation /opt/java1.2/jre/lib/PA_RISC/classic/libjvm.sl

The directory, PA_RISC, might be PA_RISC2.0, depending on the processor used by the computer running HP-UX.
 

Updating Java environment variables for OIS on UNIX

After setting the environment variables below, log out of the system and back on to activate the new settings. Run the following command to verify that the correct version of Java is set before starting Essbase:

> java –fullversion

• On HP-UX, you see java full version "JavaVM-1.3.0.01"
• On AIX, you see java full version "1.3.0"
• On Solaris, you see java full version "1.3.0_02"

Updating environment variables for OIS on AIX

Important: If you are using a DB2 instance ID, then you need to add the variables into the .profile BEFORE the DB2 instance profile is invoked.

If you use Bourne or Korn C shell, add the following additional variables from the hisjava.sh file:

export TEMP=/tmp
export JAVA_HOME=$ISHOME/jre
export PATH=$JAVA_HOME/bin:$PATH
export CLASSPATH=$JAVA_HOME/lib:$CLASSPATH
export LIBPATH=$JAVA_HOME/lib:$LIBPATH

setenv TEMP  " /tmp"
setenv JAVA_HOME "{ARBORPATH}/is"
setenv PATH "${JAVA_HOME}/bin:${PATH}"
setenv CLASSPATH "${JAVA_HOME}/lib:${CLASSPATH}"
setenv LIBPATH "${JAVA_HOME}/lib:${LIBPATH}"

Updating environment variables for OIS on Solaris

NOTE that JREHOME must be at the beginning of the PATH statement, before /usr/bin.

If you use Bourne or Korn C shell, add the following additional variables from the hisjava.sh file:

export TEMP=/tmp
export JAVA_HOME $ARBORPATH/is/bin/j2re1_3_0_02
export PATH=$JAVA_HOME/bin:$PATH
export CLASSPATH=$JAVA_HOME/lib:$CLASSPATH
export LD_LIBRARY_PATH=$JAVA_HOME/lib:$LD_LIBRARY_PATH

setenv TEMP "/tmp"
setenv JAVA_HOME "${ARBORPATH}/is"
setenv PATH "${JAVA_HOME}/bin:${PATH}"
setenv CLASSPATH "${JAVA_HOME}/lib:${CLASSPATH}"
setenv LD_LIBRARY_PATH "${JAVA_HOME}/lib:${LD_LIBRARY_PATH}"

Updating environment variables for OIS on HP-UX

Note: The directory, PA_RISC, may be PA_RISC2.0, depending on the processor used by the computer running HP-UX.  In addition, due to a problem with the Just In Time compiler in release 1.2.2 of the JRE for HP-UX, you must also set an ESS_JVM_OPTION.

Note: Some of these environment variable settings are coded assuming the variables are already set on your HP-UX system, and they add new values to your existing settings.  HP-UX does not automatically create these variables if they do not exist.  If you receive an error message about environment variables not being set, you must manually create the variables.  See your HP-UX documentation for more information about setting environment variables.

If you use Bourne or Korn C shell, add the following additional variables from the hisjava.sh file:

export TEMP =/tmp
export JAVA_HOME=/opt/java1.3/jre
export PATH=$JAVA_HOME/bin:$PATH
export CLASSPATH=$JAVA_HOME/lib:$CLASSPATH
export SHLIB_PATH=$JAVA_HOME/lib$SHLIB_PATH

setenv TEMP  " /tmp"
setenv JAVA_HOME "${ARBORPATH}/is"
setenv PATH "${JAVA_HOME}/bin:${PATH}"
setenv CLASSPATH "${JAVA_HOME}/lib:${CLASSPATH}"
setenv SHLIB_PATH "${JAVA_HOME}/lib:${ISHOME}/esslib:${ISHOME}/islib;${SHLIB_PATH}"

Finding which shell you are using

> echo $SHELL

Which gives this result:

/usr/bin/ksh

This indicates you're using the Korn Shell.  Here is a list of other responses you might get:

/usr/bin/sh  Bourne Shell
/usr/bin/rsh  Restricted Bourne Shell
/usr/bin/jsh  Bourne Shell, with job control
/usr/bin/ksh  Korn Shell
/usr/bin/rksh Restricted Korn Shell
/usr/bin/csh  C Shell

Another way is to examine the file called etc/passwd, which you can see by running the cat command, as follows:

cat /etc/passwd
 

Setting up Java on Windows

1. Set up environment variables for the Java Runtime Environment (JRE).
2. Set the JVMMODULELOCATION parameter in the essbase.cfg file so you can designate a specific installation of the Java Runtime Environment for use with DB2 OLAP Server . This setting is particularly useful if you have multiple versions of Java installed on the computer running the OLAP server component.

Setting Java environment variables on Windows

Setting JVMMODULELOCATION on Windows

c:\Program Files\IBM\DB2 OLAP Server\java\jre\bin\hotspot\jvm.dll

1. On the computer that runs the OLAP server component, change to the ARBORPATH\bin directory.
2. Locate the essbase.cfg file in this directory and open the file in a text editor. If the file does not exist, create and open a new text file named essbase.cfg .
3. In the essbase.cfg file, add a new line to the end of the file and type JVMMODULELOCATION followed by the full path and file name of the JVM library file.  For example:
JVMMODULELOCATION c:\Program Files\IBM\DB2 OLAP Server\java\jre\bin\hotspot\jvm.dll
4. Save the changed text file as essbase.cfg .
Close the file and exit the text editor.

Additional setup instructions for OLAP Integration Server

• ODBC requirements
• Configuration tips
• Configuring data sources on UNIX systems
• Configuring the OLAP metadata catalog on UNIX systems
• Configuring data sources on Windows systems
• Configuring the OLAP metadata catalog on Windows systems
• After you configure a data source
• Migrating to OLAP Integration Server
• Connecting OIS to Oracle on Solaris

ODBC requirements

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.

On UNIX systems, DB2 OLAP Integration Server installation 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.

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 following web site:

http://support.microsoft.com/directory/default.asp

For Windows NT or Windows 2000 users:  you must upgrade to Version 3.6 if you have not already done so.

For Oracle users on AIX and HP-UX computers: To configure ODBC for Oracle, you must update the ODBC.ini file to point to the MERANT 3.6 drivers.

Operating system requirements:

• Windows NT 4.0 servers with SP 5 and Windows 2000 on Pentium or later computers
• AIX version 4.3.3 or higher servers on PowerPC computers, including RS 6000
• HP-UX version 11.0 servers on PA-RISC computers
• Solaris version 2.6, 7, and 8 (Sun OS 5.6, 5.7, or 5.8) servers on Sun SPARC or ULTRASPARC computers
• Windows 95, Windows 98, Windows NT 4.0 SP5, or Windows 2000 for client software

Supported ODBC drivers matrix:

1. MERANT 3.6 ODBC drivers are supported only on HP-UX 11.0 computers using 32-bit relational database client software.
2. If you are using MERANT 3.6 ODBC drivers with Informix, Oracle, or Sybase, you must have Microsoft Data Access Components 2.5 (MDAC) installed. The MDAC installation file, installed when you install ODBC drivers, is located in    ishome\odbc\merant36\mdac on Windows and $ISHOME/odbc/merant36/mdac on UNIX..
3. The Microsoft Data Access Components 2.5 (MDAC) installation file, installed when you install ODBC drivers, is located in:   ishome\odbc\merant36\mdac on Windows.

JDBC Requirements

• JDBC Type 1 is compatible with all RDBMSs supported by DB2 OLAP Integration Server. It is installed when you install the Java Runtime Environment (included as an option in the Windows installation; included as a separate installation for UNIX).
• The JDBC Type 3 driver works on all platforms.

Configuration tips

Configuring data sources on UNIX systems

Configuring ODBC environment variables

Editing the odbc.ini file

Note: If you use a different file than the odbc.ini file, be sure to set the ODBCINI environment variable to the name of the file you use.

To add a data source to an odbc.ini file:

1. On the computer running OLAP Integration Server, open the odbc.ini file by using a text editor such as vi.
2. Find the section starting with [ODBC Data Sources] and add a new line with the data source name and description; for example:  mydata=data source for analysis.  To minimize confusion, the name of the data source should match the name of the database in the RDBMS.
3. Add a new section to the file by creating a new line with the name of the new data source enclosed in brackets; for example:   [mydata]
4. On the lines following the data source name, add the full path and file name for the ODBC driver required for this data source and any other required ODBC driver information. Use the examples shown in the following sections as a guideline to map to the data source on your RDBMS.  Note: Make sure that the ODBC driver file actually exists in the location you specify for the Driver= setting.
5. When you have finished editing odbc.ini, save the file and exit the text editor. For more information about the odbc.ini file and the ODBC driver settings for each RDBMS, see the MERANT DataDirect Connect ODBC Reference in PDF format and the related Readme files in the ODBCDocs directory. For more information about native ODBC driver settings, refer to the installation documentation for your RDBMS native ODBC drivers.

Example of ODBC Settings for DB2

Use the vi $ODBCINI command to edit the odbc.ini file and insert the following statements:

[ODBC Data Sources]
db2data=DB2 Source Data on AIX
...
[db2data]
Driver=/home/db2inst1/sqllib/lib/db2.o
Description=DB2 Data Source - AIX, native

Example of ODBC Settings for Oracle

[ODBC Data Sources]
oradata=Oracle8 Source Data on Solaris
...
[myoracle] Driver=
/export/home/users/dkendric/is200/odbclib/ARor815.so
Description=my oracle source

Tip: Run ivtestlib to verify that the environment is set to run the correct odbc driver file. For example, run ivtestlib and paste the path and file name that follow Driver= in the odbc.ini file that you have edited.

Configuring the OLAP metadata catalog on UNIX Systems

You must create an OLAP Metadata Catalog database in a supported RDBMS before configuring it as an ODBC data source.

Here is an example how you might edit odbc.ini to connect to the OLAP Metadata Catalog, TBC_MD, on DB2 Version 6.1 (on Solaris), using a native ODBC driver:

[ODBC Data Sources]
ocd6a5a=db2 v6
...
[ocd6a5a]
Driver=/home/db2instl/sqllib/lib/db2.0
Description=db2

Using ODBC drivers coded in Unicode on Solaris:

[ODBC Data Sources]
TBC_MD=IBM DB2 ODBC DRIVER
TBC=IBM DB2 ODBC DRIVER

[TBC_MD]
Driver=/export/home/arbor7fp/sqllib/lib/libdb2_36.so
Description=Sample DB2 ODBC Database

[TBC]
Driver=/export/home/arbor7fp/sqllib/lib/libdb2_36.so
Description=Sample DB2 ODBC Database

[ODBC]
Trace=0
TraceFile=odbctrace.out
InstallDir=/export/home/arbor7fp/sqllib/lib

Configuring data sources on Windows systems

To configure a relational data source with ODBC Administrator, complete the following steps:

1. On the Windows desktop, select Start > Settings > Control Panel to open the Control Panel window.
2. In the Control Panel window, perform one of the following steps:
• On Windows NT, double-click the ODBC icon to open the ODBC Data Source Administrator dialog box.
• On Windows 2000, double-click the Administrative Tools icon, and then double-click the Data Sources (ODBC) icon to open the ODBC Data Source Administrator dialog box.
3. In the ODBC Data Source Administrator dialog box, click the System DSN tab.
4. Click Add to open the Create New Data Source dialog box.
5. In the driver list box of the Create New Data Source dialog box of ODBC Administrator, select an appropriate driver-for example, IBM DB2 ODBC Driver-and click Finish to open the ODBC IBMDB2 Driver - Add dialog box.
6. In the ODBC IBM DB2 Driver - Add dialog box Database alias drop-down list, select the name of the database for your relational source data (for example, TBC in the sample application). The name of the selected database is automatically displayed in the Data Source Name text box.
7. If you want to change the name of the data source, select the name displayed in the Data Source Name text box, press Enter, and type the name you want to use for the data source.
8. In the Description text box, type an optional description that indicates how you use this driver and click Add. For example, type the following words to describe the My Business database:Customers, products, markets You might type the following words to describe the sample application database: Sample relational data source The descriptions help to identify the available data sources for your selection when you connect from Hyperion Integration Server Desktop.
9. Click OK to return to the ODBC Data Source Administrator dialog box. The data source name you entered and the driver you mapped to it are displayed in the System Data Sources list box on the System DSN tab.

To edit configuration information for a data source:

1. Select the data source name and click Configure to open the ODBC IBM DB2 - Add dialog box.
2. Correct any information you want to change.
3. Click OK twice to exit.

Configuring the OLAP metadata catalog on Windows systems

Note: This example creates a DB2 data source. Dialog boxes for other RDBMSs will differ.

To create a data source for the OLAP Metadata Catalog, complete the following steps:

1. On the desktop, select Start > Settings > Control Panel to open the Control Panel window.
2. In the Control Panel window, perform one of the following steps:
• On Windows NT, double-click the ODBC icon to open the ODBC Data Source Administrator dialog box.
• On Windows 2000, double-click the Administrative Tools icon, and then double-click the Data Sources (ODBC) icon to open the ODBC Data Source Administrator dialog box.
3. In the ODBC Data Source Administrator dialog box, click the System DSN tab.
4. Click Add to open the Create New Data Source dialog box.
5. In the Create New Data Source dialog box of ODBC Administrator, select an appropriate driver-for example, IBM DB2 Driver-in the list box, and click Finish to open the ODBC IBM DB2 Driver - Add dialog box.
6. In the Database alias drop-down list, select the name of the database for your OLAP Metadata Catalog  (for example, TBC_MD in the sample application).  The name of the selected database is automatically displayed in the Data Source Name text box.
7. If you want to change the name of the data source, select the name displayed in the Data Source Name text box, type a new name to indicate how you use this driver, and click Add.  For example, you might type the following name to indicate that you are using the driver to connect to the first OLAP Metadata Catalog:  OLAP Catalog #1   You would type the following name to indicate that you are connecting to the sample application OLAP Metadata Catalog database: TBC_MD

 
8. In the Description text box, enter a description that indicates how you use this driver. For example, you might type the following words to describe the OLAP Metadata Catalog: My first models and metaoutlines.  You might type the following words to describe the sample application OLAP Metadata Catalog database: Sample models and metaoutlines.  The descriptions help you to identify the catalog that you want to select when you connect to the OLAP Metadata Catalog from Hyperion Integration Server Desktop.

 
9. Click OK to return to the ODBC Data Source Administrator dialog box. The data source name you entered and the driver you mapped to it are displayed in the System Data Sources list box on the System DSN tab.

1. Click Configure to open the ODBC IBM DB2 - Add dialog box.
2. Correct any information you want to change.
3. Click OK twice to exit.

After you configure a data source

Note: The SQL Server ODBC driver may time out during a call to an SQL Server database. Try again when the database is not busy. Increasing the driver time-out period may avoid this problem. For more information, see the ODBC documentation for the driver you are using.

For more information on ODBC connection problems and solutions, see the DB2 OLAP Integration Server OLAP System Administrator’s Guide.

Migrating to OLAP Integration Server 7.1

Read the following topics carefully to assess migration issues that may affect your OLAP Integration Server installation. Note that the following tasks cannot be completed until after you have installed OLAP Integration Server:

• On UNIX systems, you cannot update environment variables until after the installation process has completed and the is.csh (or is.sh) files you need have been created .
• On all systems, you cannot migrate existing OLAP Metadata Catalogs until after the installation process has completed and the SQL scripts you need have been created; see Upgrading the OLAP Metadata Catalog for more information.

Preserving and existing ODBC driver

If you use the INTERSOLV (now MERANT) Version 3.10 or Version 3.11 ODBC drivers supplied with previous versions of Hyperion Integration Server, you might want to preserve the older drivers for compatibility with the other applications. In general, however, you should upgrade the ODBC drivers to the versions provided with the latest release of OLAP Integration Server.

DB2 OLAP Integration Server 7.1 Fixpak 2 and later supports MERANT Version 3.6 ODBC drivers; it does not operate with MERANT Version 3.10 or Version 3.11 ODBC drivers.

Install the new MERANT Version 3.6 ODBC drivers and preserve the older drivers by installing OLAP Integration Server to a new location. Be sure that you do not update the ODBC register settings when prompted to do so by the installation program. You can continue to use the previous ODBC definitions.

Choosing an installation directory

Verifying path variable settings

• If you install the OLAP Integration Server on a computer that runs DB2 OLAP Server, verify that the ARBORPATH environment variable is set to the main directory for DB2 OLAP Server.
• If you install the OLAP Integration Server on a computer that is not running DB2 OLAP Server, verify that the ARBORPATH environment variable is set as follows:
• For Windows systems: ARBORPATH=ISHOME\esslib
• For UNIX systems: ARBORPATH=$ISHOME
• For all upgrade scenarios, verify that the path environment variables are set as shown in the following table, after installation:

Table Notes:

1. %ISHOME% represents the main installation directory of OLAP Integration Server on Windows systems. $ISHOME represents the main installation directory of OLAP Integration Server on UNIX systems.
2. For Windows systems, check to make sure that the setup program did not add duplicate path entries for the OLAP Integration Server directories.
3. If you are using MERANT (formerly INTERSOLV) ODBC drivers, place the MERANT library at the beginning of the library path; for example:   LIBPATH=$ISHOME/odbc/merant36/lib: $LIBPATH:$ISHOME/esslib

Migrating existing OLAP metadata catalogs

You cannot upgrade an existing OLAP Metadata Catalog until after you have completed the installation process.  The Hyperion Integration Server setup program installs the scripts that you need for the upgrade.

CAUTION:  If you have installed the sample application from Hyperion Integration Server, you should back up your existing sample database, OLAP Metadata Catalog, and the OLAP models and metaoutlines stored in the catalog. You can then upgrade your existing catalog to be compatible with the current release of the software. You cannot, however, store new sample OLAP models and metaoutlines in your previous catalog.

To upgrade an existing OLAP Metadata Catalog, perform the following tasks:

• Complete the upgrade steps for the existing OLAP Metadata Catalog described in Upgrading the OLAP Metadata Catalog.
• When connecting to the relational database, make sure to use the same user name and password that you used when you created the original OLAP Metadata Catalog. This procedure adds new tables to the OLAP Metadata Catalog without disturbing the existing information.

Upgrading the OLAP metadata catalog

Upgrade the tables of an OLAP Metadata Catalog with the same utility program you normally use to create tables running SQL scripts. The SQL scripts to upgrade tables for the OLAP Metadata Catalog are in the ocscript directory where you installed OLAP Integration Server. The upgrade scripts are named ocdatabase_name_upgrd20.sql and are listed the following table, along with the utility programs with which they have been tested.
 

Database DBMS	SQL Script	Utility Program
DB2	ocdb2.sql ocdrop_db2.sql ocdb2_upgrd20.sql	DB2 Command Center, or: >DB2 -tvf
Oracle	ocoracle.sql ocdrop_oracle.sql ocoracle_upgrd20.sql	SQL*Plus
MS SQL Server	ocsqlsrv.sql ocdrop_sqlsrv.sql ocsqlsrv_upgrd20.sql	ISQL (MS SQL Server 6.5)  Query Analyzer (MS SQL Server 7.0)

To upgrade tables for the OLAP Metadata Catalog database, perform the following tasks:

1. Start the utility program.
2. Connect to the database you created for the OLAP Metadata Catalog as the user who created the original OLAP Metadata Catalog tables.
3. Open the appropriate SQL script file in the ocscript directory.
4. Run the SQL script to upgrade the tables. On SQL Server, you receive a message that you did not create data or rows. This message is normal because you created only tables and columns.
5. Verify that you have created the additional OLAP Metadata Catalog tables.  For example, type the following command:     SELECT * FROM OM_DESCRIPTION      or start the RDBMS and verify that the OLAP Metadata Catalog has the new tables.
6. Close the utility program.

Connecting OIS to Oracle on Solaris

To test whether the ODBC driver loaded successfully, run the $ISHOME/bin/ivtestlib command followed by the path to the ODBC driver.

1. In Excel XP, Select the Tools menu.
2. Click Add-Ins.
3. Click the Browse button.
4. In the Look-in field, select the essexcln.xll file and save your selection.

Changes in this FixPak

DB2 OLAP Server Miner combines OLAP and data mining technologies

The OLAP Miner client component includes a graphical user interface that guides the user through the process of setting up a deviation detection definition. This involves selecting:

• A source cube and the number of deviations to report
• Individual members and member combinations from dimensions to fully define the subcube to be mined, for example, "actual sales for all time" and "all products in the eastern region."

• Server component: Microsoft Windows NT 4.0, Windows 2000, and AIX 4.3.3
• Client component: Microsoft Windows 95, Windows 98, Windows ME, Windows NT 4.0, and Windows 2000

IBM DB2 OLAP Server Miner is licensed for use only with IBM DB2 OLAP Server.

DB2 OLAP Integration Server now upgraded to Essbase Integration Services 6.1

• New client console with dynamic Intelligent Help window
• Intelligent Help
• Load optimization
• Sort on alternate column
• Loading of Essbase properties from database columns
• XML import/export
• Improved access to the server log file
• New sample application
• UNIX ODBC configuration utility

New client console with dynamic Intelligent Help window

• Creates or updates an OLAP Metadata Catalog and, optionally, the The Beverage Company (TBC) sample application provided with Essbase Integration Services
• Automatically detects the OLAP model fact table, dimensions, and hierarchies to create an OLAP model
• Automatically detects dimensions and hierarchies in an OLAP model to create a basic metaoutline

OLAP metadata catalog and sample application creation

Automatic detection of fact table and dimensions

Automatic detection of hierarchies

Intelligent Help

• Fact
• Dimensions
• Table & Column Properties
• Hierarchies
• Finish

• The left frame lists the major tasks to be performed for each of the process groups.
• The right frame contains detailed, numbered procedures for performing the tasks itemized in the left frame. Links to automatic-detection functions and to user interface dialog boxes are provided in this frame, where appropriate.

Load optimization

Member load options

• Use Distinct Clause: If the leaf node of a given dimension should be distinct, you can choose to add the Distinct clause to the Select statement. During a member load, only the distinct combination of columns in the Select statement is returned, resulting in a quicker member load. You might want to use this option, for example, if you have created a Time dimension from the fact table.
• Use Outer Join: Use of this feature enables you to view all columns in your Essbase database, whether or not the columns between two joined tables are identical.

• Allow Duplicate Shared Members: Use of this feature enables the same member to be shared multiple times under the same parent, resulting in faster creation of the Hyperion Essbase outline.

Data load options

• Remove Extra Joins: This feature removes extra joins whether or not a surrogate key is used for a data load. If a surrogate key is used in a join, the surrogate key is loaded into Essbase as an alias, and the join is eliminated in the data load.
• Use User-defined SQL: This option enables you to use an edited version of the standard SQL generated by Essbase Integration Server.

Sort on alternate column

Loading of Essbase properties from database columns

• Two-pass calculation
• Data storage attribute
• Time balance
• Skip type
• Variance reporting
• Formulas

XML import/export

• Data Type Definition (DTD): This part describes the allowable structure of XML documents. A DTD defines the major elements within a document, the child elements, and related attributes. It can constrain the pieces of data that occur in a document, the hierarchy of the data that it includes, and the number of times each piece of data occurs. Essbase Integration Services provides a predefined DTD to ensure that you use the same data format when you create XML documents.
• XML documents: This part specifies how to use the tagged markup to indicate the meaning of data, somewhat like a card catalog. In Essbase Integration Services, the data in an XML document describes the dimensions, members, hierarchies, and settings in OLAP models and metaoutlines. This information is stored in tables in the OLAP Metadata Catalog.

Improved access to the server log file

• During a member or data load, or at any other time, you can select Tools > View Log File to view the Server log file.
• At the completion of a member or data load, a View Log File option button is enabled that you can select to view the Server log file.

New sample application

• Sample OLAP Metadata Catalog (TBC_MD)
• Sample data source (TBC)
• Sample OLAP model (TBC Model) and sample OLAP metaoutline (TBC Metaoutline)

UNIX ODBC configuration utility

• List:Use this option to list all defined DSNs for the OLAP Metadata Catalog and source databases and verify that they are correct.
• Add: Use this option to add a DSN for the OLAP Metadata Catalog and source databases.
• Delete: Use this option to delete a DSN for the OLAP Metadata Catalog and source databases.
• Test: Use this option to test that the ODBC connections that you created are valid.

FixPak 6 and later introduces a new OLAP component called DB2 OLAP Server Miner.

FixPak 5 and later fixes defects listed in the Problem Summary.  FixPak 5 does not introduce any new function.

FixPak 4 and later upgrades DB2 OLAP Server to Essbase 6.1, and adds the following features and changes to DB2 OLAP Server V7.1:
 

• Custom-defined macros enable you to combine existing calculator functions into a single new function called a macro.
• Custom-defined functions enable you to use your own customized calculator functions within the Essbase calculator framework. These custom-defined functions must be written in the Java^TMprogramming language and are called by the Essbase calculator framework as external functions.

The Java runtime environment included this FixPak is not set up for general use by other Java applications on your system.  This FixPak does not define a path to the Java JRE in either your system environment variables or user environment variables; the JRE will not interfere with other Java environments already on your system.

New Calculator functions:
 

Member Set Functions:

• The @IRDESCENDENTS function returns all descendants of the specified member (optionally up to the specified generation or level), including the specified member and the descendants of shared members.
• The @RDESCENDENTS function returns all descendants of the specified member (optionally up to the specified generation or level), including descendants of shared members, but not the specified member.
• Given a character string, the @MEMBER function returns the member with the name specified by that character string.

Mathematical Functions:

• The @EXP function returns the value of e(the base of natural logarithms) raised to the power of the specified expression.
• The @LN function returns the natural logarithm of a specified expression.
• The @LOG function returns the logarithm to a specified base of a specified expression.
• The @LOG10 function returns the base-10 logarithm of a specified expression.
• The @MAXS function returns the maximum value among the expressions in the specified member list, with the ability to skip zero and #MISSING values, or skip zero or #MISSING values.
• The @MINS function returns the minimum value among the expressions in the specified member list, with the ability to skip zero and #MISSING values, or skip zero or #MISSINGvalues.

• Range and Financial Functions
• The @MAXSRANGE function returns the maximum value of a member across a range of members, with the ability to skip zero and #MISSING values, or skip zero or #MISSING values.
• The @MINSRANGE function returns the minimum value of a member across a range of members, with the ability to skip zero and #MISSING values, or skip zero or #MISSING values.
• Relationship Functions
• The @ATTRIBUTEBVAL function returns the value (TRUE or FALSE) of the attribute from the specified Boolean attribute dimension associated with the current member.
• The @ATTRIBUTESVAL function returns the text value of the attribute from the specified text attribute dimension associated with the current member.
• String Functions
• The @CONCATENATE function returns a character string that is the result of appending a member name or specified character string to another member name or character string.
• The @SUBSTRING function returns a substring of characters from another character string or from a member name.
• Calculation Method Function
• To help maximize performance, the @CALCMODE function enables you to override the execution mode chosen by Hyperion Essbase for a formula. For example, you can use this function to change the execution of sparse member formulas that run more slowly in top-down mode to run in a faster bottom-up mode. You can also use @CALCMODE to change the execution of formulas that calculate correctly without cell mode to run in the faster block mode.

• Provides an intuitive, language interface to the DB2 OLAP Server, enabling programmatic management of Essbase applications without a prerequisite knowledge of C, Visual Basic, or the Essbase API.
• Includes the MaxL Command Shell, which can be used interactively or for running scripts. The MaxL Command Shell includes command-line argument processing, environment variable processing, nesting of MaxL scripts, and shell escapes. These features offer the flexibility needed to create a highly automated OLAP production environment.
• Includes an optional Essbase Perl Module (Essbase.pm), which extends the power of MaxL by enabling Perl programmers to embed MaxL queries in Perl scripts.

• EXPORT--Sends the data values of a database to an ASCII text file. Updated to include a format option setting to allow export of data in column or non-column format.
• GETPERFSTATS--Added performance statistics to the report to help users analyze the effectiveness of their dynamic calculator cache configuration settings.
• GETVERSION--Displays the patch number in addition to the version number.

• AGENTLOGMESSAGELEVEL--Enables you to specify the level of messages written to the Agent Event Log.
• LOGMESSAGELEVEL--Enables an administrator to specify the level of messages written to the Application Event Log.
• DYNCALCCACHEMAXSIZE--Specifies the maximum size Hyperion Essbase can allocate to each dynamic calculator cache on the server.
• DYNCALCCACHEONLY--For situations when the dynamic calculator cache has no more room, this setting specifies whether or not Hyperion Essbase may perform Dynamic Calc calculations in memory outside the dynamic calculator cache.
• DYNCALCCACHEWAITFORBLK--Specifies whether Hyperion Essbase waits until space becomes available in the dynamic calculator cache or immediately writes and calculates the data blocks in memory outside the dynamic calculator cache.
• DYNCALCCACHEBLKTIMEOUT--Specifies how long Hyperion Essbase is to wait for available space in the dynamic calculator cache.
• DYNCALCCACHEBLKRELEASE--Specifies whether Hyperion Essbase writes and calculates the blocks immediately outside the dynamic calculator cache or uses space in the dynamic calculator cache that it makes available by swapping out blocks and temporarily compressing them in a dynamic calculator cache compressed-block buffer.
• DYNCALCCACHECOMPRBLKBUFSIZE--Specifies the size of the dynamic calculator cache compressed-block buffer.
• EXPORTTHREADS--Enables the user to set the number of export threads that can be used to export data.
• JVMMODULELOCATION--Enables the user to designate a specific Java Virtual Machine library to be used by Hyperion Essbase.

FixPak 3 and later fixes defects listed in the Problem Summary. This FixPak does not introduce any new function.

FixPak 2 and later fixes defects listed in the Problem Summary. This FixPak does not introduce any new function.

FixPak 1 and later fixes defects listed in the Problem Summary. This FixPak does not introduce any new function.

Additional documentation

Updated books

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

In FixPak 11 and later:  The following updates are applied to the documentation:

TEMP or TMP variable must point to valid directory

Your TEMP or TMP environment variable must point to a valid directory location (a location that exists).  Otherwise DB2 OLAP Server might have trouble creating temporary files.

Change in permissions to update outline during data load/dimension build

Prior to FixPak 11 (Essbase Release 6.2.4), a user with only Calculate permission for a database could perform a dimension build (update outline) on the database using Application Manager. This problem has been fixed so that DB2 OLAP Server now ensures that the user has update access to the outline before allowing an Update Outline during a data load/dimension build. This fix may change the behavior for some users. If a user with Calculate permission used to be able to modify the outline prior to doing a data load/dimension build, this action will now be prohibited.

In FixPak 10 and later:  The following updates are applied to the documentation:

The Release Notes for FixPak 9 and earlier FixPaks incorrectly state that DB2 OLAP Server 7.1 supports AIX 4.3.3 or later.  On AIX, DB2 OLAP Server 7.1 only supports AIX 4.3.3; AIX 5L is not supported. The OLAP Setup and User's Guide also contains this error.

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

Additional information about the MaxL create partition statement

• For all partition types, if area aliases are used in a mapping, the area alias must be associated with the target, not the source.
• The direction of the mapped clause must go from source to target.

Multiple mappings are allowed, provided they are separated by whitespace. Mapped clauses should not be separated by commas, as is erroneously shown in the syntax documentation for the create partition statement.

In FixPak 9 and later:  The following updates were applied to the documentation:

Negative values for DLTHREADSPREPARE and DLTHREADSWRITE essbase.cfg settings.  If the number of threads in the DLTHREADSPREPARE and DLTHREADSWRITE essbase.cfg settings are specified as negative values, Essbase uses the maximum value, 16.

DISKVOLUMES Still Available.  You can still use the configuration setting DISKVOLUMES, in the configuration file essbase.cfg, instead of the database-specific settings available via Application Manager. Use DISKVOLUMES only if you need backward compatibility with earlier releases, or if you are setting up a large number of databases with the same DISKVOLUMES value at the same time.

Sample Application Versus Example Application.  A section of the Essbase Database Administrator's Guide uses an example application called TCC, The Car Company.  This is not a sample application supplied with the software but is an example used to illustrate how you can quickly create your own first application. The sample application supplied with Essbase is TBC, The Beverage Company.

Cross-Dimensional Operator Works with Member Set Functions.  Expressions such as ("1998":"2001" -> @Levmbrs (Year, 0)), using the cross-dimensional operator with a member set should now function. This operator is associative (x -> y) -> z=x -> (y -> z), but not commutative because x -> y = y -> x is a set, but the order of elements is different. (21505)

CLEARDATA Does Not Work in an IF Block.  The calculation script CLEARDATA command does not work in an IF block. This is not documented. (20949)

Moving Members and Attribute Associations.  In an outline, moving base members with attribute associations now keeps the attribute associations.  The documentation incorrectly states that it does not.

DB2 OLAP Server Does not Generate Trace Files.  DB2 OLAP Server does not generate trace files, but some documentation still indicates that it does. (014112)

Unclear Spreadsheet Example.  The example in Spreadsheet Add-In User's Guide for Excel, chapter 3, pages 3-28 through 3-31, is unclear.  It will be improved for next release. (25511)

Calculation Results Difference.  Small differences in the precision of cell values may occur between calculations run on different platforms, due to operating system math library differences.(007598)

Null processing in Dimension Build.  Documentation should state that in the dimension building setting for a Product dimension, you must select the Allow moves check box, or null processing with a generation reference will fail. (020022)

EssListCalcFunctions() Requires Supervisor Privilege And Database Access.  The documentation is missing information about the privileges required to use EssListCalcFunctions(). You must have supervisor privilege (usually granted to the administrator), and you must have database access privileges to receive this list, or an error may occur. This means, for example, if you run a program with EssListCalcFunctions() when logged in as a user who does not have both supervisor privilege and access to the database, an error will occur.

Reserved words that Require 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.

Missing Configuration Parameter for Data Load Errors.  The documentation does not include information about NOMSGLOGGINGONDATAERRORLIMIT, a configuration setting you can add to your server essbase.cfg file to prevent data load errors from being written to the application event log file after the limit described by the value of DATAERRORLIMIT is reached.  Add this item to your server configuration file essbase.cfg:

NOMSGLOGGINGONDATAERRORLIMIT TRUE

API Client Message Change.  Client messages are messages sent to the user-defined Callback function, passed to DB2 OLAP Server in EssInit. Previous to FixPak 8, if a message contained NLS characters (non-English characters, such as accented characters), DB2 OLAP Server provided them in OEM (DOS) format. In FixPak 8, the client messages are completely in character (Windows) format, to avoid the misinterpretation of certain characters.  This only affects languages other than English.

API Error for ESSG_INIT_T.  ulMaxRows has a limit of 65535 rows, and ulMaxColumns has a limit of 256 columns. The API documentation for ESSG_INIT_T is currently incorrect on these two issues (18435).

Missing Grid Expansion Configuration Settings  (14987, 18987, 20709, 22585).  If Essbase returns incorrect results from a calculation using both two-pass calculation dynamic members and you are aggregating across partitions, enter this configuration setting in your server essbase.cfg file, then restart OLAP Server: GRIDEXPANSION FALSE.   The default is TRUE.
If Spreadsheet Add-In retrievals involving partitions generate many instances of this message: "grid expansion enabled for this query," you can turn off the messages by adding this entry to your server configuration file essbase.cfg, and then restarting OLAP Server: GRIDEXPANSIONMESSAGES OFF.   The default is "ON."

Missing Parameter for Functions @NEXTS, @PRIORS.  Both these functions accept these parameters:

SKIPNONE | SKIPMISSING | SKIPZERO | SKIPBOTH, mbrName [,n, rangeList])

Functions to Help Performance on Dense Ranges.  Consider using these functions instead of prior and next if your calculation operates on dense ranges - i.e., Both crossmbr and range are along dense dimension:

@SHIFTPLUS(Mbr, CrossMbr, ShiftAmt, Range)

@SHIFTMINUS(Mbr, CrossMbr, ShiftAmt, Range)

Incorrect essbase.cfg MAXLOGINS.  The configuration setting MAXLOGINS is incorrectly listed as MAXLOGIN in the Technical Reference and Database Administrator's Guide.

In FixPak 8 and later:  The following books for DB2 OLAP Server have been updated to Essbase 6.2 and Essbase Intetration Services 6.2 and are shipped in this FixPak.

New Error Messages Document:

FixPak 8 provides an HTML document that describes what to do when you receive certain error messages.  Each documented error message includes the message number, message text, potential problems that caused the error, and potential solutions. For Release 6.2, messages involve data loading, calculation, data cache, networking, and the agent. In future releases, more functional areas will be explained.

Database Administrator’s Guide improvement:  FixPak 8 reorganizes the Database Administrator's Guide into three volumes to provide better access to the information. The updated version is available in English only.

• Volume I includes an introduction to the OLAP Server and provides the information that you need to begin planning and designing your applications and databases.
• Volume II contains information about loading, calculation, and retrieval.
• Volume III contains information about maintaining and automating your OLAP Server applications, and optimizing your OLAP Server for performance or resource use. This volume also contains the index and glossary for all three volumes.

In FixPak 7 and later:  The following books for DB2 OLAP Server have been updated to the Hyperion Essbase Integration Services 6.1 level and are shipped in this FixPak:

• OIS System Administration Guide -- updated to the Essbase Integration Services 6.1 level.
• OIS Model User's Guide -- updated to the Essbase Integration Services 6.1 level.
• OIS Metaoutline User's Guide -- updated to the Essbase Integration Services 6.1 level.

Also, FixPak 7 withdraws the Business Intelligence Tutorial because the interface it describes has been withdrawn from Essbase Integration Services 6.1.  DB2 OLAP Integration Server now offers Intelligent Help instead.

In FixPak 6 and later:  A new book, the OLAP Miner User's Guide, is provided to describe DB2 OLAP Server Miner, a new feature of DB2 OLAP Server.

In FixPak 4 and later:  The following books for DB2 OLAP Server have been updated to the Hyperion Essbase 6.1 level and are shipped in this FixPak:

• OLAP MaxL User's Guide -- this book is new and documents the MaxL administration language introduced in FixPak 4.
• OLAP Technical Reference -- updated with MaxL.
• Business Intelligence Tutorial -- updated and translated into supported languages.  The first part of the tutorial concerns the Data Warehouse component of DB2 Universal Database 7.2, and you need the Version 7.2 level of DB2 Universal Database to run those lessons.  You can run the OLAP lessons using Version 7.1 of DB2.

• OLAP Integration Server Administrator's Guide
• OLAP Integration Server Model User's Guide
• OLAP Integration Server Metaoutline User's Guide

Excel XP

Change in Solaris Command Line

cc sampapp.c -I$ARBORPATH/api/include -L$ARBORPATH/api/lib -D_REENTRANT -o esstest.out 
-lm -ldl -lposix4 -lsocket -lnsl -lpthread -lglobalc -lessotl -lessglob -lessapi  
-lessnet -lessshr -lessutl -lesssd -lesssec

Change in Persistence of Allow Settings

• If an administrator disables connections, all users with lower privileges than Application Designer for that application are prevented from making connections to its databases which would require the databases to be started. The effect of disabling connections lasts until (1) the application is stopped and restarted or (2) the administrator re-enables connections--whichever comes first.
• If an administrator disables commands, all users (including Supervisors, as a safety mechanism) are prevented from making any requests to databases in the application, including non-data-specific requests, such as viewing database information or changing database settings. The setting takes effect immediately and affects users who are currently logged in, as well as users who log in later during the administrator's session. The effect of disabling commands lasts until (1) the administrator who disabled commands logs out, (2) the application is stopped and restarted, or (3) the administrator re-enables commands--whichever comes first.
• If an administrator disables updates, all users (including Supervisors, as a safety mechanism) are prevented from making any requests to databases in the application that would have an effect on the data, such as making outline or data modifications. The setting takes effect immediately and affects users who are currently logged in, as well as users who log in later during the administrator's session. The effect of disabling updates lasts until (1) the administrator who disabled updates logs out, (2) the application is stopped and restarted, or (3) the administrator re-enables updates--whichever comes first.

Port settings and application limits

Specifically, the number of available ports is equal to:

ServerPortEnd - ServerPortBegin
------------------------------- + 1
PortInc x (ports needed per app)
 

Prior to Release 6.2, the number of ports needed per application was 1. In Release 6.2, that number was increased to (1 + AgtSvrConnections), where AgtSvrConnections is the number of connection channels between the agent and the application server, and defaults to 1. If you need more than 100 ports, then use appropriate values for these settings.

Root.sh information

Solaris and HP-UX SQL interface users should not run the file root.sh unless they want to turn on the "Cache Memory Locking" feature. Furthermore, if they want to use Cache Memory Locking, they need to have root privileges to run root.sh.

HP-UX settings

Agent log messages

   Last Login on Fri Apr 20 21:52:16 2001

Now the agent log message displays the following Date/Time format:

   Last Login on Friday, April 20, 2001 10:57:29 AM

However, all other date and time formats remain the same.

Buffered I/O Default

MaxL installation update

New configuration file settings (essbase.cfg)

CalcLimitFormulaRecursion

SQLFetchErrorPopup TRUE | FALSE

CalcReuseDynCalcBlocks

Global CALCMODE Setting

Rather than having to specify @CALCMODE(BLOCK) or @CALCMODE(BOTTOMUP)in each of your formulas, you can now set these modes once, globally. The global scope may be for all applications, a specific application, or a specific database. In your Essbase.cfg file, you can specify CALCMODE in any of the following ways:

CALCMODE (BLOCK | BOTTOMUP)

CALCMODE <App> (BLOCK | BOTTOMUP)

CALCMODE <App> <Db> (BLOCK | BOTTOMUP)

Obsolete Configuration File Settings  (essbase.cfg)

CalcOptCalcHashTbl

Known problems and limitations

Extra step when migrating from Fix pack 11 to Version 8.1. (N/A)
If you apply this Fix pack and then migrate to DB2 OLAP Server 8.1, you might have to re-configure the Spreadsheet Add-ins manually. Select Start -> Programs -> DB2 OLAP Server 7.1 -> Modify Component or License, and select the option for adding the runtime client.  You need to reboot to complete the step.  

The server rejects: @AVG("SKIP_Param", expList) the following client is out of synchronization. (19340)
The server does not accept quotation marks around the following skip parameters: SKIPNONE, SKIPMISSING, SKIPZERO, and SKIPBOTH. The Calc Script Editor and client outline verification will not detect this error. When a calculation is run with this syntax error, the application log generates the following error message: "Error parsing formula for member [] (line <no>): invalid skip instruction in function []." Note that the server validation will catch this error in the Formula Editor.

The Calc Script Editor does not generate an error message when reserved words are not quoted. (20343)
When validating a calculation script, the client may not generate an error message for the incorrect use of a non-quoted reserved word used for a dimension or member name.
Calculation script reserved words include calculation script commands, operators, report script commands, function names, and function arguments, in addition to such basic terms, as AND, BEGIN, MEMBER, FUNCTION, IF, THEN, and so on. For a list of these terms, see the Database Administrator's Guide. It is better not to use these reserved words as dimension names, member names, or aliases. If you do use them as names or aliases in calculation scripts, you must enclose them in quotation marks.

When the regular user logs out, the ESSCMD batch job is canceled by the supervisor console. (20434)
When running the nightly batch job, the application log appears and can be logged out by the console due to the following reasons:

• The Essbase script files are not locked.
• The user has no firewall connections.
• The user has read-only access.

Set Member Filter in the Essbase Query Designer (EQD) with MBCS displays broken character. (21012)
From within the Essbase Query Designer, attempting to create a member filter using multi-byte characters and an IME mode causes a data entry problem in both Excel and Essbase Query Designer.
Work around: Launch the Notepad (or any other text editor that accepts multi-byte input), enter the multi-byte text, copy, and paste the text into Essbase Query Designer. 

After reverting to direct I/O on HP-UX 11.0, DB2 OLAP Server applications may fail to load. (29017)
On HP-UX 11.0, DB2 OLAP Server applications may fail to load if you attempt to switch from direct to buffered I/O and then back to direct I/O.

Parallel export may fail when the path name contains a dot. (29604)
When the path name for a parallel export contains a dot ".", it may fail.

GetDbStats command (Esscmd) may crash the OLAP server during calculations or heavy usage. (32219)
A new essbase.cfg setting has been added to address problems with the GetDbStats command (Esscmd) crashing the OLAP server during calculations or heavy usage. If you are experiencing this problem, add the setting SamplingNumBlocks to the essbase.cfg configuration file and set it 1 to indicate the number of blocks for GetDbStats to sample. Accepted values are 1 - 100. We recommend 1 for this particular issue; however, setting to a larger number provides for better statistics.

Temporary Directory Path Issues.  (n/a)
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 /tmp directory. 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 DB2 OLAP Server functions may fail.

A new essbase.cfg setting has been added.  (n/a)
The new setting addresses problems with the GetDbStats command (Esscmd) crashing the OLAP server during calculations or heavy usage. If you are experiencing this problem, add the setting SamplingNumBlocks to the essbase.cfg configuration file and set it to 1 to indicate the number of blocks for GetDbStats to sample. Accepted values are 1 - 100. We recommend 1 for this particular issue; however, setting to a larger number provides for better statistics.

In DB2 OLAP Server Miner, the Linked Reporting Object functions do not work.  (n/a)
When you select either the 'Create LRO' or  'Delete LRO' options in OLAP Miner, an error message occurs.

Online HTML books might not display properly in Netscape Navigator.  (n/a)
When you use Netscape Navigator to display HTML books that are intended for a three-frame layout, Netscape might not load the book completely, displaying only one page of information and not displaying the table of contents in the navigation pane on the left. If this occurs, click the Reload button on the Netscape Navigator browser to display the book in three-frame format.

On AIX, a core dump or segment fault error during installation or use of DB2 OLAP Server is caused by inadequate memory. (n/a)
On AIX, if you get a core dump or a segment fault error when you install or use DB2 OLAP Server, then the memory allocated to DB2 OLAP Server on your AIX machine needs to be increased.  The default ulimit value on AIX is 1G, but DB2 OLAP Server files require 2G.   You can increase the memory by using the AIX command called ulimit.  For example, to increase the stack size, enter the following command:

ulimit -s unlimited

For more information about the ulimit command, see the AIX Commands Reference.

Starting in DB2 OLAP Server FixPak 4, the outline import/export function is no longer included in the Application Manager. (n/a)
The outline import/export function has been removed from the Application Manager from FixPak 4 (Hyperion Essbase 6.1 Patch 2).  This function continues to be available in the Spreadsheet Add-in.

On Windows, directory names greater than 8 characters cannot include spaces.  (n/a)
On Windows, when loading data from a directory, if the name of the directory includes spaces and is longer than 8 characters, an error occurs.   Either rename the directory to remove the spaces, or shorten the directory name to 8 characters or less.

Server Rejects: @AVG("SKIP_Param", expList) the Following Client Is out of Synchronization. (19340)
The server does not accept quotations marks around the following skip parameters: SKIPNONE, SKIPMISSING, SKIPZERO, SKIPBOTH. The Calc Script Editor and client outline verification will not detect this error. When a calculation is run with this syntax error, the application log has the following error message output:
Error parsing formula for member (line <no>): invalid skip instruction in function .
Note that the server validation will catch this error in the Formula Editor.

Calc Script Editor Does Not Generate an Error Message When Reserved Words Are Not Quoted. (20343)
When validating a calculation script, the client may not generate an error message for the incorrect usage of a non-quoted reserved word used for a dimension or member name.
Calculation script reserved words include calc script commands, operators, report script commands, function names, and function arguments in addition to the basic terms, such as AND, BEGIN, MEMBER, FUNCTION, IF, THEN, and so on. For a list of these terms, see the Hyperion Essbase Database Administrator's Guide. It is better not to use these reserved words as dimension names, member names, and aliases. If you do use them as names or aliases in calculation scripts, you must enclose them in quotation marks.

The ESSCMD Batch Job Is Canceled When Regular User Logs out by the Supervisor CONSOLE. (20434)
When running the nightly batch job, the application log appears and can be logged out via CONSOLE because the Essbase script files are not locked, the user has no firewall connections, and has read-only access to the Essbase script files.

In the Japanese Version, Header and Footer Strings that Are Set in Cascade Menu Item Are Preceded by Incorrect Characters. (21011)
With Japanese Hyperion Essbase Spreadsheet Add-in for Excel, header and footer strings that are set in the Cascade menu item are preceded by incorrect characters when printing and previewing.
Work around: Go into Print Preview > Setup to the Header/Footer tab and specify a custom header/footer that does not contain the incorrect characters.

Set Member Filter in Essbase Query Designer (EQD) Value with MBCS Displays Broken Character. (21012)
From within the Essbase Query Designer, attempting to create a member filter using multi-byte characters and an IME mode causes a data entry problem in both Excel and the Essbase Query Designer.
Work around: Launch the Notepad (or any other text editor that accepts multi-byte input), enter the multi-byte text, copy, and paste the text into the Essbase Query Designer.

If "Allow Application to Start" Setting Is Disabled When the ESSCMD, Call BEGINARCHIVE, Is Used, the Application and Database Cannot Restart. (21247)
If "Allow Application to Start" setting is disabled and a database is placed in the archive mode with ESSCMD, BEGINARCHIVE, after stopping the application, the application and database may not restart.

Installer overwrites UDF.Policy file (27367)
Essbase installation for both base product and patches replaces the udf.policy file, which is used in conjunction with Custom-Defined Functions. This file could have previously been updated by an Essbase administrator to give access to specific JAR files. Administrators who have updated the udf.policy file should backup their udf.policy file prior to installing Essbase and patches.

After reverting to direct I/O on HP-UX 11.0, Essbase applications may fail to load. (29017)
On HP-UX 11.0, Essbase applications may fail to load if you attempt to swich from direct to buffered I/O and then back to direct I/O.

Parallel export may fail when the path name contains a dot. (29604)
When the path name for a parallel export contains a dot ".", it may fail.

GetDbStats command (Esscmd) may crash the OLAP Server during calculations or heavy usage. (32219)
A new essbase.cfg setting has been added to address problems with the GetDbStats command (Esscmd) crashing the OLAP Server during calculations or heavy usage. If you are experiencing this problem, add the setting SamplingNumBlocks to the essbase.cfg configuration file and set it 1 to indicate the number of blocks for GetDbStats to sample. Accepted values are 1 - 100. We recommend 1 for this particular issue; however, setting to a larger number provides for better statistics.

----------- For OLAP Integration Server:

Workaround for creating OIS sample on Windows NT.  (IBM5514)
To create the OIS sample using the OIS Desktop on with Windows NT, set the TEMP and TMP environment variables as system environment variables rather than user environment variables.  Set both TEMP and TMP to C:\TEMP.

ODBCCONFIG utility sometimes fails to update oddb.ini file. (n/a)
Starting in FixPak 7, the odbcconfig utility sometimes does not fully update the odbc.ini file as expected.  To make sure the odbc driver and the path to the driver is correct, edit the odbc.ini file and update it if necessary.

In some cases, Essbase Integration Services displays Hyperion Essbase error numbers without the corresponding error message.  (10715)
WORKAROUND: View the message.txt file located in the ISHOME/esslib/bin directory or check the Essbase Integration  Services log file.

In the Metaoutline main window, if you select the toolbar to not display, the Filters toolbar and Filters icons are not displayed either. (10815)

Essbase Integration Services Release 6.1.0 software does not support Pass-through (Database Specific) transformations using SQL functions. (15131)
Specifying a built-in RDBMS function, such as Substring, or Left, causes Essbase Integration Server to generate invalid SQL.

Essbase Integration Services does not support Relational Database Management System (RDBMS) table and column names that have imbedded blanks.  (15454)
If Essbase Integration Services encounters blanks, it generates invalid SQL statements.

(Sybase databases) An incorrect error message is displayed when the user TBC does not exist in the Sybase database.  (23793)
The error message "user 3 does not exist" is displayed; the error message should read, "user TBC does not exist."

If you are using Excel and you drill down on Accounts, all the account members are highlighted as having an attached report even though you have selected only one member. (23923)

If you use tab characters to tell Essbase to use the same member name that appears in a previous record, the Essbase streaming data load does not provide the complete path of any rejected members.   (24705, 24706)
Essbase Integration Services cannot build a text file for loading rejected records.

Languages that use a comma as a decimal separator must run DB2 OLAP Server and DB2 OLAP Integration Server in the same language; for example, both products should be run in French. (25839)
Languages employing a decimal point do not have this problem.

If Essbase Integration Services 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, Essbase Integration Services cannot load the data to the parent member because the parent member is the dimension level member. In this case, Essbase Integration Services records an error in the log file.  WORKAROUND: Do not include NULLs at Generation 2.

If Oracle 8.0.x on Solaris or HP-UX fails due to the unresolved symbol, slpmprodstab, change directories to ishome/odbc/merant36/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.  The workaround is to start Essbase Integration Services in a directory that is in a file system that supports longer names.
 

Problem summary

The following problems are fixed in FixPak 11:

Drilling down in free form mode and retrieve with template returns corrupt error. 17190
In some localized versions of the Spreadsheet Add-in, a corrupt error message is displayed after drilling down on a member when free form mode and retrieve with template are enabled.

EsbOtlWriteOutline VB API call fails. 25557
The EsbOtlWriteOutline Visual Basic API call fails after renaming members that have multiple shared members.

Partition defined with Member Select and @WITHATTR fails validation. 26557
When Member Select is used to define a partition, and the partition definition contains the @WITHATTR function, validating the partition returns an error. This problem occurred because the parameter list returned from Member Select was misformed.

MaxL documentation unclear about Windows file-path formats. 27544
Please use the following guidelines when specifying Windows file locations to MaxL and MaxL Shell:

1. In cases where MaxL Shell commands accept file paths (for example, in the spool command), use single backslashes and enclose the entire file path in single quotation marks. For example,
   spool on to 'D:\output.txt'

2. In cases where MaxL statements accept file paths, use double backslashes to represent one backslash. This is necessary because MaxL treats a single backslash as an escape character. Also, enclose the entire file path in single quotation marks. For example,
   

   alter database Sample.Basic begin archive to file 'D:\\archive\\basic\\basic0311';

import database sample.basic data from data_file 'c:\\Hyperion\\Essbase\\app\\sample\\basic\\calcdat.txt' on error abort;

   To expand variables, add double quotation marks. For example,
   

   import database sample.basic data from data_file "'$ARBORPATH\\app\\sample\\basic\\calcdat.txt'" on error abort;

3. The use of backslash as an escape character enables the use of the characters ' $ \ in MaxL statements (though their acceptable use is governed by DB2 OLAP Server naming rules). For example,
   

   create user 'O\'Brian' identified by 'password';
   Result: User O'Brian is created.

MaxL command "alter application enable startup" fails. 27936
The MaxL command "alter application enable startup" fails to load the applications and returns an error.

Some data cells may not be copied when you use the DATACOPY calculation command. 40043
When you copy data using the DATACOPY calculation command, some data cells may fail to be copied.

Outline update with Japanese alias name creates rejected record file. 43386
When you update an outline that includes a member whose alias name consists of Japanese characters, a rejected record file is created but the outline is updated sucessfully.

Visual Basic API call EsbQueryDatabaseMembers() returns error on remote machine. 43431
When the DB2 OLAP Server Visual Basic API program is running on a remote machine, the VB API call EsbQueryDatabaseMembers() may return error 1042006. When the error occurs, the application log does not report the same error or any error.

Multiple LISTUSERS commands (ESSCMD) causes a memory leak in the Essbase Agent. 55210
Using the LISTUSERS command (ESSCMD) multiple times causes a memory leak in the Essbase Agent. The leak may be more evident with large numbers of users.

Essbase Agent appears to hang after abnormal disconnect. 55391
When a DB2 OLAP Server client is disconnected abnormally due to errors (such as network time-out), the Essbase Agent goes into an infinite loop and appears to be hanging.

Deleting a base attribute dimension from Excel Spreadsheet Add-in returns error. 55932
When you delete a base dimension from certain Excel Spreadsheet Add-in worksheets, and the attribute dimension that maps to that base dimension is present in the sheet, the application crashes and returns the error "Network Error[10054]: Cannot Receive Data."

EsbGetApplicationInfoEx() returns incorrect results about active connections. 55966
The VB API call EsbGetApplicationInfoEx() returns incorrect results about active connections to an application.

Saving an outline that contains a large formula may fail. 56549
In a partitioned database, when saving an outline that contains a large member formula exceeding 2KB, exception errors are returned.

Some report scripts may spike the CPU usage on the server machine to 100%. 56725
Running a query from a report script against the OLAP server spikes the CPU usage on the server machine to 100%.

Retrieval on spreadsheets containing generation/level name with no data returns error. 56736
When an input spreadsheet contains a generation/level name with no data present, a retrieval operation returns the error "Member is out of place" for valid spreadsheets.

Certain spreadsheet retrievals may crash the application. 56997
In the Spreadsheet Add-in, a retrieval may crash the application if the sheet contains Dynamic Time Series members and a dynamically calculated member with a formula containing the @XREF function.

In the Japanese version of DB2 OLAP Server V7.1 FixPak 8 ( Essbase 6.2.1) only, the Query Designer fails during launch. 57031
In the Japanese version of DB2 OLAP Server V7.1 at the FixPak 8 level, the Essbase Query Designer fails when you launch it from the Spreadsheet Add-in menu.

EssVCell function does not work the same in Office 97 and Office XP. 57058
The code for EssVCell when tested in Office 97 works fine and returns a valid value for the member intersection. The same code returns #VALUE when tested in Office XP. In this case #VALUE is in error.

Substitution variable enclosed in double quotation marks (" ") in a spreadsheet retrieval causes an unknown member name error. 57209
The same substitution variable is being used for a calc script and for a member formula. The calc script requires the member name to be enclosed in double quotation marks. When trying to use the same variable in a spreadsheet, an unknown member name error occurs.

Certain member formula calculations return incorrect results. 57252
A formula such as "@ISLEV(Time, 1)" returns incorrect results because Essbase expects a negative integer to indicate a level number (i.e., @ISLEV(Time, -1). This problem has been fixed so that @ISLEV accepts both positive and negative numbers.

Pivoting members in Japanese Essbase causes Excel exception. 57374
In Japanese Essbase on a Windows 98 Japanese OS, pivoting certain member combinations in the Spreadsheet Add-in causes an Excel exception.

The @ROUND function may produce different results in DB2 OLAP Server V1 (Essbase R5.x) than it does in Version 7 (R6.x). 57417
Calculations that use the @ROUND function may have different results in Version 7 than they had in Version 1.

Partition validation hangs on AIX. 57627
On AIX, attempting to validate a transparent partition that uses multiple sources to a single target causes the validation to hang.

A user with only Calculate permission can perform a dimension build through Application Manager. 58355
A user with only Calculate permission for a database can incorrectly perform a dimension build (update outline) on the database using Application Manager. This problem has been fixed so that DB2 OLAP Server now ensures that the user has update access to the outline before allowing an Update Outline during a data load. This fix may change the behavior for some users. See If a user with calc privilege used to be able to modify the outline prior to doing a data load from the dialog, this action will now be prohibited.

The following problems are fixed in FixPak 10.

You may not be able to print calc scripts or reports through the Application Manager on Windows 98. (13398)
Printing calc scripts or reports through the Application Manager on Windows 98 may fail.

Essbase may not allow users to edit partitions under certain conditions. (16882)
When a user (user_1) tries to edit a partition that is locked by another user (user_2), user_1 may continue to get an error message stating that the partition is locked even after user_2 logs out.

The <DUPLICATE Report Writer command may have incorrect results when you are running multiple reports. (19062)
When you run multiple report scripts, and one of the scripts uses the <DUPLICATE command, the output from subsequent scripts will appear as if they also use the <DUPLICATE command; so member names will be incorrectly repeated in the report output.

Restrictions with EssVSetSheetOption spreadsheet macro for certain options. (22028)
For spreadsheet macros, there are restrictions for Spreadsheet Option links between the "Use Both Member Names and Aliases for Row Dimensions" option and the Formula Preservation options. For example, with a macro, you cannot simultaneously select "Use Both Member Names and Aliases for Row Dimensions" and "Retain on Zooms". These restrictions have been removed so that the macros behave exactly like the Spreadsheet Add-in UI.

The @ISGEN function may fail when used in calculation scripts with the genName parameter. (22495)
When you use the @ISGEN function in a calculation script with the genName parameter (instead of genNum), the calculation may fail. The calculation script verifies, but when you run it on the server, it returns the error message: "Error compiling formula for member [memname] line 110: expected type [NUMBER} found [STRING] in function [@_D2LONG]."

Spreadsheet retrievals that contain Dynamic Time Series members may have incorrect results. (25048)
When a spreadsheet retrievals contain Dynamic Time Series members, the values retrieved for those members may be incorrect.

Replicating data from source to target may crash the target application if mappings are not complete. (25233, old id 29595)
In a replicated partition, replicating data from the source to the target may crash the target application if mappings are incomplete. The fix for this bug prevents the application crash, causes DB2 OLAP Server to ignore the unmapped block, and writes an error message to the target application log.

Dimension build may incorrectly tag some members dynamic calc. (26165)
Some members in a dimension build may be tagged dynamic calc even though the rules file is not set to tag them dynamic calc.

Dimension build fails if one field contains UDA. (26603)
Performing a dynamic dimension build fails if one field in the data source contains a user-defined attribute (UDA).

A dimension build that runs without errors in FixPaks 4 through 7 might crash the application in FixPaks 8 and 9. (27209)
A dimension build that creates an invalid outline runs without errors in DB2 OLAP Server 7.1 FixPaks 4 through 7 (Essbase 6.1) might crash the application in FixPaks 8 and 9 (Essbase 6.2). The fix for this problem is to ensure that Essbase validates the outline after it is build and before it is written to the server. In FixPak 10 (Essbase 6.2.3), a dimension build that creates an invalid outline will fail and will generate an error message, but it will not crash the application.

Memory leak when running multiple reports or retrievals. (27463, old 32440)
Running a batch of reports in an Excel VBA application uses a large amount of memory, and the memory is not released after the reports complete. To free the memory, the application must be shut down. The same problem may also occur when doing many manual retrievals in a spreadsheet.

Dimension build may hang when adding Dynamic Calc members. (27804)
On UNIX platforms, dimension builds that add dynamic calc members may hang

Calculation with @XREF returns memory message. (28167, old 33286)
Running a default calculation on a database that uses the @XREF function returns an "unable to allocate memory" message.

Data is incorrectly rounded when <ORDERBY command is present. (28882)
Running a report script that contains the <ORDERBY command incorrectly rounds data.

Spreadsheet retrievals from partitioned databases may be slow. (29102)
Spreadsheet retrievals from target databases in a transparent partition may be slow, even when all of the data in the spreadsheet lies outside the partitioned area.

Using the CLEARDATA calculator command may crash the application. (29193)
Running a calculation script with the CLEARDATA calculator command may crash the application under the following conditions:

• The CLEARDATA command is used with a shared member inside a FIX statement.
• The FIX statement references the same shared member.

FIX  ("Diet Cola")
     CLEARDATA "Diet Cola" ;
ENDFIX;

Cannot assign a Dynamic Calc member to a stored member in batch calculation. (30725)
Running a batch calculation that assigns a stored member the value of a Dynamic Calc upper level member returns the following warning:

"Regular member [] depends on dynamic-calc member []"

This can occur when the formula refers to a dense Dynamic Calc member in another block.

Data load is only able to process strings up to 32KB in length. (36324)
DB2 OLAP Server crashes if you attempt to perform a data load with strings longer than 32KB, contrary to what is stated in the documentation. An error message is now provided, and the data load aborts instead of crashing DB2 OLAP Server.

The OLAP server may crash if users retrieve data during a data load, cleardata operation, or calculation. (36779)
The OLAP server may generate network errors and then crash if users retrieve data during a data load, a cleardata, or a calulation.

Large report scripts that use the 'restrict' command may hang. (37037)
Running large report scripts that use the "Restrict" command may hang the application and may cause a performance degradation in other applications running on the same OLAP server.

Unlocking spreadsheet cells may take longer than expected. (43117)
When the OLAP server is running on HP-UX, unlocking spreadsheet cells may take longer than expected.

The EssConnect Macro may fail in the Lotus 123 Spreadsheet Add-in on Windows 98. (43125)
In the Lotus 123 Spreadsheet Add-in on Windows 98, the EssConnect Macro may fail and result in the following error: "123w caused an invalid page fault in module GLOBLC32.DLL"

Restructuring a database with a corrupt or missing .db file causes data loss. (43204)
If you restructure a database that has a corrupt or missing .db file, the .pag and .ind files may disappear.

An attribute query with two-pass and dynamic calc members may have incorrect results. (43262)
Certain spreadsheet retrievals that contain attributes, two-pass calc members, and dynamic calc members may have incorrect results.

EssCell function may fail when retrieving Dynamic Time Series (DTS) members from the target in a transparent partition. (43275)
Using the EssCell function to retrieve DTS members from the target in a transparent partition may fail if those members are part of the partitioned area.

A dimension build may truncate some member names. (43365)
Building an outline using a rules file may result in some truncated member names. The truncated member names have a ">" character at the end.

Retrievals from transparent partitions with attribute members may return incorrect data. (43403)
Spreadsheet retrievals from transparent partitions that include attribute members (in the spreadsheet) may have incorrect results.

Issuing a BEGINARCHIVE command when a user has locked blocks may cause the application to crash or hang. (43522)
If a user has locked blocks, issuing a BEGINARCHIVE command will fail and will return an error message, as expected. If the BEGINARCHIVE command is repeated, the application may hang or crash. The fix for this problem prevents repeated BEGINARCHIVE commands from causing the application to hang or crash.

Application crashes after running calcs and doing ad-hoc retrievals. (54976)
Running calculations on four source databases in a partition and then doing ad-hoc retrievals against those databases may crash the application.

Application crashes when running a calculation script that contains @XREF using FixPak 9. (55221)
Using DB2 OLAP Server 7.1 FixPak 9 (Essbase 6.2.2) or V8.1 FixPak 1 (Essbase 6.5.1), running a calculation script that contains the @XREF function crashes the application.

Performance degradation with FixPak 9 verses FixPak 7 spreadsheet retrievals. (55512)
After upgrading from FixPak 7 (Essbase 6.1.4 to 6.2.2), there is a significant performance degradation when querying a large attribute dimension.

Moving attribute members in a dimension build may fail. (55514)
Dimension builds that move attribute members may fail to move those members and the following error may be written to the err file: "Illegal data type for attribute member."

Calculations that involve top-down members and use FRMLBOTTOMUP ON may create blocks unexpectedly. (55773)
Calculations that involve top-down members and use the calculation command SET FRMLBOTTOMUP ON, or the Essbase.cfg setting CalcOptFrmlBottomUp TRUE, may create blocks unexpectedly, causing some calculation results to be incorrect.

With quicklogin enabled, Essbase does not update the security file every time you create an application and database. (55816)
When running with quicklogin enabled, DB2 OLAP Server does not update the security file every time you create an application and database. In the event of an abnormal shutdown, this can result in security information being lost.

Certain spreadsheet retrievals using the Lotus 123 Spreadsheet Add-in may be slow. (55839)
Large spreadsheet retrievals using the Lotus 123 Spreadsheet Add-in may take much longer than expected.

Dimension builds that add alias names with the Japanese character Hankaku kana may result in error messages being written to the rejected record file. (55843)
Even though you can successfully update outlines with alias names that contain the Japanese character Hankaku kana, error messages are written to the rejected record file.

A data load may crash the application if the user performing the operation does not have write access to some of the cells being loaded. (55962)
Loading data may crash the application if the user performing the data load does not have access to some of the cells in the data load.

Reports that use the <TOP command may crash the application. (56173)
Reports that use the <TOP Report Writer command and include dimension names with more than thirty characters may crash the application. The fix for this problem allows dimension names to be up to eighty characters long

MaxL does not allow a pair of partitions to be created that can be created using Application Manager. (56256)
In Application Manager, you can create two separate partitions between two databases, database A and database B. Database A is the source in one partition and database B is the source in the other partition. When you try to create the same configuration using MaxL, only one partition is created.

Running several reports concurrently on an AIX platform may take longer than expected. (56364)
On AIX platforms, running several report scripts concurrently may take much longer than expected.

Copying a database many times and then viewing application information may crash the application. (56404)
Copying a database 58 times and then selecting App > information in the application manager may crash the application

Parallel calculations that use the Calc TwoPass calculation command may crash the application. (56407, 28718)
Running a parallel calculation that uses the Calc TwoPass command may crash the application.

The following problems are fixed in FixPak 9.

Updating a database may take longer than expected when ssauditr is specified in the essbase.cfg file. 21819 (25402)
Locking and sending data from a spreadsheet may take longer than expected if the essbase.cfg file contains the entry ssauditr and the spreadsheet contains dynamically calculated cells.

Large calc scripts take a long time to start. 25016 (29321)
Large calc scripts may take a minute or longer from the time the calc script is executed until it begins calculating the database.

Dynamic calc members on the target of a transparent partition may not be calculated correctly. 25031 (29341)
Retrieving from the target of a transparent partition may give incorrect results when some of the target members are tagged as dynamic calc.

SQL fetch error does not generate Essbase error. 25036 (29346)
When a SQL fetch error occurs when loading data or building an outline through SQL Interface, neither Application Manager nor ESSCMD indicate that an error has occured, though the error is indicated in the application log. To enable the error-handling fix, place the following line in the essbase.cfg configuration file:  SQLFetchErrorPopup TRUE

Locking and sending data when Update Mode is selected may result in data being sent to the wrong cells. 25115 (29450)
In the Spreadsheet Add-in, selecting Update Mode (in Essbase > Options > Mode tab, under the Mode heading), and locking and sending data, may cause the data to be sent to the wrong members.

Outline Synchrozization may fail to update the currency category. 25143 (29842)
Changing the Currency Conversion from None (Use Ancestor) to Category on a member and trying to synchronize it through a transparent partition may not amend the currency category even though it recognizes that the outline is not synchronized.

Calculation on a transparent partition runs continually and creates a large number of empty data blocks. 25296 (29679)
Calculating the target database in a transparent partition takes an excessively long time and occupies a lot of disk space with empty data blocks.

In the Essbase Query Designer, the Find menu selection does not find shared members. 25412 (29826), 25356 (29757)
The Find menu selection in the Essbase Query Designer does not find shared members that fit the search criteria.

Entering a level or generation name fails in advanced interpretation retrieval mode. 25941 (30488)
Spreadsheet retrievals that use a level or generation name in the free form retrieval mode work, but those that use a level or generation name in the advanced interpretation retrieval mode fail and result in error messages.

Calc script using @MATCH with @SUBSTRING may cause the OLAP Server to crash 26095 (30689)
Using a calculation script that contains the @MATCH function with the @SUBSTRING function may cause the OLAP Server to crash. The following is an example of a calculation script that contains both these functions:

sales

(IF(@MATCH(MARKET, "@SUBSTRING(utah,0,1)*")==1)

sales=24;

ENDIF)

Results of spreadsheet retrievals may be incorrect if the retrieval includes members with the @XREF function. 26212 (30840)
Spreadsheet retrievals that include members with the @XREF function in member formulas may have incorrect results.

Some attribute retrievals may return incorrect results. 25612 [30069], 26447 (31148)
When a Two-Pass Calculation member formula contains another dynamic Two-Pass Calculation member, the attribute calculation may return incorrect results.

After a spreadsheet retrieval that uses the EssCell function, subsequent retrievals from different databases may fail. 26462 (31168)
Certain spreadsheet retrievals may fail if you complete a retrieval using a spreadsheet with the EssCell function, connect to a different database using a different worksheet in the same workbook, and then retrieve from the second database. At this point, the retrieval fails and Essbase displays error messages.

Numbers to the right of the decimal point may not be displayed in some retrievals. 26642, (31380), 32521 (27531)
When the regional setting is set to a language other than English, and the report is in free form mode (in the Spreadsheet Add-in, EQD, or Report Writer), numbers to the right of the decimal point may not be displayed.

Unable to load alias table using Esscmd. 26751 (31510)
Using the Esscmd LoadAlias to load an alias table may fail to load the alias table correctly resulting in some aliases being missing or truncated.

Drilling down on an attribute dimension may cause the OLAP server to hang. 26761 (31525), 26762, (31526), 26647, (31385)
Drilling down on certain attribute dimensions may cause the OLAP server to hang.

Certain retrievals may not return correct results. 26896 (31695), 26895 (31694), 25789 (30290), 25448 (29869)
Retrievals with Time Balance members may not return correct results if the report contains upper-level Time dimension members which are dynamically calculated and contain member formulas.

ESSLOGIN performance is slow. 26966 (31792)
The ESSLOGIN C API function is logging in users more slowly than expected.

Dimbuilds may fail if excessive sorting is required 27016 (31861)
Dimension builds sometimes fail on AIX 4.3.3 when a large number of items need to be sorted.

Calculations that aggregate missing values and use the CALC DIM or AGG commands may have incorrect results. 27090 (31954)
A calculation that has SET AGGMISSG ON and uses the CALC DIM or AGG command may fail to roll up some values.

The OLAP Server may crash when the disk volume partition size is set to Unlimited. 27092 (31954), 27094 (31958), 27092 (31956)
When the index of a database (ess0000x.ind) spans more than one volume and the disk volume partition size is set to Unlimited, the OLAP Server may crash.

Calculating the target database in a transparent partition may take much longer than expected. 27095 (31959)
A calculation on the target of a transparent partition may take much longer than expected if the calculation fixes on an area outside of the partition.

Printing from the Application Manager may fail if the printer name is long. 27147 (32033), 26884 (31676)
Printing with NetWare Distributed Printer Service may fail and may cause the Application Manager to crash if the printer name is long.

<LINK report command may result in an incorrect syntax error. 27170 (32059), 26023 (30591), 21888 (25494)
Report scripts that contain the <LINK command with nested parentheses may result in an incorrect syntax error.

The SET FRMLBOTTOMUP calculation command may give incorrect results. 27192 (32089)
Calculations that use the SET FRMLBOTTOMUP calculation command may have incorrect results.

Cutting and pasting members in the Outline Editor may result in lost data. 27254 (32180)
When you cut and paste members in the Outline Editor, the members are copied but the data associated with the members is not copied.

A spreadsheet retrieval that includes attribute dimensions may return incorrect results. 27480 (32457), 27498 (32479)
Certain spreadsheet retrievals that include multiple attribute dimensions and members that are ancestors of shared base members may return incorrect results.

A linked partition that is governed by filter access fails to link to the source database. 27485 (32463), 26871 (31656)
When you select View/Launch in the Linked Objects Browser to link to the source database in a linked partition that is governed by filter access, Essbase displays an error message and fails to make the link.

Some data cells may not be copied when you use the DATACOPY calculation command. 27486 (32464)
When you copy data using the DATACOPY calculation command, some data cells may fail to be copied.

The <ASYM report script command copies all data from the first column to all subsequent columns. 27493 (32473), 27384 (32346)
A report script that uses the <ASYM command may copy data from the first column into subsequent columns.

Currency conversion is taking longer than expected. 27530 (32519)
It may take longer than expected to convert currencies using the Currency Conversion module.

Certain spreadsheet retrievals that include a sparse member with @PRIOR and SKIPMISSING in a member formula may fail. 27568 (32567), 27769 (32830)
Spreadsheet retrievals may hang and it may be impossible to terminate them normally if they include sparse members that have @PRIOR and SKIPMISSING in member formulas.

The essbase.secure script (used for securing a password) causes the OLAP Server to incorrectly write an error message to the Essbase.log. 27662 (32692)
In response to the essbase.secure script, the OLAP Server generates the error message "Unknown application name -secure -ignored" to the Essbase.log.

A data load takes much more memory in 6.2.2 than it does in 6.1p3a. 27676 (32707)
Under certain conditions, data loads under 6.2.2 may use ten times more memory than they do under 6.1p3a.

Spreadsheet retrievals that contain unknown members in row headers may cause the Essbase application to crash. 27684 (32718), 27616 (32628)
If a spreadsheet retrieval contains an unknown member in a row header, Essbase may display the following error message: "You must have a row header in order to perform this retrieval" and the Essbase application may crash.

Calculation results under 6.2.2 may be different from those under 6.1p3a. 27760 (32820)
A calculation under 6.2.2 results in some missing values that are not missing when you run the same calculation under 6.1p3a.

A retrieval that requests a non-existent subset of data may cause the Essbase application to crash. 27767 (32828)
A retrieval that requests a non-existent subset of data, such as requesting (Gen4, year) when the year dimension only has three generations, may cause the Essbase application to crash.

Dimension build may fail to move a member in an attribute dimension. 27768 (32829)
A dimension build that should move a member in an attribute dimension to a different parent fails to move the member.

A retrieval takes longer to run with an optimal size retrieval buffer than it does with a much smaller retrieval buffer. 27779 (32841)
A retrieval runs faster with a small retrieval buffer size than it does with larger retrieval buffer that is the optimal size. A retrieval buffer is at optimal size when it is large enough to do the entire query in one chunk.

Retrievals that include attributes may return incorrect results. 27784 (32848)
Retrievals that contain attributes, more than one Two-Pass calc member, and more than one base member may have incorrect results.

Data load may hang if the data file contains unknown members. 27799 (32865)
The OLAP Server may hang and fail to display an error message when it encounters an unknown member during a data load.

Running several dimension builds in succession may result in a memory leak. 27849 (32932)
Running several dimension builds in succession may result in excessive memory usage that is not released when the dimension builds finish running.

A large data load via Essbase API may not generate a rejected records file. 28192 (33325)
When running a data load via the API that updates more than 3000 blocks, using a data file that contains some errors, the OLAP Server may fail to create a rejected records file.

Memory leak with calculations that use the @XREF function. 28277 (33425)
Memory used in calculations that use the @XREF function may not be released until the Essbase application is stopped and restarted.

Some calculations that use the @XREF function may fail to finish running. 28335 (33492)
Calculations that use the @XREF function may hang.

Essbase applications may crash during periods of heavy usage. 28393 (33556), 28420 (33589), 27432 (32401)
Essbase applications may crash during periods of heavy usage such as concurrent calculations or concurrent data replication operations through partitions.

Spreadsheet Add-In on French systems may drop decimal point and following numbers from drill-through reports. 28420 (33589)
On systems localized to French, the Spreadsheet Add-In may drop the decimal point and following digits from numbers displayed in drill-through reports, if the variable type of the corresponding column in the relational database fact table is floating point.

Using the Escape key to cancel calculations in Esscmd may cause the OLAP Server to crash. 28433 (33606)
Canceling calculations in Esscmd using the Escape key may cause the OLAP Server to crash.

Certain expressions in calc scripts may cause the OLAP Server to crash. 28661
Calc scripts that contain certain complex nested expressions such as FIX statements may cause the OLAP Server to crash.

View sample and member load SQL are different when sorting on a column.  When a recursive hierarchy was created and then a sort was performed on an alternate column in the hierarchy, the SQL generated for a view sample and a member load were different. SQL.  (30035)

Deleting table in OLAP model deletes two dimensions in the metaoutline.
In OLAP models, the dimension IDs were not being saved properly causing multiple dimensions to be deleted. (31101)

Calc scripts defined at application level not available.  In the Essbase Application and Database dialog box, choosing an Essbase Application for which a calc script had been defined at the application level caused the incorrect message, "No Calc Script for this database."  (31285)

Messages missing from message.txt file.  In the message.txt file, two error messages were missing. (31691)

ESSCMD script cannot be run during data loads.  If I$ISHOME contained blank, the ESSCMD script could not be run during a data load.  (31916)

When attempting to run multiple ESSCMD scripts, only the last script runs.  If multiple ESSCMD scripts were created and then added to a member or data load, only the last ESSCMD script would run. (32015)

Job scheduler not working for daily member and data loads.  The Job Scheduler did not run scheduled daily member and data loads because the year was not retained correctly in the date.  (32016)

Incorrect character set for messages.  The character set for messages pointed to Japanese characters because of an error in the message file. (32627)

During dataload, error message is displayed indicating "Unable to allocate memory".  The message displayed despite adequate memory being available. (23487)

Formulas exceeding 240 characters in length are truncated.   Any formula greater than 240 characters in length was truncated causing all characters following the 240th to be eliminated. (26619)

Intelligent Help missing in Tools menu. There was no Intelligent Help in the Tools menu. (32631)

Essbase Integration Services does not load more than one SQL query at a time.  During dataloads in the metaoutline, only the data for the first SQL statement was loaded although the remaining SQL statements were sent to Oracle for execution. (33041)

OLAP Models do not save months as a sort order.  When a "Year_Quarter_Month" hierarchy was used in an OLAP model and a sort was performed on the month, the model would not save the member MonthMM as a sort item. (33054)
 

The following problems are fixed in FixPak 8.

Change the TEMP and TMP Windows environment variables from system variables to user variables.  From the Control Panel, select System.  On the Environment tab, create new TMP and TEMP user variables and set them to the same values as their counterparts in the System Variables box.  Then delete the old TMP and TEMP system variables.
Start DB2 OLAP Integration Server as a foreground task.

(n/a) In MaxL, although the limit for stored calculations is 64 KB, calculation scripts created in MaxL that have multi-byte characters cannot exceed 40 KB. MaxL does not support outline synchronization in this FixPak.

(n/a) In the LRO example for DB2 OLAP Server Objects 7.1, the RetrieveLO method of dataserver control does not function properly.

(29210) When you attempt to kill a restructuring process, a "command not accepted" error is returned, and the restructure process is not terminated.

(16674) A formula calculated top down may not create all blocks when calculated. To correct, you can either set Create Blocks on Equation to ON, or run the calculation with update-calc off.

(18188) DB2 OLAP Server allows two instances of the an outline to be open at the same time by the same login ID. This means it is possible to have two versions of the same outline open at the same time. If you do this, each Save overwrites the changes of the other instance.  Therefore, this practice is not recommended.

(18529) In Excel, from the 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.

(18745) If all the children of a dense parent are label only, you may not be able to make that parent label only. However, you can if the parent is sparse.

(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) For Lotus, after a calculation, the Controls on Calculation box may not be selectable.

(20451) DB2 OLAP Server does not warn you if you request that export results be placed in essbase/bin when there is an export results file with the same name already in that location.

(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 it, delimit the blank fields.

(20562) Long idle time with Spreadsheet Add-in may cause extra "Please Log In" messages. Click OK until the message stops appearing.

(20600) If you create a data file with blanks in the file name, such as My Documents, Essbase may display an error message. If you encounter this error, change the file name so that it contains no blanks.

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

(21300) Using the calculator hash table optimization to speed up calculations can negatively impact performance on some outlines.

(21332) @MOD may fail validation on the client but pass validation on the server. If your attempts to save an outline on the client fail, and the outline is associated with a calculation script containing @MOD, try saving it on the server.

(21616) Incompatibilities exist between the filtering feature in Microsoft Excel and the Spreadsheet Add-in.

(22235) Using Dynamic Time Series (DTS) members on a partitioned database may cause a server crash if ALL of the following criteria are true:

-Partitions are of the type Replicated or Transparent
-DTS member or members are on the target partition
-The Time dimension is sparse on the target partition and/or the source partition

If you have this situation there is another workaround:

-The outline has DTS members defined in Time dimension and
-The partition definition doesn't mention Time dimension, indicating it should include all members.
Then you should mention 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.

(22636) @member does not validate on the client if it is used with a function. Syntax checking on the client fails; however, on the server it returns no errors.

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

(22716) If a member name contains an embedded space, &, ? or ^, you may not be able to create a security filter for the member unless you surround the member name in quotation marks, such as "Year to Date."

(22782) If you edit a custom-defined function or macro, the application may shut down and restart. If you are creating a new custom-defined function or macro, consider clicking New instead of Edit.

(22784) You may not be able to delete a custom-defined macro or a custom-defined function using Application Manager if the name is longer than 59 characters.

(22847 closed) Lack of memory during database restructure may crash server. This is an HP issue. If you encounter a problem, use this setting: set _M_ARENA_OPTS 1:32.  Consult your HP documentation for more information.

(24037) Even though only one member of a dimension has an attached report, all the members in a dimension may be highlighted as if they had a report attached.

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

(24981 closed) DB2 OLAP Server calculator functions that take strings as arguments (for example, @ISUDA, @UDA, @CONCATENATE, @SUBSTRING, @MATCH, @NAME) may not perform correctly if there is a member alias that is the same as the string. In this case, use the function @ALIAS, described in the Technical Reference.

(25511) Step 15 of "Preserving Formulas When Retrieving Data" in the Spreadsheet Add-In User's Guide is technically correct but somewhat confusing. It will be improved for a future release.

(25717) Using @ISIDESC in a dynamic calculation, that is nested inside a dynamic calculation with a two-pass calculation tag may cause OLAP Server to freeze.

(26130 closed) Calculator function @RANGE and the cross-dimensional operator (->) cannot be used inside a FIX/ENDFIX statement.

(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 view event log, when displayed via Application Manager, may incorrectly fail to show log entries because it evaluates "today" as GMT. To view log entries, select "All Dates."

(27417) If calculation times slow greatly from V1.1 to V7.1 FixPak 8, and your time dimension is dense, try changing it to sparse.

(27865) Running too many concurrent reports may overwhelm DB2 OLAP Server or operating system resources, especially against partitioned databases. If this occurs, the report processes do not ever finish.

(27927) Whenever one process is logged out by another process (such as Application Manager running on another machine), the process 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 that has an implied shared child causes the association to be ignored, and DB2 OLAP Server writes a message to the application event log. An implied shared member is a member with only one child.

(28140) EssOtlQueryMembers: On UNIX, the currency conversion type returned is incorrect. Workaround: Use EssOtlFindMember instead.

(28208, 23213) When attempting to logout all users with Application Manager, the request is honored but additionally the user making the request is also disconnected. Workaround: Login again after such a request.

(28254) Excessively large outlines (greater than 400 Mb) may fail to open.

(28339) If you export an LRO attached to a shared member, then import it again, the LRO attaches to the original member (the member that actually stores the data referenced by the shared member), not the shared member.

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

(28646) If a supervisor logs out a Spreadsheet Add-In user, and that user performs a drill-down, they will not see any error, but the retrieval will be empty. If they try to reconnect to server, then they will see a dialog box informing them of disconnect, and if they click OK the log in dialog screen appears.

(29311) If you have created the sample application Demo without direct IO, then add the direct IO configuration parameter to essbase.cfg (DIRECTIO TRUE), you may not be able to start the Demo application.

Viewing certain application logs crashes the server. (22465)
When an application log contains information starting with a bracket, viewing that log may cause the OLAP Server to crash.

When using @ISMBR(@ATTRIBUTE) with a Two-Pass Calc member in an IF statement, calculation results are inconsistent. (24102)
If the Two-Pass Calc member formula has IF without the matching ELSE, the attribute calculation on that member may return inconsistent results. The bug is that values calculated on members which match the IF condition may be carried over to members that do not match the IF condition.

Calc script crashes with "Unable to Allocate Memory" messages. (24553)
Some calc scripts return the error message "Unable to Reallocate Memory for [] in []. Refer to the Application Log for details" and may also crash the application.

SHUTDOWNSERVER command intermittently hangs the OLAP Server. (25204)
If you issue the SHUTDOWNSERVER command (ESSCMD) at the same time a user is starting an application, both ESSCMD and the OLAP Server may hang intermittently.

EQD queries return "command too long" errors. (26462)
Long Essbase Query Designer (EQD) queries may return the following error messages:

• Report Parser Error. Top of stack reached. Command too long at [#Missing]
• EQD did not return any row or column. Set to re_open.

Essbase Query Designer (EQD) does not provide a visual focus indicator. (27132)
When you open EQD, the focus is shown on "book1" but the keyboard is unresponsive. Focus is now set properly on the tree view.

Outline members in Member Selection dialog box are invisible. (27154)
When the Windows appearance scheme is High Contrast Black, outline members are invisible in the Member Selection dialog box in the Spreadsheet Add-in.

Search in Report Editor finds all Kanji characters for one double-byte search. (28436)
In Report Editor in Application Manager, when you do a search for one double-byte character in a report that contains double-byte Kanji characters, the search finds all the double-byte characters in the script. However, the search works properly when the search string has more than 3 bytes.

Attribute calculation results may be incorrect. (28907)
When a spreadsheet retrieval includes only the upper-level member from an attribute dimension, and the base dimension has Dynamic Calc members, the attribute calculation result may be incorrect.

Change in persistence of Allow Connects setting. (28929)
Disabling connections in the application settings (Allow Connects option) is now persistent (i.e., is no longer session-dependent). If an administrator disables connections for databases in an application, connections remain disabled until re-enabled by the administrator, using the application settings. Note, however, that the Allow Updates and Allow Commands settings are still session-dependent. More info ...

Formula preservation is not working. (29140)
When "Preserve Formulas" is selected in the Spreadsheet Add-in (Essbase > Options > Mode tab under Formula Preservation), and you retrieve in a spreadsheet that contains formulas, some formulas may not be preserved.

Drilling down on a member in a spreadsheet may cause the error "Maximum number of columns exceeded". (29142)
When you drill down in a spreadsheet on a member that should not return more than 256 columns, Essbase may display the following error message: "Maximum number of columns [256] exceeded [312]"

Cannot insert column(s) after a drill-down in spreadsheet. (29178)
After drilling down in a spreadsheet and then attempting to insert a column, the following error message is returned:

"To prevent possible loss of data ... move the data to a new location and try again"

Applications that contain LROs and have Direct I/O enabled may fail to start. (29311)
If an application contains Linked Reporting Objects (LROs), and the essbase.cfg file for the server includes the DIRECTIO TRUE setting, the application does not start.

Attribute member and shared member in spreadsheet return incorrect values. (29425, 29503)
When an attribute member and a shared member are present in a spreadsheet, and the shared member is part of an outline that contains two or more levels of shared members, incorrect values may be returned after retrieval.

Attribute drill-down retrieves only partial base member list. (29436)
When drilling down on a level 0 attribute member in a spreadsheet to retrieve a list of base dimension members associated with that attribute, the retrieval returns only a partial member list.

LROs not listed correctly after dimension build. (29531)
When more than two linked reporting objects (LROs) are assigned to the same cell, and a dimension build deletes two of these members (using "remove unspecified" option), attempting to view the remaining LROs via the Linked Objects Browser results in a network error and exception file.

Retrieving in certain spreadsheets crashes server. (29630)
When a spreadsheet has members from different dimensions in the same column in the row header, retrieving in the sheet may crash the OLAP Server. Essbase should detect that this is an invalid grid and should return an error instead.

Spreadsheet retrieval from transparent partition may crash application. (29808)
When a spreadsheet contains repeated members, and at least one of the repeated members has a formula and is part of a transparent partition, the Essbase application may crash when you attempt a retrieval.

The EssOtlQueryMembersEx Outline API function returns incorrect results. (29817)
The EssOtlQueryMembersEx Outline API function does not return all correct members.

LINK report command returns incomplete member set. (29890)
The report command <LINK does not return all the members it should if the result of the command needs to be ordered by alias names.

Replicated partitions may fail to send data. (29912)
When running a script that clears, loads, and calculates the source, and replicates data from the source to the target, Essbase may fail to replicate data.

The Essbase Agent may crash when login or logout requests are issued from clients. (30084)
Under certain conditions, the Essbase agent may crash when login or logout requests are issued from clients. Those conditions are as follows:

• When clients send invalid login IDs to the OLAP Server.
• When a client times out or logs out after issuing a request to open a large application log but before the request finishes its processing.

Multiple simultaneous calcs hang or crash the OLAP Server. (30421, 30499)
Multiple simultaneous calculations may hang or crash the OLAP Server.

Spreadsheet retrieval involving formulas with sparse Dynamic Calc members may crash OLAP Server. (30514)
A spreadsheet retrieval that includes a member with a formula referencing a sparse Dynamic Calc member may crash the OLAP Server.

Error produced when starting Essbase with -secure option. (30604, 16856, 17954)
When starting Essbase with the -security option, the following error messages are generated:

Cannot get terminal ioCannot set terminal io********Cannot restore terminal io

Retrieving from a database with many Dynamic Calc members may use much more memory than expected. (30707, 30825)
A retrieval from a database with many Dynamic Calc members may cause Essbase to use much more memory than expected.

Attribute retrieval with Two-Pass Calc member doubles value. (30796)
When an attribute member and a Two-Pass Calc member are present in a spreadsheet, and the upper level members in the base dimension are shared members, a retrieval returns incorrect values (double what the result should be).

Attribute retrieval rolls up incorrect values unless all children are present in retrieval. (30868)
Retrieving attribute members in a spreadsheet when all children of the member are not yet present in the sheet returns incorrect values. This problem occurs when upper level members in the base dimension are shared members.

EIS not listed in component list when valid license is used to install. (30940, 30941)
After installing Essbase Release 6.2 with a license key that includes Essbase Integration Services (EIS), EIS is not listed as a component, either on the install screen "list of options to install" or within Application Manager. However, EIS is installed and works properly.

Partition definition that validates in Essbase Release 6.1.4 does not validate in Release 6.2. (30989)
A partition definition containing the @Match command that validates in Essbase Release 6.1.4 returns the following error and does not validate in Release 6.2.

"Partition definition for slice [1] does not parse"

Long filenames error when loading data from client file. (31004, 30257, 30764)
When loading a data file from a client machine using a long pathname, an error is returned saying that long filenames are not supported.

Dataload that worked properly in Release 6.1.x fails with Release 6.2. (31523, 31411)
A dataload that worked properly in Release 6.1.x fails with Release 6.2 due to a memory over-usage issue.

The following problems are fixed in FixPak 7.

Formulas containing the @PARENT or @ANCEST functions with two parameters may generate syntax errors. (20851, R614)
@PARENT and @ANCEST functions work as expected only if the first argument is a member of the first dimension in the outline. If you request a second parameter that is not from the first dimension in the outline, DB2 OLAP Server may display formula syntax errors such as: "Error: Invalid number of parameters for this function."

Incorrect results from the member formula A=B/-C. (21993, R614)
When DB2 OLAP Server calculates the member formula A=B/-C, it may multiply B and -C instead of dividing B by -C.

Increase in retrieval times between 5.0.2p13 and 6.1.0p3a. (22494, R614)
Retrievals from the same spreadsheet view may take longer on 6.1.0p3a than they do on 5.0.2p13.

A Partition validates in 5.0.2p13 but does not validate in 6.1.0. (23360, 26108, R614)
When you validate a correctly defined partition in 6.1.0, the following error may be returned: "Cell count mismatch: area for slice [1] members per dimension." The same partition validates without errors on 5.0.2p13.

ESSCMD scripts that contain ENABLELOGIN/DISABLELOGIN commands prevent subsequent scripts from processing. (23763, 26101, R614)
When an Esscmd script contains the ENABLELOGIN/DISABLELOGIN commands, actions specified in the script are processed, but the Esscmd process may be left running; therefore, if another script is scheduled to run after it, the second script will not be started.

Selecting a linked partition in the Linked Object Browser brings up a blank spreadsheet. (23921, 26098, R614)
After you select a linked partition from the Linked Objects Browser, Essbase may display an empty spreadsheet that is not connected to the source database.

Running a calculation that uses the @XREF function may crash the application. (24198, R614)
While running a calculation that uses the @XREF function, the Essbase application may crash.

Certain spreadsheet retrievals cause application errors. (24413, 26102, R614)
Certain spreadsheet retrievals containing member formulas and dynamic calcs may cause application errors and crashes.

The @CALCMODE function causes application crash during a calculation on Microsoft Windows 2000. (24745, R614)
On Microsoft Windows 2000, when you run a calculation that uses the @CALCMODE function, the OLAP application may crash and Essbase may create an .xcp log.

Retrieval from a partitioned database may cause the OLAP application to crash. (25091, R614)
A retrieval from the target of a transparent partition may cause the OLAP application to crash if the spreadsheet includes a sparse dynamic calc member that has a self referencing member formula.

Error when drilling down in a spreadsheet if the outline has two or more attribute dimensions. (25212, 26104, R614)
Drilling down in a spreadsheet that is connected to an outline with two or more attribute dimensions may cause Essbase to display an attribute dimension in the wrong position and to display the error message "currently, multiple reports per retrieval is not supported."

Error when validating a correctly defined partition if a previous validation attempt resulted in an error. (25215, R614)
When validating a correctly defined partition definition, DB2 OLAP Server may display the following error message: "Unable to open file (C:\Docume\Admini\Locals\Temp\Ess00000.tmp)." This occurs after the following sequence of events:

• DB2 OLAP Server displays an error message when validating a partition
• You find and fix the cause of the error
• You validate the new, correctly defined partition definition

Data retrieval times may be much longer on Version 7 FixPak 4 (and later) than on Version 1.1. (25735, R614)
On outlines that contain many dense dynamic calcs, spreadsheet retrievals that take a few minutes on Version 1.1  may take several hours on Version 7, FixPak 4 and later.

A temporary Excel book file is not erased after the Spreadsheet Add-in is closed. (25764, R614)
When the Essbase Cascade feature is used to create multiple worksheets with the Spreadsheet Add-in, a temporary Excel book file remains after the Add-in is closed.

"Retrieve and Lock" incorrectly displays non-missing data as #Missing. (26105, 25214, R614)
When a retrieval contains errors and "Retrieve and Lock" is selected from the Essbase drop down menu in the Excel Add-in, DB2 OLAP Server may display #Missing in non-missing data cells.

A report takes 24 hours to run after adding an attribute dimension to the outline. (26451, R614)
When the outline is modified to add an attribute dimension with one attribute, a report that previously took only 4 minutes to run now takes 24 hours to run. The attributes are not being referenced at all in the report script.

The Essbase agent and clients may hang after repeated unsuccessful attempts to load applications. (26726, 24506, R614)
After repeated unsuccessful attempts to load applications, and when the number of file descriptors is too low, the Essbase agent may display the error "Network error [24]" repeatedly until the Essbase agent and clients hang.

DB2 OLAP Server may skip some disk drives specified in the DISKVOLUME settings. (26808, R614)
If Essbase is using buffered I/O, it may not use the order specified in the DISKVOLUME settings when spanning disk drives.

Certain calculations take much longer to run in Version 7 FixPak 4 (and later) compared to Version 1.1. (26932, R614)
Some calculation times may be much longer on Version 4 FixPak 4 and later than on Version 1.1.

Updating a database after a database copy may cause an application crash. (26984, R614)
An application may crash with the error message "1080021 (Invalid transaction handle [0x120017] passed to the Storage Manager for database [V_ini])" after the following sequence of events:

• A user accesses the database using the Excel Add-in.
• The user locks some data cells and changes their values but does not send the data.
• A second user copies the database.
• The first user attempts to send the modified values to the database.

Essbase completes the processing of a dimension build with 100 attribute dimensions, but it does not allow the resulting outline to be saved. (27424, R614)
After completing a dimension build with 100 attribute dimensions, DB2 OLAP Server fails to save the resulting outline. It displays the error message "Unable to read information from [ARBORPATH\App\AppName\DbName\DbName.otn]" and and the outline is not saved.

The PATH statement may be invalid after the Spreadsheet Add-in is installed. (27523, 27916, R614)
If the last character is the PATH statement is a space, the PATH may become invalid when the Spreadsheet Add-in is installed.

DB2 OLAP Server incorrectly interprets certain distinct Japanese characters as the same character. (27568, R614)
DB2 OLAP Server may fail to recognize that certain Japanese characters are different, resulting in error messages during some operations. For example, when two distinct characters are added as member aliases, DB2 OLAP Server may return the error "Record #1 - Alias already used as a member name (3314)."

OLAP Server may crash during calculation that includes the @WITHATTR function. (27572, 23691, R614)
When a calculation includes the @WITHATTR function and specifies the "IN" operator, the calculation may cause the OLAP Server to crash.

EsbQueryDatabaseMembers does not display alias names for shared members. (27667, R614)
The EsbQueryDatabaseMembers VB API function does not display alias names for shared members.

Creating many LROs and then listing them using the API or ESSCMD causes the application server to crash. (27698, R614)
Creating 84 LROs and using EssLROListObjects or ESSCMD to list all of the LROs in the database may crash the application server.

MaxL may fail to build a partition correctly. (27700, R614)
When you build a partition using MaxL, the partition validation may fail with the error "area 1 overlaps area 2." When you build an identical partition using the Application Manager, it validates without errors.

Memory leak while running a recursive retrieval macro. (27779, 28142, 26730, R614)
Memory usage steadily increases during a recursive retrieval macro. After about 150 retrievals, the application may crash with the error "unable to allocate aligned memory."

Access violation error when using EssGPerformOperation. (27844, 28314, R614)
When using the EssGPerformOperation Grid API function within the EssBeginDrillOrLink function, an access violation error is returned.

Results of a report script that uses D-T-S are incorrect. (27848, R614)
Report may contain incorrect data values when the report script uses dynamic time series (D-T-S) members.

Retrieving data from a large outline with attribute dimensions may crash the database. (27851, 27494, R614)
Retrieving data from a large outline with attributes may crash the database when the spreadsheet retrieval includes attribute dimensions and a two pass calc member with a cross dimensional dependency. When the spreadsheet retrieval does not include the attributes, retrieving from the same outline does not cause a crash.

A dimension build may corrupt the Essbase outline if the "EVENT 29" parameter is in the .cfg file. (27991, 22819, R614)
If the "EVENT 29" parameter is in the Essbase .cfg file, a dimension build may corrupt the outline.

DB2 OLAP Server may not release memory after a retrieval. (27992, 27365, R614)
In certain cases, DB2 OLAP Server allocates a large amount of memory for a retrieval and it may not release the allocated memory after the retrieval is finished. The OLAP application must be unloaded and reloaded to free the memory.

Limit of 512 applications per OLAP server. (28061, R614)
The limit of 512 applications per OLAP server has been lifted in FixPak 7.

Certain retrievals may incorrectly report #Missing values. (28084, 28076, R614)
When all of the following conditions are met, retrievals incorrectly result in #Missing values:

• The member is a parent/ancestor of a shared member
• The shared member has attribute associated with it
• The shared member itself is not part of the query

DB2 OLAP Server incorrectly displays an error message when @UDA is used to create a partition. (28115, R614)
When the @UDA function is used to create a partition, DB2 OLAP Server may incorrectly display the error "cell count mismatch in area ( )" when the partition is validated.

The EnableLogin Esscmd script fails periodically with errors 1054021 and 1019031. (28138, 17980, R614)
The EnableLogin Esscmd, when it is part of an Esscmd script, may fail periodically with errors "1054021 cannot modify settings for application" and "1019031 Unable to write to [c:\ARBBORPATH\APP\AppName\AppName.app]; database is in read only mode for backup." The second error is displayed even when the database should not be in read only mode.

A report displays the alias on the first member of a dimension, but it does not display the aliases on the other members of that dimension. (28144, 27099, R614)
After running a report script, only the alias on the first member of the dimension is displayed in the report. The aliases on subsequent members are not displayed.

EssGConnect may not return ESS_STS_CANCEL when it should. (28188, R614)
The EssGConnect Grid API function does not return the value of ESS_STS_CANCEL if you press the Cancel button or the Esc key in the Essbase System Login dialog box. An error value is returned instead.

A dimension build that associates attributes may corrupt aliases on other attributes. (28447, R614)
Aliases on existing attributes may be corrupt after a dimension build that associates attributes.

Large spreadsheet retrieval from a partitioned database with attributes crashes the application. (28489, R614)
The Essbase application may crash during a large spreadsheet retrieval when the database is the target of a transparent partition and the outline contains attributes.

Outline API functions may fail on Windows 95. (28614, 24218, R614)
On Microsoft Windows 95, when you use Outline API functions, the function may fail and Essbase may display the error message: "1060044 cannot create temporary file name."

Results of some queries that include dynamic calcs and certain functions may not be correct. (28621, 26809, R614)
When dynamic calc formulas involve certain functions, such as @CURRMBR, @PARENT, @SPARENT, @ANCEST, @SANCEST, results from queries that reference those formulas may not be correct because some dynamic calcs may not be triggered properly.

Dimension build may crash the OLAP server if set ESSLANG=Japanese_Japan.MS932@binary. (28651, 28553, R614)
The OLAP server may crash during a dimension build if
set ESSLANG =Japanese_Japan.MS932@binary.

Formulas that reference dynamic calcs and contain cross dimensional operators may produce incorrect results. (28838, 24117, R614)
When a formula references one or more dynamic calcs and contains one or more cross dimensional operators, results may be incorrect. The fix for this problem requires that you have the following entry in your essbase.cfg file: EVENT 28.

Deleting members from an outline may produce an internal logic error. (28883, 27225, R614)
Deleting members from an outline and saving the changes may cause Essbase to display the following error: "internal logic error 1178."

Undefined symbols adBarrGet and adGetStat when linking with libesssql on Solaris. (29007, R614)
When linking a program with with libesssql on Solaris, the compiler may give one or both of the following errors:

• Undefined first referenced symbol in file adBarrGet ./libesssql.so
• Undefined first referenced symbol in file aGetStat ./libesssql.so

The OLAP server may hang when you run EssGetApplicationInfoEx. (29064, R614)
The Essbase OLAP Server may hang when you run the EssGetApplicationInfoEx() API function before using the CREATEAPP or COPYAPP Esscmds.

Essbase attempts to bind a port that is out of the allowed range when it runs out of available ports within this range. (29294, R614)
When Essbase runs out of available network ports within the allowed range of 32768 to 33678 (incremented by 5), it may attempt to bind a port outside of this range, resulting in the following error message: "Error(1042010) Network Error [125]: Unable to Bind Host Server Socket On Port [0]." Essbase should not attempt to bind the unavailable port.

Spreadsheet retrievals from a database that is the target of a transparent partition may cause the Essbase application to crash. (29533, 29483, 28548)
When retrieving data from the target of a transparent partition, the Essbase application may crash and an .xcp log may be created.

Memory leak during some spreadsheet retrievals. (29565)
During spreadsheet retrievals, the esssvr process may fail to release memory after the retrievals have completed. The OLAP server may run out of memory after running successive retrievals.

FixPak 6 contains all the fixes from FixPak 5, but no additional fixes.  FixPak 6 introduces an early version of a new feature called DB2 OLAP Server Miner, and FixPak 7 enhances it.  See Introducing DB2 OLAP Server Miner with enhanced LRO support for more information about what OLAP Miner can do for you.

The following problems are fixed in FixPak 5.

A report takes 24 hours to run after adding an attribute dimension to the outline. (23423, P3A)
When the outline is modified to add an attribute dimension with one attribute, a report that previously took only 4 minutes to run now takes 24 hours to run. The attributes are not being referenced at all in the report script.

When using cache memory locking on Solaris, the warning #1008133 appears: "Unable to allocate memory, permission denied." (24604, P3A)
The root.sh file distributed with Hyperion Essbase OLAP Server for Solaris is incorrect and does not provide adequate access to use cache memory locking. With this fix, the root.sh is corrected.

In Hyperion Essbase Spreadsheet Add-in for Excel, the "Retain on Keep and Remove Only" and "Retain on Zooms" options do not work. (24910, P3A)
The Formula Preservation options on the Mode tab of the Hyperion Essbase Spreadsheet Add-in for Excel Options dialog box are not working. If you select "Retain on Keep and Remove Only," the formula is not preserved after removing the members. If you select "Retain on Zooms," the formula does not jump down to the proper member when zooming. If you select "Retain on Zooms, with Formula Fill," the formula is not properly replicated to the child members.

Using SSAUDITR in the Essbase.CFG file causes long update times if dynamically calculated cells are present in the update. (25402, P3A)
When an Essbase audit file is associated with an application to track updates, any write operation from the Spreadsheet Add-in to the server takes an extremely long time. For example, an update that takes 45 seconds without an audit log may take 16 to 45 minutes with an audit file. This occurs when dynamically calculated cells are included in the group of cells being sent to the server.

The Hyperion Essbase API does not properly support cancelling retrievals. (25411, P3A)
CancelRetrieve does not call the user-defined cancel retrieve callback function when the user attempts to cancel a retrieval.

The @IRR Calculator function returns 15% when all values are zero. (26388, 23884, P3A)
If a range of values is all set to zero, when using the @IRR function on this range, the result is 15%. With this bug fix, to indicate that @IRR on a range of zero values is ambiguous, the function will now return #Missing.

Data load into the target partition does not work. (26686, P3A)
Loading data into the target when the final location for the data is in a source does not work in some circumstances. The server indicates that data successfully loaded, but no data was actually sent to the source.

Saving the modified outline of a Source database in a Transparent Partition crashes the application. (26798, P3A)
When using Transparent Partitions, if you save the modified outline of the Source database, the application crashes. This behavior occurs only when adding a group of shared children members to each of the new members.

In Hyperion Essbase Spreadsheet Add-in for Excel, locking and sending a zero value to the database does not update the database. (26805, P3A)
If you lock and send a zero value to the database, the database is not correctly updated to reflect the zero value. Other values sent to the database are correctly updated, however.

If you repeatedly do dimension-build and delete-member operations, the system may run out of memory. (26852, 25205, P3A)
On HP-UX 11.00, if you perform a dimension build operation, then manually edit the outline and delete all children in a dimension, then repeat the dimension build operation, memory utilization will consistently grow.

Certain formulas on two-pass calculation members cause the server to crash when retrieving with an attribute member. (26865, P3A)
When querying on attributes, if one or more members in the attribute query is tagged as two-pass calculation, and the formula involves one or more of the following functions -- @CURRMBR, @(S)PARENT, @(S)ANCEST, @(S)(MD)PARENTVAL, or @(S)(MD)ANCESTVAL -- the server crashes. With this bug fix, the formula is ignored during an attribute calculation. This is an Essbase limitation.

Memory is not regained by the operating system after running a long calculation and then exiting from Hyperion Essbase Application Manager, resulting in a system crash. (26898, P3A)
When a calculation runs for longer than 15 minutes, memory resources gradually diminish until eventually the operating system crashes. This occurs with Windows 95 or on Windows NT/2000 systems with low memory.

When drilling in on attribute members, the result may be displayed incorrectly. (26930, P3A)
When drilling in from upper-level attribute members, the retrieval results are placed in the wrong position. This occurs when attribute members from different levels appear in the same report.

When retrieving data into the target of a transparent partition, where the target database contains an attribute dimension, the data fails to come across to the target, and an error appears after a zoom in. (26978, 24256, P3A)
The following sequence of events causes a data retrieval to the target to fail: - Add an attribute dimension to an outline - Associate the attributes with a dimension - Create a transparent partition - Make sure the attribute dimension is mapped to void - Validate the partition - Load data into the source cube and run a default calculation - Retrieve from the target

Additionally, if you zoom in on an unrelated dimension, you see error #1023046: "Incorrect number of dimensions in request from remote site 6 sent 5 required." To get the correct result, you need to map all the attribute calculation members and the attribute dimension to void. This will solve the problem if the source database and the target database are under different applications. If the two database are created within one application, then you need to add "EVENT 5" to your essbase.cfg file.

Using the lev0 function the retrieval results are erroneous. (9340, P3)
In Hyperion Essbase Spreadsheet Add-in, if you attempt to retrieve all level 0 members using the lev0 function, the Retrieve option may not return data for the level 0 members but instead considers all members at the same generation as the first level 0 member and then retrieves their data.

If you have filtered access to a linked partition database, then you may encounter a server crash while launching the partition. (13907, P3)
If you have Read-only privilege to a filter on a linked partition database, attempting to launch the partition may result in an exception file and a server crash.

Attempting to validate a linked partition fails. (19115, P3)
If you create a linked partition database and map the source outline to the target outline, attempting to validate the partition may generate the error message, "Target dimension count mismatches in Area One."

When you perform a default calculation containing FIX( @IDESCENDANTS(COMPANY,-1)), the database restructure fails. (19284, P3)
When you are performing default calculation containing FIX( @IDESCENDANTS(COMPANY,-1)) for a database, the settings in the Set Default Calc dialog box may change from the Use Calc Script Object option to the Use String option, and the statement FIX(@IDESCENDANTS(COMPANY, -1) may be truncated. As a result, your attempt to perform a database restructure may fail.

If dimension names are similar but not duplicate, the Essbase Member Selection dialog box displays an incorrect dimension. (19413, P3)
If an outline has similar dimension names, the Essbase Member Selection dialog box may ignore the dimension that is selected on a spreadsheet and display an incorrect dimension and its members.

In Hyperion Essbase OLAP Server, the Agent messages are mistranslated. (19476, 19937, P3)
In Hyperion Essbase OLAP Server, the following messages may be mistranslated: "port," "ports available," "connections in use," and "ports in use."

The Linked Objects Browser dialog box does not display the scroll bar. (19500, P3)
When you open the Linked Objects Browser dialog box, the scroll bar may not be visible at the bottom of the dialog box. The scroll bar may be displayed when you enlarge the dialog box or try to resize the columns.

In Hyperion Essbase Spreadsheet Add-in for Lotus 1-2-3, the context-sensitive help is mistranslated. (19508, P3)
In Hyperion Essbase Spreadsheet Add-in for Lotus 1-2-3, the context-sensitive helps may not be translated.

The default query name is not translated in the Hyperion Essbase Query Designer dialog box. (19510, P3)
In the Hyperion Essbase Query Designer dialog box of Hyperion Essbase Spreadsheet Add-in for Excel, the default name assigned to a new query may not be translated.

In the Hyperion Essbase Query Designer dialog box, the drop-down list box name is truncated. (19532, P3)
In the Hyperion Essbase Query Designer dialog box, the Data Sort panel drop-down list box name, Ordering, may be truncated. The problem may be noticeable in non-English versions of Hyperion Essbase Spreadsheet Add-in.

The short cut key to select Enable Secondary Button does not function properly. (19595, P3)
In Hyperion Essbase Spreadsheet Add-in, in the Global tab section of the Essbase Options dialog box, the short cut key for selecting Enable Secondary Button fails.

After retrieving data for a new query, the mouse pointer does not change back to an arrow. (19697, P3)
In Hyperion Essbase Spreadsheet Add-in for Lotus 1-2-3, after retrieving data for a new query in the Hyperion Essbase Query Designer dialog box, the mouse pointer may not change back to an arrow.

F1 key does not consistently display help in Hyperion Essbase Spreadsheet Add-in. (19918, P3)
In Hyperion Essbase Spreadsheet Add-in, the F1 key does not consistently display Essbase Help.

In non-English versions of Hyperion Essbase OLAP Server, while initializing Essbase.exe, the server requires the English characters. (19988, P3)
In non-English versions of Hyperion Essbase OLAP Server, such as on German NT, while initializing Essbase.exe, the confirmation message accepts the English alphabet "Y" instead of a language-independent value.

The Find option in the Edit menu of the Member Selection dialog box does not function properly. (20266, P3)
In Hyperion Essbase Spreadsheet Add-in, when you use the Find option to locate a value for a member that is selected in the Member Selection dialog box and using a Windows Server, the Find option may search for the value incorrectly.

Cannot delete the Server log if the Application Server is running on Windows 95/98. (20630, P3)
In Hyperion Essbase Application Manager, You cannot delete the Server log if the Application Server is running on Windows 95/98.

Attempting to rename a Boolean attribute member corrupts the outline. (20901, P3)
In Hyperion Essbase Application Manager, if you attempt to rename a Boolean attribute member directly on the outline and then enter the changes in the Boolean Member Names fields of the Attribute Member Names dialog box, when you reopen the outline, you may find the outline is corrupted.

If a dimension consists of more than 32 members with a single non-consolidated child, the attribute association with that dimension is erroneous. (21933, 23982, 25014 P3)
If there are more than 32 members in one dimension, and that dimension contains a parent with exactly one child that does not consolidate to its parent, an attempt to associate attributes to that dimension may result in a corrupt outline, with no error message.

Attribute query with sparse Two-Pass calculation members returns incorrect values. (22752, P3)
If the attribute query contains a sparse Two-Pass Dynamic Calc member, and the calculation formula refers to some blocks that are not included in the query, the result of the attribute query may not include the missing blocks.

The retrieval time increases compared to the previous releases of Hyperion Essbase OLAP Server. (22836, 24397 P3)
When retrieving data on a large number of sparse member combinations, the retrieval process is slower than the previous releases of Hyperion Essbase OLAP Server.

Calculation script does not set cells to #MISSING. (22961, 25168 P3)
In a calculation script, if a formula on a sparse member results in #MISSING, cells may not be updated.

While importing an outline from a rules file, you receive a segmentation fault. (23115, P3)
In MaxL, while importing an outline from a rules file, you may notice a segmentation fault.

The application crashes while retrieving data on an attribute dimension. (23211, P3)
In Hyperion Essbase Spreadsheet Add-in, an attempt to retrieve data on an attribute dimension may crash the application.

On UNIX, you cannot run the Grid API with more than 16383 rows, but on Windows NT, you can run more than 65000 rows. (23520, P3)
On the UNIX platform, when you are using the Grid API function, EssGlnit with the number of rows larger than 16383, the Grid API program returns an error code.

The "Allow" settings may fail if a supervisor attempts to log in. (23657, P3)
If you disallow commands, connects, or updates through Application Manager in the Application Settings dialog box, through the SETAPPSTATE command in Esscmd, or using the "alter application" command in MaxL, the settings may change if another supervisor simultaneously attempts to log in.

Shared members of a sparse Dynamic Calc member are not aggregated. (23865, P3)
Batch calculations involving shared members that are shared members of sparse Dynamic Calc members may produce incorrect results.

An EQD (Essbase Query Designer) query for more than 65536 rows crashes a spreadsheet. (23871, P3)
Using Hyperion Essbase Query Designer, attempting to create queries for more than the limit of 65536 rows crashes the spreadsheet.

When attribute dimensions are added, calculations are performed incorrectly during data retrieval. (23881, P3)
In Hyperion Essbase Spreadsheet Add-in or Report Writer, when attribute dimensions are added, calculations may be performed incorrectly on Two-Pass member formulas during data retrieval.

Queries involving attributes and Two-Pass calculation members may sometimes yield incorrect results. (23903, P3)
If a query involving attributes references a Two-Pass member and that two-pass member is dependent in turn on other two pass member(s) the query results may sometimes be incorrect.

The Visual Basic API function, EsbGetApplicationInfoEx, returns incorrect number of users connected. (23911, P3)
Although the user is connected to an application and a database, the Visual Basic API function, EsbGetApplicationInfoEx, may return zero users connected with no error code.

When performing a replicated partition on a large amount of data, an exception file is generated. (24051, P3)
In Hyperion Essbase Application Manager, when you perform a replicated partition on a large amount of data, the replicated partition may fail, resulting in a network error and an exception file.

The Visual Basic API function, EsbLROAddObject(), generates an application error. (24116, P3)
When the Visual Basic Main API function, EsbLROAddObject, is applied to associate linked reporting objects to a cell, the error message, "Cell: EXCEL.EXE - Application Error" may occur.

In an outline, the dimension order affects XREF results. (24281, P3)
XREF may return incorrect results if the dimension order in the source cube differs from the dimension order in the target cube.

Calculation never finishes across a transparent partition database. (24292, P3)
Transparent partitions may cause the database calculation to run infinitely.

Retrieving data on a spreadsheet containing a generation name produces an exception log and crashes the application. (24384, P3)
If you attempt to retrieve data on a spreadsheet containing a generation name, you may encounter an exception log and application crash.

While loading data, if the data file consists of attribute members, some data are skipped. (24477, P3)
While loading data, if the data file consists of attribute members, Hyperion Essbase OLAP Server may skip the remaining records after the first attribute member.

Using the Grid API function, BeginConditionalZoomIn, with the report specification, {UCHARACTERS}, causes a crash. (24521, P3)
If using the BeginConditionalZoomin function with the report specification, {UCHARACTERS}, results in an underlined character string longer than 127 characters, the Grid API program may crash.

During multiple bitmap mode calculation, excessive memory is allocated. (24552, P3)
When there are many shared members in the last sparse dimension, multiple bitmap mode calculation may use too much memory. Set the configuration parameter MultipleBitmapMemCheck to TRUE to prevent the excessive use of memory.

Attempting to validate an outline while performing incremental building generates an error message. (24557, P3)
While performing incremental dimension building, if you try to validate the outline, the incremental dimension building process fails and generates an error message.

If a query involving too many dynamic calculations with complex formulas fails to execute because of insufficient memory on the server, the application crashes instead of the query failing. (24669, P3)
If a query involving too many dynamic calculations with complex formulas fails to execute because of insufficient memory on the server, the application crashes instead of the query failing.

An attribute calculation with Two-Pass calculation returns inconsistent results. (24786, P3)
If you attempt to perform attribute calculations with Two-Pass calculation repeatedly, you may encounter inconsistent results.

Programs with multiple calls to EsbOtlGetAssociatedAttributes and EsbOtlGetMemberInfo result in a crash. (24807, P3)
Using the Visual Basic Main API functions, EsbOtlGetAssociatedAttributes and EsbOtlGetMemberInfo repeatedly may crash the Visual Basic program.

Registering more than 20,000 Essbase users to Hyperion Essbase OLAP Server gives fatal error when restarting. (24875, P3)
After registering 20,000 users to Hyperion Essbase OLAP Server, if you terminate Essbase and then restart, you may encounter the error message, "Fatal Error: Error reading security file [22]."

Retrieving data on a blank cell results in an application crash. (24895, P3)
If you try to retrieve data on a blank cell, the application may crash with an exception file.

In Hyperion Essbase Application Manager Japanese version, the Dynamic Time Series (DTS) settings cannot be saved. (24905, P3)
Hyperion Essbase Application Manager Japanese version may not retain the DTS settings.

While retrieving data on sparse dynamic calculation members, you may receive incorrect results. (24976, P3)
If the formula is executed in a cell mode, attempting to retrieve data on sparse dynamic calculation members may result in incorrect #MISSING values.

The Grid API function, EssGetApplicationInfoEx(), generates the error 1051030 when you pass a Null parameter to it. (24982, P3)
The use of a Null value as the second parameter in the Grid API function, EssGetApplicationInfoEx(), generates the error message 1051030, "Application does not exist."

The Agent hangs when another user attempts to access the same application while filters are being verified. (25089, P3)
Hyperion Essbase OLAP Agent may hang if one user attempts to verify a filter, while another user attempts to access the same application.

Attempting to perform a zoom in on attribute members may result in the Spreadsheet Extractor error 1130001. (25127, P3)
If you attempt to expand attribute members, you may receive the Spreadsheet Extractor error 1130001.

Attempting to retrieve data on attribute members crashes the server. (25278, P3)
Attempting to retrieve data on specific attribute members results in an exception log and application crash.

Creating 60,000 filters causes the server to crash and corrupt security files. (25298, P3)
If you try to create 60,000 filters using the ESSCMD, copy filter command, the server may crash with an exception segmentation violation. Moreover, if you attempt to restart Hyperion Essbase OLAP Server, you may receive an error message, "The security file is corrupted."

A database may lose its currency link upon stopping the Essbase Agent. (25364, P3)
If you shutdown Hyperon Essbase OLAP Server, the currency link to your database may disappear.

Deleting a shared member removes all data from the actual member. (25376, P3)
If you delete a shared member, all data from the actual member may be deleted.

Attempting to retrieve data on attribute members across transparent partitions results in incorrect values. (25585, P3)
If you perform a retrieval on attribute members from a target database of a transparent partition, you may receive incorrect results.

Using the ESSCMD command, ENDARCHIVE, the .cfg setting _SM__BUFFERED_IO TRUE results in a crash. (25715, P3)
With the .cfg setting __SM__BUFFERED_IO TRUE, if you attempt to complete archiving of data using the ESSCMD command, ENDARCHIVE, or the MaxL command END ARCHIVE, the application may crash.

The .cfg setting, __SM__BUFFER_IO TRUE, erroneously returns zero values. (25789, P3)
If the buffered IO setting is set to True, the calculated values may erroneously return zeros.

Sub-optimal performance for formulas executed in top-down mode. (26003, P3)
If a formula attached to a member is executed in a top-down mode as indicated in the application log file, performance may be sub-optimal.

The following problems are fixed in FixPak 4.

----------- For DB2 OLAP Server:

Some ESSBASE.CFG settings are not displayed in the Essbase Configuration panel of the Server Information in Application Manager. (7381, P2)
Some dialog box settings in ESSBASE.CFG are not displayed in Hyperion Essbase Application Manager Server > Information > Essbase configuration.

Locking and sending data to the target of a transparent partition may not work. (12008, P2)
When using either Spreadsheet Add-in with Free-Form interpretation or the C or Visual Basic API, an attempt to lock and send data to the target of a transparent partition may fail and generate the following error message: Error the 1014004 - Unable to update members which have not been locked.

Syntax checker does not move to the problematic line. (14020, 15997 P2)
When the syntax checker is run in the Calc Script Editor, and if an error is found, the window may not scroll to show the problematic line. To locate the line, you may have to scroll through the calculation script text to find the highlighted information.

Performing an Edit > Replace on a large calculation script will delete some portions from the calculation script. (18490, P2)
In Application Manager, performing an Edit > Replace on a large calculation script may stop the replace process or delete the replaced text and may subsequently generate the following message, "Text is not found. Do you want to start at the beginning of the file?"

If an Excel spreadsheet consists of unknown members, retrieving with Repeat Member Labels selected may result in a corrupted spreadsheet. (18733, P2)
In the Spreadsheet Add-in, retrieving for unknown members with Repeat Member Labels selected may return scrambled data.

Column shifts to the left after a Keep Only. (18973, P2)
In the Spreadsheet Add-in, an attempt to perform a Keep Only may shift the first column to the left.

Database state does not get updated when the data load is partially successful. (19176, P2)
If a data load is partially successful when you select Database > Calculate, you may encounter the message, "the database does not contain any data" even if the database contains data.

NLS characters get corrupted for object name when viewed in the server console. (19546, P2)
User, Database, and Application names containing non-English European characters are not displayed correctly in the server console.

In Lotus 1-2-3, NLS characters in cascading filenames are displayed incorrectly. (19833, P2)
In the Spreadsheet Add-in for Lotus 1-2-3, non-English European characters are incorrectly displayed in the filename when specifying them in the prefix, suffix, or workbook text box in the Cascade Options dialog box.

Incorrect SSAUDITR setting in .CFG corrupts database. (19844, P2)
An incorrect SSAUDITR setting in the Essbase.CFG may give the error message, "unable to connect to database" when you attempt to connect to the database in any client program.

In the Application Manager Japanese version, Field Properties dialog box contains mangled characters. (19953, P2)
In the Application Manager Japanese version, in the Data Prep Editor, you may find some mangled characters in the Data Load Properties and the Dimension Building Properties tabs of the Field Properties dialog box.

When searching for a string, the Calc Script Editor does not scroll through to locate it. (20492, P2)
When updating a calculation script, the Edit > Find function does not cause the window to scroll to the next occurrence and locate the string that you are searching for.