A fix is available
APAR status
Closed as program error.
Error description
- Abend SB37 on TnnnIn or TnnnMG files, or - Abend U1009 when SORT is invoked because the sort fails with SORT CAPACITY EXCEEDED, or - Abend U1004 preceeded by message IKJ56228I DATA SET dsname NOT IN CATALOG OR CATALOG CAN NOT BE ACCESSED, or - Message INZX036 ixname INDEX PARTITION n PAGESET IS INVALID. The problem occurs with DB2 V8 or V9 only (not in V7) when a partitioned TS has a cluster index that is not partitioned. The problem is also restricted to DB2 HPU R220. It does NOT occur in R310. PB 8923. ADDITONAL SYMPTOMS: 1) In DB2 V8 and V9, an unload processed natively by DB2 HPU on a TS located in a DB that has been started UT fails with SQLCODE -904 ,REASON 00C90086, TYPE OF RESOURCE 00000100 and RESOURCE NAME equal to the database name. PB 8925 2) SORT EXTERNAL may give a wrong SORT order on DATE and TIME columns when the DB2 format is equal to the output format. In this case, the SORT is made on the character representation of the column instead of the binary format. For DATE columns the problem occurs when the site format is EUR or USA, and for TIME columns, it occurs only with format USA. PB 8928 3) SORT EXTERNAL may reverse the order of numeric values, placing NEGATIVE numbers ahead of POSITIVE numbers.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 High Performance Unload. * **************************************************************** * PROBLEM DESCRIPTION: For V220: * * 1. Following errors may occur when * * unloading data from a partitioned * * tablespace which cluster index is not * * the partionning one, where ORDER * * CLUSTER is requested: * * * U1009 or B37 on TnnnIN/TnnnMG data * * sets ABEND may in SORT PHASE when * * ORDER CLUSTER is requested * * * msgINZX036 XID47231 INDEX PARTITION * * nnn PAGESET IS INVALID and * * msgIKJ56228I DATA SET xxxx.Ammm NOT * * IN CATALOG OR CATALOG CAN NOT BE * * ACCESSED. * * * U1004 ABEND * * PB 8923 * * 2. Irrelevant msgINZU127W DIRECT * * ACCESS TO DB2 CATALOG FAILED: SWITCH * * TO SQL ACCESS is issued when the * * unload statement contains a SELECT * * statement involving unqualified table * * names and HPU is run against a * * MIXED=NO susbsytem. * * PB 8941 * * 3. U1208 ABEND when unloading data * * from a partitioned tablespace having a * * non-partitioned partitioning index. * * PB 8950 * * 4. U1114 ABEND when unloading data * * from a partitoned tablespace which * * cluster index is a DPSI and the ORDER * * clause matches the cluster index key. * * PB 8951 * * * * For V310: * * 1. S0C4 ABEND occurs when running * * unloading with FAST-UNLOAD syntax where * * LOAD SYSIN generation is requested but * * no associated DDName is not allocated. * * PB 8895 * * 2. Unpredictable error (among which * * S0C4 ABEND) may occur when unloading * * data from a table involving a * * fieldproc which parameter list has * * more than one item. * * PB 8926 * * 3. Incorrect order of the output data * * if SORT(EXTERNAL) is requested and the * * ORDER BY clause involves a DATE/TIME * * field. This occurs only if susbsystem * * settings specifies EUR or USA * * DATE/TIME format. * * PB 8928 * * 4. Unload fails with msgINZU010I, * * msgINZU022E, msgDSNT408I and SQLCODE = * * -104 when unloading with SORT(EXTERNAL) * * and DB2 FORCE if the ORDER BY CLAUSE * * involves an expression. * * PB 8930 * * 5. Incorrect order of the output data * * where SORT(EXTERNAL) is requested and * * the ORDER BY clause involves a numeric * * field * * PB 8931-8932 * * 6. Unload fails with msgINZU031E when * * SORT(EXTERNAL,VSAMSIZE) and DB2 FORCE * * is requested. * * PB 8934 * * 7. The unload process stops and message * * msgINZU505Eis issued although * * SORT(EXTERNAL,VSAMSIZE) could be * * processed. This occurs when unloading * * an unsupported SELECT with DB2 YES but * * when the SELECT is compatible with * * VSAMSIZE (i.e. use of columns from a * * single table) * * PB 8946 * * * * For V220 and V310: * * 1. The STRIP scalar function used * * within an unload statement does not * * remove the trailing blanks when * * - HPU is run against a subsystem with * * MIXED=NO * * - the data to be stripped is encoded * * with UNICODE CCSID * * - the strip-character is omitted * * PB 8913 * * 2. In DB2 V810, SQLCODE=-904 occurs * * when unloading a data from a database * * with UT restrict state regardless of * * the tablespace state. * * PB 8925 * * 3. Incorrect order of output data when * * unloading data from a table-controlled * * partitioned tablespace if: * * - the ORDER clause matches the * * clustering key * * - the cluster index is partitionned * * - data from several partitions are to * * be unloaded in a single output * * dataset * * PB 8961 * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** For V220: 1. UDBEVTTS was changed to handle the case when the clustering index of a partitioned tablespace is not partitioned. 2. inzctrlhCheckTaskAutority in inzctrl was fixed to use the right ccsid 3. Extra memory freeing operation was removed from _inzbabDestroyEtb in inzbab. 4. Processing of DPSI was fixed in _inzbabBuildEtb in inzbab. For V310: 1. inzctrlfCheckCtlDdn() in inzctrlf and oddnArray in oddn were change to correctly the case where ddn is void. 2. _inzpabfDetermineEctAfppv in INZPABF was changed to correctly set the fieldproc parameter list 3. In inzgcxtrGenerate() in inzgcxtr, a conflicting optimization processing is no more performed for DATE-TIME involved in an ORDER-BY clause to be processed via an EXTERNAL sort. 4. inzoyacc was changed to return a warning code if an the ORDER BY clause contains an expression and to issue the new INZU511W message. 5. In inzgcxtrGenerate() in inzgcxtr, a conflicting optimization processing is no more performed for numerical data involved in an ORDER-BY clause to be processed via an EXTERNAL sort. 6. inzctrlzDetermineSystable in inzctrlz was fixed not to issue irrelevant INZU031E message. 7. _inzpabExternalSort in inzpab was changed to allow the use of VSAMSIZE to check if the unsupported select is compatible with VSAMSIZE anyway. For V220 and V310: 1. _inznodeConvertStripLit() in nznode was changed to correctly handle the default strip-character when unicode data is to be processed. 2. runchks in inzrun was changed to allow -904 SQLCODE if cause by UT restrict state on the database the table/tablespace to unload belongs to. 3. In _inzbabAnalyseIndexScan from inzbab, indexscan is disabled for table-controlled partitioned tablespaces to be unloaded into a single output dataset.
Problem conclusion
APPLY the PTF.
Temporary fix
Comments
APAR Information
APAR number
PK48968
Reported component name
DB2 HI PERF UNL
Reported component ID
5697F4400
Reported release
220
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2007-07-13
Closed date
2007-08-28
Last modified date
2007-09-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UK28657 UK28658
Modules/Macros
INZUTILB
Fix information
Fixed component name
DB2 HI PERF UNL
Fixed component ID
5697F4400
Applicable component levels
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":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSAUUV","label":"IBM Db2 High Performance Unload for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"220","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 February 2021