DSXchange

Hi,

Can I know whether Data Stage 7.5.1A is compatible with Teradata V2R6.2.
I am facing the issues in select query if the decimal datatype length is more than 18.

Please let me know on this.

Thanks,

Why not let us know what the 'issues' are that you are having?

I am using Teradata API as my source stage. And the table in the back end have Decimal(38,0) now the value of that Decimal is around (20,0).

But the Teradata API stage (Data Stage 7.5.1A) giving an error: Overflow occurred computing an expression involving DEMOTEST1.A1

But if the value of the decimal is <= (18,0). It works fine.

Is this the tool limitations or something else.

Please suggest me on this.

Thanks,

'Computing an expression'? Are you manipulating this decimal field in your sql or just trying to select it? Perhaps you could post your sql.

karthik_j013 wrote:Hi,

Can I know whether Data Stage 7.5.1A is compatible with Teradata V2R6.2.
I am facing the issues in select query if the decimal datatype length is more than 18.

Please let me know on this.

Thanks,

Karthi,

Plesae post the query.

Syed.

It is a simple query.

SELECT A1,A2 FROM DEMOTEST1;

DECIMAL 18 is the largest decimal precision possible in Teradata. It is a Teradata limitation.

Hi,

TTU 8.2 is supported and certified with DataStage 7.5.2 and above (7.5.3, 8.0X,..), so it could be the reason.

throbinson wrote:DECIMAL 18 is the largest decimal precision possible in Teradata. It is a Teradata limitation.

Actuall, in Teradata v2r6 can store more than 18 digits. Only the issue is
datastage 7.5.1A drivers are not campatible to handle more than 18 digits.
If it is integer we can use bigint. If really decimal values need to go for work arround to ODBC upgrade or need to store the value as varchar.

Hope this will help.

Syed

I was going by the Teradata pdf documentation for V2R6.0
-- 1143.pdf pg. 73.

n the precision. The range is from 1 through 18

Was it added for the .2 release of V2R6?