SQLSTATE 01517

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
paritosh11
Participant
Posts: 5
Joined: Thu Nov 06, 2008 12:50 am
Location: India

SQLSTATE 01517

Post by paritosh11 »

Hi,

I am getting below warning message in my parallel job in a DB2/UDB stage.

SQLSTATE 01517: A character that could not be converted was replaced with a substitute character.

Where im using a select query of the form.

SELECT A.Column1, A.Column2 FROM staging_table A WHERE some condition

In here Column2 is a VARCHAR(50) extended unicode containing Korean characters.

I have checked for NULL in the table bt there is none..also used trim functions ...etc.

This warning can be ignored bt i need a reason it is coming and how to remove it.

Thank in advance.
paritosh
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

What character set is the DB2 database stored in, and what NLS settings are you using in your job?
paritosh11
Participant
Posts: 5
Joined: Thu Nov 06, 2008 12:50 am
Location: India

Post by paritosh11 »

ArndW wrote:What character set is the DB2 database stored in, and what NLS settings are you using in your job? ...
In DB2 it is VARCHAR(50)
and in my stage NLS setting is Job default (UTF-8).

I have also tried changing the NLS setting to ASCL_KSC5601 bt the result is same.

let me know if you need any more info on this.


Thanks in Advance.
paritosh
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

Ask your DB2 administrator what character set the database is defined in. Make sure that setting is identical to what you specify in DataStage for the DB2 stage; that is probably the cause of your error.
paritosh11
Participant
Posts: 5
Joined: Thu Nov 06, 2008 12:50 am
Location: India

Post by paritosh11 »

ArndW wrote:Ask your DB2 administrator what character set the database is defined in. Make sure that setting is identical to what you specify in DataStage for the DB2 stage; that is probably the cause of your err ...
Hi,

This are the setting at DB2 Database.

Database code page = 1208
Database code set = UTF-8
Database country/region code = 1

now can u give me some idea what all i need to chage. As NLS setting in DB2 stage as i metioned before is Job default UTF -8.

Thank You,
Paritosh
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

I doubt that U can help - he's working on an all-Oracle site.

The second person personal pronoun in English is spelled "you".

You might like to perform an internet search for the SQLSTATE value.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
sendmkpk
Premium Member
Premium Member
Posts: 97
Joined: Mon Apr 02, 2007 2:47 am

Post by sendmkpk »

hi,
i am facing the same problem. but it is chinese, here.
In DB2 it is VARCHAR(255)
and in my stage NLS setting is Job default (UTF-8).

I have also tried changing the NLS setting to IBM-1386_P100_2002, UTF-16, result is same.
i tried doubling tripling length,

can some one, give his/her valuable insight into this.
Post Reply