IBM Support

MA46067 - LIC-DB-OTHER-INCORROUT SQLRPGLE USING XML FAILS WITH
SQLSTATE:2000 SQLCODE:+100

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 APAR (Authorized Program Analysis Report)

Abstract

LIC-DB-OTHER-INCORROUT SQLRPGLE USING XML FAILS WITH
SQLSTATE:2000 SQLCODE:+100

Error Description

SQLRPGLE program that calls XML functions XMLSERIALIZE and      
XMLDOCUMENT utilises SMP and LOJ RIO spinning plans returns a  
SQLSTATE:2000 SQLCODE:+100 due to placement of the bufferscan  
node. This results in an INCORROUT.                            

Problem Summary

****************************************************************
* PROBLEM: (MA46067) Licensed Program = 5770999 for i 7.1,     *
*                                        i 7.2, and i 7.3      *
*           Usability of a Product's MAJOR Function            *
*            Although rare, some SQL query instances can cause *
*            wrong results returned if SMP parallelism.        *
****************************************************************
* USERS AFFECTED: All IBM i operating system users.            *
****************************************************************
* RECOMMENDATION: Apply LIC PTF MF63051 for i 7.1.             *
*                 Apply LIC PTF MF63048 for i 7.2.             *
*                 Apply LIC PTF MF63068 for i 7.3.             *
****************************************************************
SQLRPGLE program that calls XML functions XMLSERIALIZE and      
XMLDOCUMENT utilises SMP and LOJ RIO spinning plans returns a  
SQLSTATE:2000 SQLCODE:+100 due to placement of the bufferscan  
node. This results in an INCORROUT.                            

Problem Conclusion

During optimization, when a plan is chosen, if SMP/parallelism  
is enabled, the optimizer determines if a buffer scan node is  
needed  and where to put it in the query tree to feed the      
parallelism based on the determined query SMP degree.  There are
certain locations in a final plan node tree where a buffer scan
is legitimate and other locations where that type of node is    
not.  The logic to correctly place the buffer scan node when    
there are multiple, stacked left outer join RIO spinning nodes  
was not correct in all situations. That location is also        
predicated by the query's estimated record counts and the smp  
degree value determined by the optimizer.   If the buffer scan  
is placed in the wrong location in the node tree, during the    
execution of the plan,  the query could result in wrong results,
likely few records.                                            

Temporary Fix

                       *********                                
                       * HIPER *                                
                       *********                                

Comments

Circumvention


PTFs Available

R710 MF63051 PTF Cover Letter   7192
R720 MF63048 PTF Cover Letter   7068
R730 MF63068 PTF Cover Letter   7283

Affected Modules

         
         

Affected Publications

Summary Information

Status............................................ CLOSED PER
HIPER........................................... Yes
Component.................................. 9400DG3DB
Failing Module.......................... RCHMGR
Reported Release................... R720
Duplicate Of..............................




System i Support

IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG15Q","label":"APARs - OS\/400 General"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0;V7R2M0;V7R3M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16C","label":"APARs - IBM i 7.1 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0;V7R2M0;V7R3M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16E","label":"APARs - IBM i 7.2 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0;V7R2M0;V7R3M0","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG16G","label":"APARs - IBM i 7.3 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"V7R1M0;V7R2M0;V7R3M0","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
28 October 2017