IBM Support

PK45756: ERROR MESSAGE INZU066E NO TABLESPACE FOUND FOR TABLE TABLE-NAME ISSUED WHEN UNLOADING FROM AN ALIAS AFTER MIGRATION DB2 V7 - V8.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error message INZU066E NO TABLESPACE FOUND FOR TABLE table-name
    is issued when unloading from an ALIAS after a migration from
    DB2 V7 to DB2 V8 without recreating the ALIAS.
    PB 8848
    ADDITIONAL SYMPTOM:
    1) CPU loop occurs when an ORDER BY is made on a constant value.
       PB 8849
    2) INCORROUT.
       The problem occurs on DEC(1) and DEC(2) columns when the
       select is processed by DB2. In this case when you ask for a
       conversion into DECIMAL ZONED(1) or DECIMAL ZONED(2), HPU
       writes the data in DECIMAL PACKED instead of DECIMAL ZONED.
       PB 8883
    3) Error message:
       * 227 * EXPRESSION EVALUATION ERROR       * SYSREC01* nnnnn
       can be repeated in an apparent loop when
       A: the SELECT statement involves expression using the TIME
       function against TIMESTAMP data.
       B: The native mode (data selected by HPU) is used
       PB 8877
    4) Work dataset size may be underestimated, leading to problems
       during the sort phase of the utility. Possible symptom is
       SB37 on TnnnMG data sets. PB 8798.
    5) Padding of null DBCS columns is made with a SBCS blank
       character while it should be made with a DBCS blank
       character. PB 8834
    

Local fix

  • For the first symptom addressing the old ALIAS the
    problem can be circumvented by dropping and recreating
    the alias on any currently supported DB2 release.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Users of DB2 High Perofrmance Unload.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: For 310 only....                        *
    *                      1.Work dataset size may be              *
    *                      underestimated, leading to problems     *
    *                      during the sort phase of the utility.   *
    *                      Possible symptom is SB37 on TnnnMG data *
    *                      sets. PB 8798                           *
    *                      2.Padding of null DBCS columns          *
    *                      is made with a SBCS blank character     *
    *                      while it should be made with a DBCS     *
    *                      blank character. PB 8834                *
    *                      3.Msg INZU298E LOGICAL RECORD           *
    *                      LENGTH OF THE OUTPUT FILE SYSREC01      *
    *                      IS-2147483455 is issued when conversion *
    *                      from XML data to char data is requested *
    *                       PB 8841                                *
    *                      4.Incorrect generated LOAD sysin        *
    *                      when the output record contains XML LOB *
    *                      (CLOB,BLOB, DBCLOB) data. UNKNOWN is    *
    *                      specified as the type for the XML LOB   *
    *                      data field instead of CLOB. PB 8842     *
    *                      5.SQLCODE : -452 when unloading         *
    *                      XML or LOB column into LOB  file        *
    *                      (use xLOBF keyword) with multifetch     *
    *                      enabled (ULROWSET>1). PB 8844           *
    *                      6.HPU loops when a fixed constant       *
    *                      is specified for a given column and     *
    *                      then the specified constant value was   *
    *                      sorted. PB 8849                         *
    *                      7.HPU ends with RC 8 without any        *
    *                      message when unloading from an          *
    *                      unsupported VIEW if DB2 FORCE is        *
    *                      specified. PB 8860                      *
    *                      8.The UNIT specified within             *
    *                      template is ignored when unload into    *
    *                      LOB file is requested.                  *
    *                      INZ509W UNIT NAME SPECIFIED IN TEMPLATE *
    *                      template-name IS IGNORED WHEN USING LOB *
    *                      FILE REFERENCE VARIABLES IN SQL.        *
    *                       PB 8845                                *
    *                                                              *
    *                      For 220 and 310....                     *
    *                      1.Wrong padding character is used       *
    *                      when all following conditions are true: *
    *                      - the tablespace has an ASCII or        *
    *                        UNICODE encoding scheme.              *
    *                      - a column has been added to the table  *
    *                        and no REORG or LOAD has been         *
    *                        performed afterwards.                 *
    *                      - the added column type is in the       *
    *                        following list:  CHAR,VARCHAR,        *
    *                        GRAPHIC,VARGRAPHIC.                   *
    *                      - the column is defined with the WITH   *
    *                        DEFAULT option.                       *
    *                       PB 8839                                *
    *                      2.Msg INZU066E NO TABLESPACE FOUND      *
    *                      FOR TABLE table-name is issued and      *
    *                      unload stops when unloading from an     *
    *                      ALIAS. This may happend only when HPU   *
    *                      is run under DB2 V810 (or later         *
    *                      version)  and if the ALIAS was defined  *
    *                      under DB2 V710 (or prior version).      *
    *                       PB 8848                                *
    *                      3.Conversion error when a scalar        *
    *                      function TIME(expression timestamp) is  *
    *                      used in a supported select. PB 8877     *
    *                      4.HEX(DECIMAL) gives an invalid         *
    *                      result. PB 8878                         *
    *                      5.Error when using scalar               *
    *                      functions GRAPHIC and VARGRAPHIC. HPU   *
    *                      issues some CONVERSION ERRORS. PB 8881  *
    *                      6.In DB2 V8 and V9, the CEIL            *
    *                      scalar function returns invalid data    *
    *                      type. PB 8882                           *
    *                      7.Conversion to DECIMAL ZONED (1)       *
    *                      or DECIMAL ZONED(2) is not correctly    *
    *                      processed when the select is processed  *
    *                      by DB2. PB 8883                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    For 310 only....
    1.Modules oestime, inzrunh, inzpabf were changed to fix the
      estimation problem.
    2.Module udbcrfel was changed to pad using a DBCS character
      instead of a SBCS character.
    3,4,5,6,7.Module inzpab was changed to process correctly this
      case.
    8.A message is issued to inform that the UNIT paramter is not
      taken into account.
      INZ509W UNIT NAME SPECIFIED IN TEMPLATE template-name IS
      IGNORED WHEN USING LOB FILE REFERENCE VARIABLES IN SQL.
    Explanation: The TEMPLATE definition for template-name specifies
    a UNIT name. This template is used to generate a Lob File
    Reference using a file reference variable processed by DB2.
    In such a case, the UNIT name is not used to create the file
    pointed to by the file reference. To create the file on a
    specific unit, use DFSMS ACS routines to assign a unit name
    depending on the dsname of the output file.
    Return code: 4
    User action: Change the TEMPLATE definition or accept
    return code 4.
    
    For 220 and 310....
    1.Function _inzpabfDetermineEctPvdf in inzpabf was changed so
      that the right CCSID is used to pad DEFAULT VALUES.
    2.Module inzqryv8 was changed to check if the column LOCATION
      is equal to blank or has a length of 0.
    3,4,6.Modules udbspxwr and inznode were changed to process
      correctly this scalar function.
    5.Modules udbspxwr and inznode were changed to swith to DB2
      access when these functions are used.
    

Problem conclusion

  • APPLY the PTF.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK45756

  • 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-05-23

  • Closed date

    2007-07-09

  • Last modified date

    2007-08-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UK26957 UK26958

Modules/Macros

  •    INZUTILB
    

Fix information

  • Fixed component name

    DB2 HI PERF UNL

  • Fixed component ID

    5697F4400

Applicable component levels

  • R220 PSY UK26957

       UP07/07/12 P F707

  • R310 PSY UK26958

       UP07/07/12 P F707

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