Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
sqlways:troubleshooting-guide:db2:export-conversion:data:odbc-bytes-conversion [July 10, 2018, 12:55:49 PM] alexandr.kirpichnysqlways:troubleshooting-guide:db2:export-conversion:data:odbc-bytes-conversion [August 31, 2023, 12:06:53 PM] (current) volha
Line 1: Line 1:
 \\ \\
-[[http://www.ispirer.com|Ispirer Home Page]] +[[https://www.ispirer.com|Ispirer Website]] 
-[[http://www.ispirer.com|Ispirer SQLWays Migration Product Page]] +[[https://www.ispirer.com/products/db2-migration|Ispirer Capabilities - DB2 Migration]] 
-[[http://www.ispirer.com/?click=RequestSQLWays&from=IspirerWIKI|Request SQLWays]] +[[https://www.ispirer.com/download/download-demo|Free Trial]]
 ====== COLNAME Error - Converted N Bytes. X Errors Found Beginning At Offset   ====== ====== COLNAME Error - Converted N Bytes. X Errors Found Beginning At Offset   ======
  
 ===== Symptoms ===== ===== Symptoms =====
  
-During the export process from DB2 database you can see error “COLNAME Error - Converted 50 Bytes. 49 Errors Found Beginning At Offset 0”. Here is the screenshot, how the error message looks like in the sqlways.log file:+During the export process from DB2 database you can see error “COLNAME Error - Converted 50 Bytes. Errors Found Beginning At Offset 88”. Here is the screenshot, how the error message looks like in the sqlways.log file:
  
 {{:sqlways:troubleshooting-guide:db2:export-conversion:data:unsupp_chars_log.png|}} {{:sqlways:troubleshooting-guide:db2:export-conversion:data:unsupp_chars_log.png|}}
Line 19: Line 18:
 ===== Solution ===== ===== Solution =====
  
-To solve this case please go to the ODBC Data Source Administrator and edit your DB2 ODBC Connection. On the ODBC Driver settings please go on the Translation or Conversion tab, click "Advanced" button and check the 'Allow unsupported character' checkbox. Like it is shown on the screenshot:+To solve this caseplease go to the ODBC Data Source Administrator and edit your DB2 ODBC Connection. At the ODBC Driver settingsplease go to the Translation or Conversion tab, click "Advanced" button and check the 'Allow unsupported character' checkbox. Like it is shown on the screenshot:
  
 {{:sqlways:troubleshooting-guide:db2:export-conversion:data:unsupp_chars.png|}} {{:sqlways:troubleshooting-guide:db2:export-conversion:data:unsupp_chars.png|}}
Line 25: Line 24:
  
 \\ \\
-If you will have some additional questions or face with some difficulties please contact our support team and provide detailed description of the case you faced with: [[[email protected]]]+If you have some additional questions or face any difficultiesplease contact our support team and provide detailed description of the case you encountered: [[[email protected]]] 
  
  
-\\ 
-[[http://www.ispirer.com|Ispirer Home Page]] 
-[[http://www.ispirer.com|Ispirer SQLWays Migration Product Page]] 
-[[http://www.ispirer.com/?click=RequestSQLWays&from=IspirerWIKI|Request SQLWays]] 

© 1999-2024, Ispirer Systems, LLC. All Rights Reserved.