************************************************************
Patch file name: PATCH.HTM
Applies to: All platforms
Patch Date: 8/10/98
Identification: R5.0.1_P3
************************************************************
NOTE: For important information about client/server compatibility with 5.0.1 patches, see Patch Summary.
Downloading Patches from the Arbor Software Web Site
Installing Patches from the Arbor Software 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 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.
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 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 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.
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 OS2 server platforms, and 16-bit and 32-bit clients.
The final list of problems fixed in this patch is available on the Arbor Software Web site. For instructions on downloading files from this site, see Downloading Patches from the Arbor Software Web Site.
http://www.arborsoft.com/edu_supp/enterts.html
If you do not already have access to Arbor's Technical Support Web service, ask your your company's support contact to:
Be sure to have your company's specific support contact initiate communication with Arbor'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 Arbor Software Web site, use the following lists as your guide to which file(s) you need.
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 |
501P3OS.EXE | OS/2 Server |
501P3OI.EXE | OS/2 SQL Interface |
501P3OA.EXE | OS/2 API |
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 |
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
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.
501P3OS.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.
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.
SETUP.EXE
from the root directory of the CD-ROM.
OS2SETUP.CMD from
the root directory of the CD-ROM.
setup.sh from the
root directory of the CD-ROM.
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.
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 |
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.
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:
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:
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).
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 Arbor Software Web Site, complete the following steps:
501p2hi.tar file,
create a temporary local directory on the server or client
machine, as appropriate.
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.
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 (c) 1991-1998 by Arbor Software Corporation.
All Rights Reserved.