Support Forum

Ask questions and get help from MobileTogether experts.
MobileTogether Product Information
Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Options
View
Go to last post Go to first unread
mbr  
#1 Posted : Tuesday, January 6, 2015 3:42:39 PM(UTC)
mbr

Rank: Member

Groups: Registered
Joined: 8/11/2014(UTC)
Posts: 29
Germany

Thanks: 4 times
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.
bbv  
#2 Posted : Friday, January 9, 2015 7:23:22 PM(UTC)
bbv

Rank: Administration

Groups: Registered, Administrators
Joined: 7/21/2014(UTC)
Posts: 476

Was thanked: 80 time(s) in 80 post(s)
I've reread you posting twice but still don't get it, sorry. Any chance to send your MTD file for clarification - either to this forum or to Altova Support.
bbv  
#3 Posted : Thursday, January 15, 2015 10:38:21 PM(UTC)
bbv

Rank: Administration

Groups: Registered, Administrators
Joined: 7/21/2014(UTC)
Posts: 476

Was thanked: 80 time(s) in 80 post(s)
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
mbr  
#4 Posted : Thursday, January 15, 2015 10:57:31 PM(UTC)
mbr

Rank: Member

Groups: Registered
Joined: 8/11/2014(UTC)
Posts: 29
Germany

Thanks: 4 times
I unchecked the option and problem is solved. No more error messages in the server log.

Thanks a lot.
Users browsing this topic
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.