Re: Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2

On 04/11/2018 01:20 PM, karthik kumar wrote:

> Db2 server on a docker container on my laptop: IP address 172.17.0.4
> Db2 client where postgres server is installed is on a different
> container.  IP address: 172.17.0.3
>
> Output of db2 list node directory
>
> Node 2 entry:
>
>  Node name                      = MYDB3
>  Comment                        =
>  Directory entry type           = LOCAL
>  Protocol                       = TCPIP
>  Hostname                       = 172.17.0.4
>  Service name                   = 50000
>
> output of db2 list db directory
>
> Database alias                       = SAMPLE
>  Database name                        = SAMPLE
>  Node name                            = MYDB3
>  Database release level               = 14.00
>  Comment                              =
>  Directory entry type                 = Remote
>  Catalog database partition number    = -1
>  Alternate server hostname            =
>  Alternate server port number         =

Are you using this DB2 ODBC driver?:

https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.apdv.cli.doc/doc/t0024166.html

If so check out the links below for conflict between specifying an
Instance and Protocol =TCPIP:

https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.apdv.cli.doc/doc/r0024132.html

https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.apdv.cli.doc/doc/r0008807.html

>
> $ cat /etc/odbc.ini
> [SAMPLE]
> Description = DB2 remote SAMPLE Database
> Driver = SAMPLE
> servername = 172.17.0.4
> system = MYDB3
> username = db2inst1
> password = db2inst1
> port = 50000
> PROTOCOL=TCPIP
> Debug = 1
> Commlog = 1
>
> $ cat /etc/odbcinst.ini
> [SAMPLE]
> Instance       =  MYDB3
> Description     = DB2 ODBC Driver
> Driver          = /home/db2inst1/sqllib/lib64/libdb2.so
> CommLog         = 1
> FileUsage       = 1
> #DontDLClose    = 1
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com