A fix is available
APAR status
Closed as program error.
Error description
(HPU 5.1 only) DB2 HPU stops after having issued a message such as the following: INZI800E ERROR ACCESSING TO A DATASET. ACTION : ALLOCATE RC:0x1708 REASON: 0x2 DDN: SYSnnnnn DSN: not_existing_DB2_LDS about a not yet existing LDS for the involved table space. This occurs when the more recent LDS created for the table space has just reached the maximum number of pages and no new LDS has been created yet. In such a situation, DB2 HPU should only issue the INZI800E message but continue the unload process after having issued a message informing the allocation error message can be ignored such as: INZX134 TABLESPACE FRD8A60X HAS ONLY 1 LDS. ALLOCATION ERROR ON DATA SET CAN BE IGNORED. PB52026 INZI800E INZI800 MSGINZI800E MSGINZI800
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: * * Users of High Performance Unload * **************************************************************** * PROBLEM DESCRIPTION: * * PI93113: DB2 HPU does not unload all the expected rows when * * the following conditions are fulfilled: * * - the OPTIMIZE_PART_RANGE feature is put into action (i.e. * * the INZU485I message is issued) * * - some of the logical partitions numbers involved in the * * unload (as indicated by the INZU485I message) do not match a * * physical partition with the same number * * The latter can occur when the partitions have been rotated. * * For example, for a logical unload specifying a WHERE clause * * that involves data from the logical partition # 18 (out of * * 28) only, if the OPTIMIZE_PART_RANGE feature is put in * * action as indicated by the following message: * * INZU485I NUMBER OF PARTITIONS SELECTED PASSED FROM 28 TO * * 1 * * and if the information from the SYSIBM.SYSTABLEPART DB2 * * catalog table excerpt for the involved table space is as * * follows * * SELECT PARTITION, LOGICAL_PART FROM SYSIBM.SYSTABLEPART * * WHERE DBNAME='dbname' AND TSNAME = 'tsname' WHERE * * LOGICAL_PART = 18 ; * * +--------------------------+ * * | PARTITION | LOGICAL_PART | * * +--------------------------+ * * 1_| 24 | 18 | * * +--------------------------+ * * no row is returned. * * * * PI93115: * * DB2 HPU can enter a wait state when unloading several tables * * fom a multi-table table space into a single output file and * * the zIIP mode is put into action (i.e. message INZI210I ZIIP * * ENABLE ... is issued). * * * * PI93361: * * An ABENDS0C4 can occur during a logical unload processed in * * native mode whenever the indexscan feature is put into * * action which occurs when at least all of the following set * * of conditions apply : * * - the INDEXSCAN NO option is NOT specified * * - the table space to be unloaded has a valid clustering * * index * * - only one table space is involved in the unload * * - the involved table space contains only one table * * - at least one SELECT statement of the unload is processed * * in native mode and contain either of the following * * + an ORDER BY clause which sort-key matches the key of the * * clustering index of the table space * * + an ORDER CLUSTER clause. * * The bigger the number of nullable columns is the more likely * * the issue occurs. * * * * PI93919: * * DB2 HPU stops after having issued a message such as * * INZI800E ERROR ACCESSING TO A DATASET. ACTION: ALLOCATE RC: * * 0x1708 * * REASON: 0x2 * * DDN: SYSnnnnn DSN: not_existing_DB2_LDS * * about a non yet existing LDS for the involved table space. * * This occurs when the more recent LDS created for the table * * space has just reached the maximum number of pages and no * * new LDS has been created yet. * * In such a situation, DB2 HPU should only issue the INZI800E * * message but continue the unload process after having issued * * a message informing the allocation error message can be * * ignored such as: * * INZX134 TABLESPACE FRD8A60X HAS ONLY 1 LDS. ALLOCATION * * ERROR ON DATA SET CAN BE IGNORED. * * * * PI94321: * * The request to unload LOB data as LOB files stops after an * * ABENDSB37-04 related to a LOB file has occured. * * This can occur when the following conditions are fulfilled: * * - a LOB data to be unloaded is larger than 16 tracks (i.e. * * 895 680 bytes). * * - the LOB file allocation is requested with a TEMPLATE * * statement that defines a sequantial dataset and does not * * specify any any primary quantity * * * * PI94322: * * The unload of the data from an image copy (COPYDDN option) * * can enter an everlasting wait state. * * The can occur if the following two conditions are fulfilled: * * - the fix for PI91755/PB51471 has been applied. * * - the image copy processing involves a sort, which occurs * * when one of the following condition applies: * * + the image copy was retreive from the DB2 catalog * * (COPYDDN LAST_IC or COPYDDN interger option) and the catalog * * (SYSIBM,SYSCOPY table) indicates it is an INLINE image copy * * + the input image copy is allocated in the JCL (COPYDDN * * ddname option) and the keyword INLINE or FROM_COPYTOCOPY or * * MERGE_IIC is specified * * * * PI94324: * * The INZU478I, INZU479I and INZU480I messages are related to * * a sepecific SELECT statement from the unload command but the * * SELECT they are related to is not clearly mentioned. This * * important indication should be added. * * * * PI94329: * * No rows are unloaded from an unload from an image copy * * (COPYDDN option). This can occur intermittently if the image * * copy processing involves a sort, which occurs when one of * * the following condition applies: * * - the image copy was retreive from the DB2 catalog (COPYDDN * * LAST_IC or COPYDDN interger option) and the catalog * * (SYSIBM,SYSCOPY table) indicates it is an INLINE image copy * * - the input image copy is allocated in the JCL (COPYDDN * * ddname option) and the keyword INLINE or FROM_COPYTOCOPY or * * MERGE_IIC is specified * * * * PI94330: * * An HPU job can enter an everlasting wait state when traces * * files are allocated. Traces files are produced when some * * ddnames are allocated to the DB2 HPU step. The list of this * * ddnames is not documented by the ddnames for traces always * * start with a $ (dollar sign). * * * * PI94332: * * When unloading the data from an image copy (COPYDDN option) * * using the DDLDDN feature and providing as DDLDDN input file * * a DDL containing a CREATE with 'NOT NULL WITH DEFAULT AS * * SECURITY LABEL' attributes, the job enters a never ending * * loop. * * * * PI94603: * * As a continuation of the enhancement developped for RFE96379 * * in HPU 5.1 more actions done by HPU before submitting a * * SELECT statement to DB2 are reported. These actions are the * * following the execution of the following statements: * * - SET CURRENT DEGREE = * * - SET CURRENT SQLID = * * - SET CURRENT OPTIMIZATION HINT = * * - SET CURRENT QUERY ACCELERATION = * * - SET CURRENT APPLICATION COMPATIBILITY = * * * * PI94604: * * The messages texts for INZU478I, INZU479I, INZU480I have * * been enhanced to make clearer that they are issued for a * * same feature by adding the SQL MODE PROCESSING text at their * * begining. * * * * PI94607: * * The unload from an image copy retreived from the DB2 catalog * * (COPYDDN LAST_IC or COPYDDN integer is specified) stops with * * completion code of 12 after having issued a message such as * * INZI800E ERROR ACCESSING TO A DATASET. ACTION: ALLOCATE RC: * * 0 * * REASON: 0x0 * * DDN: SYSnnnnn DSN: dsname * * This occurs if the image copy to be unloaded is a FlashCopy * * and contains the copy of a table space which more recent LDS * * has just reached the maximum number of pages and no new LDS * * has been created yet * * * * PI94608: * * The unload of the data from a FlashCopy allocated in the JCL * * (COPYDDN ddname,FLASHCOPY is specified) stops with * * completion code of 12 after having issued a message such as * * INZRE40 PAGE NO. 1 IN LDS NO. 2 OF PAGESET pageset IS NOT IN * * SEQUENCE, SCAN ABORT * * This occurs if the FlashCopy contains the copy of a table * * space which more recent LDS has just reached the maximum * * number of pages and no new LDS has been created yet * * * * PI94609: * * A logical unload in native mode fails with ABENDS0C1. This * * occurs when the following conditions are fulfilled: * * - the involved table space is not partitionned * * - the logical unload specifies an ORDER clause * * - the indexscan feature is put inot action * * - the more recent LDS created for the table space has just * * reached the maximum number of pages and no new LDS has been * * created yet. * * * * PI94610: * * The unload of the data from an image copy (COPYDDN) * * allocated via a TEMPLATE statement stops with completion * * code of 12 after having issued a message such as * * INZRE40 PAGE NO. 1 IN LDS NO. 2 OF PAGESET pageset IS NOT IN * * SEQUENCE, SCAN ABORT * * This occurs if the image copy contains the copy of a table * * space which more recent LDS has just reached the maximum * * number of pages and no new LDS has been created yet * **************************************************************** * RECOMMENDATION: * * Apply the PTF for problem resolution * ****************************************************************
Problem conclusion
Code has been changed to fix this problem
Temporary fix
PI93113: Disable the OPTIMIZE_PART_RANGE feature by specifying OPTIMIZE_PART_RANGE YES in the Technical Parameters options block. PI93115: Disable the zIIP usage for the job concerned by the issue (e.g. specify ZIIP OFF in the Technical Parameters options block). PI93361: Disable the indexscan feature by specifying INDEXSCAN NO. PI94321: Consider adding a relevant primary quantity to the template statement PI94330: Consider removing the DD cards for the trace files.
Comments
APAR Information
APAR number
PI93919
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
510
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-02-16
Closed date
2018-03-09
Last modified date
2024-06-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI54376
Modules/Macros
INZUTILK
Fix information
Fixed component name
DB2 HI PERF UNL
Fixed component ID
5697F4400
Applicable component levels
R510 PSY UI54376
UP18/03/16 P F803 ¢
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.1.0","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 June 2024