We've had the same error message when we were calling a db2 query from a linked server on SQL server.

We found the issue to be that the query was executing on db2 with some output error messages for some records (trying to convert an invalid value to a TIMESTAMP_FORMAT) and when we mitigated that error the query was able to be called again from the linked server.

Perhpas some recors in the mentioned query return an divide by 0 error.