Toad^® for IBM DB2

Beta Version 4.6.0.493

Beta Release Notes

January 27, 2010

Contents

Welcome to Toad for DB2

Toad for DB2 is a database development and administration solution that provides productivity features for rapidly creating and executing queries, automating database object management, developing SQL code, and instant access to DB2 expertise.

Developers and administrators have access to a community of users, peers, and experts to help solve development and administration issues and assist in developing applications and feedback for improving Quests products.

All of this comes with the backing of Quest Software, a healthy and growing corporate entity that can provide the necessary training, support, and superior customer service demanded by IT management.

Back to Top

New in This Release

The Toad for DB2 4.6 Beta will be introducing new features, enhancements and fixes throughout the Beta cycle.

• For a description of customer issues resolved in this release, see Resolved Issues and Enhancements.

Features and Updates in Toad for DB2 4.6 Beta

Click to review the updates and new features in the following areas:

• Prerequisites and Installation
• General Toad Environment and Functionality
• Database Administration
• Space Management
• Data Management
• Query Development

Back to Top

Prerequisites and Installation

• Toad ships and installs IBM DB2 for LUW Client 9.7 as the DB2 client. The new default location for the DB2 client is C:\Program Files\ Toad for DB2 Beta 4.6\SQLLIB.

Back to Start of Section

Back to Top

General Toad Environment and Functionality

• You can increase screen real-estate in Toad by pressing SHIFT+ALT+ENTER or selecting View | Full Screen from the menu to hide the default toolbars and display Toad in full screen mode.

• In full screen mode, you can toggle back to your previous screen size and displayed toolbars by clicking Full Screen beside the menu.

• Toad has introduced the ability to categorize connections and also apply a coloring scheme to allow you to easily identify what connection you are working with. To enable this feature, navigate to Tools | Options | Database | General and check the "Show category in explorer and object editors" checkbox:

• You can assign a category on your connections:

• Toad will then shade its features with category colors to allow for easy identification.

• We removed the Database Explorer toolbar and added toolbar buttons on the Explorer toolbar.

Back to Start of Section

Back to Top

Database Administration

Click a category in the list to view the features and updates for this release:

• Object Explorer

• Object Management - General

• Object Management - DB2 for LUW

• Object Management - DB2 for z/OS

• Utility Execution - DB2 for z/OS

• Quest IBM DB2 z/OS Component

Object Explorer

• The LUW DBM Parameters and DB Parameters were moved from the Database Explorer tree to right-hand-side tabs on the database object.  See below Object Management - DB2 for LUW section for screen shots.

• Toad now allows you to share object filters by allowing you to export and import them.  To export your filters on the database explorer select the dropdown on the schema filter control as shown below:

• Other Toad users with the same Database connection defined can import and use those filters.  To import those filters in Toad, use File | Open File to open the tpf (Toad filter pack) file:

Object Management - General

• Now within the View Editor you can launch Query Builder to easily build and maintain your queries:

• When you have completed building your query you can send it back to the View Editor:

• Toad introduces new permission editors that make it easy for you to grant/revoke privileges on multiple database objects for users, groups, and LUW Roles.  You can use "Create Like" to easily clone permissions:



• Object Editors and Utility Editors now execute scripts on a background thread allowing you to drive other features in Toad when long running scripts are being executed.

Object Management - DB2 for LUW

• On the Database - Applications tab, you can now send Dynamic SQL statements to the SQL Editor or SQL Optimizer for tuning:

• The DBM Parameters and Database Parameters are now in right-hand-side tabs on the Database.



• The DB Parameters can be view in Tabbed view or in Side-by-Side view.

• Side-by-side view allows you to see and easily set parameters for all nodes:

• Registry Variables are displayed in a tab on the right-hand-side of the Database.  For DB2 LUW v9.7, you can view the details of the new DB2_COMPATIBILITY_VECTOR:

• For LUW v9.7, Cataloged Global Temporary Tables are now displayed in the Database browser

 

• Toad includes support for new datatype/attributes introduces in LUW v9.7 including precision for Timestamp columns and Inline Lengths for LOB and XML columns.

• For DB2 LUW v9.7 indexes, the new Compress attribute can be specified.

 

• We have added new launch-points (on the database object in the database browser and on the monitor tab) to launch Spotlight and SQL Analysis:

• We have added additional features at the DB2 LUW Database level, including Activate, Deactivate, Quiesce and Unquiesce.  We modified the Tools menu to reflect these additions:

Object Management - DB2 for z/OS

• Toad now includes a options to create copies of your data during the loading of data to remove any COPY-PENDING statuses.

Utility Execution - DB2 for z/OS

Note: Many of the z/OS Admin features require that you have the Quest IBM DB2 z/OS Components installed on the DB2 z/OS subsystem. This Beta will operate with the GA version 4.5 components, so if you already have those installed you are fine.  See the Quest IBM DB2 z/OS Component Installation Guide for more information.

Quest IBM DB2 z/OS Component

The Quest IBM DB2 z/OS Components are required to manage your DB2 for z/OS subsystems.  There have been no changes made to the Quest IBM DB2 z/OS Components since version 4.5, so if you already have those installed there is no need to install them again.

Space Management DB2 LUW

• Toad now has a new Tablespace Freespace Exceptions report:



 

• We removed the top 'filter' panel from all exception reports to be able to show more details and we added highlighting to the "Stats Time" column to identify old statistics.

• All actions can now be accomplished via a right-click popup menu.

• A new "Details" tab has been added to the Database Space Usage Report.  This tab allows you to view summary and detailed container pages sizes across partitions and tablespaces.

Back to Start of Section

Back to Top

Data Management

Click a category in the list to view the features and updates for this release:

• Export Wizard

• Import Wizard

Export Wizard

• Toad now has support for exporting directly to Excel 2007 and 2010.

 

Import Wizard

• Several enhancements have been made to the Import wizard.  The wizard now allows you to specify a discard file.  Rows failing to import will be written to that discard file.

• Error messages stating the row(s) in error will be displayed on the Import Error window:

• The "Import data summary results" now displays a link to the discard file.

Back to Start of Section

Back to Top

Query Development

Click a category in the list to view the features and updates for this release:

• Query Builder

• Editor

• Debugger

Query Builder

• When opening a previously saved Query Builder file, you can right-click the Diagram pane and select Refresh to get the latest objects from the database.

Editor

• When saving an Editor file where Group Execute is enabled, Toad defaults to saving the file as a Toad Editor File (.tef). If you save as this file type, the selected group, the selected connections, and query are saved.  (When you are saving the file, you can choose to save the script as a sql file only as well.)

• Toad now shows how many Group Execute targets are selected and provides a new "Merge result sets" option:

• Files are now added to the Recent Files list when you drag them into the Editor.

• The "Pivot Grid & Chart" tab now allows you to display the Chart at the side or bottom:

• Selecting "Chart Horizontal" in the above picture will move the chart to the bottom as shown below:

• We reintroduced (by popular demand) the ability to rename Editor tabs, via a right-clicking or F2 on the tab:

• We have introduced support for generating PL/I formatted SQL:

• When running scripts with Host variables, the Type column on the "Bind Variables" window now displays the type associated with the column/variable:

Debugger

• We are introducing our support of new DB2 LUW v9.7 features.  This beta now supports the new Oracle-like datatypes such as NUMBER, VARCHAR2, BOOLEAN as well as new logic control statements such as LOOP, CASE, and IF/THEN.

Back to Start of Section

Back to Top

Under Construction

The following areas are under construction and should be avoided in this drop:

• None at this time

Back to Top 

Resolved Issues and Enhancements

Resolved Issues and Enhancements in 4.6 Beta

The following is a list of issues addressed and enhancements implemented in the current release:

Back to Start of Section

Back to Top

Known Issues

The following is a list of issues known to exist at the time of the Toad for DB2 release.

Back to Start of Section

Back to Top

Third-Party Known Issues

The following is a list of third party issues known to exist at the time of the Toad for DB2 release.

Back to Start of Section

Back to Top

Upgrade and Compatibility

Please review upgrade information in the Toad for DB2 Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

Back to Top

System Requirements

Verify that your system meets the requirements described in the following sections:

• Client Requirements

• Server Requirements

• User Requirements

• Citrix Requirements

• LDAP Requirements

• Compile and Debug Requirements for Stored Procedures

• Requirement for Capturing Container Information in a DB2 for LUW Multi-Partition Database

• Requirements for Using Toad DB2 for z/OS Functionality

• Recommended Indexes to Improve Toad Performance in DB2 for z/OS

• Requirements for Object Migration

• Version Control Requirements

Back to Top

Client Requirements

Toad for DB2 client installation requires the following.

Note: If a DB2 for LUW 7 client is installed on the machine where you are installing Toad, you must upgrade the DB2 client to version 8 before installing to avoid losing functionality in some DB2 native tools.

Back to Start of Section

Back to Top

Server Requirements

Toad supports any of these DB2 and operating system versions.

Back to Start of Section

Back to Top

User Privilege Requirements

The following are user requirements for installing and running Toad:

User Requirements to Install Toad

Only Administrators and Power Users can install Toad.

Note: The following exceptions exist for Power Users:

• A Power User cannot install Toad on a computer running Windows Vista Enterprise. This is a Windows limitation because Vista does not support Power User mode.
• (DB2 only) A Power User cannot install Toad if a DB2 for LUW version earlier than 8.1.7 already exists on the computer. Only an Administrator can install Toad under this condition. However, if the computer has an existing DB2 for LUW 8.1.7 or later installation, 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, Vista standard user--on the computer.

If a Power User installs Toad, a Restricted User cannot do the following:

• Associate file extensions.
• View the Toad shortcut icon on the desktop or the Toad menu options on 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:

• 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).
• A Windows Vista user must be either an administrator or a standard user that belongs to a Vista Administrators group. Additionally, to enable full functionality in Toad when Vista’s User Access Control security feature is turned on, the standard user must run Toad as an administrator. (Right-click the Toad icon on the Vista desktop, and select Run as administrator.)
• 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, this user can use the Import Profile function in the Toad Client Configuration wizard to import catalog entries saved to an file (via the db2cfexp command) into the Toad client catalog.
• 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:

  http://www.toadsoft.com/toaddb2/ReleaseNotes/Beta/ToadDB2LUWAuthorizations.xls

• As a minimum to manage DB2 for z/OS subsystems in Toad, the user ID specified in the Toad connection profile for a specific subsystem must either have SYSADM privileges or be granted 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:

  http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadDB2zOSAuthorizations.doc

• To run Toad, the .NET security policy must be set to Unrestricted. To modify the security policy:

1. Select Control Panel from the Windows Start menu.
2. Double-click Administrative Tools.
3. Double-click Microsoft .NET Framework version Configuration.
4. Select My Computer, and then select the Runtime Security Policy node.
5. Select Evaluate Assembly from the list of tasks in the right panel.
6. In the File field, locate and select Toad.exe.
7. Click Next, and set the permission to Unrestricted.

• 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.
• 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.)

Back to Start of Section

Back to Top

Citrix Requirements

Toad has been tested for Citrix support on Windows Server 2003 Enterprise Server (Service Pack 2) using the Metaframe Access Suite 4.0 and Citrix Presentation Server Clients 10.2. For information about installing Toad in a Citrix environment, refer to Install Toad on Citrix Systems in the Toad for DB2 Installation Guide.

Back to Start of Section

Back to Top

LDAP Requirements

To connect to a Lightweight Directory Application Protocol (LDAP) server, you must enable LDAP support and specify the host name and port number of the LDAP server for the DB2 client installed with Toad.

Note: Keep the following mind:

• You must configure LDAP support for the DB2 client installed with Toad regardless of whether an existing DB2 client on the machine is already configured to support LDAP.
• Currently, Toad for DB2 supports only access to DB2 LDAP catalog entries. Toad does not support the management of these entries.

To configure Toad to use LDAP

1. Open the Command Window for the DB2 client installed with Toad by selecting Start | All Programs | IBM DB2 | <ToadCom, ToadEval, or ToadFree> | Command Line Tools | Command Window.
2. Type the following command to enable LDAP support:

db2set DB2_ENABLE_LDAP=YES

3. Type the following command to specify the TCP/IP host name and port number of the LDAP server:

db2set DB2LDAPHOST=hostname[:port]

The port number defaults to 389 (default LDAP port) if you leave the port number blank.

4. Exit the Command Window.
5. Launch Toad and open the Connections window.

Databases on the LDAP server should now be available from the Database Alias drop-down list in the Connections window. To complete the Toad connection setup, you must create a Toad profile for each database. See Create Toad Connection Profiles in the Toad for DB2 Installation Guide.

Back to Start of Section

Back to Top

Requirement for Capturing Container Information in a DB2 for LUW Multi-Partition Database

Certain Toad functions use the DB2 snapshot monitor to capture information about containers used in DB2 for LUW databases. To capture this information for a multi-partition database, the snapshot monitor requires that all database partitions be active. Therefore, to ensure that Toad obtains container information across all partitions, execute the DB2 command ACTIVATE DATABASE real_database_name on the server before connecting Toad to the database. This command keeps all partitions on the database active. For more information about ACTIVATE DATABASE, refer to the IBM DB2 for Linux, Unix, and Windows documentation.

Back to Start of Section

Back to Top

Compile and Debug Requirements for Stored SQL Procedures

The following are the requirements for using Toad to compile and debug stored SQL procedures.

DB2 LUW Requirements

• Debugging stored procedures is available on DB2 LUW v9 and greater.
• The IBM SYSPROC.DBG procedures need to be installed and operational.
• Privileges
  • Execute authority is required on all SYSPROC.DBG_% procedures.

DB2 Subsystem Requirements

Each DB2 subsystem on which you want to compile and debug stored SQL procedures must meet these requirements:

• To compile stored SQL procedures in Toad, the DB2 stored procedure SYSPROC.DSNTPSMP must be operational on the subsystem.
• To debug stored SQL procedures in Toad, the IBM DB2 installation job DSNTIJSD must be executed on the subsystem.
• Only the unified debugger is supported with this release of Toad.  This means that the IBM SYSPROC procedures starting with SYSPROC.DBG need to be installed and operational in your subsystem.
• The IBM Unified Debugger Session manager must be installed and configured on z/OS.
• For DB2 z/OS V8
  • PTF UK25860 is required.
  • The debugger session manager, db2udsmd, must be installed and configured (see IBM's Information on Debugger Session Manager for details)
  • Start task db2udsmd with the default port number, 4553.
• For DB2 z/OS V9
  • The debugger session manager, db2udsmd, must be installed and configured (see IBM's Information on Debugger Session Manager for details)
  • Start task db2udsmd with the default port number, 4553.
• Privileges
  • Execute authority is required on all SYSPROC.DBG_% procedures.
  • The DEBUGSESSION system privilege is required for continued debugging of SQL procedures.

Back to Start of Section

Back to Top

Requirements for Using Toad DB2 for z/OS Functionality

• To perform any of the following functionality in Toad, you must have Quest IBM DB2 z/OS Component 4.5 or greater installed on your DB2 for z/OS subsystems:

  • Bind and rebind DB2 for z/OS packages and plans

  • Invoke DB2 for z/OS utilities and commands within scripts that Toad for DB2 advanced alters, migrations, and synchronizations generate

  • Run stand-alone DB2 for z/OS utilities and commands in Toad

  • Run DB2 for z/OS commands from the Editor

  • Execute remote DB2 for z/OS scripts

  • Create, alter, or drop dataset templates

  • Run Display, Start, and Stop commands on DB2 for z/OS databases, tablespace, and indexes

  • Access accurate buffer-pool information for the DB2 subsystem

  • View volumes available for defining storage

  • Access information about current threads connected to the DB2 subsystem

  • Assign a RACF group to a Toad Security role to control the Toad features available to all users belonging to the RACF group.

If you currently have the Quest IBM DB2 z/OS component version 4.5 installed on your DB2 subsystem, you can use those with the 4.6 Beta.

If the Quest IBM DB2 z/OS component version 4.5 installation does not currently exist on your DB2 subsystem, perform a new installation of Quest IBM DB2 z/OS Component 4.6. Use the instructions found in the Quest IBM DB2 z/OS Installation Guide (available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation).

• The IBM stored procedure SYSPROC.DSNUTILU must be installed and operational on each DB2 subsystem on which you are executing DB2 utilities. For additional information about SYSPROC.DSNUTILU, refer to Appendix B of the IBM DB2 Universal Database for z/OS Utility Guide and Reference.

Note: A 32K character-size limit exists for each utility statement executing through DSNUTIILU.

• When Toad generates an ALTER script that contains multiple UNLOADs and LOADs of table data, ensure that the DSN values in the dataset templates include a &SEQ variable to create unique dataset names.
• When Toad migrates data from one subsystem to another, Toad invokes the IBM DB2 for z/OS UNLOAD and LOAD utilities. The definition for Reorg Unload dataset template should define a dataset that resides on a pack (VOLSER) that is accessible by both the source and target subsystem.

Back to Start of Section

Back to Top

Recommended Indexes to Improve Toad Performance in DB2 for z/OS

User-defined indexes on specific system catalog tables can improve performance when you are browsing DB2 for z/OS objects in Toad. The following link contains the DDL for indexes that can optimize Toad performance on your DB2 for z/OS subsystem. Keep in mind that the creation of these indexes is a recommendation only. The indexes can have different results in different environments, depending on the number of DB2 objects and the amount of data involved. To create these indexes, edit and run the DDL contained in the following file:

http://www.toadsoft.com/toaddb2/ReleaseNotes/Latest/ToadDB2zOSIndexes.txt

Additionally, if the schema drop-down lists in the Object Migration wizard populate slowly, consider creating an index on the SCHEMA and CREATOR columns in the catalog table for each object type. Here is a list of some of the object-type tables:

SYSIBM.SYSSYNONYMS
SYSIBM.SYSSEQUENCES
SYSIBM.SYSROUTINES
SYSIBM.SYSTABLES
SYSIBM.SYSDATATYPES
SYSIBM.SYSINDEXES
SYSIBM.SYSTRIGGERS
SYSIBM.INDEXES

Back to Start of Section

Back to Top

Requirements for Object Migration

The following are specifications for using Toad's Object Migration wizard to migrate DB2 objects and their dependencies:

• You cannot migrate objects between a DB2 for LUW and DB2 for z/OS platform and vice versa.
• Unexpected results can occur if you map two source schemas to the same target schema, and the two source schemas contain same-named objects (for example, if you map both source Schema A and source Schema B to target Schema C, and Schema A and Schema B both contain a table with the name Table1).

Back to Start of Section

Back to Top

Version Control Requirements

Supported Providers

Toad for DB2 supports the following version control providers for the versions and platforms listed. Testing is not complete for versions and platforms not listed:

Configuration Prerequisites

You must configure Toad to work with your existing version control system. Ensure that you install the following on the same computer where you installed Toad.

Note: Toad connects to your version control system based on login information included in your configuration. Your version control client does not need to run for Toad to connect.

Back to Start of Section

Back to Top

Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Far-East Asia, Japan.

However, this release has the following known capabilities or limitations:

• During the Toad for DB2 installation process, if the user overrides the default installation path, the new path specification cannot contain Unicode characters. This limitation exists because Toad installs a DB2 for LUW client in the specified Toad installation path, and DB2 installations do not support Unicode characters.
• (Applies ONLY to the Xpert edition of Toad for DB2 for z/OS and to the DBA edition of Toad for DB2 for LUW or z/OS) The Toad SQL Tuning for DB2 z/OS, Toad SQL Analysis for DB2 LUW, and Toad Remote Script Execution (for DB2 LUW or z/OS) features support single-byte character sets only. These features do not support double-byte or multi-byte character sets. All DB2 client and server installations should be configured to use the same or compatible character encodings and the same locale and regional options.

Back to Top

Getting Started

Contents of the Release Package

The Toad for DB2 Beta package contains the following products:

• Toad for DB2 4.6 Beta
• Quest IBM DB2 z/OS Component 4.6
• Product documentation, including:
  • On-line help

Installation Instructions

For important information about installing Toad for DB2, refer to the Toad for DB2 Installation Guide available from the Windows Start menu under Program Files | Quest Software | Toad for DB2 | Documentation.

Installation Instructions for Additional Components

This Beta will work with the commercial GA versions of the following components.  To install other Toad DB2 commercial components, please refer to the following documentation.

Back to Start of Section

Back to Top

For More Information

Contacting Quest Software:

Refer to our Web site for regional and international office information.

Contacting Quest Support:

(Commercial and Trial Support only)

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.

Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com/.

From SupportLink, you can do the following:

• Quickly find thousands of solutions (Knowledgebase articles/documents).
• Download patches and upgrades.
• Seek help from a Support engineer.
• Log and update your case, and check its status.

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.

Yahoo Group

(Freeware Support)

You can join the Toad for DB2 discussion group by sending an email to: toad_db2-subscribe@yahoogroups.com

Back to Start of Section

Back to Top

© 2010 Quest Software, Inc.
ALL RIGHTS RESERVED.

This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

If you have any questions regarding your potential use of this material, contact:

Refer to our web site for regional and international office information.

Trademarks

Quest, Quest Software, the Quest Software logo, Aelita, Akonix, Akonix, AppAssure, Benchmark Factory, Big Brother, ChangeAuditor, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, GPOAdmin, I/Watch, Imceda, InLook, IntelliProfile, InTrust, Invertus, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, MessageStats, NBSpool, NetBase, Npulse, NetPro, PassGo, PerformaSure, Quest Central, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, vAnalyzer, vAutomator, vControl, vConverter, vEssentials, vFoglight, vMigrator, vOptimizer Pro, vPackager, vRanger, vRanger Pro, vReplicator, vSpotlight, vToad, Vintela, Virtual DBA, VizionCore, Vizioncore vAutomation Suite, Vizioncore vEssentials, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.

Back to Top