flodubois 270000K6H5 Visits (1381)
OMPE recently delivered a very useful functionality for anyone who wants to track the evolutionary trend of key performance metrics. The new OMPE Spreadsheet Input Data Generator can be used to generate a CSV (comma-separated value) file containing a chosen subset of statistics or accounting indicators. The default field selection includes all the fields that have a column in the associated OMPE Performance database (PDB) table, but these lists can easily be customized to meet your own needs for reporting. This CSV data can then be transferred to workstations and imported into spreadsheets to improve DB2 performance analysis using graphical representations or pivot tables.
Requirements: APAR PM73732 and OMPE v510 PTF UK90267 / OMPE v511 PTF UK90268
flodubois 270000K6H5 Visits (1399)
To help you convert your plans and packages from using private protocol to using DRDA protocol, DB2 provides a priv
The tool will inserts a '*' in place of an empty value in the location part of any PKLIST entry. If you use an asterisk, at run time the location comes from the special register CURRENT SERVER and DB2 checks privileges to use the SQL statements in the package at that location. This could result in a significant increase in authorization checks and lead to an important CPU overhead.
flodubois 270000K6H5 Visits (1089)
If you have created native SQL stored procedures in V9 and you want to maximize the 31-bit virtual storage constraint relief on entry in DB2 10 CM, REBINDing the associated packages is not enough. You will need to regenerate the stored procedure so that the SQL control statements as well as the non-control statements are rebound.
To regenerate an existing version of a native SQL procedure:
Michael_D. 1100004WAH Visits (3926)
PTF UK91435 (APAR PM79520)
is required for DB2 10 for z/OS customers in a Data Sharing environment
PTF UK91435 is required for DB2 10 for z/OS customers
Michael_D. 1100004WAH Visits (2503)
APAR PM81799: ABEND04E RC00C90101 IN DSNIREDO ERQUAL5005 DURING A RECOVER UTILITY.
All DB2 10 for z/OS users who use COPY or RECOVER online utility with FLASHCOPY
DB2 has been modified to ensure compensation log records are not written while COPY FLASHCOPY is running.
Additionally, this APAR will insure ensure that error conditions are handled correctly.
All DB2 10 for z/OS users are affected who use COPY or RECOVER online utility with FLASHCOPYAll DB2 10 for z/OS users who use COPY or RECOVER online
utility with FLASHCOPY
Michael_D. 1100004WAH Visits (3403)
Michael_D. 1100004WAH Visits (2488)
In preparation to DB2 10 migration there is a need to answer the question if DB2 tooling will support the full functionality of a given DB2 version or will it tolerate the new version and worse if it will not support the new version. Mainly this will be most important if new functionality are effectively used and if the migration of a given DB2 environment completed the conversion to new function mode ( DB2 10 NFM ). Nevertheless, is is also important to watch and maintain the DB2 10 maintenance level to answer the question supported or tolerated.
This table provides information regarding DB2® Tools support for DB2® 10 for z/OS.
For more information on which new functions of DB2 10 are utilized by any specific product, or to find out about DB2 10 compatibility for products or releases not included in this matrix, please contact your IBM Customer Service Representative.
Michael_D. 1100004WAH Visits (3366)
Customers running with DB2 10 NFM have noticed that table spaces associated with the DB2 directory data base or catalog (DSNDB01 and SPT01) experience significant space growth resulting from BIND/REBIND operations, DDL, utility activity (Reorg). The only way customer could sustain the issue was by frequently scheduling reorgs on the DB2 directory and catalog in DB2 10 NFM.
Updated list of APARs for excessive SPT01/DBD01 growth – Base and LOB tablespaces - including related Utility APARs in this area!
DB2 10 NFM Cat/Dir SPT01/DBD01 excessive growth
APAR PM66874 to resolve: LOB integrity abend during REORG of DBD01.
DB2 10 NFM Cat/Dir SPT01/DBD01 excessive growth related
APAR PM68842 to resolve: REORG abend. Broken aux index.
agburke 060001QPDN Visits (1903)
These two APARs address unexpected table space growth due to internal DB2 algo
· PM80804 – LOB space growth in V10 due to old read claim LRSN
agburke 060001QPDN Visits (2538)
Many of you, including our own L2 performance team have spent many years creating spreadsheets to combine the stats and accounting data to reveal things like average CPU seconds or elapsed time per occurrence or COMMIT based on the CONNTYPE. This can be used to get a profile of the typical transactions, then look for outlyers based on top 10 reports. Now there is a new IFCID that can aggregate such information, and it can be started by using the STATS CLASS 9 trace.
· PM62797 – IFCID 369 addition to aggregate stats and accounting information in Stats class 9
· PM72949 for OMPE V5.1.1
You will want to check with your vendors to determine when/if your other accounting and stats reports can take advantage of this new functionality.
agburke 060001QPDN Visits (1810)
FlashCopy technology continues to become a more integral part of DB2 recoverability, especially in V10. There APARs relate to FlashCopy image copies and RESTORing a a system from Space Efficient FlashCopy.
This has to do with a Buffer manager flag.
· PM77661 – V10 FlashCopy image copy CONSISTENT shows broken page when used against classic segmented table space
These have to do with a flag that is set in HSM.
· PM76937 - V9 RESTORE SYSTEM fails using space efficient FlashCopy
· PM53237 – V10 RESTORE SYSTEM fails using space efficient FlashCopy
agburke 060001QPDN Visits (2112)
Here are 2 zIIP related APARs.
In z/OS 1.10 (APAR) WLM started creating work dependent enclaves to allow difernt zIIP offload potential for related enclaves.
In DB2 v10 when Runstats offloads to ZIIP it creates dependent WLM enclaves in STC instead of work-dependent enclaves. This causes a problem for SAP customers who run WLM Enclaves and DB2 stored procedures like ADMIN_UTL_SCHEDULE. In the reported case, a SAP ABAP program calls DB2 stored procedure ADMIN_UTL_SCHEDULE with max_parallel 10 and 1000 tablespaces to process RUNSTATS.
· PM75060 – zIIP eligible RUNSTATS tasks were running in dependent enclaves under STC
This APAR affects QWACZIIP_ELIGIBLE, which represents zIIP eligible workload that executed on a CP. Some customers saw large amounts of zIIP eligible work running on CPs, but in actuality it was an incorrect calculation of the Utility's processing time.
· PM74888- zIIP eligible work incorrectly reported for Utility execution
agburke 060001QPDN Visits (2050)
Regarding the DB2 for z/OS migration process, customers have seen failures due to ALTERing a catalog table that has no available version numbers (SQLCODE4732).
In addition, we are changing the premigration checkout jobs, DSNTIJPM and DSNTIJPA, to add queries that will identify cases where the version numbers are bad. The premigration checkout jobs are to be run before migration processing begins (ie in the release being migrated from). If there is a version number problem then the version numbers can be corrected prior to the migration process. This will ensure that the migration process will not fail due to this problem. See the ++HOLD actions for this APAR for further guidance for using DSNTIJPM or DSNTIJPA.
The following SELECT statement can be used to determine if there are catalog objects that have version number problems:
SELECT SUBSTR(CREATOR,1,8) AS CREATOR,
SUBSTR(NAME,1,8) AS NAME,
WHERE DBID = 6
AND (CURRENT_VERSION < OLDEST_VERSION);
If there are table spaces returned with this query then the version numbers can be corrected by a REORG of the table space and then by running MODIFY RECOVERY with DELETE to recycle version numbers. Additional information about version numbers can be found in the Utility Guide and Reference and also in the Administration Guide.
· PM70914 – DB2 migration fails due to catalog tables having incorrect version numbers
agburke 060001QPDN Visits (1977)
We have enhanced the storage request processing for distributed threads to avoid a bottleneck condition that can occur in the DDF communication buffer storage. 04E abends due to virtual storage constraints could be seen in V9 and V10 in some customer environments. This APAR has been marked HIPER, but can also improve the current DDF processing when a rush of distributed threads enter the system at the same time.
· PM75473 – DDF threads have slow response time, and bottleneck due to 64-bit storage requests
agburke 060001QPDN Visits (1632)
This APAR concerns customers who partition table spaces based on a timestamp column. When this customer moved to DB2 10 this query lost the ability to prune partitions on a partitioned table space and the response time increased dramatically. In this case the application was comparing the timestamp column to a host variable with a timestamp precision (6). The temporary fix is to use PLANMGMT to fall back to the previous access path.
· PM81692 – performance degradation for table partitioned on timestamp
This APAR deals with table insert experiencing longer than expected space search times. This can occur when the clustering index does not provide an adequate position for insert within the table.
· PM75921 – long insert times due to inadequate search for free space in the clustering index