This content has been marked as final. Show 2 replies
. . . .Have you checked dependencies (for your table and all associated PL/SQL) and verified that they all exist?
. . . .Has the offending table been redefined (columns, indexes, triggers, constraints)?
I just found the problem...
I have a trigger defined on the table that uses a synonym for another user table.
That synomym was dropped, so the trigger was invalid.
I didn't notice the problem because the trigger was disabled, so the WM$ procedure wasn't being generated, and there were no "visible errors".
Recreating the synomyn, the problem was solved.
Thanks for your help!