Archives of the TeradataForum
Message Posted: Mon, 30 Aug 2004 @ 17:54:37 GMT
Been there, done that with a few applications on our network.
Have your network admin trace the connections into the warehouse. You are probably right about the web-app. Sometimes the application server will echo a request because the timeout values are set too low so the application times out and resends the request.
Little does the Teradata system know that this is a repeat request because it is busy answering the first one then the second one then the (well, you get the idea.)
We found that the switches, firewalls, local directors or routers might also be a factor in this echo. Or simply put, your ASP application was designed this way to send a query every time someone hits a page.
All of this will become clear once you get the Network Admin to trace the echoing.
On our side we found that one of our applications had a memory leak and would start echoing 3 requests if we did not reboot the system once a day. ( this was not a good answer by the way!)
We spoke with the vendor and they provided a patch for the leak... All is well.
Try to determine where the request is coming from. This can be done using PMON or Teradata Manager ==> Sessions. Drill down into the SQL to determine the source IP and track it back to the system.
Even if it is a web application, it should have one source IP to trace back too.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 15 Jun 2023|