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
varchar conversion
Moderators: chulett, rschirm, roy
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.
An explaination of the job design will help pointing out the problem too.
Can you also check if you have the length defined correctly.
Narasimha Kade
Finding answers is simple, all you need to do is come up with the correct questions.
Finding answers is simple, all you need to do is come up with the correct questions.
Re: varchar conversion
Why don't you define the varchar with 4000 in length ?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
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.
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.
Re: varchar conversion
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.
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:Why don't you define the varchar with 4000 in length ?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