Support Forum

Using "DB Execute" instruction with "For every node ..." option, the defined SQL operation (i.e. Update or Call <Stored Procedure>) is successfully executed on every selected row and $MT_DBExecute_Result is null.
The DBExecute instruction is embedded between "DB Begin Transaction" and "DB Commit Transaction".

While the operation itself is successful, the server log shows three error messages per involved row:
Database: [Microsoft][ODBC Driver Manager] Function sequence error
Database: [Oracle][ODBC]Invalid cursor state.
Database: [Microsoft][ODBC Driver Manager] Function sequence error

Obviously this seems to be a "cosmetic" problem only, but nevertheless it fills the server log and misleads people monitoring the server.

When replacing single updates on rows by using the "Save" operation on the DB connection, server log entries do not occur. But calls to stored procedures can not be replaced this way.

Thanks for sending your files to Altova Support.

The reason of this false reporting is because you have enabled the option "Store results of SELECT statements in $MT_DBExecute_Result" for SQL which has no SELECT statements in it. The easiest would be to simply uncheck this option, because it doesn't make sense in your case.

We have also added a workaround which would prevent reporting errors for such cases