This is a discussion on SQL30020 on extended ascii characters within the DB2 forums, part of the Database Server Software category; --> Hello, we have a legacy application written in C. It uses embedded sql to connect to the database and ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, we have a legacy application written in C. It uses embedded sql to connect to the database and to perform queries on it. Now we are writing several extensions in .net, and it would be necessary to use the same connection instance as the embedded sql because of transactions. So I open the database connection in .net (Odbc, OleDb and ibm .net data provider was also tried), and the embedded sql queries can use it. However, when a parameter in the embedded sql query contains extended ascii characters (e.g ö, ü, ä etc.), I get the following error: SQL30020N Execution of the command or SQL statement failed because of a syntax error in the communication data stream that will affect the successful execution.... Reason Code:0x220E, SQLSTATE=58009. In the legacy application we use single-byte characters to store strings exclusively. The codepage is 1250 on both the client computer and the database. We use DB2 9.1.200.166, the OS is Vista (XPSP2 was also tried) Tamas |