************************************************************

Hyperion Essbase Version 5.0.1
Patch 13 Release Notes

************************************************************

Patch file name: PATCH.HTM

Applies to: All platforms

Patch Date: 9/24/99

Identification: R5.0.1_P13

************************************************************

NOTES:

For important information about client/server compatibility with 5.0.1 patches, see Patch Summary.
If you are installing client products from an Essbase patch release, you must install server products to the same patch level. Using older server versions with newer client versions is not recommended and is not supported.
Arbor Software has merged and is now Hyperion Solutions Corporation. Information in these Release Notes pertaining to Arbor/Hyperion's Web site and/or corporate name reflects this name change. In future releases, the new name will also be reflected in Essbase products and other communications.

Patch Installation Overview

Key

Patch Summary

Problem Summary

Downloading Patches from the Hyperion Solutions Web Site

Files to Download

Installing Patches from the Hyperion Solutions Web Site

Installing Patches from CD-ROM

Patch Installation Overview

This file describes problems corrected by one or more Essbase patches. Even if you have only one of the problems fixed in one of the patches, you need to perform a full patch installation. You can install this patch by downloading the appropriate file(s) from the Hyperion Solutions Web site, or by installing from CD-ROM. For detailed information about Essbase installations, see the Installation Notes.

To see which file(s) you need to download, see Files to Download.

For instructions on installing the file(s), see Installing Patches from the Hyperion Solutions Web Site or Installing Patches from CD-ROM.

Essbase patches are cumulative, beginning with Patch 1 of Essbase Version 5.0.1. That is, each patch contains new fixes, plus all the fixes for the previous patches.

Key

R5.0.1_P13 is Release 5.0.1, Patch 13

R5.0.1_P12 is Release 5.0.1, Patch 12

R5.0.1_P11 is Release 5.0.1, Patch 11

R5.0.1_P10 is Release 5.0.1, Patch 10

R5.0.1_P9 is Release 5.0.1, Patch 9

R5.0.1_P8 is Release 5.0.1, Patch 8

R5.0.1_P7 is Release 5.0.1, Patch 7

R5.0.1_P6 is Release 5.0.1, Patch 6

R5.0.1_P5 is Release 5.0.1, Patch 5

R5.0.1_P4 is Release 5.0.1, Patch 4

R5.0.1_P3 is Release 5.0.1, Patch 3

R5.0.1_P2 is Release 5.0.1, Patch 2

R5.0.1_P1 is Release 5.0.1, Patch 1

Patch Summary

Patch R5.0.1_P13
Patch 13 fixes problems on all server platforms, and 16-bit and 32-bit clients.
Patch R5.0.1_P12
Patch 12 fixes problems on all server platforms, and 16-bit and 32-bit clients.
Patch R5.0.1_P11
Patch 11 fixes problems on all server platforms, and 16-bit and 32-bit clients.
Patch R5.0.1_P10
Patch 10 fixes problems on all server platforms, and 16-bit and 32-bit clients.
Patch R5.0.1_P9
Patch 9 fixes problems on all server platforms, and 16-bit and 32-bit clients.
Patch R5.0.1_P8
Patch 8 fixes problems on all server platforms, and 16-bit and 32-bit clients.
NOTE:
In addition to bug fixes, Patch 8 contains a new ESSBASE.CFG setting which lets you specify whether shared members have Linked Reporting Objects that are unique from those of their corresponding regular members. For more information, see LROs On Shared Members.
Patch R5.0.1_P7
Patch 7 fixes problems on all server platforms, and 16-bit and 32-bit clients.
Patch R5.0.1_P6
Patch 6 fixes problems on all server platforms, and 16-bit and 32-bit clients.
NOTE:
In addition to bug fixes, Patch 6 contains three new groups of Essbase APIs for stream data loading, setting ARBORPATH, and Hyperion Integration Server Drill-Through. For more information, see New Essbase APIs.
Patch R5.0.1_P5
Patch 5 fixes problems on all server platforms, and 16-bit and 32-bit clients.
NOTES:
- Patch 5 code includes a working version of the upcoming Lotus 97 Spreadsheet Add-in, which is in Beta. General availability of this product is scheduled for mid-October 1998, via the Web. Lotus 97 Spreadsheet Add-in files may appear in your Bin directory. These files are untested with Patch 5.
- In addition to Essbase Version 5.0.1 bug fixes, Patch 5 contains (1) revised code and online help for the Hyperion Integration Server Drill-Through feature and (2) three revised spreadsheet online documentation files. For more information, see the following sections:
  - Hyperion Integration Server Drill-Through
  - Revised Spreadsheet Documentation
Patch R5.0.1_P4
Patch 4 fixes problems on all server platforms, and 16-bit and 32-bit clients.
Patch R5.0.1_P3
Patch 3 fixes problems on all server platforms, and 16-bit and 32-bit clients.
NOTES:
- If you install a Patch 2 or later 32-bit Spreadsheet Add-in (e.g., Excel 97), you must also install a Patch 2 or later server. If you attempt to use a Patch 2 or later 32-bit Spreadsheet Add-in with a pre-Patch 2 (i.e., 5.0.1 or 5.0.1 Patch 1) server, spreadsheet retrievals fail with the following error message:
```
Bad Binary Spreadsheet Table
```
  This client/server incompatibility now occurs because of the implementation of Hyperion Integration Server Drill-Through code in Patch 2.
  You may use a pre-Patch 2 Spreadsheet Add-in with a Patch 2 or later server.
- If you have SQL Interface installed and you want to install a patch, you must install the same patch version for both the Essbase server and SQL Interface before restarting the server.
- As of Patch 3, 32-bit Spreadsheet Add-ins provide a new style in the Essbase Options dialog box (Style page). The new option, "Integration Server Drill-Through," allows spreadsheet users to define a style for data cells that have Integration Server Drill-Through reports attached to them.
Patch R5.0.1_P2
Patch 2 fixes problems on all server platforms, and 16-bit and 32-bit clients.
NOTES:
- Patch 2 consisted of two separate patch releases: one for all server platforms except HP-UX, and one for the HP-UX platform specifically ("Patch 2HP"). These two patches are both included in Patch 3.
- In addition to bug fixes, Patch 2 contains: code and online help for the Hyperion Integration Server Drill-Through feature; INTERSOLV's latest ODBC drivers for UNIX; SQL Interface for the HP-UX platform; and two revised spreadsheet online help files. For more information, see the following sections:
Patch R5.0.1_P1
Patch 1 fixes problems on NT or Windows and OS/2 server platforms, and 16-bit and 32-bit clients.

Problem Summary

The following problems are fixed in Patch 13. Unless otherwise noted, these fixes are reflected in the patched server software and do not require a client upgrade; however, we recommend upgrading client and server software to the same patch level.

For the latest list of problems fixed in this patch, connect to Hyperion's Technical Support Web site at:

http://support.hyperion.com/ts

The Time and Date Formats are Incorrect in the Japanese version of Hyperion Essbase (8566, P13)
This fix requires a client upgrade. The Japanese version of Hyperion Essbase does not display the month and day, and time format displayed is incorrect.

Not Enough Virtual Memory for Some Queries (8859, 12721, 14409, P13)
Large queries may cause virtual memory problems.

Month Not Displayed in the Server Information Dialog Box of the Japanese version of Hyperion Essbase (9040, P13)
This fix requires a client upgrade. The System Info tab of the Server Information dialog box is not displaying the month in the Japanese version of Hyperion Essbase.

EssGetMbrInfo Macro Does Not Work With Spreadsheet Add-in for Lotus 1-2-3 Release 5 (9174, P13)
This fix requires a client upgrade. With the Spreadsheet Add-in for Lotus 1-2-3 Release 5, the EssGetMbrInfo macro does not work. With this fix, the macro works correctly, assuming the following guidelines are used:

Connect to the appropriate sheet name using {EssConnect}, rather than Essbase > Connect.
Do not use spaces in between the commas.
The last parameter, indicating where to put the results, should refer only to the sheet name and cell.

Data Retrieval Fails When a Backslash Character ('\') is Present in a Member Name or an Alias Name (9310, 9311, 9312, P13)
This fix requires a client upgrade. Member Selection fails when a member name or an alias name contains a backslash character.

In Certain Cases, Rows are Dropped as a Result of Pivoting the Spreadsheet View (12126, P13)
In certain cases, using the Spreadsheet Add-in for Excel, certain rows are dropped when pivoting the spreadsheet.

Memory Leak Occurs with Consecutive, Repeated Retrievals (12185, 13762, P13)
This fix requires a client upgrade. Consecutive, repeated retrievals in Excel Spreadsheet Add-in cause a memory leak.

In Certain Spreadsheet Views, Pivoting with the "Repeat Member Labels" Option Enabled Causes Unexpected Results (12386, P13)
In certain spreadsheet views, with repeated members, pivoting brings back unexpected results.

Successive Dimension Builds Cause Memory Leak (12463, P13)
The application server (ESSSVR process) uses an increasing amount of memory with successive dimension builds done using an ESSCMD script.

Users or Groups With Application Designer Privileges Cannot Run Their Own Calc Scripts (13297, P13)
Users or groups with application designer privileges cannot run their own calc scripts because the client returns an "insufficient privilege" error message.

"Retain on Keep and Remove Only" Option Causes Application Server Crash (13816, P13)
When the "Retain on Keep and Remove Only" option is turned on, spreadsheet operations using Keep Only and Remove Only to customize the view after retrievals crash the application server.

Keep-Only and Remove-Only Operations Fail When Repeat Member Labels is On (14139, P13)
Some "Keep Only" and "Remove Only" Spreadsheet Add-in operations do not work when the "Repeat Member Labels" option is enabled.

On a Particular Database, Default Calc Fails to Complete when No Data is Loaded (14405, P13)
For a specific database outline, a default calculation on the empty database never completes. In addition to the fix, the data cache setting must be 30MB, and the CALCLOCKBLOCKDEFAULT .cfg setting needs to be at least 107, in order for the reported case to work.

After a Retrieval, a Spreadsheet Cell Displays #MISSING Instead of the Correct Value (14588, P13)
Certain dependent dynamic calc members are not calculated, hence the data values are #MISSING in the spreadsheet.

In the Japanese Version of Essbase, Dimension Build Using String Replacements Fails (14809, P13)
This fix requires a client upgrade. If the rules file uses string replacements of MBCS characters, the build may fail.

Changing Retrieval Modes in Essbase > Options Causes Display Setting Impermanence (14824, P13)
This fix requires a client upgrade. In the Essbase Options dialog box, after switching from Advanced Interpretation retrieval mode to Free Form retrieval mode, and then selecting Suppress #Missing Rows and Suppress Zero Rows on the Display tab, the latter display settings are not retained after clicking OK and then selecting Essbase > Options again.

Replicating Data in a Partition with a Validation Error Causes Application Crash (14852, P13)
In a certain scenario, replicating data in a partition with a validation error causes the application to crash.

Calculation Results are Incorrect When Sparse Members Roll up from Level 0 to Level 1 (14996, P13)
Calculations involving aggregations may be incorrect when AGGMISSING is set to ON.

After Using the @PRIOR Function in a Calc Script, Database Statistics Indicate that an Extra Level-0 Block Has Been Created (15035, P13)
The @PRIOR function used in a calc script (with Create Block on Equation unchecked in Database Settings) may result in Database Statistics showing an extra level-0 block.

A Calculation with Calculator Cache On Returns Different Values than the Same Calculation Run with the Calc Cache Turned Off (15083, P13)
A calc script using arrays is calculated incorrectly when calculator cache is used; for example, by including the following lines in the ESSBASE.CFG file:

CALCCACHEHIGH  30000000
CALCCACHEDEFAULT 10000000
CALCCACHELOW  5000000

Calculations Take Longer After Migration From Patch 7 to Patch 11 (15195, P13)
Calculations may take longer after migration from Patch 7 to Patch 11.

In Spreadsheet Add-in, Dynamic Calc may Produce Incorrect Results (15357, P13)
Using Dynamic Calc in Spreadsheet Add-in may produce random results.

Hyperion Essbase Creates #MISSING Blocks When Option is not Enabled (15371, P13)
Hyperion Essbase creates extra #MISSING blocks when the Create Blocks on Equation option is not enabled.

Renaming Any Member When Outline Logging is Set to True Causes the Server to Crash (15385, P13)
When the OUTLINECHANGELOG parameter is set to True, an attempt to rename a member in the database outline causes the server to crash.

Time Balance Computations Returns Wrong Values For Dynamically Calculated Periods (15416, P13)
Using Dynamic Calc with Time Balance computations returns wrong values.

Changing Database Access of a User Connected through the Spreadsheet Client Causes Crash (15428, P13)
Changing a user's database access from Read Only to Read/Write and vice versa, while the user is attempting to connect to the database and perform a lock and send, causes the application server to crash.

Report Scripts Return Incorrect Results When They Contains a Dynamic Time Series Member (15533, P13)
In a report script, when the innermost column member is a dynamic time series member, the data cells may be moved to the wrong column.

With the Clock Advanced, Viewing the Application Event Log in Application Manager Shows a Blank Screen for Dates Later than 2000 (15608, P13)
With the computer's clock set to a date beyond 2000, viewing the application event log by a date later than 2000 in Application Manager displays a blank screen.

Many Dynamic Calc Members Crashes the Application (15647, P13)
For a particular database, the application crashes during a calculation with the the following calc script, with "Create Blocks on Equation" enabled:

Set cache high;
Set Aggmissg On;
Set Frmlbottomup On;
Set Updatecalc off;
Calc all;

EssRetrieve Macro Retrieves Onto Wrong Sheet in the Lotus 1-2-3 Spreadsheet Add-in (15760, P13)
This fix requires a client upgrade. Using the EssRetrieve macro in the Spreadsheet Add-in for Lotus 1-2-3, a retrieval is done on the active sheet instead of the specified sheet.

Server Crash or Inability to Create a New Index or Data File Occurs After Viewing Database Information (15783, P13)
After selecting Database > Information in the Application Manager, one of the following occurs:

The Server process crashes.
The Server process is unable to create a new index or data file when there is more than enough available disk space in which to do so.

Data Load from Certain Erroneous Data Files Crash the Server (16024, P13)
Loading data from a data file containing duplicate member names (or other errors) crashes the server.

Hyperion Essbase Fails When Users with Read/Write Permission Attempt to Run a Calculation (16147, P13)
Hyperion Essbase fails with an error message during consecutive attempts to run default calc.

Group Rights to Run Specific Calcs Defaults to Run All Calcs (16193, P13)
Group rights to run specific calcs defaults to access rights to run all calcs.

Dense Restructure Occurs After Changing Only Sparse Members in an Outline (16630, P13)
Moving, adding and changing sparse members in an outline causes a dense restructure when saving the outline. With this fix, an index-only restructure takes place upon saving the outline.

Time Balance Computations Incorrect With Some Sparse and Dense Dimension Configurations (16740, P13)
Data calculations may be incorrect when time dimension has a sparse dimension tag and accounts dimension has a time balance tag.

In the Spreadsheet Add-in for Lotus 1-2-3, Cascading Replicated Spreadsheets to a Printer Results in No Printout (16809, P13)
This fix requires a client upgrade. In the Spreadsheet Add-in for Lotus 1-2-3, the Cascade destination-type option of "Printer" (used to print replicated spreadsheets) does not work.

A Spreadsheet Add-in With Limited SKU Crashes While Exiting Excel (17008, P13)
This fix requires a client upgrade. On Windows 95, a Spreadsheet Add-in with limited SKU fails with an error message while exiting Excel.

The following problems were fixed in Patch 12.

Cell Count does not Run Correctly When Using Certain Alphanumeric and Japanese Characters (8680, P12)
The cell count in member selection tools is incorrect when member names consist of certain alphanumeric and Japanese characters.

Connecting to a Second Spreadsheet While Using Aliases in the First Spreadsheet Results in Error Message (9224, P12)
In Hyperion Essbase Spreadsheet Add-in, connecting to a database in the first sheet and enabling the option Use Aliases and Member Names, and then attempting to connect to a second database in the second sheet results in an error message.

With Certain Character Sets, a Retrieval in the Spreadsheet Add-in Changes the Sort Order of Member Names in the Spreadsheet (9286, P12)
With certain alphanumeric and Japanese characters, a retrieval results in incorrect sorting of the database outline members in the spreadsheet.

Multiple Retrievals on Dynamic Calc Members Return Varying Results (11451, P12)
In certain spreadsheets, multiple retrievals on dynamic calc members return varying results. The data in a column changes after about 12 retrievals.

EssVGetDataPoint Produces Network Errors in the Log File (11910, P12)
While retrieving a data range containing a large number of rows, the EssVGetDataPoint API function produces network error #10053, recorded in the log file. Repeated use of the EssVGetDataPoint function can result in a large number of errors in the log file, causing the function to fail and necessitating the shut down and restart of the application.

Application Designer Cannot Access Copied Calc Script (13297, P12)
The Application Designer user cannot access a calc script in the proprietary application when that calc script has been copied over from another application.

Member Comment for EsbOtlAddMember() is not Written to the Outline (13732, P12)
The MbrInfo.szComment field does not get updated to the outline when adding a member using the Visual Basic EsbOtlAddMember() API function.

Saving Outline with Large Member Formula Fails With Option to Create an Outline Change Log (.OLG) (14043, P12)
Attempting to save certain large member formulas to the outline fails when the ESSBASE.CFG file contains the setting OUTLINECHANGELOG TRUE.

Some Year-to-Date Calculations are Incorrect if the Corresponding Level-0 Periodic Members are Dynamic Calc (14256, P12)
In a dense dimension, calculations on level-0 dynamic calc members with formulas may return the wrong results for Year-to-Date dynamic time series.

Japanese Version of Hyperion Essbase for Windows NT Displays Incorrect Login Time (14439, P12)
Incorrect login times are displayed in the Agent window of the Japanese version of Hyperion Essbase for Windows NT.

VB Application Crashes When Calling EsbPartitionPutReplCells() to Replicate Partition Data (14443, P12)
Replicating data in a partition from source to target using the Visual Basic API function EsbPartitionPutReplCells() crashes the application. The same procedure works without problems through Application Manager.

A File Linked Reporting Object (LRO) Cannot be Added to a Lotus 1-2-3 Data Cell (14630, P12)
This fix requires a client upgrade. An attempt to view or launch a file that is attached using the Linked Object option results in an error message. When the user attempts to view the file again, the file is not listed in the Linked Objects Browser window.

The Application Fails When Running Two Calculation Scripts in Parallel (14681, P12)
The application may crash when two concurrent calculation scripts attempt to write to the same data block.

Users Can Add Members to a Group Beyond their Privileges, but the Members Disappear (14827, P12)
A User with Create/Delete Users privilege can add members to a group having higher security privileges. The members seem to be added, only to disappear from the group's list of members. An error message appears only in the log file. With this fix, users with Create/Delete Users privilege cannot add members to a group with higher privileges, or to a group created by a supervisor.

Server Crashes When Creating or Migrating a Large Number of .PAG Files (14931, P12)
When the server is creating or migrating .PAG files, if the number of .PAG files exceeds 99 on Windows NT and OS/2, or 82 on UNIX, the Hyperion Essbase server crashes.

The following problems were fixed in Patch 11. Unless otherwise noted, these fixes are reflected in the patched server software and do not require a client upgrade; however, we recommend upgrading client and server software to the same patch level.

Certain Japanese characters cannot be found using the Calc Script Editor's or Outline Editor's Find dialog box (9201, P11)
This fix requires a client upgrade. Certain Japanese characters cannot be found using the Calc Script Editor's or Outline Editor's Find dialog box.

In HP-UX, Linked Reporting Objects Cause Excel and Application Manager to Stop Responding (12030, P11)
With a HP-UX server, attachment of a cell note in the Spreadsheet Add-in causes Excel and Application Manager to stop responding when database operations are attempted.

Longer $ARBORPATH after Changed Installation Results in LRO Problems (12524, P11)
This fix requires a client upgrade. Changing the location of the network installation causes Application Manager to crash during LRO previewing, if the changed location results in a lengthened $ARBORPATH.

@PRIOR in a Dense Dynamic Calc Member Formula Returns the Wrong Result When Time is Sparse (12722, P11)
The @PRIOR function used in a dense Dynamic Calc member formula returns the wrong result when the Time dimension is sparse.

Solaris Patch 9 Installations Generate "bad tag" Error Messages (12759, P11)
On Solaris, installation of the Patch 9 Server, API, or SQL Interface generates a series of "bad tag" messages.

Long PATH Variables are Truncated During Server Installations on Windows NT and Windows 95/98 (13005, P11)
Long PATH variables (>255 characters) are truncated when you install the Hyperion Essbase server on NT or Win9x. With this fix, the environment is updated only when necessary. If the updated value would be too long, no update occurs, and there is an informational message.

Integration Server Drill-Through Data is Truncated and Scrambled (13324, P11)
This fix requires a client upgrade. In Lotus and Excel Spreadsheet Add-ins, Integration Server Drill-Through data is displayed as truncated column headers going down one column.

On AIX SQL Interface, a Case-Sensitivity Setting Used for Non-Intersolv Driver Configuration is Ignored (13372, P11)
On AIX, with the DB2 ODBC driver, the 'UpperCaseConnection' parameter of the ESSSQL.cfg file has no effect on how the password is presented to the DB2 ODBC driver.

Operations on Invalid Spreadsheets Cause Application to Shut Down (13485, 13969, 13526 P11)
Particular operations on invalid spreadsheet views (ambiguous members in inner rows) cause abnormal shutdowns of the application. With this patch, the crashes are prevented and an error message is displayed.

The Lock Parameter of the EssBeginReport() API Function Fails to Lock All Blocks Indicated in the Report Specification (13657, P11)
A report update for a particular database fails because the lock flag of EssBeginReport() locks only one block, where it should be locking two.

Data Load Proceeds Without Detecting an Error in Rules File Header Definition (13787, P11)
Errors are not generated, and data records may be loaded into the wrong dimension, when member names in the data source are from the same dimension as members defined in the Header Name field of the rules file (from Data Prep Editor: Options > Data Load Settings > Header Definition tab). This fix ensures that the data load stops and reports an error if the data file contains a member that is from the same dimension as members specified in the Header Name field.

Application Not Successfully Deleted from DB2 OLAP Server Looks as if were Deleted in Application Manager (14275, P11)
Hyperion Essbase removes the App folder and the security file entry for an application after a DB2 function, EssSmAppDelete(), fails to delete the application.

Application Shuts Down During Re-creation of LRO Following a Dense Restructure (14321, P11)
A Linked Reporting Object disappears after a dense restructure and calculation, and the application abnormally terminates when you try to create a new LRO.

ESSLANG Language-Environment Variable is Not Documented (14499, P11)
Information about the Hyperion Essbase ESSLANG environment variable is missing from Version 5.0.1 documentation. English versions of Hyperion Essbase are already set by default to use the correct code page. For non-English versions of the client and server, you need to set the ESSLANG variable (which defines the code page) to be the same on both the client and the server. The ESSLANG variable can be a user variable or a system variable. If $ARBORPATH is defined as a system variable, create ESSLANG as a system variable also. If $ARBORPATH is defined as a user variable, create ESSLANG as a user variable.

ESSLANG settings should follow this format: ESSLANG=<locale>
where <locale> is a supported Uniscape GlobalC locale of the format
<Language>_<Country>.<code page name>@<sort order>

Here is an example of a Japanese ESSLANG environment variable setting:
ESSLANG=Japanese_Japan.MS932@binary

Supported locales, and more information about code pages, are listed on the Uniscape page at: http://www.uniscape.com/technology/global_c_locales.htm

The following problems were fixed in Patch 10.

Incorrect Results Returned from Calc Scripts using Cross-Dimensional Operators that Compare #MISSING to Zero (9303, P10)
A calc scipt comparing a value (by means of cross dimensional operators) to zero returns incorrect results when the value being compared to zero is #MISSING.
For example, If (Actual->Sales->Feb < 0)
should evaluate False, not True, if the data for Actual->Sales->Feb is #MISSING.

Alias Name Not Added to Shared Member during Dimension Build (9417, P10)
When updating an outline using a rules file, an alias name fails to be added to a shared member in cases where the shared member's alias is the same as the regular member's alias.

On Solaris, in the Japanese version of Essbase, Unable to Create Database with Same Ending Characters as Another Database (11713, P10)
On Japanese version of Essbase running on Solaris, creation of a database named with the same ending characters as an existing database fails with a message that the database already exists.

Suppress Missing Spreadsheet option does not Suppress #No Access cells in versions 5.0 and later of the server (11849, P10)
In Versions 5.0 and later of the server, using Excel, the Suppress Missing spreadsheet option does not also suppress the display of cells for which a user has no access. Patch 10 includes a new Essbase.cfg setting as a workaround for this problem.

SupNA ON = Suppress Missing spreadsheet option suppresses the display of cells for which a user has no access.
SupNA OFF = Suppress Missing spreadsheet option does not suppress the display of cells for which a user has no access.
The default value is OFF. To work around the problem, you must include SupNA ON in your Essbase.cfg file.

@IRR Function Returns Incorrect Values for Some Members (12210, P10)
The Internal Rate of Return (@IRR) function returns incorrect values for some members, depending on the input values.

Deleting Linked Reporting Objects (LROs) fails in Excel 7 or 8 (12222, P10)
After deleting an LRO via the Linked Objects Browser in Excel, then closing and re-opening the browser, the object is still attached.

After Deleting Applications on AIX, Some Application Files Remain on Spanned Volumes (12760, 12653 P10)
On AIX, after deleting an application, the application's .PAG and .IND files remain on the spanned drives.

Default Calculation Returns Incorrect Data Values for Dynamic Calc Members (12769, P10)
@CURRMBRRANGE is not working correctly in calculations with sparse dynamic calc members.

Linked Reporting Objects added with the API to Implied Shared Members do not Appear in Excel (12825, P10)
LROs added with the API to implied shared members appear in Application Manager, but not in Excel.
Note: Shared members are "implied" in relationships where a parent has only one child that consolidates.

Need Process ID Numbers (PID) for Applications (12858, P10)
The NT Task Manager does not display PIDs for individual Essbase applications: all of the running Essbase applications appear as undifferentiated esssvr.exe processes. This prevents the ability to stop a single application, in the event that it hangs.
With this patch, the PID for individual applications can be found in the Essbase.log file in your ESSBASE directory. When the application starts, a line like the following appears in the log file:
Application Sample loaded - connection established.
That line will now include a process ID number, which you can use in conjunction with the kill operating-system utility provided with NT Resource Kit or other toolkits.

Calculation Using Time Balance Tags Ignores Values Following a Missing Block (12860, P10)
A calculation of a sparse, Dynamic Calc, Accounts member with a Time Balance tag attached ignores non #MISSING blocks that succeed #MISSING blocks. For example, a non #MISSING value following a series of #MISSING values is not included in the parent-member average.

An EssSetDatabasestate API Request Coming From an Earlier Client Version Resets the Retrieval Buffer Settings to Zero (13109, P10)
When an EssSetDatabasestate API call to a Version 5.0.1 server is made from a pre-Version 5 client, the Retrieval Buffer Size and Retrieval Sort Buffer Size settings are reset to zero.

The following problems were fixed in Patch 9.

Essnet.dll Missing from Lotus 1-2-3 Spreadsheet Add-in Installation
An updated Essnet.dll file is not installed with the Lotus 1-2-3 Spreadsheet Add-in files for Patches 6, 7, and 8. The message Error loading USE or USELSX module: lsx123.DLL appears after an attempt to load the add-in.

Essbase Cannot Create a Database Using Certain Japanese Characters (8989, P9)
Error messages occur when you use the CREATEDB command in an ESSCMD script to create a database named with certain Japanese characters.

#MISSING Values Don't Aggregate Properly after Moving Child Members in an Outline (9338, P9)
In certain outlines, when SET AGGMISSG is ON, after moving all children of one parent to another parent in the same dimension, and then calcuating the database with SET UPDATECALC and CALC ALL, the spreadsheet shows that the parent with the removed children retains the original value (instead of having an updated value of #MISSING).

Integration Server Drill-Through Report Execution Returns Error Message (11648, P9)
On UNIX operating systems, when you attempt to execute an Integration Server Drill-Through report from the Spreadsheet Add-in, the report fails and Essbase returns an Invalid Login String message.

Retrieval on Dynamic Calc Members with Formulas Causes Infinite Loop of Messages on Server Window (11791, P9)
In the spreadsheet, if you manually enter names of Dynamic Calc members that have member formulas, and then do a Retrieve, an infinite loop of messages (tried to read below bottom of stack in cpop(stk)) appears in the server window.

A #MISSING Value for a Child Member Does Not Consolidate after Lock and Send (11929, P9)
A #MISSING value for a child member in a particular outline fails to consolidate following a spreadsheet lock and send. A retrieval should show the new parent value as #MISSING.

Essbase Cannot Create a Database with '&' as Part of the Database Name (11977, P9)
In ESSCMD or Application Manager, when you try to create a database that has an '&' symbol as part of the database name, Essbase generates an error 1019002 - unable to create database.

Particular Calculation Scenario Crashes the Server (12018, P9)
When a member formula contains the @PRIOR function, and the member which uses the formula is calculated twice in a calc script, the application server crashes.

Zoom In with Repeat Member Labels Distorts Spreadsheet View (12347, 12348, P9)
When the "Repeat Member Labels" option is enabled in the Spreadsheet Add-in, zooming in on certain members distorts the spreadsheet view, and error messages are displayed.

Pivoting Columns with Repeat Member Labels Distorts Spreadsheet View (12385, P9)
When the "Repeat Member Labels" option is enabled in the Spreadsheet Add-in, pivoting column headings distorts the spreadsheet view.

The following problems were fixed in Patch 8.

In the Japanese Version of Essbase, Formulas on Japanese Outline Members Are Deleted After Outline Updating (8685, P8) In the Japanese version of Essbase, when a formula is attached to a Japanese member of the outline, the formula is deleted after the outline is updated with the "Update Outline" in the Outline Editor.

Certain Queries Fail in Spreadsheet Add-in When "Repeat Member Labels" Option Is Enabled (8968, 8984, 9087, 9291, 11672, P8)
When the "Repeat Member Labels" option is enabled in the Spreadsheet Add-in, certain types of queries (retrievals, pivots, and zooms) fail and return error messages.

EssGUpdateLRO Returns Error for Linked URLs (11491, P8)
The EssGUpdateLRO GRID API function works properly for files and cell notes, but returns the following error for linked URLs:

[Invalid object option for URL link entered -  3 ]

Essbase Fails to Start on NT when the Regional Setting is "Polish" or "English (New Zealand)" (11507, 11945 P8)
The Essbase Agent fails to start on Windows NT when the Regional Setting is set to "Polish" or "English (New Zealand)." Instead, the following error message occurs:
Failed on GcSetLocale ()

Database Queries Following Certain Calculations Crash the Server (11518, P8)
Following certain calculations using the "Aggregate Missing Values" and "Create Blocks on Equations" options (boxes checked in Database|Settings), database queries crash the Essbase server.

Patch 8 fixes the problem and provides an enhanced crash recovery for databases affected by this bug only. To avoid starting over with an empty or backup database, install Patch 8, leaving the crashed, pre-Patch 8 database in place. Then re-select the database.
Note: If you do not install Patch 8 before reselecting the database, then crash recovery will run into the same problem.

Free Form Retrieval in Excel Incorrectly Interprets Very Large or Small Values (11528, P8)
When Free Form mode is enabled in the Spreadsheet Add-in for Excel, a retrieval on a very large or very small number incorrectly returns numeric values as text strings. For example, a retrieval on 0.000005 incorrectly returns 5e-006 as a left-justified text value.

Time Balance "Last" Tag Returns Incorrect Values for Upper-Level Time Dimension Members (11570, P8)
The Time Balance "Last" tag returns incorrect values for upper-level Time dimension members if the last child member has a (~) (non-rollup) sign attached to it.

CCONV Calc Command Incorrectly Sets Data to #MISSING (11779, P8)
In certain calc scripts, the CCONV calculation command sets data to #MISSING if the associated currency database outline contains Dynamic Calc members.

Validate in ESSCMD Produces an "LRO free catalog page" Error Following Sparse Restructuring of a Database with LROs (11859, P8)
Validate in ESSCMD produces an "LRO free catalog page" error following sparse restructuring of a database with LROs.

The following problems were fixed in Patch 7.

Certain Japanese Members in a Dimension Cause Data Loads to Fail (10639, P7)
A data load fails after encountering certain Japanese members in a dimension.

Incomplete Error Message Displayed After Failed Login to Hyperion Integration Server Drill-Through (10845, P7)
When an attempt to log in to Hyperion Integration Server Drill-Through from the Spreadsheet Add-in fails, the error message that is displayed does not provide the Integration Server name. This error message has been changed so that the name of the Integration Server that the user is trying to connect to is displayed.

Windows 95 Clients Hang After Executing Customized Hyperion Integration Server Drill-Through Report (10861, P7)
On Windows 95, Excel and Lotus 1-2-3 hang after a customized Hyperion Integration Server Drill-Through report is executed.

On a Macintosh 4.1.2 Excel Client, Essbase Returns an Error When Attempting Data Retrieval (10946, P7)
On a Macintosh 4.1.2 Excel client (running against an Essbase Version 5 Windows NT server), data retrievals fail with the following error message:

Binary Spreadsheet Table Token Error

Retrieval on a Dynamic Calc Member using @MDPARENTVAL in the Member Formula Crashes Server (11169, P7)
Retrieving from the spreadsheet on a Dynamic Calc member using @MDPARENTVAL in the member formula crashes the Essbase server.

Essbase Server Crashes After Executing Hyperion Integration Server Drill-Through Report and Shutting Down Agent (11251, 11428, P7)
After executing an HIS Drill-Through from the Spreadsheet Add-in and attempting to shut down the Agent, the Essbase server crashes and the shutdown for the Agent is aborted.

Retrieval with Duplicate Members in Title Row Crashes Server (11350, P7)
A spreadsheet retrieval crashes the server when the title row of the sheet contains duplicate members, and when the duplicate member is the last member in the row. In the example below, East is a duplicate member from the Market dimension, which already appears in the title row:

Market Measures Product Scenario East

Year

Canceling Message After Saving Partition Closes Partition Wizard (11402, P7)
After saving a modified partition to the server and canceling the message dialog that appears, Essbase incorrectly closes the Partition Wizard and returns to Partition Manager. This problem has been fixed, and the message dialog has been changed. It now reads as follows:

The source, target, or type information has changed in this session.

Yes: Create a new partition.
No:  Overwrite the existing partition.

             Yes       No       Cancel

Dynamic Time Series Member That Contains Parentheses Returns Error in Spreadsheet Add-in (11434, P7)
When retrieving on a Dynamic Time Series member (from the Time dimension) that contains parentheses within the member name, the Spreadsheet Add-in returns an error message stating that the sheet contains an unknown member. Examples of types of member names that would encounter this problem are "Mar(March)" or "04(YTD)".

@PARENTVAL Function Not Working Correctly with Dynamic Calc (11450, P7)
If you use @PARENTVAL on a member whose parent is tagged as Dynamic Calc, the retrieval results are incorrect (i.e., the updated database value for the parent member is not shown).

Data Still Returned After Member is set to #MISSING in a Calc Script (11459, P7)
Data is still shown for a member after locking and sending data, then setting the member to #MISSING by running a calc script like the following:
Set UPDATECALC OFF; FIX (Sales, Budget, Jan) Cola = #MISSING; ENDFIX;

Record Containing Duplicate Members Is Incorrectly Loading Data Instead of Being Rejected (11464, P7)
When loading a record that contains duplicate members in the same row, the record incorrectly loads to the wrong area of the database instead of being rejected.

In Certain Scenarios, After Updating an Outline, Restructuring with All Data Fails (11483, 11486, 11006 P7)
In certain scenarios, after updating an outline containing data, restructuring with all data fails with Internal Logic Error 7118.

Version 5.0.1 Patch 4 SQL Interface Installation Program for AIX Incorrectly Defaults to Intersolv Drivers (11501, P7)

On AIX, the Version 5.0.1 Patch 4 SQL Interface installation program (sql-inst.sh) no longer prompts you to choose between the Intersolv or DB2 ODBC drivers, and incorrectly defaults to Intersolv. This problem has been fixed so that install program works as it did in the general release of Version 5.0.1.

Calculated Results Inconsistent between Version 4.1.2 and 5.0.1 (11569, P7)
In a calc script, a cross-dimensional assignment within an IF statement causes the block not to be marked as dirty in Version 5.0.1, returning incorrect results.

Report Writer Script Containing the LINK Command Crashes the Server (11585, P7)
In Report Writer, when a report script contains a LINK command, the Essbase server crashes without generating an exception log.

Application Manager Incorrectly Allows Two Members with Same Alias (11613, P7)
Application Manager incorrectly allows you to create two different members with the same alias name and does not display an error message. The appropriate error message is displayed only when the alias name is set through the Attributes field.

Incorrect Dynamic Time Series Results with Certain Report Writer Scripts (11616, P7)
After running a certain Report Writer scripts, Dynamic Time Series members return incorrect results.

@PRIOR Function not Working Correctly without Assignment Operator (11638, 11465, 10325 P7)
Using an @PRIOR statement without an assignment operator (=) returns inconsistent calc and report script results. @PRIOR, @NEXT and @SHIFT (and variants) should work regardless of assignment.

AIX SQL Interface Installation Program Does not Create the ivoracle7.so File (11656, P7)
On AIX, the ivoracle7.so file is not created when the the SQL Interface installation program (sql-inst.sh) is run.

The following problems were fixed in Patch 6.

Certain Formulas Cause Data Loads From Excel 97 Data Files to Abort (10864, P6)
In Excel 97, formulas that return string results will cause a data load to abort. This effect also occurs when opening the same data file in the Data Prep Editor.

When Sparse Restructuring Results in an Empty Database, the Server Crashes During Dimension Build (11084, 11103 P6)
After performing a sparse restructuring that results in an empty database, the Essbase server crashes during a subsequent dimension build with the following error message: Assertion 8400.

Report Writer Returns 0's in Asymmetric Reports With Multiple Dynamic Time Series Members (11220, P6)
Report Writer returns 0's in asymmetric reports containing multiple DTS members.

Zooming Out on a Member Causes Application to Crash in a Rare Scenario (11264, P6)
In a rare spreadsheet scenario with the "Repeat Member Labels" option enabled, performing operations on a particular member crashes the application.

In Patch 4, the EssOtlQueryMembersByName API Call is Missing from the essotln.lib File (11331, P6)
The EssOtlQueryMembersByName API call is missing from the essotln.lib file. The wrong library files were copied for the Patch 4 installation.

@IRR Function Returns Incorrect Values for Some Members (11347, P6)
The @IRR function returns incorrect values for some members.

When Copying Applications and Databases in ESSCMD, Entering an Invalid Name as the Destination Can Cause Data Loss (11354, P6)
When copying applications or databases using ESSCMD, entering an invalid name as the copy destination can cause data loss.

Zooming in on a Member with a Specific Spreadsheet Layout Crashes Application With Assertion Failure 6178 (11403, P6)
In a rare scenario, the application crashes when you zoom in or perform other actions on a member in a spreadsheet layout where the innermost column member has more members than the others. The problem occurs because asymmetric grids are mistakenly detected as symmetric grids.

Certain Calculations Running Against Large Outlines Cause the Server to Crash (11424, P6)
Certain calculations running against large outlines cause the server to crash.

Report Writer Returns Extra Data When a Single Report Script Contains Multiple Reports (11472, P6)
Report Writer returns extra data when there are multiple reports (multiple !'s) in a report script. One symptom of this problem is the occurrence of an error message while attempting to post journals in EAM (Essbase Adjustment Module).

The following problems were fixed in Patch 5.

Windows NT Event Viewer Reports Errors When Starting Essbase Agent as a Service (9765, P5)
When starting the Essbase Version 5.x Agent as a service, the Windows NT Event Viewer lists Error type events. These should be listed as informational messages only.

Security File Corruption Occurs When Deleting Databases With Substitution Variables Identical to Those Defined for an Application (10343, 10426, 10809 P5)
In certain scenarios, security file corruption occurs when deleting applications/databases that contain substitution variables. If substitution variables with identical names are defined at both the database and application levels, deleting the application or the database may result in duplicate substitution variables, which in turn may lead to corruption of the security file.
The fix in Patch 4 ensured that deleting applications with identical substitution variables would not corrupt the security file. The Patch 5 fix additionally ensures that deleting databases with identical substitution variables does not corrupt the security file.

Certain Spreadsheets in Excel 97 Cause Formula Preservation to Fail with Range Functions (10593, P5)
With certain spreadsheets in Excel 97, the Formula Preservation option fails with range functions.

"Essbase Help" is Missing From the Excel Help Menu in Japanese Spreadsheet Add-in (10656, P5)
The "Essbase Help" selection is missing from the Excel Help menu in the Japanese Spreadsheet Add-in.

In Application Manager, Calc Scripts Assigned to a User Are Not Reflected in the Supervisor's View (10716, 10963 P5)
In Application Manager, calc scripts assigned to a user are not reflected in the Supervisor's view. Although the user's calculation access is correctly affected by the assignment of the calc script, the Supervisor, after assigning it, sees that the Allow All Calcs box is still checked for that user in the Execute Calc Scripts dialog box.

Selecting the Style for Hyperion Integration Server Drill-Through Data Cells Crashes the Server (10736, P5)
In Patch 3, 32-bit Spreadsheet Add-ins included a new Style in the Essbase | Options dialog box (Style page) for Hyperion Integration Server Drill-Through data cells. In that patch, clicking this checkbox resulted in a server crash. This problem has been fixed so that the "Integration Server Drill-Through" checkbox can be selected and a style defined for Drill-Through cells.

Error Message Returned During Member Select with "Use Aliases" Enabled in Essbase | Options Dialog Box (Windows 95 Only) (10880, P5)
With particular outlines, an error message is returned during a Member Select operation when the "Use Aliases" option is enabled in the Essbase | Options dialog box (Windows 95 only).

Default Calculations on Dynamic Calc Tags Within Time or Measures Dimensions Crashes the Server (10977, P5)
Default calculations (Calc All) performed on members tagged as Dynamic Calc in the Time or Measures dimensions crashes the server.

@PRIOR and @NEXT Calculator Functions Return Incorrect Values in Version 5.0.1 Patches 2 and 3 (10990, P5)
The calculator functions @PRIOR and @NEXT return incorrect values in version 5.0.1, Patches 2 and 3.

In Spreadsheet Add-ins, the "View Method By Member Name" Option in the Member Selection Dialog Box is Not Selected by Default (11167, P5)
In all Spreadsheet Add-ins, the "View Method By Member Name" option in the Member Selection dialog box should be selected by default, but instead must be selected by the user. This problem is fixed for 32-bit add-ins, but still exists for 16-bit add-ins.

Report Writer May Generate #MISSING or Incorrect Values in Asymmetric Reports With Multiple Dynamic Time Series Members (11220, P5)
Report Writer may generate #MISSING or incorrect values in asymmetric reports with multiple DTS Members. This error may be visible in ESSCMD, Application Manager, or a spreadsheet.

The following problems were fixed in Patch 4.

Excel Crashes After Attempting Essbase SQL Drill-Through on Results from Previous Query (8142, P4)
If you attempt an SQL Drill-Through operation on a sheet that contains the results of a previous SQL Drill-Through query, Excel crashes.

EsbOtlDeleteMember API Call Incorrectly Deletes Shared Members from Outline (10372, P4)
When the EsbOtlDeleteMember structure is called, and a descendent of the member being deleted is shared, all other instances of the shared member are incorrectly deleted from the outline.

Index-Only Restructuring After Data Load Causes Memory Leak (10450, 10919 P4)
After a data load, performing an index-only restructuring of the database causes a memory leak.

In Lotus and Excel, Zooming Out on Top-Level (Dimension Members) Crashes the Essbase Server (10692, P4)
In all versions of Lotus and Excel, zooming out on top-level (dimension) members in the spreadsheet crashes the Essbase server.

Selecting the Style for Hyperion Integration Server Drill-Through Data Cells Crashes the Server (10736, P4)
In Patch 3, 32-bit Spreadsheet Add-ins included a new Style in the Essbase | Options dialog box (Style page) for Hyperion Integration Server Drill-Through data cells. In that patch, clicking this checkbox resulted in a server crash. This problem has been fixed so that the "Integration Server Drill-Through" checkbox can be selected and a style defined for Drill-Through cells.

Wrong Version Number Displayed When Installing 5.0.1 Patch 2 on HP-UX (10752, P4)
The wrong version number is displayed in the installation program screens of Essbase Version 5.0.1 Patch 2 SQL Interface on HP-UX.

Installation of "501P132.EXE" (Excel 32-bit client patch) as Shared Executable Fails (10781, P4)
When the "Copy disks as shared executables to network drive" is selected while installing the "501P132.EXE" patch file, the following message is incorrectly displayed, and the installation fails:

"Please insert disk 6 of Excel Spreadsheet Add-in for 32-bit Windows"

Security File Corruption Occurs When Deleting Applications/ Databases With Identical Substitution Variables (10809, 10343, 10426, P4)
In certain scenarios, security file corruption occurs when deleting applications/databases that contain substitution variables. If substitution variables with identical names are defined at both the database and application levels, deleting the database may result in duplicate substitution variables, which in turn may lead to corruption of the security file.
The fix in Patch 4 ensures that deleting applications with identical substitution variables does not corrupt the security file. This problem may still occur when deleting databases with identical substitution variables (to be fixed in Patch 5). Security file corruption can be avoided by deleting substitution variables from an application/database before deleting the application/database, which prevents references to the deleted application in the remaining substitution variables.

Retrieval on Dynamic Times Series Member Deletes Alias Name When "Use Aliases" Option Is Enabled (10817, P4)
A spreadsheet retrieval on a Dynamic Time Series member incorrectly deletes the alias name when the "Use Aliases" option is enabled.

Validating Replicated Partition Crashes Target Application Server (10821, P4)
When validating a replicated partition, the target application server crashes. This problem may also occur when checking the cell count between the source and target.

Lotus 1-2-3 May Hang During Member Select Operations (10850, P4)
Lotus 1-2-3 may hang during certain Essbase Member Select operations.

Retrieval on Particular Dynamic Calc Members in Essbase Version 5.0.1 (Patch 2) Produces Incorrect Results (10908, P4)
Results from retrieving particular Dynamic Calc members in Essbase Version 5.0.1 Patch 2 are different from those produced in Version 5.0 (Patches 1-4). This problem occurs when the Dynamic Calc member being retrieved has a cross-dimensional member reference.

Calc Scripts Return Inconsistent Results Between Essbase Version 4.1.2 (Patch 10) and 5.0.1 (Patch 2 or Patch 3) (10950, P4)
The same calc scripts return inconsistent results between Essbase Version 4.1.2 (Patch 10) and 5.0.1 (Patch 2 or Patch 3). In 5.0.1, this problem occurs with outlines that have particular forward calculation references. The calculator now behaves as it did in Version 4.1.2.

In the Japanese Version of Essbase, Double-Byte Characters in Member Names Cause Errors in Formulas (10956, 10921 P4)
In the Japanese version of Essbase, formulas disappear from the outline because the double-byte member names are not recognizable to the server during parsing.

ESSCMD Does Not Work in Windows 95 Following a Full Installation from the Essbase 5.0.1 Patch 2 or Patch 3 CD (10958, P4)
As of 5.0.1 Patch 2, keystrokes entered into ESSCMD on Windows 95 appear as "<<<<<" and do not work. This problem occurs because a Windows NT server version of ESSSD.DLL is used in place of the Windows 95 version. By default, the Essbase server is installed first, and the client is installed last. A work-around (independent of this patch) is to install the Windows 95 Essbase server after installing the client.

32-bit Excel Spreadsheet Add-ins Are Not Available on Windows 95 and Windows NT 3.51 After Installing Essbase 5.0.1 Patch 2 or Patch 3 (10959, 10972, 11257 P4)
After installing Essbase Version 5.0.1 Patch 2 or Patch 3, 32-bit Excel Spreadsheet Add-ins do not work on Windows 95 or Windows NT 3.51 because of a missing .DLL file. This file is now provided as part of installation.

Server Crashes When Attempting to Create a Database with Certain Japanese Characters (10986, P4)
When attempting to create a database using the common Japanese word for "budget", error messages are returned, and the Essbase server crashes.

When Retrieving Data Following a Calculation, the Essbase Version 5.0.1 Patch 3 Server Retrieves Incorrect and Fluctuating Dynamic Calc Values (11003, P4)
Following a calculation, if you retrieve a Dynamic Calc member that has a shared member as a child, and the real member associated with that shared member is also a Dynamic Calc member, the 5.0.1 Patch 3 server returns incorrect and fluctuating values.

Copying Applications with Certain Japanese Application and Database Names Fails (11064, P4)
Copying applications that have certain Japanese application and database names fails. This problem occurs if the name of the copied application or its databases includes certain double-byte characters, and the ESSLANG environment variable is not set.

Certain Member Formula Calculation Results are Inconsistent Between Essbase Version 5.0.1 Patch 2 and 5.0.1 Patch 3 (11085, P4)
Calculation results are inconsistent between Essbase Versions 5.0.1 Patch 2 and 5.0.1 Patch 3 when the following formula is used:

IF (Member == #Missing)

The following problems were fixed in Patch 3.

Long Formulas Are Deleted After Retrieval in Excel (9920, P3)
In Excel, formulas with strings that are more than 255 characters in length are deleted after data retrieval. This problem has been fixed for Excel 97. For Excel 5.0 and Excel 95, this problem occurs because of an Excel system limitation.

EsbSetDatabaseState API Call Resets Particular Database Settings (9947, P3)
On Windows NT (x86 machine), the EsbSetDatabaseState API call resets particular database settings (e.g., "Create Blocks on Equations," "Allow Database to Start," "Start when Database Starts," "Aggregate Missing Values"). To fix this problem, the following fields have been added to the ESB_DBSTATE_T structure:

ESB_ULONG_T RetrievalBuffer;
ESB_ULONG_T RetrievalSortBuffer;
ESB_USHORT_T IsolationLevel;
ESB_BOOL_T PreImage;
ESB_LONG_T TimeOut;
ESB_ULONG_T CommitBlocks;
ESB_ULONG_T CommitRows;
ESB_ULONG_T nVolumes;

16-bit Spreadsheet Add-ins Crash if Locale Information Is Missing (10181, P3)
16-bit Spreadsheet Add-ins (e.g., Excel 5.0, 1-2-3 Release 5) crash if Locale information cannot be found. For example, if the \Locale16 directory is deleted from the \Essbase directory, the 16-bit Spreadsheet Add-in does not load and the application crashes.

32-bit Excel Crashes if Users Are Disconnected from Essbase While Using Retrieval Wizard (10249, P3)
In 32-bit versions of Excel, Excel crashes if a user is disconnected from Essbase while using the Retrieval Wizard.

EssGGetLRODesc() Grid API Function Fails to Return Filename in Description (10403, P3)
On Solaris, the EssGGetLRODesc() Grid API function does not return the filename when connecting to a Windows NT server.

Spreadsheet Cell-Reference Formulas Do Not Retrieve Data Correctly (10432, 10467, 10550, 10606, P3)
In all versions of Excel and in Lotus 16 spreadsheets (with 5.0.1 client and server), using Visual Basic commands or cell-reference formulas to retrieve data does not retrieve data correctly. No data value is retrieved for the referenced member. This problem occurs when Formula Preservation is enabled.

Application Manager with Limited SKU License Incorrectly Enables Certain Commands (10457, P3)
When using Application Manager with a Limited SKU license, the following commands are incorrectly enabled:

File | New command: This menu item should be grayed out.
Save and Save As commands: These menu items are grayed out, but it is possible to save via a Confirmation dialog box that appears upon closing each Application Manager editor.

On HP-UX, Some #MISSING Values are Replaced by Zeros or Other Characters During Data Load (10498, P3)
On HP-UX, some #MISSING values are arbitrarily replaced by zeroes or other strange floating point numbers during data loading from Windows NT to HP-UX. To correct this problem, go to the HP website at http://us-support.external.hp.com/ and install the following HP-UX patches:

PHSS_12694 UCOMP/LIBMP
PHSS_14920 HP DCE/9000 1.5 cumulative patch
PHSS_15043 10.x HP aC++ runtime library components
PHSS_15549 LIBCL
PHSS_14371 HP C++ (A.10.36) core library components

Application Manager Allows Creation of Files Using Windows NT Reserved System Names (10521, P3)
Application Manages incorrectly allows the creation of (and writes to the security file) files using Windows NT reserved system names.

Certain Calc Scripts Return Different Results From Previous Versions of Essbase (10528, P3)
On Windows NT (x86 machine), calc scripts that produced correct results in Version 4.1.2 produce different results in Version 5.0.1. This problem may occur with calc script that include temporary variables in a sparse formula.

Performing Quick, Successive Pivots in Excel Crashes Client (10534, P3)
In Excel 5.0 and Excel 97, performing quick, succesive pivot operations in the spreadsheet crashes the client.

Reports Spanning Transparent Partitions Returns Missing or Incorrect Data (10540, 10674, P3)
Reports that span transparent partitions return missing or incorrect data.

On Solaris, Timing Error Causes Application Crash (10577, P3)
On Solaris, timing error causes application crash when getting database information or using GETDBSTATS.

Zooming In on Particular Member Crashes Server (10595, P3)
In the Spreadsheet Add-in, zooming in on a particular type of member crashes the Essbase server. This problem may occur when zooming in on a dense, dynamic calc member that has a formula containing a cross-dimensional operator.

Server Crashes After Successful Restructure When Using the IBM DB2 OLAP Server (10614, P3)
The Essbase server crashes after a successful database restructure. This problem occurs only when using the IBM DB2 OLAP Server's Relational Storage Interface.

Member Names with Non-Alphanumeric Characters (such as @ or !) May Cause Calculation Errors even when Enclosed in Double Quotes (10637, P3)
Member names containing non-alphanumeric characters are parsed incorrectly, resulting in calc script validation failure, even when the member names are enclosed in double quotation marks.

Application Manager Does Not Display All Entered Users (10638, P3)
After entering 400 or more users in Application Manager, all users entered do not appear in the users/group security window.

Zooming In on Members in Particular Asymmetric Reports Crashes Server (10657, P3)
In Excel 97, zooming in on members in particular asymmetric reports may crash the Essbase server.

Identical Operands Around Mathematical Operators Returns Incorrect Values (10662, P3)
In a member formula containing a mathematical operator (e.g., <=, >=), if the operands on either side of the operator are identical, incorrect values are returned. For example, the formula "12 >= 12" would return an incorrect value instead of the correct value (0).

Report Writer Performance Is Slower in Version 5.x than in Version 4.x (10670, P3)
On Solaris, generating reports via Report Writer takes longer in Version 5.x than in Version 4.x.

Retrieving Certain Dynamic Calc Members Crashes Server (10689, P3)
Retrieving a sparse, Dynamic Calc member that is used in an IF statement crashes the Essbase server.

Certain Linked Reporting Objects (LRO) Insertions Crash Server (10713, P3)
Certain LRO insertions crash the Essbase server.

Retrieval on Dynamic Time Series Member in Certain Spreadsheets Crashes Client (10717, P3)
In 32-bit Excel, a retrieval on a dynamic time series member in certain sheets crashes the client. This problem occurs because of incorrect usage of dynamic time series (i.e., the generation of the latest time period is lower than the dynamic time series member in the database outline). An error message is now issued when this operation is attempted.

Failure of Assertion 7027 Crashes the Server (10721, P3)
The server crashes during the commit or abort of a transaction due to failure of assertion 7027. this problem occurred only in Version 5.0 and Patch releases of Version 5.0. The problem was fixed in the base release of Version 5.0.1, but the fix was confirmed only in this Patch 3 release of Version 5.0.1.

SQL Server Does Not Accept SUM Functions in SELECT Statements (10726, P3)
SQL Server does not accept SUM functions within SELECT statements with the drivers supplies with Essbase Version 5.x. SUM functions worked properly with Essbase Version 4.1.2.

Integration Server Option Added to Spreadsheet Add-in (Options|Styles) Does Not Work (10736, P3)
As of Patch 3, 32-bit Spreadsheet Add-ins provide a new style in the Essbase Options dialog box (Style page). The new option, "Integration Server Drill-Through," will allow spreadsheet users to define a style for data cells that have Integration Server Drill-Through reports attached to them. Caution: This style option is not yet functional. Checking this option will result in a server crash. This will be corrected and functional in Patch 4.

Running the Same Report Scripts Consecutively Returns Different Values for Same Data Cell (10777, P3)
If two report identical scripts are run consecutively, the second report returns a different value for the same data cell. If the Essbase server is shut down between the two report scripts, the same (correct) results are returned.

Checkmark Missing from "Navigate Without Data" Spreadsheet Add-in Essbase Menu, Non-English Versions Only (10779, P3)
In non-English versions of the Spreadsheet Add-in, the check mark next to the "Navigate Without Data" menu command does not appear after selecting the menu item.

Certain Spreadsheet Retrievals with @MDSHIFT Function Crashes the Server (10796, P3)
In certain spreadsheets, a retrieval on a member that has the @MDSHIFT function associated with it crashes the Essbase server and generates an exception log.

Integration Server Drill-Though in Excel Fails with "Unable to Allocate Memory" Message (10811, P3)
When you are connected to the Integration Server, double-clicking a data cell in Excel returns the following error message instead of the Linked Objects Browser:

"Unable to allocate memory"

Locking and Sending a Spreadsheet That Contains Data for Both Regular and Shared Member Does Not Work Properly (10812, P3)
Locking and sending a spreadsheet that contains data for both regular and shared members does not work properly. This problem has been fixed so that the second data value correctly overwrites the first value.

Retrieving Dynamic Time Series Members Incorrectly Returns Zero Values (10813, P3)
Retrievals on dynamic time series members against an empty database return zero (0) values instead of "#Missing." This problem occurs when a sheet contains multiple dynamic time series members with different latest time period settings.

Incorrect Results Returned from Formula Containing @ANCESTVAL (10845, P3)
When the @ANCESTVAL function is used in a member formula, incorrect results are returned.

The following problems were fixed in Patch 2.

Server Crashes Upon Attempting to Generate Certain Transaction Management Messages (5547, P2)
On all server operating systems, the Essbase server may crash when attempting to generate certain Transaction Management messages.

Essbase Agent NT Service Does Not Work Properly If You Log Off After Loading the Application and Database (9248, P2)
If you start the Essbase Agent as an NT service, load an application and database from ESSCMD, and log off from Windows NT, the following problems occur:

ESSCMD is unable to connect to the application and database.
Windows NT runs slowly.

Users with Write Privileges Are Unable to Lock and Send Data from Particular Sheets (10128, 10572, P2)
When a spreadsheet user does not have Write privileges for the first data cell in a sheet and attempts to Lock data values on the sheet, the Lock operation fails with an error message. This problem has been fixed so that (1) no error message appears and (2) the Lock and Send operation succeeds for the appropriate cells.

Using ESSCMD to Run a Report with a Substitution Variable Crashes the Server (10140, P2)
Using ESSCMD to run a report with a substitution variable crashes the server and creates an exception log. The report can be run from Application Manager without problems, but if you use ESSCMD RunRept (interactive or batch mode), Essbase returns the following error:

"Unknown command [] in Report"

The brackets contain meaningless characters.

Report Generation Slower in Version 5.x than in Version 4.x (10339, P2)
Generating reports in Version 5.x takes longer than in Version 4.x. Performance improvements have been made for report generations with large numbers of members in dense dimensions.

Lock and Send Retrievals Slower in Version 5.x than in Version 4.x (10384, P2)
On AIX, Lock and Send retrievals in Version 5.x take longer than in Version 4.x.

On UNIX, Lock Contention Produces Excessive Messages in the Log File (10385, P2)
In UNIX, lock contention causes excessive messages to appear in the log file.

"Unable to Write Information to File [.TCT]" Error After Index-Only Restructuring (10394, P2)
The following error message appears when the Transaction Manager attempts to extend the .TCT file following index-only restructuring:

"Unable to write information to file [.tct]."

Retrievals in Excel 97 on Particular Sheets Crashes the Server (10478, P2)
In Excel 97, the Essbase server crashes on a spreadsheet retrieval when the first column member in the sheet is an unknown member. When this problem occurs, the following error message is returned:

"Cannot receive data"

On UNIX, Agent Returns Incorrect Swap Information if the Swap Size is Greater than 2 GB (10493, P2)
On UNIX operating systems, the Agent returns incorrect swap information if the swap size is greater than 2 GB.

Using RLE Data Compression May Result in Incorrect Values With Particular Databases (10494, P2)
Using the Run-Length Endoding (RLE) data compression type may result in incorrect values when a database has blocks that contain no cases of 4 or more repeated values.

On HP-UX, Some #MISSING Values are Replaced by Zeros or Other Characters During Data Load (10498, P2)
On HP-UX, some #MISSING values are arbitrarily replaced by zeroes or other strange floating point numbers during data loading from Windows NT to HP-UX. To correct this problem, go to the HP website at http://us-support.external.hp.com/ and install the following HP-UX patches:

PHSS_12694 UCOMP/LIBMP
PHSS_14920 HP DCE/9000 1.5 cumulative patch
PHSS_15043 10.x HP aC++ runtime library components
PHSS_15549 LIBCL
PHSS_14371 HP C++ (A.10.36) core library components

Various Dynamic Restructuring Scenarios Cause Server to Crash (10499, P2)
With particular dense/sparse configurations, a server crash occurs if you perform a varying series of actions, one of which includes changing members from shared to stored, renaming members, and adding a formula.

Server Crashes When Running a Calc Script Containing a Large Cross-Dimensional Operator Calculation (10506, P2)
When you run a large calc script in Application Manager that contains a long section using cross-dimensional operators (->), the Essbase server crashes and generates an exception log.

Server Crashes When Running a Calc Script Containing a Large Member Formula (10507, P2)
When you run a calc script in Application Manager that contains a large member formula, the Essbase server crashes and generates an exception log.

Renaming, Copying, or Deleting Applications Does Not Work Properly with Backslash as Last Character (Japanese Version) (10517, P2)
In the Japanese version of Application Manager, you cannot rename, copy, or delete an application if the last byte of the original application name is equivalent to a single-byte backslash character ( \ ).

ESSCMD Does Not Work With Japanese Characters (10513, P2)
ESSCMD does not work with multi-byte or single-byte Japanese characters.

Creating a Database with Certain Japanese Characters May Crash Server (10515, P2)
The Essbase server may crash when you create a database if the database name contains certain Japanese multi-byte characters belonging to the KATAKANA character set.

In the Japanese Version of Application Manager, Case-Sensitivity Is Not Fully Recognized (10520, P2)
In the Japanese version of Application Manager, Essbase is not properly stopping the creation of two applications with the same name (one lowercase, one uppercase).

Member Select Does Not Recognize Member Names with Certain Japanese Characters (10522, P2)
In the Spreadsheet Add-in or the Partition Wizard (Application Manager), the member selection tool does not recognize members with certain Japanese characters.

Retrieving Dynamic Time Series Members Across Transparent Partition Returns Incorrect Data (10536, P2)
Retrieving a Dynamic Time Series member across a transparent partition returns incorrect or fluctuating values for that member. This problem has been fixed in Patch 2, so you must install Patch 2 on all servers containing databases that participate in distributed partitions.

In Non-English Versions of Application Manager, Partition Wizard Page Labels Appear in English (10537, P2)
In certain non-English versions of Application Manager, the Partition Wizard page navigation labels appear in English rather than in the correct language.

Server Crashes When Processing Transparent Partition Request with Incorrectly Mapped Dimensionality (10551, P2)
A transparent partition validate operation crashes the Essbase server (1) both the target and source databases belong to one application and (2) the validate operation finds incorrectly defined area mappings. The crash occurs after retrieving in the spreadsheet. No crash occurs if the source and target databases belong to two separate applications. The following error appears in the application server log:

"Incorrect number of dimensions in request from remote site;
[4] sent [5] requested; check member mapping between regions;"

Running a Calc Script after Locking and Sending Data from Spreadsheet Returns Error Message (10558, P2)
Running a calc script after locking and sending data from the spreadsheet returns the following error message:

Need to copy to esm block during dynamic calculation. esm block not found. Internal logic error

This problem may occur when a regular outline member depends on a cross-dimensional, dynamic calc member.

Spreadsheet Retrieval Returns Column Headers Instead of Correct Error Message (10573, P2)
With an Essbase Version 4.1.2 client (in Excel 97) and a Version 5.0.1 server, a retrieval on an empty spreadsheet with "Suppress #Missing" or "Suppress Zeroes" enabled returns column headers when only an error message should be returned.

Deleting User-Defined Attributes in Outline Editor Produces Incorrect Results (10589, P2)
If you delete a User-Defined Attribute (UDA) in the Application Manager's Outline Editor, Essbase may delete the wrong UDA.

Dynamic Calc Failure: Running a Two Pass Calculation on a Sparse Accounts Dimension Returns Incorrect Results When Used with @ANCESTVAL or @PRIOR Functions (10615, 10616 P2)
If you run a Two Pass Calc using @ANCESTVAL or @PRIOR on a dimension configured as Sparse and tagged as Accounts, incorrect results are returned.

Spreadsheet Retrieval Against Particular Outline May Crash Server (10617, P2)
A spreadsheet retrieval may crash the Essbase server when the Accounts dimension is configured as Sparse and has Dynamic Calc, Two Pass members.

Shutting Down an Application or Database Crashes Essbase Server During Extremely Rare Timing Scenarios (10636, P2)
Shutting down an application or database causes the Essbase server to crash during extremely rare timing scenarios.

Certain Japanese Members in a Dimension Cause Data Loads to Fail (10639, P2)
A data load fails after encountering certain Japanese members in a dimension.

The following problems were fixed in Patch 1.

SQL Query Fails if the Select Statement Contains a Text String, Number, Date Value, or Expression (4959, P1)
An SQL query fails if the select statement contains a text string, number, date value, or expression. For example, the error message
"There is no data records for the selected SQL Data Source"
occurs if you issue the query statements:
SELECT 'A TEXT STRING' FROM TABLENAME. SELECT A + B FROM TABLENAME SELECT MAX (COLUMNAME) SELECT COUNT (*) FROM TABLENAME

Adding a User to a Group Through ESSCMD "Adduser" Fails (9725, P1)
After running an ESSCMD script to add a user to a group, the list of groups associated with that user in Application Manager does not reflect the change.

Logins Are Incorrectly Enabled When DISABLELOGIN Command Is Active (9578, 10106, 10151, P1)
Under the following conditions, logins are incorrectly enabled even when the DISABLELOGIN command (ESSCMD) is active or the "Allow Connects" option is disabled in Application Manager:

When the same user who issued the DISABLELOGIN command logs in via a different avenue (Excel, Lotus, and so forth)
When another Supervisor or Application Designer (with privileges to the application in question) logs in or out
When a user who was already connected (before the DISABLELOGIN was issued) disconnects

This problem has been resolved. In addition, Supervisors and Application Designers will be able to log in and out even when logins are disabled without affecting the DISABLELOGIN setting. Supervisors or Application Designers can enable or disable this setting, assuming they have proper access privileges.

Excel Client Cannot Connect to Named Pipes Server in Windows 95 (9651, P1)
In Windows 95, the 32-bit Spreadsheet Add-in for Excel cannot connect to the Essbase server over Named Pipes.

Database Designer Privilege Assigned at Group Level Doesn't Give User Sufficient Privileges (9733, 10402 P1)
On Windows NT (x86 machine), users with no application access who are also part of a group with Database Designer access cannot run calc scripts.

Blocks Incorrectly Created from Locking and Sending #MISSING Values in an Excel Spreadsheet (9885, 10451 P1)
In Excel, locking and sending a database with cleared data (#MISSING values) causes Essbase to report in database statistics that blocks exist, along with a page and index file. These should not exist for an empty database.

SQL Drill-Through Client Connection Fails Every Other Attempt Using Microsoft ODBC Driver for SQL Server 6.5 (9908, P1)
SQL Drill-Through client connection fails alternately using Microsoft ODBC Driver for SQL Server 6.5. The prior client/server connection is not properly cleared, and interferes with the subsequent attempt.

Clicking Style Tab in Essbase Options Dialog Box Crashes Client, Windows 3.11 (9993, P1)
On Windows 3.11 (Excel and Lotus), clicking the Style tab in the Essbase Options dialog box crashes the Spreadsheet Add-in.

ADDUSER Command (ESSCMD) Gives Incorrect User Access (10018, P1)
If you add a user to an existing group using the ADDUSER command (ESSCMD), the user does not have the same level of access as users added through Application Manager.

When a User Adds Another User to a Group with Higher Privileges, Other Members of the Group are Removed (10026, P1)
When user A adds user B to a group with higher privileges than user A has, the pre-existing members of the group who also have higher privileges than user A are removed from the group.

Users Cannot Connect to Essbase Server Over Named Pipes on Windows NT (10078, P1)
With Named Pipes on Windows NT, users are unable to connect to the Essbase server from Application Manager unless their user privileges are set to Administrator. This problem has been fixed so that all NT users can connect to the server over Named Pipes.

EsbLROUpdateObject Not Updating Cell Notes (10109, P1)
After a call to EsbLROGetCatalog, the EsbLROUpdateObject API call does not update cell notes.

Pivoting Columns in Particular Spreadsheets Returns Error Message (10111, P1)
In particular spreadsheet views, pivoting a column dimension to a row location produces the following error message:

"Report heading cannot be interpreted."

This problem occurs when the database contains two or more dimensions with an identical hierarchy, and one of these dimensions is pivoted in the spreadsheet.

Lock and Send in Free Form Mode Hangs the Server (10120, P1)
In 32-bit Excel, performing a Lock and Send operation in Free-Form mode crashes the Essbase server. This crash occurs because the Spreadsheet Add-in is sent into a loop while attempting to copy byte-by-byte row information.

Application Event Log Not Reflecting Data Cache Settings (10123, P1)
On Windows NT (x86 machine), the application event log does not reflect the values set for data cache in Database | Settings | Storage. The settings are now displayed correctly.

Particular Spreadsheet Retrieval Crashes Server (10125, P1)
On Windows NT (x86 machine), a spreadsheet retrieval crashes the server when:

The Scenario dimension is dense and the Accounts dimension is sparse, and
The Accounts dimension contains Dynamic Calculation members.

Multiple Selection of Non-adjacent LROs Not Deleted Properly (10130, P1)
On all client operating systems, when you select non-adjacent linked reporting objects (LROs) from the Linked Objects Browser dialog box and click "Delete", all of the selected LRO's are not deleted.

Setting Concurrency Parameters Wait to "Indefinitely" or "(0) No Waiting" Produces Error Message (10132, P1)
Under Committed data block access, setting the "Concurrency Parameters Wait" option to "Indefinitely" or "(0) No Waiting" produces an error message.

Users with Create/Delete Application Privileges Cannot Delete Applications (10157, P1)
Users who have security privileges to "Create/Delete Applications" can create, but cannot delete, applications.

Particular Spreadsheet Retrieval Crashes Server (10158, P1)
On Windows NT (x86 machine), a spreadsheet Zoom operation crashes the Essbase server if you zoom in on the Scenario dimension when the Time dimension is dense and has a Dynamic Calc tag.

Member Select by Dynamic Time Series Fails with Numeric Member Names (10164, P1)
On Windows NT (x86 machine), when you specify the latest time period for a Dynamic Time Series member during Member Selection, if you select one of the numeric member names and press the Preview or OK button, Essbase returns an error message.

Retrieval with Duplicate Members in Sheet Crashes Server (10169, P1)
Under the following conditions, a retrieval in Excel crashes the server:

The title row of the sheet contains duplicate members.
A row before the first row dimension contains at least one data value.

For example:

Market Measures Product Scenario Market

#MISS

Year

Retrieving under these conditions in Essbase Version 4.1.2 did not produce a crash.

In Spreadsheet Add-in or GRID API, Linked Partition Retrieval Returns 0 Data Values (10171, 10381, P1)
In the Spreadsheet Add-in or the Grid API, retrieving linked partitions causes the database to display 0 values for the target database. The data values are correct when the linked partition definition is removed.

Error Message When Retrieving in Formatted Sheets Containing Particular Formulas (Excel 7.0) (10173, P1)
In Excel Version 7.0, retrieving data in formatted sheets that contain certain formulas produces an error message and crashes Excel.

SQL Drill on Invalid Data Point Crashes Server (10175, P1)
On Windows NT (x86 machine), attempting an SQL Drill-Through on a column heading against an Oracle 8 data source crashes the Essbase server.

Cascade Crash on Lotus 123 After Changing Double-Clicking Option in Essbase Option/Global (10176, P1)
If you invoke the Cascade command from a Lotus 1-2-3 client after launching a linked reporting object and then changing the settings for double-clicking (Essbase | Options | Global...), the Spreadsheet Add-in crashes. We were unable to test this fix because the problem was not reproducible in Hyperion's QA lab.

Using Member Selection with Generation Name Option and Pattern Matching Crashes Server (10178, P1)
In Excel, using Member Selection with the Generation Name option and Pattern Matching crashes the server and creates an exception log.

Retrieval on Cell with More Than 176 Characters Crashes Excel (10179, P1)
In an Excel spreadsheet, a retrieval on a cell containing more than 176 characters crashes Excel and generates an exception log.

Successive Spreadsheet Retrievals on Same Data Return Different Results (10190, P1)
In particular spreadsheets, successive retrievals on the same set of data produce different results. This problem occurs when there are complex, cross-dimensional formulas in the outline.

Failure of Dynamic Calc Retrievals on Sparse Members (10201, P1)
In spreadsheets, with certain outline configurations, a retrieval using Dynamic Calc on a sparse member fails with the following error message or a server crash:
"Need to copy ESM block during the dynamic calc. ESM block not found, Essbase internal error. Report to Arbor."

Canceling Retrieval Wizard Clears Objects Grid (10233, P1)
In Objects 1.0 and 1.1, if you open the Retrieval Wizard and then select Cancel, the Visual Grid is cleared.

Spreadsheet Operations Crash Server in Particular Sheets (10289, P1)
If a spreadsheet contains repeated member labels in nested columns and a spreadsheet query operation is performed (e.g., retrieval, zoom, pivot), the Essbase server crashes and generates an exception log.

Dialog Box Tabs in Japanese Version of Application Manager Not Translated Correctly (10296, P1)
Instead of showing Japanese characters, the tabs in Application Manager dialog boxes display incorrect single-byte ASCII characters.

Possible Data Loss When Doing Lock and Send to an Empty Database (10348, P1)
When doing Lock and Send to an empty database with an outline change on the same restructure, the next restructure can cause data loss.

Data Freespace Corruption Occurs During Fatal Error Handling (10357, P1)
Database freespace corruption occurs during fatal error handling.

When @CURRMBRRANGE and @MDSHIFT Are Used Inside a Complex Formula, Incorrect Values are Returned (10360, P1)
When @CURRMBRRANGE and @MDSHIFT are used inside a complex formula, incorrect values are returned.

EsbGetVersion Does Not Return Information (10367, P1)
The EsbGetVersion API call does not return version information for the connected Essbase server.

Installation Registration Program Returns Invalid Code after Successful Execution (10368, P1)
Registration program on installation runs correctly with a valid serial number, but upon exit returns an invalid 4-digit number instead of the proper "0".

Objects 1.1 Fails with Conditional Retrieve Method (10370, P1)
In Objects 1.1, an error message is returned when the EssGBeginConditionalRetrieve or EssGBeginConditionalZoomIn Grid API function is called.

Zooming In on Shared Members Deletes All Dimension Members (10390, P1)
In 32-bit Excel, zooming in on shared members causes all members of the dimension to disappear. The members of the dimension containing the original member remain intact.

Server Crashes with Failure of Assertion Error Message (10398, P1)
Under the following conditions, the Essbase server crashes with a "Failure of assertion 7061" error message:

Committed access is enabled
The Lock Timeout interval is set to Indefinite or to a specific timeout value entered in seconds
Multiple concurrent transactions are processing

Japanese Calc Script Editor Displays English Strings (10408, P1)
In the Japanese version of Application Manager, the following strings in the Calc Script Editor are displayed in English:

Find Member ...
Expand All
Use Aliases
Alias Table

Japanese Partition Manager and Partition Wizard Display English Strings (10409, P1)
Particular parts of the Japanese Partition Manager and Partition Wizard are displayed in English.

Agent Crashes During Concurrent SQL Access on Solaris (10410, P1)
On Solaris, the Agent crashes during concurrent SQL access.

Esssvr Crashes Trying to Connect to Oracle SQL Server on Solaris Platform (10412, P1)
Esssvr crashes trying to connect to Oracle SQL Server because ODBC 3.x does not allow connection on Solaris if the server thread stack size is too small.

Verify Button or Check Syntax Command in Particular Calc Script Crashes Application Manager (10444, P1)
With particular calc scripts, Application Manager crashes when you select the Verify button or the Syntax | Check Syntax command in the Calc Script Editor.

Windows NT Server Fails to Start When the globlc32.dll File in the Redist Directory is Copied to the Bin Directory (10448, P1)
On Windows NT, the server fails to start when the globlc32.dll file in the Redist directory is copied to the Bin directory. This problem occurs because the .dll in the Redist directory is older than the one in Bin.

Essbase Double-Clicking Not Working (Excel 97 Only) (10452, P1)
In Excel 97, the "Enable Double-Clicking" Option in the Essbase Options dialog box does not override Excel's "Edit Directly in Cell" option. This problem has been fixed so that the Excel in-cell editing option is automatically disabled when the Essbase "Enable Double-Clicking" option is enabled.

Search Function Fails in Calc Script Editor and Report Script Editor (10454, P1)
The search function (Find) does not work properly in Application Manager's Calc Script Editor and Report Script Editor.

Two Pass & Dynamic Calc Member of Accounts Dimension Not Calculating Properly (10455, 10460, P1)
In certain outline configurations, the correct calculation order is not being followed calculated, producing incorrect calculation results. This problem occurs when the Accounts dimension is Sparse and contains a member that is tagged Two Pass and Dynamic Calc.

Calc Script Syntax Verification Sometimes Fails When a Valid Substitution Variable Is Part of Script (10461, P1)
In Application Manager, a syntax check of a calc script containing a valid substitution variable may return a failure.

Server Crash During Sparse/Dense Configuration Change in Particular Outline (10465, P1)
In outlines with specific Dense/Sparse configurations and a Dynamic Time Series member present, the Essbase server may crash when a dimension is changed from Sparse to Dense or vice versa.

Shutting Down a Database with Rare Timing Scenario May Crash Server (10466, P1)
Shutting down a database may crash the Essbase server under very rare timing scenarios.

Server Crashes After Performing Lock and Send With Views that have Substitution Variables (10468, P1)
The Essbase server may crash after you perform Lock and Send operations on Spreadsheet Add-in with substitution variables.

Application Manager Crashes on Verification of a Calc Script Containing an Unmatched Quotation Mark (") (10485, P1)
If you have an unmatched quotation mark in a calc script, Application Manager crashes when verifying the calc script.

Server Error Messages Misreports Available Memory (10490, P1)
The available memory on the server is reported incorrectly in an error message.

Downloading Patches from the Hyperion Solutions Web Site

Using a Web browser such as Netscape Navigator or Microsoft Internet Explorer, connect to Hyperion's Technical Support Web site at:
http://support.hyperion.com/ts
Enter your Site ID, Server ID, and name; then click "Push the button to login."
If you do not already have access to Hyperion's Technical Support Web service, ask your your company's support contact to:
- call the support hotline at (408) 744-1200 or (203) 703-3600
- call the European support numbers:
```
Germany   00 49 40 32005285
          00 49 40 32005269
France    00 33 15 5940139
UK        00 44 1344 664007
```
- send e-mail to TSadmin@hyperion.com
Be sure to have your company's specific support contact initiate communication with Hyperion's Technical Support.
Click "Patch Central."
Do one of the following:
- Select the appropriate executable files to download, based on the "Files to Download" section below, and follow the on-screen downloading instructions.
- Click "5.0.1 Patch 9 Release Notes" to download the Release Notes file.

The "Problem Summary" section of the Release Notes contains the final list of problems fixed in the patch.

Files to Download

When downloading files from the Hyperion Web site, use the following lists as your guide to which file(s) you need.

NT or Windows Files

`501p12ns.exe`	NT (Intel) Server
`501p12ds.exe`	NT (Dec Alpha) Server
`501p1295.exe`	Win95 Server
`501p12ni.exe`	Windows NT SQL Interface
`501p12da.exe`	Dec Alpha API
`501p12na.exe`	NT and 32-bit Windows API
`501p1232.exe`	32-bit Excel Client (Excel V7 and V8)
`501p12l3.exe`	32-bit Lotus 1-2-3 Client
`501p12nd.exe`	32-bit SQL Drill-Through
`501p1216.exe`	16-bit Excel Client (Excel V5)
`501p12lo.exe`	16-bit Lotus 1-2-3 Client (Lotus 1-2-3 V5)
`501p12wd.exe`	16-bit SQL Drill-Through
`501P12am.exe`	16-bit Application Manager
`501p12wa.exe`	16-bit Windows API

OS/2 Files

`501p12os.exe`	OS/2 Server
`501p12oi.exe`	OS/2 SQL Interface
`501p12oa.exe`	OS/2 API

UNIX Files

`501p12hs.tar`	HP-UX Server
`501p12hi.tar`	HP-UX SQL Interface
`501p12ha.tar`	HP-UX API
`501p12ss.tar`	Solaris Server
`501p12si.tar`	Solaris SQL Interface
`501p12sa.tar`	Solaris API
`501p12as.tar`	AIX Server
`501p12ai.tar`	AIX SQL Interface
`501p12aa.tar`	AIX API

Installing Patches from the Hyperion Solutions Web Site

The patch installation is similar to a full Essbase installation, except that your sample applications, databases, and data files are not re-installed. Your existing applications and databases are not affected in any way. However, it is always a good idea to back up your applications and databases before an installation. For detailed information on Essbase installations, see the Installation Notes.

Follow the patch installation instructions for the appropriate platform:

NT or Windows Servers and Clients

OS/2 Servers and Clients

UNIX Servers and Clients

NT or Windows Servers and Clients

Make sure Essbase is not running when you perform the patch installation procedure.
Before downloading the appropriate executable file(s), create a temporary local directory on the server or client machine, as appropriate.
Connect to Hyperion's Technical Support Web site at:
http://support.hyperion.com/ts
Click "Patch Central."
Download the appropriate file(s) to the temporary directory you created. For more information, see Files to Download.
If you are installing more than one patch file, download the files into separate temporary directories before installing, or download and install one file, delete the file, and then download the next file.
Expand the executable file by typing the name of the file (without the extension) from a command prompt, or by double-clicking the file.
The executable file decompresses into separate directories (Disk1, Disk2, etc.) and runs SETUP.EXE from the Disk1 directory, which launches the installation program.
Follow the on-screen instructions to perform a full Essbase installation.
After the files are expanded, you can delete the .EXE file.

OS/2 Servers and Clients

Make sure Essbase is not running when you perform the patch installation procedure.
Before downloading the appropriate compressed file(s), create a temporary local directory on the server or client machine, as appropriate.
Connect to Hyperion's Technical Support Web site at:
http://support.hyperion.com/ts
Click "Patch Central."
Download the appropriate file(s) to the temporary directory you created. For more information, see Files to Download.
Expand the compressed file by typing the file name followed by "-d" from a command prompt. For example:
501p12os.exe -d
Each file automatically decompresses into separate directories (Disk1, Disk2, etc.).
Run SETUP.EXE from the Disk1 directory.
Follow the on-screen instructions to perform a full Essbase installation.
After the files are expanded, you can delete the .EXE file.

UNIX Servers and Clients

On the UNIX platforms, the patch installation disables SQL Interface. SQL Interface must be reinstalled or reconfigured after installing the patch.

Make sure Essbase is not running when you perform the patch installation procedure.
Before downloading the appropriate .tar file(s), create a temporary local directory on the server or client machine, as appropriate.
Connect to Hyperion's Technical Support Web site at:
http://support.hyperion.com/ts
Click "Patch Central."
Download the appropriate file(s) to the temporary directory you created. For more information, see Files to Download.
To untar a file, enter the following command:
tar -xf filename.tar
from the temporary directory containing the .tar file. This command extracts the files necessary to perform a complete installation.
Run essinst to launch the installation program.
Follow the on-screen instructions to perform a full Essbase installation.
After the files are expanded, you can delete the .tar file.

Installing Patches from CD-ROM

On the UNIX platforms, the patch installation disables SQL Interface. SQL Interface must be reinstalled or reconfigured after installing the patch.

For detailed information on Essbase installations, see the Installation Notes.

Make sure Essbase is not running when you perform the patch installation procedure.
Before copying the appropriate patch file(s), create a temporary local directory on the server or client machine, as appropriate.
Insert the CD-ROM into your CD-ROM drive.
Select the appropriate executable files to copy to your local drive, based on the Files to Download section.
Copy the appropriate file(s) to the temporary directory you created.
If you are installing more than one patch file, download the files into separate temporary directories before installing, or download and install one file, delete the file, and then download the next file.
Follow the instructions for the appropriate platform:
For Windows platforms:
- Expand the executable file by typing the name of the file (without the extension) from a command prompt, or by double-clicking the file.
  The executable file decompresses into separate directories (Disk1, Disk2, etc.) and runs SETUP.EXE from the Disk1 directory, which launches the installation program.
For OS/2 platforms:
- Expand the compressed file by typing the file name followed by "-d" from a command prompt. For example:
  
  501p12os.EXE -d
  Each file automatically decompresses into separate directories (Disk1, Disk2, etc.).
- Run SETUP.EXE from the Disk1 directory.
For UNIX platforms:
- To untar a file, enter the following command:
  tar -xf filename.tar
  from the temporary directory containing the .tar file. This command extracts the files necessary to perform a complete installation.
- Run essinst to launch the installation program.
Follow the on-screen instructions to perform a full Essbase installation.

Hyperion Integration Server Drill-Through

Version 5.0.1 Patch 2 and later patches provide code and online help for the Hyperion Integration Server Drill-Through feature. Be sure to install both the Patch 2 or later Server and the Patch 2 or later 32-bit Spreadsheet Add-in. If you use a Patch 2 or later Spreadsheet Add-in with a pre-Patch 2 server, spreadsheet retrievals will fail.
Patch 5 provides bug fixes and a revised (final) online help file for the Hyperion Integration Server Drill-Through feature.

For both patch installations, the online help file for Drill-Through, OLAPSQLD.HLP, is installed to the ESSBASE\BIN directory.

ODBC Driver Support for SQL Interface on UNIX

Hyperion Solutions supports the ODBC interface.

INTERSOLV Version 3.02 ODBC drivers are provided with Hyperion Essbase Version 5.0.1 Patch 2 (or later) SQL Interface for Informix, Oracle, and Sybase databases on AIX, HP-UX, and Solaris platforms.

Hyperion Solutions has tested the following database configurations.

Database Server (via Database Client) AIX 4.3 HP-UX 10.20 Solaris 2.6

Informix 7.22 Server (via Informix Client SDK 2.01 with esql 9.14) XY

Oracle 7.3.2 Server (via Oracle 7.3.3 client) X

Oracle 7.3.2 Server (via Oracle 7.3.4 client) X X

Sybase Adaptive Server Enterprise 11.5 (via Sybase Open Client 11.1.1) X X X

X =
The INTERSOLV Version 3.02 ODBC drivers for these configurations of database server, database client, and UNIX platform have been tested with Hyperion Essbase Version 5.0.1 Patch 2 SQL Interface. They work successfully, subject to the limitations documented in the final PATCH.HTM file, which can be found on the Hyperion Solutions Web site's "Enter Technical Support Section" ( http://www.hyperion.com/edu_supp/enterts.html).

XY =
Two INTERSOLV Version 3.02 ODBC drivers for Informix on Solaris have been tested with Hyperion Essbase Version 5.0.1 Patch 2 SQL Interface. One, ARif7912.so, works with the Informix 7.22 Server and Informix Client SDK 2.01 with esql 9.14, subject to the limitations documented in the final PATCH.HTM file, which can be found on the Hyperion Solutions Web site's "Enter Technical Support Section" (http://www.hyperion.com/edu_supp/enterts.html). The other, ARinf12.so for the Informix 7 client (which is not thread-safe), does not work.

A blank cell indicates that the INTERSOLV Version 3.02 ODBC drivers for these configurations of database server, database client, and UNIX platform have not been tested with Hyperion Essbase Version 5.0.1 Patch 2 SQL Interface.

HP-UX SQL Interface Installation Instructions

Hyperion Essbase Version 5.0.1 Patch 2 (or later) SQL Interface runs on the HP-UX platform.

See ODBC Driver Support for SQL Interface on UNIX for tested database configurations. See Chapter 1, Product Components and Software Registration, of Hyperion Essbase Version 5.0.1 Installation Notes for information on the software registration process.

This section contains the following information:

Before Installing SQL Interface on HP-UX
Installing SQL Interface on HP-UX from CD-ROM
Installing SQL Interface on HP-UX from Downloadable Files
Before Linking SQL Interface to Your INTERSOLV ODBC Driver
Linking SQL Interface to Your INTERSOLV ODBC Driver
After Linking SQL Interface to Your INTERSOLV ODBC Driver
Configuring Your Data Source and ODBC Driver

Before Installing SQL Interface on HP-UX

You must install the Hyperion Essbase 5.0.1 Patch 2 (or later) server on HP-UX before you install Hyperion Essbase SQL Interface on HP-UX. Follow these steps:

Install the Hyperion Essbase Version 5.0.1 Patch 2 (or later) server.
Update your environment settings.
Verify that the Essbase server is working.

For information on installing the Essbase server and updating the environment on HP-UX, see Chapter 2, CD-ROM Installation, and Chapter 6, UNIX Server Installation, of the Hyperion Essbase Version 5.0.1 Installation Notes.

Also, you must install your relational database management system (including the correct database client), and you must set the required environment variables to run your RDBMS, before you install SQL Interface on HP-UX.

On Oracle, set ORACLE_HOME and ORACLE_SID. Also, make sure that SHLIB contains the Oracle library path ($ORACLE_HOME/lib). On Sybase, set SYBASE and DSQUERY. Also, make sure that SHLIB contains the Sybase library path ($SYBASE/lib).

For Informix users, set INFORMIXDIR and INFORMIXSERVER. Also, make sure that SHLIB contains the Informix library path ($INFORMIXDIR/lib).

Installing SQL Interface on HP-UX from CD-ROM

To install SQL Interface on HP-UX from CD-ROM, complete the following steps:

Log in to the server as arbor.
Insert the CD-ROM into your CD-ROM drive.
Change to the top directory of the CD-ROM (for example, cd\cdrom).
Use the ls command to find setup.sh (or SETUP.SH).
Some UNIX CD-ROM drivers list file names in uppercase. Others list them in lowercase. See whether setup.sh is in uppercase or lowercase.
Enter ./setup.sh or ./SETUP.SH, depending on what you learned in step 4.
When prompted for which product to install, select SQL Interface.
Follow the prompts and provide the information requested.
To cancel installation at any time, press Ctrl-C.
When prompted, enter your license number exactly as it appears on your registration card.
See Chapter 1, Product Components and Software Registration, of the Installation Notes for more information on software registration.
When prompted, type the directory where you want to install Essbase.

The installation program uses \home\essbase as the default directory. You can choose another directory, and if it does not exist, the installation program will create it for you.

After you install SQL Interface on HP-UX, you must take additional steps to set your environment. See the following sections for more information.

Installing SQL Interface on HP-UX from Downloadable Files

To install SQL Interface on HP-UX using downloadable files from the Hyperion Solutions Web Site, complete the following steps:

Make sure Essbase is not running when you perform the patch installation procedure.
Note: The name of the appropriate file to download varies depending on which patch you are installing. For example, the appropriate file for Patch 2 is 501p2hi.tar.
Before downloading the appropriate file, create a temporary local directory on the server or client machine, as appropriate.
Connect to the Hyperion Solutions Web site's "Enter Technical Support Section" ( http://www.hyperion.com/edu_supp/enterts.html) and download the appropriate file to the temporary directory you created.
To untar the file, enter the following command:
tar -xf 501p2hi.tar
from the temporary directory containing the file. This command extracts the files necessary to perform the installation.
Run essinst to launch the installation program.
Follow the on-screen instructions to install SQL Interface.
After the .tar file is expanded, you can delete it.

Before Linking SQL Interface to Your INTERSOLV ODBC Driver

After you install SQL Interface on HP-UX by running setup.sh, you must set certain environment variables before you run inst-sql.sh to link SQL Interface to your ODBC driver. The steps you take depend on the driver you will use.

On Oracle 7.1, if the $ORACLE_HOME/lib directory does not contain the libclntsh.sl file, make the file by completing the following steps:

Log in as user arbor.
Make sure you have Write access to the $ORACLE_HOME/lib directory. For example, type:
```
su oracle
```
Type the following:
```
make -f $ARBORPATH/bin/genclntsh.mk
```

On Oracle 7.2 and 7.3, if the $ORACLE_HOME/lib directory does not contain the libclntsh.sl file, make the file by completing the following steps:

Log in as user oracle.
Change to the $ORACLE_HOME/rdbms/lib directory.
Modify the clntsh.mk file by adding -lsql to the end of each ld command.
Type the following:
```
make -f clntsh.mk shlib
```

For more information on setting environment variables for your ODBC driver, see the INTERSOLV DataDirect ODBC Drivers Reference, which is in .PDF format in your $ARBORPATH\ODBCDOCS directory. To view this document, use Adobe� Acrobat Reader� Version 3.0.1, which is provided in the ADOBE directory for HP-UX on the Essbase 5.0.1 CD-ROM. Also see Oracle, Sybase, or Informix documentation.

Linking SQL Interface to Your INTERSOLV ODBC Driver

The following files are installed with the Essbase server on HP-UX:

The SQL Interface library file (libesssql.sl)
A stub ODBC drivers file (libesssql.arbor.sl)

The INTERSOLV ODBC drivers file (libesssql.insolv.sl) is installed with SQL Interface on HP-UX.

The SQL Interface library file symbolically links to the stub ODBC driver file until SQL Interface is installed. You then link the library file to the INTERSOLV ODBC drivers file by running inst-sql.sh. Running inst-sql.sh ensures that server processes can access the software necessary for SQL Interface.

The inst-sql.sh script uses the odbc.ini, odbcinst.ini, and template (extension .tmpl) files in the $ARBORPATH\setup directory to create a set of files that point Essbase to the correct driver product.

The script handles the following for you:

Ensures root privileges are not accidentally granted to a user-level script
Checks for the availability of the Essbase server
Checks for the availability to the Essbase server of supported database systems
Provides default environment extensions as shell files in the $ARBORPATH\bin directory
Provides initialization files in $ARBORPATH\bin for access by the driver software

To run inst-sql.sh, enter the following command, still as user arbor:

inst-sql.sh

Essbase prompts you to supply information when necessary. When the script finishes, the command prompt appears. Enter:

exit

Under some circumstances, you may need to have an extra library dynamically compiled. If the script determines you need an extra library, it creates and compiles it for you.

After Linking SQL Interface to Your INTERSOLV ODBC Driver

inst-sql.sh generates odbc.csh for the C shell, and odbc.sh for the Bourne or Korn shell. These files contain commands that specify the correct environment variables for Essbase. After you run inst-sql.sh, and link SQL Interface to your INTERSOLV ODBC driver, you must make these Essbase environment variables available to your current shell environment.

To make the Essbase environment variables available to your current shell environment, do one of the following:

In the C shell, use the source command against odbc.csh in the .login or .cshrc file.
In the Bourne or Korn shell, use the source command against odbc.sh in the . (period) in the .profile file.

For example, add the following statement to your .login or .cshrc file:

% source $ARBORPATH\setup\odbc.csh

To change the environment settings, edit odbc.csh or odbc.sh.

Configuring Your Data Source and ODBC Driver

After you install SQL Interface on HP-UX and set your environment variables, you must configure your data source. You may need to configure your ODBC driver.

For more information on configuring your data source and ODBC driver, see the SQL Interface Guide. Also see the INTERSOLV DataDirect ODBC Drivers Reference in your $ARBORPATH\ODBCDOCS directory. To view the INTERSOLV document, which is in .PDF format, use Adobe� Acrobat Reader� Version 3.0.1, which is provided in the ADOBE directory for HP-UX on the Essbase 5.0.1 CD-ROM.

Revised Spreadsheet Documentation

Certain spreadsheet documentation has been revised since the Hyperion Essbase Version 5.0.1 release. Patch 5 (or later) contains the most recent documentation.

The following online help files have been modified:

ESSEXCEL.HLP
ESSLRO.HLP

These two files are installed during the patch installation process to the ESSBASE\BIN directory, overwriting the existing files of the same name.

The online Spreadsheet Add-in User's Guide for Excel has been modified. This file, ESSEXCEL.PDF, is installed during the patch installation process to the ESSBASE\DOCS\CLIENT directory, overwriting the existing file of the same name.

LROs On Shared Members

Patch 8 contains a new ESSBASE.CFG option, LROONSHAREDMBR, which lets you specify whether shared members have Linked Reporting Objects that are unique from those of their corresponding regular members.

The default (and pre-Patch 8) behavior is as follows: Shared members do not share LROs with their corresponding regular members. To retain this behavior, you do not need to do anything.

LROONSHAREDMBR

Syntax

LROONSHAREDMBR TRUE | FALSE

TRUE LROs related to regular members are not shared by shared members. The default value is TRUE.

FALSE Shared members have the same LROs as corresponding regular members.

Description

A Linked Reporting Object (LRO) is an external file, cell note, or URL that you link to a cell in a Hyperion Essbase database. Users can then retrieve the object from the Spreadsheet Add-in.
A LROONSHAREDMBR setting of TRUE tells Essbase to make shared member LROs unique from the LROs of regular members.
For example, assume the LROONSHAREDMBR option is FALSE. If you link an LRO to the data cell related to Diet Colas (100-20) under the parent member Colas (100), the corresponding data cell for Diet Colas (100-20) under the parent member Diet shares the same LRO.

Example

LROONSHAREDMBR FALSE

New Essbase APIs

Patch 6 contains new APIs for three different areas:

Stream Data Loading
Setting ARBORPATH
Hyperion Integration Server Drill-Through

Stream Data Loading

Two new C Main API functions (EssBeginDataLoad() and EssEndDataLoad()) improve stream data loading by continuing to load rows, and record errors, after an improper row is encountered.

EssBeginDataload

Description

EssBeginDataload() starts sending an update specification to the active database, and can unlock any data blocks locked for update. The update data can either be stored in the database, or just verified and any errors returned.

Syntax

ESS_STS_T EssBeginDataload (hCtx, Store, Unlock, abortOnError, pRules);

ESS_HCTX_T	hCtx;
ESS_BOOL_T	Store;
ESS_BOOL_T	Unlock;
ESS_BOOL_T	abortOnError;
ESS_POBJDEF_T	pRules;

Parameters

hCtx	Essbase API context handle.
Store	Controls storage of data. If TRUE, data is stored in the server; if FALSE, no data is stored.
Unlock	Controls unlocking of data blocks. If TRUE, all relevant blocks which are locked will be unlocked (after data is stored, if necessary). If FALSE, no blocks are unlocked.
abortOnError	If TRUE, data load stops on the first error. Otherwise, data load continues.
pRules	Pointer to the rules file object definition structure.

Return Value

None.

Notes

EssBeginDataload() must be followed by at least one call to EssSendString() to send the update specification, and then a call to EssEndDataload().
Each string passed to EssSendString() following EssBeginDataload() must be terminated with a carriage return/linefeed character sequence ("\r\n").
If both the Store and Unlock flags are set to FALSE, the database merely performs a syntax check of the update specification.
Unlike EssBeginUpdate(), which ignores input rows (records) after an improper input row, EssBeginDataload() processes the remaining input rows, and commits them if appropriate.
EssEndDataload() returns a linked list of errors in ESS_MBRERR_T.

Access

EssBeginDataload() requires the caller to have write privilege (ESS_PRIV_WRITE) to the active database.

Example

ESS_STS_T     sts = ESS_STS_NOERR;
ESS_BOOL_T    Store;
ESS_BOOL_T    Unlock; 
ESS_STR_T     Query1, Query2;
ESS_PMBRERR_T pMbrErr;
   
   Store  = ESS_TRUE;
   Unlock = ESS_FALSE;
   Query1 = "Year Market Scenario Measures Product 12345";
   Query1 = " Jan  East  Scenario Measures Coke  125";
                  
   /* Begin Update */
   sts = EssBeginDataload (hCtx, Store, Unlock, ESS_FALSE, ESS_NULL);  
   
   /* Send update specification */
   if(!sts)
      sts = EssSendString(hCtx, Query1);
      sts = EssSendString(hCtx, Query2);
      
   /* End Update */
   if(!sts)
      sts = EssEndDataload(hCtx, &pMbrErr);

EssEndDataload

Description

EssEndDataload() marks the end of an update specification being sent to the active database, and must be called after sending the update specification using EssSendString().

Syntax

ESS_STS_T EssEndDataload (hCtx, ppMbrError);

ESS_HCTX_T	hCtx;
ESS_PPMBRERR_T	ppMbrError;

Parameters

hCtx

Essbase API context handle.

ppMbrError

Pointer to the linked list of errors contained in ESS_MBRERR_T. Possible errors (and error strings) are:

ESS_MBRERR_UNKNOWN (Unknown member [membername] in dataload, [number] records returned.)
ESS_MBRERR_DBACCESS (You have insufficient access privilege to perform a lock on this database.)
ESS_MBRERR_BADDATA (Invalid member [membername] in data column.)
ESS_MBRERR_DUPLICATE (Duplicate members from the same dimension on data record, [number] records completed.)
AD_MSGDL_ERRORLOAD (Unable to do dataload at Item/Record [number].)

Return Value

Returns zero, if successful. Otherwise, returns an error code, as follows:

If abortOnError is TRUE:
- The error code for the first error condition is returned.
- The error list is NULL.
If abortOnError is FALSE:
- An error list is returned, if the server can process the data and can continue.
- Otherwise, in exceptional circumstances, the error code explaining why the server cannot continue is returned. For example:
  AD_MSGDL_COLS (too many data values in a record)
  AD_MSGDL_MISDIM (data value encountered before all dimensions selected)

Notes

EssEndDataload() must be preceded by a call to EssBeginDataload(), and at least one call to EssSendString().
The memory allocated for ppMbrErr must be freed using EssFreeMbrErr().

Access

EssEndDataload() requires the caller to have write privilege (ESS_PRIV_WRITE) to the active database.

Example

ESS_STS_T     sts = ESS_STS_NOERR;
ESS_BOOL_T    Store;
ESS_BOOL_T    Unlock; 
ESS_STR_T     Query1, Query2;
ESS_PMBRERR_T pMbrErr;
   
   Store  = ESS_TRUE;
   Unlock = ESS_FALSE;
   Query1 = "Year Market Scenario Measures Product 12345";
   Query1 = " Jan  East  Scenario Measures Coke  125";
                  
   /* Begin Update */
   sts = EssBeginDataload (hCtx, Store, Unlock, ESS_FALSE, ESS_NULL);  
   
   /* Send update specification */
   if(!sts)
      sts = EssSendString(hCtx, Query1);
      sts = EssSendString(hCtx, Query2);
      
   /* End Update */
   if(!sts)
      sts = EssEndDataload(hCtx, &pMbrErr);

Setting ARBORPATH

Three new APIs (EssSetPath(), EsbSetPath(), and EssGSetPath()) set the ARBORPATH variable for the current API process at runtime, enabling the API to locate the Locale directory and the default message database.

EssSetPath

Description

EssSetPath() sets the ARBORPATH environment variable for the current process.

Syntax

ESS_FUNC_M EssSetPath (pszPath);

ESS_STR_T

pszPath;

Parameters

pszPath

Pointer to the string describing the ARBORPATH environment variable

Return Value

If successful, returns ESS_STS_NOERR.
If pszPath is too long, returns API_NAME_TOO_LONG (1030009).

Notes

Call EssSetPath() before calling EssInit().
pszPath cannot exceed 120 characters, as defined in ESS_PATHLEN.
pszPath applies only to the current process.
Hyperion (Arbor) DLLs must be accessible from the system path. EssSetPath() does not resolve the path for the Hyperion (Arbor) DLLs.

Example

ESS_STS_T
ESS_SetPath()
{ 
   ESS_STS_T sts;
   ESS_STR_T pszPath = "C:\\Essbase";
   sts = EssSetPath (pszPath);
   return sts;
}

EsbSetPath

Description

EsbSetPath() sets the ARBORPATH environment variable for the current process.

Syntax

EsbSetPath (Path)

ByVal Path As String

Parameters

Path

String describing the ARBORPATH environment variable

Return Value

If successful, returns ESB_STS_NOERR.
If Path is too long, returns API_NAME_TOO_LONG (1030009).

Notes

Call EsbSetPath() before calling EsbInit().
pszPath cannot exceed 120 characters, as defined in ESB_PATHLEN.
pszPath applies only to the current process.
Hyperion (Arbor) DLLs must be accessible from the system path. EsbSetPath() does not resolve the path for the Hyperion (Arbor) DLLs.

Example

Sub ESB_SetPath
   Dim sts  As Long
   Dim Path As String
   
   Path = "C:\Essbase"
   sts  = EsbSetPath(Path)
End Sub

EssGSetPath

Description

EssGSetPath() sets the ARBORPATH environment variable for the current process.

Syntax

ESSG_FUNC_M EssGSetPath (pszPath);

ESSG_STR_T

pszPath;

Parameters

pszPath

Pointer to the string describing the ARBORPATH environment variable

Return Value

If successful, returns ESSG_STS_NOERR.
If pszPath is too long, returns API_NAME_TOO_LONG (1030009).

Notes

Call EssGSetPath() before calling EssGInit().
pszPath cannot exceed 120 characters, as defined in ESSG_PATHLEN.
pszPath applies only to the current process.
Hyperion (Arbor) DLLs must be accessible from the system path. EssGSetPath() does not resolve the path for the Hyperion (Arbor) DLLs.

Example

ESS_STS_T
ESSG_SetPath()
{ 
   ESS_STS_T  sts;
   ESSG_STR_T pszPath = "C:\\Essbase";
   sts = EssGSetPath (pszPath);
   return sts;
}

Hyperion Integration Server Drill-Through

Four new C Main API functions, seven new Grid API functions, and several new constants, data types, and structures provide Hyperion Integration Server Drill-Through functionality.

In addition to four new functions (EssDTGetHeader(), EssDTGetData(), EssDTClose(), and EssDTExit()), the C Main API has a new constant, data type and structure for Drill-Through functionality.

Constant Definition

ESS_DESCRIPTION_LEN Maximum length (255) of string data retrieved by EssDTGetData() or EssDTGetHeader()

Data Type Essbase Type Description

typedef ESS_DTINST_T *ESS_PDTINST_T pointer to a drill-through initialization structure

ESS_DTBUFFER_T

This structure defines a report data cell.

typedef struct ESS_DTBUFFER_T
{
   ESS_ULONG_T row;
   ESS_ULONG_T column;
   ESS_CHAR_T  data[ESS_DESCRIPTION_LEN + 1];
} ESS_DTDATA_T, *ESS_PDTDATA_T, **ESS_PPDTDATA_T;

Data Type Field Description

ESS_ULONG_T row 0-indexed row number for the given data block.

ESS_ULONG_T column 0-indexed column number for the given data block.

ESS_CHAR_T data [ESS_DESCRIPTION_LEN + 1] Data value for the given data block.

EssDTGetHeader

Description

EssDTGetHeader() retrieves the report data header information for the given drill-through instance handle.

Syntax

ESS_FUNC_M EssDTGetHeader (pDTInst, pBuffer, pulCount);

ESS_PDTHINST_T pDTInst;

ESS_PPDTBUFFER_T pBuffer;

ESS_PULONG_T pulCount;

Parameters

pDTInst Initialized drill-through instance handle.

pBuffer Array of header information structures for given columns.

pulCount Count of data blocks in the pBuffer header information array.

EssDTGetData

Description

EssDTGetData() retrieves an array of report data for the given drill-through instance handle.

Syntax

ESS_FUNC_M EssDTGetData (pDTInst, pBuffer, pulCount);

ESS_PDTHINST_T pDTInst;

ESS_PPDTBUFFER_T pBuffer;

ESS_PULONG_T pulCount;

Parameters

pDTInst Initialized drill-through instance handle.

pBuffer Array of report data structures for given data cells.

pulCount Count of data blocks in the pBuffer header information array.

Notes

Call EssDTGetData() until pulCount is 0 (zero).

EssDTClose

Description

EssDTClose() ends the drill-through session for the given drill-through instance handle.

Syntax

ESS_FUNC_M EssDTClose (pDTInst);

ESS_PDTHINST_T pDTInst;

Parameters

pDTInst Initialized drill-through instance handle for the given data cell range(s).

Notes

EssDTClose() closes the drill-through session, but does not free up memory.
EssDTExit() closes the drill-through session and frees up memory.

EssDTExit

Description

EssDTExit() ends the drill-through session and frees up memory for the given drill-through instance handle.

Syntax

ESS_FUNC_M EssDTExit (pDTInst);

ESS_PDTHINST_T pDTInst;

Parameters

pDTInst Initialized drill-through instance handle for the given data cell range(s).

Notes

EssDTExit() closes the drill-through session and frees up memory.
EssDTClose() closes the drill-through session, but does not free up memory.

In addition to seven new functions (EssGDTBeginDrillThrough(), EssGDTEndDrillThrough(), EssGDTGetData(), EssGDTGetHeader(), EssGDTGetReportData(), EssGDTListReports(), and EssGDTReportCount()), the Grid API has six new constants, a new data type, and two new structures for Driil-Through functionality.

Three constants are used by the Grid API Drill-Through functions (EssGDTxxx()).

Constant	Definition
`ESSG_DESCRIPTION_LEN`	Maximum length (255) of string data retrieved in ESSG_DTDATA_T by EssGDTGetData(), or in ESSG_DTHEADER_T by EssGDTGetHeader()
`ESSG_ERR_INVALIDDTHANDLE`	Error message constant returned to caller if the given drill-through instance handle is invalid
`ESSG_ERR_NODTREPORTS`	Error message constant returned to caller if no drill-through report is defined for the given drill-through instance handle

Three constants are used by ESSG_DTHEADER_T in EssGDTGetHeader() to specify the type of report data header information to be retrieved.

Constant Definition

ESSGDTINT 0

ESSGDTFLOAT 1

ESSGDTSTRING 2

One new data type is used by the Grid API Drill-Through functions (EssGDTxxx()).

Data Type Essbase Type

typedef ESSG_PVOID_T ESSG_DTHINST_T, *ESSG_PDTHINST_T ESSG_DTHINST_T, ESSG_PDTHINST_T

Data Type	Essbase Type
typedef ESSG_PVOID_T ESSG_DTHINST_T, *ESSG_PDTHINST_T	`ESSG_DTHINST_T, ESSG_PDTHINST_T`

This structure defines header information for a specific column.

typedef struct ESSG_DTHEADER_T
{
   ESSG_ULONG_T         colIndex;
   ESSGDTREPORTDATATYPE dataType;
   ESSG_CHAR_T          data[ESSG_DESCRIPTION_LEN + 1];
} ESSG_DTHEADER_T, *ESSG_PDTHEADER_T, **ESSG_PPDTHEADER_T;

Data Type Field Description

ESSG_ULONG_T colIndex 0-based index of the column position.

ESSGDTREPORTDATATYPE dataType Data type of the given column of data.

ESSG_CHAR_T data [ESSG_DESCRIPTION_LEN + 1] Heading text for the given column of data.

This structure defines a report data cell.

typedef struct ESSG_DTDATA_T
{
   ESSG_ULONG_T row;
   ESSG_ULONG_T column;
   ESSG_CHAR_T  data[ESSG_DESCRIPTION_LEN + 1];
} ESSG_DTDATA_T, *ESSG_PDTDATA_T, **ESSG_PPDTDATA_T;

Data Type Field Description

ESSG_ULONG_T row 0-indexed row number for the given data block.

ESSG_ULONG_T column 0-indexed column number for the given data block.

ESSG_CHAR_T data [ESSG_DESCRIPTION_LEN + 1] Data value for the given data block.

EssGDTBeginDrillThrough

Description

EssGDTBeginDrillThrough() returns the drill-through instance handle for the given data cell range(s).

Syntax

ESSG_FUNC_M EssGDTBeginDrillThrough (hGrid, usCells, pCells, ppDTInst);

ESSG_HGRID_T hGrid;

ESSG_USHORT_T usCells;

ESSG_PRANGE_T pCells;

ESSG_PPDTHINST_T ppDTInst;

Parameters

hGrid Handle of the original grid returned by EssGNewGrid().

usCells Number of cell ranges in the pCells array.

pCells Array of cell ranges selected to receive drill-through report data.

ppDTInst Drill-through instance handle returned for the given data cell range(s).

EssGDTEndDrillThrough

Description

EssGDTEndDrillThrough() ends the drill-through session and frees up memory for the given drill-through instance handle.

Syntax

ESSG_FUNC_M EssGDTEndDrillThrough (pDTInst);

ESSG_PDTHINST_T pDTInst;

Parameters

pDTInst Initialized drill-through instance handle for the given data cell range.

EssGDTGetData

Description

EssGDTGetData() retrieves an array of report data for the given drill-through instance handle.

Syntax

ESSG_FUNC_M EssGDTGetData (pDTInst, pBuffer, pulCount);

ESSG_PDTHINST_T pDTInst;

ESSG_PPDTDATA_T pBuffer;

ESSG_PULONG_T pulCount;

Parameters

pDTInst Initialized drill-through instance handle.

pBuffer Array of report data structures for given data cells.

pulCount Count of data blocks in the pBuffer array.

Notes

Call EssGDTGetData() until pulCount is 0 (zero).

EssGDTGetHeader

Description

EssGDTGetHeader() retrieves the report data header information for the given drill-through instance handle.

Syntax

ESSG_FUNC_M EssGDTGetHeader (pDTInst, pBuffer, pulCount);

ESSG_PDTHINST_T pDTInst;

ESSG_PPDTHEADER_T pBuffer;

ESSG_PULONG_T pulCount;

Parameters

pDTInst Initialized drill-through instance handle.

pBuffer Array of header information structures for given columns.

pulCount Count of data blocks in the pBuffer header information array.

EssGDTGetReportData

Description

EssGDTGetReportData() executes the predefined default drill-through report for the given data cell range, and returns report data via the given grid handle hDAGrid.

Syntax

ESSG_FUNC_M EssGDTGetReportData (hGrid, hDAGrid, usCells, pCells);

ESSG_HGRID_T hGrid;

ESSG_HGRID_T hDAGrid;

ESSG_USHORT_T usCells;

ESSG_PRANGE_T pCells;

Parameters

hGrid Handle of the original grid returned by EssGNewGrid().

hDAGrid Handle of the new grid to receive drill-through report data.

usCells Number of cell ranges in the pCells array.

pCells Array of cell ranges selected to receive drill-through report data.

EssGDTListReports

Description

EssGDTListReports() returns a list of report names for the given drill-through instance handle.

Syntax

ESSG_FUNC_M EssGDTListReports (pDTInst, pBuffer, pulCount);

ESSG_PDTHINST_T pDTInst;

ESSG_PSTR_T pBuffer;

ESSG_PULONG_T pulCount;

Parameters

pDTInst Initialized drill-through instance handle.

pBuffer Array of report names for the given drill-through instance handle.

pulCount Count of blocks in the pBuffer header information array.

EssGDTReportCount

Description

EssGDTReportCount() returns the number of reports defined for the given data cell range(s).

Syntax

ESSG_FUNC_M EssGDTReportCount (hGrid, usCells, pCells, uspReportNum);

ESSG_HGRID_T hGrid;

ESSG_USHORT_T usCells;

ESSG_PRANGE_T pCells;

ESSG_PUSHORT_T uspReportNum;

Parameters

hGrid Handle of the original grid returned by EssGNewGrid().

usCells Number of cell ranges in the pCells array.

pCells Array of cell ranges selected to receive drill-through report data.

uspReportNum Number of reports defined for the given data cell range(s).

Database Server (via Database Client)	AIX 4.3	HP-UX 10.20	Solaris 2.6
Informix 7.22 Server (via Informix Client SDK 2.01 with esql 9.14)			XY
Oracle 7.3.2 Server (via Oracle 7.3.3 client)			X
Oracle 7.3.2 Server (via Oracle 7.3.4 client)	X	X
Sybase Adaptive Server Enterprise 11.5 (via Sybase Open Client 11.1.1)	X	X	X

TRUE	LROs related to regular members are not shared by shared members. The default value is TRUE.
FALSE	Shared members have the same LROs as corresponding regular members.

Constant	Definition
ESS_DESCRIPTION_LEN	Maximum length (255) of string data retrieved by EssDTGetData() or EssDTGetHeader()

Data Type	Essbase Type	Description
typedef ESS_DTINST_T	*ESS_PDTINST_T	pointer to a drill-through initialization structure

Data Type	Field	Description
ESS_ULONG_T	row	0-indexed row number for the given data block.
ESS_ULONG_T	column	0-indexed column number for the given data block.
ESS_CHAR_T	data [ESS_DESCRIPTION_LEN + 1]	Data value for the given data block.

ESS_PDTHINST_T	pDTInst;
ESS_PPDTBUFFER_T	pBuffer;
ESS_PULONG_T	pulCount;

pDTInst	Initialized drill-through instance handle.
pBuffer	Array of header information structures for given columns.
pulCount	Count of data blocks in the pBuffer header information array.

Constant	Definition
`ESSGDTINT`	0
`ESSGDTFLOAT`	1
`ESSGDTSTRING`	2

ESSG_HGRID_T	hGrid;
ESSG_USHORT_T	usCells;
ESSG_PRANGE_T	pCells;
ESSG_PPDTHINST_T	ppDTInst;

hGrid	Handle of the original grid returned by EssGNewGrid().
usCells	Number of cell ranges in the pCells array.
pCells	Array of cell ranges selected to receive drill-through report data.
ppDTInst	Drill-through instance handle returned for the given data cell range(s).

ESSG_PDTHINST_T	pDTInst;
ESSG_PPDTDATA_T	pBuffer;
ESSG_PULONG_T	pulCount;

ESSG_PDTHINST_T	pDTInst;
ESSG_PPDTHEADER_T	pBuffer;
ESSG_PULONG_T	pulCount;

hGrid	Handle of the original grid returned by EssGNewGrid().
hDAGrid	Handle of the new grid to receive drill-through report data.
usCells	Number of cell ranges in the pCells array.
pCells	Array of cell ranges selected to receive drill-through report data.

ESSG_PDTHINST_T	pDTInst;
ESSG_PSTR_T	pBuffer;
ESSG_PULONG_T	pulCount;

Hyperion Essbase Version 5.0.1 Patch 13 Release Notes

Contents

NT or Windows Files

OS/2 Files

UNIX Files

Before Installing SQL Interface on HP-UX

Installing SQL Interface on HP-UX from CD-ROM

Installing SQL Interface on HP-UX from Downloadable Files

Before Linking SQL Interface to Your INTERSOLV ODBC Driver

Linking SQL Interface to Your INTERSOLV ODBC Driver

After Linking SQL Interface to Your INTERSOLV ODBC Driver

Configuring Your Data Source and ODBC Driver

Revised Spreadsheet Documentation

EssBeginDataload

EssEndDataload

EssSetPath

EsbSetPath

EssGSetPath

ESS_DTBUFFER_T

EssDTGetHeader

EssDTGetData

EssDTClose

EssDTExit

EssGDTBeginDrillThrough

EssGDTEndDrillThrough

EssGDTGetData

EssGDTGetHeader

EssGDTGetReportData

EssGDTListReports

EssGDTReportCount

Hyperion Essbase Version 5.0.1
Patch 13 Release Notes