Database Commits not going through

[enzo]

Hi,

I was wondering if anybody else had this problem, we are trying to parse a very messy OBX segment, that involves a bit of procedure work. I have written a transform that has a SQL insert statment.

Everything works fine... except nothing gets comitted to the Database, in fact when I run the SQL-Profiler there is no commit.

Script:
while(obxtree[i] != null)
{
logger.info("Looping: "+ i.toString());

set_id = obxtree[i]['OBX']['OBX.1'].toString();

query = "" ;
logger.info(query);
dbConn.executeUpdate(query);
dbConn.commit();
i=i+1;
logger.info("End Of Loop");
}
logger.info("Survived this one");
dbConn.commit();
dbConn.close();
logger.info("Close -- Exit");


The values are correcty populated... the Profiler picks it up and find the correct SQL being, with Autocommit on and Off nothing gets committed to the server

Server is SQL-2005, Mirth is version 1.3.2

[nshaik]

Reatabase Commits not going through

To help isolate the problem, try this:

Use the same db login id/password and the update statement copy from the profiler. Exectue it from Microsoft Management Studio. Check if it is getting committed.

Hope it helps!

[enzo]

Reatabase Commits not going through

Well the SQL statement printed by the log file works fine on SQL Server, the SQL injection detected by the profiler states that there is an error. However I dont think that was ever meant to run from the console.

Either way there is no exception thrown by the object, as it would do if there was a malformed SQL statement.

Usually the output from the profiler looks like
1. Connection
2. Precision
3. SQL Statement
4. Variables for statement
5. Commit

Step five is missing, I cant move from mirth 1.3.2 to 1.5, and as yet I havent tested if this happens on mirth 1.5