Archives of the TeradataForum
Message Posted: Sat, 16 Apr 2005 @ 18:25:36 GMT
| Subj: | | Re: ODBC HYT00 Login Timeout Expired message |
| |
| From: | | Victor Sokovin |
| | Then we did a restore of DBC and TD started to display the error ODBC HYT00 when we ran a complex query, and other clients wanted to
stablish a connection to TD using WINDDI or SQL ASSIsTANT. | |
HYT00 might be caused by a wide variety of reasons, from non-optimally functioning RAID configuration (which RAID do you use?) to bugs in the
ODBC driver. As you have recently replaced the disks, I'd say it might be worth to (re)test the RAID. Perhaps a good diagnostics utility can find
some problems.
| | Also the performance decreased even when the hard disks are faster than the past disks. | |
| | Does it have to do the number of amps in the performance? | |
| | The new configuration consists of 5 amps. | |
| | How can i calculate the correct number of amps to configure on this system taking in account the processors specification described
above? | |
I'd like to merely redirect you to the following thread in the archives:
www.teradataforum.com/teradata/20030228_210943.htm
.
It discusses a similar and seemingly simple example but shows that performance tuning is an equation with many variables even in simplest
cases. For example, the new disks are faster, which is good, but their capacity is probably higher as well, and that could be just too much for
the old CPUs, etc.
The thread also contains a practical discussion of the Vproc configuration.
Regards,
Victor
| 
