You are not logged in.

Problem with DB2/400 data access: Palo 3.2 CE in connection with IBM client access OBDC driver Version 11.64 or 11.00 (V5R4)

Dear visitor, welcome to Palo Community Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Momo2

Trainee

  • "Momo2" started this thread

Posts: 1

Date of registration: Aug 26th 2011

  • Send private message

1

Friday, August 26th 2011, 10:12am

Problem with DB2/400 data access: Palo 3.2 CE in connection with IBM client access OBDC driver Version 11.64 or 11.00 (V5R4)

Hi community,

we have made a change from Palo 3.1 CE with client access version V5R2 (odbc driver 9.00) to

Palo 3.2 CE with client access version V5R4 (odbc driver 11. 64 or 11.00).

If we test the connection entry in an etl project, we get the message:

[IBM] [iSeries Access ODBC-Treiber]Fehler bei Datenübertragungsverbindung. comm rc=8015 - CWBSY1006 - Benutzer-ID ist ungültig, Password length = 0, Prompt Mode = Never, System IP = ourSystemIP

But User ID und Password are ok.

Does anybody know about that problem. We are working on a windows 2008 R2 server system and we have tried both driver version 32 bit and 64 bit. Same result.

Thanks in advance for an answer.



Hello again,

We have solved the problem. We are using now genericDB and jdbc driver from client access.

This post has been edited 1 times, last edit by "Momo2" (Aug 26th 2011, 1:44pm) with the following reason: We have solved the problem

tish1

Sage

Posts: 761

Date of registration: Jul 13th 2009

Location: Vienna / Austria

Occupation: Senior Consultant @ Vector SW DV GmbH

  • Send private message

2

Monday, July 9th 2012, 9:49pm

Hi,

Quoted from "Momo2"

We are using now genericDB and jdbc driver from client access.

Very often this solution is faster than via ODBC. And you don't need a setup of Client Access as well.

Regards.
Robert Tischler
Senior Consultant Vector SW DV GmbH

Similar threads

Rate this thread