Quest Central® for IBM DB2

Version 5.0.2

Release Notes

June 2008

Contents

Welcome to Quest Central for DB2

New in this Release

Resolved Issues and Enhancements

Known Issues

 Third Party Known Issues

Upgrade and Compatibility

 System Requirements

Global Operations

Getting Started

For More Information

Welcome to Quest Central for DB2

Quest Central for DB2 is an integrated suite of tools for managing DB2 on Linux, Unix, Windows, and z/OS. Quest Central provides complete database administration, SQL tuning, space management, and performance diagnostics across all platforms from a single console.

These Release Notes contain an overview of new features, list the known issues, and describe requirements for this release of Quest Central for DB2. For complete information about installing Quest Central for DB2 v5.0, refer to the Quest Central for DB2 Installation Guide. (The Installation Guide is available from the Windows Start menu under Program Files | Quest Software | Quest Central for DB2 v5.0.)

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.

Back to Top

New in This Release

New in 5.0.2

This release contains the following enhancement:

For a list of resolved issues, refer to the Resolved in 5.0.2 section of Resolved Issues and Enhancements.

Features and enhancements introduced in 5.0.1

This release contains no new features but does resolve several issues, as listed in the Resolved in 5.0.1 section of Resolved Issues and Enhancements.

Features and enhancements introduced in 5.0.0

The following features and enhancements are included in Quest Central for DB2 v5.0:

Back to Top

Resolved Issues and Enhancements
 

Resolved in 5.0.2

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

Component

Resolved Issue/Enhancement

Case ID
Change Request ID

General Extracting DDL for DB2 9.5 tables no longer generates errors. Case#601848
CR#46,374
Database Administration The online help for the Compare wizard has been revised to make information about the result types (including the ? for those objects that exist on both the source and the target, but whose DDL is not explicitly generated in the Compare script) more evident in the F1 help topic. Case#307923,
Case#529986
CR#45,229
CR#211174
Spotlight on DB2 for z/OS Spotlight now calculates and displays the correct number of volumes in the External Storage component on the home page for DB2 for z/OS subsystems. Case 601818-1
CR#47,911

 

Resolved in 5.0.1

The following is a list of issues addressed and enhancements implemented in Quest Central for DB2 5.0.1:

Component

Resolved Issue/Enhancement

Case ID
Change Request ID

General The data defined with the REAL data type is now displaying properly in the SQL Editor window when you select Browse Data. Case#481400
CR#203284
(DB2 for LUW only) SELECT...GET_ROUTINE_OPTS execution following a call to SET_ROUTINE_OPTS is now producing the correct results. Case#571299
CR#227925
Database Administration The online help for the Compare wizard now explains that objects listed with a ? in the results are those that exist on both the source and the target, but whose DDL is not explicitly generated in the Compare script. For example, these objects might be indexes that the system implicitly generates for constraints such as primary keys. Case#307923,
Case#529986
CR#211174
(DB2 for z/OS only) When you alter a constraint at the table level, the UNLOAD, CREATE TABLE, and UNLOAD statements are now being generated properly. Case#489456
CR#203103
(DB2 for LUW only) The year and month functions are successfully parsed because the function names are no longer being treated as reserved words. Case#502444
Case#550631
CR#216920
CR#224234
(DB2 for LUW only) The analysis and exception errors that occur when parsing a view during a database Compare are fixed. Case#533460
CR#219922
(DB2 for z/OS only) The parsing error generated when extracting DDL for a view containing !! in the syntax is fixed. Case#542359
CR#221881
(DB2 for LUW only) The CREATE TABLESPACE syntax has been updated to accommodate the tablespace types and type defaults for DB2 for LUW v9. Case#544761
CR#222381
When extracting DDL and permissions for procedures or functions, Quest Central for DB2 now includes the schema with the specific name to query the system catalog. This avoids problems that occur when multiple procedures or functions have the same specific name. Case#550500
CR#223630
(DB2 for LUW only) Procedures and functions on the Alter Permissions window are now listed by their procedure or function names, not by their specific names or system-generated names. Case#556890
CR#224783
(DB2 for z/OS only) By creating the indexes described in the section Recommended Indexes for Improving Migration Performance in DB2 for z/OS, you can improve the speed at which Quest Central for DB2 extracts DDL for the objects selected for migration, especially when these objects exist in a large DB2 for z/OS subsystem. Case#561038
The package extract DDL now excludes the double quotes around the package name. Case#562403
CR#226115
(DB2 for z/OS only) The error generated when attempting to alter an index to remove the CLUSTER option (by deselecting the Cluster index values option) is fixed. Case#565763
CR#228191
The parsing error that was generated when extracting DDL for views in which return column name expressions do not contain AS clauses is fixed. Case#572276
CR#228239
SQL Analysis Issues with Object Setup in Extended Analysis have been resolved. Case#534122
CR#220850
The error generated when parsing SELECT statements with embedded parentheses is fixed. Case#541777
CR#221774
The error generated when parsing DECLARE statements is fixed. Case#574012
CR#228468

 

Resolved in 5.0.0

The following is a list of issues addressed and enhancements implemented in Quest Central for DB2 5.0.0:

Component

Resolved Issue/Enhancement

Case ID
Change Request ID

General (DB2 for LUW) Multiple SQL1009N messages and access violations no longer occur when attempting to display the Configuration window for a database cataloged on a loopback node. A single SQL1009N message is now generated (and the Configuration window does not open). See the information for PMR 23399,756,000 in the Third Party Known Issues section. Case#340178
CR#203480
Quest Central for DB2 handles data-browsing in a more consistent manner for those columns with a large amount of data. Case#392872
Case#402549
Case#477363
CR#156154
(DB2 for LUW) SET command issues that occurred when using SQL Editor to call a stored procedure have been resolved. Case#427599
CR#174905
Selecting text in a script and then clicking elsewhere in the script will unselect the text (as is normal). Case#460964
CR#192497
Invalid syntax in a CREATE statement no longer causes Quest Central for DB2 to fail. Case#535236
CR#219757
(DB2 for z/OS) Space usage information for volumes is now displaying when you create a storage group. Case#537666
CR#205629
Quest Central for DB2 now disallows editing data on objects defined with LONGVARCHAR, GRAPHIC, VARGRAPHIC, BLOB, CLOB, or DBCLOB columns having a length greater than 255. Case#539955

CR#199124

Database Administration (DB2 for LUW) The Migration wizard is no longer generating blank SET SCHEMA and SET CURRENT PATH statements in the migration script. The correct values for these statements are generated. Case#432076
CR#156342
Permissions on procedures and functions are displaying properly for user groups. Case#436531
CR#180118
If you open the Edit Table Column window from the Alter Table window, but make no changes to the column or to the table, the prompt to save pending changes no longer erroneously displays when attempt to close the Alter Table window. Case#460937
CR#191841
If the Properties window is open for a table when you attempt to execute an alter for this same table via the Alter window, the alter process hangs. Case#474230
CR#191978
The LOAD statement generated during a table alter properly indicates column names longer than 18 characters. Case#535260
CR#220172
Space Management (DB2 for LUW) Generating the script for a table REORG that uses TSM as the backup medium no longer results in an SQL0104N error on the BACKUP section of the script. Case#450652
CR#187931
(DB2 for LUW) The Free page % and Free pages fields in Identify Exceptions and Space Calculator are now displaying correct information for an SMS tablespace defined on a partition other than the coordinating partition. (The host name added to DNS or to the etc/hosts file must be the same name found in dbnodes.config at the server for the host.) Case#464267
Case#472006
CR#196656,
CR#198560
(DB2 for LUW) When TSM is selected as the backup medium type for a table REORG, a blank Options field on the Backup tab of the Reorg Tables window no longer generates an error in the script. Case#484460
CR#188066
(DB2 for z/OS) Space Calculator no longer generates an incorrect script after altering the space on an object with multiple partitions. Case#537575
CR#220351
(DB2 for z/OS) Batch utility jobs with scripts containing comments are no longer failing. This fix requires that the Quest for DB2 LOADLIB be updated. See the Getting Started section. Case#541981
CR#196376
SQL Analysis SQL0104N error messages no longer generate in the qsdbg.log file for SQL Analysis extended analysis jobs. Case#522130
Case#547296
CR#215666
SQL Tuning (DB2 for LUW) The parsing error involving DO as a correlation name has been resolved. Case#468268
CR#194960
The Print window now displays after the SQL Tuning Print Options window to allow you to select a printer. Case#520700
CR#214266

Back to Top

Known Issues

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

Component

Known Issue

Change Request ID

Installation

The Quest Central for DB2 agent installation process on a Windows machine is not stopping the services for previously installed Quest Central for DB2 agents.

Workaround:
Manually stop the services for any previously installed Quest Central for DB2 agents on the Windows machine before installing the new agent.

 CR#222841
General

(DB2 for LUW) 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.

 N/A

(DB2 for LUW) The Browser pane in the Quest Central for DB2 Explorer displays the status Unknown for any tablespace that is not defined on the default (coordinating) partition (usually 0) in a multi-partitioned database. This status is displayed because Quest Central for DB2 connects only to the default partition to obtain the tablespace status. If the tablespace is not defined on the default partition, the status is shown in the Browser pane as Unknown.

Workaround:
Access the Space Calculator component in Quest Central for DB2 to view the actual status of the tablespace.

 N/A
(DB2 for z/OS) Scripts that use templates generated by Quest Central for DB2 v4.0 or later for native DB2 for z/OS utilities must be regenerated by Quest Central for DB2 v4.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. N/A

(DB2 for z/OS) If you right-click a 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 v8 Runtime Client, the SELECT statement might contain SELECT * instead of actual object column names.

Workaround:
If you want all object columns referenced in the SELECT statement, 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.

 N/A
Database Administration Certain 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. N/A

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 DB2 for LUW table, the process will always execute an EXPORT statement, a CREATE statement, and an IMPORT/LOAD statement. If an extended alter is performed on a DB2 for z/OS table, the process executes a REORG UNLOAD statement, a CREATE statement, and a LOAD statement.

The exceptions to this assumption 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.
  • (DB2 for LUW only) The table has a LOB column. If no data exists in the table, the table will not be unloaded or loaded.
  • 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.
 N/A
(DB2 for LUW) 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. N/A
(DB2 for LUW) 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 on or migrate a table that contains a DATALINK column. N/A
(DB2 for z/OS) Migration erroneously allows you to migrate 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 Quest Support for more information. N/A
Space Management (DB2 for LUW) In a DB2 ESE multiple-partitioned environment, backup operations before and after a table REORG are not supported in this release. N/A
(DB2 for LUW) In a DB2 ESE multiple-partitioned environment, the BACKUP utility can run against only a single partition. You must ensure that each partition is backed up individually. N/A
(DB2 for LUW) When restoring a database in a DB2 ESE multiple-partitioned environment, ensure that all partitions of the database have valid backups. For more detail, refer to Chapter 8 in the IBM DB2 Universal Database Administration Guide: Implementation. N/A

(DB2 for LUW) Because of the new DB2 directory structure and the default permissions granted to the directories in DB2 v9, SPM00580W errors might be generated in Identify Exceptions and Space Calculator for objects in SMS tablespaces.

Quest Central for DB2 testing shows that when DB2 v9 is running on the server and the client is running DB2 v8.1.7 or later, CREATE DATABASE creates two directories instead of one. For example, if you create the database SAMPLE, DB2 creates two directories—SAMPLE and SQL00001. By default, TEMPSPACE is created as an SMS tablespace in the new SAMPLE directory.

The permissions for the SAMPLE directory default to 700, allowing only the instance owner to have access to the directory and its SMS tablespaces, including TEMPSPACE and any other SMS tablespaces created in this directory.

Workaround:
To avoid generating the SPM00580W errors for the SMS tablespaces in all such directories on the DB2 instance, run the Quest Central agent (QcAgent) as the instance owner.

If more than one DB2 instance exists on the server and the SPM00580W errors occur, run a separate QcAgent for each instance. Each QcAgent must run under the instance owner ID. Additionally, a separate port is required for each DB2 instance. To assign the port numbers, refer to the section, Changing the Port Numbers for the Quest Central for DB2, on page 5-45 in the Quest Central for DB2 Installation Guide.

N/A

(DB2 for LUW) 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.

Workaround:
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.
  • 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 and execute it:

#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.

 N/A

(DB2 for z/OS) If you generate a native IBM utility script using the Quest Central for DB2 v3.1.1 client, then save it to a remote subsystem, and run it on an MVS subsystem on which the Quest Central for DB2 v4.8.1 or later mainframe components are installed, the job will fail with a syntax error.

Workaround:
In order for native IBM utility jobs to run on a Quest Central for DB2, version 4.8.1 or later mainframe installation, make sure template names 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>)))=

You can change template syntax either from the Mainframe Job Review page of the Remote Job wizard on a Quest Central for DB2 v3.1.1 client or in the member containing the job, after you use FTP to transfer it to the mainframe.

 N/A
Spotlight on DB2 (classic version )

(DB2 for z/OS) QPAGENT terminates the record feature if traces are not active.

Workaround:
Make sure the monitor trace for CLASS(01) is active before starting the record feature.

 CR#45,016

(DB2 for LUW) When you launch Spotlight on a DB2 v8 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 you can give DB2 control of the maxappls database configuration parameter. The default setting of Automatic for this parameter allows DB2 to dynamically assign resources as needed to support new applications.

Workaround:
Turn off the default alarm for the metric behind the Percent of Max component in Spotlight on DB2 for LUW. 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.

 N/A

(DB2 for LUW) The following are recommendations for using the record feature in Spotlight:

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

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

 N/A
SQL Analysis (DB2 for LUW only)

DB2 truncates 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.

Workaround:
Clear the Collect Deadlocks option on the Create Collection window in SQL Analysis to disable deadlock monitoring.

 N/A

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

Workaround:
A fix for this issue is included in DB2 for LUW v8.1 FixPak 5. See IBM APAR JR18739 for more information.

 N/A

Quest Central for DB2 v5.0 or greater is not compatible with versions 2.0, 3.0 or 4.0 of Quest Central for DB2.

Workaround:
Install Quest Central for DB2 v5.0 client on the client machine; install the Quest Central for DB2 v5.0 agent 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.

 N/A
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. N/A

 

Back to Top

Third Party Known Issues

The following is a list of IBM DB2 for LUW APARs that affect the various components in Quest Central for DB2.

APAR or
PMR#

APAR or PMR Description

 Fix

Affected Component
APAR 38001,756 "Queries with a join and an IN predicate where all arguments of the predicate are constants, host variables, or parameter markers could crash the instance..."

This issue can cause the instance to crash during Quest Central for DB2 Migration or Compare and Sync functions.

 Version 9.5
FixPak 2		 Database Administration
PMR 30268,756 DB2 does not permit you to execute the CREATE DATABASE command from the CLP or the Command Editor on a DB2 for LUW version 9 client to create a database on a version 8 server. Working as designed Database Administration
JR18739 Databases on DB2 for LUW v8.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
IY86315 "A REMOTE LOAD (FROM WINDOWS TO UNIX) USING “LOAD CLIENT” COMMAND EXPECTS EACH LINE OF DEL/ASC DATA FILE TO BE TERMINATED BY THE DELIMITER…IF EACH LINE IN DATA FILE WAS NOT TERMINATED BY THE DELIMITER, THE LOAD RETURNS AN SQL ERROR, DEPENDING ON THE DATA TYPE OF THE LAST COLUMN..."

Workarounds include appending a delimiter to each line of the data to be loaded, running the LOAD or EXPORT to an .ixf file, running the LOAD on the Unix machine, or using an IMPORT instead of a LOAD.

 Version 8
FixPak7		 Utilities (Space Management)
JR20165 "LOAD CLIENT OF IXF FILE FROM WINDOWS TO UNIX WITH METHOD N FAILS TO LOAD THE FIRST COLUMN..." Version 8
FixPak 8		 Utilities (Space Management)
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 yet Spotlight
PMR 23399,756,000 The Db2cfgGet API fails with an SQL1009N from the database cataloged in the database directory in a circular loopback configuration. No fix yet Framework--Client Configuration

 

Back to Top

Upgrade and Compatibility

Please review the upgrade information in the Quest Central for DB2 Installation Guide.

 

Back to Top

System Requirements

Verify that your system meets the following minimum requirements. Refer to the Quest Central for DB2 Installation Guide for more detailed system requirement information, including recommended DB2 maintenance levels.

This section provides the following information:

Client Requirements

Quest Central for DB2 client requires the following.

Memory

256 MB of RAM minimum

Hard Disk Space

  • 160 MB of free hard-disk space required to run Quest Central for DB2

or

  • Approximately 220 MB if you are installing Knowledge Xpert in addition to Quest Central for DB2

Operating System

Microsoft® Windows® 2000, 2003, or XP

Additional Software
  • IBM® DB2® for LUW (Linux, Unix, or Windows) v8.1 Runtime Client or later

Note: Quest Central for DB2 requires DB2 for LUW v8.1 Runtime Client when running against a DB2 for LUW v8.1 64-bit server.

  • IBM DB2 Connect v7.2 or later (required for z/OS support)

Managed Database Requirements

Each DB2 database Quest Central for DB2 manages or monitors can be any of these versions:

Database Versions
  • IBM DB2 for Linux, Unix, and Windows (LUW) Enterprise Server Edition (ESE) v8.1 or later (32-bit or 64-bit)

Notes:

  • A minimum of IBM DB2 for LUW v8.1 with FixPak 1 applied is required for SQL Analysis.
  • A minimum of IBM DB2 for LUW v8.1 with FixPak 10 applied is required for SQL Analysis in a RedHat or SuSE Linux 2.6 Kernel environment on an x86-64 (AMD64) server.
  • In 64-bit zLinux environments, the Quest Central for DB2 Agent supports only DB2 for LUW v9.
  • IBM DB2 for z/OS v7 or 8

Note: Quest Central for DB2 was tested in DB2 for z/OS v8 Compatibility Mode (CM) and is fully supported in this mode. Quest Central for DB2 was also tested against DB2 for z/OS v8 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 v8 as follows:

  • Quest Central for DB2 in general—Fully supports both modes as of Quest Central for DB2 v4.9.1 with the limitation described above
  • Spotlight on DB2—Fully supports both modes as of Quest Central for DB2 v4.9.1
  • SQL Tuning—Fully supports both modes as of Quest Central for DB2 v4.8.2
  • Other product or mode combinations—Not supported
Operating Systems Supported by the Quest Central for DB2 Agent
  • 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 zLinux
  • SuSE Linux Enterprise Server 8 and 9 United Linux for Intel x86
  • SuSE Linux 9 (2.6 Kernel) on AMD64 (x86_64)
  • RedHat Enterprise Linux AS 3.0 and 4.0 zLinux (31-bit)
  • RedHat Enterprise Linux AS 2.1, 3.0, and 4.0 for Intel x86
  • RedHat Enterprise Linux AS 4.0 (2.6 Kernel) on AMD64 (x86_64)

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.

Supported Mainframe Operating Systems IBM z/OS v1.4 or later

Requirements to Run Spotlight on DB2 for LUW

Spotlight on DB2 for LUW has these requirements.

User Requirements

Classic Spotlight on DB2 for LUW (available with this release of Quest Central for DB2) requires access to DB2 snapshot data. To access snapshot data, users must have SYSADM, SYSMAINT, or SYSCTRL authority. Users who do not have the proper authority can access snapshot data if the DB2_SNAPSHOT_NOAUTH parameter is activated.

To activate this parameter, 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.

Licensing Requirements

The stand-alone Spotlight on DB2 for LUW v6 requires a separate installation. To integrate this version of Spotlight with Quest Central for DB2, you must obtain two license keys:

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

Requirements to Run SQL Analysis

SQL Analysis requires the following.

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:

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

Configuration Parameter Requirements

SQL Analysis has the following configuration parameter requirements:

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

  1. 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.

  1. Check that the State to be configured at system restart option is set to available.
  1. Restart the machine.
  2. 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

Recommended Indexes for Improving Migration Performance in DB2 for z/OS

To improve the performance of the Quest Central for DB2 Migration feature on large DB2 for z/OS databases, create the following indexes:

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 supports any single-byte character set. Double-byte or multi-byte character sets are not supported. All product components must be configured to use the same or compatible character encodings and must be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America.

 

Back to Top

Getting Started

Contents of the Release Package

The Quest Central for DB2 release package contains the following products:

Install Quest Central for DB2 as a Standalone Product

The Quest Central for DB2 installation process involves the installation of three components:

or

Mainframe components installation LOADLIB update (if a pre-5.0 version of the mainframe components already installed)

Install the Quest Central for DB2 Client

If you have a pre-5.0 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 5.0.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 5.0 version of the Quest Central for DB2 client installed on your machine, the installation wizard performs a version 5.0.2 client maintenance installation, allowing you to do any of the following:

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

Install 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 a previous version of the agent to version 5.0.2, refer to 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 5.0 version of the Quest Central for DB2 agent installed on your database server, the installation wizard guides you through a 5.0.2 agent installation maintenance. If you have a pre-5.0 version of the agent installed on the database server, the installation wizard launches a new agent installation.

Install the Quest Central for DB2 Mainframe Components

To have full Quest Central for DB2 functionality available for administering, managing space for, monitoring, and tuning DB2 for z/OS subsystems, you must install the Quest Central for DB2 mainframe components on each subsystem you intend to manage. For installation instructions, refer to the Installing Quest Central for DB2's Mainframe Components chapter in the Quest Central for DB2 Installation Guide for instructions.

Update the Quest Central for DB2 LOADLIB on z/OS

Quest Central for DB2 v5.0.2 contains a change to a Quest Central for DB2 for z/OS module. To take advantage of this change, perform the appropriate action:

To update the Quest Central for DB2 LOADLIB, you need to re-create it. This process involves transferring an xmi file from Quest Central for DB2 client installation directory to the mainframe and expanding the PDS/E for the LOADLIB. It is recommended that you create the LOADLIB in 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

  1. 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.
  2. At a TSO command prompt, type the following

TSO RECEIVE INDATASET (‘sequential.file.name’)

  1. 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.

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

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

  1. APF-authorize the new LOADLIB.

Run Quest Central for DB2 as Part of QCE

If you want to run Quest Central for DB2 within the Quest Central Explorer (QCE) environment, you need to do the following:

Phase 1: Install Quest Central for DB2 as a standalone.

Phase 2: Install, update, or upgrade QCE (see below).

Phase 3: Run Quest Central for DB2 from the QCE console.

Perform a New Installation of QCE

To perform a new installation of QCE

  1. Download the QCE console component from the following location:

http://www.quest.com/Quest-Central-Explorer/

  1. Navigate to the directory or folder where you downloaded the component, and run the executable in this directory or folder to install QCE.
  2. After the installation is complete, double-click the Quest Central Explorer icon on your desktop to launch QCE.
  3. From the Quest Central Explorer window, select View | Check for Installed Products to add Quest Central for DB2 to the console.

Update a Current QCE v3.0

If you already have QCE v3.0 installed, you need to run a search feature within QCE that looks for newly installed products, such as Quest Central for DB2 v5.0.2, to add.

To update your currently installed QCE v3.0

  1. Start QCE.
  2. From the Quest Central Explorer window, select View | Check for Installed Products to add Quest Central for DB2 functionality to the console.

Upgrade from a pre-3.0 QCE Version

If you have a pre-3.0 version of QCE installed on your machine, uninstall this product, and follow the instructions in Perform a New Installation of QCE to install QCE v3.0 of  and to add Quest Central for DB2 functionality to the console.

Run Quest Central for DB2 from the QCE Console

To run Quest Central for DB2 from the console

  1. From the QCE console, highlight the DB2 node in the Databases section.
  2. Click the appropriate icon or link on the QCE console to open Quest Central for DB2 or to start a separate Quest Central for DB2 SQL Tuning, Spotlight on DB2 for LUW v6, or Knowledge Xpert for DB2 session.

Back to Top

For More Information

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

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:

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.

 

Back to Top

© 2008 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:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
 

www.quest.com

Email: legal@quest.com

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

Trademarks

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk, Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, InTrust, IT Dad, I/Watch, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQL Watch, SQLab, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, 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.

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

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656
Email: legal@quest.com

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