I follow the steps:
1.In configure OLE DB Connection Manager dialog, I click New.
2.In Connection Manager dialog ,I choose Native OLE DB\Microsoft OLE DB Provider for DB2.
3.In Connection Manager dialog I click the "Data Links" button. Now I am on "Data link property" dialog.
4.On connection tab, I enter fmdb for data source, which is my remote database name. On Network section I choose TCP/IP Connection and set the right IP/Port. Uncheck Single sign-on and enter the user and password. Then comes the Database section. Database name fmdb for Initial catalog,"fmdbrun" for Default Schema, then what is Package Collection?(My db2 database is in a AIX/RS 6000 box).
5.On advanced tab, I choose DB2/6000 for DBMS platform, ISO 8859-1 Latin-1(28591) for Host CCSID, and ANSI/OEM Simplified Chinese GBK(936) for PC Code page, then what's Default qualifer, I eft blank.
6. Then I switch back to "connection" tab, if I left "Package collection" blank and click "Test Connection" button,I got "Test connection failed because of an error in initializing the provider.- invalid parameter". If I use FMDBRUN(the default schema) for "Package collection" and click "Test Connection", I got "Test connection failed because of an error in initializing the provider. - The network connection was terminated because the host failed to send any data. SQLSTATE:08S01,SQLCODE:-605".
Anybody knows what's wrong.
#4
leave the default schema blank.
for package collection: user account that you are using to sign in with into package collection. then, click on packages once you have entered your info and packages will be rebinded on the server.
test connection
Default qualifer. I don't know what this references.
|||
Thanks for your help. Yes, now I can connect to my db2(v8.1 fixpak 13) database on aix. But there are other problems, I created a new OLE DB Source, using the microsoft OLE DB provider for db2 connection, I use "Table or view" data access mode, and I can list the tables and views from a aix box, but when I choose a table and click the "preview" button, a dialog with the following warning message appears:
The component reported the following warnings:
Warning at {A5BF9D8B-F130-4E7C-805F-28F8ACA90520}[OLE DB Source [3673]:
Cannot retrieve the column code page info 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 incorrent. If
the component does not support the property, the code page from the component's locale ID
will be used.
Choose OK if you want to continue with the operation.
Choose Cancel if you want to stop the operation.
My DB2 databse uses iso 8859-1 code page.
If a choose OK, visual studio will uses 100% CPU and stops responding, I have to kill the visual studio process.
And on the "Data link property" dialog, after I filled every thing ,"Test connection" button works well, but the "Packages" button throw a dialog with message" External component has thrown an exception".
|||
Are you defining 8859-1 as your default code page in your data flow source and destination?
Alwaysusedefaultcodepage property on the source and destinaton probably needs to be changed to TRUE
|||I had lots of problems connecting to our DB2 AS400. Here is a link to my solution. My error messages were different from yours. However, my solution might still work for you because it uses components and connection types that appear to be a lot more compatible with DB2.
http://www.mathgv.com/sql2005docs/UsingSSISwithAS400.htm
Thanks,
Greg|||
Yes, I have tried use the ADO.NET/ODBC and the ADO.NET/OLE DB methods, this way both IBM's and Microsoft's providers can work well, except correctlly interpreting ISO-88591 strings in DB2 varchar columns to unicode or other codepage strings.
|||Ryan.Kelley wrote:
Are you defining 8859-1 as your default code page in your data flow source and destination?
Alwaysusedefaultcodepage property on the source and destinaton probably needs to be changed to TRUE
Yes, on the "All" tab of the "Data link property" dialog I have seen Host CCSID is set to 28591and PC Code Page is set to 936, and even I set the following properties to the Extended Properties, the same problem occurs:
default code page = 28591;always use default code page = true
Is there any offical documentation to the Extended Properties property.
Have you tried to conver to your specific code page where there are conversion issues? Look into the link below.
CodePageConvert is an SSIS dataflow component that translates from and to any code page or unicode character representations.
http://www.microsoft.com/downloads/details.aspx?familyid=9E56417E-23D1-4FD3-8D6D-61314FAA2DE3&displaylang=en
Can you provide what your issues are right now?
Is it specific to gettinghte code page to display the proper char set? or is there erros that are occuring when the conversion is being done? can you provide the type of errors that you are running into.
|||
Have you tried to conver to your specific code page where there are conversion issues? Look into the link below.
CodePageConvert is an SSIS dataflow component that translates from and to any code page or unicode character representations.
http://www.microsoft.com/downloads/details.aspx?familyid=9E56417E-23D1-4FD3-8D6D-61314FAA2DE3&displaylang=en
Can you provide what your issues are right now?
Is it specific to gettinghte code page to display the proper char set? or is there erros that are occuring when the conversion is being done? can you provide the type of errors that you are running into.
When use the Microsoft OLE DB Provider for DB2, I can create an OLE DB Connection to DB2(and test connection success), and when create an OLE DB source using the OLE DB connection, I can fetch table/view list from DB2, but when I click the preview button ,the above warning dialog appears.
When use the IBM OLE DB Provider for DB2 and follow the same procedure, the preview button works, but the columns with varchar set to iso 88591 codepage can not be interpreted correctlly.
|||Have you tried to conver to your specific code page where there are conversion issues? Look into the link below.
CodePageConvert is an SSIS dataflow component that translates from and to any code page or unicode character representations.
http://www.microsoft.com/downloads/details.aspx?familyid=9E56417E-23D1-4FD3-8D6D-61314FAA2DE3&displaylang=en
Because OLE DB connection and source can't work, so I think it can't help.
|||I also put the issue on google groups, here is the link:
http://groups.google.com/group/comp.databases.ibm-db2/browse_thread/thread/25f91fd33c9ff2d3
|||Ryan.Kelley, are you here.|||Hi guys, I need your help,^_^|||Ryan.Kelley wrote: Have you tried to conver to your specific code page where there are conversion issues? Look into the link below.
CodePageConvert is an SSIS dataflow component that translates from and to any code page or unicode character representations.
http://www.microsoft.com/downloads/details.aspx?familyid=9E56417E-23D1-4FD3-8D6D-61314FAA2DE3&displaylang=en
Can you provide what your issues are right now?
Is it specific to gettinghte code page to display the proper char set? or is there erros that are occuring when the conversion is being done? can you provide the type of errors that you are running into.
When use the Microsoft OLE DB Provider for DB2, I can create an OLE DB Connection to DB2(and test connection success), and when create an OLE DB source using the OLE DB connection, I can fetch table/view list from DB2, but when I click the preview button ,the above warning dialog appears.
When use the IBM OLE DB Provider for DB2 and follow the same procedure, the preview button works, but the columns with varchar set to iso 88591 codepage can not be interpreted correctlly.
The "DefaultCodePage" warning is harmless... Are you talking about that warning dialog when using the Microsoft OLE DB Provider for DB2? Ryan mentioned how to eliminate that.
No comments:
Post a Comment