Db2 ODBC showing columns with special character in single quotes in UDT

[former_member280203]

Hi,

Need Urgent help !

If we use the ODBC drivers for DB2 iseries as connection in Universe designer we have a situation where it shows single quotes against some columns that have special characters. How do we remove or convert them into a readable column without it throwing a INVALID TOKEN error (PFA screen shot of the error as well).

Environment Details: BO 4.1 SP 5

Tool: UDT

Database source: ODBC DB2 iseries 5 (connection 32 bit)

When we go with the default PRM settings the above issue persists. Do anyone have any ideas on specific paramters to set for this to resolve.

FYI, we already tried the below parameter and it doesnt resolve the wingle quotes.

<Parameter Name="DELIMIT_IDENTIFIERS">YES</Parameter>

  <Parameter Name="IDENTIFIER_DELIMITER">"</Parameter>

  <Parameter Name="DELIMIT_LOWERCASE">YES</Parameter>

[Former Member]

Hi,

I believe you need to edit the db2iseries.prm files under the SAP BO install directory. On my computer they are under "C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer".

db2\db2iseries.prm

db2\extensions\qt\db2iseries.prm

odbc\db2iseries.prm

odbc\extensions\qt\db2iseries.prm

I think it may only be the last one you need to edit but I changed all four on my system just to be sure. Add this new parameter at the top under <Configuration>.

<Parameter Name="IDENTIFIER_DELIMITER">&quot;</Parameter>

This will cause the columns to have double quotes around them which is what DB2 on IBM i expects.

HTH,

Brandon

[former_member8403]

Hi Divi,

DB2 for i version 5 is not supported any more by SAP BO 4.1.

Try with version 6.1.

Best Regards,

Mark

[Former Member]

Hi Divi,

Can you share the actual column names? Is it same as what we see in the screenshot?

Talking about single quote ('), it seems like its encoding is bit different. Can you simply delete and put single quotes again and then try to parse?

Regards,

Yuvraj

[former_member280203]

It doesn't work even if we remove the single quotes and parse it again. It still throws a error. My instinct says its a issue related to how it interprets column delimiter that have special characters. In BO 3.1 version we could get some blogs that suggest modification of PRM file but unable to find any help on how to so similar configuration for BO 4.1.