=================================================================== DB2 OLAP Server Analyzer V8.1 -- Refreshed Fix Pack 5 FOR THE IBM PRODUCT, THIS DOCUMENT SUPERSEDES AND OVERRIDES THE DOCUMENTATION PROVIDED BY HYPERION. IF YOU SEE ANY INFORMATION IN THE HYPERION DOCUMENTATION THAT CONTRADICTS THIS README FILE, IGNORE THE INFORMATION IN THE HYPERION DOCUMENTATION. July 2004 Service level: Hyperion Analyzer 7.0.1.0.1790 First created: 06/27/04 =================================================================== CONTENTS 1. Welcome to Fix Pack 5 2. Before you install 3. Installing the Fix Pack on Windows 4. Installing the Fix Pack on UNIX 5. Installing the Fix Pack on Linux 6. Known Issues =================================================================== 1. Welcome to Fix Pack 5 -------------------------- Fix Pack 5 offers the following enhancements: - Startup in Report Manager - Introduces Dependant Subscription Controls - Enhanced Relational Connections - Fix Pack 5 adds support for Linux AS v2.1 - AIX 5.1 and 5.2 are supported with Analyzer 8.1 FP 5 - Fix Pack 5 adds support for Java Plugin v1.4.2_03 - Fix Pack 5 supports WebSphere Application Server v5.0 and above Note: - WebSphere v3.5.5 is not supported with Fix Pack 5 - HP-UX 11.0 is not a supported platform. Please ignore references to HP-UX 11.0 in the documentation. - Support for Analyzer on the AIX 4.3.3 and Windows NT platform will not continue after Analyzer 8.1 FP5 - Support for WebSphere v4.0.5 for use with Analyzer will not continue after Analyzer 8.1 FP5 Fix Pack 5 is available from the IBM FTP site: www.ibm.com/software/data/db2/db2olap/fixpacks.html#81anz =================================================================== 2. Before you install ---------------------- - Fix Pack 5 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 Fix Pack 5. - WebSphere Application Server v4.0 users MUST install Fix Pack 5 (to bring WebSphere up to v4.0.5 level) prior to installing Analyzer's Fix Pack 4. If this is not done, Analyzer will not work. - To change the Analyzer RDBMS user password, please refer to the documentation called ClassesXML_Editor_Utility.pdf located at URL: ftp://service.software.ibm.com/ps/products/db2olap/fixes /analyzer/v81/fp5/ClassesXML_Editor_Utility.pdf Note: On AIX, there may be a need to edit the ClassFactoryConfig.sh file before using it. Edit the first line that states "$JAVA_HOME/bin/java.sh" to state "$JAVA_HOME/bin/java" instead. Save the file and then run ClassFactoryConfig.sh. - For customers who are installing Analyzer on a machine that already has WebSphere 5 installed, please create an 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 FP5 with Analyzer base code with WebSphere 5 and WebSphere 5 Express as well as with Analyzer FP3. - For more information on fixed issues and further known issues including the latest support information, please refer to Hyperion's Analyzer readme file called ha_701_readme.pdf located under root drive:\unzipped_image\docs\lang\Readme - For Java Plugin v1.4.2_03, compression needs to be turned on in order for the Analyzer JAR files to be cached as a smaller size than before (approximately 4MB versus 8MB). The default setting for compression is set to 0% (ie. none). Note: Though the documentation does state Java Plugin v1.4.2_03 and higher, this means within the v1.4.2 level. This information also pertains to Java Plugin v1.3.1_09 where the word higher means within the v1.3.1 level. Thus, versions like 1.4.0, 1.4.1, 1.5 and so forth are not supported. - For troubleshooting tips, please search our technotes database at the following URL: http://www.ibm.com/software/data/db2/db2olap/support.html - 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 Fix Pack 5 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 (Analyzer FP2 and below) 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 section 6 called "Known Issues". - If you install a new Fix Pack for DB2 UDB 7.2 or DB2 UDB 8.1 after Analyzer FP5 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 locations: C:\WAS_HOME\installedApps\...\Analyzer70.ear\Analyzer70.war \WEB-INF\lib (Windows) /usr/WAS_HOME/installedApps/.../Analyzer70.ear/Analyzer70.war /WEB-INF/lib (AIX) /opt/WAS_HOME/installedApps/.../Analyzer70.ear/Analyzer70.war /WEB-INF/lib (Solaris) /opt/WAS_HOME/installedApps/.../Analyzer70.ear/Analyzer70.war /WEB-INF/lib (Linux) where WAS_HOME is the installation path for WebSphere. - It is recommended that you uninstall Tomcat v4.0.4 before installing Tomcat v4.1.18 during the install of Analyzer FP5. - Downloading WebSphere Application Server 4.0.5 (Fix Pack 5): You can download WebSphere Application Server 4.0.5 (Fix Pack 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_5_SUN.tar 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 Fix Pack 5 to be successfully installed. =================================================================== 3. Installing the Fix Pack on Windows ------------------------------------ Prior to installing Analyzer 8.1 Fix Pack 5, it is imparative that the following 6 steps be done since Analyzer FP5 uses the same context root (Analyzer7_Server) and creates a new .ear file with the same name as in Analyzer 8.1 FP4 (Analyzer70.ear): To prepare for the installation: 1) Remove the adm subdirectory under C:\hyperion\analyzer (WIN) 2) Remove the ear subdirectory under C:\hyperion\analyzer (WIN) 3) Remove the existing Analyzer70.ear 4) Remove all contents in _hya_tmp directory except the setup.properties file 5) Remove the Analyzer70 directory under WAS_HOME\temp where WAS_HOME is the install path for WebSphere 6) Stop the Analyzer70 enterprise application in the Administrative Console (in WebSphere) and then uninstall Analyzer70 To install this Fix Pack: a) Download the analyzer81_fp5.zip file to a temporary directory on your Windows system. Make sure the path name of the directory does not include spaces. The Fix Pack installation program does not support directories whose names have spaces in them. Underscore characters are acceptable in directory names. b) Unzip the analyzer81_fp5.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 you are running DB2 UDB 7.2 and it's on a remote machine, copy the db2java.zip to the local machine where Analyzer FP5 is being installed. If you are running DB2 UDB 8.1 on the remote machine, copy both db2java.zip and db2jcc.jar to the local machine where Analyzer FP5 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 Fix Pack 5 with the existing Analyzer repository (eg. default, ANALYZ60, ANALYZ62 or ANALYZ65), please backup the database (called ANALYZ60, ANALYZ62 or ANALYZ65) in DB2 UDB (or other RDBMS') prior to installing Fix Pack 5. =================================================================== 4. Installing the Fix Pack on UNIX --------------------------------- Prior to installing Analyzer 8.1 Fix Pack 5, it is imparative that the following 3 steps be done since Analyzer FP5 uses the same context root (Analyzer7_Server) and creates a new .ear file with the same name as in Analyzer 8.1 FP4 (Analyzer70.ear). To prepare for the installation: 1) Remove the adm subdirectory under /usr/hyperion/analyzer (AIX) /opt/hyperion/analyzer (Solaris) 2) Remove the ear subdirectory under /usr/hyperion/analyzer (AIX) /opt/hyperion/analyzer (Solaris) 3) Remove the existing Analyzer70.ear 4) Remove all contents in _hya_tmp directory except the setup.properties file 5) Remove the Analyzer70 directory under WAS_HOME\temp where WAS_HOME is the install path for WebSphere 6) Stop the Analyzer70 enterprise application in the Administrative Console (in WebSphere) and then uninstall Analyzer70 To install the fix pack: a) Download the analyzer81_fp5_aix.tar (or analyzer81_fp5_sun.tar) file to a temporary directory on your UNIX system. Make sure the path name of the directory does not include spaces. The Fix Pack installation program does not support directories whose names have spaces in them. Underscore characters are acceptable in directory names. b) Untar the analyzer81_fp5_aix.tar (or analyzer81_fp5_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 you are running DB2 UDB 7.2 and it's on a remote machine, copy the db2java.zip to the local machine where Analyzer FP5 is being installed. If you are running DB2 UDB 8.1 on the remote machine, copy both db2java.zip and db2jcc.jar to the local machine where Analyzer FP5 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 Fix Pack 5 with the existing Analyzer repository (eg. default, ANALYZ60, ANALYZ62 or ANALYZ65), please backup the database (called ANALYZ60, ANALYZ62 or ANALYZ65) in DB2 UDB (or other RDBMS') prior to installing Fix Pack 5. =================================================================== 5. Installing the Fix Pack on Linux ----------------------------------- Prior to installing Analyzer 8.1 Fix Pack 5, it is imparative that the following step be done. 1) From an existing Analyzer install on a different platform, copy the file called Analyzer.properties and place it onto the Linux machine where Analyzer 8.1 FP5 will be installed. The file Analyzer.properties is located under the default path: c:\hyperion\analyzer\conf (Windows) /usr/hyperion/analyzer/conf (AIX) /opt/hyperion/analyzer/conf (Solaris) To install the fix pack: a) Download the analyzer81_fp5_linux.tar file to a temporary directory on your Linux system. Make sure the path name of the directory does not include spaces. The Fix Pack installation program does not support directories whose names have spaces in them. Underscore characters are acceptable in directory names. b) Untar the analyzer81_fp5_linux.tar file and then run AnalyzerSetup. c) When prompted, input the path location where the copied Analyzer.properties file resides. 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 you are running DB2 UDB 7.2 and it's on a remote machine, copy the db2java.zip to the local machine where Analyzer FP5 is being installed. If you are running DB2 UDB 8.1 on the remote machine, copy both db2java.zip and db2jcc.jar to the local machine where Analyzer FP5 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) Linux: /home/db2inst1/sqllib/java12 (DB2 UDB 7.2) /home/db2inst1/sqllib/java (DB2 UDB 8.1) where db2inst1 is the instance owner for DB2. =================================================================== 6. Known Issues: -------------------- - The link for API Toolkit Developer's Guide is broken when trying to access off the Analyzer index.html page. The workaround is to launch the API Toolkit Developer's Guide from Hyperion Analyzer Information Map link. 04-06-0019 (7567) - Print settings in header/footer section do not get saved when "Print selected object" option is chosen. Print settings do get saved in header/footer if the "Print Screen" option is chosen instead. (7587) - Defect 04-03-0128 (larger print size when opacity in traffic lighting is set to less than 100%) is listed as fixed in the Hyperion Readme file. However, this fix addresses only the "Print Selected Object" option where the print size will be smaller with opacity set to less than 100%. This fix does not address the issue when the "Print Screen" option is chosen instead. - Depending on the ports that EAS is using there is the possibility of a conflict between EAS and the Analyzer installer. If the Analyzer installer hangs while EAS is running on the same machine you will need to stop EAS and the Analyzer installer, then run the Analyzer installer again while EAS is stopped. It is strongly recommended that all OLAP related applications be stopped before installing other OLAP related products. Many of these products use common files and ports. Conflict are possible during installation if some of these products are running during the installation process. OLAP related products include but are not limited to: EAS - Essbase Administration Services EDS - Essbase Deployment Services EES - Essbase Enterprise Services EIS - Essbase Integration Services ESS - Essbase Spreadsheet Service DB2 OLAP Server (Essbase) Hyperion products Custom products that use the Hyperion APIs - Labels on charts may disappear. There is a known issue with the Netchart engine where if there is something laying over a chart area, it will show in Normal view but will occasionally disappear and then reappear. 01-05-0113 (7258) - Help section under Administration Tools is pointing to the Java Client Usage document instead of the Administrator's Guide. The Workaround to view the correct document is to click on Help > Information Map and choose the Administrator's Guide. 04-03-0167 (7375) - 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) 03-12-0081 - GRAPHIC/VARGRAPHIC datatype showing as CHAR/VARCHAR datatype instead with DB2 UDB 8.1 FP5. This may occur with other Fix Pack levels for DB2 UDB 8.1. (7412) - Using a "$" sign in user's password does not get processed and no error message appears. 04-03-0030 - With Web Publish > Report Group, when the "Select a Directory" panel appears, the "file name" field is looking for a chosen folder name (ie. choose a folder for example, c:\temp) and then all the reports that are in the report group will get saved into the chosen foder (in this case, temp). - 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\...\ Analyzer7_Server\wp_templates directory Filename.html needs to reside under APPSERVER_HOME\...\ Analyzer7_Server\wp_output directory - Memory problems for Websphere on Solaris environment. There are two workarounds. Select the workaround that matches your installation. First workaround: Install Hyperion Analyzer 7.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/Analyzer70.ear/ Analyzer70.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/Analyzer70.ear/ Analyzer70.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/Analyzer70.ear/Analyzer70.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 Fix Pack 9 (or DB2/UDB 8.1 Fix Pack 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 Fix Pack 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 Fix Pack 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 Fix Pack 9 is required, then you will also need to apply a special build on top of Fix Pack 9 to resolve the memory allocation errors. These fixes will be integrated in a future DB2/UDB 7.2 Fix Pack. For DB2/UDB 7.2 Fix Pack 9 on AIX, use special build 7711. For DB2/UDB 7.2 Fix Pack 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 Fix Pack 2 or Fix Pack 2+. Although the problem occurs at all levels of DB2 v8.1, the fix is only available at the Fix Pack 2 or 2+ level. Before applying the special build, confirm DB2 v8.1 is using one of the following two maintenance levels: Fix Pack 2 (s030508) Fix Pack 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. =================================================================== Licensed Material - Program Property of IBM (c) Copyright IBM Corp. 1998, 2004. 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-2004 Hyperion Solutions Corporation. All rights reserved. Hyperion is a registered trademark and Hyperion Solutions is a trademark of Hyperion Solutions Corporation. ===================================================================