9/9/2019 Ibmda400 Ole Db Provider
'System.InvalidOperationException: The 'IBMDA400.DataSource.1' provider is not registered on the local machine.' But when i run trough the UI is runs fine. I am uisng OLE DB driver to the connect to AS400. Can you please tekk ne where a im going wrong. The log file entery is as follows. When creating a Linked Server to our AS400 using the IBM DB2 UDB for iSeries IBMDA400 OLE DB Provider, we are running into an issue. When trying to browse table or run queries using a Domain Admin.
Dear All, My objective to use SSIS to to pull data from DB2 and store into SQL Server. Working environment is: Database: DB2 UDB iSeries V5R3 Provider: IBM DB2 UDB for iSeries IBMDA400 OLE DB Provider SQL Server 2005 SP: Latest i-e SP2 In connection manager, i have changed the following properties in OLEDB driver settings and connection with DB2 is tested successfully. 1- CATALOG LIBRARY LIST = AS/400 library 2- PERSIST SECURITY INFO = TRUE 3- INITIAL CATALOG = Database Name 4- Defualt Collection = AS/400 library After testing connection, I Created an OLE DB source and in OLE DB Datasource Editor set following properties: 1- VALIDATE EXTERNAL METADATA = FALSE 2- ALWAYS USE DEFAULT CODE PAGE = TRUE In OLEDB source editor, if i use 'Table or View' name option then the drop table list is populated perfectly and i can specify any table. With this option Package executes fine. But if i use the SQLCommand and specify the query, it prase the query correctly and i can preview the data in this source editor. But upon execution package return the following error message. OLE DB Source 1 Error: An OLE DB error has occurred.
Error code: 0x80040E00. There is a workaround of this problem i-e to use Datareader in source but i am interested to go with OLEDB. Can anyone help in this regard. Thanks in Advance. Phil, These are the errors which i can see in SSIS progress tab: OLE DB Source 1 Error: SSIS Error Code DTSEOLEDBERROR.
An OLE DB error has occurred. Error code: 0x80040E00. DTS.Pipeline Error: SSIS Error Code DTSEPRIMEOUTPUTFAILED. 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. DTS.Pipeline Error: SSIS Error Code DTSETHREADFAILED. 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. DTS.Pipeline Error: SSIS Error Code DTSETHREADCANCELLED. 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. DTS.Pipeline Error: SSIS Error Code DTSETHREADFAILED. Thread 'WorkThread0' has exited with error code 0xC0047039. There may be error messages posted before this with more information on why the thread has exited.
Warning: SSIS Warning Code DTSWMAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (5) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount.
Change the MaximumErrorCount or fix the errors. Thanks, Babar. I have little success in narrow down the issue.
According to my test runs, this problem only occure if i try to use SQL command mode in OLEDB source and destination. These two controls produces no error with Table or View mode and package executes successfully.:) Unfortunately In Lookup transformation, both SQL command and Table mode produce the same error. But if i specify Table or View Mode and Table (in the database) has no data then no error is produced. As i manually enter some data in the lookup table the lookup transformation fails again.:(. Hello Just wanted to share some info I found after a long research. Many people seem to have this issue and no-one has been willing to share the solution and provide a workaround instead.
It looks like IBM has accepted the problem and created a PTF (APAR SE27941) to fix it. I have not tried it, but it really describes the problem. As we are behind loading PTF's on our system, maybe with this post someone will beat me to it and can let us know if it really works. This is the link to the APAR description.
If you search in the IBM PTF database using the APAR number you will get the details of the cumulative PTF. And let us know if it works.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |