home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC67821 Status: Closed

THE SQL TEXT FOR FAILED STATEMENTS (EG SQL0270N) DOES NOT APPEAR IN THE
EVENT MONITOR , INSTEAD THERE IS ONLY A " - "

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
If a sql statement fails with sqlcode its text may not appear in 
event monitor output 
 
for example: 
 
db2 "create table t1 (id int)" 
db2 "alter table t1 alter column id set generated always as 
identity" 
this will trigger -270 error with reason 72, "A nullable column 
cannot be changed to become an identity column" 
 
db2 "alter table t1 alter column id set generated always as 
identity" 
DB21034E  The command was processed as an SQL statement because 
it was not a 
valid Command Line Processor command.  During SQL processing it 
returned: 
SQL0270N  Function not supported (Reason code = "72"). 
SQLSTATE=42997 
 
However dynamic sql snapshot contains this statement text 
 
db2pd -db dbname -dynamic 
 
Dynamic SQL Statements: 
Address            AnchID StmtUID    NumEnv     NumVar 
NumRef     NumExe     Text 
0x0000002AC93CD760 124    1          1          1          1 
1          alter table t1 alter column  id set generated always 
as identity
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users prior to DB2V97 FP2                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* THE SQL TEXT FOR FAILED STATEMENTS (EG SQL0270N) DOES        * 
* NOTAPPEARIN THE EVENT MONITOR , INSTEAD THERE IS ONLY A  " - * 
* "                                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 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 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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
First Fixed in DB2 V97 FP2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.04.2010
22.06.2010
22.06.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 FixList