I am using a JDBC adapter to poll a DB2 table on an AS/400 system. The table is polled and the Basic Notification operation is used to begin the process of inserting the data passed in a document to a Siebel database. I am running into an issue if an error occurs within the component that polls the table on the AS/400. This table is used as a temporary table. Once the adapter picks up the data from the table, checks the XRef table (SQL Server) and publishes the document, the row is deleted from the temporary table. If an error occurs within this component, the row still gets deleted in the temporary table but the process does not publish the document; it is stuck in a loop because of the error.
Has anyone come across an issue similar to this? If so, what was done to resolve it?
As of right now I go through and remove the row from the temporary table using a delete operation if an error occurs, however I do not have a good way to store the data so it can be sent off to Siebel at a later time. If anyone can offer some good advice, that’d be great.