Archives of the TeradataForum

Message Posted: Thu, 17 Apr 2003 @ 21:18:38 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Thursday, April 17, 2003 17:08 -->

Capturing data with a network sniffer right off the Teradata machine might be difficult as you are likely to have many IP addresses to work with. Here are some thoughts.

If I were faced with this problem, I would first look to restrict the questionable query to a single COP entry and point that COP to a dedicated IP address. This might require some code modifications. Then eliminate the other traffic on the dedicated COP. This too could be a challenge, but not a show stopper. Should you do this, be certain to later undo it.

I hope that somebody who knows the workings of a network sniffer can add to this discussion by describing how a sniffer can restrict data collection.

Continuing with the idea of directing the transaction to a single COP, should you fail to prevent other transactions from using the specified COP, still attach the sniffer to the Teradata IP address and collect messages from the various transactions. One would expect to eventually catch the failing transaction.

Next, failing to dedicate an IP address, attach single or multiple sniffers to each IP address rotating thru the different IP addresses, collecting that massive data, until you eventually catch the culprit in action. I would think you were considering this is the basis for why you wrote this message.

	<Prev	Next>		<<First	<Prev	Next>	Last>>