IBM(R) DB2(R) Data Archive Expert, Version 2 Release 1, Fix Pack 1 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 CORRECTED KNOWN PROBLEMS 1.2 ENHANCEMENTS 2.0 PREREQUISITES 2.1 Hardware requirements 2.2 Software requirements 3.0 INSTALLATION INSTRUCTIONS 4.0 CUSTOMIZATION INSTRUCTIONS 5.0 CORRECTIONS TO DOCUMENTATION 6.0 HOW TO GET HELP 7.0 KNOWN PROBLEMS, RESTRICTIONS, AND WORKAROUNDS 8.0 NOTICES 8.1 Use of Evaluation Program 8.2 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Data Archive Expert, Version 2 Release 1, Fix Pack 1 README file. This README file contains information about installing IBM DB2 Data Archive Expert. IBM DB2 Data Archive Expert has been tested and validated with DB2 Universal Database(TM) Version 8 Fix Pack 9. Subsequent releases might require additional maintenance. 1.1 CORRECTED KNOWN PROBLEMS The following problems are corrected by this fix pack: - APAR: PK18787: The sample content button is not working properly in the create specification stage. - You can specify table space information for a retrieve target table when creating a remote archive retrieve specification. - Added support for junction tables in remote archives. - Added support for tables with the cascade delete option in remote archives. - You can complete an archive run for a remote archive specification in the "Partially Completed" state. - Fixed file archive and file retrieve problem caused by LOB objects with multiple tables in the archive unit. - Added delete confirmation message when deleting a run data version. - Improved performance. - Corrected the schema names for remote archive packages. When you configure a database with the DB2 Data Archive Expert database server GA driver, the configuration creates a remote archive package with a schema name that does not contain the product prefix AHX. With this fix pack, the problem is corrected. If you already have a database configured with the GA driver, you must complete the following steps: On Windows systems: 1. For each database, drop the package "HALLER.DAEXLOAD" and the schema "HALLER" by issuing the DB2 commands "drop package" and "drop schema". 2. Install the DB2 Data Archive Expert database server fix pack 1 driver. 3. Connect to the database and issue the "DB2 BIND daexload.bnd" command from the server install directory. On AIX system: 1. For each database, drop the package "SHUWANG8.DAEXLOAD" and the schema "SHUWANG8" by issuing the DB2 commands "drop package" and "drop schema". 2. Install the DB2 Data Archive Expert database server fix pack 1 driver. 3. Connect to the database and issue the "DB2 BIND DAEXLOAD.bnd" command from the server install directory. On other UNIX systems: 1. For each database, drop the package "DREHER8.DAEXLOAD" and the schema "DREHER8" by issuing the DB2 commands "drop package" and "drop schema". 2. Install the DB2 Data Archive Expert database server fix pack 1 driver. 3. Connect to the database and issue the "DB2 BIND DAEXLOAD.bnd" command from the server install directory. - Fixed DB2 Data Archive Expert database server uninstall problems: - The server directory does not get deleted. - The symbolic links to DB2 Data Archive Expert files are removed from the database instances. On UNIX systems, if you run the ahxLinks.sh command with the DB2 Data Archive Expert database server GA driver for DB2 instance, you need to put DB2 instance name into the "temp1file" file that exists on the server installation directory. The uninstallation process for the DB2 Data Archive Expert database server in fix pack 1 will remove the DB2 Data Archive Expert symbolic links for the DB2 instances that appear in the "temp1file" file. If the "temp1file" file does not exist under the server directory, then create one and add the DB2 instance name that you already ran with ahxLinks.sh to configure DB2 Data Archive Expert. If you have already run the ahxLinks.sh from fix pack 1 for all of the database instances, then no action is required. 1.2 ENHANCEMENTS - The Node Directory Tool: Purpose: The DB2 Data Archive Expert User Interface requires you to enter database location information used to connect to the DB2 databases. If you have already cataloged databases on client systems you can use this tool to extract some of the connection information from the DB2 Node directory on those client systems and import it into DB2 Data Archive Expert. The node directory tool runs as a standalone application. To get the node directory tool, install the DB2 Data Archive Expert Integrated Console Solution Component Fix Pack 1. The tool will import the database information into either the existing database location file for each ISC user or create a new location file for users. For Windows systems as DB2 client system: 1. Unzip the NodeDirextractTool.zip file (exists on the client install directory). 2. Import the existing database location file, copy _locs from the \ISC\AppServer\properties\com\ibm\ahx directory to the directory where you will run this application. 3. Issue the command: "ndextract.bat ". 4. Copy the location file back to the ISC directory \ISC\AppServer\properties\com\ibm\ahx. 5. From the ISC interface, edit the imported database locations by giving them each a more meaningful name and filling in the rest of the required fields. For UNIX system as DB2 client system: 1. Extract the files from NodeDirExtractTool.tar (exists on the client install directory). 2. Import the existing database location file, copy _locs from the /ISC/AppServer/properties/com/ibm/ahx directory to the directory where you will run this application. 3. Issue the command: "./ndextract.sh ". 4. Copy the location file back to the ISC directory /ISC/AppServer/properties/com/ibm/ahx. 5. From the ISC interface, edit the imported database locations by giving them each a more meaningful name and filling in the rest of the required fields. Note: If the bkp__locs file exists, delete the file before running the command. Troubleshooting for the Node Directory application: There are native libraries used by the node directory tool that only run with a 32 bit Java JRE. The node directory tool can be run on systems with 64 bit processors, but a 32 bit JRE is required. You must also edit the script file ndextract.sh to point to the 32 bit DB2 library. If you receive a "Command not found Error," Java is not specified in your path. You can either update the path or pass the Java path as the second argument in the ndextract script. Example: If Java is installed in the directory /usr/java13_32, you can run the node directory tool with the following command: ./ndextract.sh /usr/java13_32/jre/bin/ (Important: the last forward slash must be included). 2.0 PREREQUISITES DB2 Data Archive Expert has hardware and software requirements. 2.1 Hardware requirements DB2 Data Archive Expert has the following hardware requirements: -Memory and disk space sufficient to fulfill DB2 minimum requirements. -Approximately 25 MB of free disk space on any supported platform. -Additional space for user data (varies depending on the size of your databases and the amount of activity your system encounters). The DB2 Data Archive Expert ISC installation process requires 1.2GB of temporary disk space. 2.2 Software requirements DB2 Data Archive Expert requires: JVM (JRE) 1.3.1 or higher for all source or target servers DB2 UDB V 8.0 on Linux, UNIX, and Windows with fix pack 9 or higher for sources and targets of remote archives. DB2 V 8.0 Fix Pack 9 is required for archiving to local tables. Remote archiving is not supported for Linux, UNIX, and Windows Unicode databases. -IBM JDBC driver: If you want to use DB2 Data Archive Expert with z/OS as a database server, you must install the DB2 UDB Administration Client. The DB2 UDB Administration Client is a stand alone UDB installation package that contains the JDBC drivers, the Configuration Assistant, and other DB2 UDB for Multiplatforms components. The DB2 Data Archive Expert Integrated Solutions Console (ISC) component has been tested on the following: AIX 5.2 64 bit Windows 2000 32 bit Linux for xSeries 32 bit Solaris 8 32 bit The DB2 Data Archive Expert database server has been tested on the following: AIX 5.1, 5.2, 5.3 64 bit Windows 2000, XP, 2003 32 bit Solaris 8 and 9 Linux RHEL 3 for xSeries 32 bit Linux RHEL 3 for pSeries and zSeries 64 bit Linux SuSE 8 for xSeries 32 bit Linux SuSE 8 for pSeries and zSeries 64 bit 3.0 INSTALLATION INSTRUCTIONS The installation program will detect whether the DB2 Data Archive Expert v2.1 is installed. Because this fix pack requires that DB2 Data Archive Expert v2.1 is installed, a message will be issued and the install program will exit if it is not detected. If DB2 Data Archive Expert v2.1 is found, Fix Pack 1 is installed in the directory that contains your current DB2 Data Archive Expert files. This is true for both the DB2 Data Archive Expert client and server installation programs on all platforms with the exception of the client behavior on Solaris systems. To install DB2 Data Archive Expert fix pack 1, complete the following tasks: 1. Start the DB2 Data Archive Expert ISC component installation program by running the following platform-specific setup files: AIX: setupDAEClientAix Windows 32 bit: setupDAEClientWin32.exe Linux for xSeries 32-bit: setupDAEClientLinux Solaris: setupDAEClientSolaris For Solaris systems: - When you install Fix Pack 1 through GUI mode, after the Welcome panel, a dialog is shown to remind you to install the Fix Pack 1 to the same location where you installed DB2 Data Archive Expert v2.1. Select "Yes" to continue if you remember where you installed DB2 Data Archive Expert v2.1. Select "No" to exit the installation program and check where you originally installed DB2 Data Archive Expert v2.1. Once you find the directory information, return to install Fix Pack 1. If you use the console mode, it is assumed that you know the directory where you originally installed DB2 Data Archive Expert v2.1. - Fix Pack 1 will create a separate uninstallation program under the install directory. If you want to uninstall DB2 Data Archive Expert, you should uninstall Fix Pack 1 first (for example, under the daeiscuninst2 directory), then uninstall DB2 Data Archive Expert v2.1 (for example, under the daeiscuninst directory). Note: When you attempt to uninstall DB2 Data Archive Expert v2.1, you might get a return code of 200. The uninstallation program is trying to remove the DB2 Data Archive Expert client from the ISC. You can ignore this complaint because that DB2 Data Archive Expert client was already removed when you uninstalled Fix Pack 1. 2. Start the DB2 Data Archive Expert database server installation program by running the following platform-specific setup files: Note: You must ensure that a JRE is defined in your PATH before running the installation program for the DB2 Data Archive Expert database server. Before you run the set up file, ensure that you have a valid DB2 environment where you can run the "db2level" command. AIX: setupDAEServerAix Windows 32 bit: setupDAEServerWin32.exe Solaris: setupDAEServerSolaris Linux for pSeries 64 bit: setupDAEServerPlnx Linux for zSeries 64 bit: setupDAEServerZlnx Linux for xSeries 32 bit: setupDAEServerXlnx 3. Check for Service updates. See section 6.0. Be sure to check the support website for any fix packs that may be required. 4. Configure DB2 Data Archive Expert. See Section 4.0 Note: If you are using an AIX 5.3 system and receive a java core dump error when you attempt to install or uninstall DB2 Data Archive Expert, you might have a problem with the native library libaixppk.so, which is used by the AIX platform. For a resolution to this problem, see the InstallShield documentation at http://support.installshield.com/kb/view.asp?articleid=Q111262. 4.0 CUSTOMIZATION INSTRUCTIONS For complete instructions on how to customize and use DB2 Data Archive Expert, refer to the DB2 Data Archive Expert for z/OS and Multiplatforms User's Guide. If you received your copy of DB2 Data Archive Expert electronically, locate the User's Guide here: http://www.ibm.com/software/data/db2imstools/library.html If you are installing this image from a CD-ROM, the documentation is located in /doc directory. The User's Guide on the Web can contain updates to the publication on CD-ROM. 5.0 CORRECTIONS TO DOCUMENTATION The following sections describe corrections to documentation after the book was published. 6.0 HOW TO GET HELP For a complete and up-to-date source of DB2 Data Archive Expert information, including information on issues discovered after this README was published, go to the following Web site: DB2 Data Archive Expert Online Support: http://www.ibm.com/software/data/db2imstools/support.html If you are not able to find your answer searching the listed URL, call 1-800-IBM-SERV to speak to an IBM representative for assistance. 7.0 KNOWN PROBLEMS, RESTRICTIONS, AND WORKAROUNDS At the time the product went to distribution, the following problems, restrictions and workarounds surfaced during the final phases of product packaging and test. The items are listed below. See the restrictions section of the DB2 Data Archive Expert User's Guide for more information about product restrictions. 1. For AIX 64-bit systems, the DB2 Data Archive Expert uninstallation program will display the following message: An unhandled error occurred -- specify system property "is.debug" for more information. This is an InstallShield problem. There is no impact on the successful uninstall of DB2 Data Archive Expert. 2. After running the uninstallation program, if you intend to re-run the installation program, you must drop the DB2 Data Archive Expert database objects that were created during the installation. Once this is completed, the installation program can be run again. 3. Remote archive DAEXLOAD failure: If you are having trouble remote archiving to zLinux source or targets, and are receiving a -6555 SQL code message, run the following command: db2set DB2ATLD_PORTS=6000:6127 This will increase the number of ports that are available to the LOAD utility, and might fix the problem. 4. If you receive the following error message and SQL codes when you are configuring a remote archive, your FEDERATED parameter might not be set correctly. Error message: AHXM030 SQLCode: -20076 SQLState: 0A502 SQLMessage: DB2 SQL error: SQLCODE: -20076, SQLSTATE: 0A502, SQLERRMC: 1 For a Federated server, set the DBM variable to YES and restart the database manager. Connect to your source and target databases and issue the DB2 command "DB2 CREATE WRAPPER DRDA." 5. If you receive the following error message and SQL codes when you are configuring a remote archive, the DRDA wrapper might not exist. Error message: AHXM030 SQLCode: -204 SQLState: 42704 SQLMessage: DB2 SQL error: SQLCODE: -204, SQLSTATE: 42704, SQLERRMC: DRDA Check your source and target databases to ensure that the DRDA wrapper was created. If it was not created, connect to the database and issue the DB2 command "DB2 CREATE WRAPPER DRDA." 6. If you receive the following error message, you might have a license issue. Error message: AHXM031 Exception has been thrown: LUM KEY CHECK FAILED Ensure that the schema in the stored procedure is correct. Check that the stored procedure AHXLICENSECHECK exists. On UNIX systems, check that symbolic links for the ahxv210.jar file exist for the DB2 instance in the SQLLIB/function directory. Ensure that the Path to the license key field has the correct directory name. 7. For the ISC interface, a retrieve specification cannot be created for a file archive specification that has a specified junction table. 8. From the ISC interface, if you run a specification that has a junction table in the archive unit, DB2 Data Archive Expert might create empty schema. DB2 Data Archive Expert uses the "DB2 authorization ID" value as the schema name to create a view. During configuration of the database, this value is set to blank. To prevent this problem, before you run your specification select the database location from the "Control database locations" page, click "User settings," and enter and save the correct user settings. For remote archives, the "DB2 authorization ID" value must be saved on both the source and target database locations. 9. For the ISC interface, Some ISC pages do not automatically refresh. For example, the "Working with specifications" page does not refresh automatically when you set up your remote target information. 10. For the ISC interface, the sample content text editor sometimes converts the < and > characters to corresponding hypertext substitution strings. 11. For the ISC interface, when you select unique columns for a table on the "Select columns" page, the behavior of the Apply button is inconsistent. Behavior: If you select a DB2-enforced index from the box, clicking the Apply button will check mark the columns that make up that index. If you select the NON DB2 ENFORCED choice, the behavior is different. If you make changes to the columns that are selected and click the Apply button, the selected columns may change. To specify columns for a NON DB2 ENFORCED index, you must do the following: 1. Select NON DB2 ENFORCED. 2. Click the Apply button. 3. Update the columns that you want for the index by selecting or deselecting the corresponding check boxes for those columns. 4. Do NOT click Apply. Click Next instead. 5. When you return to the Unique columns page, ensure that the correct columns are shown for each table in your archive unit. 12. For file and second-level archives on Multiplatforms, if you add columns that are not nullable to tables in your archive unit, you will be able to retrieve only the archive data versions that have all of the additional columns. 8.0 NOTICES This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10594-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: IBM World Trade Asia Corporation Licensing 2-31 Roppongi 3-chome, Minato-ku Tokyo 106, Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this publication to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. Licensees of this program who want to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this information and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement, or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. 8.1 Use of Evaluation Program If you are using an evaluation copy of the program, the following terms apply: This program contains a disabling device that will prevent it from being used upon expiration of this license. You will not tamper with this disabling device or program. You should take precautions to avoid any loss of data that might result when the program can no longer be used. See the License Agreement terms that apply to the use of evaluation code. 8.2 Trademarks and service marks The following terms are trademarks or service marks of the IBM Corporation in the United States or other countries or both: DB2 IBM iSeries z/OS zSeries Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, and service names may be trademarks or service marks of others. (C) Copyright IBM Corporation 2003, 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.