************************************************************
Patch file name: PATCH.HTM
Applies to: All platforms
Patch Date: 11/2/98
Identification: R5.0.1_P6
************************************************************
NOTES:
Downloading Patches from the Hyperion Solutions Web Site
Installing Patches from the Hyperion Solutions Web Site
Installing Patches from CD-ROM
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.
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 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 5 fixes problems on all server platforms, and 16-bit and 32-bit clients.
NOTES:
Patch 4 fixes problems on all server platforms, and 16-bit and 32-bit clients.
Patch 3 fixes problems on all server platforms, and 16-bit and 32-bit clients.
NOTES:
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.
Patch 2 fixes problems on all server platforms, and 16-bit and 32-bit clients.
NOTES:
Patch 1 fixes problems on NT or Windows and OS/2 server platforms, and 16-bit and 32-bit clients.
The following problems are fixed in Patch 6. For the latest list of problems fixed in this patch, connect to Hyperion's Technical Support Web site at:
http://support.hyperion.com/ts
Visual Basic Version of EssLoginSetPassword API Is Not Available (10040, P6)
The Visual Basic version of the EssLoginSetPassword API is not available. A new API,
EsbLoginSetPassword, has been added.
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:
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:
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:
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:
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 [Retrievals in Excel 97 on Particular Sheets Crashes the Server (10478, P2).tct]."
"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:
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 errorThis 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:
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:
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:
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:
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:
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.
http://support.hyperion.com/ts
If you do not already have access to Hyperion's Technical Support Web service, ask your your company's support contact to:
Germany 00 49 40 32005285
00 49 40 32005269
France 00 33 15 5940139
UK 00 44 1344 664007
Be sure to have your company's specific support contact initiate communication with Hyperion's Technical Support.
The "Problem Summary" section of the Release Notes contains the final list of problems fixed in the patch.
When downloading files from the Hyperion Web site, use the following lists as your guide to which file(s) you need.
501P6NS.EXE | NT (Intel) Server |
501P6DS.EXE | NT (Dec Alpha) Server |
501P695.EXE | Win95 Server |
501P6NI.EXE | Windows NT SQL Interface |
501P6DA.EXE | Dec Alpha API |
501P6NA.EXE | NT and 32-bit Windows API |
501P632.EXE | 32-bit Excel Client (Excel V7 and V8) |
501P6L32.exe | 32-bit Lotus 1-2-3 Client |
501P6ND.EXE | 32-bit SQL Drill-Through |
501P616.EXE | 16-bit Excel Client (Excel V5) |
501P6LO.EXE | 16-bit Lotus 1-2-3 Client (Lotus 1-2-3 V5) |
501P6WD.EXE | 16-bit SQL Drill-Through |
501P6AM.EXE | 16-bit Application Manager |
501P6WA.EXE | 16-bit Windows API |
501P6OS.EXE | OS/2 Server |
501P6OI.EXE | OS/2 SQL Interface |
501P6OA.EXE | OS/2 API |
501P6HS.TAR | HP-UX Server |
501P6HI.TAR | HP-UX SQL Interface |
501P6HA.TAR | HP-UX API |
501P6SS.TAR | Solaris Server |
501P6SI.TAR | Solaris SQL Interface |
501P6SA.TAR | Solaris API |
501P6AS.TAR | AIX Server |
501P6AI.TAR | AIX SQL Interface |
501P6AA.TAR | AIX API |
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
http://support.hyperion.com/ts
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.
The executable file decompresses into separate directories
(Disk1, Disk2, etc.) and runs SETUP.EXE from the
Disk1 directory, which launches the installation program.
.EXE file.
http://support.hyperion.com/ts
501P6OS.EXE -d
Each file automatically decompresses into separate directories (Disk1, Disk2, etc.).
SETUP.EXE from the Disk1 directory.
.EXE file.
On the AIX platform, the patch installation disables SQL Interface. SQL Interface must be reinstalled or reconfigured after installing the patch.
.tar file(s),
create a temporary local directory on the server or client
machine, as appropriate.
http://support.hyperion.com/ts
tar -xf filename.tar
from the temporary directory containing the .tar
file. This command extracts the files necessary to perform a
complete installation.
essinst to launch the installation program.
.tar file.
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.
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.
For Windows platforms:
SETUP.EXE from the Disk1 directory, which launches the installation program.
For OS/2 platforms:
501P6OS.EXE -d
Each file automatically decompresses into separate directories (Disk1, Disk2, etc.).
SETUP.EXE from the Disk1 directory.
For UNIX platforms:
tar -xf filename.tar
from the temporary directory containing the .tar
file. This command extracts the files necessary to perform a
complete installation.
essinst to launch the installation program.
For both patch installations, the online help file for Drill-Through, OLAPSQLD.HLP, is installed to the ESSBASE\BIN directory.
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 |
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.
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:
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:
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).
To install SQL Interface on HP-UX from CD-ROM, complete the following steps:
arbor.
cd\cdrom).
ls command to find setup.sh (or SETUP.SH).setup.sh is in uppercase or lowercase.
./setup.sh or ./SETUP.SH, depending on what you learned in step 4.
Ctrl-C.
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.
To install SQL Interface on HP-UX using downloadable files from the Hyperion Solutions Web Site, complete the following steps:
501p2hi.tar.
tar -xf 501p2hi.tar
from the temporary directory containing the file. This command extracts the files necessary to perform the installation.
essinst to launch the installation program.
.tar file is expanded, you can delete it.
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:
arbor.
$ORACLE_HOME/lib directory. For example, type:
su oracle
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:
oracle.
$ORACLE_HOME/rdbms/lib directory.
clntsh.mk file by adding -lsql to the end of each ld command.
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.
The following files are installed with the Essbase server on HP-UX:
libesssql.sl)
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:
$ARBORPATH\bin directory
$ARBORPATH\bin for access by the driver software
To run inst-sql.sh, enter the following command, still as user arbor:
inst-sql.shEssbase prompts you to supply information when necessary. When the script finishes, the command prompt appears. Enter:
exitUnder 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.
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:
odbc.csh in the .login or .cshrc file.
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.cshTo change the environment settings, edit
odbc.csh or odbc.sh.
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.
Certain spreadsheet documentation has been revised since the Hyperion Essbase Version 5.0.1 release. Patch 5 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.
New Essbase APIs
Patch 6 contains new APIs for three different areas:
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.
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
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() 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:
|
Return Value
Returns zero, if successful. Otherwise, returns an error code, as follows:
Notes
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);
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.
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
Notes
Example
ESS_STS_T
ESS_SetPath()
{
ESS_STS_T sts
ESS_STR_T pszPath = "C:\Essbase";
sts = EssSetPath (pszPath);
return sts;
}
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
Notes
Example
Sub ESB_SetPath Dim sts As Long Dim Path As String Path = "C:\Essbase" sts = EsbSetPath(Path) End Sub
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
Notes
Example
ESS_STS_T
ESSG_SetPath()
{
ESS_STS_T sts
ESSG_STR_T pszPath = "C:\Essbase";
sts = EssGSetPath (pszPath);
return sts;
}
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 Driil-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 |
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. |
Description
EssDTGetHeader() retrieves the report data header information for the given drill-through instance handle.
SyntaxESS_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. |
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).
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
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
In addition to seven new functions (EssGDTRequestDrillThrough(), 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 |
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. |
Description
EssGDTRequestDrillThrough() returns the drill-through instance handle for the given data cell range(s).
Syntax
ESSG_FUNC_M EssGDTRequestDrillThrough (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). |
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. |
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).
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. |
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. |
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. |
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). |
Copyright (c) 1991-1998 by Hyperion Solutions Corporation.
All Rights Reserved.