|
Problem IC66118
|
Status: Closed |
INSTANCE CRASH IN FUNCTION SQLNG_BUILD_SET_OP DURING QUERY COMPILE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
This problem can only happen in v97 fixpack 1.
If the instance is not configured for DPF (therefore, it is a
single partition), and a query is compiled with the scrollable
cursor attribute turned on (CLI attribute), and it is not an
updateable scrollable cursor, then the compile of that query has
a chance to trap and cause instance crash with the following at
the top of the stack (see the stack traceback file):
sqlng_build_SET_op
sqlng_process_set_op |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users affected: all *
****************************************************************
* PROBLEM DESCRIPTION: *
* INSTANCE CRASH IN FUNCTION SQLNG_BUILD_SET_OP DURING *
* QUERYCOMPILE. *
****************************************************************
* RECOMMENDATION: *
* apply v97 fp2 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
fix contained in v97 fp2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.02.2010
12.07.2010
12.07.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
