Archives of the TeradataForum
Message Posted: Thu, 22 Jun 2006 @ 14:54:37 GMT
| Subj: | | Re: Query State is PARSING |
| |
| From: | | Hough, David |
Look in dbc.sessioninfo to make sure COGNOS and Queryman are running in the same transaction mode, Teradata versus ANSI. Our experience here
is that a lot of the server based products force ANSI for cross-platform consistency, while the client tools choose the system default (almost
always Teradata). We currently have a problem query that generates different join plans depending on the transaction mode (incident is open).
If you want to test your query in both modes from Queryman, create a special DSN for ANSI testing and force ANSI mode on the ODBC driver
options panel. You may have to scroll the Session Mode option list to see ANSI, depending on the driver version (the box was too small on
some).
Don't modify your normal DSN to ANSI, and always logout of the ANSI version immediately after testing. ANSI transaction semantics start the
transaction with the first statement you enter and complete it only with a COMMIT WORK. That means you accumulate locks until you do the COMMIT
or logout, which makes Bad Things Happen on the system if you walk away from an incomplete session.
/dave
| 
