DSD.BCIPut call to OCONV failed

MURALI123 · Post by **MURALI123** » Mon Jun 29, 2009 12:34 am

Hi all,
i load the data from db2 to sql server which shows the below warning Column: ColumnName, NLS mapname: UTF8, Column data (after conversion): xxxx xxx?xxx, Column data (in hex, before conversion) xxxxxxxxxxxxxxxxxxx
can any body help me about the above warning how can i sloved?i am using ds server 8.0.1

thanks,
Malli

ArndW · Post by **ArndW** » Mon Jun 29, 2009 12:49 am

Which stage is generating the error? If a transform, what is your OCONV function?

[edited] - I just saw the "BCIPUT", which tells me which stage. What data types do you have - the error means that the contents of a field did not convert to the target data type. Since the fields will be stored internally as strings, this error could occur on any type of field which is modified from the source (which will be strongly typed as it comes from a database).

ray.wurlod · Post by **ray.wurlod** » Mon Jun 29, 2009 12:56 am

Welcome aboard.

DSD.BCIPut() is the function used by the ODBC stage when doing Insert or Update. So it's nothing to do with the reading from DB2. You have an ODBC stage writing to SQL Server, and that's where the problem lies.

ODBC stage requires that you conform to ODBC standards. One of those is that dates must be in YYYY-MM-DD format. Is it possible that you're getting something different out of DB2?

When NLS is involved, the maps must be compatible.

Also, can you please advise whether you're using "Date" in the data element column of the Columns grid in the stage that connects to SQL Server?

MURALI123 · Post by **MURALI123** » Mon Jun 29, 2009 2:57 am

Hi ray,
I am using the data type is VarChar2() in sql server and db2 also

Once again to find the below log :

Column: ColumnName, NLS mapname: UTF8, Column data (after conversion): XXXX XXXX?XXX, Column data (in hex, before conversion)
XXXXXXXXXXXXXXXXXXXXXXXXXX

here XXXX XXXX?XXX is a Input String data
XXXXXXXXXXXXXXXXXXXXXXXXXX is Hex numbers

can you give me what is the problem
Thanks,
Murali

MURALI123 · Post by **MURALI123** » Mon Jun 29, 2009 3:07 am

Hi ray,
i used in the column type is in sql server is NvarChar()

thanks,
Malli

ArndW · Post by **ArndW** » Mon Jun 29, 2009 4:56 am

What NLS setting is your db2? What NLS is your SQL Server? What NLS specifications did you give in the corresponding stages in DataStage?

MURALI123 · Post by **MURALI123** » Mon Jun 29, 2009 5:59 am

NLS Setting in DB2 is NONE
NLS is in SQL Server is also NONE
i set the NLS Locale to US-ENGLISH

Thanks,
Malli

MURALI123 · Post by **MURALI123** » Mon Jun 29, 2009 6:53 am

Hi,
Transformer stage generating the error
iam not used any oconv function but data is from db2 to odbc some rows are not populated because of the some invalid characters data.
so can you see the below post for full details.
Thanks,
Malli

ArndW · Post by **ArndW** » Mon Jun 29, 2009 8:22 am

Can you identify which column is causing the error? (remove columns one-by-one until the error goes away). The "BCI.PUT" call is not done in the transform stage - are you sure that this error is being caused there?

chulett · Post by **chulett** » Mon Jun 29, 2009 9:06 am

Keep in mind the fact that in Server jobs the transformer (the active stage) always "generates the error" regardless of the actual source of the problem.

MURALI123 · Post by **MURALI123** » Tue Jun 30, 2009 6:29 am

Hi,
the source string data Contains some invalid chracters with 2 rows those are not transfered to sql server so what i do to slove this issue.

here source is db2 column datatype is VarChar2() and target is SQL server column data type is NvarChar2().

can you suggest me how to transfer the above rows of data.

Thanks,
Malli

ArndW · Post by **ArndW** » Tue Jun 30, 2009 6:40 am

Malli,

we are trying to help you, but without additional information it is going to be impossible and trying to get this data from you is proving itself rather difficult. You state "some invalid chracters <sic>" but in reality characters can only be invalid codepoints when given a context; but without knowing which character values and which NLS code page it is impossible.

You will need to reduce your test case to a single row and preferably a single character, then get the numeric value of that character in the source and in DataStage. Before you narrow down the cause nobody can help you.

MURALI123 · Post by **MURALI123** » Tue Jun 30, 2009 6:49 am

Hi,
while loading data from db2 stage to ODBC is SQL Server i am getting the below warning

DSD.BCIPut call to OCONV failed.
Column: CountryName, NLS mapname: UTF8, Column data (after conversion): ?RGFD INMNGDS, Column data (in hex, before conversion) C65CDD4E442049534C414E4453

Here ? refers some invalid chracter

So can you suggest me how to slove this i am not used any Oconv Function
Input & output data is String.

Thanks,
Malli

ray.wurlod · Post by **ray.wurlod** » Tue Jun 30, 2009 4:34 pm

What NLS map name is being used when extracting from DB2?
Are the data in the DB2 table(s) really encoded using this map?

MURALI123 · Post by **MURALI123** » Tue Jun 30, 2009 11:23 pm

Hi,
NLS map name is Project default (ISO8859-1) used is used in db2 stage.
I dont know the data in db2 tables really encoded using this map.

so can you suggest me how can i slove this issue.

Thanks,
Malli

DSXchange