Quest Centralä version 4

Copyright 2006 Quest Software, Inc. All Rights Reserved.

Quest Central for DB2 Version 4.9.2

Release Notes

Revised: October 2006 These release notes contain information about Quest Central for DB2. For information about installing Quest Central for DB2 version 4.9.2, refer to the following document:

· Quest Central for DB2 Installation Guide You can view the complete library of product documentation at the following location:

http://www.quest.com/db2

For detailed procedures about using Quest Central for DB2, refer to the Quest Central for DB2 online help.

Recent changes in the Release Notes · New features

· Updates to instructions about installing Quest Central for DB2 as a stand-alone product

· Instructions for updating the LOADLIB for Quest Central for DB2 for z/OS

· Information about running Quest Central for DB2 as part of QDMS

· New bug fixes

http://www.quest.com/db2

Quest Central for DB2 Release Notes 2

Contents

Overview ......................................................................................................................................... 5 What is new in this release .............................................................................................................. 5

Integration with QDMS............................................................................................................... 5 Features previously introduced in version 4.9.1.............................................................................. 5

Integration with Spotlight on DB2 for LUW 5.0.1...................................................................... 5 Ability to monitor multiple instances from your console ........................................... 5 Granular control of multiple-partition monitoring...................................................... 5 New OS drilldowns..................................................................................................... 5 Support for SSH on Unix............................................................................................ 6 Automatic historical data collection feature ............................................................... 6 Enhanced Alarm Log .................................................................................................. 6 Enhanced graph and chart control............................................................................... 6 Connection profile enhancements............................................................................... 6

Spotlight on DB2 for z/OS support for DB2 for z/OS version 8................................................. 6 Features previously introduced in version 4.9.0.............................................................................. 6

Support for DB2 for LUW version 8.2........................................................................................ 6 Support for mixed-case and special characters in object names.................................................. 6 Real-Time Statistics Advisor for DB2 for z/OS.......................................................................... 7 Integration with Quest SQL Optimizer for DB2 UDB................................................................ 7 Side-by-side installation with other Quest Centrals .................................................................... 7 Latest Knowledge Expert ............................................................................................................ 7

Installing Quest Central for DB2 as a standalone product .............................................................. 7 Installing the Quest Central for DB2 client ................................................................................. 7 Installing the Quest Central for DB2 Agent ................................................................................ 8 Updating the Quest Central for DB2 LOADLIB on z/OS........................................................... 8

Running Quest Central for DB2 as a part of QDMS....................................................................... 9 If you are performing a new installation of QDMS..................................................................... 9 If you already have the QDMS version 2.1 installed................................................................... 9 If you have an pre-2.1 version of QDMS installed...................................................................... 9 Running Quest Central for DB2 from the QDMS console.......................................................... 9

Installing Spotlight for DB2 for LUW version 5.0........................................................................ 10 System requirements ..................................................................................................................... 10

Client requirements ................................................................................................................... 10 Database support ....................................................................................................................... 10 Quest Central for DB2 Agent requirements .............................................................................. 11

Quest Central for DB2 mainframe requirements........................................................................... 11 Licensing requirements for Spotlight ............................................................................................ 11 Global operation of Quest Central for DB2 .................................................................................. 11 DB2 for LUW version 8/version 7 compatibility issues ............................................................... 12

SQL Analysis............................................................................................................................. 12 Database Administration ........................................................................................................... 12 Space Management.................................................................................................................... 13 Spotlight .................................................................................................................................... 13


IBM issues affecting Quest Central for DB2................................................................................. 13 Additional DB2-related issues for Spotlight ............................................................................. 15

For DB2 for LUW version 7 databases..................................................................... 15 For DB2 for LUW version 8 databases..................................................................... 15

Additional DB2-related issues for SQL Analysis...................................................................... 15 Additional DB2-related issue for Database Administration...................................................... 15

Other known issues affecting Quest Central for DB2 in general .................................................. 16 Quest Central for DB2 scripts containing EXPORT statements ............................................... 16 Backup operations ..................................................................................................................... 16 DB2 for LUW Backup/Restore considerations ......................................................................... 16 Native DB2 for z/OS utility scripts ........................................................................................... 16 SOC4 ABENDS when running SYNCSORT in DB2 for z/OS ................................................ 16 Browse Data menu item in DB2 for z/OS ................................................................................. 17

Other known issues in Database Administration for DB2 for LUW............................................. 17 Compare Wizard Optional Object Properties page ................................................................... 17 LOAD command and servers with multiple database partitions ............................................... 17 Generation of EXPORT, IMPORT, and LOAD commands ..................................................... 17 Windows that support drag and drop......................................................................................... 17 Exporting or importing DATALINK columns.......................................................................... 18

Other known issues in Database Administration for DB2 for z/OS.............................................. 18 Compare Wizard Optional Object Properties page ................................................................... 18 Generation of REORG UNLOAD and LOAD utilities............................................................. 18 Windows that support drag and drop......................................................................................... 18 Migrating tables that contain LOB data .................................................................................... 18

Other known issues in Space Management for DB2 for LUW ..................................................... 18 Database application heap ......................................................................................................... 18

Other known issues in Space Management for DB2 for z/OS ...................................................... 19 Generated template name incompatibility with remote native IBM utility jobs ....................... 19

Other known issues in SQL Tuning for DB2 for LUW ................................................................ 20 Error generated when processing recommended virtual indexes .............................................. 20

Other known issues in SQL Analysis for LUW ............................................................................ 20 Deadlock events exhibit erroneous information........................................................................ 20 Quest Central for DB2 version incompatibility......................................................................... 20 Potential data loss ...................................................................................................................... 20 LOCKTIMEOUT configuration parameter requirement........................................................... 20 Page requirement for running a DB2 event monitor ................................................................. 20 Required authorities................................................................................................................... 20 Kernel change required for enabling asynchronous I/O on AIX 4.3 ......................................... 21

Other known issues in Spotlight on DB2 for LUW....................................................................... 22 DB2 issues ................................................................................................................................. 22 Record feature recommendations .............................................................................................. 22 DB2 snapshot access for users without appropriate authority................................................... 22

Enhancements for Quest Central for DB2 version 4.9.2 ............................................................... 22 Enhancements for Quest Central for DB2 version 4.9.1 ............................................................... 22

4.9.1 enhancements for Database Administration ..................................................................... 22 Enhancements for Quest Central for DB2 version 4.9.0 ............................................................... 23

4.9.0 enhancements for Database Administration ..................................................................... 23 4.9.0 enhancements for SQL Analysis ...................................................................................... 23


Bug fixes for Quest Central for DB2 version 4.9.2 ....................................................................... 23 4.9.2 bug fixes for Quest Central for DB2 in general................................................................ 23 4.9.2 bug fixes for Database Administration............................................................................. 23 4.9.2 bug fixes for Space Management ..................................................................................... 24

Bug fixes for Quest Central for DB2 version 4.9.1 ....................................................................... 24 4.9.1 bug fixes for Quest Central for DB2 in general................................................................ 24 4.9.1 bug fixes for Database Administration............................................................................. 24 4.9.1 bug fixes for Space Management ..................................................................................... 25 4.9.1 bug fixes for SQL Tuning................................................................................................. 25

Bug fixes for Quest Central for DB2 version 4.9.0 ....................................................................... 25 4.9.0 bug fixes for Quest Central for DB2 in general................................................................ 25 4.9.0 bug fixes for Database Administration............................................................................. 26 4.9.0 bug fixes for Space Management ..................................................................................... 26 4.9.0 bug fixes for SQL Tuning................................................................................................. 27 4.9.0 bug fixes for SQL Analysis .............................................................................................. 27

Contacting Quest Software............................................................................................................ 28 Contacting Quest Support.............................................................................................................. 28 Disclaimer ..................................................................................................................................... 29


Overview These Release Notes describe the new features in Quest Central for DB2 version 4.9.2, specify the latest requirements for running Quest Central for DB2, describe known issues and workarounds having to do with installation, help files, and operating system platforms, and provide a list of corrected customer issues.

What is new in this release

Integration with QDMS Quest Central for DB2 version 4.9.2 has integrated with Quest Database Management Solutions (QDMS). QDMS provides a console environment from which you can explore and use the capabilities of the Quest Software products available for each of your RDBMSs—such as SQL Server, Oracle, Sybase, and now DB2.

From the QDMS console, you can launch Quest Central for DB2, Knowledge Xpert for DB2, Quest Central for DB2 SQL Tuning, or Spotlight on DB2 for LUW.

Features previously introduced in version 4.9.1

Integration with Spotlight on DB2 for LUW 5.0.1 Quest Central for DB2 now integrates fully with Spotlight on DB2 for LUW version 5.0.1 when you open a Spotlight session on a DB2 for LUW version 8 database in Quest Central for DB2. (The classic Spotlight on DB2 for LUW version 4.9.1 is still launched when you are using a DB2 for LUW version 7 database.)

The 5.0.1 version of Spotlight on DB2 provides the features described below.

Ability to monitor multiple instances from your console With Spotlight on DB2 for LUW versions 4.9.1 and earlier, you open a Spotlight monitoring session on a single DB2 instance, thereby limiting the DB2 databases that you could monitor to databases on that instance only. With the 5.0.1 version, you can now monitor DB2 databases and database partitions on multiple DB2 instances during your Spotlight session. When you select a connection to a database or database partition from the Spotlight browser, Spotlight automatically attaches to the instance containing that system. When you switch your monitoring focus to a connection for another database or database partition in the browser, Spotlight then attaches to the instance for that connection.

Granular control of multiple-partition monitoring A new facility, the Spotlight Connection Manager, lets you set up a connection to a specific DB2 for LUW database or to a single partition for that database. (You no longer have to set up a connection for a database in order to monitor its partitions individually.)

New OS drilldowns

This version of Spotlight integrates with Spotlight on Windows and Spotlight on Unix to provide a home-page-style drilldown to monitor the Windows, Linux, or Unix operating system in which the DB2 database server is running. (Spotlight on Windows and Spotlight on Unix are automatically installed as part of your Spotlight on DB2 for LUW version 5.0.1 installation.)


Support for SSH on Unix

Spotlight on Unix supports the SSH (secure shell) protocol for connecting to Unix operating systems. (Spotlight on DB2 for LUW version 5.0.1 integrates with Spotlight on Unix to monitor the Unix operating system in which a DB2 database server runs.)

Automatic historical data collection feature

Historical data is now collected on a continuous basis while a connection is open. You no longer have to start and stop a recording to collect this information. To view historical data, you simply select a collection period from the history browser to play back home-page and drilldown events that appear to be happening live, even though they took place days, weeks, or even months ago.

Enhanced Alarm Log Spotlight offers several new ways to view the alarms on the Alarm Log—for example, by any given connection, by all connections, and by alarm duration. Additionally, the Alarm Log rule system has been enhanced to include where…is not criteria and more customization features for actions.

Enhanced graph and chart control Spotlight provides more options to customize graphs and charts on drilldowns. For example, you can modify the graph line style, choose to display either lines or area-fills in a graph, select colors for the various chart and graph components, or zoom in on a part of a graph to magnify specific information (the graph axes are adjusted).

Connection profile enhancements

The type of Spotlight monitoring that takes place for each connection to a DB2 database and database partition is now controlled by a profile that you define for that connection. A connection profile not only provides the information needed to connect to the specific DB2 database or database partition you want to monitor but also controls what will be monitored during that connection. For example, each profile sets DB2 monitor switches and turns on or off the SQL Archiver and operating system monitoring to determine the kinds of data collected each time that connection is opened in Spotlight.

Spotlight on DB2 for z/OS support for DB2 for z/OS version 8 Spotlight on DB2 for z/OS now supports DB2 for z/OS version 8, including Unicode and long-name support.

Features previously introduced in version 4.9.0 The following features were introduced in Quest Central for DB2 version 4.9.0.

Support for DB2 for LUW version 8.2 Quest Central for DB2 now supports for DB2 for LUW (Linux, Unix, and Windows) version 8.2 (also known as version 8.1.7) and later. The Quest Central for DB2 functionality—including Migration, Compare and Synchronize, and Extended Alter—supports the catalog columns and values introduced in this version of DB2.

Support for mixed-case and special characters in object names A Quest Central for DB2 client preference is available to allow mixed-case and special characters (such as blanks) in the database object names. When this preference is enabled, all object names entered through the Quest Central for DB2 client are automatically enclosed in quotations prior to any SQL or command execution.


Real-Time Statistics Advisor for DB2 for z/OS The Real-Time Statistics Advisor provides various views of the statistics that IBM DB2 for z/OS’s own real-time statistics facility collects on tablespaces and index spaces. The Advisor lets you set statistic thresholds that trigger alerts when utilities (such as REORG, COPY, and RUNSTATS) need to be run on objects.

Integration with Quest SQL Optimizer for DB2 UDB If you have Quest SQL Optimizer for DB2 UDB installed, you can click the Optimize button on the SQL tab in your Quest Central for DB2 SQL Tuning session (for DB2 for LUW) to launch an SQL optimization process on your current tuning scenario. SQL Optimizer automatically generates every possible SQL alternative that produces the same results set as the SQL in your scenario. SQL Optimizer then benchmarks these alternatives to determine which tuned version performs best in your database environment.

Note: SQL Tuning’s integration with Quest SQL Optimizer is available only if you have installed Quest SQL Optimizer for DB2 UDB version 2.8.0 or later.

If you want to download SQL Optimizer for DB2 UDB, go to the following location:

http://www.quest.com

Provide your Quest Central for DB2 license key as the license key for SQL Optimizer.

Side-by-side installation with other Quest Centrals Version 4.9 of Quest Central for DB2 allows side-by-side installation with any Quest Central for Oracle, SQL Server, and Sybase versions or previous standalone versions of Quest Central for DB2. For information about installing Quest Central for DB2 version 4.9, refer to the Quest Central for DB2 Installation Guide.

Latest Knowledge Expert This version of Quest Central for DB2 includes the Knowledge Expert for DB2 version 5.2.0.

Installing Quest Central for DB2 as a standalone product

Installing the Quest Central for DB2 client If you have a pre-4.9 version of Quest Central for DB2 client installed on your machine (or you want to install the client for the first time), the installation wizard launches a new installation for the 4.9.2 client. Refer to the instructions in the Installing Quest Central on the Client Machine chapter in the Quest Central for DB2 Installation Guide.

If you already have a 4.9 or 4.9.1 version of the Quest Central for DB2 client installed on your machine, the installation wizard performs a version 4.9.2 client maintenance installation, allowing you to do any of the following:

· Upgrade the client to version 4.9.2

· Add new Quest Central for DB2 components

· Remove currently installed components

· Re-install client files to resolve an installation problem

Follow the Installation maintenance instructions in the Installing Quest Central on the Client Machine chapter in the Quest Central for DB2 Installation Guide.

http://www.quest.com


NOTE: You can now have Knowledge Expert running during the Quest Central for DB2 installation. Previously, if Knowledge Expert was running during an installation, the installation failed.

Installing the Quest Central for DB2 Agent Whether you are performing a new installation of the Quest Central for DB2 Agent on your database server or you are upgrading an existing 4.9 or 4.9.1 version of the Agent to version 4.9.2, refer the Installing the Quest Central for DB2 Agent chapter in the Quest Central for DB2 Installation Guide for instructions.

NOTE: If you already have a 4.9 or 4.9.1 version of the Quest Central for DB2 Agent installed on your database server, the installation wizard guides you through an Agent upgrade. If you have a pre-4.9 version of the Agent installed on the database server, the installation wizard launches a new Agent installation.

Updating the Quest Central for DB2 LOADLIB on z/OS This release contains a change to a Quest Central for DB2 for z/OS module. To take advantage of this change, you must re-create the Quest Central for DB2 LOADLIB. This update involves transferring an xmi file from Quest Central for DB2 client installation directory to the mainframe and expanding the PDS/E for the LOADLIB.

NOTE: Create the LOADLIB a new PDS/E. However, if you decide to copy the updated LOADLIB to the existing PDS/E containing the current Quest Central for DB2 LOADLIB, back up the current LOADLIB before completing the following steps.

To update the LOADLIB for Quest Central for DB2 for z/OS:

1. Allocate a sequential file on the mainframe using the following attributes: RECFM=FB

LRECL=80

BLKSIZE=3120

2. Use FTP or an IND$FILE transfer to copy OS390/loadlib.xmi (located in the folder or directory in which the Quest Central for DB2 client is installed) to the sequential file you set up in step 1. Transfer the file in binary mode.

3. At a TSO command prompt, type the following: TSO RECEIVE INDATASET (‘sequential.file.name’)

4. At message INMR906A, type the following: DATASET(‘loadlib.name’)

The variable ’loadlib.name’ is either the name of the new PDS/E or the name of the old LOADLIB you are replacing, depending on whether you created a new PDS/E or are using the existing LOADLIB.

5. If you chose to receive the xmi dataset into a new PDS/E, do the following:

· Change WLM procedures, QPDSNAT, and QPAGENT procedures to reflect the new load library name.

· APF-authorize the new LOADLIB.


Running Quest Central for DB2 as a part of QDMS If you want to run Quest Central for DB2 within the Quest Database Management Solutions (QDMS) environment, you need to do the following:

1. Install Quest Central for DB2. 2. Install, upgrade, or update QDMS.

If you are performing a new installation of QDMS To perform a new installation of QDMS:

· From the Quest Central for DB2 4.9 installation CD-ROM, run the executable located in the Common Components directory.

Or

1. Download the Quest Database Management Solutions console component from the following location: http://www.quest.com/downloads/?requestdefid=4564

2. Navigate to the directory or folder where you downloaded the component, and run the executable in this directory or folder to install QDMS.

3. After the installation is complete, double-click the Quest Database Management Solutions icon on your desktop to launch QDMS.

4. From the Quest Database Management Solutions window, select View | Check for Installed Products to add Quest Central for DB2 to the console.

If you already have the QDMS version 2.1 installed If you already have QDMS version 2.1 installed, you need to run a search feature within QDMS that looks for newly installed products.

To update your currently installed QDMS version 2.1:

1. Start QDMS. 2. From the Quest Database Management Solutions window, select View | Check

for Installed Products to add Quest Central for DB2 functionality to the console.

If you have an pre-2.1 version of QDMS installed If you have a pre-2.1 version of QDMS installed on your machine, uninstall this product, and follow the instructions in If you are performing a new installation of QDMS to install version 2.1 of QDMS.

Running Quest Central for DB2 from the QDMS console To run Quest Central for DB2 from the console:

1. From the QDMS console, highlight the DB2 node in the Databases section. 2. Click the appropriate icon or link on the QDMS console to open Quest Central for

DB2 or to start a separate Quest Central for DB2 SQL Tuning, Spotlight on DB2 for LUW version 5.0.1, or Knowledge Xpert for DB2 session.

http://www.quest.com/downloads/?requestdefid=4564


Installing Spotlight for DB2 for LUW version 5.0 At the end of the Quest Central for DB2 installation (or upgrade), you are given the option to install stand-alone Spotlight for DB2 for LUW version 5.0. This latest version of the stand-alone Spotlight integrates with Quest Central for DB2, allowing you to monitor DB2 for LUW version 8 databases.

If you select the option to install this version of Spotlight and you already have a Spotlight for DB2 version 5.0 installed on your client machine, the Simple option made available during the installation process removes the existing version 5.0 Spotlight, but does not install the 5.0.1 version. You should install the 5.0.1 version by manually executing SoUDB_Installer.exe found in your Quest Central for DB2 installation folder. You can also install this version of Spotlight by using the Repair option in your Quest Central for DB2 installation. For instructions on using the Repair option, refer to the Installation maintenance section in the Installing Quest Central on the Client Machine chapter in the Quest Central for DB2 Installation Guide.

System requirements Verify that your system meets the following minimum requirements.

Client requirements The Quest Central for DB2 client requires the following:

· Microsoft Windows 2000, 2003, or XP

· 256 MB RAM

· 160 MB of free hard-disk space (approximately 312 MB if you are installing Knowledge Xpert and Spotlight on DB2 for LUW version 5.0.1)

· IBM DB2 for LUW (Linux, Unix, and Windows) version 7.2 Runtime Client or later

NOTE: Quest Central for DB2 requires a DB2 for LUW version 8.1 Runtime Client when running against a DB2 for LUW version 8.1 64-bit server.

· IBM DB2 Connect version 7.2 or later (required for z/OS support)

Database support Each database that Quest Central manages or monitors can be any of these versions:

· IBM DB2 for Linux, Unix, and Windows (LUW) Enterprise Server Edition (ESE) version 8.1 or later (32-bit or 64-bit)

NOTE: A minimum IBM DB2 for LUW version of 8.1 (with FixPak 1 applied) required for Spotlight and SQL Analysis

· IBM DB2 for Linux, Unix, and Windows (LUW) Enterprise Edition (EE) or Extended Enterprise Edition (EEE) version 7.2 (32-bit) or later

NOTE: A minimum IBM DB2 for LUW version of 7.2 (with FixPak 8 applied) required for Spotlight and SQL Analysis

· IBM DB2 for z/OS version 7 or 8


Quest Central for DB2 was tested in DB2 for z/OS version 8 Compatibility Mode (CM) and is fully supported in this mode. Quest Central for DB2 was also tested against DB2 for z/OS version 8 Enable New Function Mode (ENFM) and New Function Mode (NFM) and works in these environments as long as no new DB2 functionality, except for the Unicode catalog, is enabled or exploited. At this time, Quest Central for DB2 supports ENFM and NFM in DB2 for z/OS version 8 as follows:

· Spotlight on DB2—Fully supports both modes as of Quest Central for DB2 version 4.9.1 · SQL Tuning—Fully supports both modes as of Quest Central for DB2 version 4.8.2 · Quest Central for DB2 in general—Fully supports both modes as of Quest Central for

DB2 version 4.9.1 with the limitation described above · Other product or mode combinations—Not supported

Quest Central for DB2 Agent requirements The Quest Central for DB2 Agent runs on any of these operating system platforms:

· Microsoft Windows 2000, 2003, or XP

· Sun Solaris 7 or later

· IBM AIX 4.3 or later

· SuSE Linux Enterprise Server 8 and 9 for IBM mainframes

· SuSE Linux Enterprise Server 8 and 9 United Linux for Intel x86

· Red Hat Enterprise Linux AS 2.1, 3.0, and 4.0 for Intel x86 NOTE: You must install the compat-libstdc++-7.3-2.96.122.i386.rpm

compatibility library. You will find this package on the RedHat Advanced Server 3.0 installation CDs.

Refer to the Quest Central for DB2 Installation Guide for more detailed system requirement information, including recommended DB2 maintenance levels.

Quest Central for DB2 mainframe requirements · IBM z/OS version 1.4 or later

Licensing requirements for Spotlight If you install Spotlight on DB2 for LUW version 5.0 for integration with Quest Central for DB2, you must obtain two license keys:

· A Quest Central for DB2 license key

· A stand-alone Spotlight on DB2 for LUW license key

If you previously purchased a stand-alone version of the classic Spotlight on DB2 for UDB version 4.7 or Spotlight on DB2 for LUW version 5.0, you can continue to use the licensing key that you obtained for that version of Spotlight.

Global operation of Quest Central for DB2 This section contains information about installing and operating this product in non-English or non-ASCII configurations, such as those needed by customers outside the USA. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.


This product was not enabled and was not tested for international operation. Only U.S. English configurations of this product and U.S. English datasets are fully supported. Support for non-ASCII characters and/or non-English configurations might work appropriately, but these configurations have not been tested and this product should be used with caution in these environments. For specific support information, contact Quest customer support.

DB2 for LUW version 8/version 7 compatibility issues Quest Central for DB2 version 4.9.2 operates with severe limitations in an environment in which a DB2 for LUW version 8 Runtime Client is run against DB2 for LUW version 7 instances. Refer to your IBM DB2 UDB V8.1 Release Notes, Part I, Back-Level Server Support for a complete list of inter-version incompatibility issues.

Quest Central for DB2 version 4.9.2 operates properly in these environments:

· A DB2 for LUW version 7 client is run against version 7 instances.

· A DB2 for LUW version 8 client is run against version 8 instances.

· A DB2 for LUW version 7 client is run against version 8 instances, with the exceptions described in the following sections for specific Quest Central for DB2 components.

· A DB2 for LUW version 8 client is run against version 7 instances, with the exceptions described in the following sections for specific Quest Central for DB2 components.

SQL Analysis The SQL Analysis component does not support the collection of SQL on a DB2 for LUW version 8 database when you are using a DB2 for LUW version 7 database as the SQL Analysis Repository. The repository must be a DB2 for LUW version 8 database. When SQL Analysis attempts to run a SQL collection in this unsupported configuration, SQL Analysis shuts down and displays the following message:

SQC70353E SQL Analysis agent was unable to start a SQL Analysis collection. SQL Analysis agent found the managed database incompatible versions 'version number' and 'version number' respectively. Please migrate the repository database to a DB2 version compatible with the managed database or use the SQL Analysis Repository Manager to select a repository database with a DB2 version compatible with the managed database.

Database Administration The Database Administration component behaves unexpectedly under the following two circumstances.

First, running a DB2 for LUW version 7 client against a DB2 for LUW ESE version 8 instance that spans multiple partitions can cause the Tablespace, Database, and Database Configuration windows in Database Administration not to open as expected. This situation can also cause -1198 SQL codes to occur.

Secondly, running a DB2 for LUW version 8 client against a version 7 instance causes unpredictable behavior when you select to run Database Administration functions from pop-up menus for existing objects:

· The Index, Procedure, Table, Trigger, Function, and View windows do not open. The SQL035IN message is returned.


· The Tablespace, Database Configuration, and Instance Configuration windows do not open. The SQL165IN message is returned.

· The Database window does not open. The message DBA00011E is returned, indicating that the database information could not be retrieved.

Space Management Running a DB2 for LUW version 8 client against a version 7 instance causes unpredictable behavior when you select to run Space Management functions from right-click menus for existing objects:

· The Rebuild Index window does not open. The SQL035IN message is returned.

· The Table Load and Reorg windows do not open. The SQL165IN message is returned.

Spotlight Running a DB2 for LUW version 7 client against DB2 for LUW version 8 instances causes the following behaviors in the Spotlight component.

· A version mismatch message is displayed under Instance Identification on the Spotlight instance-level home page.

· External storage information, all database configuration parameters, and all information based on these configuration parameters (including the Page Cleaners and Prefetchers information on the database and partition home pages, as well as certain data on the Tablespaces drilldown) are disabled.

· All sub-drilldowns on the Tablespaces drilldown are disabled.

IBM issues affecting Quest Central for DB2 The following chart details known IBM DB2 for LUW versions 7 and 8 issues that affect the various components in Quest Central for DB2.

APAR # APAR descriptions Fix Affected component

JR14929 TABLE UDFs (OLEDB or SQL) that are defined via CREATE FUNCTION command to return DECIMAL(x,y) will show LENGTH=0 and SCALE=0 in the SYSCAT.FUNCPARMS table.

Version 7, FixPak 2

Database Administration

IY30686 INSTANCE CRASH WITH SIGNAL 11 IN SQM_EVMON.

Version 7, FixPak 9

SQL Analysis

JR18098 RUNNING THE INDEX ADVISOR FROM A VERSION 7 CLIENT AGAINST A VERSION 8 DATABASE CAUSES THE DATABASE TO CRASH.

Version 7, FixPak 9

SQL Analysis

SQL Tuning


APAR # APAR descriptions Fix Affected component

IY45245 Entries will be logged in the db2diag.log, stating 2003-03-27-14.33.38.666141 instance:db2lxb Node:0000 PID:6472(db2agent(LXB)) Appid: "LOCAL.db2lxb.03032719338 access_plan_manager sqlra_rollup_dyn_stmt Probe:20 Database Statement not protected!

Turning off the monitor switch for the statement stops this behavior, but doing so results in Spotlight not displaying any SQL statements.

Version 7, FixPak 10

Spotlight

JR18739 Databases on DB2 for LUW version 8.1 (with FixPaks 1 through 4 applied) generate deadlock events that show a zero lock-wait start time.

Version 8, FixPak 5

SQL Analysis

IY57306 LIBRARY-ID NOT BEING STORED IN SYSTEM CATALOG TABLES FOR OLE STORED PROCEDURES

Version 8, FixPak 7b

Database Administration

IY76570 THE DB2 UDB INSTANCE MAY CRASH AFTER A TRAP IN THE FUNCTION LOAD_DCS_APPLID_INFO. THIS HAPPENS MORE ON WINDOWS THAN ON OTHER PLATFORMS… The crash occurs when the Event Monitor is trying to access an application that has not fully initialized or is in the process of terminating. In either case, the application client’s SETI pointer is NULL.

Version 8, FixPak 11

Spotlight

PMR 86905 When you record more than one DB2 for LUW database at a time, the Record feature returns data for only one tablespace. Additionally, you must have the Tablespaces drilldown open for this database as you record.

No fix as yet

Spotlight

PMR 68754.756

In DB2 for LUW version 8 ESE (multiple-partition) environments, you might experience some counters that show negative numbers. This is an intermittent problem, primarily affecting statistics counters in the Client Applications and Databases drilldowns.

No fix as yet

Spotlight


Additional DB2-related issues for Spotlight The following DB2-related issues for Spotlight have not yet been resolved.

For DB2 for LUW version 7 databases When you launch Spotlight on a DB2 for LUW version 7 database, the following issues might exist:

· Various time fields are corrupted by accessing the File | Reset Monitor Statistics feature in Spotlight. CPU times affected include agent_sys_cpu_time and agent_usr_cpu_time.

· The Monitor Switches window in Spotlight causes other DB2 for LUW instance-level counters to reset. This is true when the Monitor Switches window is invoked automatically at startup or when the user selects File | Options | Monitor Switches. The Spotlight Options | Update Monitor Switches API shows intermittent failure in DB2 for LUW EE version 7.2 systems. To correct this issue, apply DB2 for LUW version 7.2 FixPak 6.

For DB2 for LUW version 8 databases

The following issue might exist when you launch Spotlight on a DB2 for LUW version 8 database:

The Percent of Max component shown on the Client Apps panel of the database and partition home pages might show inconsistent percentage values. These inconsistencies occur because DB2 can control the maxappls database configuration parameter. The default setting of Automatic for this parameter in DB2 means that DB2 dynamically assigns resources as needed to support new applications.

It is recommended that you turn off the default alarm for the metric behind the Percent of Max component in Spotlight on DB2 for LUW version 5.0 or greater. Refer to the Spotlight online help for details on disabling the capture of a specific metric or on disabling the metric thresholds that can generate alarms.

Additional DB2-related issues for SQL Analysis The following DB2-related issues have not yet been resolved:

· When SQL Analysis runs a DB2 event monitor against a multiple-partition instance in DB2 for LUW version 7.1 (with FixPak 4 or FixPak 5 applied) on a Solaris machine, the instance can hang or crash. Upgrade to DB2 for LUW version 7.1 FixPak 6 or later to resolve this problem.

· Databases on DB2 for LUW version 7.1 FixPak 7 and later (and version 8.1 and later) truncate dynamic SQL statement text in a DB2 event monitor when deadlock monitoring is enabled. The truncated statement text displays in SQL Analysis with three consecutive periods (...) at the end. To avoid the truncation, clear the Collect Deadlocks option on the Create Collection window in SQL Analysis to disable deadlock monitoring.

Additional DB2-related issue for Database Administration DB2 for LUW version 7.1 users must have the version 7.1 FixPak 4 (or later) installed. This FixPak contains a fix that prevents an instance from becoming unusable when you attempt to configure DB2 for LUW version 7.1 databases.


Other known issues affecting Quest Central for DB2 in general

Quest Central for DB2 scripts containing EXPORT statements When a Quest Central for DB2 script containing one or more EXPORT statements is executed remotely on an AIX machine, you might see the following message:

mkdir: 0653-357 Cannot access directory...

: A file or directory in the path name does not exist.

You can safely ignore this message. Your EXPORT statements will continue to execute normally. If you need to verify that your script executed successfully, check the .log file in the following location:

[Questhome]/[Hostname]/Jobs/[jobname]/[jobname].log

where [Questhome] is the directory where Quest Central for DB2 is installed, [Hostname] is the name of the machine that is running the agent, [jobname] is the directory for the job, and [jobname].log is the name of the log file.

Backup operations Backup operations before and after a table REORG on a DB2 for LUW EEE or ESE (on multiple partitions) database are not supported in this release.

DB2 for LUW Backup/Restore considerations Note the following:

· When executed in an EEE or multiple-partition ESE environment, the DB2 BACKUP command is run against a single partition. You must ensure that each partition is backed up individually.

· When restoring a database in an EEE or multiple-partition ESE environment, you must ensure that all partitions of the database have valid backups. For more detail, refer to Chapter 8 of the IBM DB2 Universal Database Administration Guide: Implementation, version 7.

Native DB2 for z/OS utility scripts Scripts that use templates generated by Quest Central for DB2 version 4.0 or later for native DB2 for z/OS utilities must be regenerated by Quest Central for DB2 version 4.8 (or later) before they can be executed. Any script containing a #DELIM statement generated by earlier versions must be regenerated by the 4.8 (or later) version before it can be executed.

SOC4 ABENDS when running SYNCSORT in DB2 for z/OS Users running SYNCSORT in the WLM environment receive ABENDS0C4 errors when DSNUTILB calls SYNCSORT. To fix this problem, users can contact SYNCSORT to obtain a tape that contains support for DB2 stored procedures. This fix applies some ZAPs to the current SORT modules and then creates a new SORT stub and aliases to a new reentrant module SYNCFNI. The documentation accompanying the tape provides instructions for applying the fix.


Browse Data menu item in DB2 for z/OS If you right-click a DB2 for z/OS table, view, or alias and select Browse Data, the SQL Editor displays the data. The SELECT statement that retrieves the data references each column in the object. (You can view this statement on the SQL tab.) However, if you are running with the DB2 for LUW version 8 Runtime Client, the SELECT statement might contain SELECT * instead of actual object column names. If you want all object columns referenced in the SELECT statement, you must apply DB2 for z/OS APAR PQ62695—Add stored procedures and views for use by ODBC and JDBC drivers.

NOTE: This APAR (PQ62695) affects the SELECT statement only, not the select results. The results will always show all of the columns in the object.

Other known issues in Database Administration for DB2 for LUW

Compare Wizard Optional Object Properties page The Comparison of Optional Object Properties page of the Compare Wizard has been changed. This page allows you to adjust the comparison process by designating the object properties you do not want to be compared. Not selecting a given property means that it will not be compared. If the property is selected, it will be compared. In previous releases, selecting a property meant that the property would not be compared.

LOAD command and servers with multiple database partitions Database Administration can generate LOAD statements when needed in extended alters, migrations, and compares. However, because only the IXF format is supported, LOAD cannot be used for tables that reside on more than one database partition. If this case is detected, IMPORT, instead of LOAD, will automatically be used to load the data.

Generation of EXPORT, IMPORT, and LOAD commands In most cases, Database Administration assumes that a table has data even if it does not. For example, if an EXTENDED ALTER is done on a table, the process will always execute an EXPORT statement, a CREATE statement, and an IMPORT/LOAD statement. The exceptions to this rule are as follows:

· The Keep data when altering database objects option in DB2 settings is off.

· The table has an identity column. If there is no data in the table, the table will not be unloaded or reloaded.

· The table has a LOB column. If there is no data in the table, the table will not be unloaded or reloaded.

· Changing any part of the column data type or the not null attribute. If there is no data in the table, the table will not be unloaded or reloaded.

Windows that support drag and drop Some Database Administration windows support the reordering of a list via drag and drop. If a list of items supports the drag-and-drop functionality, you should drag and drop your items only within the window list itself. If you drag an item onto the list of objects in the console, an access violation might occur and Quest Central for DB2 will have to be restarted.


Exporting or importing DATALINK columns The Database Administration component does not support the exporting or importing of DATALINK columns from or into a table. This limitation might cause problems when you perform an extended alter or migrate a table that contains a DATALINK column.

Other known issues in Database Administration for DB2 for z/OS

Compare Wizard Optional Object Properties page The Comparison of Optional Object Properties page of the Compare Wizard has been changed. This page allows you to adjust the comparison process by designating the object properties you do not want to be compared. As of this release, not selecting a given property means that it will not be compared. If the property is selected, it will be compared. In previous releases, selecting a property meant that the property would not be compared.

Generation of REORG UNLOAD and LOAD utilities As of this release, in most cases, Database Administration assumes that a table has data even if it does not. For example, if an EXTENDED ALTER is performed on a table, the process executes a REORG UNLOAD statement, a CREATE statement, and a LOAD statement. The exceptions to this rule are as follows:

· The Keep data when altering database objects option in DB2 settings is off.

· The table has an identity column. If there is no data in the table, the table will not be unloaded or reloaded.

· Changing any part of the column data type or the not null attribute. If there is no data in the table, the table will not be unloaded or reloaded.

Windows that support drag and drop Some Database Administration windows support the reordering of a list in the window via drag and drop. If a list of items supports the drag-and-drop functionality, you should drag and drop your items only within the window list itself. If you drag an item onto the list of objects in the console, an access violation might occur and Quest Central for DB2 will have to be restarted.

Migrating tables that contain LOB data Migration erroneously allows you to migrate DB2 for z/OS tables that contain LOB columns with data. The UNLOAD and LOAD of table data with LOB columns is not supported. You must edit the generated script for it to run successfully. Contact Technical Support for more information.

Other known issues in Space Management for DB2 for LUW

Database application heap In situations where there is a small database application heap size, you might receive the following error message:

SQL0954C Not enough storage is available in the application heap to process the statement. SQLSTATE=57011

In these cases, the returned result list might be incomplete.


To remedy this problem, you can increase the applheapsz database configuration parameter using either of these methods:

· Right-click the database in the Quest Central for DB2 object tree and select Configure from the right-click menu. When the Configure Database window opens, select the applheapsz parameter from the list, and click Edit. Enter a larger value in the Edit Configuration Parameter window, and click OK. On the Configure Database window, click Build Script. When the SQL Editor opens, execute the script.

Or

· Open the SQL Editor from the Quest Central for DB2 tool bar. When the SQL Editor opens, enter this script in the upper pane on the SQL tab: #ATTACH DB2;

UPDATE DATABASE CONFIGURATION FOR databasename USING applheapsz nnnn;

DETACH;

where databasename is the name of the database and nnnn is a larger value than the one currently assigned to applheapsz for this database. Execute the script.

Other known issues in Space Management for DB2 for z/OS

Generated template name incompatibility with remote native IBM utility jobs In situations where you generate a native IBM utility script using the Quest Central for DB2 version 3.1.1 client, save it to a remote subsystem, and run it on an MVS subsystem on which the Quest Central for DB2 version 4.8.1 or later mainframe components are installed, the job will fail with a syntax error. In order for native IBM utility jobs to run on a Quest Central for DB2, version 4.8.1 or later mainframe installation, template names must adhere to the convention of an equal sign and three opening parentheses, followed by the template name, three closing parentheses, and an equal sign: =(((<template name>)))=

Template syntax may be changed either from the Mainframe Job Review page of the Remote Job wizard on a Quest Central for DB2 version 3.1.1 client or in the member containing the job, after you use FTP to transfer it to the mainframe.


Other known issues in SQL Tuning for DB2 for LUW

Error generated when processing recommended virtual indexes The Virtual Index facility in SQL Tuning makes use of IBM's special registers. When you are running the Virtual Index facility from a DB2 for LUW version 7.1 client (with FixPaks 1 through 8 applied) against a DB2 for LUW version 8 server, the version 8 server database might crash. The crash is related to the use of the special registers in this specific environment. The issue is fixed in FixPak 9. See IBM APAR JR18098 for more information.

Other known issues in SQL Analysis for LUW

Deadlock events exhibit erroneous information Databases on DB2 for LUW version 8.1 (with FixPaks 1 through 4 applied) generate deadlock events that exhibit a zero lock-wait start time. A fix for this issue is included in DB2 for LUW version 8.1 FixPak 5. See IBM APAR JR18739 for more information.

Quest Central for DB2 version incompatibility For SQL Analysis, Quest Central for DB2 version 4.9 or greater is not compatible with versions 2.x, 3.x or 4.0.0 of Quest Central for DB2. You must install the Quest Central for DB2 version 4.9 client on the client machine and the Quest Central for DB2 Agent version 4.9 on each server. For details on installing Quest Central in these locations, refer to the Installing Quest Central on the Client Machine and Installing the Quest Central for DB2 Agent chapters in the Quest Central for DB2 Installation Guide.

Potential data loss SQL Analysis repositories upgraded to version 4.5 should not be managed by version 2.0, 3.0, or 4.0 Quest Central for DB2 clients. Incompatibilities with these client versions could potentially lead to SQL Analysis collection data loss. Refer to the Installing Quest Central on the Client Machine and Installing the Quest Central for DB2 Agent chapters in the Quest Central for DB2 Installation Guide for more information.

LOCKTIMEOUT configuration parameter requirement Ensure that the LOCKTIMEOUT configuration parameter is set to a value other than -1 for the database in which you are installing the SQL Analysis Repository tables and for the database on which you are collecting data.

Page requirement for running a DB2 event monitor SQL Analysis requires 36 4-kilobyte pages to run an event monitor during a SQL collection process. For more information on setting the mon_heap_sz parameter appropriately for running an event monitor, refer to the IBM DB2 Universal Database System Monitor Guide and Reference.

Required authorities To assign a SQL Analysis Repository to a DB2 instance containing the database on which you intend to run a collection (and to which you are currently connected), you need these authorities:

· The user ID connected to the database requires SYSADM authority.

· The user ID running the Quest Central for DB2 Agent (and related SQL Analysis agents) must belong to the SYSADM group for the instance.


To run a collection on a DB2 database, the user ID connected to this database requires the following authorities and privileges:

· DBADM authority on the database

· SELECT, INSERT, UPDATE, and DELETE privileges on the SQL Analysis Repository tables

Kernel change required for enabling asynchronous I/O on AIX 4.3 SQL Analysis now uses asynchronous I/O to read event monitor files during a collection process. AIX 4.3 requires a kernel change to enable asynchronous I/O. (AIX 5.1 does not require this change because asynchronous I/O is enabled by default.)

To enable asynchronous I/O on an AIX 4.3 machine:

1. Issue the following command to verify that the fileset bos.rte.aio is installed: lslpp -l bos.rte.aio

If this fileset is not installed, see your system administrator to have it installed.

If the fileset is installed, you will receive output similar to this:

Fileset Level State Description

Path: /usr/lib/objrepos bos.rte.aio

4.3.3.0 COMMITTED Asynchronous I/O extension

Path: /etc/objrepos bos.rte.aio

4.3.3.0 COMMITTED Asynchronous I/O extension

2. Use SMIT to issue the following command, which verifies that the aio0 device is available:

smit chgaio

The Change/Show Characteristics of Asynchronous I/O screen is displayed.

3. Check that the State to be configured at system restart option is set to available. · If this option is not set to available, change it to available and continue with

step 4. Or

· If this option is set to available, go on to step 5.

4. Restart the machine. 5. Issue the following command to verify the aio0 state for a final check:

lsdev -C |grep aio

The command should return the following message:

aio0 Available Asynchronous I/O


Other known issues in Spotlight on DB2 for LUW

DB2 issues There are some known DB2 for LUW issues that affect Spotlight. Refer to the Known IBM issues section in these release notes for more information.

Record feature recommendations The following are recommendations for using the record feature in classic Spotlight on DB2 for LUW version 4.9.2:

· Do not set foreground and background refresh rates below 30 - 60 seconds because doing so affects performance.

· When you record more than one database at a time, the record feature can return tablespace data for only one tablespace. You must have the tablespace drilldown open for this database as you record. This is due to an IBM DB2 snapshot issue (PMR 86905).

· When you record a single database, the record feature returns tablespace data without requiring the tablespace drilldown to be open.

DB2 snapshot access for users without appropriate authority In DB2 for LUW version 8.0 and later, users who do not have SYSADM, SYSMAINT, or SYSCTRL authority can access DB2 snapshot data.

To allow access to the snapshot data, the DB2_SNAPSHOT_NOAUTH parameter must be activated. A user with appropriate authority (SYSADM, SYSMAINT, or SYSCTRL) issues the following command and restarts DB2:

db2set DB2_SNAPSHOT_NOAUTH=on

NOTE: Issuing this command causes DB2 to not verify the privileges of the current user when one of the snapshot functions is accessed.

With this authority, some of the Spotlight data and functions will be unavailable. For example, monitor switches cannot be changed, and no data is returned for storage use and tablespaces. Various other sub-drilldowns might also be unavailable, depending on the settings in your particular work environment.

Enhancements for Quest Central for DB2 version 4.9.2 No enhancements were included in Quest Central for DB2 version 4.9.2.

Enhancements for Quest Central for DB2 version 4.9.1 The following enhancements were implemented for Quest Central for DB2 version 4.9.1.

4.9.1 enhancements for Database Administration

Case ID CR ID Enhancement description

345036, 384814 126156

The option has been added to not perform RUNSTATS when the option Do not migrate data is selected for a migration.


Enhancements for Quest Central for DB2 version 4.9.0 The following enhancements were implemented for Quest Central for DB2 version 4.9.0.

4.9.0 enhancements for Database Administration


N/A 14536 Quest Central for DB2 now supports DB2 for LUW version 8.1.2 (and later) database manager and database configuration parameters.

373534 146106 Database Administration now generates a table ALTER instead of a DROP and CREATE after a VARCHAR column is lengthened.

4.9.0 enhancements for SQL Analysis


240666 78127

The online help documents that SQL Analysis windows can show CPU times that are greater than the elapsed times in multi-processor environments in which parallelism is enabled.

367071 143417 SQL Analysis now records the machine name on which a collection actually runs rather than the machine name on which the collection is scheduled.

Bug fixes for Quest Central for DB2 version 4.9.2 The following customer bug fixes were implemented in Quest Central for DB2 version 4.9.2.

4.9.2 bug fixes for Quest Central for DB2 in general

Case ID CR ID Description

440112 181576 The Editing Data window shows an incorrect display format for columns defined as decimal datatypes.

4.9.2 bug fixes for Database Administration


414321 417607 417819 427433 440330 168316

The primary index is being excluded in the DDLs that are generated during the execution of a Migrate, Compare, or Extract DDL.

412373 170215 An error occurs when extracting the DDL for a trigger in a DB2 for z/OS version 8 subsystem running in compatibility mode.

430711 443061 446584 454863 176529 An error occurs when parsing a statement containing the word CASE.


4.9.2 bug fixes for Space Management


370073 428559 146507

A Dr. Watson error is generated when the user attempts to run Calculate Space on a tablespace.




384060 153240 The Increase indent of select lines button copies the first line of text after the cursor position.

397648, 408586 158943 DESCRIBE TABLE command fails in SQL Editor.

405501 162789

Executing various DB2 for z/OS commands in SQL Editor without establishing a connection to the subsystem appear to execute successfully, but the commands actually fail because there is no connection.

378568 165097 Incorrect values display for DB2 for z/OS version 8 buffer pools in the Properties window.

409985 165550 The installation and update DDL scripts for the Quest Central for DB2 mainframe components require a CCSID EBCDIC clause.



338930 123300 During the DDL extraction process on a trigger in DB2 for LUW, the parser is not recognizing the RTRIM keyword in the WHEN clause in the trigger DDL.

399920 164653

For a 64-bit DB2 database on a Windows machine, Quest Central for DB2 performs a DROP and CREATE of a tablespace instead of an ALTER RESIZE when a container size is edited. (This same behavior occurs when the user selects the Extend option for a container in the Alter window.)

409978 165531 In a DB2 for z/OS environment, dropping a plan fails because of delimiter errors in the generated script.

411449, 422102, 426635 165624

In a DB2 for z/OS version 8 environment running in compatibility mode, the Extract DDL function on a view fails because data from the SYSIBM tables is returned in hex format.

418698 170012 Extract DDL run on views generates extra quotes on column names.

413552 170214 Actions performed on triggers that contain the word CURRENT fail.

420167 170844 When you reduce a container size, the ALTER TABLE REDUCE script is built with incorrect values for the size.

418215 172399 During a table alter, the GENERATED ALWAYS AS option in a column definition is incorrectly dropped when the column is updated.



411320, 427466, 430090 176567

An extra delimiter being generated in the script to drop a package is causing the function to fail.

409978, 425143 176568

An extra delimiter being generated in the script to rebind a package is causing the function to fail.



276544, 313018 116342

Batch Analysis reports run against an object list showing zeros and -1s incorrectly in the CARD column.

410192, 415420, 416426, 417507, 422881, 427793, 431376 165971

RUNSTATS and Extract DDL fail on a partitioned tablespace when the tablespace is created without a partition 0.

409744 167209 A REORG with BACKUP options fails with a SQL30082N (PASSWORD MISSING) error.

4.9.1 bug fixes for SQL Tuning


318461, 332482, 332749, 409860 120697

Removed the test execution that is performed when running the Recommend Virtual Index function in SQL Tuning

406648 164195 In a DB2 for z/OS environment, the user is unable to select a tunable SQL statement from a package.




252114 116315 SQL Editor is displaying certain hex values as blanks in table columns.

310285 116338 Some table columns are not properly spaced in the grid showing the results of the Browse Data option.

322652 116009 Display Bufferpool output shows incorrect information when the console command character is a dash.

356842 134007 When the user prints the information on the Results tab in SQL Editor, the printout is not showing the correct number of lines.

370040 153432 A RUNSTATS job that is executing remotely on 4,229 tables fails.



374789 141216 The upgrade process for Quest Central for DB2 mainframe components fails when you are upgrading from 4.8.1 to 4.9.

376986 147747

In the Quest Central for DB2 browser, the Space Allocated column heading should specify (Mb), not (Kb); and the column values should be rounded rather than truncated.

379366 146111 The parser fails on an INSERT statement.

380389 149611

When the results of a Browse Data are copied from SQL Editor to Microsoft Excel, accent marks and circumflexes in the original table data are translated into Chinese characters, unrecognizable characters, or other characters in the Excel document.



289118 95498 The database Compare process fails on a clustered index.

337891 123945 During the Extract DDL process, Quest Central for DB2 is failing to put delimiters (“) around certain column names containing special characters.

349221 129307 The Create Like function for an index is generating a script that lists the columns in an order different from the order specified in the function.

362994 140021 Database Administration needs to support complex trigger generation.

367545 142847 Compare schema process results in a truncation error.

374534 146292 Unformatted text in scripts causes batch jobs to fail.

372245 146482 An error occurs when attempting to view object properties.

381804 150734

When altering multiple containers, the user receives a message stating that container size value entered is less than the minimum required size (even when this is not the case).

381580 151357 A parser error occurs when the user attempts to compare schemas, and the target schema includes a specific materialized query table.

385347 153868

The CREATE PROCEDURE statement generated in a migration script is showing more parameters than are defined in the actual DDL for the stored procedure.

368276 154532 A fatal error occurs on an index during a schema-level compare.

389884 155787 In the Object Customization step of the Migration Wizard, the source indexes’ primary and secondary are not being reported.



376423 133766 The LOAD utility fails because the template for the load input file attempts to create a new file.

370121 144202

In Space Calculator, incorrect totals are shown if you choose to extend a container and if the extended allocation size is specified in units that are different from the units defined for the current container allocation size.



370679 144404 An overflow line in the JCL is causing an error in generated utility jobs.

370631 144410

User wants the Remote Job wizard to pull in the IP address of the MVS system for the FTP process. The Wizard currently pulls in the IP address found in the RESYNC area of the –DIS DDF output.

369974 144457

Quest Central for DB2 templates for utility processing generate characters in the dataset name that are additional to what IBM generates. These additional characters are causing the script to fail. The Quest Central for DB2 templates are also pulling in SSID values that are different from the SSID values that the IBM templates pull in.

371106 144624

The target DBMS values generated in scripts vary depending on whether batch execution is selected and on which blueprint is selected for the job. Basically, if the DB2 Group Attach name is generated as target DBMS, the script fails. Jobs generated with the subsystem ID or the location name run successfully.

376422 147169 Space Management needs to support the tablespace and index space recovery options new to DB2 for z/OS version 7.

376997 147442

When using the Batch Analysis wizard against a DB2 for z/OS subsystem, the user is unable to specify exception criteria thresholds if the user unselects the options to run the REORG and RUNSTATS utilities.

379203 148756

The REORG batch job running against a partitioned tablespace fails when the job has the following conditions: the JCL is generated from the DSNUTILB blueprint, and the job is defined to reorganize selected (not all) partitions.

388811 154306

When the user changes the Number of Rows value on the Table tab in Space Calculator in a DB2 for z/OS environment, the value in the Rows column on the Index tab is not updated accordingly to reflect the change.

4.9.0 bug fixes for SQL Tuning


366501 141209 The execution of a SQL statement containing a correlation name results in the error SQL0206N SQLSTATE 42703.

4.9.0 bug fixes for SQL Analysis


333032 120097

When the user assigns a SQL Analysis Repository database to begin a collection, the following error occurs: SQC05010E: ScAdCom - Error opening the ScCNTRepo result file (d:\db2\QUESTC~1\Agent\db\tmp\OUT3) (rc=2) for read access.

373157 146280

A SQL collection ends with an incomplete status after encountering the same parser error multiple times. (The errors states the following: SQLC70323W Statement parse failed (rc=70015) for statement length exceeds log buffer size…) This error is generated when the SQL in a collection uses schema with a reserved word such as COMMENT.

386517 152814 The parser fails when user.firstname is used as a correlation name.


Contacting Quest Software E-mail [email protected]

Mail Quest Software, Inc.

World Headquarters

5 Polaris Way

Aliso Viejo, CA 92656

USA

Web site www.quest.com

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

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

Visit SupportLink (http://support.quest.com).

Quest Support provides around-the-clock coverage with our web self-service. You can quickly do the following:

· Find thousands of solutions (KB articles/documents)

· Download patches and upgrades

· Seek help from a Support engineer

· Log, update, and check the status of your ongoing case

View the Global Support Guide (http://support.quest.com/pdfs/Global Support Guide.pdf) for a detailed explanation of support programs, online services, contact information and policy and procedures.

mailto:[email protected]

www.quest.com

http://support.quest.com/

http://support.quest.com/pdfs/Global%20Support%20Guide.pdf


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.

Quest Centralä version 4

Documents