Protocol Specific Error Codes 113
for Linux, Unix, and Windows Forum > Topic: SQL30081N error in client connect to DB2 serverThis topic has been locked. No replies Display:ConversationsBy Date 1-1 of 1 Previous Next yangwtao 270000B0N1 1 Post Pinned topic SQL30081N error in client connect to DB2 server 2013-10-27T02:15:38Z | Tags: Answered question This question has been answered. Unanswered question This question has not been answered yet. I am a new comer to DB2. The problem DB2 v10.5 express-c installed on both server and client. OS are Enterprise Linux 5.catalog node and DB both completed successfully. catalog DB2 server node on client db2 catalog tcpip node db2node remote DB2-EL5 server 50000 ostype linux catalog Database on client: db2 catalog db mydb at node db2node Anybody can help with my problem. Thanks! Problem discription: [db2adm@oc0386348167 ~]$ db2 connect to mydb user db2adm using rootroot SQL30081NA communication error has been detected. Communication protocol being used: "TCP/IP".Communication API being used: "SOCKETS".Location where the error was detected: "192.168.122.129".Communication function detecting the error: "connect".Protocol specific error code(s): "113", "*", "*".SQLSTATE=08001 [db2adm@oc0386348167 ~]$ Analysis: DB2 server configuration (192.168.122.129)： [db2inst1@DB2-EL5 ~]$ hostname DB2-EL5 [db2inst1@DB2-EL5 ~]$ db2 list db directory System Database Directory Number of entries in the directory = 2 Database 1 entry: Database alias = MYDB Database name = MYDB Local database directory = /home/db2inst1 Database release level = 10.00 Comment = Directory entry type = Indirect Catalog database partition number = 0 Alternate server hostname = Alternate server port number = Database 2 entry: Database alias = SAMPLE Database name = SAMPLE Local database directory = /home/db2inst1 Database release lev
wrote: > While trying to start multiple DB2 connections we receive the following > message: > SQL30081N A communication error has been detected. Communication > protocol being used: "TCP/IP". Communication API being used: "SOCKETS". > Location where the error was detected: "158.73.207.45". Communication function > detecting the error: "connect". Protocol specific error code(s): "113", > "*", "*". SQLSTATE=08001 113 means "host unreachable" (from https://www.ibm.com/developerworks/community/forums/html/topic?id=52ead6a3-88b3-4e54-b11b-8f33e6aac683 errno.h on Linux). Can you ping 158.73.207.45 from this system? Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 Previous message View by thread View by date Next message Error https://www.mail-archive.com/linux-390@vm.marist.edu/msg48414.html while connecting to DB2 Connect fro... Martin, Terry R. (CMS/CTR) (CTR) Re: Error while connecting to DB2 Co... Scott Rohling Re: Error while connecting to DB2 Co... Alan Altmark Re: Error while connecting to DB... Martin, Terry R. (CMS/CTR) (CTR) Re: Error while connecting to DB2 Co... Alan Altmark Re: Error while connecting to DB... Martin, Terry R. (CMS/CTR) (CTR) Re: Error while connecting t... Evans, Kevin R Re: Error while connecting to DB2 Co... Alan Altmark Re: Error while connecting to DB... Evans, Kevin R Re: Error while connecting t... Richard Gasiorowski Re: Error while connecti... Evans, Kevin R Re: Error while con... Richard Gasiorowski Re: Error while... Scott Rohling Reply via email to Search the site The Mail Archive home linux-390 - all messages linux-390 - about the list Expand Previous message Next message The Mail Archive home Add your mailing list FAQ Support Privacy OFAA4D13AF.BE0660FC-ON
a little change to install DB2 server in Linux, http://www.oraclema.com/db2/install-db2-in-linux.html espacially in silent mode. This post just a practice of my homework. And any suggestions will be welcome. I. pre-install tasks My test https://gist.github.com/gabrielfalcao/4216897 environment OS is RHEL6.5 X64, and DB2 version is v10.1. Since v9.7.2, the kernal parameters do not need to modify manually, as the protocol specific database manager modifies kernal parameters dynamically when it starts. And not like Oracle, DB2 with response file installation no need to create account in OS, as you can specify users in the response file. 1. edit /etc/hosts, add hostname and ip address, and disable selinux 1 2 protocol specific error 3 4 5 6 7 8 [root@hadr01 ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.56.60 hadr01 192.168.56.61 hadr02 [root@hadr01 worktmp]# sed -i '/^SELINUX/s/enforcing/disabled/g' /etc/selinux/config 2. extract DB2 binary, and run prerecheck 1 2 3 4 5 6 7 8 [root@hadr01 worktmp]# ls -ltr total 734968 drwxr-xr-x. 3 root root 4096 Apr 4 2012 server -rw-r--r--. 1 root root 999 Sep 5 10:24 db2ese_c.lic -rw-r--r--. 1 root root 752588810 Sep 5 10:24 v10.1_linuxx64_server.tar.gz -rw-r--r--. 1 root root 1528 Sep 5 10:59 db2ese.rsp [root@hadr01 worktmp]# cd server/ [root@hadr01 server]# ./db2prereqcheck Fix the warnings or errors until all requirements db2prereqcheck matched. 1 2 --For TSAMP installation [root@hadr01 server]# yum install libstdc++.i686 perl ksh pam.i686 -y a GitHub account Sign in Create a gist now Instantly share code, notes, and snippets. Star 17 Fork 13 gabrielfalcao/gist:4216897 Created Dec 5, 2012 Embed What would you like to do? Embed Embed this gist in your website. Embed Share Copy sharable URL for this gist. Share Clone via HTTPS Clone with Git or checkout with SVN using the repository's web address. HTTPS Learn more about clone URLs Download ZIP Code Revisions 1 Stars 17 Forks 13 TCP socket error codes Raw gistfile1.txt 0 = Success 1 = Operation not permitted 2 = No such file or directory 3 = No such process 4 = Interrupted system call 5 = Input/output error 6 = No such device or address 7 = Argument list too long 8 = Exec format error 9 = Bad file descriptor 10 = No child processes 11 = Resource temporarily unavailable 12 = Cannot allocate memory 13 = Permission denied 14 = Bad address 15 = Block device required 16 = Device or resource busy 17 = File exists 18 = Invalid cross-device link 19 = No such device 20 = Not a directory 21 = Is a directory 22 = Invalid argument 23 = Too many open files in system 24 = Too many open files 25 = Inappropriate ioctl for device 26 = Text file busy 27 = File too large 28 = No space left on device 29 = Illegal seek 30 = Read-only file system 31 = Too many links 32 = Broken pipe 33 = Numerical argument out of domain 34 = Numerical result out of range 35 = Resource deadlock avoided 36 = File name too long 37 = No locks available 38 = Function not implemented 39 = Directory not empty 40 = Too many levels of symbolic links 41 = Unknown error 41 42 = No message of desired type 43 = Identifier removed 44 = Channel number out of range 45 = Level 2 not synchronized 46 = Level 3 halted 47 = Level 3 reset 48 = Link number out of range 49 = Protocol driver not attached 50 = No CSI structure available 51 = Level 2 h