Skip to main content

How can I identifying 'Corrupted' Extracted Data?




  • Best answer
    DSP Expert

    DanDowney: In Collect, go to the Vertical View of the Target Source. Change the SAP Settings Language to 1 (Chinese). Then use BOA RFC to download the data. It will display correctly in the sdb.

  • DSP Expert

    JDanos: I always like to ensure that any language packs are installed on the servers that are used in the process, including SQL and APP. The other suspects are the actual drivers themselves and looking at some of the details of how a DSN is actually set up. Sometimes tweaks are needed to change how that driver works with double-byte.

  • DSP Expert

    VGazquez: Hi Andy, this is in addition to previous answers. The collation has two purposes:

    1. Relates to the bit pattern and code page
    2. Specifies how character data is sorted and compared (language, regional conventions, case-sensitive etc)

    The issue that you are having is due to the sort property. The range that you use in the like needs to sort the data to determine whether is in that range or not. For instance, the character 'ñ' , goes between 'n' and 'o' in the SQL_Latin1_General_CP1_CI_AS, but it goes after the 'z' in the Latin1_General_BIN. Same will happen with a vowel with or without accent and upper/lower case characters, or even special characters are in different order. Check the attached screenshot


Please sign in to leave a comment.