DSXchange

Hi all,

We are using a column as varchar without specifying any length.

But while loading in the oracle table we specify as 4000 length in oci stage. Records with length more than 110 are going to reject link with a warning in log which specify a future chance of truncation.

I tried using modify stage to remove warning and success load

It still goes into reject link.

can anyone suggest me a new idea

Thanks

What is the length of this column specified in your target oracle table?

Length in target table is 4000

narasimha wrote:What is the length of this column specified in your target oracle table?

What is the exact error message you get? This would give a better idea of what might be happening

An explaination of the job design will help pointing out the problem too.

Can you also check if you have the length defined correctly.

pkomalla wrote:Hi all,

We are using a column as varchar without specifying any length.

But while loading in the oracle table we specify as 4000 length in oci stage. Records with length more than 110 are going to reject link with a warning in log which specify a future chance of truncation.

I tried using modify stage to remove warning and success load

It still goes into reject link.

can anyone suggest me a new idea

Thanks

Why don't you define the varchar with 4000 in length ?

Error which i get is as follows

When checking operator: When binding output schema variable "outrec": When binding output interface field "LOOKUP_STRING" to field "LOOKUP_STRING": Implicit conversion from source type "string" to result type "string[max=4000]": Possible truncation of variable length string.

narasimha wrote:What is the exact error message you get? This would give a better idea of what might be happening

An explaination of the job design will help pointing out the problem too.

Can you also check if you have the length defined correctly.

If I mention 4000 through out the process, at remove duplicate sorting is using scratch space for 4000 which we cannot afford

So we left the length as empty throught out the job.

Just in the oci stage for load, we specify it as 4000 length varchar.

Chuah wrote:

pkomalla wrote:Hi all,

We are using a column as varchar without specifying any length.

But while loading in the oracle table we specify as 4000 length in oci stage. Records with length more than 110 are going to reject link with a warning in log which specify a future chance of truncation.

I tried using modify stage to remove warning and success load

It still goes into reject link.

can anyone suggest me a new idea

Thanks

Why don't you define the varchar with 4000 in length ?