So, I have 2 database instances, one is for development in general, another was copied from development for unit tests.
Something changed in the development database that I can't figure out, and I don't know how to see what is different.
When I try to delete from a particular table, with for example:
delete from myschema.mytable where id = 555
I get the following normal response from the unit test DB indicating no row was deleted:
SQL0100W No row was found for FETCH, UPDATE or DELETE; or the result of a query is an empty table. SQLSTATE=02000
However, the development database fails to delete at all with the following error:
DB21034E The command was processed as an SQL statement because it was not a valid Command Line Processor command. During SQL processing it returned: SQL0440N No authorized routine named "=" of type "FUNCTION" having compatible arguments was found. SQLSTATE=42884
My best guess is there is some trigger or view that was added or changed that is causing the problem, but I have no idea how to go about finding the problem... has anyone had this problem or know how to figure out what the root of the problem is?
(note that this is a DB2 database)
What are your favorite database-related discussion forums? [closed]
Effect of field name length of a database on performance?
Should you make a self-referencing table column a foreign key?
Alpha Software v 9
It seems to suggest that another table has a foreign key pointing at the problematic one, when that FK on the other table is dropped, the delete should work again.
How to fix possible db corruption?
(Presumably you can re-create the foreign key as well).
Database Driven Front End Controller / Page Management Good or Bad?
Does that help any?.
Approaches to a Wiki - Database hybrid
TBC files from an old and unknown database system
if you are using JDBC and the prepared statement did not get its arguments set before executing the query)?.
Can you do a select on that table for the row where id = 555 ? . You could try running a RUNSTATS and REORG TABLE on that table, those are supposed to sort out wonky tables..
Neither runstats nor reorg table have any affect on the problem..
your arguments of triggers, procedure, functions and etc.
datatype of arguments..