using long var char job failed, nvar job was successful

peep · Post by **peep** » Tue Sep 18, 2012 4:43 pm

Hi I was running a job and it failed while data type is long varchar.

but it ran fine with nvar char data type.our database is DB2.

what are the differences between these two datatypes?

what point of view do i need to research to find out the root cause of this issue?

from datastage point of view or Database point of view?

ray.wurlod · Post by **ray.wurlod** » Tue Sep 18, 2012 8:32 pm

It's from neither point of view; it's from a METADATA perspective that you have this issue.

VARCHAR is your traditional, variable-length character string containing, typically, ASCII characters.

NVARCHAR is one way of specifying that the contained data are encoded using something other than a single-byte character set. For example it might be encoded using some form of Unicode such as UTF-8, or it might be encoded using a character-set-specific encoding such as BIG5 for Chinese.

What you have to get right is that they match between DataStage and the database. This is usually accomplished by importing the table definition and loading that into DataStage jobs.

peep · Post by **peep** » Tue Sep 18, 2012 9:04 pm

so u r saying it could be either from database or datastage rite.

varchar has ascii character

what abt nvar char?

ray.wurlod · Post by **ray.wurlod** » Tue Sep 18, 2012 9:40 pm

Get yourself a premium membership so that you can read the whole of my answer, which does cover NVARCHAR data type.

You have also misinterpreted what I said, again (probably) because you can't see the entirety of my post.