IBM(R) DB2(R) Recovery Expert for Multiplatforms, Version 2 Release 1 Fix Pack 2 README CONTENTS 1.0 ABOUT THIS README FILE 1.1 Evaluation code 1.2 Language support 1.3 Before using DB2 Recovery Expert 1.3.1 Testing DB2 Recovery Expert 1.4 Corrected known problems 2.0 PREREQUISITES 2.1 Hardware requirements 2.1.1 Graphical display requirements 2.1.2 Solaris 10 support is added 2.2 Software requirements 2.2.1 Fix Pack installation requirements 2.2.2 32-bit Java Runtime Environment required 2.2.3 AIX-specific software requirements 2.2.4 DB2 Grouper-specific requirements 2.3 Online Help system requirements 2.4 Installation not supported with DB2 alternate Fix Packs 2.5 Tivoli Storage Manager (TSM) configuration requirements 3.0 INSTALLATION INSTRUCTIONS 3.1 General installation instructions 3.2 Installing in a partitioned database environment 3.3 Ownership and permissions issues in UNIX environments 3.3.1 Installation ownership and permissions requirements 3.3.2 Configuration ownership and permissions requirements 3.4 AIX-specific installation information 3.4.1 Insufficient Number of Shared Memory Segments (SQL1224N) 3.5 Silent Install Feature 3.6 Post installation steps 3.6.1 Archive Log Inventory Data (ALID) must be rebuilt (REQUIRED) 3.6.2 Versioning Repository (VR) must be rebuilt (REQUIRED) 4.0 CUSTOMIZATION INSTRUCTIONS 5.0 RESTRICTIONS 5.1 Cannot recover DB2 V7 objects into DB2 V8 5.2 Date formats used by DB2 Recovery Expert 5.3 DATALINK columns not supported by table space recovery with online backups 5.4 Restrictions for LOB/long fields in separate DMS table spaces 5.5 User-defined structured types not supported by table recovery 5.6 User-defined Types not supported by Log Analysis 5.7 Must connect to database for multiple partition operations 5.8 Locating backups when using database aliases 5.9 Restriction for SQL generation for LOB/LONG columns after table recovery or DB2 LOAD 5.10 Dependencies of views are not recovered 5.11 Database recovery use default path 5.12 Database recovery to 64-bit instance requirement 5.13 Online Help system restriction 5.14 SQL generation problem for large non-COMPACT LOB columns 5.15 Restriction for character and graphic columns containing null bytes 6.0 DB2 RECOVERY EXPERT FAST BACKUP 6.1 RE Fast Backup prerequisites 6.2 Software requirements 6.3 Supported network storages 6.4 Supported storage area network (SAN) 6.5 Supported network attached storage (NAS) 6.6 Installing Fast Backup 6.7 Using NAS on Windows 6.8 Using NAS and Fast Backup on Windows 2003 6.9 Using Fast Backup by multiple instances 6.10 Using the Fast Backup Command Line Interface 6.11 When to do a table space level backup 6.12 Point-in-time table space fast backup restore in a multi-partitioned environment 6.13 Table space level backup 6.14 DB2 Fast Backup considerations and restrictions 6.15 Linux FOR xSeries (64-bit DB2) 6.16 Using the ESS V2 Flashcopy feature 6.17 Cataloging another system and instance 6.18 Clearing PVID on AIX 6.19 Setting JAVA_HEAP_SZ 6.20 Installation error resolutions 6.21 RE Fast Backup history image error resolutions 6.22 RE Fast Backup client log data 6.23 Object restore considerations for SAN storage 6.24 Table space container volume considerations 6.25 AIX Freeze/Thaw feature 6.26 Fast Backup task considerations using user exit 6.27 DS8000 volume search range 7.0 CORRECTIONS TO DOCUMENTATION 7.1 Using column filters with Log Analysis 7.2 Online dropped partitioned database recovery 7.3 Using primary or unique keys with SQL generation 8.0 HOW TO GET HELP 9.0 NOTICES 9.1 Other Notices 9.2 Use of evaluation program 9.3 Trademarks and service marks 1.0 ABOUT THIS README FILE Welcome to IBM DB2 Recovery Expert, Version 2 Release 1 README file. This README file contains information about installing IBM DB2 Recovery Expert. IBM DB2 Recovery Expert has been tested and validated with DB2 Universal Database(TM) Version 8 Releases 1 and 2. Subsequent releases might require additional maintenance. In this README file, the following naming convention applies: IBM DB2 Recovery Expert for Multiplatforms is abbreviated to DB2 Recovery Expert. 1.1 Evaluation code If you are using evaluation code, the evaluation code enables you to try this product for a period of 60 days. After 60 days, you must purchase a license to continue to use the product. When you purchase the product, the license is enforced based upon the platform on which you are running IBM DB2 Recovery Expert. Read NOTICES Section 9.2, Use of evaluation program, and the License Agreement provided with your evaluation copy of the program. Also, please read section 3.2 for information about installing and using the product in a partitioned database environment. 1.2 Language support DB2 Recovery Expert is a translated product that supports the following languages: English, Japanese, Korean, Russian, Simplified Chinese, and Traditional Chinese. The product will select the appropriate language according to the system locale definition. The default language is English. 1.3 Before using DB2 Recovery Expert DB2 Recovery Expert is a new product that offers advanced recovery facilities. Because recovering your data is of such critical importance, you must be experienced with the recovery process and with the recovery facilities included with DB2 Recovery Expert before deploying DB2 Recovery Expert to your production environment. Therefore, it is recommended that you thoroughly test DB2 Recovery Expert in a test environment before you deploy it to your production environment. 1.3.1 Testing DB2 Recovery Expert -Back up your data using the method of your choice. DB2 Recovery Expert depends on a quality backup of your data. -Analyze your logs using the Log Analysis tool. -Create and inspect Undo/Redo SQL. -Familiarize yourself with the versioning repository. Failure to fully understand and implement recovery facilities can result in unpredictable results. 1.4 Corrected known problems This release contains corrections for the following problems: APAR PK11989: Minilog db2mm command pathname initialization is fixed. APAR PK14492: Database recovery will recover to the correct target instance. APAR PK17390: Support DB2 WSE where db2nodes.cfg file doesn't exist. APAR PK20645: If DB2TOOLS is defined as the top directory, the RE launcher doesn't come up on Windows systems. APAR PK21881: Log analysis reports broken log sequence on AIX (generates error message ARY0202E). APAR PK23158: Log Analysis reads non-log files in log directories (generates error message ARY0201E). APAR PK23408: Log analysis uses excessive amounts of memory (generates error message ARY0187E). APAR PK23453: Container redirection panel doesn't list system temporary table spaces. APAR PK25308: GUI doesn't recognize LOGRETAIN setting if only the LOGARCHMETH1 parameter is set. APAR PK26430: Unable to use a 64-bit TSM user exit. IY81421 (DB2 APAR): When installing DB2 Recovery Expert, the DB2 Recovery Expert Control Center plugin successfully installs on the DB2 Control Center toolbar. However, due to a problem with DB2, all previously installed Control Center plugins are overlayed. There is no workaround for this problem. This problem is fixed in DB2 UDB Version 8, Fix Pack 12. 2.0 PREREQUISITES DB2 Recovery Expert has hardware and software requirements. 2.1 Hardware requirements DB2 Recovery Expert has the following hardware requirements: -Memory and disk space sufficient to fulfill DB2 minimum requirements. -For Windows platform install: Approximately 150 MB of free disk space on any Windows platform. -For UNIX platform install: Approximately 150 MB of free disk space in the /tmp filesystem, 75 MB of free disk space in the target install filesystem (the default location is /opt) and 100 MB of free disk space in the /var filesystem, for any UNIX platform. -Additional space for user data (varies depending on the size of your databases and the amount of activity your system encounters). Requirements for the Archive Log Inventory Data (ALID) files and other intermediate data created during log analysis can be very large (gigabytes). 2.1.1 Graphical display requirements A graphical display terminal (X-terminal or equivalent software emulation environment) is required to use the full functionality of DB2 Recovery Expert. If necessary, the initial product installation can be performed in text mode by specifying the "-console" argument on the product installer command. Some of the product functionality is available via command line tools that do not require a graphical display, but a graphical display will be required to run the Recovery Expert GUI application to perform object recovery. When initializing the graphical display environment on UNIX/Linux systems, be sure to set the DISPLAY variable to the desired output device before running DB2 Recovery Expert. You can test that the display terminal works correctly by using the "xclock" command. 2.1.2 Solaris 10 support is added The Recovery Expert Version 2 Release 1 Modification level 1 Full License and Evaluation product now support Solaris 10. It is not necessary to apply Fix Pack 1 on this level of code because Fix Pack 1 is equivalent to the Modification 1 level. 2.2 Software requirements To use IBM DB2 Recovery Expert in UNIX/Linux environments, you must have IBM DB2 V8 ESE Fix Pack 5 or later. To use IBM DB2 Recovery Expert in Windows environments, you must have IBM DB2 V8 ESE Fix Pack 7a or later. This release of DB2 Recovery Expert for Multiplatforms requires you to run DB2 locally. To run Recovery Expert, you must install the IBM JDBC driver. This driver is included with the DB2 Run-Time Client. Recovery Expert does not include this component. 2.2.1 Fix Pack installation requirements Fix Packs for this product are cumulative. If you are installing a Fix Pack, you must have a licensed version of DB2 Recovery Expert for Multiplatforms, Version 2 Release 1 installed on your system at the minimum required code level. 2.2.1.1 Fix Pack installation requirements for Fast Backup If you are installing Fix Pack 2, you must ensure that the Fast Backup Administration Database Repository (gdbdb) exists. For more information about the Fast Backup Administration database, refer to the "Configuring and Administering DB2 Recovery Expert Fast Backup" section of the DB2 Recovery Expert User's Guide. 2.2.2 32-bit Java Runtime Environment required DB2 Recovery Expert requires a 32-bit Java Runtime Environment (JRE). On AIX and Windows platforms, a 32-bit JRE will be installed if a suitable JRE is not found on the system. On other platforms, the product installation will fail if a suitable JRE is not found, and the user must locate and install a 32-bit JRE before proceeding with the installation. The installation process records the location of the JRE so it can be used later by DB2 Recovery Expert. Please refer to the User Guide for additional information about the product Java requirements. 2.2.3 AIX-specific software requirements To use Recovery Expert with AIX, you must ensure that the level of the C++ Runtime environment fileset installed on the system is at least version 5.0.2.0. For AIX 5L systems: You can view the current fileset level with the command: lslpp -L xlC.aix50.rte If the fileset version is less than 5.0.2.0, you must obtain and install the fileset xlC.aix50.rte to the latest available maintenance level for version 5.0.2.x. For more information about obtaining and updating filesets, contact your AIX system administrator. 2.2.4 DB2 Grouper-specific requirements Grouper is an optional software component that is independently packaged and installed separately from DB2 Recovery Expert. For more information about installing Grouper, refer to the DB2 Grouper Users Guide. If you already have the DB2 Grouper component installed, you must be at the Grouper Build 164 level. If you are at a previous build level, install the latest Grouper Fix Pack. 2.3 Online Help system requirements DB2 Recovery Expert uses an Eclipse-based help system with the following software requirements: - On Windows systems, the help system requires Microsoft Internet Explorer Version 6.0 SP1 or later, or Mozilla-based browsers Version 1.7 or later. - On UNIX and Linux platforms, the help system requires Mozilla-based browers Version 1.7 or later. The Eclipse-based help system has the following Operating System requirements in the UNIX environments: - For AIX 5.1, maintenance level 5.1.0.75 or higher. - For AIX 5.2, maintenance level 5.1.0.75 or higher. The help system does not officially support AIX 5.1 or Solaris 8. The help system can be used on these operating systems, but problems can only be reported on supported operating system levels. In Solaris environments, Mozilla needs to be accessible via the PATH environment variable definition. 2.4 Installation not supported with DB2 alternate Fix Packs DB2 Recovery Expert installation requires a standard version of DB2 that is installed in the default location. DB2 alternate fix packs are not supported and will be ignored by the install procedure. 2.5 Tivoli Storage Manager (TSM) configuration requirements If Tivoli Storage Manager (TSM) is used for archiving DB2 logs or backups, DB2 Recovery Expert requires that the TSM configuration parameter "PASSWORDACCESS" is set to "GENERATE". 3.0 INSTALLATION INSTRUCTIONS 3.1 General installation instructions To install DB2 Recovery Expert, ensure that you don't have DB2 Control Center running on your system, and then complete the following tasks: 1. Log on to your system: For Windows, perform the following steps: a. Log in as the Administrator user if your Windows system is configured for multiple user accounts. b. Locate the directory containing the setup files and run db2rewin32setup.exe For non-Windows systems, perform the following steps: a. Log in as the SuperUser ("root") user. b. Open a terminal window to activate a command-line shell. c. Change your current directory to the one containing the DB2 Recovery Expert installation package, as shown in the list below: AIX - db2reaixsetup Linux on x86/x86_64 - db2rexlinuxsetup Linux on pSeries - db2replinuxsetup Solaris - db2resolarissetup d. Run the installation package from the shell. For example, "./db2reaixsetup". Note: If the program is not executable, you can make it executable with the command "chmod u+x ./db2re*setup". 2. The installation wizard starts. Follow the instructions in the installation wizard, clicking Next to proceed through the install. 3. Check for Service updates on the Fix Pack Web site: http://www.ibm.com/software/data/db2imstools/support/fixpaks.html 4. Configure DB2 Recovery Expert. See Section 4.0 3.2 Installing in a partitioned database environment In a partitioned database environment, your database may be spread across several computers, which share a common directory area for each instance using the Network File System. If you are installing a fully-licensed version of DB2 Recovery Expert, you should install it onto a shared file system so that each computer participating in the partitioned database can access it from a common location. You can do this by specifying a path on the shared file system during the installation process. You must ensure that the target filesystem permits SetUID programs to be executed. If you are installing an evaluation version of DB2 Recovery Expert, you should not install it onto a shared filesystem. Instead, you must install it separately on each computer that is part of the partitioned environment. This requirement is related to the way that the evaluation license is processed. When installing a Fix Pack version of Recovery Expert, you must install it in the same directory on each computer where the licensed version was previously installed. After the installation is complete, refer to the DB2 Recovery Expert for Multiplatforms User's Guide for additional configuration and customization steps. 3.3 Ownership and permissions issues in UNIX environments 3.3.1 Installation ownership and permissions requirements The DB2 Recovery Expert front-end program (db2recex) is a SetUID program that is owned by root. It initially executes as the root user, then changes to the identity of the DB2 instance user as specified in the DB2INSTANCE environment variable or on a command line argument. Any users that will execute Recovery Expert must be added to the DB2 instance's primary group. For security purposes, the target directory into which Recovery Expert is installed should not be writable by "group" or "others". In general, the ownership and permissions of the various Recovery Expert files that are installed should not be changed. When the product executes, it performs some security checks to ensure that certain directories and files are accessible but are not writable or executable by "group" or "others". If the security checks fail, an error message will be displayed and the problem must be resolved before the product will run. Recovery Expert must be installed into a filesystem that permits SetUID programs to be executed. The default installation into /opt/IBM/DB2TOOLS/RecoveryExpert sets up the correct ownership and permissions, but does not ensure that /opt allows SetUID programs to execute. If the product is installed into an NFS shared network filesystem, additional steps may be required to ensure that the NFS filesystem is exported and mounted correctly so as to allow execution of a SetUID program owned by root. If the correct settings are not in effect when Recovery Expert is started, it will terminate with an error message. 3.3.2 Configuration ownership and permissions requirements The DB2 Recovery Expert configuration parameters are defined in the "recex.properties" file located in the "conf" subdirectory in the product installation tree. This configuration file must be owned and writable by the root user, but cannot be writable by "group" or "others". The DB2 Recovery Expert base data directory is defined using the DATA_DIR keyword in the recex.properties file. The default definition sets the data directory to "/var" with the installation directory path appended, so it typically defaults to: "/var/opt/IBM/DB2TOOLS/RecoveryExpert". When the product is run by a particular DB2 instance, a subdirectory is created under the base directory using the name of the DB2 instance (e.g., "db2inst1"), so the complete data directory name for the "db2inst1" user might be "/var/opt/IBM/DB2TOOLS/RecoveryExpert/db2inst1". The user can change the definition of DATA_DIR to point to a different location if desired; for example, the recex.properties configuration file could be changed to define DATA_DIR as: DATA_DIR=/db2files/db2re In this case, the actual data directory used for the user "db2inst1" would be "/db2files/db2re/db2inst1". Note: the curly braces that appear around the directory separator character (/) in the original configuration file are optional in UNIX environments and can be omitted when updating pathnames in the file. Thus, it is not necessary to enter: DATA_DIR={/}db2files{/}db2re However, they are required in Windows environments. Currently, Recovery Expert enforces some ownership and permissions requirements on the base data directory and the immediate subdirectories that are created under it for a specific DB2 instance. The base directory (identified by DATA_DIR) must be owned by "root" and the access permissions must to set to prevent write access by "others". The instance-specific subdirectories underneath that directory must be owned either by "root" or the DB2 instance user, and the access permissions must to set to prevent write access by "group" or "others". If the correct settings are not in effect when Recovery Expert is started, it will terminate with an error message. 3.4 AIX-specific installation information 3.4.1 Insufficient Number of Shared Memory Segments DB2 on AIX(R) version 4.3.3 or later will not allow more than a few simultaneous local connections to a database. If the connection limit is reached, DB2 Recovery Expert will report an error message when attempting to connect to a database. An error code SQL1224N message may also be displayed or written to the Recovery Expert log file. The failure results from an operating system-imposed limit on the number of shared memory segments available to DB2. The error message states, "Could not connect to database: [IBM][CLI Driver] SQL1224N. A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. " If this error occurs when you attempt to connect to a database, the error usually indicates that the number of shared memory segments allowed by AIX to connect to the database has been exceeded. In this case you must change the DB2 configuration to increase the number of shared memory segments or avoid using shared memory. Additional information about this topic can be found by searching the DB2 Technical Support Knowledge Base for Technote document numbers 1154603 (SQL1224N connection error when using DB2 on AIX) and 1009742 (SQL1224N error with WebSphere Application Server) on the IBM web site (www.ibm.com). For complete instructions on how to resolve this issue, please refer to the DB2 Recovery Expert for Multiplatforms User's Guide. 3.5 Silent Install Feature An automated silent install option is available to allow installing Recovery Expert without requiring any user interaction. The silent install uses a response file that defines installation parameter settings. A sample response file is provided with the product and can be customized as needed for use with subsequent installs. See product user guide for more information. Starting from FP2, install program will detect components that are already installed and update those components automatically. You will not be prompted to choose the components for install any more. You can also run the install silently. If the Fast Backup Server component is not installed, type "db2rexxxsetup -silent" from the command line, and Recovery Expert will be updated. If the Fast Backup Server is installed previously, then you must provide the information for the Fast Backup Server Administration Database in a response file, then run the command "db2rexxxsetup -options ary_install_fp" from the command line. The following is a sample response file, titled ary_install_fp: -silent -W DB_User_Input.DB2Dbname="GDBDB" -W DB_User_Input.DB2Instance="db2admin" -W DB_User_Input.DB2Passwd="password" 3.6 Post installation steps 3.6.1 Archive Log Inventory Data (ALID) must be rebuilt (REQUIRED) The format of the Archive Log Inventory Data (ALID) files that contain log meta data used by DB2 Recovery Expert has changed in this release. If you have used a previous version of DB2 Recovery Expert with any databases, the ALID data files maintained for each database need to be rebuilt to use the new format. After installing this release of the product, you should either delete the old data files, or run the Log Analysis command line tool with the -Z parameter for each database before using any of the other DB2 Recovery Expert features. You can delete all of the old ALID files manually, and they will be automatically recreated using the new format the next time the Log Analysis tool is run. The data files are located under the data directory that is defined in the product recex.properties configuration file using the DATA_DIR property. On Windows systems, the default location is the "data" subdirectory under the product installation directory, which is typically "C:\Program Files\IBM\DB2TOOLS\RecoveryExpert\data". On UNIX/Linux systems, the default data directory is "/var/opt/IBM/DB2TOOLS/RecoveryExpert". If a previous version of Recovery Expert was used on the machine, there will be a data directory tree and a subdirectory for each DB2 instance with which Recovery Expert was used. You can delete the entire subdirectory contents for each instance. Instead of deleting the old ALID files, you can run the "db2la" Log Analysis command to generate new ALID files. This method requires running db2la for each database that Recovery Expert will be used with. You should specify a begin timestamp that is near to the current timestamp to limit the report phase. For Unix systems, use this syntax: db2la -d database -S -V 3 -Z -b `date +%Y%m%d%H%M%S` On Windows systems, run the command using this format: db2la -d -S -V 3 -Z -b "yyyy/mm/dd hh:mm:ss" Rebuilding the log inventory data can require processing all of the available archive logs, so the process can potentially take a long time if there is a lot of log data to process. If desired, use the "startlog" directive in recex.properties to skip processing older logs. If you do not rebuild the inventory files, an error message indicating this requirement may be reported when running the Log Analysis tool or the GUI application. Please refer to the DB2 Recovery Expert product user guide for more information about the Archive Log Inventory Data. 3.6.2 Versioning Repository (VR) must be rebuilt (REQUIRED) The format of the Versioning Repository (VR) data used by DB2 Recovery Expert has changed in this release. If you have used a previous version of DB2 Recovery Expert with any databases, the VR for each database needs to be rebuilt to use the new format. After installing this release of the product, you should perform the following steps for each database before using any of the other DB2 Recovery Expert features: - delete the VR partition group: db2 drop nodegroup ORVRNG1 - create the VR using the GUI application or the CreateVersionRepository command line tool. 4.0 CUSTOMIZATION INSTRUCTIONS For complete instructions on how to customize and use DB2 Recovery Expert, refer to DB2 Recovery Expert for Multiplatforms User's Guide. If you received your copy of DB2 Recovery 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 RESTRICTIONS 5.1 Cannot recover DB2 V7 objects into DB2 V8 DB2 data and objects that have been backed up in DB2 V7 format cannot be recovered into DB2 V8 objects. They must be recovered in V7 format. 5.2 Date formats used by DB2 Recovery Expert DB2 Recovery Expert displays most date and time values using localized formats for various international regions. However, user input in the GUI application and for the command line parameters currently requires specifying date/time values using a fixed format. In particular, the text box for specifying the date on the GUI application Point-in-time Selection panel requires the date in the year/month/day format "YYYY/MM/DD" (for example, "2005/09/28"). The same is also true for the Log Analysis Tool Report parameters panel for the Start date and End date fields. The formats for date/time parameters used by the command line tools currently use a fixed format that follows the year/month/day order, and are documented in the product user guide. 5.3 DATALINK columns not supported by table space recovery with online backups DB2 Recovery Expert does not currently support recovering table spaces that contain tables with DATALINK columns when online backups are used. However, the recovery may be accomplished by recovering the tables individually. 5.4 Restrictions for LOB/long fields in separate DMS table spaces DB2 Recovery Expert does not currently support recovering dropped tables when the table data and the LOB/long field data for the table are located in separate backups. This issue can arise if separate table space backups are performed for the table spaces that contain the related data. 5.5 User-defined structured types not supported by table recovery DB2 Recovery Expert does not support data recovery through the GUI application or the db2ox command line tool for tables that contain columns defined in terms of a User Defined Structured Type (UDST), or for "typed tables" where the entire table is defined in terms of a UDST using the syntax: CREATE TABLE OF [...] where identifies the structured type name upon which the table column attributes are based. UDST definitions (without the data) can be recovered from the GUI application Object Selection panel. Also, table space recovery is supported for table spaces that contain tables dependent on UDSTs, as long as the recovery path does not include redo/undo SQL. Finally, table recovery is supported for tables with columns defined as Distinct (not Structured) UDTs. 5.6 User Defined Types not supported by Log Analysis The Log Analysis tool and the recovery process do not support generating detailed reports or redo/undo SQL for tables containing User Defined Type (UDT) columns. This applies to both User Defined Distinct Types and User Defined Structured Types. Recovery paths involving redo/undo SQL will not be displayed by the GUI application for tables dependent on UDTs. Recoveries are still possible as long as SQL generation is not required. 5.7 Must connect to database for multiple partition operations When using the GUI application to create or update the Versioning Repository (VR), or to perform an object recovery in a multiple partition environment that includes more than one computer, it is necessary to use the File | Connect menu to connect to the database after selecting the database name from the pull-down menu on the main application panel. This is required to specify the username and password parameters for establishing the database connection across all partitions. This step is not required for single partition environments, or for multiple partition environments where all partitions are defined on the same computer. 5.8 Locating backups when using database aliases When backups are taken for a database, they are recorded using the name of the database alias (name) that was used with the backup command. If DB2 Recovery Expert connects to an alternate database alias to perform log analysis or a recovery, backups must exist for the database under the selected alias name or else Recovery Expert will not be able to locate the backups. 5.9 Restriction for SQL generation for LOB/LONG columns after table recovery or DB2 LOAD To ensure correct SQL generation for UPDATEs and DELETEs performed on tables containing LOB/LONG columns after a DB2 LOAD or a recovery using a Fast Backup is run, it is necessary to perform a full database or table space backup that includes the affected table space following the LOAD. The backup image establishes a new sequence point for SQL generation following the LOAD. DB2 Recovery Expert performs a DB2 LOAD as part of the table recovery procedure. To avoid leaving the table space in a backup pending state, Recovery Expert either performs the LOAD with the COPY option (default), or you can select an option to perform a table space backup after the data is loaded. To avoid potential SQL generation problems after the recovery, the user should select the option to perform a backup. If a backup is not taken after a LOAD, log analysis may be unable to reconstruct details for UPDATE and DELETE operations that are subsequently performed on the affected table. In this case, it will report "NOT AVAILABLE" for LOB/LONG column values in the detailed report and in any generated SQL statements that reference those columns. 5.10 Dependencies of views are not recovered During a table or table space recovery, DB2 Recovery Expert recovers table dependencies, including views that are related to tables that are being recovered. It cannot recover views that are defined in terms of other views unless the dependent views exist at the time of the recovery. If the dependent views do not exist, the recovery will succeed, but the affected views will not be created. If a view cannot be recreated during a recovery because it has missing dependencies, you can manually recreate the view later after all of the dependences have been recreated. 5.11 Database recovery use default path DB2 Recovery Expert only supports recovering a database to the default database path location that is defined by the DB2 instance DFTDBPATH parameter. It cannot restore a dropped database to its orginal location. To restore a database to a different location that the current default setting, use one of these methods: 1) Perform the recovery by using the DB2 RESTORE command, and specify the desired location on the command arguments. 2) - Temporarily change the DFTDBPATH instance parameter to the desired location. - Perform the database recovery using DB2 Recovery Expert. It will restore the database using the altered path definition. - Reset the DFTDBPATH instance parameter to its original value. 5.12 Database recovery to 64-bit instance requirement To recover a database to a 64 bit DB2 instance, the instance must be cataloged as a remote node. 5.13 Online Help system restriction The Eclipse help creates and accesses many files and directories under the Eclipse directory and marks them with owner/permissions of the current user (the DB2 instance user that is running RE). If you are the first user to run it, all of the files and directories will be get created with your identity. You can then continue to run help in the future, but all other users will be locked out due to the owner/permissions settings. Another user might be able to run the help if the ownership/permissions are set to more "open" values. 5.14 SQL generation problem for large non-COMPACT LOB columns Incorrect column data might be produced for SQL statements generated by Log Analysis during recoveries or when the Log Analysis tool is used directly to create REDO or UNDO SQL. The problem occurs for tables containing BLOB, CLOB, or DBCLOB columns that are defined as "NOT COMPACT" when the column data exceeds the maximum size of an SQL constant and requires using reference parameters in the generated SQL. In these cases, performing the generated SQL will add garbage data at the end of the recovered LOB column data. 5.15 Restriction for character and graphic columns containing null bytes The DB2 Recovery Expert Log Analysis tool and object recoveries that generate REDO or UNDO SQL do not produce valid SQL for character columns (CHAR, VARCHAR, LONG VARCHAR, CLOB), or graphic columns (GRAPHIC, VARGRAPHIC, LONG VARGRAPHIC/DBCLOB) when the column data includes null bytes (hexadecimal 00 values). In this case, the SQL statement is truncated at the occurrence of the null byte and the trailing quote character is missing. Performing the statement will produce an error message. Recovery paths that do not include SQL generation will avoid this problem. A similar problem exists in partitioned database environments for table space recoveries from online backups and table recoveries from either online or offline backups. If tables have CHAR,VARCHAR, LONG VARCHAR, GRAPHIC, VARGRAPHIC, or LONG VARGRAPHIC columns that contain null bytes, the recovery will eliminate the null bytes and produce incorrect results. This problem also occurs when the db2ox command line tool is used to extract table data in DEL format. 6.0 DB2 RECOVERY EXPERT FAST BACKUP FOR MULTIPLATFORMS This section contains information about installing IBM DB2 Recovery Expert Fast Backup. IBM DB2 Recovery Expert Fast Backup has been tested and validated on DB2 Universal Database(TM) Version 8 Release 1 Fix Pack 7a and DB2 Universal Database(TM) through Version 8 Release 2. Subsequent releases might require additional maintenance. In this section, the following naming convention applies: IBM DB2 Recovery Expert Fast Backup for Multiplatforms is abbreviated to DB2 Recovery Expert FB. 6.1 RE Fast Backup prerequisites DB2 Recovery Expert has hardware and software requirements. 6.2 RE Fast Backup software requirements To use IBM DB2 Recovery Expert FB, you must have one of the following DB2 versions: - IBM DB2 V8 ESE Fix Pack 7a or later If you use IBM DB2 V8 ESE Fix Pack 9, you must apply IY71480. If you use RE Fast Backup with Java 1.4.2 and DB2 64-bit instance on Solaris, you must use Java Version 1.4.2-10 or later. 6.2.1 Data Capture Changes (DCC) option requirement The Data Capture Changes (DCC) option must be set on tables that are backed up using Fast Backups in order to support SQL generation during point-in-time recoveries or by the Log Analysis tool. 6.3 Supported network storages To use IBM DB2 Recovery Expert FB, your DB2 server must be connected with one or more Network Storages. Supported Storages are described in the following sections. 6.4 Supported Storage Area Network (SAN) The following SAN storage devices are supported by RE Fast Backup. - IBM Enterprise Storage Server Model F20 or compatible with FlashCopy (V2 or later) - IBM TotalStorage DS8000 series or compatible with FlashCopy (AIX/Windows/Linux) - Hitachi Freedom Storage Lighting 9900V series or compatible with Hitachi ShadowImage software. - EMC Symmetrix DMX800 Series or compatible with TimeFinder/mirror - NEC iStorage S Series S4100 or compatible with Dynamic Data Replication software 6.5 Supported Network Attached Storage (NAS) Netapp Filer F700 Series or compatible with Snapshot software and SnapRestore software 6.6 Installing Fast Backup 6.6.1 Installing the Fast Backup Windows client To install Fast Backup, unzip the Fast Backup Windows client to the Windows system that you will install on. Execute setup.exe to install. 6.6.2 Installing the Fast Backup Windows server The Fast Backup server is part of Recovery Expert. To install Fast Backup, you must select the Custom Install option when installing Recovery Expert. If you choose not to install the Fast Backup function at this time, you have the option to install it at a later time. Refer to the section titled "INSTALLATION INSTRUCTIONS" for instructions on installing the Fast Backup Windows server. 6.6.3 Installing the Fast Backup Server on a DB2 V8.2 Fix Pack 9 system If you are installing DB2 Recovery Expert Fast Backup server on a DB2 V8.2 Fix Pack 9 system for the first time, you might receive errors during the Fast Backup administration database creation. After the installation, enter the following commands to create your Fast Backup Administration database: For Windows: %DB2TOOLS%\RecoveryExpert\fastbackup\ddl> gdbcreate -db GDBDB -user username -pass password -recreate on %DB2TOOLS%\RecoveryExpert\fastbackup\ddl> gdbcprop -db GDBDB For Linux and UNIX: $DB2TOOLS/RecoveryExpert/fastbackup/ddl> ./gdbcreate -db GDBDB -user username -pass password -recreate on $DB2TOOLS/RecoveryExpert/fastbackup/ddl> ./gdbcprop -db GDBD 6.7 Using NAS on Windows If you use NAS for database storage, you must mount NAS by DB2 service account. For example, DB2 service is started as DB2ADMIN, DB2ADMIN must mount NAS storage. Also make sure to check an appropriate file system for the OS that you are using. 6.8 Using NAS and FastBackup on a Windows 2003 server If you use Windows 2003 Server and NAS, the share name of NAS should not include any spaces. 6.8.1 Mounting NAS Mount NAS on drive N: (you can use any drive letter) NET USE N: \\nasstorage\db2_data 6.8.2 Installing AUTOEXNT AUTOEXNT is a utility of Windows Server 2003 Resource Tool Kits. Download and install Windows Server 2003 Resource Tool Kits. As of 2005/04/05, Windows Server 2003 Resource Tool Kits is on the following url: http://www.microsoft.com/downloads/details.aspx?familyid=9d467a69 -57ff-4ae7-96ee-b18c4790cffd&displaylang=en 6.8.3 Configuring the AUTOEXNT service To configure the AUTOEXNT service: 1. Right click on "My Computer", select "Manage" 2. Select "Service" on "Services and Applications" 3. Open "AutoExNT" properties 4. Set startup as "Automatic" 5. Open "Log On" tab and select "Local System account" 6. Click on "Apply" 7. Open %systemroot%\system32\AUTOEXNT.bat or create the file. 8. Write your setting as follows: NET USE N: \\nasstorage\db2_data 9. Log on using db2 service account 10. Restart AutoExNT service 11. Create DB on N 6.9 Using Recovey Expert Fast Backup by multiple instances If you would like to use DB2 Recovery Expert from a db2 instance user account which didn't create Fast Backup Administration Repository Database, you must run the gdbcprop command from that account before running DB2 Recovery Expert. On Windows: %DB2TOOLS%\RecoveryExpert\fastbackup\ddl\gdbcprop.cmd -db On UNIX and Linux: $DB2TOOLS/RecoveryExpert/fastbackup/ddl/gdbcprop -db 6.10 Using the Recovery Expert Fast Backup Command Line Interface To use DB2 Recovery Expert FB command on a client PC, set the DB2SYSTEM environment variable.For example, to get the backup history from the DB2 server named "DSVR", type: SET DB2SYSTEM=DSVR %DB2TOOLS%\RecoveryExpert\fastbackup\bin\gdbtask list Or, you can run the command with the option: %DB2TOOLS%\RecoveryExpert\fastbackup\bin\gdbtask list -db2system DSVR 6.11 When to do a table space-level backup A Recovery Expert table space backup can only be used for a non-dropped, point-in-time table space recovery. If you create, drop, or alter a table in the table space that was backed up using Fast Backup, then you are must create a new Fast Backup. The new backup will enable you to recover the table space to a point-in-time after the table in the table space was altered, created, or dropped. 6.12 Point-in-time table space fast backup restore in a multi-partitioned environment To perform a point-in-time table space fast backup restore in a multi-partitioned environment: 1. Start Recovery Expert. 2. Connect to the catalog partition and perform the point in time recovery. This will do the fast backup restore and generate redo sql for the catalog partition. 3. Connect to each of the other partitions that are defined. 4. Run Log Analysis redo sql for the same time period that it was run for on the catalog partition (start time is the end of the fast backup time, and end time is the recovery point in time). 6.13 Table space level backup When doing a table space level backup, please note the following items: -The table space must be in the quiesce share state when running a fast backup for it. -If you run insert/update/delete sql in this situation, DB2 returns error code SQL0290N. -If you want to use the tablespace backup as an online backup, change the application to check SQL0290N. 6.14 DB2 Recovery Expert Fast Backup considerations and restrictions 6.14.1 Consideration of more than one table space backup If you back up more than one table space, you can run a point-in-time recovery for one table space. In this situation, all of the other table spaces might be recovered to the point where you backed up. If the backup image is stored in volumes that support object restore, all of the other table spaces will be preserved as they are. 6.14.2 Restriction for a remotely-cataloged database When running Recovery Expert Fast Backup, do not specify a remotely- cataloged database. If you specify a remotely-cataloged database, you will not be able to select the recovery path, which uses Recovery Expert Fast Backup. 6.15 Linux for xSeries (64-bit DB2) Recovery Expert FB is restricted on Linux for xSeries (64-bit DB2) because DB2 does not support stored procedures in that environment. Go to: http://www-306.ibm.com/software/data/db2/udb/ad/v8/java/ for more information on DB2 Java Support. 6.16 Using the ESS V2 Flashcopy feature To maintain complete disk consistency on ESS, Recovery Expert FB Fix Pack 1 supports CG feature and flashcopy freeze option. Before running the Recovery Expert FB task using Recovery Expert FB Admin window, you must create two ESS tasks. The first task is Consistency Task. And the other is Flashcopy with freeze option. 6.16.1 How to create a consistency task 1. Connect to the ESS Server using a web browser 2. Select "Copy Services" 3. From the "Available Actions", select an action 4. Left-click on "Logical Subsystems" and right-click twice on the LSS 5. Left-click on "Consistency Created" and click Next 6. Click Next 7. Type "ConsistencyTask" on Task Name panel 8. Click Save 6.16.2 How to create a FlashCopy with the FREEZE option 1. Connect to the ESS Server using a web browser 2. Select "Copy Services" 3. From the "Available Actions", select an action. 4. Select "Volumes" 5. Select the correct item in "Source" and "Target" 6. Click a volume from the source list to specify the backup source 7. Right-click on a volume from the target list to specify the backup target 8. Right-click the target volume again 9. Select "Establish FlashCopy pair" and click Next 10. Select "Freeze Flashcopy Consistency Group" and click Next 11. Type "freezeflash" on TaskName panel 12. Click Save 6.16.3 How to create the Recovery Expert FB backup task using the CG and FREEZE features 1. Start the DB2 Control Center 2. Select a system and open the Recovery Expert FB Admin window 3. Select "Task Setting" and click on "Create Task" 4. Input "Freeze-Flash" on Task ID panel 5. Click "Create Volume Mapping" 6. Select the source ESS volume 7. Select the "flashcopy-freeze" from the backup method combo box 8. Select the consistency task if needed 9. Select the "flashcopy" from the restore method combo box 10. Click Apply 11. Click Close 12. Click OK 6.17 Cataloging another system and instance To manually catalog another system and instance: - Check that the node name and the system name are the same - Check that you have run the CATALOG command with the REMOTE_INSTANCE option For example, to catalog a system named OTRSYS and an instance named db2inst1, run the following command: > db2 CATALOG TCPIP NODE OTRSYS REMOTE OTRSYS SERVER 50000 REMOTE_INSTANCE db2inst1 6.18 Clearing PVID on AIX If the same PVID appears after rebooting on AIX, you can change it using the following steps: 1. Check the pv using following command: > lspv 2. If the same PVID is displayed, then check and specify the target SAN volume. The target volume is the volume that was copied by storage cli command during the backup phase. For example: ESS. > rsList2105s.sh 3. Run the following command to clear the target volume: > chdev -l hdiskxx -a pv=clear 6.19 Setting JAVA_HEAP_SZ After installing Recovery Expert Fast Backup, please change the dbm config JAVA_HEAP_SZ parameter. To change this value, enter the following command: > db2 update dbm cfg using JAVA_HEAP_SZ 4096 6.20 Installation error resolutions If you receive an error during installation, check the following: - If the problem is related to a stored procedure, use the following link for more information: http://publib.boulder.ibm.com/infocenter/db2help/index.jsp?topic=/com.ibm.db2.udb.doc/ad/t0004675.htm - If the problem is related to an administration node catalog, run the following command to check the local administration node information: > db2 list admin node directory If there is no administration node, you can perform either of the following tasks: - Start the DB2 Control Center: > db2cc - Run the following command to catalog administration node: > db2 catalog admin local node system ostype If you cataloged the local admin node as tcpip node, uncatalog the node and re-catalog it as local node: > db2 uncatalog node > db2 catalog admin local node system ostype - If the problem is related to updating Recovery Expert Fast Backup repository database, check the log file in %DB2TOOLS%\RecoveryExpert\log\gdbupdate.log: If you find a SQL0954C error, run the following command to check the current value of the APPLHEAPSZ parameter for the repository database: > db2 get db cfg for Ensure that there is no other application accessing the repository database, then run the following command to increase the application heap size and update the repository database: > db2 update db cfg for using APPLHEAPSZ > gdbupdate -db -user -pass 6.21 REFB history image error resolutions - Check if the Admin node directory exists: > db2 list admin node directory If there is no administration node, you can perform either of the following tasks: - Start the DB2 Control Center: > db2cc - Run the following command to catalog the administration node: > db2 catalog admin local node system ostype - Check that the REFB properties file exists: For Windows: > %APPDATA%\IBM\gdb\gdb.properties For Linux and UNIX: > cat ~/IBM/gdb/gdb.properties If there are no lines or information about this system, run the following command: > gdbcprop -db -user -pass 6.22 RE Fast Backup Client log data RE Fast Backup Client log directory is %APPDATA%\IBM\gdb\log in Windows system. The REFB Client log data files dumped when you use the Fast Backup interface from the DB2 Control Center or REFB Command. 6.23 Object restore for SAN storage considerations The target SAN storage volume to be used for the Object restore must be accessible by the DB2 server system during the Object restore operation. For IBM ESS SAN storage, the target volume can be made accessible by ESS Administration home page: 1. Open ESS Administration home page 2. Click "ESS Specialist" 3. Click "Strorage Allocation" 4. Click "Open System Storage" 5. Click "Modify Volume Assignments" 6. Select the target volume for the DB2 server 7. Select "Assign selected volumes to target hosts" 8. Select a "Target Host" as the DB2 server 9. Click "Perform Configuration Update" 6.24 Table space container volume considerations In case of the table space backup, make sure that the database directory is not located in the volumes in which its table space containers to be backed up by Fast Backup is located. If you have the database directory and its table space containers in the same volume, the restore operation can damage the database. 6.25 AIX Freeze/Thaw feature Fast Backup supports the AIX Freeze and Thaw features, which ensures the integrity of the target volumes during an online ESS/DS8000 FlashCopy on AIX, by default. When Freeze is active, all accesses to the specific filesystem are suspended on AIX systems and the online ESS/DS8000 FlashCopy operation is secured. This feature is enabled under the both of the following conditions: - the filesystem type of the source volume is "jfs2" - the APAR IY66043 on AIX 5.2, or IY59928 and IY59770 on AIX 5.2, or IY59929 on AIX 5.3 installed 6.26 Fast backup task considerations using user exit If you back up a database on more than one volume using the TSM sample script (a sample that uses a user exit function), you should create one task that addresses all of the volumes for that database. Do not create tasks with the sample script for each of the volumes separately. In that case, you will encounter the error with the message below during backup (even if the configuration is correct): "No target volume is found in the remote server or rsList2105s command is already running in the other process." This error might occur because the ESS CLI/DS CLI command that lists volumes cannot run concurrently on the same host machine. If you run Fast Backup for ESS/DS8000 using more than one task with your own user exit script(s), you must be careful of the timing of using the ESS CLI/DS CLI command in the script(s). 6.27 DS8000 volume search range In some DS8000 environments, it might take a long time to show Create Volume Mapping window in creating a Fast Backup task. You can set the volume range to be searched, and shorten the time by adding the following line to gdbconf file in the /etc directory: DSSEARCHGANGE=- For example, if you want to set the search range from volume ID 0700 to 0790, add a line such as: DSSEARCHRANGE=0700-0790 7.0 CORRECTIONS TO DOCUMENTATION 7.1 Using column filters with Log Analysis If column filters are used with the Log Analysis GUI application or command line tool, both the column name and column value must be specified. Wildcards are not supported; only a specific column name and column value can be provided. 7.2 Online dropped partioned database recovery To perform a recovery of dropped partitioned databases, the log files must be available in the correct directory structure and specified in the overflow log path on Recovery Options. The overflow log path must be accessible to all partitions that are defined for the database. For a multi-partitioned database, the log file directory structure should be [logfiles]/NODE####/C#######/ with the log files for each partition and log chain located in the corresponding node and chain directory. The overflow log path must be set to the [logfiles] directory and DB2 ROLLFORWARD automatically looks in the appropriate NODE#### directory for each partition. Run the rollfoward only after the last partition defined to the database is restored and is run for all partitions. It is recommend that you use log archiving when using online backups. This will ensure that the log files are available in the expected directory structure if the database is dropped. If log archiving is not used, the log files are deleted when the database is dropped. For more information, see the restriction titled "Connecting to the database for multiple partitioning" in the Recovery Expert Users Guide. 7.3 Using primary or unique keys with SQL generation When generating UNDO or REDO SQL, ensure that there is a primary or unique key defined on the table for which you are generating SQL. Log analysis will use only the unique key columns when generating the SQL WHERE clauses to match specific rows for UPDATE and DELETE operations. Without a primary or unique key, the results might not match the correct rows that were changed by the original SQL. To avoid data comparison problems, do not use floating point columns defined as data type "REAL" in the primary or unique key definition. 8.0 HOW TO GET HELP For complete and up-to-date source of DB2 Recovery Expert information, including information on issues discovered after this README was published, go to the following Web site: DB2 Recovery 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. 9.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 as 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. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate 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. 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 IBM's application programming interfaces. 9.1 Other Notices 9.1.1 IBM Eclipse Help System The Eclipse Help system contains excluded components. 9.1.1.1 The following components are excluded components: -Ant1.6.2 -SAX 2 -DOM -Lucene 1.4.3 Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. 9.1.1.2 The following componenent is an excluded component. - Tomcat 4.1.30 The Apache Software License, Version 1.1 Copyright (c) 2000 The Apache Software Foundation. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the Apache Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "Apache" and "Apache Software Foundation" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact apache@apache.org. 5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of the Apache Software Foundation. For more information on the Apache Software Foundation, please see http://www.apache.org/. Portions of this software are based upon public domain software originally written at the National Center for Supercomputing Applications, University of Illinois, Urbana-Champaign. 9.1.1.3 The following component is an excluded component: MX4J 1.1.1 LICENSE MX4J is released under an Apache-style license. In practice this means that you can do almost anything you want with the code, including its use in commercial software. The actual text of the license is included below: The MX4J License, Version 1.0 Copyright (c) 2001 MX4J. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This product includes software developed by the XM4J project http://mx4j.sourceforge.net." Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments normally appear. 4. The names "MX4J" and "mx4j" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact Simone Bordet, :biorn_steedom@users.sourceforge.net or Carlos Quiroz, :tibu@users.sourceforge.net 5. Products derived from this software may not be called "MX4J", nor may "MX4J" appear in their name, without prior written permission of Simone Bordet. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE CHRIS SEGUIN OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This software consists of voluntary contributions made by many individuals on behalf of MX4J. For more information on MX4J, please see http://mx4j.sourceforge.net/> 9.1.2 ICU4C and ICU4JNI components The International Components for Unicode (ICU4C and ICU4JNI) are excluded components. ICU License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE Copyright (c) 1995-2003 International Business Machines Corporation and others All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both the above copyright notice(s) and this permission notice appear in supporting documentation. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization of the copyright holder. All trademarks and registered trademarks mentioned herein are the property of their respective owners 9.1.3 Info-Zip unzipSFX stub file is an excluded component. THIRD PARTY LICENSE TERMS AND CONDITIONS, NOTICES AND INFORMATION The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: - the Excluded Components are provided on an "AS IS" basis; - IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE; - IBM will not be liable to you or indemnify you for any claims related to the Excluded Components; and - IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components. UnZipSFX Stub file: The Program includes “UnZipSFX stub” software from the Info-Zip group which is Copyright (c) 1999-2002, Info-ZIP. All rights reserved. IBM did not modify the UnZipSFX software. There are no extra charges or costs due to the use of this code, and the original compression sources are freely available from http://www.info-zip.org/ on the Internet. 9.2 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 for a complete explanation of the terms that apply. 9.3 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: AIX DB2 DB2 Universal Database DB2 Universal Database Enterprise Server Edition IBM 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 2001, 2005; Copyright Rocket Software, Inc., 2001.2005. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.