{"id":303,"date":"2014-02-04T10:25:52","date_gmt":"2014-02-04T10:25:52","guid":{"rendered":"http:\/\/it.tuxie.eu\/?p=303"},"modified":"2014-02-04T10:27:38","modified_gmt":"2014-02-04T10:27:38","slug":"db2-10-5-communication-serverclient-debian-7-2-x64","status":"publish","type":"post","link":"http:\/\/it.tuxie.eu\/?p=303","title":{"rendered":"DB2 10.5 communication (server<-->client), Debian 7.2 x64"},"content":{"rendered":"

We have „almost“ fresh DB2 install in our Debian environment, running in VirtualBox. Well, now we want to have this db2 instance as server and client (host) would be connecting into server from some GUI. Few steps are necessary.<\/p>\n

<\/p>\n

1) Server side<\/strong><\/p>\n

Setting communication protocol is mandatory. This activity is done in very old special environment = registry. Don‘ t shout and panic, DB2 registry are not so beloved Windows registry \ud83d\ude09<\/p>\n

db2inst1@debian:~$ db2set DB2COMM=TCPIP<\/strong><\/span><\/span><\/p>\n

And of course we can check all values in registry:<\/p>\n

db2inst1@debian:~$ db2set -all<\/strong><\/span><\/span>
\n[i] DB2COMM=TCPIP<\/span>
\n[i] DB2AUTOSTART=YES<\/span>
\n[g] DB2SYSTEM=debian<\/span>
\n[g] DB2INSTDEF=db2inst1<\/span>
\n[g] DB2ADMINSERVER=dasusr1<\/span><\/p>\n

Next we need to locate port number for service dedicated to db2 instance. Default values for me:<\/p>\n

db2inst1@debian:~$ cat \/etc\/services | grep db2<\/strong><\/span><\/span>
\nDB2_db2inst1\u00a0\u00a0 \u00a060006\/tcp<\/span>
\nDB2_db2inst1_1\u00a0\u00a0 \u00a060007\/tcp<\/span>
\nDB2_db2inst1_2\u00a0\u00a0 \u00a060008\/tcp<\/span>
\nDB2_db2inst1_3\u00a0\u00a0 \u00a060009\/tcp<\/span>
\nDB2_db2inst1_4\u00a0\u00a0 \u00a060010\/tcp<\/span>
\nDB2_db2inst1_END\u00a0\u00a0 \u00a060011\/tcp<\/span><\/p>\n

Ok, we can remember first line = 60006.<\/p>\n

Now database manager must know number to bind db2 service.<\/p>\n

db2inst1@debian:~$ db2 get dbm cfg | grep TCP\/IP<\/strong><\/span><\/span>
\n\u00a0TCP\/IP Service name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 (SVCENAME) =<\/span><\/p>\n

db2inst1@debian:~$ db2 update dbm cfg using SVCENAME 60006<\/strong><\/span><\/span><\/p>\n

Ok, time for restarting server and double check value \ud83d\ude42<\/p>\n

db2inst1@debian:~$ db2stop<\/strong><\/span><\/span>
\n02\/03\/2014 21:25:04\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0 0\u00a0\u00a0 SQL1025N\u00a0 The database manager was not stopped because databases are still active.<\/span>
\nSQL1025N\u00a0 The database manager was not stopped because databases are still active.<\/span>
\ndb2inst1@debian:~$ db2stop force<\/strong><\/span><\/span>
\n02\/03\/2014 21:25:11\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0 0\u00a0\u00a0 SQL1064N\u00a0 DB2STOP processing was successful.<\/span>
\nSQL1064N\u00a0 DB2STOP processing was successful.<\/span>
\ndb2inst1@debian:~$ db2start<\/strong><\/span><\/span>
\nSQL8007W\u00a0 There are „83“ day(s) left in the evaluation period for the product <\/span>
\n„DB2 Advanced Enterprise Server Edition“. For evaluation license terms and <\/span>
\nconditions, refer to the License Agreement document located in the license <\/span>
\ndirectory in the installation path of this product. If you have licensed this <\/span>
\nproduct, ensure the license key is properly registered. You can register the <\/span>
\nlicense by using the db2licm command line utility. The license key can be <\/span>
\nobtained from your licensed product CD.<\/span>
\n02\/03\/2014 21:26:08\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0 0\u00a0\u00a0 SQL1063N\u00a0 DB2START processing was successful.<\/span>
\nSQL1063N\u00a0 DB2START processing was successful.<\/span>
\ndb2inst1@debian:~$ <\/span><\/p>\n

db2inst1@debian:~$ db2 get dbm cfg | grep TCP\/IP<\/strong><\/span><\/span>
\n\u00a0TCP\/IP Service name\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 (SVCENAME) = 60006<\/span><\/p>\n

The only needed thing is to know ip address:<\/p>\n

root@debian:~# ifconfig | grep Bcast<\/strong><\/span><\/span>
\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 inet addr:192.168.56.102\u00a0 Bcast:192.168.56.255\u00a0 Mask:255.255.255.0<\/span><\/p>\n

Server side part is completed now.<\/p>\n

 <\/p>\n

2) Client side<\/strong><\/p>\n

Let\u00b4s try to connect with DBeaver<\/a>:<\/p>\n

\"\"<\/p>\n

\"\"<\/p>\n

Done.<\/p>\n

 <\/p>\n

-a-<\/p>\n","protected":false},"excerpt":{"rendered":"

We have „almost“ fresh DB2 install in our Debian environment, running in VirtualBox. Well, now we want to have this db2 instance as server and client (host) would be connecting into server from some GUI. Few steps are necessary.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[7,11],"tags":[],"_links":{"self":[{"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=\/wp\/v2\/posts\/303"}],"collection":[{"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=303"}],"version-history":[{"count":0,"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=\/wp\/v2\/posts\/303\/revisions"}],"wp:attachment":[{"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=303"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=303"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/it.tuxie.eu\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=303"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}