Hi, I'm trying to use The Microsoft OLE DB Provider for DB2 for SSIS 2008. It's not working, could any one please suggest what are the requirments or other alteratives to connect to DB2 using SSIS 2008? I also tried using SSIS 2008 iSeries IBMDA400 OLEDB Driver and doesn't seem to work as welll Thank you

Can you able to connect to the DB2 server from your machine? Try using ODBC. Thanks Ayyappan Thangaraj UG Lead, Puducherry, http://SQLServerRider.blogspot.com

You need to be running SQL Server 2008 Enterprise Edition to use the DB2 Provider.Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA Blog: Mr. Wharty's Ramblings Please mark solved if I've answered your question, vote for it as helpful to help other user's find a solution quicker

Dear Suzzane, Let me the see the error message you recieved. and Please insure that you installed IBM iSeries Access for Windows and its service pack. Please let me know. Thanks.

Hi Waldif: This is what I get when I try to run package. However, I can see the records when I execute the Statement from OLEDB SOURCE EDITOR - SQL Command Text. The error below occurs when I close OLEDB SOURCE EDITOR and try to run the package: STRANGE and Annoying: Error: 0xC0202009 at Data Flow Task, OLE DB Source [1]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E00. Error: 0xC0047038 at Data Flow Task, SSIS.Pipeline: 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. Information: 0x40043008 at Data Flow Task, SSIS.Pipeline: Post Execute phase is beginning. Thanks heaps. You mentioned service pack, if you could provide me with direct link to Service pack (if required and it's a solution) will be appreciated. This issue has been bugging me for quiet long time.

Suzzane, Please make sure that you installed iSeries Access for windows before installing the service pack. Use this link to find your service pack depend on your version: http://www-03.ibm.com/systems/i/software/access/windows/casp.html And please let me know. Thanks.

Downloaded the SI42424 and tried to install on XP 32 bit. and It gave me this error below: "The Primary Language version Mri2924 that is currently installed does not match any available langauge versions. The upgrade can not continue" Not sure what I've done wrong.

Also installed this patch (ftp://public.dhe.ibm.com/as400/products/clientaccess/win32/v5r4m0/servicepack/si37892/) and still getting this wierd behariour of OLEDB Source Editor: 1. On Command I pass SQL SELECT , then click on preview. I get this error: No error message available, result code: DB_E_CANTCANCEL(0x80040E15). (System.Data) 2. However, when I click on Build Query and Click Execute Query, it returns row. Bit frustrated and no idea which one of the following is not right. 1. SSIS 2008 Bug. 2. IBM Driver. 3. My Configuration (All I did is selected Native OLEDB\IBM DB2 UDB for iSeries IBMDBA400 OLE DB Provider and entered the server file name).

Dear Suzzane, The last error you posted is clearly means that you should install the Service Pack for IBM iSeries Access for Windows. I faced the same error before and after installing the SP it worked. Now we have to know which verions of SP should we install. So what is your IBM DB server version this may help. And remember that this error is not a Bug in SSIS 2008 nor IBM Driver. Please let me know. Thanks.

Thanks Heaps Walif. The connection is now working. However, I get the following error message when I set OLE DB Destination with command. " An OLE DB record is available. Source: "IBMDA400 Command" Hresult: 0x80004005 Description: "SQL0104: Token . was not valid. Valid tokens: <IDENTIFIER>. Cause . . . . . : A syntax error was detected at token .. Token . is not a valid token. A partial list of valid tokens is <IDENTIFIER>. This list assumes that the statement is correct up to the token. The error may be earlier in the statement, but the syntax of the statement appears to be valid up to this point. Recovery . . . : Do one or more of the following and try the request again: -- Verify the SQL statement in the area of the token .. Correct the statement. The error could be a missing comma or quotation mark, it could be a misspelled word, or it could be related to the order of clauses. -- If the error token is <END-OF-STATEMENT>, correct the SQL statement because it does not end with a valid clause.". Error: 0xC0209029 at Load PO to DB2, OLE DB Destination [1907]: SSIS Error Code DTS_E_INDUCEDTRANSFORMFAILUREONERROR. The "input "OLE DB Destination Input" (1920)" failed because error code 0xC020907B occurred, and the error row disposition on "input "OLE DB Destination Input" (1920)" specifies failure on error. An error occurred on the specified object of the specified component. There may be error messages posted before this with more information about the failure. Error: 0xC0047022 at Load PO to DB2, SSIS.Pipeline: SSIS Error Code DTS_E_PROCESSINPUTFAILED. The ProcessInput method on component "OLE DB Destination" (1907) failed with error code 0xC0209029 while processing input "OLE DB Destination Input" (1920). The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running. There may be error messages posted before this with more information about the failure."