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.
APAR (Authorized Program Analysis Report) |
Abstract
LIC-DB-OTHER-SRCB6005121 A SQL QUERY WITH A HIGH VOLUME OF
SUBSTR SCALAR FUNCTIONS MAY RESULT IN SYSTEM CRASH SRCB6005121
Error Description
System crashed recursing DbpmBinaryPatternMatchOperation for a
SQL Query with a high volume of SUBSTR scalar functions
Problem Summary
System crashed since too many DbpmSubstringOperation filled and
eventually overflowed the stack. An SQL Query with a high
volume of SUBSTR scalar functions could cause this type of
problem and crash the system.
Problem Conclusion
There is an SQE query that has tons of attribute operations (AO)
called back to back performing substring functions. The calls
were not foliating, so the stack would grow until it overflowed
and took the system down. Fix was made to the AOs to make the
calls foliate (meaning no room was taken on stack) so the stack
does not overflow and crash the system.
Temporary Fix
Comments
Circumvention
PTFs Available
R540 MF54236 2094
R545 MF54238 2094
R610 MF54241 2122
R611 MF54243 2122
R710 MF54290 2115
Affected Modules
Affected Publications
Summary Information
Status............................................ | CLOSED PER |
HIPER........................................... | No |
Component.................................. | 9400DG3DB |
Failing Module.......................... | RCHMGR |
Reported Release................... | R610 |
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
Document Information
Modified date:
28 October 2013