Trouble with AS400 DB2 as a Data Source

  • I'm having Trouble with AS400 DB2 as a Data Source.

    When I preview the data I get an warning and then it displys the data::w00t:

    Warning at {E3C602D4-5D5E-45FC-90CB-D258DAFE5FA6}[OLE DB Source[1]]. Cannotretrieve the column code page info from the OLE DB provider. If the component supports the "DefaultCode" property, the code page from the property will be used. Change the value of the property if the current string code page values are incorrect. If the componenet does not support the property, the code page from the component's local ID will be used.

    Choose OK if you to continue with operation.

    Choose cancel if you want to stop the operation.

    Any help would be appreciated.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • I set the property "AlwaysUseDefaultCodePage" to true and the warning goes away.

    Now I'm getting the following errors:

    [OLE DB Source [1]] Error: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E00.

    Error: SSIS Error Code DTS_E_PRIMEOUTPUTFAILED. The PrimeOutput method on component "OLE DB Source" (1) returned error code 0xC0202009. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing. There may be error messages posted before this with more information about the failure.

    Error: SSIS Error Code DTS_E_THREADFAILED. Thread "SourceThread0" has exited with error code 0xC0047038. There may be error messages posted before this with more information on why the thread has exited.

    Error: SSIS Error Code DTS_E_THREADCANCELLED. Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown. There may be error messages posted before this with more information on why the thread was cancelled.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • I recreate the package on two servers. It failed on the first one but it ran on the second server without any warnings or errors.

    I installed IBM Client Access Components on the second server two weeks ago.

    I did not have to change any property settings.

    I still can't get it to execute on my machine.:unsure:

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • The file that runs the iSeries Service has the same version and size.

    On the machine that it does not work in 6/8/2005 modified date and on the machine that it is working it has a modified date of 3/11/2007.

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

  • I feel like I'm talking to myself, well I guess I am.:hehe:

    Resolved the problem removed the client access components from my client pc and it works.:-D

    For better, quicker answers on T-SQL questions, click on the following...
    http://www.sqlservercentral.com/articles/Best+Practices/61537/

    For better answers on performance questions, click on the following...
    http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

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

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