Post reply

SSIS 2016 problem when upgrading 2008 packages

  • September 15, 2017 at 3:33 am

    #340054

    I have a new sql server with SQL Server 2016 64bit., old server was SQL Server 2008 R2 64bit.
    I upgraded the ssis packages to the new version using BIDS and it went fine.
    When I opened a package that contains tables that fetches data from Oracle (using Oracle Provider for OLEDB version 12c) the Data flow OLEDB source reports a problem that it cannot convert certain columns that have the correct datatype.

    Example:
    id int
    description varchar(10)

    Using SSIS and the following settings in the packages.
    id - dt_I4
    description - dt_str

    The system fails to do this and reports an error that the unicode is incorrect.
    My workaround is to place a SSIS Data conversion that converts the columns to the correct type. WHY!!!! On the old system this works, why does SSIS automatically convert the columns to DT_WSTR when it is clearly DT_STR?

    Is this a setting or is it related to the OLEDB provider, and more importantly, how do I solve it.

  • September 15, 2017 at 4:10 am

    #1959554

    When using dt_str, you need to specify the code_page; normally this is 1252. Have you used the correct one?

    Thom~

    Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
    Larnu.uk

  • September 18, 2017 at 11:59 pm

    #1959895

    Yes, it is the same. The strange part is that when I fetch data from Oracle using a pl-sql select, the source OLEDB component wants to convert it to DT_WSTR. To get around the problem I had to do the convert to DT_WSTR and then add a new convert between the source and destination component that changes it back to DT_STR again.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply