=================================================================== DB2 OLAP Server Analyzer V8.1 -- Refreshed FixPak 3.1 November 2003 Service level: Hyperion Analyzer 6.5.1.0.00937 =================================================================== CONTENTS 1. Welcome to FixPak 3 2. Before you install 3. Installing the FixPak on Windows 4. Installing the FixPak on UNIX 5. Things to Note 6. Fixed Issues =================================================================== 1. Welcome to FixPak 3.1 -------------------------- FixPak 3 offers the following enhancements: - Enhanced functionality in Java Client, HTML Client, relational Administrative amongst other areas. - WebSphere v3.5.5 is not supported with FixPak 3.1. - AIX 5.1 is supported with Analyzer 8.1 FP3.1. Please also refer to the file called readme.pdf which is located under: C:\hyperion\analyzer\docs (WIN) /usr/hyperion/analyzer/docs (AIX) /opt/hyperion/analyzer/docs (Solaris) Note: Each language has its own folder. FixPak 3.1 is available from the IBM FTP site: ftp://service.software.ibm.com/ps/products/db2olap/fixes/ analyzer/v81/fp31/ Original file dated: 11/19/03 File updated: 11/25/03 =================================================================== 2. Before you install ---------------------- - FixPak 3.1 only supports the Refreshed edition of DB2 OLAP Server Analyzer Version 8.1. If you have not yet upgraded to the Refreshed edition, please do so before applying FixPak 3.1. - WebSphere Application Server v4.0 users MUST install FixPak 5 (to bring WebSphere up to v4.0.5 level) prior to installing Analyzer's FixPak 3.1. If this is not done, Analyzer will not work. - For customers who are installing Analyzer on a machine that already has WebSphere 5 installed, please create a empty file called admin.config and save it to the WAS_HOME\bin directory prior to installing Analyzer base code (v8.1 Refreshed). More information is available at: WAS5: ftp://service.software.ibm.com/ps/products/db2olap/fixes /analyzer/v81/fp3/anafp3_was5adv.pdf WAS 5 Express: ftp://service.software.ibm.com/ps/products/db2olap/fixes /analyzer/v81/fp3/anafp3_was5xprs.pdf Please note that the above documentation pertains to installing FP3.1 with Analyzer base code with WebSphere 5 and WebSphere 5 Express as well as with Analyzer FP3. - If there is a previous release of Hyperion Analyzer on the system, it is strongly recommended that you backup your current Analyzer repository prior to installing FixPak 3.1 as the database tables within the Hyperion Analyzer repository have been reorganized. During the installation, the tables are automatically migrated to the new structure. As a result of the table changes, previous releases of Hyperion Analyzer repository do not work with this release of Hyperion Analyzer. - There are known memory issues regarding Analyzer on the Solaris platform. Please refer to the section 5 called "Things to Note" below. - Should a new FixPak for DB2 UDB 7.2 or DB2 UDB 8.1 be installed after Analyzer FP3.1 is installed, ensure to synch up the JDBC drivers (for example, db2java.zip with DB2 7.2, and db2java.zip and db2jcc.jar with DB2 8.1). Copy and replace the existing files of the same name to the following location: C:\WAS_HOME\installedApps\...\Analyzer65.ear\Analyzer65.war \WEB-INF\lib (Windows) /usr/WAS_HOME/installedApps/.../Analyzer65.ear/Analyzer65.war /WEB-INF/lib (AIX) /opt/WAS_HOME/installedApps/.../Analyzer65.ear/Analyzer65.war /WEB-INF/lib (Solaris) where WAS_HOME is the installation path for WebSphere. - It is recommended to uninstall Tomcat v4.0.4 prior to installing Tomcat v4.1.18 during the install of Analyzer FP3.1. - Downloading WebSphere Application Server 4.0.5 (Fixpak 5) You can download WebSphere Application Server 4.0.5 (Fixpak 5) from the following FTP sites: For Windows: ftp://ftp.software.ibm.com/software/websphere/appserv/support /fixpacks/was40/fixpack5/Windows/ For Advance Edition, download: Filename: was40_ae_ptf_5.zip File size: 69.5 MB Date: 12/11/2002 12:00 AM For Advance Edition Single Server, download: Filename: was40_aes_ptf_5.zip File size: 67.0 MB Date: 12/11/2002 12:00 AM For AIX: ftp://ftp.software.ibm.com/software/websphere/appserv/support /fixpacks/was40/fixpack5/AIX/ For Advance Edition, download: Filename: was40_ae_ptf_5_AIX.tar File size: 75.5 MB Date: 12/11/2002 12:00AM For Advance Edition Single Server, download: Filename: was40_aes_ptf_5_AIX.tar File size: 72.9 MB Date: 12/11/2002 12:00AM For Sun: ftp://ftp.software.ibm.com/software/websphere/appserv/support/ fixpacks/was40/fixpack5/Sun/ For Advance Edition, download: Filename: was40_ae_ptf_5_SUN.tar File size: 90.6 MB Date: 12/11/2002 12:00AM For Advance Edition Single Server, download: Filename: was40_aes_ptf_3_SUN.tar 5 File size: 87.5 MB Date: 12/11/2002 12:00AM - The directory structure "C:\hyperion\analyzer" in Windows, "/usr/hyperion/analyzer" in AIX, and "opt/hyperion/analyzer in Solaris (by default from a previous installation of Analyzer) must be intact for Fixpak 3.1 to be successfully installed. - HP-UX 11.0 is not a supported platform. Please ignore references to HP-UX 11.0 in the documentation. =================================================================== 3. Installing the FixPak on Windows ------------------------------------ Prior to installing Analyzer 8.1 FixPak 3.1, it is imparative that these 3 steps be done first: 1) remove the ear subdirectory under C:\hyperion\analyzer (WIN) 2) remove (or rename) the existing Analyzer65.ear (since Analyzer 8.1 FixPak 3.1 install creates a new ear file with the same name) 3) stop the Analyzer65 enterprise application in the Administrative Console (in WebSphere) and then uninstall Analyzer65 (since the same enterprise application name will be used when the Analyzer65.ear from the FP3.1 install gets deployed into WAS) Proceed with the steps outlined below on installing this FixPak. This next section describes how to apply this FixPak: a) Download the analyzer81_fp31.zip file to a temporary directory on your Windows system. Make sure the path name of the directory does not include spaces. The FixPak installation program does not support directories whose names have spaces in them. Underscore characters are acceptable in directory names. b) Unzip the analyzer81_fp31.zip file to the same drive where Analyzer 8.1 Refresh is installed. Then run AnalyzerSetup.exe. c) Analyzer Windows Client and Analyzer Server are not separate downloads. On the installation panel called "Usage Mode", choose the appropriate radio button. To upgrade Analyzer Windows Client, choose the option called "Windows Client". To upgrade Analyzer Server, choose the option called "Enterprise Edition". d) Analyzer now requires that the location for the JDBC Driver Path (eg.db2java.zip for DB2 UDB v7.2 and db2java.zip for DB2 UDB v8.1) be supplied during installation (on panel "Configure RDBMS Repository"). If DB2 UDB is located on a remote machine, please copy the db2java.zip (for DB2 UDB 7.2) file and both db2java.zip and db2jcc.jar (for DB2 UDB v8.1) and put this (these) file(s) onto the local machine where Analyzer FP3.1 is being installed. By default, this file can be found at: Windows: C:\Program Files\SQLLIB\java (DB2 UDB 7.2) C:\Program FIles\IBM\SQLLIB\java (DB2 UDB 8.1) AIX: /home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /home/db2inst1/sqllib/java (DB2 UDB 8.1) Solaris: /export/home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /export/home/db2inst1/sqllib/java (DB2 UDB 8.1) where db2inst1 is the instance owner for DB2. e) If you install WebSphere Application Server 4.0 on a system that has DB2 Personal Edition installed on it, you might get an error message about not having proper version of DB2. The workaround is to click "Cancel" on the message dialog, and then "Resume Setup". The installation continues normally. f) To start the WebSphere Application Server 4.0 Service, the "Server" service must be present and started on the machine. The "Server" service can be installed by adding "File and Printer Sharing" from Network Connections in the Control Panel. You need the Windows CD to add "File and Printer Sharing" and then you need to reboot. WebSphere Application Server 4.0 requires the "Computer Browser" service to be started, which in turn is dependent on the "Server" and "Workstation" services. Note: If installing Fixpak 3.1 with the existing Analyzer repository (eg. default, ANALYZ60 or ANALYZ62), please backup the database (called ANALYZ60 or ANALYZ62) in DB2 UDB (or other RDBMS') prior to installing Fixpak 3.1. =================================================================== 4. Installing the FixPak on UNIX --------------------------------- Prior to installing Analyzer 8.1 FixPak 3.1, it is imparative that these 3 steps be done first: 1) remove the ear subdirectory under /usr/hyperion/analyzer (AIX) /opt/hyperion/analyzer (Solaris) 2) remove (or rename) the existing Analyzer65.ear (since Analyzer 8.1 FixPak 3.1 install creates a new ear file with the same name) 3) stop the Analyzer65 enterprise application in the Administrative Console (in WebSphere) and then uninstall Analyzer65 (since the same enterprise application name will be used when the Analyzer65.ear from the FP3.1 install gets deployed into WAS) Proceed with the steps outlined below on installing this FixPak. This next section describes how to apply this FixPak: a) Download the analyzer81_fp31_aix.tar (or analyzer81_fp31_sun.tar) file to a temporary directory on your UNIX system. Make sure the path name of the directory does not include spaces. The FixPak installation program does not support directories whose names have spaces in them. Underscore characters are acceptable in directory names. b) Untar the analyzer81_fp31_aix.tar (or analyzer81_fp31_sun.tar) file to the same machine where Analyzer 8.1 Refresh is installed. Then run AnalyzerSetup. c) Analyzer now requires that the location for the JDBC Driver Path (eg.db2java.zip for DB2 UDB v7.2 and db2java.zip for DB2 UDB v8.1) be supplied during installation (on panel "Configure RDBMS Repository"). If DB2 UDB is located on a remote machine, please copy the db2java.zip (for DB2 UDB 7.2) file and both db2java.zip and db2jcc.jar (for DB2 UDB v8.1) and put this (these) file(s) onto the local machine where Analyzer FP3.1 is being installed. By default, this file can be found at: Windows: C:\Program Files\SQLLIB\java (DB2 UDB 7.2) C:\Program FIles\IBM\SQLLIB\java (DB2 UDB 8.1) AIX: /home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /home/db2inst1/sqllib/java (DB2 UDB 8.1) Solaris: /export/home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /export/home/db2inst1/sqllib/java (DB2 UDB 8.1) where db2inst1 is the instance owner for DB2. Note: If installing Fixpak 3.1 with the existing Analyzer repository (eg. default, ANALYZ60 or ANALYZ62 or ANALYZ65), please backup the database (called ANALYZ60 or ANALYZ62 or ANALYZ65) in DB2 UDB (or other RDBMS') prior to installing Fixpak 3.1. =================================================================== 5. Things to Note: -------------------- - Web Publish functionality requests for HTML client Login information when double clicking on the filename.HTML should just open without a Login prompt. The workaround is to open the Analyzer report within the HTML client instead. (6910) - On Solaris 5.8, OLAP Server cubes that have these special characters (eg. ç ã á é í ó ú ü) are not rendering within Analyzer's Database Connection. However, reports and report groups can be named with these special characters. (6920) - On all languages except English, the Export to PDF function displays correct data in Adobe Acrobat but displays the data on alternate pages within PDF. (6921) - If a report is saved after inserting tokens within the header and/or footer area within the Print area, and the "Allow print settings to be saved with report" is checked, reopening the report and clicking on Print will bring up a blank Print panel. This issue does not occur when custom text is inserted into the header and/or footer area and the print settings are saved with the report. (6935) - Within the Report Properties panel, note that only filename.jsp (for the JSP Template field) and filename.html (for the Publish To field) are needed. Filename.jsp needs to reside under APPSERVER_HOME\...\ Analyzer6_Server\wp_templates directory Filename.html needs to reside under APPSERVER_HOME\...\ Analyzer6_Server\wp_output directory - Installations on Japanese Operating Systems Due to limitations in WebSphere 4.0.5 application server, the HTML Web Client and Analysis Server Console cannot transmit double-byte Kanji characters in WebSphere implementations. - Database for WebSphere Application Server 4.0.5 on AIX needs to be cataloged as a remote database even if it is not. Please refer to the IBM Redbook (http://ibm.com/redbooks) "IBM WebSphere V4.0 Advanced Edition Handbook for further details. - IBM DB2 8.1 Analyzer repositories: The specified JDBC driver directory must contain both the db2java.zip and the db2jcc.jar drivers. - Memory problems for Websphere on Solaris environment. There are two workarounds. Select the workaround that matches your installation. First workaround: Install Hyperion Analyzer 6.5.0 and deploy to WebSphere as described in Installation Guide. (This assumes that OLAP EDS has been installed). Then take these steps: 1. Copy the following files: ees_es_server.jar ees_japi.jar to this directory: /opt/WebSphere/AppServer/installedApps/Analyzer62.ear/ Analyzer62.war/WEB-INF/lib 2. Delete admees.jar from /opt/hyperion/analyzer/adm/lib 3. Edit the Analyzer.properties file in the following directory: /opt/WebSphere/AppServer/installedApps/Analyzer62.ear/ Analyzer62.war/WEB-INF/conf and set the following values: UseEssbasePassthru=true UseEDS=true EDSPort=5001 or whatever port EDS is using EDSServerName=hostname of EDS server 4. Modify the ADM.properties file in the following directory: /opt/WebSphere/AppServer/installedApps/Analyzer62.ear/Analyzer62.war /WEB-INF/classes and set the following values: ADM_USE_CORBA=0 5. Make sure there are no admserver processes running. The second workaround: A high level of exceptions causes the ADM server process to crash due to a buffer overrun in the Java Virtual Machine. To avoid this, start the ADM server process manually rather than allowing it to start automatically within the scope of the Web Application Server. 03-06-0333 To start the ADM server process manually: 1. Locate all adm.ior files on the Solaris server. These files are usually located in the web application server’s directory structure. 2. End the admserver process. 3. Delete all of the existing adm.ior files. Note: One adm.ior file is created in the next step. 4. Stop and re-start the Web Application Server, log on to Hyperion Analyzer and connect to Hyperion Essbase. This starts the ADM server process automatically. 5. Search for the adm.ior file. There should only be one copy of this file. You must now start the admserver process manually. 6. Stop the Web Application Server and end the admserver process. 7. Open the startup script for the Web Application Server and locate the JAVA_HOME environment variable. 8. Create a new .sh script in the directory where the adm.ior file from Step 5 resides with the following information (Be sure to edit the paths for JAVA_HOME and PATH to match your environment): JAVA_HOME=/opt/websphere/appserver/java export JAVA_HOME ADM_TRACE_LEVEL=4 export ADM_TRACE_LEVEL PATH=/opt/websphere/appserver/java/bin:$PATH export PATH java -version admserver -ORBStdProfileComponents 0 > adm.log 9. Start the ADM server process manually by executing this shell script prior to starting the Web Application Server. All ADM tracing is output to the file specified in the last line of the shell script (adm.log). - Analyzer sites using DB2/UDB 7.2 fixpak 9 (or DB2/UDB 8.1 fixpak 2)for Analyzer repository will receive the following errors on various client and admin functions: CLI0602E Memory allocation error on server. CLI0210E Memory allocation failure. DB2/UDB Fixpak 9 changes how memory was allocated by JDBC layer for CLOB objects, in some cases requesting too much memory. This problem is described in DB2/UDB APARs IY45529 and IY45585. We recommend that DB2/UDB fixpak 9 not be installed on the DB2 instance containing the Analyzer 8.1 repository, unless a critical DB2 fix is needed from that maintenance level. If DB2/UDB 7.2 fixpak 9 is required, then you will also need to apply a special build on top of fixpak 9 to resolve the memory allocation errors. These fixes will be integrated in a future DB2/UDB 7.2 fixpak. For DB2/UDB 7.2 fixpak 9 on AIX, use special build 7711. For DB2/UDB 7.2 fixpak 9 on Windows, use special build 7789. You may obtain a copy of the above special build files from the DB2 OLAP Server support page: http://www-3.ibm.com/software/data/db2/db2olap/support.html IBM DB2® OLAP Analyzer 8.1 sites that using DB2 UDB, Version 8.1 for the Analyzer repository may receive the following errors on various Analyzer client and Analyzer admin functions: This error occurs when the DB2 JDBC layer allocates too much memory for CLOB objects. This problem is described in DB2 UDB APAR IY47914. The following special fix builds are available to correct this problem. These special builds require DB2/UDB v8.1 fixpak 2 or fixpak 2+. Although the problem occurs at all levels of DB2 v8.1, the fix is only available at the fixpak 2 or 2+ level. Before applying the special build, confirm DB2 v8.1 is using one of the following two maintenance levels: Fixpak 2 (s030508) Fixpak 2+ (s030611) The following 6 special builds for DB2 UDB v8.1 are available to correct the memory error: hotfixpkg_8321.exe for DB2 v8.1 FP2 on Windows hotfixpkg_8324.exe for DB2 v8.1 FP2+ on Windows special_8322.tar.Z for DB2 v8.1 FP2 on AIX special_8325.tar.Z for DB2 v8.1 FP2+ on AIX special_8323.tar.Z for DB2 v8.1 FP2 on Solaris special_8326.tar.Z for DB2 v8.1 FP2+ on Solaris. These 6 special builds are available at the following FTP address: ftp://service.software.ibm.com/ps/products/db2olap/fixes/analyzer/v81 /db2v8fix Refer to the readme files in the above directory for additional installation instructions for the special builds. =================================================================== 6. Fixed Issues: -------------------- Improved memory consumption on the Analyzer server when using the HTML Web Client. When a DTS selection is a default selection in a combo box control, the name displays incorrectly and displays incorrect data. 01-06-0097 Analysis Tools (Traffic Lighting, Show/Hide, Calculations, Data Formatting and Sorting) definitions do not reference both, ID (Member Name) and Descriptions (Alias). 02-01-0096 Analyzer HTML Web Client does not allow change password on next login with Hyperion Essbase Authentication. 02-07-0057 When using the dynamic selection, Also select Siblings, on a relationally stored member (hybrid analysis) in the row axis, any dynamic selection made in the columns will not display the parent member. 02-08-0006 When the length of the member name or alias is long, the name is not fully visible within the retrieve top/bottom dialog. 02-10-0122 Hiding members with "show/hide" function only works for spreadsheets. It should work for charts as well. 02-11-0072 When a report is created with a larger screen resolution and viewed with a client with lower resolution, component that were statically placed on panels are no longer visible. 03-02-0020 With using Essbase Deployment Services (EDS), Link Reporting Object indicators no longer display. 03-02-0086 When applying Analysis Tool | Show/Hide on members derived from dynamic selections using Essbase substitutions variables, fail to be honor as the substitution variable changes. 03-02-0098 Retrieving a listing of Essbase Intergration Server (EIS) drill through reports and an EIS drill through report performs slowly. 03-04-0060 When a report or report group is deleted and is referenced with a user’s user preference | start up options, the reference to the report or report group is lost. 03-04-0110 When creating a SQL query within the SQL Grid object, the "GROUP BY" clause is not observed. 03-04-0178 Word Wrap on Columns does not work. 03-05-0010 When using the Java Web Client with Essbase Alias Tables, Link Report Objects will display with the default Alias, but not with other Aliases. 03-05-0144 When using the HTML Web Client, machines set with the Japanese regional settings are unable to display the multiple pie charts. 03-05-0179 A member and DTS of that same member do not display as available columns when creating an Analysis Tool | Show/Hide Only definition. 03-06-0029 Restrict Data on a member name derived from a dynamic selection using a substitution variable is referencing the member name and not the substitution variable name. 03-06-0037 Defining an Analysis Tool | Calculation with the SUM function causes the Java Web Client to not respond. 03-06-0151 Show Selected Member First right click setting is not saved with report. 03-06-0260 When trying to use an Alias Controller to control multiple data sources, the change only occurs in the first data source. 03-06-0270 In Design Mode when selecting multiple combo boxes and attempting to change the borders, only applies to the first combo box selected. 03-06-0294 Related Content Indicators used with Hyperion Financial Management database connections disappear after accessing the list of related content. 03-06-0301 Search fails when any member name or alias contains a backslash. 03-07-0002, 03-09-0009 Password changes not being updated to Essbase. 03-07-0011, 03-09-0075 Calculations - Divide by 0 error #div/0! isn't carried through multi step calculations and in some cases creates inaccurate results. 03-07-0058 Combo Boxes that use the "less than" character (<) in Analyzer 5.x cause the report group to error out during migration. 03-07-0070 Auto-Migration from 6.2.1 to 6.5 does not keep the column size. 03-07-0091 Analyzer API command GetPropertyValueString seems to be very slow. 03-07-0134 When connecting to a Hyperion Financial Management data source connection, traffic Lighting is not saved properly. 03-07-0139 When using Essbase Deployment Services (EDS), change password and expired password does not work for Essbase authenticated users. 03-08-0015 Importing 6.2.1 reports and report groups into 6.5 performs slowly. 03-08-0088 Freeze headers is not working on a SQL Grid spreadsheet. 03-08-0104 If selection button object contains a '>' symbol in its name, the name will not display the next time the report is opened. 03-08-0136 Multi Level combo box selections get reset after making selections. 03-08-0210 When applying an Analysis Tools | Calculation and Show/Hide only displaying calculated members on a nested dimension, users are unable to drill on a member in the outer most dimension. 03-08-0236 When multiplying a missing or n/a value by a constant of 1, the result is '1". 03-08-0237 When using the Analyzer Console, users are unable to login with double byte character (dbcs) names. 03-09-0051 When using the HTML Web Client, garbled characters appear in the Print Preview window 03-09-0053 Pinboards with 3+ levels reload (save) incorrectly. 03-09-0055 Setting border to none on a spreadsheet object does not get applied upon save. 03-09-0056 On reports migrated from 6.2, the Filter Panel does not update when subscription selections are changed. 03-09-0138 Drill shortcuts do not work on columns. 03-09-0147 Export in Analyzer 6.5 Administration Tool fails to create the mapping of roles to user groups. 03-09-0152 Combo box controls containing selections with spaces before the member name no longer function after upgrading to 6.5. 03-09-0210 When migrating a report from 6.2 to 6.5, tabs containing descriptions (alias) displays as id (member name). 03-09-0213. Improved applet load time. 03-10-0012 =================================================================== Licensed Material - Program Property of IBM (c) Copyright IBM Corp. 1998, 2003. All Right Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. IBM, DB2, and DB2 OLAP Server are trademarks of International Business Machines Corporation in the United States, other countries, or both. Portions (c) 1991-2003 Hyperion Solutions Corporation. All rights reserved. Hyperion is a registered trademark and Hyperion Solutions is a trademark of Hyperion Solutions Corporation. Portions (c) Blue Sky Corporation. All rights reserved. ===================================================================