DB2 FOR LUW / DB2FORLUW / 970 - DB2

When the same ALTER TABLE ... ALTER COLUMN SET DATA TYPE is 
called multiple times it may return a SQL0670N on subsequent 
attempts if the following two conditions are met as part of 
the call: 
 
- the new data type specified is identical to the existing 
  data type of the column 
- the data type is either DECIMAL or TIMESTAMP 
 
Example: 
 
$ db2 "create table tbl4k(col1 decimal(18,0))" 
DB20000I  The SQL command completed successfully. 
 
$ db2 "alter table tbl4k alter column col1 set data type 
decimal(18,0)" 
 
DB20000I  The SQL command completed successfully. 
 
$ db2 "alter table tbl4k alter column col1 set data type 
decimal(18,0)" 
DB21034E  The command was processed as an SQL statement 
because it was not a valid Command Line Processor command. 
During SQL processing it returned: 
SQL0670N  The row length of the table exceeded a limit of 
"4005" bytes. (Tablespace "USERSPACE1".)  SQLSTATE=54010 
 
- This APAR will remove the extraneous error message from 
  being presented on the subsequent executions of the command. 
- The error itself can be ignored as this statement has no 
effect 
  on column definition, even if successful.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 9.7.                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 7.                            * 
****************************************************************

Avoid running the same command multiple times.

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 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 9.7 FixPack 7.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC83537 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

13.07.2011
17.12.2012
17.12.2012

9.7.FP7