PH06844: SQLCODE433 ON REMOTE XML FETCH WITH CONTINUE

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• A remote fetch for a XML column using FETCH WITH CONTINUE
  semantics may result in SQLCODE -433.
  
  There are cases when the sqlcode will not result on a remote
  XML FETCH WITH CONTINUE. The sqlcode will only occur
  when Db2 is not able to move the complete XML on the first FETCH
  (WITH CONTINUE). The reason is the SQLDA host variable
  buffer for the XML is less than the serialized XML.
  
  Note, a local fetch on a XML column with FETCH WITH
  CONTINUE semantics works fine. In addition, a LOB does
  not have the problem with either local or remote FETCH WITH
  CONTINUE semantics.
  
  
  
  Additional Keywords:
  DB2DDF DB2XML XMLALL SQLCODE433
  

Local fix

• 1. Write a JAVA application (or any programming language) to
     SELECT from a Remote RDBMS and INSERT into Db2 for z/OS.
  2. Run a manual LOAD from files on a distributed client and LOAD
     to Db2 for z/OS, but you need to store the serialized XML
     data temporarily somewhere.
  3. With Db2 for z/OS V12, DRDA fast load from files residing on
     distributed clients.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Db2 11 and Db2 12 for z/OS users of      *
  *                 XMLs when using FETCH WITH CONTINUE          *
  *                 statement or utility LOAD with cross-loader  *
  *                 function in a distributed environment.       *
  ****************************************************************
  * PROBLEM DESCRIPTION: An SQLCODE433 or -433 occurs when using *
  *                      XMLs and query with FETCH WITH CONTINUE *
  *                      or utility LOAD with cross-loader       *
  *                      function in a distributed environment.  *
  ****************************************************************
  * RECOMMENDATION: Apply corrective PTF when available.         *
  ****************************************************************
  An SQLCODE433 or -433 occurs when using XMLs and FETCH WITH
  CONTINUE or utility LOAD with cross-loader function in a
  distributed environment.
  
  The reason the sqlcode occurs is because Db2 fails to
  materialize XMLs on the wire before copying the first piece of
  XML data to the application. In other words, Db2 fails to
  process XMLs on the wire within the context of FETCH WITH
  CONTINUE  semantics.
  
  As a result, when Db2 detects there is still XMLs data on
  the wire to fit into the application storage, the SQLCODE is
  then incorrectly generated.
  
  Please note that when processing XML in the context of FETCH
  WITH CONTINUE semantics, Db2 needs to know the XML textual
  length before copying the first piece of XML data to the
  application. And the only way to know the XML textual
  length is to materialize XML.
  
  Additional keywords:  DB2DDF CROSSLOADER
  

Problem conclusion

• Db2 is corrected to avoid the SQLCODE when processing XML
  with FETCH WITH CONTINUE or LOAD utility with cross-loader
  function in the distributed environment.
  

Temporary fix

Comments

APAR Information

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

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

  UI61741 UI61742

Modules/Macros

•    DSNOLMAT
  

Fix information

• Fixed component name

  DB2 OS/390 & Z/

• Fixed component ID

  5740XYR00

Applicable component levels

• RB10 PSY UI61742

     UP19/03/26 P F903

• RC10 PSY UI61741

     UP19/03/23 P F903

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.