| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IC98515 | Status: Closed |
RUN NNSTAT FAILED WITH SQL0134N OR SQL1131N WHEN THERE IS AN INDEX INCLUDE LOB TYPE COLUMN | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
You may meet SQL0134N or SQL1131N when running NNSTAT on an
nickname with an index inlcude lob type column.
Here is the reproducing SQLs:
db2 => describe table n1
Data type
Column
Column name schema Data type name
Length Scale Nulls
------------------------------- --------- -------------------
---------- ----- ------
C1 SYSIBM CLOB
32768 0 Yes
C2 SYSIBM CLOB
2097088000 0 Yes
C3 SYSIBM BLOB
2097088000 0 Yes
3 record(s) selected.
db2 => CALL SYSPROC.NNSTAT(
'TERASERV','DB2INST1','N1','C1',NULL,2,'/tmp/log1.txt::DIAG',?)
SQL1131N A stored procedure process has been terminated
abnormally. Routine
name: "SYSPROC.NNSTAT". Specific name: "NNSTAT_EXTENDED".
SQLSTATE=38503
or
db2 => CALL SYSPROC.NNSTAT(
'TERASERV','DB2INST1','N1','C1',NULL,2,'/tmp/log1.txt::DIAG',?)
SQL0134N Improper use of a string column, host variable,
constant, or
function "COUNT". | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fix Pack 4. * **************************************************************** | |
| Local Fix: | |
Use NNSTAT method 1 | |
| available fix packs: | |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 30.12.2013 10.09.2014 10.09.2014 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.4 |
|