When using Toad 4.7 (and previous versions) to do updates to tables on the data grid, there is an issue with a particular table.
When trying to update one specific column (a date) on a specific row, the update produced a -151. The issue is with updating the key column of the table but there was no update made to this column specifically. It looks like the SQL statement that was created to perform this update by Toad was attempting to set values on every single column on the table for that row even though only the one column had changed.
Normally, this would not produce a -151. however, the table in question was a partitioned table created many years ago (DB2 v5 and migrated to the current 8.1.5 database), and apparently the rules for updating this table are very different than newly created partitioned tables.
SETs on an update should only be done on columns that were updated, not everything.