Toad for IBM DB2 Release Notes
Total Page:16
File Type:pdf, Size:1020Kb
Toad for IBM DB2 7.1.x Release Notes Monday, November 18, 2019 Contents About Toad for IBM DB2 1 New Features 1 System Requirements 2 Resolved Issues and Enhancements 4 Known Issues 4 Third Party Known Issues 6 Getting Started 7 Toad for DB2 Editions 7 Product Licensing 8 Globalization 8 About Us 9 Copyright 9 About Toad for IBM DB2 With Toad, developers and database administrators can use a familiar, proven tool to manage databases. Toad empowers developers and administrators, of varying skill levels, to rapidly create and execute queries, automate database object management, and develop SQL more efficiently. Toad also provides utilities to compare, extract and search for objects, manage projects, import/export data and administer the database, while increasing your productivity and delivering access to an active user community. Toad for IBM DB2 7.1.2 is a patch release with new features, security enhancements and resolved issues. New Features In Toad for IBM DB2 7.1 the following new features were implemented: Security and Installation Enhancements For this release of Toad for IBM DB2 we have provided internal security adjustments. We have revised a list of third party components in use according to their known and potential vulnerabilities. Toad uses only reliable and safe components by third party vendors. See the list of third party components in Toad for IBM DB2the help file, section About Us | Third Party Components. Our Toad installers are now based on the Wix Toolset , which improves user experience and performance of the installation process. See Resolved Issues for more enhancements and resolved issues in this release of Toad for IBM DB2. Learn More Get the latest product information, find helpful resources, and join a discussion with the Toad for IBM DB2 team and other community members. Join the Toad for IBM DB2 community at Toad World. Toad for IBM DB2 7.1 Release Notes 1 Toad for IBM DB2 7.1.x System Requirements Client Requirements Before installing Toad, ensure that your client system meets the following minimum hardware and software requirements: Requirement Details Platform 2 GHz processor (recommended minimum) Memory 8 GB of RAM minimum, 16 GB recommended Note: The memory required may vary based on the following: l Applications that are running on your system when using Toad l Size and complexity of the database l Amount of database activity l Number of concurrent users accessing the database Hard Disk 800 MB to install Toad Space 162 MB to run Toad Note: The disk space required may vary based on the edition of Toad selected for installation. Operating Windows Server® 2008 R2 SP2 System Windows Server® 2012 Windows Server® 2012 R2 Windows Server® 2016 Windows Server® 2019 Windows® 7 SP1 (32-bit or 64-bit) Windows® 8.1 (32-bit or 64-bit) Windows® 10, version 1809 .NET Microsoft® .NET Framework 4.7.1 Framework Database When connecting to a DB2 database/subsystem, ensure that you have a DB2 Client or IBM Client Data Server Driver installed. Toad supports DB2 Client versions 9.7.6 through 11.1. Toad has been tested with the following versions of the DB2 Client: 9.7.6, 9.7.9 , 10.1.0, 10.1.2, 10.1.3, 10.5.0, 10.5.2, 10.5.3, and 11.1.0. Additional Web Browser Requirements Microsoft® Internet Explorer® 11 or later Screen Toad supports screen resolutions up to 3200 x 1800 and display DPI settings up to 150% Server Requirements Before installing Toad, ensure that your server meets the following minimum hardware and software requirements: Requirement Details Database Server IBM DB2 for LUW 9.5, 9.7, 10.1, 10.5, 10.5.0.5, 11.1 IBM DB2 for z/OS 10, 11, 12 Note: Toad may support IBM DB2 Express and SWE in addition to listed above servers but note that no testing was performed on it. Note: Windows 8, 10 and Windows Server 2012 require the following Fix Pack in order to ensure registration of DLLs in Global Assembly Cache: Toad for IBM DB2 7.1 Release Notes 2 Toad for IBM DB2 7.1.x Requirement Details IBM DB2 LUW 10.5 Fix Pack 4 IBM DB2 LUW 10.1 Fix Pack 4 IBM DB2 LUW 9.7 Fix Pack 10 Note: To use Access 2016 64-bit to connect to an Access database in Toad, the Microsoft Access Database Engine is required and might not be included in the Access installation. The engine must match the architecture (bitness) of Toad. Virtualization Support Requirement Details Application When deploying Toad in a virtualization environment, for best results ensure the Virtualization system accurately reflects the applicable client hardware and software requirements listed in this document. Toad has been developed using Microsoft guidelines (see Remote Desktop Services programming guidelines) and can be deployed and operated in virtualization environments such as Citrix XenApp, Microsoft App-V, and VirtualBox. See "Install Toad on Citrix Systems" (page 1) for more information. User Requirements User Requirements to Install Toad Only Windows Administrators and Power Users can install Toad. Note: The following exceptions exist for Power Users: l A Power User can install Toad as long as this user belongs to the DB2ADMNS or DBUSERS group. If an Administrator installs Toad, the Administrator can share the Toad shortcut icon on the desktop and menu items with any user—a Power User, Restricted User—on the computer. If a Power User installs Toad, a Restricted User cannot do the following: l Associate file extensions. l View the Toad shortcut icon on the desktop or the Toad menu options in the Windows Start menu. As a workaround, Restricted Users can create a shortcut to Toad from the install directory and place the shortcut on their desktop. User Requirements and Restrictions for Running Toad The following describes the requirements and restrictions for users who launch and run Toad: l A Windows Power User or Restricted User must belong to the DB2ADMNS or DB2USERS group. To add the user to one of these groups, select Start | Control Panel | Administrative Tools | Computer Management | System Tools | Local Users and Groups | Groups | DB2ADMNS or DB2USERS. l A Windows Power User or Restricted User does not have the authority to add or remove DB2 catalog entries using the Toad Client Configuration wizard. However, these users can use the Import Profile function in the Toad Client Configuration wizard to import catalog entries to Toad. l To take full advantage of Toad for DB2 LUW functionality, the user ID specified in the Toad connection profile for each DB2 for LUW database connection requires the authorizations listed in the following document: ToadDB2LUWAuthorizations.xls l As a minimum requirement to manage a DB2 for z/OS subsystem in Toad, the user ID defined in the Toad connection profile for the subsystem must either have SYSADM privileges or SELECT privileges on the DB2 catalog tables. For a complete list of authorizations (and corresponding GRANT statements) a user requires to take full advantage of Toad for DB2 z/OS functionality, refer to the following document: ToadDB2zOSAuthorizations.doc Toad for IBM DB2 7.1 Release Notes 3 Toad for IBM DB2 7.1.x l To create or modify the QuestSoftware.ToadSecurity table to enable Toad Security, the user who maintains this table must have privileges to create, insert, update, and delete it. All other users need only the ability to read the QuestSoftware.ToadSecurity table to use Toad Security features. l For information about defining a RACF, Unix, or Linux group as a Toad Security role, see the About Setting Up Toad Security topic in the Toad online help. This topic explains how to add the Toad Security icons to your toolbar and how to define Toad Security roles that apply to your current connection. (The ability to define RACF, Unix, and Linux groups as Toad Security roles works with DB2 for LUW 9 or later databases and DB2 for z/OS 8 or later subsystems.) Resolved Issues and Enhancements The following is a list of issues addressed and enhancements implemented in this release of Toad for IBM DB2: Resolved Issues in 7.1.2 Feature Resolved Issue / Enhancement Defect ID Dimensional We have improved work with calculated fields and aggregate values in QAT-15139 Viewer Dimensional Viewer General Collation property while importing data using Automation script has been QAT- modified to improve performance with certain JOINS on Tables 15314/4572415 SQL Editor AutoCommit on IBM DB2 connections now works as designed TDB-3950/ 4576728 Team Publishing a script with different schemas from the same database now QAT- Server works correctly 15319/4534571 Resolved Issues in 7.1 Feature Resolved Issue / Enhancement Defect ID Code Completion Dragging and dropping column names from Object QAT-15117 Explorer to Editor now works correctly. Object Details (DOV) We fixed an issue in the DB2 z/OS Subsystem - Right- TDB-3943/454799 Hand-Side Dynamic Statement Cache tab where a DB2 error was being thrown when a DSC table was selected if that table creator began with an @. Pivot Grid Pivot Grid now allows you to use Aggregated data values QAT-14558/4415769 in a calculated field. Query Builder You now can select LAG and LEAD in the list of functions QAT-14252/4438857 for calculated fields in Query Builder. SQL Editor Highlighting keyboard shortcuts now work correctly in QAT-15111/4542078, Editor. 4555409, 4559368, 4564671 Known Issues The following is a list of issues known to exist at the time of this release. Feature Description Support Case/Defect ID Object Details When a DB2 object is created, DB2 implicitly creates TDB-870 authority for the user who created that object.