FixPak Date: December 2001
Service Levels:
The OLAP Integration Server clients no longer support Windows 95. The OIS clients support Windows 98, Windows NT 4.0 SP5 and later, and Windows 2000.
If you have installed the DB2 OLAP Integration Server (OIS) sample application, then before installing this FixPak you should back up your existing OIS sample database, OLAP Metadata Catalog, and the OLAP models and metaoutlines that you want to preserve. After backing up your samples, you can upgrade your existing catalog to be compatible with FixPak 7 (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, which is not compatible with previous FixPaks. Do not attempt to use the FixPak 7 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 7 client, you must also install the FixPak 7 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.
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 7 for DB2 OLAP Server Version 7.1 is the equivalent of maintenance level 4 (patch 4) for Hyperion Essbase Release 6.1 plus Hyperion Integration Server 6.1. Hyperion maintenance levels are cumulative; each level contains new fixes, plus all the fixes for the previous maintenance levels.
FixPak 6: FixPak 6 contains all the fixes from FixPak 5, plus a new feature, DB2 OLAP Server Miner 7.1.
FixPak 5: R6.1.0_P3A is Essbase 6.1.0 Patch 3A from Hyperion, and R2.0_P2 is Integration Server 2.0 Patch 2 from Hyperion. These are the service levels in FixPak 5 from IBM. FixPak 5 fixes problems on all server and client platforms for DB2 OLAP Server 7.1 only; this FixPak does not add any additional fixes for DB2 OLAP Integration Server 7.1 beyond what was added in FixPak 4.
FixPak 4: R6.1.0_P2 is Essbase 6.1.0 Patch 2 from Hyperion, and R2.0_P2 is Integration Server 2.0 Patch 2 from Hyperion. These are the service levels in FixPak 4 from IBM. FixPak 4 fixes problems on all server and client platforms for DB2 OLAP Server 7.1 and DB2 OLAP Integration Server 7.1.
FixPak 3: R6.0.0_P3 is Essbase 6.0.0 Patch 3 from Hyperion, and R2.0_P1 is Integration Server 2.0 Patch 1 from Hyperion. These are the service levels in FixPak 3 from IBM. FixPak 3 fixes problems on all server and client platforms for DB2 OLAP Server 7.1 and DB2 OLAP Integration Server 7.1.
FixPak 2: R6.0.0_P2 is Essbase 6.0.0 Patch 2 from Hyperion, which is in FixPak 2 from IBM. FixPak 2 fixes problems on all server and client platforms for DB2 OLAP Server 7.1.
FixPak 1: R6.0.0_P1 is Essbase 6.0.0 Patch 1 from Hyperion, which is in FixPak 1 from IBM. FixPak 1 fixes problems on all server and client platforms for DB2 OLAP Server 7.1.
FixPak 4 and later changes the levels of software supported by DB2 OLAP Server:
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.
Minimum RAM | 64 MB or greater (128 MB or
greater for UNIX platform) base recommendation:
The base recommendation for running DB2 OLAP Server and its sample applications is a 64 MB minimum. On UNIX platforms, base requirement is 128 MB of physical memory (256 MB recommended), and at least twice the MB of physical memory for swap space (when physical memory is less than .5 GB). Contact your system administrator or hardware vendor for optimum swap configuration. Start with the base amount of RAM for your platform, and then allocate additional memory to accommodate your applications. |
To stop Windows NT and Windows 2000 services:
c:\tempTo change your Windows 2000 TMP User Variable and TEMP Environment Variable, take these steps:
Your applications are automatically
migrated to the latest FixPak level when you open them.
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.
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.
Filename | Server Components |
---|---|
aix.tar | AIX OLAP
Server AIX OLAP Integration Server AIX SQL Interface AIX Application Programming Interface AIX OLAP Miner |
solaris.tar | Solaris Operating Environment
OLAP Server Solaris Operating Environment OLAP Integration Server Solaris Operating Environment SQL Interface Solaris Operating Environment Application Programming Interface |
hpux.tar | HP-UX OLAP
Server HP-UX OLAP Integration Server HP-UX SQL Interface HP-UX Application Programming Interface |
To start the server installation:
This command extracts the
files necessary to perform a complete installation.
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:
Filename |
|
Client Components |
---|---|---|
wincd1.zip | Japanese
Korean Simplified Chinese Traditional Chinese |
Application
Manager Spreadsheet Add-in for Excel Spreadsheet Add-in for 1-2-3 Integration Server desktop OLAP Miner (English only) |
wincd2.zip | English
French German Italian Spanish Brazilian Portuguese |
Application
Manager Spreadsheet Add-in for Excel Spreadsheet Add-in for 1-2-3 Integration Server desktop OLAP Miner (English only) |
wincd3.zip | Danish
Finnish Norwegian Swedish Czech Hungarian Russian |
Application
Manager Spreadsheet Add-in for Excel Spreadsheet Add-in for 1-2-3 Integration Server desktop OLAP Miner (English only) |
To start the installation:
You can also install OLAP Miner in this FixPak. OLAP Miner supports the following levels of Windows operating systems:
|
|
Server Components |
|
---|---|---|---|
wincd1.zip | Japanese
Korean Simplified Chinese Traditional Chinese |
OLAP
Server OLAP Integration Server SQL Interface Application Programming Interface OLAP Miner |
Application
Manager Spreadsheet Add-in for Excel Spreadsheet Add-in for 1-2-3 Integration Server desktop OLAP Miner (English only) |
wincd2.zip | English
French German Italian Spanish Brazilian Portuguese |
OLAP
Server OLAP Integration Server SQL Interface Application Programming Interface OLAP Miner |
Application
Manager Spreadsheet Add-in for Excel Spreadsheet Add-in for 1-2-3 Integration Server desktop OLAP Miner (English only) |
wincd3.zip | Danish
Finnish Norwegian Swedish Czech Hungarian Russian |
OLAP
Server OLAP Integration Server SQL Interface Application Programming Interface OLAP Miner |
Application
Manager Spreadsheet Add-in for Excel Spreadsheet Add-in for 1-2-3 Integration Server desktop OLAP Miner (English only) |
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.
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:
|
|
|
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:
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.
installp java_devX.rte
The next step is to set the Java environment variables for your operating system.
chmod +x jXrel_XXXXX-solsparc.bin
where XXXXX represents the specific version number. Then run the self-extracting binary:
jXrel_XXXXX-solsparc.bin
The next step is to set the Java environment variables for your operating system.
swinstall rte_XXXXX.depot
where XXXXX represents the specific version number.
The next step is to set the Java environment variables for your operating system.
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 –fullversionFor DB2 OLAP Server, you will see this:
Product | Shell | Script |
DB2 OLAP Server | Korn or Bourne | essjava.sh |
DB2 OLAP Server | CShell | essjava.csh |
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"Note that $JREHOME/bin must be added to the beginning of LIBPATH.
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/jreNote that $JREHOME/bin must be added to the beginning of LIBPATH.
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
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"If you use the Bourne or Korn shell, add the following text to the .profile file:
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
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"If you use the Bourne or Korn shell, add the following text to the .profile file:
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
/ARBORPATH/java/*.jarThen set the JVMMODULELOCATION to enable Hyperion Essbase to find and load Java. JVMMODULELOCATION is a setting in the essbase.cfg file that enables you to 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. To set the JVMMODULELOCATION parameters, you must specify the full path and filename of the Java Virtual Machine (JVM) library. The location and name of this library varies, depending on the JRE version and the operating system you are using. To set JVMMODULELOCATION:
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.aOn Solaris (JRE 1.3): The path of the JVM library file is:
/usr/j2se/jre/lib/sparc/client/libjvm.soCAUTION: 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.slThe directory, PA_RISC, might be PA_RISC2.0, depending on the processor used by the computer running HP-UX.
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 –fullversionFor DB2 OLAP Integration Server, you will see this:
Product | Shell | Script |
DB2 OLAP Integration Server | Korn or Bourne | hisjava.sh |
DB2 OLAP Integration Server | CShell | hisjava.csh |
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=/tmpIf you use C shell, add the following additional variables from the hisjava.sh file:
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}"
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=/tmpIf you use C shell, add the following additional variables from the hisjava.sh file:
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}"
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 =/tmpIf you use C shell, add the following additional variables from the hisjava.sh file:
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}"
> 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
The DB2 OLAP Server installation program copies the Java files to your workstation. However, to avoid interfering with any existing Java environments you might have on that workstation, the installation program does not set up the environment variables that DB2 OLAP Server needs to access the Java files. To complete the installation of Java, set up the following environment variables on Window NT and Windows 2000:
JREHOME=%ARBORPATH%\java\jre
CLASSPATH=%ARBORPATH%\java\jre\lib\ext\jaxp.jar;
%ARBORPATH%\java\jre\lib\ext\parser.jar;%CLASSPATH%
On Windows 2000, add this variable to your PATH statement:
%JREHOME%\binOn Windows NT, add this variable to your PATH statement:For example, you can set your PATH to the following value:
PATH=%JREHOME%\bin;%PATH%
C:\Program Files\IBM\DB2 OLAP Server\java\jre\binFor example, you can set your PATH to the following value:
PATH= C:\Program Files\IBM\DB2 OLAP Server\java\jre\bin;%PATH%
c:\Program Files\IBM\DB2 OLAP Server\java\jre\bin\hotspot\jvm.dll
To set JVMMODULELOCATION:
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.
Database
Server (Client) |
AIX
4.3.3 |
HP-UX 11.0
(1) |
Solaris
2.6, 2.7, 2.8 (Sun OS 5.6, 5.7, 5.8) |
Windows NT 4.0 , 2000 |
---|---|---|---|---|
DB2 UDB
6.1
|
DB2 6.1
ODBC |
DB2 6.1
ODBC |
DB2 6.1
ODBC |
DB2 6.1
ODBC |
DB2 UDB
7.1
|
DB2 7.1
ODBC |
DB2 7.1
ODBC |
DB2 7.1
ODBC |
DB2 7.1
ODBC |
Informix 9.
2
|
Not currently
supported |
MERANT
3.6 |
MERANT
3.6 |
MERANT 3.6
(2) |
MS SQL Server
6.5.201
|
Not currently
supported |
Not currently
supported |
Not currently
supported |
MS SQL Server
3.7 ODBC (included in MDAC 2.5) (3) |
MS SQL Server
7.0
|
Not currently
supported |
Not currently
supported |
Not currently
supported |
MS SQL Server
3.7 ODBC (included in MDAC 2.5) (3) |
MS SQL Server
2000 (no client required) |
Not currently
supported |
Not currently
supported |
Not currently
supported |
MS SQL Server
3.7 ODBC (included in MDAC 2.5) (3) |
Oracle
8.04
|
MERANT
3.6 |
MERANT
3.6 |
MERANT
3.6 |
MERANT 3.6
(2) |
Oracle
8i
|
MERANT
3.6 |
MERANT
3.6 |
MERANT
3.6 |
MERANT 3.6
(2) |
Sybase
12
|
Not currently
supported |
Not currently
supported |
MERANT
3.6 |
MERANT 3.6
(2) |
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.
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
[ODBC Data Sources]Note: ServerName=mytnsServerName must refer to the name of an Oracle database defined in the tnsnames.ora file. For more information, see the Oracle installation documentation.
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.
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
[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
To configure a relational data source with ODBC Administrator, complete the following steps:
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. 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.
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.
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:
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.
Operating System | Path Variable Settings (1) |
Windows NT
or Windows 2000 (2) |
PATH=CURRENT_PATH;%ISHOME%\Bin; %ISHOME%\odbc\merant36\lib |
AIX (3) | LIBPATH=$LIBPATH:$ISHOME/odbc/merant36/lib:$ISHOME/esslib
PATH=$PATH:$ISHOME/bin |
HP-UX (3) | SHLIB_PATH
$SHLIB_PATH:$ISHOME/odbc/merant36/lib:$ISHOME/esslib
PATH=$PATH:$ISHOME/bin |
Solaris (3) | LD_LIBRARY_PATH= $LD_LIBRARY_PATH:$ISHOME/odbc/merant36/lib:$ISHOME/esslib PATH=$PATH:$ISHOME/bin |
Table Notes:
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:
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:
To test whether the ODBC driver
loaded successfully, run the $ISHOME/bin/ivtestlib command followed by the path to the ODBC
driver.
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:
IBM DB2 OLAP Server Miner is licensed for use only with IBM DB2 OLAP Server.
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:
The Hyperion Essbase calculator language can now be extended through the creation of custom-defined macros and 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:
Mathematical Functions:
The parallel export process works
only with the multidimensional storage manager, not the relational storage
manager.
- PAREXPORT--Executes a parallel export by enabling you to specify the number of export threads to be used, export filename(s) for the data, the type of data to export, and and how the data is to be exported.
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.
www.ibm.com/software/data/db2/db2olap/library.html
In FixPak 7 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:
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:
The online API Reference incorrectly states that the C MAIN API function, EssCopyApplication, starts the application. The new application is not started and has never in the past.
The Database Administrator's Guide erroneously stated when calculating an average, if the skip property was None, DB2 OLAP Server did not count #MISSING values when it calculated an average. The correct behavior is that if the skip property is None, #MISSING values are not skipped when DB2 OLAP Server calculates parent values, averages are not shown as exceptions. All values are counted.
Starting in FixPak 7, the Business Intelligence Tutorial has been removed because the interface it describes has been removed from OLAP Integration Server. OIS now offers Intelligent Help instead.
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.
Last Login on Fri Apr 20 21:52:16 2001Now the agent log message displays the following Date/Time format:
Last Login on Friday, April 20, 2001 10:57:29 AMHowever, all other date and time formats remain the same.
Therefore, if performing maintenance operations that require disabling connections, updates, or commands, you must make those maintenance operations within the same session as the one in which the setting was disabled. So while performing maintenance operations in batch mode, you must either complete all the tasks that motivated the disabling of commands, connects, or updates as part of the same session in the same script, or, disable commands/connects/updates manually in Application Manager or Administration Console prior to performing those tasks, staying logged in to that session for the duration of the maintenance operations.
Note:
The session-persistent application settings
are accessed in the following interfaces: Essbase Application Manager (In the
Application Settings dialog box, Allow Commands, Allow Connects, and Allow
Updates) Essbase Administration Console (In Application Properties, Allow
Commands, Allow Connects, and Allow Updates) ESSCMD command-line interface:
SETAPPSTATE options 6-8. MaxL language interface:
alter
application
alter
application
alter
application
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)For information about the purpose and operation of CALCMODE, see the online Technical Reference, Essbase Functions section.
DB2 OLAP Server Miner now
supports linked reporting objects (n/a)
OLAP Miner is enhanced in FixPak 7 with LRO
support.
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:
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:
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:
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:
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.
The first
part of the formula disappears when you use Flashback. (20589,
P2)
When using the Spreadsheet Add-in with Lotus 1-2-3,
an attempt to retrieve data on a formula that has an error followed by a
Flashback may cause the first part of the formula to
disappear.
EsbGetDatabaseState does not return default or modified values. (20626,
P2)
The VB API routine, EsbGetDatabaseState, does not
return correct values in the ESB_DBSTATE_T structure. In particular, the default
values for Retrieval Buffer Size and Sort Buffer Size are either 0 or incorrect.
Additionally, any new values that you enter through Hyperion Essbase Application
Manager are ignored.
@SUM function
does not work correctly with User Defined Attribute (UDA). (20758,
P2)
@SUM function may not work correctly with more than
one macro as its expList.
Incorrect
handling of operators, such as AND and OR inside a FIX statement. (20766,
P2)
FIX command involving member functions used with
AND, OR operators may generate incorrect member sets.
While using
the @CHILDREN function, you cannot put space between the parentheses and the
member name. (21174, P2)
While using the @CHILDREN
function within a FIX statement, inserting a blank space between the parentheses
and the member name may yield an error message.
Zoom In
results in an error message if maximum number of rows exceeds 8,192. (21242,
23210 P2)
In the Spreadsheet Add-in with Lotus 1-2-3, an
attempt to zoom into more than 8,192 rows may result in an error
message.
Generating an
exception log file, while synchronizing outlines causes the application to
crash. (21293, P2)
While synchronizing outlines, a crash may occur and
an exception error log is generated when using an alias in the partition
definition.
Error in
outline synchronization with transparent partition on a shared member. (21620,
P2)
During outline synchronization, an attempt to add
both shared and regular members in the same dimension to a target database may
not add the shared member, and it may give the error message, "There is 1
Message in the application log identifying a change that was not applied during
the outline synch."
Calculation
on a transparent partition seems to run indefinitely. (21651,
P2)
Two types of formulas, Constant Assignment and
Forward References, when attached to a sparse member, trigger top-down
execution. But the application log may not contain messages indicating top-down
execution.
Unable to
restructure data on an HP-UX 64-bit machine if the directory name exceeds 8
characters. (21656, P2)
Creating directory names
with more than eight characters may generate an exception error log file and
hinder the data restructure process.
Translation
for Member Selection is incorrect. (21744, P2)
In the
Spreadsheet Add-in with Excel, Essbase Member Selection features are erroneously
translated. For example, "insert list before active cell" translation is
misleading. Also, the message at the bottom of the Member Preview dialog box is
mistranslated. This problem is noticed in Spreadsheet Add-in (Essbase Release
6.0 P1) Japanese version.
Text type
attribute member having only numeric values does not get associated. (21748,
P2)
While using a rules file to associate the attribute
members with the base member, a text type attribute member that contains only
numeric values and begins with the 0 may not get associated with the base
member.
Zoom In may
cause incorrect results if Essbase Options are checked. (21785,
P2)
In Hyperion Essbase Spreadsheet Add-in, when the
options, Display > Cell > Repeat Member Labels and Zoom > Member
Retention > Remove Unselected Groups are selected, an attempt to zoom in may
cause incorrect results.
When the row
header has invalid alias name, the Excel spreadsheet shows incorrect values.
(21804, P2)
In the Spreadsheet Add-in, if the option Use Both
Member Names and Aliases for Row Dimensions is selected, retrieving may result
in incorrect values when row members contain invalid alias
names.
Case
sensitivity does not work correctly during dimension building. (21906,
P2)
Case sensitivity may not function correctly and may
cause the server to freeze during dimension building.
Zoom Out does
not function correctly if Formula Preservation is checked. (21949,
P2)
When Formula Preservation is selected in the
Spreadsheet Add-in, zoom out may give erroneous results.
Attribute
dimension building corrupts the outline. (22020, 22325,
P2)
When a user tries to build and associate an
attribute dimension on the base dimension, Application Manager randomly
associates attributes at all levels and corrupts the
outline.
Internal Rate
of Return (@IRR) function produces incorrect results. (22163,
P2)
Using @IRR in a calculation script may produce
incorrect Retrieve results.
Database
restructure causes the application to crash. (22206,
P2)
If a member is renamed after another member that is
deleted, the new member may map to both previous and existing members and cause
the server to crash.
"Invalid
Block Header" error following a calculation script or other long running update
operation. (22256, P2)
Error 1006010 or 1006016
appears following a calculation script or other long-running update operation.
Although the problem has been corrected by this patch, the error message
indicates that the database was corrupted. This patch will not fix corruption
that has already occurred. You must therefore restore the most recent clean
backup of the database or start over with an empty
database.
Lotus 1-2-3
results in an error message if #MISSING is set to 0. (22333,
P2)
In Spreadsheet Add-in with Lotus 1-2-3, if the
#MISSING label is set to zero and there is no data, an error message is produced
stating, "The sheet contains an unknown member 0."
Dimension
building for base member hierarchy does not work properly. (22350, 22695
P2)
Dimension building for a base member hierarchy may
not work properly when using the generation build method. The rules file does
not contain attribute member associations, but when the rules file updates the
outline, it assigns attributes to members of different
levels.
A crash may
occur when verifying an outline containing lengthy date and numeric attribute
member names. (22395, P2)
If a full name of a date
or numeric attribute member, including parents and ancestors when applicable, is
larger than 80 characters, an attempt to save or validate the outline may cause
a crash.
Loading and
unloading data for a 250 GB database may result in a memory leak. (22412,
P2)
When starting DB2 OLAP Server, when you build
dimensions by Dynamic Dimension Build, upload data by Dynamic Data Load, or
calculate and then shutting down the product, allocated memory may not be
released and the operating system may crash.
Passwords
visible on UNIX when using the secure mode. (22491, P2)
When DB2 OLAP
Server is installed on UNIX in secure mode, passwords may still be
visible.
The C API
routine, ESSCMD EssOtlOpenOutlineQuery, leads to a memory leak. (22543,
P2)
The C API function, EssOtlOpenOutlineQuery,
allocates memory that is not released in EssOtlFreeMembers as it should be,
which eventually seriously hinders system performance.
After default
calculation lower level data may override upper level data. (22742,
P2)
When Aggregate Missing is off, lower level
consolidation that results in #Missing may override upper level
data.
Data not
rolling up properly when using an attribute dimension. (22756,
P2)
When an attribute dimension is used, the Spreadsheet
Add-in may not generate correct data roll-up.
The ESSCMD
GETDBSTATS fails when executed. (22816, P2)
Then ESSCMD GETDBSTATS
may not function if it is executed on a cube whose dimension name consists of a
particular character, such as '%n.'
The ESSCMD
EssOtlQueryMembers returns wrong result when outline exceeds 16K members.
(22853, P2)
The outline API, routine EssOtlQueryMembers, does
not return the correct number of outline members when the outline contains more
than 16K members.
Sparse
restructure causes Linked Reporting Object (LRO) counter to be reset. (22926,
P2)
When adding a new LRO immediately after a sparse
restructure, the following error occurs: "Object # already
exists".
Unable to
initialize GRID API when Regional Setting is German (Austrian). (22962,
P2).
The GRID API will fail to initialize when the
Regional Setting in the Control Panel is set to German
(Austrian).
Memory leak
in EssVSetSheetOption and EssVSetGlobalOption. (22998,
P2)
The VBA routines, EssVSetSheetOption and
EssVSetGlobalOption, leak memory on Windows 95/98 clients, causing degraded
performance when they are used repeatedly.
"Cannot
access object: Ess00000.TMP" error when running 4 batch jobs. (23034,
P2)
When running concurrent programs that use the
Outline API, Hyperion Essbase OLAP Server occasionally cannot create temporary
file names and displays the error message, "Cannot access object:
Ess00000.TMP."
Hyperion
Essbase Application Manager is not displaying the Disk Volume. (23059,
P2)
The Storage tab on the Database Settings dialog box
in Application Manager contains a table that is not always in synchronization
with the Disk Volume edit field or updated when changes are made to the disk
volumes.
EssCell may
not work for Dynamic Time Series. (23119, P2)
In Hyperion Essbase
Spreadsheet Add-in, running EssCell (Y-T-D) on an outline with attributes may
return #MISSING instead of the Y-T-D value.
EssVGetDataPoint returns incorrect values for Dynamic Time Series.
(23130, P2)
When using Dynamic Time Series in a spreadsheet to
return a specific H-T-D (April), the EssVGetDataPoint mistakenly returns "H-T-D"
instead of "H-T-D(April)."
Sparse
Dynamic Calc fails in a calculation script. (23156, P2)
If a
calculation of a stored member depends on a virtual block, either through
parent-child relationship or through formula, calculation of the virtual block
may not be triggered correctly, causing incorrect results for the stored
member.
GRID API
crashes with multiple concurrent logins and logouts on a multiprocessor machine.
(23175, P2)
The GRID API may crash on connect or disconnect when
using multiple threads on a multiprocessor machine.
Data is
incorrect when aggregated with Create Block on Equation and from bottom-up.
(23274, P2)
When using SET FRMLBOTTOMUP ON, the dependencies of
top-down formulas may be processed incorrectly, causing some blocks to be missed
during calculation.
EssVGetDataPoint function does not return correct data for a first page
header. (23275, P2)
EssVGetDataPoint function
may not work properly for the first page header of a query unless the cell being
inquired is in the first column.
Division by
values between .000000000000004 and -.000000000000004 results in a #MISSING.
(23375, P2)
In FixPak 4, the division with denominator values
between .000000000000004 and -.000000000000004 may result in a
#MISSING.
While
ignoring the TimeStamp parameter, EsbGetLogFile returns the entire log. (23396,
P2)
The Visual Basic API routine, EsbGetLogFile, ignores
the TimeStamp parameter and returns the entire log file rather than the entries
of the log file produced after the date and time specified by the TimeStamp
parameter.
@XREF
triggered by a query will not automatically log off the source database. (23470,
P2)
Queries involving Dynamic Calculations with @XREF
leave users logged into the remote sources of @XREF
references.
The server
produces incorrect results if the number of blocks to be locked exceeds the
LOCKBLOCK setting. (23656, P2)
When using formulas on
sparse members for which the number of blocks to be locked exceeds the LOCKBLOCK
setting, the current LOCKBLOCK setting may not return correct
values.
After moving
members of a sparse dimension, the server crashes while doing a base level
restructure (23925, P2)
After moving a sparse
dimension member, an attempt to restructure at the base level may result in a
network error, 10054, or may even cause the data to
disappear.
----------- For OLAP Integration Server:
Cannot Tag a
Parent and Child Dynamic Calc and Store with Dimension Build (14688,
15277)
In Hyperion Application Manager, a parent with a
single child cannot be tagged with Dynamic Calc and Store using Dimension
Build.
Drill-Through
Reports May Not Work if Level Build is Done with Null Value in the First Column
(21388, 22041)
If doing a level build with a null value in the
first column (GEN2) and a drill-through report is defined on the lower level of
the hierarchy, the drill-through reports do not appear when drilling down on all
the lower level members in Excel. If, however, you add an upper-level
drill-through report, the lower-level report is accessible.
Workaround
for 21388 and 22041:
Set the following
configuration parameter in essbase.cfg:
HISLEVELDRILLTHROUGH appname
This parameter sets the
Hyperion Integration Server drill-through mode for the application specified in
appname.
Shared
Members Not Added if Data is Sequential (21706)
When
metaoutline members are created from columns with sequential data, the "Add as
shared members" option is not applied.
Base
Dimension Name Not Automatically Updated After Renaming Attribute Member
(21795)
When renaming an attribute member, the base
dimension name is not updated onscreen without first performing a refresh
(F5).
DB2 OLAP
Integration Server Fails on Metaoutlines when Missing Corresponding Items in
OLAP Model (21803)
In a Metaoutline, attempting to view the Properties
on an attribute dimension column that does not have the corresponding dimension
in the OLAP Model causes Hyperion Integration Server to
fail.
Columns Added
to Drill-Through Reports are Sometimes Not Saved
(21859)
On occasion, columns added to Drill-Through reports
are not saved. This sometimes occurs after adding both intersections and columns
to a Drill-Through report.
Columns in
Drill-Through Reports are Sometimes Displayed Incorrectly
(21860)
On occasion, after editing a Drill-Through report,
columns set to be sorted in a descending order are listed instead in an
ascending order.
Member and
Data Loads Sometimes Report Zero Members Loaded (21865)
Following a
member and data load, Hyperion Integration Server Desktop may sometimes report
that zero members are loaded and some of the data is rejected. This may occur
after adding a dimension and a filter to an OLAP model and then previewing the
results before performing a member and data load.
Renaming an
Attribute Dimension as a Standard Dimension May Cause Server Crash
(21928)
If an attribute dimension is renamed as any of the
standard dimensions in an OLAP model, the validation will pass but during a
member load, the server may crash.
A Problem
Occurs if Applying a Boolean Condition when Creating Metaoutline with a Boolean
Attribute Dimension (21975)
The Boolean condition of
"not case sensitive" is not applied when creating a metaoutline with a Boolean
Attribute dimension.
Data Loads
Containing a Large Number of Duplicate Members Cause DB2 OLAP Server and DB2
OLAP Integration Server to Freeze (21998, 22147)
Performing a
data load using data that contains thousands of duplicate members causes DB2
OLAP Server and DB2 OLAP Integration Server to freeze.
Workarounds
for 21998 and 22147:
Set the following
configuration parameters in essbase.cfg:
NoMsgLogginOnDataErrorLimit = TRUE
DataErrorLimit =
1
Then, restart the Essbase server.
An alternate workaround is to start the OLAP Server component (olapisvr.exe) from the DOS prompt with the -C parameter set to 3100 or less.
Incorrect
Null Promotion in Outlines Built with Aliases (22232)
In an OLAP
Metaoutline, if a null value occurs where a value for a GENERATION or LEVEL
field is expected, the child value is promoted in its place. A problem occurs
when adding aliases to dimension members in an OLAP Metaoutline, causing
incorrect null promotion in the resulting Essbase outline.
Using ODBC
Version 3.6x Instead of Version 3.7x with SQL Server 7 Causes
Catalog Access Problems in Some Cases (22388)
You may experience ODBC
errors if you are using Microsoft SQL Server version 7 with version 3.6x of the
ODBC drivers, included in version 2.5 of the Microsoft Data Access Components
(MDAC). The type of problem encountered involves user access to catalogs other
than their own residing on the server. If you are experiencing this problem,
please visit the Microsoft web site for
information on obtaining the latest MDAC.
Installation
Script Links esslib to lib when Installing Over Existing OLAP Integration Server
(23191)
When installing over an existing DB2 OLAP
Integration Server, the installation script creates a symbolic link from esslib
to lib, placing all ess* shared library files in the wrong
directory.
Query Does
Not Properly Group By Parent for Data Loads of Parent/Child Dimensions
(23377)
When performing an attribute load for parent/child
dimensions, the SELECT statement used by OLAP Integration Server does not
contain the correct "GROUP BY" clause. This causes incorrect results when there
are shared dimension members.
Important Note: The fix included in this patch, a modification to the GROUP BY clause of the SELECT statement, is not supported on Informix databases and is a limitation for this patch.
Query for
Attribute Loads Does Not Use the Keyword, "DISTINCT"
(23382)
The SELECT statement used by OLAP Integration Server
when performing an attribute load does not contain the keyword "DISTINCT". For
some databases, this omission can result in a large number of rejected records
in the log file, slow load times, and, occassionally, an Essbase server
failure.
The following problems are fixed in FixPak 3.
DB2 OLAP
Integration Server Is Unable to Obtain a Read Lock Using Oracle
(23433)
A date format problem occurs when using certain
combinations of the MERANT ODBC driver and the Oracle relational database
management system (RDBMS). In this circumstance, DB2 OLAP Integration Server is
unable to lock a model ormetaoutline in the OLAP Metadata Catalog, thus
preventing access to OLAP models or metaoutlines.
Error message
"Cannot access object: Ess00000.TMP" when using the Outline API. (23034,
P3)
When running concurrent programs that use the
Outline API, DB2 OLAP Server occasionally cannot create temporary file names and
displays the error message "Cannot access object:
Ess00000.TMP".
HP-UX and AIX
only: correct header file versions required. (23460 P3)
FixPak 2
contained incorrect versions of API header files for the HP-UX and AIX
platforms. If you installed the FixPak 2 C API for these platforms, you should
install FixPak 3 over your FixPak 2 installation.
Database
fails to load with buffered I/O in effect and an Index Page size less than 8K.
(21733, P3)
When buffered I/O is in effect (see the information
message in the application log) and the user specifies an Index Page size less
than 8K, DB2 OLAP Server over-allocates memory to the Index cache during
database startup. If the user then specifices a large Index cache (for example
500M), the Index cache memory allocation might consume most or all of the
available memory, in which case the database fails to load.
The following problems are fixed in FixPak 2.
Cannot Tag a
Parent and a Child Dynamic Calc and Store with Dimension Build. (14688,
P2)
In the Application Manager, a parent with a single
child cannot be tagged with Dynamic Calc and Store using Dimension
Build.
EsbLROAddObject() May Give Error 1030718. (17507,
P2)
If the usOption parameter of EsbLROAddObject is set
to ESB_STORE_OBJECT_API, the API may produce error 1030718: Invalid object
option for cell not entered.
The Server
May Not Be Able to Create Database Whose Names Contain Certain Foreign
Characters. (18532, P2)
If a database name
contains certain foreign characters, like Kanji or Katakana, the Application
Manager may produce an error 1019002: Failed to create
database.
An Attempt to
Create and Delete a Chart on Lotus 1-2-3, Release 9.0 May Disable the
Double-Click Drilling Function of the Mouse. (18719,
P2)
When creating and deleting a chart on the
spreadsheet using DB2 OLAP Server V1.1 FixPak 7 (Essbase 5.0.2 P7) with Lotus
1-2-3 Release 9, may disable the double-click drilling
function.
Server
Crashes During Extremely Heavy Concurrent Update Workload. (19397,
P2)
Server crashes during extremely heavy concurrent
update workload.
Excel Does
Not Prompt to Save When Essbase Cascade Is Performed. (19431,
P2)
In the Spreadsheet Add-in, if a cascade is performed
the users are not prompted to save the file on exit.
Database
Setting "Create block on equation" Behaves Differently After Release 5.0.2 P9.
(19496, P2)
When "Create blocks on equation" is enabled,
execution of certain formulas during calculations may clear contents of some
data blocks.
Essbase
EssRetrieve Macro Lock Option for 2 and 3 No Longer Works for Lotus 9.1. (19522,
P2)
The lock options 2 and 3 available for the
EssRetrieve macro may no longer work for Lotus 9.1. When EssRetrieve macro is
run with EssSend macro, the following error message appears in Lotus: "Unable to
Update Members Which Have Not Been Locked."
5.0.2 P10
Locale Files and ESSBASE.MDB Are Not Replaced in a New Patch Installation.
(19775, P2)
Patch installation does not update <ARBORPATH>
/bin/essbase.mdb or locale files because they are
read/only.
Long Member
Formula Gets Truncated with Member Load Using Rules File. (19902,
P2)
An attempt to load members using rules file fails
when long member formulas are truncated in the member load rules file field. But
if the same member formula is entered manually using the member formula editor
text box, then it works fine.
ESBGetLogFile
Will Not Get the Server Log File Unless Application Name Is Undefined. (19936,
P2)
The VB API routine EsbGetLogFile will not get the
server log and will return a non-zero value when the AppName parameter is
explicitly set to null. It only works properly when the AppName parameter is
undefined.
EssVRetrieve
(Empty, Empty, 1) and EssVFlash (Empty) Use 100 % of CPU. (19946,
P2)
EssVRetrieve or EssRetrieve with the range parameter
is set to empty it may use close to 100% of the CPU for 2-3 minutes.
Furthermore, after the retrieve, EssVFlash may use close to 100% of the
CPU.
Volume
Spanning Has Been Set but Index File Creation Is Not Rolling Over to the Next
Volume. (19973, P2)
The error 1019028: "Out
of disk space, unable to write information to file," appears when a new page
file is created and the current disk volume has less than 1024 bytes of
available space.
Retrieve
Returns Invalid Values on Certain Databases with Circular Dependencies Between
Blocks. (20158, P2)
If a circular dependency
between blocks exists, retrieval of Dynamic Calc values may produce incorrect
results.
Retrieval
Through C API Renders Incorrect Results When Compared to Excel. (20283,
P2)
An
Essbase report containing a member name in quotes immediately followed by an '!'
without any space in between may not get recognized. This may result in a row
with the unrecognized members to repeat the value from the row
above.
EssOtlFreeMembers() Is Declared Twice in ESSOTL.H. (20409,
P2)
API programs that include the file ESSOTL.H do not
compile because EssOtlFreeMembers() is declared twice.
Calc Never
Finishes Across a Transparent Partition. (20579, P2)
Transparent
partitions may cause database calculation to run
infinitely.
Renaming a
Member with Shared Attribute Incorrectly Causes Complete Restructure. (20764,
P2)
In a time dimension, an attempt to add, rename, and
categorize members as shared members in the data storage may rapidly reduce the
page size indicating that complete data restructuring has taken place. But upon
each time, if a shared member is deleted or added to the outline, and the
outline is saved, the page file does not change, thus, indicating that data
restructure is not taking place.
Attributes
with Lengthy Text Names May Crash the Application. (20795,
P2)
In a Hyperion Essbase outline, if the sum of all the
text characters for attribute member names exceed 80 characters, saving or
verifying the outline may crash the application.
Spreadsheet
Retrieval Causes the Application to Crash and Core Dump on HP-UX. (20813,
P2)
In the Spreadsheet Add-in, when using a specific
spreadsheet view where the Essbase option Use Both Alias and Member Name is
enabled and where some dimensions are not represented, performing a Zoom In will
cause the application to crash. A core dump may also be created as a result of
the application crash.
EssVSetOption
Does Not Work. (20866, P2)
In the Spreadsheet
Add-in, the use of EssVSetOption may not work if the focus is on any of the VB
controls at the time of the calls.
Unable to
Synchronize an Outline After the Outline Is Revised for Transparent Partition.
(20904, P2)
An attempt to re-synchronize outlines of transparent
partitioned databases may disable the Edit and Apply option
buttons on the Synchronize Outline dialog box.
Sample Report
Generates Error. (20913, P2)
Running Sample report
asym.rep generates an error message: "incorrect asymmetric report [8] records
processed." This has been fixed only in the Japanese
version.
Right Click
of the Mouse to Collapse Member Values Displays Irregular Layout with
Spreadsheet Add-in. (20916, P2)
In the Spreadsheet
Add-in, if Repeat Member Labels and Use Both Member Names and Aliases for Row
Dimension settings are enabled, an attempt to collapse data to higher levels may
display irregular layout for member names.
When
Substitution Variables Are Set to Validate a Calc Script an Error "Unknown
Member" Is Generated. (20927, P2)
When running a calc
script that is associated with an outline, the application generates an error
message: "unknown variable or member name," if the substitution variables are a
substring of another.
VB API
Crashes on EsbOtlGetMemberInfo. (20941, P2)
VB API crashes when the
API call EsbOtlGetMemberInfo is used for a text attribute that returns a null
string value.
Report Script
with a Substitution Variable May Result in an Error Message in Double-Byte
Platforms. (20945, P2)
An attempt to run a
report script repeatedly on a double byte platform with a substitution variable
added to may result the following error message: "10001070 UNKNOWN LAST MEMBER
FOR _uY-T-D_v IN REPORT."
Performance
Problem with Dimension Build for Aliases on Shared Members. (20997,
P2)
When doing a Dimension Build on an outline where a
large number of shared members that have aliases are being added, the dimension
build may become slow.
If There Is
More than One Substitution Variable, Changing One Value May Cause Some of the
Previous Substitution Variable to Disappear. (20999,
P2)
If more than 1 substitution variable is defined,
changing the value of any one substitution variable may cause the first or the
previous substitution variable to disappear.
Record #65536
Is Missed When Doing a File/Update Outline. (21000, P2)
Record #65536
is missed when doing a File/Update Outline with a large data file (having more
than 65535 records).
In the
Japanese Application Manager, Except for the Active Application, No other
Application Names Are Listed for Copying. (21001, P2)
Unlike the
Application Manager English version, the Japanese Beta of DB2 OLAP Server 7.1
(Essbase Release 6.0 Japanese Beta) does not provide any choices of application
names to be listed for copying to the database.
Some Items
Are Truncated and Misaligned in Server Information Dialog Box and Database
Information Dialog. (21002, 21035, P2)
Some items are truncated
and misaligned in the Application Manager Server Information dialog box and
Database Information dialog box.
Attribute
Query with Shared Members and Two-Pass Calc Members May Cause Server to Crash.
(21099, P2)
On AIX 4.3.3 server, in ESSBASE. CFG file, if the
setting is OUTLINECHANELOG TRUE, an attempt to add a member and save the outline
may generate an exception log.
In the
Japanese Spreadsheet Add-in One of the Error Messages Is Not Correctly
Translated. (21135, P2)
In the Spreadsheet
Add-in, if Essbase Member Selection menu is selected then an attempt to select a
member will give the incorrectly translated message "1 no 22 sentak
saremashita."
Clicking a
Member Cell May Clear the Spreadsheet. (21159, P2)
In the
Spreadsheet Add-in, when dimensions listed in the column heading appear in only
one row, double-clicking a data cell may clear the
spreadsheet.
Renaming a
Logical Column Name in a Model Causes Member Load to Abort. (21184,
P2)
When the contents of a FIX statement results in an
empty list, the OLAP server ignores the FIX statement and performs the
calculation on the whole database.
In the
Japanese Application Manager, Event Log Displays Overwrapping Characters When
Scrolled to Left. (21188, P2)
In the Application
Manager, event log displays overwrapping 2-byte characters when the window
scrolls to right and then scrolls back to left.
Escape
Characters ("\) Do Not Work Properly in DB2 OLAP Server V1.1 FixPak 7 (Essbase
5.0.2 P11). (21189, P2)
The Escape characters
used in ESSCMD to update substitution variables fail when used with FixPak 11,
but work fine for FixPak 7.
Adding
Members to Outline with OUTLINECHANGELOG TRUE Crashes the Database. (21190,
P2)
On AIX 4.3.3 server, in ESSBASE. CFG file if the
setting is OUTLINECHANELOG TRUE, an attempt to add a member and save the outline
may generate an exception log.
Drill-Through
May Not Work When Outline Has Attribute Dimensions. (21202,
P2)
In the Spreadsheet Add-in, invoking Server
Drill-Through may generate an error message.
The Multiple
UPDATEVARIABLE Command Updates the First Variable. (21207,
P2)
In DB2 OLAP Server V1.1 FixPak 11, when running the
calc script, multiple UPDATEVARIABLE commands only update the first
variable.
Dynamic Calc
May Generate Inconsistent Results. (21215, P2)
In the
Spreadsheet Add-in, retrieval may generate inconsistent results for the same
member combination depending on the view and order of
retrievals.
Loading Data
by Using an Excel Workbook with Formulas or Custom Text After the First Sheet
Crashes the Application. (21219, P2)
In the Spreadsheet Add-in
DB2 OLAP Server Version 7, loading data using an Excel spreadsheet as a source,
if there are formulas or custom texts on the sheets after reading the first
sheet the application crashes.
Loading Data
with Rules File Set with "Add to existing value" with #MISSING After 0 Value,
Gives #MISSING. (21272, P2)
In a rules file when
loading data is set with "Adding to the existing value" and if you load data
with #MISSING after a value of 0 is loaded, the Retrieve instead of returning 0
returns #MISSING.
The Option
CALCOPTCALCHASHTBL TRUE Causes Inconsistent Results. (21300,
P2)
In some cases when the CALCOPTCALCHASHTBL is set to
TRUE in the ESSBASE.CFG file, incorrect data values may be
calculated.
Report Script
Produces Different Results from Release 5.0.2 P11 to 6.0 P1. (21305,
P2)
In the Application Manager, a report script with
more than one MASK command produces different output from Release 5.0.2 P11 to
6.0. P1. The file output in 6.0 P1 is larger than 5.0.2
P11.
Esssvr
Crashes When Performing Dense Restructure. (21501, P2)
Essbase server
generates a general protection fault while doing dense restructure for level 0
data.
Application
Manager Crashes When Viewing a Member with a User-Defined Attribute (UDA) List
Display Larger than 4k. (21534, P2)
If a member has a UDA
that is greater than 4K, when the outline is expanded in the Outline Editor
where such a member with a UDA exists, Application Manager
crashes.
Wording of
Grandparent and Parent option of Member Name Format in Application Manager Is
Incorrect (21574, P2)
In the member name format
panel of the attribute member names dialog of Application Manager, the member
name format grandparent and parent is not correct. It should read
grandparent.
Retrieval on
a Dynamic Calc Member Across Transparent Partitions May Be Slow on 5.0.2 P11.
(21636, P2)
In the Spreadsheet Add-in, retrieval on a Dynamic
calc member in a transparent partition may be slower in 5.0.2 P11 than in 5.0.2
P7.
In the API
EsbSetUser, if the PwdChgNow Option Is Set to True, then the User Is Prompted to
Change the Password Only One Time. (21683, P2)
If the
Application Manager Global Server Setting for the "Number of days before user
needs to change password" is set to greater than 0, and the EsbSetUser option
PwdChgNow is set to True, then the user is requested to Change Password only
once upon the first login.
Attribute
Calc Does Not Aggregate Values from Upper Level Shared Members. (21684,
P2)
Attribute calc does not aggregate values to the
parent of a shared member, if the shared member is related to an upper level
member that has base members as its children.
Retrievals on
a Transparent Target Database Take Longer on 5.0.2 P11 than on 5.0.2 P7. (21692,
P2)
A retrieval on a target database with three source
databases takes approximately 35 seconds with FixPaks 11 and 12 for DB2 OLAP
Server V1.1 (5.0.2 P11 and 5.0.2 P12) compared to approximately 6 seconds with
FixPak 7 for DB2 OLAP Server V1.1 (5.0.2 P7).
No
libglobalc.so in Essbase\api\lib. (21768, P2)
FixPak 11 for DB2 OLAP
Server V1.1 (5.0.2 P11) UNIX installation does not put libglobalc.so into the
Essbase\api\lib directory. This may result in compiler errors when using the
API.
Calc Time
Degrades from FixPak 10 to FixPak 12 for DB2 OLAP Server V1.1. (21772,
P2)
Calc script time increases from FixPak 10 of DB2
OLAP Server V1.1 (5.0.2 P10) to FixPak 12 (5.0.2 P12).
User with
Create/Delete Permissions Cannot Edit Users. (21810,
P2)
Two users have been provided with Create/Delete user
permissions and without Create/Delete user permissions respectively. If you
attempt to edit the second user while logged in as a first user who has
Create/Delete permissions, the check boxes are grayed out.
Huge Formulas
with Many Member References Can Cause an Essbase Internal error. (21821,
P2)
If a formula (attached to a member in an outline or
in a calculation script) involves references to more than a 1000 members,
Hyperion Essbase server can report an internal error "Calculator Stack Contains
a NULL Object."
Not All Data
Returned When Buffer Size Is 32K. (21838, P2)
When the API call
EsbGetStringBuf is used on a particular report with a buffer size of 32767,
records are skipped in the report. The report is correct with the buffer size is
32766.
Retrieval on
a Target Database Crashes the Target Application. (21876,
P2)
Retrieval across transparent partitions with
attributes could cause crashes in certain cases.
Data Load
Causes Error on the UNIX Server. (21884, P2)
On UNIX platform, loading
data with text file and rules file may generate error message, " unknown
member[...] found while processing string [...]."
In the
Application Manager, the RUN Button in the Calc Script Editor or Report Writer
Dialog Box Is Enabled When the Database Is (all dbs). (21901,
P2)
When a calc script or a report file is created and
saved in the (all dbs) database dialog box in Hyperion Essbase Application
Manager, the RUN button is enabled which actually should not be
enabled.
Unable to Set
Calc Scripts as Default Calc with FIX, LOOP, and IF Statements. (21909,
P2)
If a calc script containing FIX/LOOP/IF statement is
set to serve as default calculation, Essbase crashes. The same calc script can
be executed as a non-default calculation without any problem. It is the "Set
Default Calc" operation that causes Essbase to crash.
Security
Files May Get Corrupted When Installing Version 1 FixPak 1. (21924,
P2)
When migrating from DB2 OLAP Server Version 1.1 to
Version 7, additional copies of the of the database may get created each time
the server is stopped and started.
Cannot Delete
Server Log if Application Server Is Running. (22035,
P2)
In the Application Manager, an attempt to delete
event log may fail if application server is running. This is fixed in all server
platforms except Windows 95/98.
EssVCascade
Ignores Suppress #MISSING Option. (22044, P2)
The Spreadsheet Add-in
VBA function EssVCascade ignores the suppress #MISSING flag set in Essbase
options.
Changes to
Original and Shared Members on Source Do Not Synchronize Properly to Target.
(22048, P2)
Changes to original and shared members on the source
outline do not properly synchronize at the target outline and produce an error
message in application log, "There is 1 message in the application log
identifying a change that was not applied during outline
synchronization."
Calc Works in
FixPak 11 of DB2 OLAP Server V1.1 (5.0.2 P11) but Causes Exception Log in
Version 7.1 (6.0 P1) (Only with Data). (22142, P2)
In Version 7.1
(6.0 P1) execution of formulas that contain lists of numbers mixed with member
names may cause the application to crash.
EssCell May
Not Work with Dynamic Time Series. (22184, P2)
#MISSING is
returned instead of the Dynamic Calc member value when EssCell is used on a
Dynamic Time Series member (for example, EssCell ("Q-T-D")
).
@AVG Member
Formula in 6.0 P1 Causes the Server to Crash. (22189,
P2)
If a Dynamic Calc member has an @AVG member formula
attached, upon retrieval, zooming in the parent of this member causes the server
to crash and generate an exception log file.
Loading Data
with Rules File May Cause Memory Leak. (22349, P2)
Data Load with
4-GB rules file errors after loading 10 million records.
Unloading and
Loading a Database in Read-Only Mode, Does Not Start the dbwriter. (22411,
P2)
When a database is unloaded, while in read-only mode
and loaded back again, the dbwriter is not started. So the data operations
following this sequence crash the application when it tries to initiate the
dbwriter.
The following problems are fixed in FixPak 1.
Server
Ignores Formulas With Members which Contain a Dot in Their Names. (15758,
P1)
The application log gives error 1200324, if you use
a "." in the member name. Furthermore in Application Manager the Dimension
Specification dialog box shows the error: "!!FORMULA NOT
LOADED!!"
No Error Is
Generated for Invalid Formulas. (15815, P1)
No Error Message is
generated if member names with a dot are not quoted.
In a Calc
Script, no Error Is Generated When there Is no Statement After an IF Clause.
(17654, P1)
An IF statement not containing a semicolon is
erroneous and the error should be reported.
Insufficient
Rights to Various Essbase Tasks After Running "root.sh." (17830,
P1)
After running the root.sh file, the ownership of
many files are changed from "arbor" to "root." Also, some files cannot be
opened; for example, the outline file.
If Multiple
Threads Attempt to Use Essbase APIs Concurrently, the API May Become Unstable.
(18117, P1)
Concurrent API calls may cause instability or
crashes because the API is not thread safe.
In
Spreadsheet Add-in, Repeat Member Labels Option May Cause Incorrect Retrieval.
(18734, P1)
During retrievals the Repeat Member Labels Option,
if set to true may change some of the column headers and retrieve incorrect
data.
Cannot Pivot
on Certain Members When Repeat Member Labels Option Is Set to True. (18738,
P1)
When Repeat Member Labels option is set to true in
the Spreadsheet Add-in, the pivot operation works only if mouse points to a
specific cell in the target row. It gives an error for all other cells in the
target row.
Incorrect
Behavior if Repeat Member Labels Option Is Set to True. (18740,
P1)
When the Repeat Member Labels option is set to true
in the Spreadsheet Add-in, the Remove Only or Keep Only operations may not
function correctly.
Status Is
Returned to Cell on a Wrong Sheet After Flashback Is Called. (18802,
P1)
The return value of Lotus Spreadsheet macro may be
displayed on the wrong sheet after the Spreadsheet Add-in Flashback command is
called.
Year-To-Date
(Y-T-D) Changes When Order of Months Changes. (19073,
P1)
In some cases, the Y-T-D data shown in the
Spreadsheet Add-in retrieval differs when the presentation order of month
columns is changed. This bug is a duplicate of 18147, Patch
11.
The Set
Substitution Variable Scope Option in the Formula Editor Shows a Problem.
(19160, P1)
An attempt to reconnect to the server after choosing
set Substitution Variable Scope may result in an error message: "Invalid Login
ID - request [List Applications] failed."
EssOtlQueryMembersEx Does not Handle Label Only Members Properly.
(19207, P1)
The EssOtlQueryMembersEx API command does not return
shared or label only members.
If a Member
Name Is 0 in the Outline, Error: "Data item found before member" May be
Displayed. (19291, P1)
While using the
Spreadsheet Lock & Send feature with data set to 0 or #MISSING the error:
"Data item found before member" occurs.
No Result
When Member Has a Calc Script Formula that Contains Dynamic Member and
Cross-Dimensional Operator. (19393, P1)
#MISSING is returned upon
retrieval of a member if the value of the member is "fixed" by a calc script
that contains a Dynamic Calc member. This bug is a duplicate of 17946, Patch
11.
Users who Are
not Logged Into Application Manager Are not Logged Off. (19469,
P1)
Users who log on to the Application Manager but do
not log on to any applications are not automatically logged off after some
timeout. This bug is a duplicate of bug 18482, P11.
Certain
Foreign Characters May Cause the Spreadsheet Add-in to Freeze. (19479,
P1)
If certain foreign characters are used in the
worksheet or file name, the Spreadsheet Add-in freezes.
Using the
Down Arrow Key in the Linked Reporting Objects (LRO) Causes the System to Crash.
(19489, P1)
In the Spreadsheet Add-in, using the down arrow key
in the LRO browser may cause the system to crash. This problem is specific to
Lotus 1-2-3 R9.0 on Windows NT.
Running
Currency Conversion Calc Script Crashes the Application. (19892,
P1)
The Application Manager may crash when running a
currency conversion calc script on a database that has attribute
dimensions.
A Rules File
that May Be Saved in Application Manager In DB2 OLAP Server 7.1 May not Work.
(19950, P1)
When saved in DB2 OLAP Server Application Manager
Release 7.1, rules file for SQL import failed.
Migrating the
Database Index from DB2 OLAP Server Version 1 Format to Version 7 Format Failed
with the Version 1 .PAG File Size Between 2 GB and 2 GB Minus 8 Kb. (20008,
P1)
This is a boundary case that affected .pag files
whose size is 2 Gb minus 8 Kb when being migrated from Version 1. Note that part
of this fix imposes a maximum file size of 2147475456 bytes (2 Gb minus 8 Kb)
for index and .pag files in Version 7. Files migrated from Version 1 can
be a full 2 Gb on NT and 2147483647 bytes (2 Gb - 1 byte) on
UNIX.
Database
Without Data May Take Long Time to Restructure. (20063,
P1)
With the fix, if the database does not have data,
Link Reporting Objects (LRO), or partitions defined on it, DB2 OLAP Server
will take no time to restructure.
CopyApp
Command May not Function Correctly With Multibyte Characters. (20228,
P1)
CopyApp command functions incorrectly if the source
application name contains multibyte characters; for example, Japanese character
sets such as Kanji.
If Advanced
Online JFS Is not Installed, DB2 OLAP Server Will not Start on HPUX. (20319,
P1)
If Essbase is using vxfs as its disk volumes and if
advanced online JFS is not installed, then direct I/O will not be used, buffered
I/O will be used instead. Otherwise, Direct I/O is used. This is a new behavior
of DB2 OLAP Server Version 7.
Error 1200420
and 1200324: Compiler Errors on Member Formulas. (20325,
P1)
Member formulas with IF, ELSEIF, and ENDIF
statements may generate compilation errors and be ignored.
Performance
Fixes for Formula Calculation Using Certain @IS* Functions. (20679,
P1)
Fixed problem which caused performance degradation
in formula calculator on cubes with large blocks; optimized @ISLev(dimName,
levName | levNum),@ISGen(mbrName) functions and also, other functions from this
family.
DB2 OLAP
Server 7.1 May Freeze on UNIX Platforms. (20684, P1)
DB2 OLAP Server
7.1 may freeze on some faster UNIX platforms.
When the
Spreadsheet Add-in Is Installed in Excel, Excel Is Unusable from Within Internet
Explorer (IE) V5. (20688, P1)
When the Spreadsheet
Add-in is not installed, Excel works fine within IE V5; but if the Spreadsheet
Add-in is installed, basic Excel functionality does not
work.
Occasionally
the Server Crashes When Users Logout After Outline Synchronization. (20717,
P1)
The server may occasionally crash with a "not
responding" error when users logout after outline
synchronization.
DB2 OLAP
Server May Crash Doing CALC ALL on an Outline with Attribute Dimensions. (20727,
P1)
CALC ALL on an outline with attribute dimensions may
cause Hyperion Essbase to crash.
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.
----------- For OLAP Integration Server:
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 Essbase and Essbase Integration Services 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. WORKAROUND: Start Essbase Integration Services in a directory that is in a file system that supports longer names.