Queryman Locking up 1

[Guest_imported]

When we use Queryman to do delimited ASCII file exporting, It freezes up sometimes after it has been running for a while. It is always on diferent records. Has anyone had this problem and how did they fix it?

 

[tdatgod]

Hi,
Which version of Windows?
NT 4.0
NT 5.0 (W2K)
NT 5.1 (XP)

--

 

[TheTeradataKid]

Windows 2000

 

[tdatgod]

Hi,
I guess I should have asked, What version of Queryman?

HELP -> ABOUT

 

[MartinvdP]

Hi td_kid (and tdatgod)

I also experience some hang-ups, but then with the ODBC driver. (Doing queries with +/- 400.000 return rows)
For me it helped playing with the ODBC timeouts (via the odbc manager, not in my vb program), but still hanging seems a but drastic.
bytheway i am not sure if tweaking the odbc helps for queryman, it might use the CLI.

Also Queries do hang-up occasionally doing a rdAsyncEnable (vs rdExecDirect) query with the odbc. I find this very funny, while I assume queryman also does his thing a-synchrone.
I worked around it by only connecting a-synchrone, the rest direct but this is not the most user-friendly and effective solution, while I can not do some kind of process indication, and must do my stuff in a sequence.

Does anyone have something similar, or have a solution?

I’ll appreciate it,
Martin

Dev. Info
odbc version 2.08.00.00
ms-vb version: 6.0 sp3
ms-vb method: rdoEnvironment, rdoresultset
queryman: 5.1.0, 25 may 2000
Teradata: V2R3

 

[tdatgod]

Hi,
From what I can see it appears offical support or windws 2000 is in queryman 5.1.1 which is part of the TUF 6.0.1 release.

We just released TUF 6.1, 3 weeks ago (July 30, 2001). Queryman 5.2 was part of this release.

It accompanies teradata version 4.1 which was also released then, although you can use the one without the other, some of the features require both to be fully functional.

I don't know what was done to Queryman directly, as I work on the Database server side not the client utilities. I see there werre a lot of DRs closed against queryman.

I did see there is a 2.8.1 version of the ODBC driver, but it changed the way Time stamps and/or dates are handled, so using it may require changing your applications.


If you would like any documentation on the client software you can visit.....

http://www.info.ncr.com/sd/sd-1.cfm

click on Teradata Client and select the version of Software or the program your are using.

hope this helps.

--

 

[tdatgod]

Hi,
If you have a case that you can give me showing how to reproduce the HANG I could open a problem report, or you could open a incident with the GSC assuming you have a customer site ID.

However as I pointed out above we justed released 5.2 so I doubt I can get anyone to look at a 5.1 problem unless it can be reproduced at 5.2 as well.