DB2 - Problem description
Problem IC74027 | Status: Closed |
DB2SYSC CRASHED IN SQLODIAGNOSEFREEBLOCKFAILURE() FOLLOWING USER INTERRUPT DURING LIKE PREDICATE PROCESSING | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Signal 11 crash can be experienced during LIKE predicate processing following a user interrupt. Stack trace can resemble the following: sqloCrashOnCriticalMemoryValidationFailure sqloCrashOnCriticalMemoryValidationFailure sqlofmblkEx sqlriCCCLikeLong (or sqlriCCCLikeLongEsc, sqlriCCCLikeComputeRulesCore, sqlriCCCLikeShort or sqlriCCCLikeShortEsc) sqlriExecThread sqlriExecThread sqlrita sqlriExecThread sqlri_mj sqlriSectInvoke sqlrr_smp_router sqlrr_subagent_router sqleSubRequestRouter sqleProcessSubRequest RunEDU EDUDriver sqloEDUEntry | |
Problem Summary: | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Comment | |
This will improve the DB2 code. Since like predicates is common practice for writing a query | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.01.2011 08.12.2011 08.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |