IBM Support

IY94682: LOAD FROM CURSOR WITH REMOTE FETCH NOT ABLE TO SKIP PARTITIONING PHASE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The load from cursor with remote fetch is not able to skip the
    partitioning phase even though both tables are partitioned the
    same way and the source and target tables are on the same
    server.
    
    To reproduce the problem, on a partitioned database environment,
    create two tables which have exactly the same definition, and
    do a load from cursor with remote fetch between the two tables
    (note that you will need at least one row of data in the source
    table). In the table definition, specify at least two
    partitioning keys where the order of the keys are different
    from the column order, for example:
    
    
    CREATE TABLE "DB2INST1"."PROD_BAL"  (
                     "ACCOUNT_NUMBER" VARCHAR(15) NOT NULL ,
                     "PRODUCT_NUMBER" VARCHAR(15) NOT NULL ,
                     "BUS_SERVICE" VARCHAR(100) )
                    DISTRIBUTE BY HASH("PRODUCT_NUMBER",
                    "ACCOUNT_NUMBER")
    
    CREATE TABLE "DB2INST1"."PROD_BAL1"  (
                     "ACCOUNT_NUMBER" VARCHAR(15) NOT NULL ,
                     "PRODUCT_NUMBER" VARCHAR(15) NOT NULL ,
                     "BUS_SERVICE" VARCHAR(100) )
                    DISTRIBUTE BY HASH("PRODUCT_NUMBER",
                    "ACCOUNT_NUMBER")
    
    declare c1 cursor database sample user id using password for
    select *  from db2inst1.prod_bal;
    
    
    load from c1 of cursor insert into db2inst1.prod_bal1;
    
    
    In DB2 Version 9.1 GA, it will not skip the partitioning
    phase when it should. For example, you will see the following
    partition message in the screen output:
    
      PARTITION      002      +00000000    Success.
    

Local fix

Problem summary

  • USERS AFFECTED: Users running load operations from cursors in a
    partitioned database environment.
    PROBLEM DESCRIPTION: Refer to ERROR DESCRIPTION. If this APAR
    is not applied, a load from a cursor with a remote fetch cannot
    skip the partitioning phase. The load operation might attempt to
    partition the data unnecessarily.
    PROBLEM SUMMARY: Refer to the ERROR DESCRIPTION.
    

Problem conclusion

  • First fixed in DB2 Version 9.1 Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IY94682

  • Reported component name

    DB2 DPF

  • Reported component ID

    5724N7400

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-02-09

  • Closed date

    2007-08-23

  • Last modified date

    2008-10-10

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

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

Fix information

  • Fixed component name

    DB2 DPF

  • Fixed component ID

    5724N7400

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
07 January 2022