Load Ingest Data
Results 1 to 4 of 4

Thread: Showing Error While Mapping NVARCHAR Column

  1. #1
    Debasis.Sharma is offline Junior Member
    Join Date
    Jul 2010
    Location
    India
    Posts
    2
    Rep Power
    0

    Showing Error While Mapping NVARCHAR Column

    Showing Error While Mapping NVARCHAR Column.

  2. #2
    Gadi.Farhat is offline Development Manager
    Join Date
    Mar 2009
    Posts
    255
    Rep Power
    11
    What is the error? What are you doing exactly?
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

  3. #3
    Debasis.Sharma is offline Junior Member
    Join Date
    Jul 2010
    Location
    India
    Posts
    2
    Rep Power
    0

    RE Showing Error While Mapping NVARCHAR Column

    Created a TEST table on Source DB with following
    [T1] [int] NOTNULL,
    [T2] [nchar](10)NULL,
    [T3] [nvarchar](50)NULL,
    [T4] [nvarchar](max)NULL,
    [T5] [decimal](18, 10)NULL,
    [T6] [varchar](max)NULL,
    [T7] [varbinary](max)NULL,

    T1 Primary Key

    Created Same TEST table on Destination DB

    Try Attunity CDC it's not working

    TITLE: Package Validation Error
    ------------------------------

    Package Validation Error
    ------------------------------
    ADDITIONAL INFORMATION:

    Error at Full Load Data Flow [TEST Full Load Destination [34]]: Column "T2" cannot convert between unicode and non-unicode string data types.
    Error at Full Load Data Flow [TEST Full Load Destination [34]]: Column "T3" cannot convert between unicode and non-unicode string data types.
    Error at Full Load Data Flow [SSIS.Pipeline]: "component "TEST Full Load Destination" (34)" failed validation and returned validation status "VS_ISBROKEN".
    Error at Full Load Data Flow [SSIS.Pipeline]: One or more component failed validation.
    Error at Full Load Data Flow: There were errors during task validation.
    (Microsoft.DataTransformationServices.VsIntegratio n)
    ------------------------------
    BUTTONS:

    OK
    ------------------------------


  4. #4
    Gadi.Farhat is offline Development Manager
    Join Date
    Mar 2009
    Posts
    255
    Rep Power
    11
    Hi,

    The error you are getting is because the Full Load Source component exposes Unicode columns (nvarchar) as string (DT_STR) and the Full Load Destination component which uses the SQL Server Native OLEDB provider exposes unicode columns as Unicode (DT_WSTR).


    Use one of the following options to solve this problem:

    1. Add a Covert transformation between the Full Load Source and the Full Load Destination components to convert the columns from DT_STR to DT_WSTR.

    2. Add a new OLEDB Connection Manager to the package that uses the SQL Server Native OLEDB provider to connect to the source database and, replce the Connection Manager used by the Source component with the new created Connection Manager.


    Regards,

    Gadi
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •