 | 1 | initial version |
It seems highly unlikely that the TCP symptoms you pasted have anything to do with duplicate records in the database. A duplicate ACK is just a message telling the other side that a packet hasn't been received when it should have, and "Previous segment not captured" means that a packet is missing. TCP connections transport data reliably (or fail completely, after retrying without success), but it doesn't duplicate anything when it comes to the actual application payload.
Having programmed database applications myself I can be reasoable sure that the problem is somewhere in the database/application logic, not the network That would mean that switches and network cards are not to blame for this.
| | 2 | No.2 Revision |
It seems highly unlikely that the TCP symptoms you pasted have anything to do with duplicate records in the database. A duplicate ACK is just a message telling the other side that a packet hasn't been received when it should have, and "Previous segment not captured" means that a packet is missing. TCP connections transport data reliably (or fail completely, after retrying without success), but it doesn't duplicate anything when it comes to the actual application payload.
Having programmed database applications myself I can be reasoable am reasonably sure that the problem is somewhere in the database/application logic, not the network That would mean that switches and network cards are not to blame for this.
