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

# Arbor Essbase Version 5.0.1
Patch 3 Release Notes

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

Patch file name: PATCH.HTM

Applies to: All platforms

Patch Date: 8/10/98

Identification: R5.0.1_P3

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

## Contents

NOTE: For important information about client/server compatibility with 5.0.1 patches, see Patch Summary.

Patch Installation Overview

Key

Patch Summary

Problem Summary

Downloading Patches from the Arbor Software Web Site

Files to Download

Installing Patches from the Arbor Software Web Site

Installing Patches from CD-ROM

Copyright Information

## 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 Arbor Software 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 Arbor Software Web Site or Installing Patches from CD-ROM.

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

## Key

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_P3

  Patch 3 fixes problems on all server platforms, and 16-bit and 32-bit clients.

  NOTES:

  - If you install a Patch 2 or Patch 3 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 Patch 3 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 Arbor Integration Server Drill-Through code in Patch 2.

    You may use a pre-Patch 2 Spreadsheet Add-in with a Patch 2 or Patch 3 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," will allow spreadsheet users to define a style for data cells that have Integration Server Drill-Through reports attached to them. Caution: This option is not yet functional. Checking this option will result in a server crash. This will be corrected and functional in Patch 4.

- 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 Arbor 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:

    - Arbor Integration Server Drill-Through
    - ODBC Driver Support for SQL Interface on UNIX
    - HP-UX SQL Interface Installation Instructions
    - Revised Spreadsheet Documentation

- Patch R5.0.1_P1

  Patch 1 fixes problems on NT or Windows and OS2 server platforms, and 16-bit and 32-bit clients.

## Problem Summary

The following problems are fixed in Patch 3. For the latest list of problems fixed in this patch, connect to the Arbor Software Web site's "Enter Technical Support Section": `http://www.arborsoft.com/edu_supp/enterts.html`.

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:

1. PHSS_12694 UCOMP/LIBMP
2. PHSS_14920 HP DCE/9000 1.5 cumulative patch
3. PHSS_15043 10.x HP aC++ runtime library components
4. PHSS_15549 LIBCL
5. 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, P2)
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.

On UNIX Platforms, Aliases are Reported in Reverse Order Compared with Windows NT (10743, P3)
On UNIX platforms, aliases are reported in reverse order compared with Windows NT.

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:

1. PHSS_12694 UCOMP/LIBMP
2. PHSS_14920 HP DCE/9000 1.5 cumulative patch
3. PHSS_15043 10.x HP aC++ runtime library components
4. PHSS_15549 LIBCL
5. 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)
A 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 Arbor'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, P10)
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 Arbor Software Web Site

1. Using a Web browser such as Netscape Navigator or Microsoft Internet Explorer, connect to:

   `http://www.arborsoft.com/edu_supp/enterts.html`

2. Enter your Site ID, Server ID, and name; then click "Enter Technical Support" to access the Technical Support Web service.

   If you do not already have access to Arbor's Technical Support Web service, ask your your company's support contact to:

   - call the support hotline at (408)744-1200, or
   - send e-mail to `TSadmin@arborsoft.com`

   Be sure to have your company's specific support contact initiate communication with Arbor's Technical Support.

3. Click "Patch Central."

4. 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 3 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 Arbor Software Web site, use the following lists as your guide to which file(s) you need.

### NT or Windows Files

`501P3NS.EXE` | NT (Intel) Server
`501P3DS.EXE` | NT (Dec Alpha) Server
`501P395.EXE` | Win95 Server
`501P3NI.EXE` | Windows NT SQL Interface
`501P3DA.EXE` | Dec Alpha API
`501P3NA.EXE` | NT and 32-bit Windows API
`501P332.EXE` | 32-bit Excel Client (Excel V7 and V8)
`501P3ND.EXE` | 32-bit SQL Drill-Through
`501P316.EXE` | 16-bit Excel Client (Excel V5)
`501P3LO.EXE` | 16-bit Lotus 1-2-3 Client (Lotus 1-2-3 V5)
`501P3WD.EXE` | 16-bit SQL Drill-Through
`501P3AM.EXE` | 16-bit Application Manager
`501P3WA.EXE` | 16-bit Windows API

### OS/2 Files

`501P3OS.EXE` | OS/2 Server
`501P3OI.EXE` | OS/2 SQL Interface
`501P3OA.EXE` | OS/2 API

### UNIX Files

`501P3HS.TAR` | HP-UX Server
`501P3HI.TAR` | HP-UX SQL Interface (new in Patch 2)
`501P3HA.TAR` | HP-UX API
`501P3SS.TAR` | Solaris Server
`501P3SI.TAR` | Solaris SQL Interface
`501P3SA.TAR` | Solaris API
`501P3AS.TAR` | AIX Server
`501P3AI.TAR` | AIX SQL Interface
`501P3AA.TAR` | AIX API

## Installing Patches from the Arbor Software 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

1. Make sure Essbase is not running when you perform the patch installation procedure.

2. Before downloading the appropriate executable file(s), create a temporary local directory on the server or client machine, as appropriate.

3. Connect to the Arbor Software Web site's "Enter Technical Support Section" ( `http://www.arborsoft.com/edu_supp/enterts.html`) and download the appropriate file(s) to the temporary directory you created.

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

5. Follow the on-screen instructions to perform a full Essbase installation.

6. After the files are expanded, you can delete the `.EXE` file.

### OS/2 Servers and Clients

1. Make sure Essbase is not running when you perform the patch installation procedure.

2. Before downloading the appropriate compressed file(s), create a temporary local directory on the server or client machine, as appropriate.

3. Connect to the Arbor Software Web site's "Enter Technical Support Section" ( `http://www.arborsoft.com/edu_supp/enterts.html`) and download the appropriate file(s) to the temporary directory you created.

4. Expand the compressed file by typing the file name followed by "`-d`" from a command prompt. For example:

   `501P3OS.EXE -d`

   Each file automatically decompresses into separate directories (Disk1, Disk2, etc.).

5. Run `SETUP.EXE` from the Disk1 directory.

6. Follow the on-screen instructions to perform a full Essbase installation.

7. After the files are expanded, you can delete the `.EXE` file.

### UNIX Servers and Clients

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

1. Make sure Essbase is not running when you perform the patch installation procedure.

2. Before downloading the appropriate `.tar` file(s), create a temporary local directory on the server or client machine, as appropriate.

3. Connect to the Arbor Software Web site's "Enter Technical Support Section" ( `http://www.arborsoft.com/edu_supp/enterts.html`) and download the appropriate file(s) to the temporary directory you created.

4. To untar the files, 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.

5. Run `essinst` to launch the installation program.

6. Follow the on-screen instructions to perform a full Essbase installation.

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

## Installing Patches from CD-ROM

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.

On the AIX platform, 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.

1. Make sure Essbase is not running when you perform the patch installation procedure.

2. Insert the CD-ROM into your CD-ROM drive.

3. Do one of the following:

   - For NT and Windows platforms, run `SETUP.EXE` from the root directory of the CD-ROM.
   - For OS/2 platforms, run `OS2SETUP.CMD` from the root directory of the CD-ROM.
   - For UNIX platforms, run `setup.sh` from the root directory of the CD-ROM.

4. Follow the on-screen instructions to perform a full Essbase installation.

## Arbor Integration Server Drill-Through

Patch 2 provides code and online help for the Arbor Integration Server Drill-Through feature. Be sure to install both the Patch 2 Server and the Patch 2, 32-bit Spreadsheet Add-in. If you use a Patch 2 Spreadsheet Add-in with a pre-Patch 2 server, spreadsheet retrievals will fail.

The online help file for Drill-Through, `OLAPSQLD.HLP`, is installed during the patch installation process to the `ESSBASE\BIN` directory.

## ODBC Driver Support for SQL Interface on UNIX

Arbor Software supports the ODBC interface.

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

Arbor Software 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 Arbor 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 Arbor Software Web site's "Enter Technical Support Section" ( `http://www.arborsoft.com/edu_supp/enterts.html`).

XY =
Two INTERSOLV Version 3.02 ODBC drivers for Informix on Solaris have been tested with Arbor 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 Arbor Software Web site's "Enter Technical Support Section" (`http://www.arborsoft.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 Arbor Essbase Version 5.0.1 Patch 2 SQL Interface.

## HP-UX SQL Interface Installation Instructions

Arbor Essbase Version 5.0.1 Patch 2 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 Arbor 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 Arbor Essbase 5.0.1 Patch 2 server on HP-UX before you install Arbor Essbase SQL Interface on HP-UX. Follow these steps:

1. Install the Arbor Essbase Version 5.0.1 Patch 2 server.
2. Update your environment settings.
3. 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 Arbor 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:

1. Log in to the server as `arbor`.
2. Insert the CD-ROM into your CD-ROM drive.
3. Change to the top directory of the CD-ROM (for example, `cd\cdrom`).
4. 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.
5. Enter `./setup.sh` or `./SETUP.SH`, depending on what you learned in step 4.
6. When prompted for which product to install, select SQL Interface.
7. Follow the prompts and provide the information requested.
   To cancel installation at any time, press `Ctrl-C`.
8. 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.
9. 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 Arbor Software Web Site, complete the following steps:

1. Make sure Essbase is not running when you perform the patch installation procedure.
2. Before downloading the `501p2hi.tar` file, create a temporary local directory on the server or client machine, as appropriate.
3. Connect to the Arbor Software Web site's "Enter Technical Support Section" ( `http://www.arborsoft.com/edu_supp/enterts.html`) and download the appropriate file to the temporary directory you created.
4. 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.

5. Run `essinst` to launch the installation program.
6. Follow the on-screen instructions to install SQL Interface.
7. 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:

1. Log in as user `arbor`.
2. Make sure you have Write access to the `$ORACLE_HOME/lib` directory. For example, type:

       su oracle

3. 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:

1. Log in as user `oracle`.
2. Change to the `$ORACLE_HOME/rdbms/lib` directory.
3. Modify the `clntsh.mk` file by adding `-lsql` to the end of each `ld` command.
4. 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

The following online help files have been modified since the Arbor Essbase Version 5.0.1 release:

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

## Copyright Information

Copyright (c) 1991-1998 by Arbor Software Corporation.

All Rights Reserved.