red_ghost
Member
Right now I'm working on an inventory system for a client. One of the problems that nothing can be done about is I can't debug on their system, because they do not have vb.net installed on it and refuse to do so. I also cannot access their DB2 from our system, and I can't monitor anything in their DB2 system either. The software I'm programming is setup in 3 segments. There is the user interface WMS system which writes out to a sql server database, there is a record processor that writes, reads, and compares data from SQL Server to the DB2, then there is their DB2 system. The problem I'm having is when my processor application takes the records in the interface table and does an insert into corresponding DB2 table that the record should be put in, an insert trigger catches it, but locks the table, which causes the record processor application to go haywire. They can't figure out why the locks are being generated. Its fairly simple on my side, I use a datareader to go through the sql database and get the records that aren't processed (that have a IE_Status='F') and then I do an insert into whatever DB2 table I'm supposed to. But since the trigger is causing a lock, it freezes up right at the command.ExecuteNonQuery(). The first insert happens, but freezes up right after. Its able to insert fine if he takes the triggers off the tables, so that leads me to believe its something with the DB2. Any ideas? 
