compilation error "string too large"

kollurianu · Post by **kollurianu** » Tue Mar 07, 2006 12:58 pm

Hi All,

i got a compilation error

Compiling: Source = 'RT_BP2089/JOB.984735793.DT.1394537298.TRANS1', Object = 'RT_BP2089.O/JOB.984735793.DT.1394537298.TRANS1'
************************************************ Input string too long, limit 8192
(idEXECCOMPARE1.Transformer_5)

As iam comparing newrec and oldrec i have concatenated all the fields and
did comparings the input fields are around 125 ,

so i got the above error is there any way that i could fix this issue

Any ideas , greatly appreciated...

Thanks alot ..............

kcbland · Post by **kcbland** » Tue Mar 07, 2006 1:14 pm

Break your long constraint into sections using stage variables, and then compare a set of stage variables in the constraint. Your text is too long.

kollurianu · Post by **kollurianu** » Tue Mar 07, 2006 1:39 pm

wonderful idea Kenneth!!! but what is the max size of the string that datastage holds ...accordingly i would split the string to so many parts...

Thanks alot..........

ArndW · Post by **ArndW** » Tue Mar 07, 2006 2:09 pm

I've reached the limit in the graphical object size, I seem to recall part of the error message told you; perhaps it is 512 or 1024 bytes. If you are close, change then name of your incoming link(s) to just 1 letter, that will significantly reduce the overall string length. The best solution for long-term maintenance is to split the unwieldy line into several ones, though.

kcbland · Post by **kcbland** » Tue Mar 07, 2006 2:17 pm

The error message indicates 8192 bytes is the limit.

Arnd: The problem is a long constraint expression (See other posts regarding this).

ArndW · Post by **ArndW** » Tue Mar 07, 2006 2:23 pm

I missed the 8Kb in the message. Still, that long expression used a longish link name, chopping that down to 1 could save enough bytes to compile, though.

kollurianu · Post by **kollurianu** » Tue Mar 07, 2006 2:52 pm

i did not get clearly is the string too large or the value in the string is too long , when i checked that the length of the string value is 3350 bytes,so what did it mean 8kb , means string is too large...
i just had 2 stage variables one is for the current record and one is for the old record.

so please any one could clarify me....

Thanks alot.....

ArndW · Post by **ArndW** » Tue Mar 07, 2006 4:03 pm

I think you were using a builting null handling function, which gets expanded inline before compilation.

kollurianu · Post by **kollurianu** » Tue Mar 07, 2006 4:10 pm

Thanks alot Arnd!
so how it needs to be split....just randomly 2 or 3 parts ...

so is it the value in the stage variabes too long or stage variable is too long , just trying to understand..

Any ideas...
Thanks alot..

kumar_s · Post by **kumar_s** » Tue Mar 07, 2006 4:10 pm

Was record/field delimiter properly set?

ArndW · Post by **ArndW** » Tue Mar 07, 2006 4:12 pm

The value of the text is too long

ray.wurlod · Post by **ray.wurlod** » Tue Mar 07, 2006 4:27 pm

It's the actual expression that is too long. You need to create the same logic in a routine, and invoke that. Or to break up the long expression into a number of smaller ones, storing the intermediate results in stage variables, and logically combine the results there. I have created jobs that tested over 100 separate columns (reporting errors separately) by this means; they are still fairly efficient.

kollurianu · Post by **kollurianu** » Wed Mar 08, 2006 2:07 pm

Ray Thanks alot for ur response , i would try that way.

thanks alot every one....

parag.s.27 · Post by **parag.s.27** » Thu Mar 09, 2006 6:02 am

Hi,

I also had the same scenario where i need to concatenate all input fields to a single output fields and input has 325 columns.

Try to have two stage variables where in one have one you concat one and in other concat another.

then you compare these two stage variables

If you still get the problem then define the output column as Varchar with length 65536. then in this output column u concat all input columns.

cheers