IBM Support

PM02613: XMLSERIALIZE TO SERIALIZE THE XML TO A CLOB GETS A -904

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • XMLSERIALIZE to serialize the XML to a CLOB gets a -904
    

Local fix

  • No Work Around
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All DB2 9 for z/OS users of the XMLSERIALIZE *
    *                 function.                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION: An SQLCODE904 or -904 with a reason     *
    *                      code rc00D50001 can occur for a query   *
    *                      which has many iterations of the        *
    *                      XMLSERIALIZE function.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    An SQLCODE904 or -904 with a reason code of rc00D50001 can occur
    for a query which has many iterations of the XMLSERIALIZE
    functions.  In the reported case, XMLSERIALIZE is used
    to serialize the XML to a CLOB and received the SQLCODE -904
    error after processing some 355 XML columns, each having an
    approximate length of 512 KB.  Currently, DB2 uses XML memory to
    temporarily cache the XMLSERIALIZE output.  However, because DB2
    did not reuse this memory, the -904 is issued.  DB2 should reuse
    the memory after each row.
    
    The following example illustrates a failing case exhibiting many
    iterations of the XMLSERIALIZE function that can result in
    accumulating XML storage if T2 has many rows.
    
    
       SELECT XMLSERIALIZE(XMLDATA AS CLOB(1M)),
              XMLSERIALIZE(XMLDATA AS CLOB(1M))
       FROM T2;
    

Problem conclusion

  • DB2 is modified to reuse the XML storage for the XMLSERIALIZE
    function to prevent the SQLCODE904 condition.
    
    Additional keywords: SQLXML
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM02613

  • Reported component name

    DB2 OS/390 & Z/

  • Reported component ID

    5740XYR00

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-12-02

  • Closed date

    2010-05-27

  • Last modified date

    2010-07-01

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

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

    UK57386

Modules/Macros

  • DSNXGSFN DSNXOAUX DSNXOOS2
    

Fix information

  • Fixed component name

    DB2 OS/390 & Z/

  • Fixed component ID

    5740XYR00

Applicable component levels

  • R910 PSY UK57386

       UP10/06/16 P F006

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":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.1","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
01 July 2010