FixPak Date: November 2002
Service Levels:
FixPak 1 is the equivalent of Release 6.5.1 of the Hyperion products.
Hyperion maintenance levels are cumulative; each level contains new fixes
and all the fixes for the previous maintenance levels.
To stop Windows NT and Windows 2000 services:
echo $SHELL
If the returned value is: /usr/bin/csh, change your shell to Korn Shell with this command:
setenv SHELL /usr/bin/ksh
The Korn Shell persists as your shell until you logout your current session. When you log in again, your shell reverts to your default shell, which is C Shell in this example.
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp01/olap_win/wincd.zip
If you are installing from a CD, copy the file to the temporary directory. If you have installed clients on other computers, you need to download the file to those computers, too.
To start the installation:
To start the server installation:
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp01/olap_win/wincd.zip
If you are installing from a CD, copy the file to the temporary directory. If you have installed clients on other computers, you need to download the file to those computers, too.
To start the installation:
You need to download a number of files that contain the product code and documentation. The number varies according to how many operating systems you use and which documentation you want. You can download the files from here:
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp01/eas/
Important installation tips:
You need to download a number of files that contain the product code and documentation. The number varies according to how many operating systems you use and which documentation you want. You can download the files from here:
ftp://service.software.ibm.com/ps/products/db2olap/fixes/v81/fp01/eas/
Important installation tips:
To read the Administration Services documentation and begin the installation, see Installing the FixPak for DB2 OLAP Server Administration Services.
To read the Enterprise Services documentation and begin the installation, see Installing the FixPak for DB2 OLAP Server Enterprise Services.
The following links work only after you finish installing the FixPak, or if you are reading this from the DB2 OLAP Server Web site. These links do not work while you are running the installation program. The documents displayed by these links refer to the OLAP products by their Hyperion names, not by their IBM names.
User-Defined Tables
In DB2 OLAP Integration Server 8.1 FixPak 1, you can create your own user-defined tables. These virtual tables, which behave as a standard RDBMS view, can be used anywhere a regular RDBMS table or view is used. This feature enables you to create and edit OLAP models without altering your relational schema or modifying the Integration Services generated SQL.
You create a table in the new User-Defined Table Definition dialog box by simply entering a name for the table and entering its SQL definition. The new table is listed in the left frame of the OLAP model main window.
Drill-Through From Secondary Data Sources
With DB2 OLAP Integration Server 8.1 FixPak 1, you can create and run a drill-through report using both primary and secondary data sources. In previous versions of Integration Services, a system administrator could define primary and secondary data sources from which to load members and data; however, the system administrator could only create drill-through reports from the primary data source.
FixPak 1 enables the OIS system administrator to create a drill-through report that accesses data from the primary data source and to create other drill-through reports that access data from a secondary data source. With this feature, the spreadsheet user can drill through to data from multiple data sources that display on multiple sheets within a single workbook.
Enhanced Support for Recursive Hierarchies
DB2 OLAP Integration Server 8.1 FixPak 1 greatly enhances the support for recursive hierarchies by enabling you to perform the following tasks:
DB2 OLAP Integration Server 8.1 FixPak 1 gives you the option of saving your customized drill-through report filters for later use. After you select and modify a system-generated drill-through report with the Spreadsheet Add-in, you can elect to save the filter and store it in the OLAP Metadata Catalog. Later, you can pick and choose from a list of your customized report filters when performing a drill-through query using the Spreadsheet Add-in.
Replace Zeroes with #MISSING Option
DB2 OLAP Integration Server 8.1 FixPak 1 gives you the option of substituting zero values with the string #MISSING during data loads. This action provides several immediate benefits:
Protection of Changes During Disconnects
DB2 OLAP Integration Server 8.1 FixPak 1 prevents the loss of any changes to your OLAP model or metaoutline if you are disconnected from your data source, DB2 OLAP Integration Server, or the OLAP Metadata Catalog. This protection covers all changes that you enter while editing an OLAP model or metaoutline. Should a connection be lost, OIS lets you reconnect to the source, catalog, or server as needed.
OLAP Model Save As and Rename Commands
DB2 OLAP Integration Server 8.1 FixPak 1 extends the options available when you save an OLAP model. Earlier versions of Integration Services did not keep associated metaoutlines when an OLAP model was saved under a different name. Consequently, you were required to rebuild the metaoutlines for the new OLAP model.
In FixPak 1, the Save As command is modified and a new Rename command is provided. These commands enable you to choose among the following options when saving an OLAP model:
DB2 OLAP Integration Server 8.1 FixPak 1, when you create or update an OLAP Metadata Catalog for the first time within a new release, a set of scripts is automatically run. These scripts enable you to migrate to the current release of Integration Services from your earlier version. Starting in FixPak 1, you can migrate automatically from all earlier versions.
Rapid Display of Tables
DB2 OLAP Integration Server 8.1 FixPak 1 displays up to 50,000 tables within the left frame of the OLAP model main window in significantly less time than was required in previous releases. Earlier versions of Integration Services read all the tables and all the columns in retrieving needed data; FixPak 1 reads the table names only and retrieves detailed information later when you expand the tables. This feature enables companies with very large data sources to import source tables rapidly for use in creating OLAP models.
Expanded Support of RDBMS Data Types
DB2 OLAP Integration Server 8.1 FixPak 1 adds several data types to its list of supported RDBMS data types on DB2 and SQL Server. For these databases, FixPak 1 supports the following additional data types:
DB2 OLAP Integration Server 8.1 FixPak 1 gives you the option of resetting your OLAP database prior to a member load or a member and data load. This feature can significantly reduce the amount of time required for the load.
Earlier versions of OIS provided you with the option to “Delete all members first” before a member load or a member and data load. Deleting all members first required that the OLAP outline be opened. If the outline was large or if there were drill-through reports in the outline, a significant amount of time was needed to open it. By enabling you to reset the OLAP database prior to the load, DB2 OLAP Integration Server 8.1 FixPak 1 empties the database outline, thus eliminating the necessity of opening it before the load can be started.
Cancel Button in View Sample
In DB2 OLAP Integration Server 8.1 FixPak 1, the View Sample operation has been modified so that you can cancel the operation at any time without exiting from Integration Services or losing any changes that you have made to an OLAP model or metaoutline. This feature prevents time-consuming system processing and server disconnects when accessing an excessive number of data rows in the relational source.
The instructions for silent installation are mislabeled in the Installation Guide as applying only to DB2 OLAP Server Miner. You can use the instructions in "Installing DB2 OLAP Server Miner on Windows" to do a silent install for DB2 OLAP Server on Windows as well as OLAP Miner.
If you use silent install for both DB2 OLAP Server and for OLAP Miner, ensure you copy the setup.iss file for OLAP Miner into a different temporary directory, or the file will overwrite the one for DB2 OLAP Server.
Configuring your spreadsheet program manually
If you have Lotus 1-2-3 or Excel installed before you install DB2 OLAP
Server, the installation program for DB2 OLAP Server detects the spreadsheet
program and configures it to work with OLAP applications. But if
you install Lotus 1-2-3 or Excel after installing DB2 OLAP Server for the
first time, you must configure the spreadsheet program manually.
Follow these steps:
If license error occurs when installing on UNIX, leave "other"
directory blank
If you are running the installation and you reference an "other" OLAP directory for the license information, and the installation cannot detect the directory, leave the directory blank on the panel where you are prompted for the "other" directory. The installation continues, and later in the installation process you are prompted for the license information.
On UNIX, use only the FixPak installation to add components
After you install FixPak 1 or later on UNIX, you must use the FixPak installation program to add any additional components to your UNIX system. If you run the GA-level installation program after installing FixPak 1 or later, the license program causes an error. After you enter the license information you are prompted with a list of OLAP components. The products detected on your existing 8.1 installation will be checked and you can check additional products to add to the installation.
On Windows, stop servers before running Modify Component or License Information
In the Windows installation program, on the Setup - Maintenance panel, when you select the Modify or Repair actions, the installation program attempts to stop the server components so they won't interfere with the action. Under some circumstances, the servers might not stop successfully. IBM recommends you manually stop the servers for all DB2 OLAP Server products before running the Modify or Repair actions.
On AIX, do not use the "./olapisvr" command to start the OIS server
On AIX, if you try to start the server component of DB2 OLAP Integration
Server using the command './olapisvr', a core dump occurs. To start
the server successfully, invoke the $ISHOME/hisjava.sh file
to set up the OIS environment variables, and then run the olapisvr
command to start the server. For example:
Tip for using 'Aggregate Missing Values'
If your database allows or requires 'Aggregate Missing Values' setting set to YES, then you may want to consider using ZLIB as the compression scheme. ZLIB particularly works well on such databases compared to other compression schemes. However, changing the aggregate missing values setting may have an impact on calculation results - see the Database Administrator's Guide. Consider using ZLIB only if you have already determined that the setting should be YES for other reasons.
Tip for validating outlines that use formulas with customer-defined functions
Outlines containing formulas that use custom-defined functions (CDFs) cannot be validated on the client. Outlines containing CDFs must be validated on the server.
Installations on UNIX require adding $arborpath/dll to LD_LIBRARY_PATH
Currently, the Installation Guide states that you need to set $arborpath/dlls to LD_LIBRARY_PATH before you can run SQL Interface. In fact, you must set $arborpath/dlls to the LD_LIBRARY_PATH environment variable for any UNIX installation regardless of whether you use SQL Interface. (28270)
New configuration setting to support ragged hierarchies
A new configuration file setting, HARAGGEDHIERARCHY, enables support of null values in columns of dimension tables that are used to create dimensions for Hybrid Analysis-enabled outlines. The dimension build that these dimension tables result in the outlines are known as ragged hierarchies.
NOTE: The HARAGGEDHIERARCHY setting is not valid for the Accounts dimension.
If you have null values in columns of dimension tables used to create
dimensions in an Hybrid Analysis-enabled outline, use the HARAGGEDHIERARCHY
setting in essbase.cfg to enable Hybrid Analysis to account for
these null values during SQL generation.
Syntax
HARAGGEDHIERARCHY [appname [dbname]] TRUE | FALSE
| appname | Optional parameter. If you supply an application name, the setting applies to all databases within the named application. If you do not supply an application name, the setting applies to all applications and databases on the server. |
| dbname | Optional parameter. If you supply a database name and an application name, the setting applies only to the named database. If you do not also provide an application name, the database is ignored and the setting applies to all applications and databases on the server. |
| TRUE | Setting the value to TRUE enables Hybrid Analysis to account for null values during SQL generation. Note that this setting may have impact on performance because SQL generation is not optimized well on most relational databases. |
| FALSE | Setting the value to FALSE prevents Hybrid Analysis from recognizing the null values or gaps in the ragged hierarchy. This option does not affect performance. The default is FALSE. |
(56003)
Correction to Hybrid Analysis Configuration File Settings
The following Hybrid Analysis configuration file settings are missing the application and database parameter in the documentation. Specifying the application and database is optional and lets you apply the configuration setting at the application, database, or global level. The correct syntax is given below:
HAENABLE [appname [dbname]] TRUE | FALSE
HAMAXNUMCONNECTION [appname [dbname]] n
HAMAXNUMSQLQUERY [appname [dbname]] n
HAMAXQUERYROWS [appname [dbname]] n
HAMAXQUERYTIME [appname [dbname]] n
HARETRIEVENUMROW [appname [dbname]] n
ODBCINI Environment Variable Needs to be Set for UNIX Platforms
To run Hybrid Analysis on UNIX platforms, set, in the .profile, the ODBCINI environment variable to $ARBORPATH/ODBC.INI, which contains the definition for the relational data source. (55168)
Quicklogin No Longer Required to Start Parallel Login Processing
To enable parallel login processing when you start DB2 OLAP Server, you no longer need to specify essbase password -quicklogin or set the QUICKLOGIN command in the Essbase configuration file. DB2 OLAP Server automatically starts up with parallel login. (55520)
Incremental Restructuring Turned Off When Adding Shared Members
Adding shared members to an outline automatically turns off incremental restructuring. (55467)(55470)
Correction for EsbGetDatabaseInfo Example
The example for the EsbGetDatabaseInfo Visual Basic API documentation contains errors.
The following sample code is incorrect:
If sts = 0 Then For n = 1 To Items sts = EsbGetNextItem(hCtx, ESB_REQINFO_TYPE, Items) Next End IfThe correct code is:
If sts = 0 Then For n = 1 To Items sts = EsbGetNextItem(hCtx, ESB_DBREQINFO_TYPE, DbReqInfo) Next End If(43501)
Correction to Hybrid Analysis Guidelines
The following information updates the documentation in Appendix D of the Database Administrator's Guide:
Hybrid Analysis has some guidelines with which you should be familiar:
Correction to ESTIMATEFULLDBSIZE Documentation
The following text corrects the ESTIMATEFULLDBSIZE ESSCMD documentation in the online Technical Reference.
Outlines that contain sparse formulas of any type or topdown formulas are not supported. Results of the estimation on such databases may be invalid.
Syntax
ESTIMATEFULLDBSIZE
Description
You can select an application and database, then issue this command. DB2 OLAP Server returns the number of blocks the database creates. The database can have all data loaded, or it can have a random sampling of data loaded.
Example
Assume that you have fully loaded Sample Basic. Use this command before
calculation to predict the number of blocks that the calculation would
create if it were executed. This example shows the command and the output
that results:
estimatefulldbsize;
Estimated count of blocks after full calculation = 335
Time elapsed to calculate this estimation = 0.02 seconds
(55822)
Range List Requirement Removed
Functions that take a range list as a parameter no longer require that the list contain only members from the same dimension. (39993)
The online help for the Edit URL dialog box does not work. 17408
(19807)
When you select Edit URL from the Linked Object Browser dialog box
and click Edit and then Help, the Spreadsheet Add-in displays an error
message and the help topic fails to appear.
In the Spreadsheet Add-in, the style selected for drill-through reports
is applied to all members in a dimension at the same level or below that
of the member with the drill-through report. 20724
If any member of a dimension has a drill-through report available,
and Integration Server Drill-Through is selected in the Essbase > Options
> Style tab of the Spreadsheet Add-in, all members of that dimension at
that level or below are displayed as having drill-through reports.
The Getdbstate Esscmd may fail to return the correct value for Concurrency
Wait. 21276 (24720)
The Getdbstate Esscmd incorrectly returns a zero value for Concurrency
Wait.
In some cases, Hybrid Analysis may round relational data using incorrect
precision. 22946
DB2 OLAP Server V8.1 may round all of the data from relational
sources to the same precision regardless of data type. In FixPak 1, Essbase
uses the column definitions from the fact table columns to generate expressions
in the select list with the correct casting. The fix for this problem is
to have Essbase HA use the precision described in the relational data.
Repeated calculations that fix on sparse members might run slowly
due to excessive fragmentation. 24882
If you run repeated calculations or data loads affecting the same set
of data blocks, subsequent calculation or data load times may deteriorate
because of excessive fragmentation. In FixPak 1, the effects of fragmentation
due to repeated loads or calculations is minimal and there should be no
drastic degradation in performance.
Calc script validation may fail to detect certain errors. 25734 (30211)
A calc script that fixes on one of the members to be calculated does
not generate errors during validation, and running the calc script crashes
the application. The validation now detects the error.
Copying a database during a data export may fail. 27608
Copying a database during a data export may fail if the original database
and the database created by copying the original have the same name.
In the Spreadsheet Add-in, the Essbase > Cascade option creates a
file in which the timestamp is not NLS enabled. 27656 (32684)
The cascade option creates worksheets and a file containing an index
of the worksheets. The timestamp in the index file is not NLS enabled,
that is, the format of the date is mm-dd-yy, instead of the format required
by regional settings.
Data load via transparent partition may fail. 27759
You can load data remotely to the source database of a transparent
partition by loading the data to the partitioned area of the target database.
This bug may cause the remote data load to fail with the following error
message "(1014004) Unable to Update Members Which Have Not Been Locked."
Calculating a database using a calc script with at least one formula
may cause the application to crash. 27911
Running a calc script with at least one formula may cause the application
to crash and cause DB2 OLAP Server to create an exception log.
The @ROUND function may produce different results in DB2 OLAP Server
V1.1 than it does in V7.1. 27971
Calculations that use the @ROUND function may have different results.
In the Spreadsheet Add-in, retrievals that return exactly 256 columns
may fail. 28121
Any retrieval or spreadsheet operation, such as a pivot or drill down,
that returns exactly 256 columns may fail.
The OLAP server may crash during a database copy if the security
file is very large. 28271 (33419)
Copying a database with a very large security file (73MB), may cause
the OLAP server to crash.
Spreadsheet retrievals with all members in the same column may crash
the application. 28342 (33499, 33113)
Certain spreadsheet retrievals that have unusual formatting, such as
displaying all members in a single column, may cause the application to
crash.
LDAP Authentication does not work using Active Directory. 28417
An externally authenticated DB2 OLAP Server user cannot log in using
LDAP parameters when the external LDAP repository is Microsoft Active Directory
on Windows 2000.
Parallel calculations that use the Calc TwoPass calculation command
may crash the application. 28718
Running a parallel calculation that uses the Calc TwoPass command may
crash the application.
Certain spreadsheet retrievals may misalign column headings and data.
28728
In spreadsheets that have Use Both Member Names and Aliases for Row
Dimensions selected (in Essbase > Options > Display tab), and have row
members placed between two columns, retrievals may misalign the column
headings and data.
The UPDATEVARIABLE command may fail to update substitution variables.
28849
The UPDATEVARIABLE command fails to update substitution variables when
the case does not match that of the original database and application.
After updating substitution variables using the UPDATEVARIABLE command,
the new variables are displayed in the Application Manager under Server
> Substitution Variables, but a spreadsheet retrieval returns the old
variables and their associated values.
The OLAP server may crash when connecting to Analyzer. 29039
When running on the Solaris 8 platform, the OLAP server may crash when
connecting to an application via DB2 OLAP Server Analyzer 7.1 (Hyperion
Analyzer 5.0.3).
Certain queries may crash the application. 29187
Retrievals of dynamic calc members with member formulas containing
the @PRIOR function may cause the application to crash.
Linked Partitions may not work. 29190
Drilling down on partitioned target members may not launch the linked
objects browser.
Calculations that use the CALC DIM calculation command may crash
the OLAP server. 29211
Using the CALC DIM calculation command with the dimension names listed
out of outline order may crash the OLAP server and generate an exception
log.
Essbase error while clearing database. 29225
When INCRESTRUC TRUE is specified in the essbase.cfg file,
clearing data may fail and may result in the error "Unable to free
aligned memory for [datctxp->ppDatMemPage[]]in[adDatTermDatCtx]."
The results of calculations that use SET AGGMISSG ON may be incorrect.
30739
Some calculations that include the command SET AGGMISSG ON may fail
to aggregate the missing values, thereby resulting in incorrect values.
A calculation fails to use the correct values for substitution variables
that have been changed using EsbCreateVariable. 33115
Values for substitution variables that have been created or changed
through the Visual Basic API function EsbCreateVariable() might not be
evaluated correctly by subsequent calculations.
Calculating currency conversions may take longer than expected. 33869
Running the CCONV calculation command on Currency Conversion applications
may take longer than expected.
The MaxL Perl Module may limit the length of query results to 128
characters. 35170
Query results from the MaxL Perl Module may be truncated if they are
greater than 128 characters in length.
Cannot view connection information in the Application Manager during
a dimension build. 36451
While running a dimension build, you cannot access Security > Connections
from Application Manager for any application on that OLAP server.
The memory used when starting the OLAP Server increases as the setting
for CALCLOCKBLOCKDEFAULT is increased. 36822
The OLAP Server uses relatively more memory at startup when the CALCLOCKBLOCKDEFAULT
is higher than it does when this setting is lower.
Attribute queries containing upper-level attribute members that have
implied share base members may return incorrect results. 36982
Queries from databases with upper level attribute members that have
level-one base members with only one child may return incorrect results.
Memory leak when running calculations that use the @XREF function.
37090
Calculations that use the @XREF function may fail and may result in
the error message "Unable to Allocate Memory"
Some calculations may be incorrect in DB2 OLAP Server V8.1 that were correct in previous versions. 37742, 40027, 40039
Spreadsheet retrievals that have the same member in two consecutive
rows may fail. 43242
Spreadsheet retrievals that have the same member in two consecutive
rows worked in earlier releases, but in V8.1 the same spreadsheet retrievals
fail with the error message, "A column item [] conflicts with a row item
[]."
Spreadsheet retrievals that use certain styles may crash Excel. 43248
Using styles for linked objects, read only cells, or read/write cells
may cause Excel to crash during spreadsheet retrievals.
Spreadsheet retrievals from transparently partitioned databases with
attribute dimensions may crash the application. 43306
Retrieving from a database that has attribute dimensions and is the
target in a transparent partition may crash the application.
The VB API EsbGetDatabaseState incorrectly reports that "Two Pass
Calculation" is not selected even though it has been selected through the
Database Administrator. 43321
The Database Administrator interface does not set the CalcTwoPass field
in the ESS_DBSTATE_T structure used by the Visual Basic API function EsbGetDatabaseState().
The function incorrectly returns that "Two Pass Calculation" is not selected
when "Two Pass Calculation" was set through the Database Administrator
(through Database > Settings > General tab).
Data loads from files with a large number of columns may fail because
of excessive memory usage. 43433
Certain free form data loads from data files that have a large number
of columns may fail because of excessive memory usage. Data files created
by exporting data from a database with a large number of sparse members
may have a large number of columns.
The SQL Drill Through Add-in (DB2 OLAP Server V.1. FixPak 14) may
fail to work with the V8.1 DB2 OLAP Server and Spreadsheet Add-in. 43499
After installing the V8.1 level of the OLAP server and Spreadsheet
Add-in, and the V1.1 FixPak 14 SQL Drill Through Add-in, SQL Drill Through
fails to appear in Essbase pull down menu of the Spreadsheet Add-in.
Retrieving dynamic time series data using the Esscell function may
fail. 43553
The Esscell function may incorrectly return zeros for dynamic time
series data.
Deleting databases may not delete data that resides on spanned disk
volumes. 54953
Using ESSCMD or Application Manager to delete databases may fail to
delete .pag files from the spanned disk volumes.
Parallel calculations may crash the application under certain circumstances.
55126
Parallel calculations may crash the application if the calculation
includes a sparse dynamic calc member that (1) consolidates into its stored
parent and (2) has a formula that causes a top down calculation.
Spreadsheet retrievals may be slower in DB2 OLAP Server V7.1 FixPak
8 and later, and in V8.1, than in V7.1 FixPak 7 or earlier. 55512
Certain spreadsheet retrievals may take longer.
Dimension builds that change consolidation properties may also alter
attribute associations. 55244
Changing consolidation properties using a dimension build rules file
may alter existing attribute associations, causing the outline to become
invalid.
Executing a "kill" command of any kind in UNIX against any type of Essbase process is unsupported. Issuing a kill command, especially on a database that is calculating, has a high probability of corrupting the database.
If all supported methods of shutting down an Essbase process have been exhausted, and a kill must be executed, heed the following precautions to reduce the amount of damage to the database:
Hybrid Analysis Known Issues
Hybrid Analysis supports only DB2 using native drivers or Meant drivers, Oracle ODBC using Meant drivers or native drivers, and SQL Server. See the Installation Guide for details about platform release levels and drivers supported.
If your system has Oracle ODBC drivers and you plan to use Hybrid Analysis, you must upgrade to Oracle 8.1.6 or later (30531). Enabling Hybrid Analysis while using Oracle ODBC drivers earlier than 8.1.6 causes the following conditions:
MaxL Known Issues
V8.1 of the MaxL Perl Module (essbase.pm) works with V8.1 of the DB2 OLAP Server. It is not compatible with previous releases of DB2 OLAP Server.
Although the limit for stored Essbase calculations is 64 KB, calculation scripts created in MaxL that have multi-byte characters cannot exceed 40 KB.
Database notes created using MaxL appear stripped of newline-character formatting when viewed in the Spreadsheet Add-in.
Memory and System Information on Microsoft
Because of a Microsoft system limitation, if you are running DB2 OLAP Server on a Microsoft platform with more than 4 GB memory, the information about memory and disk swapping in the System Information tab of the Server Information dialog box may be incorrect.
$ISHOME/odbc/merant40
Please see the Installation Guide for information on updating
environment variables in UNIX.
(54870)
| Problem
Number |
Description | |
| IBM6154 | On Windows, if you are logged on with a user ID that does not have administrator privileges, and you try to run the Modify License utility, an error occurs. Ask your server administrator to run the utility for you. Additionally, if you run the Spreadsheet Add-in with a user ID that does not have administrator privileges, you might see a message such as, "Error loading USE or USELSX module lsx123.dll". To prevent this message from occurring, manually remove the Spreadsheet Add-in from the spreadsheet program for this user ID, using the spreadsheet interface. | |
| IBM6193 | On Windows 98, if you run silent install, you might encounter this error: "Sharing Violation Reading drive C... Abort, Retry, Fail." If you type Fail, the installation completes successfully. | |
| 16412 | In Excel, in Query Designer, the server location radio button may not be active in the "Hyperion Essbase Query Designer Save As Query" window when you try to save a query. This occurs because a selected cell is in Edit mode. If you are typing in a cell, Essbase menu items do not function, although they appear enabled, until you get out of Edit mode. | |
| 17023 | If a member name contains the ampersand (&), even if it is surrounded with quotation marks, and if the member name is in a calculation script, the script may fail validation if the user has Application Designer permission. DB2 OLAP Server incorrectly interprets the ampersand as the signal for a substitution variable. If you run the script without validation, it performs the calculation correctly. Users with supervisor privilege do not receive this validation error. | |
| 17253 | DB2 OLAP Server does not support discontinuous selection in Lotus, although it does in Excel. | |
| 17267 | At the end of a calculation started in Lotus, a dialog box appears with a message that the calculation is complete. Clicking on the dialog box does not close it. Press Esc/Cancel from the keyboard to close the dialog box. | |
| 17927 | DB2 OLAP Server does not warn you if you request that export results be written to a file that already exists. Essbase overwrites the existing file. | |
| 17957 | If you create a dimension build rule that uses "Create Using Text" on the last column, and if the last true field in the input file is an "Alias" column that has some blank records, the text generated by the "Create Using Text" feature will not be placed into the last column, but will be placed in any record where the "Alias" column is blank. The rule, which passes validation, will fail during the build. To correct, delimit the blank fields. | |
| 18015 | Leaving the Spreadsheet Add-in idle for long periods of time may cause extra "Please Log In" messages, because the user may have been logged out due to inactivity. Click OK until the message stops appearing. | |
| 18041 | DB2 OLAP Server may not be able to open a file if the directory location contains a space. This is true for all files such as load files, rules files, calculation scripts, etc. Consider moving the file so that there are no spaces in the directory path. | |
| 18046 | When logged in with database designer privilege, the entire list of users is displayed in Security > Database, even though only the list of users that the database designer has privileges to modify should appear. Attempts to modify users for whom database designer should not have privileges will not be successful. | |
| 18342 | If you use Set Member Filter in EQD, any MBCS values may display as broken characters. Type the values into Notepad, and then copy and paste them over the broken characters. | |
| 19288 | Using Dynamic Time Series (DTS) members on a partitioned database may
cause a server crash if these conditions are true:
|
|
| 19522 | When compiling client API programs on NT, with MS VC ++ version 6.0
and higher, you may experience API program crashes if you have used a constant
string assignment to a CHAR pointer, such as:
char * name = "myname";Workaround: Do not use a constant string assignment to a CHAR pointer, or use only ESSBASE data types. |
|
| 19632 | Valid calculation scripts with a FIX command and nested parentheses within the FIX command may not validate in the Calc Script Editor of the Application Manager and may report spurious errors. The same script will run without problems on the server. | |
| 20203, 30329 | If you start DB2 OLAP Server as a service on NT, you can
ignore this message, it is informational only:
The description for Event ID ( 0 ) in Source ( EssbaseService ) cannot be found. It contains the following insertion string(s): EssbaseService error: 0, Starting Essbase Service.... |
|
| 20775 | If you use the Query Designer to change members in a spreadsheet,
then select a dimension and choose Essbase > Cascade, and then in
the Destination Options tab, select the option "One Workbook, Separate
Sheets," you may receive the Microsoft Visual C++ Runtime Library error:
Runtime Error! C:\Program Files\Microsoft Office\Office\Excel.exe....abnormal program termination! error. |
|
| 22233, 23800, 23344 | Running too many concurrent reports may overwhelm product or operating system resources, especially against partitioned databases. If this occurs, reduce the number of such reports running concurrently. | |
| 22999 | If, during outline revision, you delete a member with a
particular alias name, and then create a new member with the same alias
name, the alias will fail to register and DB2 OLAP Server creates the new
member without an alias.
Workaround: Either delete the alias from the Outline Editor and save, or use a different alias name when revising. |
|
| 23086 | Due to a Microsoft bug, you may not be able to display the Spreadsheet Add-in in IE 5.0 if you are running on operating system NT4.0. If you try to open an .xls file from IE 5.0 on NT4.0, the spreadsheet may open in a separate window. | |
| 23374 | The application log, when displayed via Application Manager, may incorrectly fail to show some log entries for the current day because it evaluates the time using GMT. To view missing log entries, select "All Dates." | |
| 23974 | Trying to associate an attribute with an implied shared member causes the association to be ignored, and Essbase writes a message to the application log. An implied shared member is a member with only one child. | |
| 24044 | For EssOtlQueryMembers on UNIX, the currency conversion
type returned is incorrect.
Workaround: Use EssOtlFindMember instead. |
|
| 24350 | When the installation program for SQL Interface asks you to specify a driver, if you specify Merant, you won't be able to use DB2 Native drivers, and if you specify DB2 Native drivers, you won't be able to use Merant drivers. | |
| 24351 | Some characters, such as those using umlaut or accent marks, cannot be typed in ESSCMD interactive mode. | |
| 25659 | If you use a partition definition where one or more member functions in the definition resolve to an empty set, then DB2 OLAP Server may write more than one message in the application log when you validate the partition. Each message has the same information about a member function resolving to an empty set. All but the first message in the sequence can be ignored. | |
| 26028 | If you enable parallel calculation (CALCPARALLEL or SET
CALCPARALLEL greater than the default 0) on a database that is part of
a transparent partition, increase the value of SERVERTHREADS for each source
database that is part of the transparent partition, using these rules:
|
|
| 27139 | If you use Hybrid Analysis with source data in Oracle,
in either of these situations, you must use Oracle version 8.1.7 or higher:
<ROW (Market) [HA-enabled dimension] <DESCENDANTS (Market) |
|
| 27171 | If you use direct I/O, and have set DLTHREADSWRITE to a value of 16 or greater, Essbase may crash during a parallel data load. If you encounter this error, reduce the number of block write threads by lowering the value of DLTHREADSWRITE to 15 or less, then restarting Essbase. | |
| 29248 | When running DB2 OLAP Server V7.1 FixPak 5 or V8.1 on Windows 2000 or Windows NT systems, using the EsbSetActive Visual Basic API in code samples in Microsoft Access 2000 may crash Microsoft Access. | |
| 31691 | You must save a rules file and the data file it uses to the same ARBORPATH/App/database_name directory as the database whose outline you are working with. | |
| 33810 | On AIX, due to limitations of the operating system, the information displayed in the System Info tab and License Info tab (or equivalent if retrieved outside Application Manager) may be unavailable. | |
| 43247 | Visual Basic API does not support VB.net at this time. | |
| 43406 | In DB2 OLAP Server V8.1, Application Manager is unable to modify an outline or load data if the text file is located in a different application database directory on the same server. | |
| 55620 | Adding both shared and non-shared members to a parent in
the outline of a partitioned database may cause the application to crash
and may cause an access violation error.
Workaround: Change the order in which the shared and non-shared children are listed in the outline under the parent. The non-shared children should be listed first and the shared children should be listed at the end of the outline. |
|
| 55837 | After importing a large number of LROs (for example, over
100 LROs) using MaxL or Administration Services, restructuring the outline
may cause the database to crash.
Workaround: Increase the index cache size from the default value of 10240 KB using the alter database MaxL statement, the Index Cache setting in the Database Properties window (Caches tab) in Administration Services, or the Index Cache setting in the Database Settings dialog box (Storage tab) in Application Manager. |
|
| 55926 | Before using the MaxL alter database statement to
get invalid block header information for a given database, be sure that
the server is not performing other operations, such as calculations or
dataloads; otherwise, an exception error may occur. Before running the
MaxL statement to get invalid block header information, the database administrator
must forcibly log off all users and disable all logins to ensure that no
other users or processes are using the server.
The complete MaxL statement to get invalid block header information is alter database DBS-NAME validate data to local logfile 'FILE-NAME';. |
Licensed
Material - Program Property of IBM
(c)
Copyright IBM Corp. 1998, 2002. All Right Reserved.
US
Government Users Restricted Rights - Use, duplication or disclosure restricted
by GSA ADP Schedule Contract with IBM Corp.
IBM,
DB2, and DB2 OLAP Server are trademarks of International Business Machines
Corporation in the United States, other countries, or both.
Portions
(c) 1991-2002 Hyperion Solutions Corporation. All rights reserved.
Hyperion is a registered trademark and Hyperion Solutions is a trademark
of Hyperion Solutions Corporation.
Portions
(c) Blue Sky Corporation. All rights reserved.