Post reply

column code page warning in lookup transformation

  • March 1, 2007 at 6:29 am

    #369704

     Regarding the warning about "Cannot retrieve the column code page from the OLE DB provider. If the component supports the "DefaultCodePage" property, the code page from that property will be used. Change the value of the property if the current string code page values are incorrect. If the component does not support the property, the code page from the component's locale ID will be used."

    Setting AlwaysUseDefaultCodePath="TRUE" will cause this error to go away

    This works fine with oledbsource and destination.

    But how to avoid for lookup transformation??

    I am using Oracle Provider for OLE DB 10.2.0.2.20.

    One more problem i am facing is, SSIS is mapping varchar2 to DT_WSTR.

    All suggestion/solutions are appreciated.

    Thanks

     

  • March 5, 2007 at 8:00 am

    This was removed by the editor as SPAM

  • March 12, 2008 at 12:54 am

    #788405

    Hi,

    I tried by setting the property validate external metadata to false. Its not showing any validation warning on the component during design but will show the warning during execution.

  • March 21, 2008 at 10:56 am

    #792612

    rana (3/1/2007)

    Setting AlwaysUseDefaultCodePath="TRUE" will cause this error to go away

    This works fine with oledbsource and destination.

    I am using Oracle Provider for OLE DB 10.2.0.2.20.

    One more problem i am facing is, SSIS ismapping varchar2 to DT_WSTR.

    All suggestion/solutions are appreciated.

    Thanks

    Unfortunately it isn't possible to turn it off for the Lookup component. Not in SSIS2005 anyway.

    -Jamie

    Jamie Thomson
    http://sqlblog.com/blogs/jamie_thomson

  • November 24, 2015 at 2:35 pm

    #1842196

    Does anyone have an answer for this question?

    I am working with a new client and we have implemented an SSIS with Oracle solution to run the ETL. We are using the Attunity drivers to manage the source and destination connections, but when implementing an SSIS Lookup transformation through OLEDB connection, we are running into this codepage error.

    If anyone has found a workaround or fix to this, I would appreciate it.

Viewing 5 posts - 1 through 4 (of 4 total)

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