DB2 10 Information APARs and APARs Mentioned at the IDUG EMEA Conference

One of the best things to see and hear at IDUG conferences is all the IBM DB2 developers and product authors talking about their enhancements within DB2. Many IBM developers presented the latest information on DB2 10, Netezza, DB2 pureScale, IDAA, Data Studio and the enhancements coming through the new DB2 LUW Galileo.

Since the developers are really close to the DB2 components and its code they know the latest and greatest information. One of the things they usually talk about is the latest fixes and APARs that affect their DB2 component code. In general the best way to keep up with all the DB2 10 APARS is to subscribe to the information APARS:

II14477: DB2 9 MIGRATION/FALLBACK INFOAPAR TO/FROM DB2 10

II14474: DB2 V8 MIGRATION/FALLBACK INFOAPAR TO/FROM DB2 10

The links to these APARs are listed here on my web site. Just click on the link and subscribe to it with your IBM id and you will receive an email every time it is updated.

I wanted to pass along all the fixes and APARs mentioned within the IDUG Prague presentations. Some of these APARS are old, may have been reopened or are within the DB2 10 Information APARS mentioned earlier. They were noted by the DB2 developers in the IDUG Prague presentations so your shop may want to verify them as you prepare and implement DB2 10.

 

 

APAR PM27073- Display size for SPT01

****************************************************************

* USERS AFFECTED: All DB2 users. *

****************************************************************

* PROBLEM DESCRIPTION: Preconditioning for adding support to change the in-line length of DSNDB01.SPT01.

****************************************************************

* RECOMMENDATION: *

****************************************************************

New function is needed to support changing the in-line length of DSNDB01.SPT01. This will improve performance and provide the ability to compress the package data that is stored in-line.

 

APAR PM27811 supports inline LOBs

****************************************************************

* USERS AFFECTED: All DB2 users. *

****************************************************************

* PROBLEM DESCRIPTION: The in-line length of DSNDB01.SPT01 can not be changed this can affect performance and the DASD required for packages.

****************************************************************

* RECOMMENDATION: *

****************************************************************

In DB2 V10 NFM the package information is stored in a LOB table space with an inline length of 0 which causes the following two problems:

 – All the package information is stored in the LOB table space and this can not be compressed. This can cause more DASD to be used for packages.

– When package information is stored in the LOB, the base row and the LOB row must be read. This can affect performance.

 

 APAR PM28500 Location Name Support

****************************************************************

* USERS AFFECTED: All Distributed Data Facility (DDF) users. Specifically those using profile tables facility to monitor threads and connections for TCP/IP access to a DB2 server.

****************************************************************

* PROBLEM DESCRIPTION: This APAR addresses the following profile table facility enhancements:

* 1. Additional profile filters support for system profile monitoring functions. These are:

* – Server Location Name or Server

* Location alias,

* – Client End User ID,

* – Client End Application Name,

* – Client End Workstation Name.

* 2. Default filter and default threshold support.

* 3. Setting up a default value for DB2 for z/OS embedded SQL applications in the Client End User ID, Client End User Application Name, and Client End User Workstation Name special registers.

****************************************************************

 

APAR II14296: REMOVING THE NEED TO SPECIFY SORTNUM ON DB2 UTILITIES AND DB2 UTILITIES’ STRATEGY FOR DFSORT PROCESSING

 

APAR PM32360

****************************************************************

* USERS AFFECTED: All Users of the IBM Data Server Driver for JDBC and SQLJ

****************************************************************

* PROBLEM DESCRIPTION: IBM Data Sever Driver for JDBC and SQLJ version 3.62.57 is provided by this APAR ( JCCV36257 )

* *

* This APAR is applicable to IBM Data Sever Driver for JDBC and SQLJ for DB2 z/OS V10, DB2 z/OS V9 and the alternate supplemental driver for DB2 z/OS V8. ( JCCZOSDB2V10, JCCZOSDB2V9, JCCZOSDB2V8)

* *

* This APAR delivers a new release (3.62) of the IBM Data Server Driver for JDBC and SQLJ providing an accumulation of defect fixes and enhancements.

* *

* Individual items are documented in the APAR summary section that follows.

****************************************************************

 

APAR OA17735

****************************************************************

* USERS AFFECTED: All users of z/OS 1.7.1 (JBB772S) and above.

****************************************************************

* PROBLEM DESCRIPTION: This APAR contains the SRM function for BLOCKED WORKLOAD.

****************************************************************

 

APAR OA23849

****************************************************************

* USERS AFFECTED: All z/OS V1R8 and later users of the DFSMShsm FRBACKUP and FRRECOV commands that want to use PPRC primary volumes in their copy pool environments.

****************************************************************

* PROBLEM DESCRIPTION: Customer wants to use PPRC volumes in their copy pool definitions. Currently PPRC volumes are not supported for selection in the FRBACKUP or FRRECOV functions.

****************************************************************

 

APAR OA33106

****************************************************************

* USERS AFFECTED: Users running z/OS HBB7750 and above.

****************************************************************

* PROBLEM DESCRIPTION: Increased ESQA storage usage for an SRB that is using a linkage stack when its status is being saved.

****************************************************************

  

APAR OA35885

Current real and auxiliary storage usage information is not available for high virtual storage

****************************************************************

* USERS AFFECTED: Users of HBB7750 and above.

****************************************************************

* PROBLEM DESCRIPTION: In support of PM24723, RSM IARV64 macro service should provide an interface to obtain the real frame and auxiliary storage in use to support an input high virtual storage range.

****************************************************************

* RECOMMENDATION: *

****************************************************************

 

APAR PK21861

****************************************************************

* USERS AFFECTED: Users of Dynamic Statement Caching and bind option KEEPDYNAMIC(YES)

****************************************************************

* PROBLEM DESCRIPTION: ABEND04E RC00E2003 DSNSVBK 067E with high cached SQL statement pools

****************************************************************

* RECOMMENDATION: *

****************************************************************

 

APAR PK56922

****************************************************************

* USERS AFFECTED: All DB2 V8 and V9 users migrating to V10.

****************************************************************

* PROBLEM DESCRIPTION: Toleration of fallback from DB2 Version 10.

* *

* In a Data Sharing environment, required for coexistence of V10 with V9 or V10 with V8.

****************************************************************

 

APAR PK61766

****************************************************************

* USERS AFFECTED: All users of DB2 Version 8 or 9 for z/OS who intend to run future versions of DB2 with Version 8 or 9 early code.

****************************************************************

* PROBLEM DESCRIPTION: Changes to the early code are being made to provide compatability with future releases of DB2 for z/OS.

****************************************************************

 

APAR PK64045

****************************************************************

* USERS AFFECTED: All Distributed Data Facility (DDF) users. Specifically those with plans or packages bound with DBPROTOCOL(PRIVATE).

****************************************************************

* PROBLEM DESCRIPTION: Private protocol capability will not be available in DB2 10 for z/OS. Thus, many customers are trying to migrate their application plans and packages to use DRDA protocol and need assistance in knowing the steps to convert to DRDA protocol. Also, certain application processing which uses private protocol may not convert correctly to DRDA protocol.

****************************************************************

 

APAR PK77514

****************************************************************

* USERS AFFECTED: All DB2 IFC statistics users.

****************************************************************

* PROBLEM DESCRIPTION: IFCID1 latch statistics counters mapped by DSNDQVLS were marked as serviceability.

****************************************************************

 

 APAR PK80375

****************************************************************

* USERS AFFECTED: All DB2 users of packages.

****************************************************************

* PROBLEM DESCRIPTION: A new DB2 subsystem parameter is provided to allow compression to be turned on or off for DB2 directory space SPT01.

****************************************************************

 

APAR PK81470

****************************************************************

* USERS AFFECTED: DB2 users running with datasharing mode.

****************************************************************

* PROBLEM DESCRIPTION: In DB2 Z/OS V9, the space search logics for member cluster with PCTFREE=0 and FREEPAGE=0 is not consistent with logics in V8. Many customers insist to expect the consistency between V9 and V8.

****************************************************************

 

 APAR PK81471

****************************************************************

* USERS AFFECTED: ALL DB2 for z/OS non-segmented and non-UTS table with APPEND attribute which is explicitly specified.

****************************************************************

* PROBLEM DESCRIPTION: There are high number of get pages and CPU utilization with tables defined with APPEND YES attributes in the non-segmented tablespace during high concurrent insert workload *

****************************************************************

 

APAR PK83108

****************************************************************

* USERS AFFECTED: All DB2 users

****************************************************************

* PROBLEM DESCRIPTION: Create tablespace or index may fail with RC00D70025 due to insufficient volume space for a DB2 managed data set. The DB2 stogroup is defined with multiple specific volsers which are SMS guaranteed space volumes.

****************************************************************

 

APAR PK85068

****************************************************************

* USERS AFFECTED: All users of DB2 EXPLAIN tables in DB2 UDB for z/OS Version 8 and DB2 Version 9.1 for z/OS are affected by this change.

****************************************************************

* PROBLEM DESCRIPTION: Use of EBCDIC EXPLAIN tables and of EXPLAIN tables in a previous-release format is deprecated in DB2 V8 and V9.

* . *

* Procedures and programs are provided to assist with:

* – Putting DB2 explain tables into current release format

* – Migrating EBCDIC explain tables to Unicode

****************************************************************

 

APAR PK85856

****************************************************************

* USERS AFFECTED: All users of DB2 V8 or V9 Utilities for z/OS with DFSORT V1R10 who wish to offload additional workload to zIIP processors.

****************************************************************

* PROBLEM DESCRIPTION: DFSORT support for additional zIIP offload by DB2 Utilities. In conjunction with DB2 APAR PK85889, this PTF enables DB2 Utilities to offload portions of sort workload to zIIPs when they are available.

****************************************************************

 

APAR PK85889

****************************************************************

* USERS AFFECTED: All DB2 for z/OS V8 and DB2 9 for z/OS utility users

****************************************************************

* PROBLEM DESCRIPTION: DB2 Utilities expanding zIIP offload capability. In conjunction with DFSORT APAR PK85856, this PTF enables DB2 Utilities to offload portions of sort workload to zIIPs when they are available.

****************************************************************

 

 APAR PK86956

****************************************************************

* USERS AFFECTED: Users of DB2 Automation Tool.

****************************************************************

* PROBLEM DESCRIPTION: Running Copytocopy utility from an incremental image copy results in error message “HAAB121E:No image copy exists to support COPYTOCOPY” even when an incremental or full image copy is present in SYSCOPY.

****************************************************************

* RECOMMENDATION: APPLY the PTF.

****************************************************************

 

APAR PK87280

****************************************************************

* USERS AFFECTED: All DB2 users.

****************************************************************

* PROBLEM DESCRIPTION: Existing version 8 and 9 early code is not compatible with version 10 base code. Toleration code needs to be added to ensure version 8 and version 9 early code can be run with a version 10 DB2 subsystem.

* *

* Without this apar applied, an ABEND0C4 in CSECT DSNWSDWA may be encountered when record services are invoked from CSECT DSNAPRHX.

****************************************************************

* RECOMMENDATION: *

****************************************************************

 

APAR PK92339

****************************************************************

* USERS AFFECTED: All Distributed Data Facility (DDF) users. Specifically where the private protocol capability is no longer required or desired for application remote access.

****************************************************************

* PROBLEM DESCRIPTION: Once all packages and plans have been converted from private protocol, support is required to prevent any future introduction of Private Protocol objects or requests into the system.

****************************************************************

 

APAR PK96294

****************************************************************

* USERS AFFECTED: All DB2 z/OS 9 users who uses a LIKE predicate where the left-hand side (LHS) of LIKE can match to a key that is defined in a padded index on expression.

****************************************************************

* PROBLEM DESCRIPTION: A query may receive an incorrect output or experience a poor performance if the query meets the following conditions:

* 1. references a LIKE predicate whose LHS operand matches to a key of an index on expression.

* 2. the pattern of LIKE is a stand- alone constant, host variable, or parameter marker. 

*3. for the incorrect output case, the matched index is a padded index.

****************************************************************

 

APAR PM04968

****************************************************************

* USERS AFFECTED: DB2 UDB for z/OS Version 8 and DB2 Version 9.1 for z/OS System Administrators are affected by this change.

****************************************************************

* PROBLEM DESCRIPTION: Provide a DB2 Version 10 for z/OS premigration checkout job in DB2 UDB for z/OS Version 8 and DB2 Version 9.1 for z/OS.

****************************************************************

 

APAR PM09354

****************************************************************

* USERS AFFECTED: Users who invoke the REBIND PACKAGE command such that both the PLANMGMT and DBPROTOCOL options are specified.

****************************************************************

* PROBLEM DESCRIPTION: When the REBIND PACKAGE command is invoked under the following conditions, DB2 erroneously raises a DSNT216I error:

* * The value of the PLANMGMT option is specified as (BASIC) or (EXTENDED), and, The value of the DBPROTOCOL option is being changed from (DRDA) to (PRIVATE), or vice versa

 

****************************************************************

 

APAR PM13525

****************************************************************

* USERS AFFECTED: All DB2 9 and DB2 10 for z/OS users of the BIND PACKAGE DEPLOY command or REBIND PACKAGE for a native SQL Procedure or CALL statement of a native SQLPL Procedure.

****************************************************************

* PROBLEM DESCRIPTION: DB2 10 for z/OS introduced new runtime structures that differ from DB2 9 systems for section 1 (logic) of native SQL procedures. This affects coexistence as well as fallback/migration paths if a native SQL procedure is created, rebound and/or regenerated in different system levels.

* . *

* The following examples show some cases where this may happen. Other possible symptoms may occur.

* 1. SQLCODE -992 when deploying a native stored procedure created, rebound, regenerated from DB2 10 to DB2 9.

* 2. DSNT246I message when REBINDING on DB2 9 a native SQL procedure that was created or regenerated on DB2 10.

* 3. SQLCODE -904 on DB2 9 when trying to run a native SQL procedure that was created or regenerated on DB2 10.

****************************************************************

 

APAR PM17665

****************************************************************

* USERS AFFECTED: All Distributed Data Facility (DDF) users. Specifically where DB2 z/OS is accessed as a server, via DRDA protocols, from remote DB2 for z/OS client applications.

****************************************************************

* PROBLEM DESCRIPTION: With the elimination of DB2 Private Protocol in DB2 10 for z/OS, the current DB2 server authorization behavior relative to DB2 for z/OS clients is no longer applicable.

****************************************************************

 

APAR PM19034

****************************************************************

* USERS AFFECTED: All DB2 9 for z/OS and DB2 10 for z/OS users of CHECK utilities

****************************************************************

* PROBLEM DESCRIPTION: Add a zparm to control FASTREPLICATION keyword on DSSCOPY command of CHECK utilities.

****************************************************************

 

APAR PM24721

****************************************************************

* USERS AFFECTED:

* 1. All DB2 for z/OS users who needs to bind or rebind applications.

* 2. All DB2 for z/OS users who use RTS table

****************************************************************

* PROBLEM DESCRIPTION:

1. The LOB table spaces of catalog and directory Objects could show high getpage activity and grow rapidly during application BIND/REBIND process.

* 2. The NPAGE value of LOB table space is not updated in the RTS table.

****************************************************************

 

APAR PM24723

****************************************************************

* USERS AFFECTED: All DB2 users.

****************************************************************

* PROBLEM DESCRIPTION: This APAR provides enablement for APAR PM24723: IFCID 225 real storage statistics enhancements

****************************************************************

 

APAR PM25679

****************************************************************

* USERS AFFECTED: DB2 users of BIND and REBIND PACKAGE commands who intend to utilize new function to detect access path changes, reuse access paths, or perform simulated REBINDs.

****************************************************************

* PROBLEM DESCRIPTION: With new options, users of the BIND and REBIND PACKAGE commands will be able to detect access path changes (APCOMPARE) and reuse access paths (APREUSE). In addition, users of the REBIND PACKAGE command can use the new EXPLAIN(ONLY) option to populate EXPLAIN records without performing an actual REBIND.

****************************************************************

 

APAR PM25934

****************************************************************

* USERS AFFECTED: DB2 for z/OS users who have queries using a data partitioned secondary index (DPSI) and more than one partition is qualified for limited partition scan.

****************************************************************

* PROBLEM DESCRIPTION: THE PROBLEM THIS FIX ADDRESSES HAS THE FOLLOWING SYMPTOMS:

* When a query uses a data partitioned secondary index, and more than one partition qualifies for limited partition scan, DB2 could underestimate the index access cost of the data partitioned secondary index and choose a suboptimal access path.

****************************************************************

 

APAR PM26475

****************************************************************

* USERS AFFECTED: DB2 users that need to model CPU speed, number of processors, RID pool, sort pool, and bufferpool settings on a test system to match a production system.

****************************************************************

* PROBLEM DESCRIPTION: This APAR allows a test system to better recreate environment settings on a test system compared to a production system.

****************************************************************

 

APAR PM26762

****************************************************************

* USERS AFFECTED: All DB2 9 for z/OS users of CHECK utilities (i.e. CHECK INDEX, CHECK LOB, or CHECK DATA) with SHRLEVEL CHANGE.

* All DB2 10 for z/OS utility users who use the utility FlashCopy functions.

****************************************************************

* PROBLEM DESCRIPTION: New function is being added for the utility Flash Copy functions which facilitate use with Metro Mirror peer-to-peer remote copy hereafter referred to as PPRC. In addition, the fast replication option for the RECOVER utility can be specified in a zparm.

****************************************************************

 

APAR PM26973

****************************************************************

* USERS AFFECTED: DB2 users that need to model CPU speed number of processors, RID pool, sort pool, and bufferpool settings on a test system to match a production system.

****************************************************************

* PROBLEM DESCRIPTION: This APAR allows a test system to better recreate environment settings on a test system compared to a production system.

****************************************************************

 

APAR PM27249

****************************************************************

* USERS AFFECTED: All DB2 9 for z/OS and all DB2 10 for z/OS users of RUNSTATS utility collecting HISTOGRAM statistics.

****************************************************************

* PROBLEM DESCRIPTION: MSGDSNU636I and MSGDSNU632I shows uneven distribution in quantiles during RUNSTATS collection of HISTOGRAM statistics.

****************************************************************

 APAR PM28296

****************************************************************

* USERS AFFECTED: All DB2 10 for z/OS users of audit policy feature.

****************************************************************

* PROBLEM DESCRIPTION:

* 1.The traces started by audit policies can be stopped by any authorized user.

* 2.IFCID 271 trace record is not generated for SECMAINT category.

* 3.ABEND0C4 DSNWVCST+17E0 during DB2 startup, when audit policies are specified to be started at DB2 startup.

****************************************************************

 

APAR PM28390

****************************************************************

* USERS AFFECTED: ALL DB2 10 FOR z/OS USERS OF FLASHCOPY-SUPPORTED UTILITIES WHO MAKE FLASHCOPY IMAGE COPIES

****************************************************************

* PROBLEM DESCRIPTION: FLASHCOPY FAILS BUT SYSCOPY RECORD IS WRITTEN ANYWAY, LEADING TO MSGDSNU1563I DURING RECOVER UTILITY OR OTHER PROBLEMS ASSOCIATED WITH INCORRECT INFORMATION IN SYSIBM.SYSCOPY.

****************************************************************

 APAR PM29124

****************************************************************

* USERS AFFECTED: DB2 10 for z/OS users of the CHAR built-in scalar function with decimal input values

****************************************************************

* PROBLEM DESCRIPTION: In Version 10, the formatting of decimal data has changed for the CHAR function. The following changes have been made so that the result of the CHAR function is now consistent with the result of the CAST (decimal-expression as CHAR(n)).

* 1. Leading zeroes in the input value are removed.

* 2. Leading zeroes are not added to an input value.

* 3. If the scale of the decimal value is zero, the decimal character is not returned.

* 4. A leading blank is not returned for a positive decimal value.

****************************************************************

 

APAR PM31314

****************************************************************

* USERS AFFECTED: All DB2 Users who would like to use Timestamp with time zone for System_time period columns.

****************************************************************

* PROBLEM DESCRIPTION: Provide new functionality of System_time period columns with Timestamp with time zone support. Also provide new ROW END value so that conversion will make value wrap to a invalid value.

****************************************************************

 

APAR PM31614

****************************************************************

* USERS AFFECTED: All DB2 users.

****************************************************************

* PROBLEM DESCRIPTION: Some packages experience higher CPU times and LC25 when compared with a prior release of DB2.

****************************************************************

 

APAR PM32360

****************************************************************

* USERS AFFECTED: All DB2 users.

****************************************************************

* PROBLEM DESCRIPTION: Some packages experience higher CPU times and LC25 when compared with a prior release of DB2.

****************************************************************

 

APAR PM33767

****************************************************************

* USERS AFFECTED: All users of the DB2 optimization hints (OPTHINT), the EXPLAIN PACKAGE statement, or the APRETAINDUP option on the REBIND PACKAGE command. *

****************************************************************

* PROBLEM DESCRIPTION: This APAR corrects several problems related to the use of DB2 optimization hints (OPTHINT), the EXPLAIN PACKAGE statement or the APRETAINDUP option on the REBIND PACKAGE command. This APAR also adds support for upcoming APAR PM25679.

****************************************************************

 

APAR PM37300

****************************************************************

* USERS AFFECTED: All Distributed Data Facility (DDF) users. Specifically where DB2 for z/OS is accessed as a server, via DRDA protocols, from remote DB2 for z/OS client applications.

****************************************************************

* PROBLEM DESCRIPTION: With the elimination of DB2 Private Protocol in DB2 10 for z/OS, the current DB2 server plan owner based authorization behavior relative to remote DB2 for z/OS client systems is no longer applicable. APAR PM17665 made changes to allow users to move to this new authorization environment however additional new function is required.

****************************************************************

 

APAR PM45650

RC00C90101 DSNONLLE ERQUAL5063 or incorrout or other LOB corruption after RECOVER BACKOUT YES of a LOB tablespace.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>