Thanks Mark, but no luck. This wierd record got here sometime after I had executed a DROP TRIGGER on it. OBJECT_ID and DATA_OBJECT_ID are both 0, so I cannot trace down to the system tables where it thinks the object lives.
I guess I'll have to bite the bullet and try metalink :-(