Bare with me im buisness not technical. We have a screen that updates a DB2 table. The table then has a trigger to update another table when ever you insert rows on the original table. It seems to work fine the vast majority of time but i have had two occasions where we had a serious problem where dsipite the first table haqving been updated correctly the second table was not. It seems to be suring a period of heavy activity on the screen and update to the original table. Our DBD's tell me its not possible for the trigger to stop unless they manually do so.
No error was reported to us or trapped by our ops team and they only possible expenation they can give was if we were tryinbg to update a row that didnt exist.
Any one got any idea why this trigger would would hundreds of time, but not on two occasions.
No error was reported to us or trapped by our ops team and they only possible expenation they can give was if we were tryinbg to update a row that didnt exist.
Any one got any idea why this trigger would would hundreds of time, but not on two occasions.