RE: SQL 2005: Microsoft OLE DB Providers for DB2 not working with

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Hello Todd,
thank you for your answer.

I have tried it from my PC and not directly on the server.
When I connectet remotely direct on te server and tried it out, it worked!
(With the Microsoft OLE DB Provider for DB2 that was made available November
2005)
Why? I dont know. I also do not know if this expected behaviour.

As I looked at the results, I see, that there are some little details to
solve manually.
Regards, Martin

"Todd C" wrote:

Hello Martin
I have had success using the Microsoft OLE DB Provider for DB2, but it
took me a while to get connected. You will probably need to know the Initial
Catalog and Package Collection properties, along with username and password.

My suggestion: Try designing a package without the wizard to make sure you
can connect to DB2. Get everything working on the DB2 connection and take
notes about various settings (for example, I had to put in the server's IP
address in three different places for it to work, and it took several
iterations of password settings).

Once you have that working, try going through the wizard again. After it
creates the package for you, open the Connection Manager for your DB2
connection and set it up the same as you did the first one.

I know wizards are good for doing a lot of the heavy package design for you
but I don't think they handle all the little details, especially for things
like this.

I assume you are using the DB2 connection available from the SQL Server 2005
Feature Pack that was made available November 2005?

If you still have trouble, post the error messages you get back here.

HTH
--
Todd Chittenden


"geisslerm" wrote:

Hello,
I'm trying to get data from my AS/400 to SQL Server 2005 using the SQL
Server Import and Export Wizard.
I have used:
IBM DB2 UDB for iSeries IBMDA400 OLE DB Provider,
IBM DB2 UDB for iSeries IBMDARLA OLE DB Provider,
IBM DB2 UDB for iSeries IBMDASQL OLE DB Provider,
Microsoft OLE DB Provider for DB2
all of them are not working. (throwing different errors)
Has anybody done this successfully?
If yes, how?

I do not want to export and import every table manually :-)

Regards
Martin

.

Relevant Pages

  • RE: web parts and a database
    ... service's provider can not correctly establish ... connection to the underlying database. ... services(include membership, rolemanager, profile, personalization ...) ... Are you creating and developing the web project through HTTP/IIS server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: cant send email
    ... It means you were trying to send from a connection other than Cox. ... the provider of the SMTP server must match the ... Ask your home ISP if they have a port other than '25' for SMTP. ... Substitute the SMTP server belonging to your away-from-home connection. ...
    (microsoft.public.windows.vista.mail)
  • Re: VS2008 using SQL2k as membership provider?
    ... occurred while establishing a connection to the server. ... (provider: Named Pipes Provider, ... My config file looks like ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: web parts and a database
    ... such problem is likely due to the webpart ... service's provider can not correctly establish ... connection to the underlying database. ... Are you creating and developing the web project through HTTP/IIS server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Cannot connect to an MSAS 2000 Server
    ... What happens is that if the 9.0 provider fails, it will try to do COM ... > I am trying to use ADOMD.NET v9.0 to connect to an MSAS 2000 Server. ... > Microsoft.AnalysisServices.AdomdClient.AdomdConnection Connection = new ... > endReceivalIfException, Boolean readSession, Boolean ...
    (microsoft.public.sqlserver.olap)