That error message comes from the par$er, so the only way I can think of the new setup generating the error, but the old one working fine would be that the new one is possibly using ODBC extensions ? (similar to the queryman option) ?

As a first step can you turn on DBQL on the user id and verify if both the SQLs are same ?

It looks like in new setup, Informatica is firing an MSR (multi statement request) where as the old seems to be the plain fashioned single statement insert. The former gives better performance than the later though.

I am not familiar with Informatica., but I think the right place to start looking for, would be some where in the Informatica process if it's "packing" multiple insert statements into a single request or so (in the name of efficiency).

do you think the problem is in the informatica setup or the odbc setup.in the new odbc driver their is many new parameters like :disable Asyc,Disable Parsing . . . are the new parameter can cause this behavior.

we've just learned that teradata does not supply an odbc driver for hp unix, 64 bit with the RISC processors (our machine). therefore we will not be able to connect directly to emedny with our new 64 bit version of informatica until such time that a driver becomes available or we upgrade to new machine or processors.

The driver worked fine with 32 bit and INformatica release 7.1.3. We are now upgrading to Informatica 8.1.1 with 64 bit, since Informatica only supports 2 releases back.