If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

As we told you in the other newsgroup already: you have 5 NOT NULL columns (w/o defaults) in the table and assign only values for 4 of them. Unless you have some triggers in the picture that assign a value to the remaining NOT NULL columns, the above statement cannot work.

In short, we would need the complete DDL of all objects associated with the table and the INSERT statement.

this msg is detected because (for some reason) DB2 thought that you like to execute a function named '='. It definitely doesn't come from the insert-stmt.
Some we need to look somewhere else:
1) trigger
2) UDT
3) check-contraint

by all means, the '=' should come from somewhere. which is the starting point

First thing we did was to check for any Triggers, but none on this table and there are no check constraints as well. There was a stored procedure depending on this table, but as mentioned, there are no triggers to initiate this stored procudure.

The issue was resolved after we raised a PMR with IBM support. The issue was with referential integrity corrruption. (APAR IZ00678). -440 is also sometimes encountered as part of this issue it seems. After we dropped and recreated our FKs, the issue went away.

The catch here is even if you upgrade to the latest fixpak, the issue does not get resolved, because the referentail integrity constarints are already corrupted. So dropping and recreating is the only option. I guess IBM also has a patch just in case to clean up this mess.

ps. The same sqlcode was encountered even when we were trying to delete from the table. Both the issues got resolved now.